Yes! Yes! Someone else saw the exact same weird problem I did! :) :) I have the same card, and saw the exact same problem when I went from RedHat to SuSE 6.4. I found a fix / workaround for myself, and reported it at length to SuSE tech support. It may have involved upgrading my kernel to 2.2.15, though. If you're going to fix things the way I did, first, could you confirm that in the present state you can boot up, do an "ifconfig eth0", and the network still won't work? I'd also be interested to know what you've tried so far. Here's what I did: Suffer through the tcpdump workaround long enough to download the sources to the pcmcia-cs-3.1.14 package (from pcmcia.sourceforge.net/pcmcia) and the sources to the Linux 2.2.15 kernel (from ftp.kernel.org/pub/linux/kernel/v2.2). Compile the kernel, then compile the pcmcia-cs package for the new kernel. Since I don't know who you are, I don't know if the prospect of recompiling stuff scares you, but if it does let me know and I'll give more detail on this section. At this point, you ought to find (at least, I did) that your network will start working if you do an "ifconfig eth0" or a tcpdump -p (which runs tcpdump without enabling promiscuous mode) but still won't work until then. Now in your /etc/pcmcia/network.opts file, there will be lines that say # Extra stuff to do after setting up the interface start_fn () { return; } (Dunno if you know all about schemes, but if you don't, just apply the following change to the codeblock labeled "SuSE,*,*,*)". Else apply the change to all the schemes you use. Happily, if you use YaST to configure different schemes, it will keep this manual change to the SuSE scheme.) start_fn () { ifconfig eth0; return; } and voila, your network will work without a problem. Mostly. Even with DHCP. And if it affects the modem, then that's just bizarre and I give up. It really shouldn't though, because this change is independent of the "serial" scripts. (I suspect my modem of having been broken before I switched to SuSE, so I haven't tested it.) The only annoying thing in this workaround is that if SuSEconfig runs for whatever reason (like your changing something in YaST) the network will break again. It may be that you can "rcpcmcia restart" it to get it to fix itself; I've just rebooted it so far. Now the reason for this. As you've noted, it's not dealing with responses to its ARP requests until something or other gets set, through ifconfig or tcpdump or whatever. I haven't been able to track down the reason for that, and it was mainly dumb luck that caused me to upgrade to kernel 2.2.15. (Before that, I tried the SuSE kernel, the recompiled SuSE kernel, the "vanilla" kernel, the recompiled "vanilla" kernel, and the APM kernel which just hated the pcmcia package. I also recompiled the pcmcia-cs sources for each of these kernels, except the APM one. Under none of them did "ifconfig eth0" get the network to start working, as I recall, and I'm too lazy to go through all that madness again to confirm this. Which is why I'm asking you. :) But I did notice that in the "SUPPORTED.CARDS" file that comes with the pcmcia_cs tarball, the card we have is listed with the tulip_cb driver and a line that says "Not recommended: support is experimental and unreliable". I'm just taking this to mean that I'll never figure out all of what's going on here, and it is something to do with that driver, and SuSE 6.3 and RedHat got lucky somehow, and if I cross my fingers then the pcmcia-cs-3.1.15 will support the Xircom CB cards better. -tara On Mon, 8 May 2000, Derek Fountain wrote:

I'm continuing to struggle to get SuSE running on my Dell 5000 notebook. SuSE-6.3 handled the Xircom network card (a PCMCIA based tulip) perfectly, but wouldn't talk to the modem (on the same Xircom card). I upgraded to SuSE-6.4 at the weekend and the modem problem is fixed. :-)

The network is now broken though. :-(

The network device is detected and set up correctly, and things configure as I want, but the adapter doesn't receive information. The really odd thing is that if I put the adapter in promiscuous mode using tcpdump, it works fine!

If I ping another machine on my net the arp request goes out, and is returned by the pingee, but the notebook doesn't receive the arp reply unless I've run tcpdump in another window. This is a less than convienient workaround!

Anyone got any ideas where the problem might be?

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/