Next-in-Thread Next Message

Sad "no valid ROM images found!" on 3.1.12 pcmcia-cs: How can I deal with it? 

Forum: Non-x86 PCMCIA Issues
Date: 2000, Mar 10
From: Tsuneya Watabe watabe

Hi there,

First of all, I'd like to apologize for this lengthy message.

Currently I'm using a 10B-T/100B-TX cardbus card (Macsense, tulip_cb) with a 
2.2.15pre7 kernel on my PowerBook 2400c/180. The card works fine with 3.1.11 
pcmcia-cs. Recently I successfully built a 2.3.50 kernel with PCMCIA support off 
at the kernel level. Then I compiled 3.1.12 pcmcia-cs for this new devlopmenal 
kernel. When booting into this new system, I get the messages below:

 kernel: Linux PCMCIA Card Services 3.1.12
 kernel:   kernel build: 2.3.50 #7 Fri Mar 10 11:41:24 JST 2000
 kernel:   options:  [pci] [cardbus]
 kernel: Intel PCIC probe:
 kernel:   TI 1130 PCI-to-CardBus at slot 00:13, mem 0x80803000
 kernel:     host opts [0]: [pci only] [pci irq 22] [lat 32/176] [bus 1/2]
 kernel:     host opts [1]: [pci only] [pci irq 23] [lat 32/176] [bus 3/4]
 kernel:     No interrupts!!  polling interval = 1000 ms
 cardmgr[510]: starting, version is 3.1.12
 cardmgr[510]: watching 2 sockets
 kernel: cs: cb_alloc(bus 3): vendor 0xffff, device 0xffff
 kernel: cs: no valid ROM images found!
 cardmgr[510]: initializing socket 1
 cardmgr[510]: unsupported card in socket 1
 cardmgr[510]:   no product info available
 kernel: cs: cb_free(bus 3)
 kernel: cs: cb_alloc(bus 3): vendor 0xffff, device 0xffff
 kernel: cs: no valid ROM images found!
 cardmgr[510]: initializing socket 1
 cardmgr[510]: unsupported card in socket 1
 cardmgr[510]:   no product info available

However, the same card is well recognized under 2.2.15pre7 kernel and 3.1.11 
pcmcia-cs as shown below:

 cardmgr[1492]: starting, version is 3.1.11
 cardmgr[1492]: watching 2 sockets
 kernel: cs: cb_alloc(bus 2): vendor 0x1011, device 0x0019
 cardmgr[1492]: initializing socket 1
 cardmgr[1492]: socket 1: Macsense MPC-200 PCB Rev3.1 DTCKA25
 cardmgr[1492]: executing: 'insmod /lib/modules/2.2.15pre7/pcmcia/cb_enabler.o'
 cardmgr[1492]: executing: 'insmod /lib/modules/2.2.15pre7/pcmcia/tulip_cb.o'
 kernel: cs: cb_config(bus 2)
 kernel:   fn 0 bar 1: io 0x100-0x17f
 kernel:   fn 0 bar 2: mem 0x900c0000-0x900c03ff
 kernel:   fn 0 rom: mem 0x90080000-0x900bffff
 kernel: tulip_attach(bus 2, function 0)
 kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by 
 danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
 kernel: eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:A0:0C:90:4D:1D, IRQ 23.
 kernel: eth0:  EEPROM default media type Autosense.
 kernel: eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
 cardmgr[1492]: executing: './network start eth0'
 kernel: eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
 kernel: eth0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
 kernel: eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.

These log messages suggest that cs on 3.1.12 with 2.3.50 kernel appears to try to 
use a different bus (bus 3 instead of bus 2) and eventually can not allocate the correct 
addresses of vendor and device. I don't know whether or not this error is deriving from 
the kernel itself or from pcmcia-cs. Is there any workaround for it?

BTW, I experienced the same "no valid ROM images found!" problem when dealing 
with other new 2.2.15x kernels (pre9, pre10, pre11 and pre12).

Furthermore, here is another problem with using 3.1.12 pcmcia-cs under my working 
kernel (2.2.15pre7). With this combination, I get the wrong IRQ setting for my card:

 kernel:   fn 0 bar 1: io 0x100-0x17f
 kernel:   fn 0 bar 2: mem 0x900c0000-0x900c03ff
 kernel:   fn 0 rom: mem 0x90080000-0x900bffff
 kernel: tulip_attach(bus 2, function 0)
 kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by 
 danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
 kernel: eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:A0:0C:90:4D:1D, IRQ 199.
 [snip]
 cardmgr[625]: executing: './network start eth0'
 cardmgr[625]: + ioctl: Operation not supported
 cardmgr[625]: + SIOCSIFFLAGS: Resource temporarily unavailable
 cardmgr[625]: + SIOCSIFFLAGS: Resource temporarily unavailable
 cardmgr[625]: + SIOCADDRT: Network is down
 cardmgr[625]: + SIOCADDRT: Network is unreachable

Changing PCIC_OPTS for irq definition didn't work.  Any hints?

TIA

Tsuneya Watabe

Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 2 All

1. None The irq thing is easy; I'm not sure about the bus problem by David Hinds, 2000, Mar 10
(_ Feedback Thank you for suggestions; beta solved IRQ problem and bus numbering was my fault. by Tsuneya Watabe, 2000, Mar 12

Add Message to: ""no valid ROM images found!" on 3.1.12 pcmcia-cs: How can I deal with it?"

Members Subscribe Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10