Hans van den Boogert wrote:
That explains something I experienced before. Thanks for the tip.
BTW, this pciutils package is not in the basic Debian 2.1 set up, yet with
every boot up the kernel invokes lspci, which is doesn't find of course. Is
this an oversight from the team who
Sorry. Your message could not be delivered to:
Jorge Araya (Mailbox or Conference is full.)
>> "RvdM" == Remco van de Meent <[EMAIL PROTECTED]> writes:
RvdM> It's strange indeed; it has come up before, and because the
RvdM> default Debian 2.1 install comes with 2.0.36, which doesn't
RvdM> support the /proc/bus/pci interface of the 2.2 kernels (the
RvdM> interface that pciutils uses) it
>That explains something I experienced before. Thanks >for the tip.
>BTW, this pciutils package is not in the basic Debian >2.1 set up, yet
>with
>every boot up the kernel invokes lspci, which is >doesn't find of
>course. Is
>this an oversight from the team who compiled the >installation list,
or
Hans van den Boogert wrote:
> BTW, this pciutils package is not in the basic Debian 2.1 set up, yet with
> every boot up the kernel invokes lspci, which is doesn't find of course.
> Is this an oversight from the team who compiled the installation list, or
> is there a reason for omitting? Seems a b
>Another tip that might be helpful; if you are using slink, install pciutils
>package, which provides
>lspci utility which can be invoked by pnpdump when called with the
argument '-c
>'.
>Once lspci is installed pnpdump worked fine for me, I did not have to make
any
>further
>modifications in /etc/
6 matches
Mail list logo