[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Boot problems: PCI device(s) unrecognized..



This means that the code to recognize the card in the
kernel is not there. Everything will still work OK as
the driver is there and will load. I used to patch
pci.h before compiling a kernel to get rid of this for
me. With the latest kernel this has been *fixed*.

On Wed, 3 Jun 1998, Gregory Guthrie wrote:

> When I boot, I get:
> 
> 
> pcibios_init : BIOS32 Service Directory structure at 0x000f9a20
> 
> pcibios_init : BIOS32 Service Directory entry at 0xf04e0
> 
> pcibios_init : PCI BIOS revision 2.10 entry at 0xf0510
> 
> Probing PCI hardware.
> 
> Warning : Unknown PCI device (8086:7180).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (8086:7181).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (1023:9750).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (8086:7110).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (8086:7111).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (8086:7112).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (8086:7113).  Please read
> include/linux/pci.h 
> 
> Warning : Unknown PCI device (10b7:9050).  Please read
> include/linux/pci.h 
> 
> 
> 
> ALl the details from /proc/pci are below.
> 
> 
> The device is a 3Com 3c905 Ethernet card, which seems to load OK,
> 
> 
>   3c59x.c:v0.30-all 12/23/96 becker@cesdis.gsfc.nasa.gov
> 
>     3Com EtherLink III: Overriding PCI latency timer (CFLT) setting of
> 32, new     value is 255.
> 
>   loading device 'eth0'...
> 
>   eth0: 3Com 3c905 Boomerang 100baseTx at 0xd000, 00:60:08:68:65:9b, IRQ
> 11
> 
>     Internal config register is 16302d8, transceivers 0xe040.
> 
>     8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface.
> 
> 
> and runs fine!
> 
>   eth0: Initial media type MII.
> 
>   eth0: vortex_open() InternalConfig 016302d8. 
> 
>   eth0: vortex_open() irq 11 media status 8802.
> 
>   eth0: Media selection timer tick happened, MII.
> 
>   eth0: Media MII is has no indication, 8802.
> 
>   eth0: Media selection timer finished, MII.
> 
> 
> It also looks like my AGP graphics board shows up as PCI, and a few other
> bridge devices. It is a new PII motherboard (Asus).
> 
> 
> AM I ok, or do I need to do something.
> 
> 
> Thanks for any information or pointers.
> 
> 
> Gregory Guthrie
> 
>    guthrie@Mum.edu
> 
> --------------------------------------------------------
> 
> PCI devices found:
> 
>   Bus  0, device  11, function  0:
> 
>     Ethernet controller: 3Com Unknown device (rev 0).
> 
>       Vendor id=10b7. Device id=9050.
> 
>       Medium devsel.  IRQ 11.  Master Capable.  Latency=248.  Min
> Gnt=3.Max Lat=8.
> 
>       I/O at 0xd000.
> 
>   Bus  0, device   4, function  3:
> 
>     Bridge: Intel Unknown device (rev 1).
> 
>       Vendor id=8086. Device id=7113.
> 
>       Medium devsel.  Fast back-to-back capable.  
> 
>   Bus  0, device   4, function  2:
> 
>     USB Controller: Intel Unknown device (rev 1).
> 
>       Vendor id=8086. Device id=7112.
> 
>       Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master
> Capable.  Latency=32.  
> 
>       I/O at 0xd400.
> 
>   Bus  0, device   4, function  1:
> 
>     IDE interface: Intel Unknown device (rev 1).
> 
>       Vendor id=8086. Device id=7111.
> 
>       Medium devsel.  Fast back-to-back capable.  Master Capable. 
> Latency=32.  
> 
>       I/O at 0xd800.
> 
>   Bus  0, device   4, function  0:
> 
>     ISA bridge: Intel Unknown device (rev 1).
> 
>       Vendor id=8086. Device id=7110.
> 
>       Medium devsel.  Fast back-to-back capable.  Master Capable.  No
> bursts.  
> 
>   Bus  1, device   1, function  0:
> 
>     VGA compatible controller: Trident Unknown device (rev 243).
> 
>       Vendor id=1023. Device id=9750.
> 
>       Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
> Capable.  Latency=64.  
> 
>       Non-prefetchable 32 bit memory at 0xe3000000.
> 
>       Non-prefetchable 32 bit memory at 0xe2800000.
> 
>       Non-prefetchable 32 bit memory at 0xe2000000.
> 
>   Bus  0, device   1, function  0:
> 
>     PCI bridge: Intel Unknown device (rev 3).
> 
>       Vendor id=8086. Device id=7181.
> 
>       Medium devsel.  Fast back-to-back capable.  Master Capable. 
> Latency=64.  Min Gnt=9.
> 
>       Non-prefetchable 32 bit memory at 0x40010100.
> 
>       Non-prefetchable 32 bit memory at 0x22a0d0e0.
> 
>       Non-prefetchable 32 bit memory at 0xe3d0e200.
> 
>       Non-prefetchable 32 bit memory at 0xe3f0e3f0.
> 
>   Bus  0, device   0, function  0:
> 
>     Host bridge: Intel Unknown device (rev 3).
> 
>       Vendor id=8086. Device id=7180.
> 
>       Medium devsel.  Fast back-to-back capable.  Master Capable. 
> Latency=64.  
> 
>       Prefetchable 32 bit memory at 0xe4000000.
> 
> 
> 
> --------------------------------------------------------
> 
> Dr. Gregory Guthrie
> 
> guthrie@mum.edu         (515)472-1125    Fax: -1103
> 
>        Computer Science Department
> 
>        College of Science and Technology
> 
>        Maharishi University of Management
> 
>       (Maharishi International University 1971-1995)
> 
> --------------------------------------------------------
> 
> 
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 

/*********************** Running Debian Linux ***********************
*   For God so loved the world that He gave his only begotten Son,  *
*   that whoever believes in Him should not perish...    John 3:16  *
* W. Paul Mills            *  Topeka, Kansas, U.S.A.                *
* wpmills@midusa.net       *  http://homepage.midusa.net/~wpmills/  *
* wpmills@networksplus.net *  http://www.networksplus.net/wpmills/  *
* Bill, I was there several years ago, why would I want to go back? *
********************************************************************/


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: