Re: Why no lspci on install disk?
On Fri, Dec 02, 2005 at 03:12:32PM -0800, Ross Boylan wrote:
> On Fri, Dec 02, 2005 at 11:56:04PM +0100, Sven Luther wrote:
> > On Fri, Dec 02, 2005 at 10:07:01PM +0100, Frans Pop wrote:
> > > On Friday 02 December 2005 21:57, Ross Boylan wrote:
> > > > The etch beta1 netinst CD doesn't seem to have lspci on it, though the
> > > > installation reports ask for its output.
> > >
> > > The assumption is that you will end up with an installed system and be
> > > able to run lspci on that or that you have an old installation you can
> > > run lspci on.
> > > If the installation fails, one option is to use a live CD like Knoppix to
> > > get the info.
> > >
> > > > Have I missed something, or is this a bug (or feature)?
> > >
> > > It's a current feature we'd like to change at some point (and IIRC there
> > > is an open wishlist bug report for an lspci udeb).
> >
> > In the meantime, the information is hidden in /proc/pci and
> > /proc/bus/pci/devices (altough less obviously so). I still think a lspci udev
> > would come in handy to debug some missing modules problems that come up, but
> > as said, there is a workaround.
> >
> > Friendly,
> >
> > Sven Luther
> Is there an easy way to get from the proc files to info that is like
> that of lspci? I looked in /proc for my original report, but couldn't
> figure out what to do.
/proc/pci should contain most of this info :
Bus 36, device 14, function 0:
Class 0c00: PCI device 11c1:5811 (rev 0).
IRQ 40.
Master Capable. Latency=16. Min Gnt=12.Max Lat=24.
Non-prefetchable 32 bit memory at 0xf5000000
[0xf5000fff].
Ah, indeed, the names and such are no more there, used to be so in older
kernels. I guess lspci will be a good thing to have for that. Mmm, actually :
/usr/bin/lspci:
libpci.so.2 => /usr/lib/libpci.so.2 (0x0ffd7000)
libc.so.6 => /lib/libc.so.6 (0x0fe78000)
/lib/ld.so.1 => /lib/ld.so.1 (0x30000000)
So, you probably need only to put /usr/bin/lspci and /usr/lib/libpci.so.2 into
the system and run them. Not entirely sure though. you can just wget them, but
doing a .udeb out of them should be really trivial too, at least a
repackaged-udeb kind of udeb.
Friendly,
Sven Luther
Reply to: