Sorry about the network.opts thing - I had reviewed the HOWTO, but I missed that bit... Ejecting and re-inserting the card has never resulted in the card becoming activated - it always comes back up non-functional. Here's the message log from an eject and re-insert: May 19 13:30:06 cpt kernel: cs: cb_free(bus 35) May 19 13:30:06 cpt cardmgr[489]: shutting down socket 1 May 19 13:30:06 cpt cardmgr[489]: executing: './network stop eth0' May 19 13:30:06 cpt cardmgr[489]: executing: 'modprobe -r 3c575_cb' May 19 13:30:06 cpt cardmgr[489]: executing: 'modprobe -r cb_enabler' May 19 13:30:10 cpt kernel: cs: cb_alloc(bus 35): vendor 0x10b7, device 0x6560 May 19 13:30:10 cpt cardmgr[489]: initializing socket 1 May 19 13:30:10 cpt cardmgr[489]: socket 1: 3Com 3CCFEM656B w/Winmodem May 19 13:30:10 cpt cardmgr[489]: executing: 'modprobe cb_enabler' May 19 13:30:10 cpt cardmgr[489]: executing: 'modprobe 3c575_cb' May 19 13:30:10 cpt kernel: 3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html May 19 13:30:10 cpt kernel: cs: cb_config(bus 35) May 19 13:30:10 cpt kernel: fn 0 bar 1: io 0x280-0x2ff May 19 13:30:10 cpt kernel: fn 0 bar 2: mem 0x60023000-0x6002307f May 19 13:30:10 cpt kernel: fn 0 bar 3: mem 0x60022000-0x6002207f May 19 13:30:10 cpt kernel: fn 1 bar 1: io 0x200-0x27f May 19 13:30:10 cpt kernel: fn 1 bar 2: mem 0x60021000-0x6002107f May 19 13:30:10 cpt kernel: fn 1 bar 3: mem 0x60020000-0x6002007f May 19 13:30:10 cpt kernel: fn 0 rom: mem 0x60000000-0x6001ffff May 19 13:30:10 cpt kernel: vortex_attach(device 23:00.0) May 19 13:30:10 cpt kernel: eth0: 3Com 3CCFE656 Cyclone CardBus at 0x280, 00:50:04:95:45:2c, IRQ 11 May 19 13:30:10 cpt kernel: eth0: CardBus functions mapped 60022000->c8046000 May 19 13:30:10 cpt kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII interface. May 19 13:30:10 cpt kernel: MII transceiver found at address 0, status 7809. May 19 13:30:10 cpt kernel: Enabling bus-master transmits and whole-frame receives. May 19 13:30:10 cpt cardmgr[489]: executing: './network start eth0' HOWEVER, at your suggestion, I tried the '/sbin/cardctl reset' command. There were no beeps. but the interface came up! I saw no messages added to the log as a result of this command. I've seen no differences in the log between when the card comes up OK and when it goes into the flashing 100 state. Finally, I have seen this message in the log quite a bit (don't know if it applies): May 19 14:05:40 cpt modprobe: modprobe: Can't locate module block-major-22 Thanks for your help! Michael |