| 1 |
Joshua Murphy wrote: |
| 2 |
> On Mon, Jan 12, 2009 at 5:07 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 3 |
> |
| 4 |
>> Denis <denis.che@×××××.com> writes: |
| 5 |
>> |
| 6 |
>> |
| 7 |
>>>> You can use the "lspci" command, its in the pciutils package (if I'm |
| 8 |
>>>> not mistaken) to get your system hardware information. |
| 9 |
>>>> |
| 10 |
>>> Just like magic :-) Thank you so much! |
| 11 |
>>> |
| 12 |
>> If you liked lspci you will really like lspci -v. |
| 13 |
>> Pointed out to me recently here: |
| 14 |
>> |
| 15 |
>> From: Dale <rdalek1967@×××××.com> |
| 16 |
>> Subject: Re: Re: kernel config hell |
| 17 |
>> Message-ID: <4956DFA4.5050801@×××××.com> |
| 18 |
>> |
| 19 |
>> The last thing in each listing is the actual name of the kernel module. |
| 20 |
>> (if required) |
| 21 |
>> |
| 22 |
> |
| 23 |
> And for the drivers list only --> lspci -k |
| 24 |
> Cuts out all the extras that you're very unlikely to need :D |
| 25 |
> |
| 26 |
> |
| 27 |
|
| 28 |
You the man! Very nice information there. |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives