Can only connect to internet if 1st boot into XP then restart & boot into Suse 10.1
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Can only connect to internet if 1st boot into XP then restart & boot into Suse 10.1
I have PC configured with for dual boot with XP and SuSe 10.1 and connected to Linksys WRT54G v1 set up as Gateway to cable modem.
Network card is: 3Com 3C920B-EMB-WNM Integrated Fast Ethernet Controller
Network Driver: 3c59x
Cable modem is 100Mb/s but cable connection to back of the house is poor and in XP I manually adjusted this to 10Mb/s to ensure an internet connection.
If I boot directly into SuSe 10.1 then I get the following outputs:
linux-bf2c:/home/cepmw1 # /etc/init.d/network restart
Shutting down the NetworkManagerDispatcher done
Shutting down the NetworkManager done
Shutting down the DHCP DBUS Daemon done
Starting the DHCP DBUS Daemon done
Starting the NetworkManager done
Starting the NetworkManagerDispatcher done
linux-bf2c:/home/cepmw1 # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
linux-bf2c:/home/cepmw1 # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
Anyone out there can tell me what XP is doing that SuSe 101.1 is not doing when negotiating with the router and how I can fix this to NOT have to boot into XP?
btw - I am using DD-WRT v23 SP1 firmware on router, but this issue was seen with Linksys firmware
The problem seems to be with DHCP. I would wonder about something querky or defective in either the card or router or the ethernet cable (cable's the most likely suspect).
Anyway, you could try manually assigning the network configuration:
Judging by what you've posted, it seems your cable is no good. Try running a large series of ping packets, and see what the success rate is.
Windows:
ping -n 200 192.168.1.1
Linux:
ping -c 200 192.168.1.1
Yes, the cable seems to be the problem. When booting direct into Linux, the system is defaulting to 100 Mb/s which is too fast to negotiate with the router. When booting first into XP, I've manually set it to 10 Mb/s and it gets IP assigned fine by router. Restarting and booting into Linux (rather than shut down and new boot) presumably maintains the connection with the router and the speed at 10 Mb/s.
Booting staright into Linux and manually typing:
>ethtool -s eth0 speed 10 duplex full autoneg off
followed by:
>/etc/init.d/network restart
solves my networking problems
but updating YaST / System / etc/sysconfig Editor / Hardware / Network / DEVICE NAME / ETHTOOL_OPTIONS
with
ethtool -s eth0 speed 10 duplex full autoneg off
or
speed 10 duplex full autoneg off
does not work - system defaults to 100 Mb/s on straight boot into Linux
I had thought of that, but my problem lies with threading the cable through some narrow, blind holes in the walls of the flat to reach my office which is at the back. It took me an age just to succesfully thread the cable thro' last time I did it, and another age to succesfully fit the connector....
Ahhh... so you put the plastic end on yourself. Did you do it with a proper crimping tool? Properly capping the wire is something of an art, and it's very easy to screw it up. Do you think that the problem might just be in the way you attached the connector? Perhaps not all eight of the wires are making contact---this would explain why your line wants to run at 10mbps: the old 4 or 5-wire cables were only designed to run at 10mbps. That seems to me to be a pretty likely suspect. If you have a crimping tool, you could just try putting on a new connector. That would be the best solution---unless you think the wire itself is only rated to 10mbps... but wires of that guage are very old and quite uncommon except in recycling/refurbishing computer shops.
Does the cable have eight multi-coloured wires? If so, it ought to be able to handle 100 or even 1000 mbps, and the connector is the likely culprit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
