Hi, I've installed Suse 7.1 on a machine equipped with two network cards. eth0 is handling my cable modem connection over twitsted pair. Ethernet chipset is SIS900, located on the motherboard. Yast2 mistakenly used a realtek driver for this (known bug of Yast2). I changed the etc/modules.conf line to read "alias eth0=sis900" in stead of "alias eth0=real1234-two" (don't look at the numbers 1234 since I can't remember them) Internet access using my cable modem is fine. So far so good. eth1 is handling a local network using coax. Chipset is realtek. No mistake in Yast2 this time, though it took me some time to figure out why eth0 was not working at first :-( A ne2k-pci driver is running for this ethernet interface. And it's working ok. I have a second PC (let's call this one B) connected over the local coax network and it's pinging the first machine (called A). When I type CTRL-ALT-F1 on machine A, the machine switches to a nice text-mode login screen. The switch takes some time (seems strange, but after some 5 seconds I'm in text mode). Now the ping fails. I switch back with CTRL-ALT-F7, I'm back in graphical mode. Now the ping works again ! This is highly repeatable. Text mode --> network not OK Graphical mode --> network OK When I'm in text mode, and check with netstat -i and ifconfig, I see that there are no received packets in A (although machine B is sending ICMP packets by the dozens). Also when I do a ping from A to B, I get no transmitted packets. In stead, they are counted as errored packets (on the transmit side). Since this error could be linked to the graphical card: it's an on-board nVidia TNT type (motherboard is 370 type). Now the tricky part is that I needed to give the machine to my uncle yesterday evening because his daughter needed it right away because she needs to know linux for one of her exams. My uncle can live with network-only-in-graphical-mode since that is his normal working mode anyway. Has anybody any clue about what could be causing this behaviour. I'll have some time on the machine in two weeks time, but any hints on what to check for are highly appreciated. I'll try to update this post tomorrow with more detailed HW-configuration data. Best regards, Nico De Ceulaer