Re: pciutils package (was: Sound blaster 16 pnp)
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 compiled the installation list, or is there a reason for omitting? Seems a bit strange to me. Hans Infact it seems to be the best thing that could have been done. PnP support is provided beginning with kernel 2.2 series and slink is by default shipped with 2.0.36 pciutils package will not work with 2.0.36, so there is no use putting it into the basic Debian 2.1 setup. Slink is a kernel 2.2 ready distribution and it is nice to have lspci invoked (without making any modifications in the boot scripts) at runtime once you have upgraded to kernel 2.2 I get to like debian more and more when I notice such design details. Byeee Onur
NDN: Re: pciutils package (was: Sound blaster 16 pnp)
Sorry. Your message could not be delivered to: Jorge Araya (Mailbox or Conference is full.)
Re: pciutils package (was: Sound blaster 16 pnp)
>> "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 might have been better to not RvdM> to include that call to lspci. I think it has been done to allow to drop in a 2.2 kernel (I think you have to update netbase though). And as it doesn't do any harm on 2.0 kernels, it is easier to let keep the program execution in, as to advice the user to add it to the startup file. Ciao, Martin
pciutils package (was: Sound blaster 16 pnp)
>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 >is >there a reason for omitting? Seems a bit strange to >me. I was wondering about that message at boot up too. It started after upgrading to slink from hamm. I had no idea WTF lspci was, thought it was a hardware reference. Guess I'll have to install pciutils. BTW I did not have any problems configuring my SB16 (which I thought was a vibra), it's a 16 bit ISA card, PNP. Just let pnpdump do it's thing, edit the dump and then rebuild the kernel with the settings found. Then tested it with X11Amp (compiled from potatoe sources under slink). Now to get some real speakers instead of the 2 by nothing ones I have now. === Amateur Radio, when all else fails! http://www.qsl.net/wa2mze Debian Gnu Linux, Live Free or . _ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com
Re: pciutils package (was: Sound blaster 16 pnp)
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 bit strange to me. It's strange indeed; it has come up before, and because the default Debian 2.1 install comes with 2.0.36, which doesn't support the /proc/bus/pci interface of the 2.2 kernels (the interface that pciutils uses) it might have been better to not to include that call to lspci. -Remco
pciutils package (was: Sound blaster 16 pnp)
>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/isapnp.conf > 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 is there a reason for omitting? Seems a bit strange to me. Hans
