| 1 |
On Fri, Nov 14, 2008 at 12:38 AM, Volker Armin Hemmann |
| 2 |
<volker.armin.hemmann@××××××××××××.de> wrote: |
| 3 |
> On Thursday 13 November 2008, Dan Wallis wrote: |
| 4 |
>> On 13/11/2008, Jorge Peixoto de Morais Neto |
| 5 |
>> |
| 6 |
>> <please.no.spam.here@×××××.com> wrote: |
| 7 |
>> > On Thu, Nov 13, 2008 at 7:05 PM, Dan Wallis <mrdanwallis@×××××.com> wrote: |
| 8 |
>> > > On 12/11/2008, Volker Armin Hemmann |
| 9 |
>> > > |
| 10 |
>> > > <volker.armin.hemmann@××××××××××××.de> wrote: |
| 11 |
>> > >> as root: lspci |
| 12 |
>> > > |
| 13 |
>> > > Why as root? I get exactly the same output when I run it as my own |
| 14 |
>> > > user as when I run it as root. Or have I got my system set up |
| 15 |
>> > > different to everyone else? |
| 16 |
>> > |
| 17 |
>> > $ lspci |
| 18 |
>> > bash: lspci: command not found |
| 19 |
>> > echo ${PATH} |
| 20 |
>> > |
| 21 |
>> > /usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1. |
| 22 |
>> >2:/opt/sun-jre-bin-1.5.0.06/bin:/opt/sun-jre-bin-1.5.0.06/javaws:/usr/game |
| 23 |
>> >s/bin At least in my system, the lspci binary resides in /usr/sbin, which |
| 24 |
>> > is not in ${PATH} |
| 25 |
>> > So you should either call lspci as root or issue the explicit command |
| 26 |
>> > /usr/sbin/lspci |
| 27 |
>> |
| 28 |
>> Yes, I do have that directory in my PATH. |
| 29 |
>> |
| 30 |
>> > That said, if you want to use the -v flag of lspci (for extra |
| 31 |
>> > verbosity), you should be root, or you will see some fields filled |
| 32 |
>> > with <access denied> |
| 33 |
>> |
| 34 |
>> Thanks for the tip; I didn't know about the verbose flag. It looks |
| 35 |
>> like that'll come in useful when I do my next build in a few weeks. |
| 36 |
> |
| 37 |
> not really. For an enduser --verbose isn't very helpfull. |
| 38 |
> |
| 39 |
|
| 40 |
Don't know if I qualify as an end-user, but I find: |
| 41 |
Kernel driver in use: |
| 42 |
very usefull. |
Archives