Problem solved. I did more research based on some excellent clues provided by Buddy Coffey, Keith Warno, and BobF. My thanks to you all. :-) Here's what seems to have gone wrong... my /etc/modules.conf was set up like so: alias eth0 3c90x This would work for 2.2.13, because there was a /lib/modules/2.2.13/net/3c90x.o file in existence. When I compiled for 2.2.14, the same .config file as I used for 2.2.13 generated "3c59x.o". Under the very latest Yast 1.03 (I updated it today from an FTP mirror) I can select under System Administration Integrate Hardware into System Configure Networking device either: "3c59x/3c90x" or "3c90x/3c980 B/C series" The former will configure "alias eth0 3c59x" in /etc/conf.modules, while the latter will configure "alias eth0 3c90x". I double-checked my card... It's a 3C905B... The correct setting is the 3c59x/3c90x setting (alias eth0 3c59x). Under 'make menuconfig', I have selected: Network device support ---> Ethernet (10 or 100Mbit) ---> [*] 3Com cards <M> 3c590/3c900 series (592/595/597) "Vortex/Boomerang" support This seems to correspond to the .config file's line: "CONFIG_VORTEX=m" In amongst all these options, I suspect that I had compiled the 3c90x.o driver at some point in the past when I was messing with many different types of 3Com cards. By this point (switching to 2.2.14), I had only the one card in the system. To sum all that up: Probably operator headspacing on my part. It's working beautifully again. Thanks again for the help folks! I'm going to bed... Argentium -- 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/