-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos F Lange wrote:
I solved the problem with brute force (see my other e-mail today), but I wanted to reply here to see if learn some more.
On Tue June 5 2007 14:11, G T Smith wrote:
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.
ifstatus: eth0 device: nVidia Corporation MCP51 Ethernet Controller (rev a1) eth0 configuration: eth-id-00:15:f2:bf:d8:2c eth0 dhcpcd is still waiting for data eth0 is up 2: eth0:
mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:15:f2:bf:d8:2c brd ff:ff:ff:ff:ff:ff inet6 fe80::215:f2ff:febf:d82c/64 scope link valid_lft forever preferred_lft forever netstat is too big, but it did not have _anything_ under "Active Internet connections".
Netstat would be without switches. Should have been a bit more specific...... I should also have suggested ifconfig NOT ifstatus.... my mistake... <snip>
I tried deleting the content in: /etc/resolv.conf /etc/HOSTNAME /etc/sysconfig/network/routes
What we are more interested in is hardware configuration related files. These are usually found in /etc/sysconfig/[network|hardware] directories. These three should change on connection anyway.
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.
OK. I deleted the 2 entries in /etc/udev/rules.d/30-net_persistent_names.rules
But this cleaning did not solve the problem. Did I forget anything?
What was not clear in the original Post was that this was an on board chipset, these can require specially tailored versions of the drivers that are usually provided by the MOBO manufacturer. (I have also had problems with Windows and Linux in the past with generic drivers and onboard NICs). This rather sounds like it should have been a case of using NDISWRAPPER with the windows drivers, or checking whether the MOBO manufacturer or nvidia has more recent linux drivers. If you installed the MOBO drivers under windows (or they were pre-installed) they have may have made firmware changes which were incompatible with your current Linux drivers. BTW Initial NDISWRAPPER based configuration is usually best done outside of YaST. Then you can use YaST to setup the appropriate NDISWRAPPER based configuration.
Thanks for all the help, Carlos FL
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGZ8UEasN0sSnLmgIRAqKEAKC1ZYLXlmm3C2Z0aFRTS+/8veToHACgtSRC CW1sZ44HAzDG/hopGS/BmYo= =vH3Z -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org