-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos F Lange wrote: > On Tue June 5 2007 09:37, G T Smith wrote:
<snip> > >> A very faint possibility is that there >> may be an issue with connection negotiation (Duplex, 10/100 mbps >> etc). > > Would there be any log for this negotiation? > What are the reported packet stats from ifstatus/netstat like? Lots of incoming error packets would be a strong indicator. With a consumer router you are unlikely to get this kind of report of connection status. So even if the driver configuration switches were available to force the type of connection it would be guesswork to get the right configuration in place. The suggestion made elsewhere of an iffy cable is worth considering, but could be easily eliminated by connecting with a cable you know has been working before. >>>> b) Which NIC? >>> nVidia Corporation MCP51 Ethernet Controller <snip> > No. Every machine is unique. This one just got a new NIC, which worked > fine in Suse for 2 days before I first booted into Windows. When I > booted back into Linux, then my problems started. That is why I > suspected the DHCP server had some hiccup, but resetting it did not > help. > The suggestion of making certain that all traces of the previous card configuration are removed which has also been made is also sound. I do not entirely trust YaST in this area. If the machine had not powered down for 2 days before booting into windows I would take a hard look at the udev persistant names rules and associated settings. These can generate the odd surprise. > Carlos FL -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGZcNpasN0sSnLmgIRAtE/AJ9vPwZEzUnSoMt5yI357K4emD9lswCgr0x7 /BaUVitbAO3OPxnW2uuVxog= =4YxZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
