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