| 1 |
Harry Putnam wrote: |
| 2 |
> Denis <denis.che@×××××.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>>> You can use the "lspci" command, its in the pciutils package (if I'm |
| 6 |
>>> not mistaken) to get your system hardware information. |
| 7 |
>>> |
| 8 |
>> Just like magic :-) Thank you so much! |
| 9 |
>> |
| 10 |
> |
| 11 |
> If you liked lspci you will really like lspci -v. |
| 12 |
> Pointed out to me recently here: |
| 13 |
> |
| 14 |
> From: Dale <rdalek1967@×××××.com> |
| 15 |
> Subject: Re: Re: kernel config hell |
| 16 |
> Message-ID: <4956DFA4.5050801@×××××.com> |
| 17 |
> |
| 18 |
> The last thing in each listing is the actual name of the kernel module. |
| 19 |
> (if required) |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
> |
| 24 |
> |
| 25 |
|
| 26 |
Yea, if that module don't work, you know what to kick to the curb and |
| 27 |
then try something else. |
| 28 |
|
| 29 |
Dale |
| 30 |
|
| 31 |
:-) :-) |
Archives