I'm using Bering rc2 in a box with two wired NICs and one wireless. When the box boots, the wireless network (eth2) fails to come up. (And dhcpd and shorewall fail too as a result.) But when I run '/etc/init.d/pcmcia restart' from the console there's no problem. And then dhcpd and shorewall can be started fine too.
>From /var/log/syslog: May 19 16:20:10 chloris kernel: Linux PCMCIA Card Services 3.1.33 May 19 16:20:10 chloris kernel: kernel build: 2.4.18 #3 Sat Apr 20 07:09:10 CEST 2002 May 19 16:20:10 chloris kernel: options: [pci] [cardbus] May 19 16:20:11 chloris kernel: Intel ISA/PCI/CardBus PCIC probe: May 19 16:20:11 chloris kernel: Ricoh RF5C296/396 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00 May 19 16:20:11 chloris kernel: host opts [0]: none May 19 16:20:11 chloris kernel: ISA irqs (scanned) = 3,4,5,7,9,12,14,15 status change on irq 15 May 19 16:20:11 chloris cardmgr[860]: watching 1 sockets May 19 16:20:11 chloris cardmgr[861]: starting, version is 3.1.33 May 19 16:20:12 chloris sshd[870]: connect from 192.168.1.2 May 19 16:20:13 chloris cardmgr[861]: socket 0: RayLink PC Card WLAN Adapter May 19 16:20:13 chloris kernel: cs: memory probe 0x0d0000-0x0dffff: clean. May 19 16:20:13 chloris cardmgr[861]: executing: 'insmod /lib/modules/2.4.18/pcmcia/ray_cs.o essid=MY_ESSID hop_dwell=128 beacon_period=256 translate=0' May 19 16:20:14 chloris kernel: ray_cs.c,v 1.31 2002/02/17 23:30:12 root Exp - Corey Thomas [EMAIL PROTECTED] May 19 16:20:14 chloris cardmgr[861]: + Using /lib/modules/2.4.18/pcmcia/ray_cs.o May 19 16:20:14 chloris kernel: ray_cs Detected: WebGear PC Card WLAN Adapter Version 4.88 Jan 1999 May 19 16:20:14 chloris cardmgr[861]: executing: './network start eth2' May 19 16:20:14 chloris kernel: eth2: RayLink, irq 3, hw_addr 00:00:F1:11:26:FF May 19 16:20:14 chloris cardmgr[861]: + /sbin/ifup: interface eth2 already configured I suspect that if I modified whatever calls '/etc/init.d/pcmcia start' to instead call '/etc/init.d/pcmcia restart, all would be well. That is, I think the reason my manual 'restart' succeeds is that the restart script does a './network stop eth2' before beginning the process that failed above. Any idea what might have grabbed eth2 before cardmgr gets fired up? I've searched the log files, and there's no prior mention of eth2. It's not looking wrong in any file in /etc, either, as far as I can see. Thanks, --Eric House PS I posted recently about a similar system where the problem was that the wireless net hadn't finished coming up when dhcpd started looking for eth2. That I fixed simply by adding a 'sleep 10' to /etc/init.d/dhcpc -- crude though that is. This is not the same problem; that is, the wireless card doesn't just need more time to init. ****************************************************************************** * From the desktop of: Eric House, [EMAIL PROTECTED] * * Crosswords 4.0 for PalmOS is out!: <http://www.peak.org/~fixin/xwords> * ****************************************************************************** _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
