(Ted Harding) wrote:
On 19-Aug-07 18:17:50, CDW (Linux) wrote:
(Ted Harding) wrote:
There's a lot of possibilities for this!
One thing to look at is whether you have a default gateway set up in Linux. If (as root) you enter the command
route
you should see somthing like
Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
where the "192.168.1.1" should be replaced by the IP address of your actual router. If you don't get a "default" line in the output from "route" then nothing for outside will get to the router.
I get the following :- Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 10 0 0 eth0 169.254.0.0 * 255.255.0.0 U 10 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.1.51 0.0.0.0 UG 10 0 0 eth0
Ah. I've just noticed that there's a 169.254.0.0 address in my list. That would appear to come from a DHCP config but I purposely didn't set that so would that be stopping it working? If so, how do I remove it?
I don't think it matters. I get the same too (on a Red Hat 9 system) without any DHCP going on. It's supposed, I think, to represent some alternative network numbering, and as far as I know is simply a dummy.
Thanks for that info.
My machine deleted the original of this mail so apologies if this screws up the threading.
Wayne Stallwood wrote :- On Sun, 2007-08-19 at 18:02 +0100, CDW (Linux) wrote:
I watched the light on the back of the LAN card and as XP was rebooting, the green LED illuminated. At no time does it do so in Linux.
The link light (if it is a link light but if there is only 1 this is usually the case) operates at the very lowest level, in fact in many cases it will work without an OS being loaded. Until you get that to come on in linux there isn't much point playing with the IP configuration.
Out of interest at the router end do you get a link light for the port the machine is plugged into ?
Nope. I swapped the cables from another machine and the fault went with the cable.
I'd suggest that as rare as it is nowadays, you have a network card that has dubious support in Linux or there is some miss-configuration at the interface level.
Do you know what card (or chipset) it is.
I can find that from Windows which is where I am now and it's reported as Realtek RTL8139/810x Family Fast Ethernet NIC. But I also did it from Linux as requested in case it was being mis-described there. It doesn't appear to be as it's shown as :- 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
You may as well get this from Linux with the lspci command Then while you are there run the following and have a look at the output
sudo mii-tool
The output from that is :- eth0: negotiated 100baseTx-FD, link ok SIOCGMIIPHY on 'eth1' failed: Operation not supported
It's possible that the linux driver has miss-negotiated the link speed (everything defaults to auto nowadays, but with certain combinations of cards, cables and hubs/switches/routers you can get a problem)
You could also try forcing the interface down to the lowest level.
sudo mii-tool --force=10baseT-HD
Tried that :- [root@Linux chris]# mii-tool --force=10baseT-HD SIOCGMIIPHY on 'eth1' failed: Operation not supported
Hmm. That appears to be trying to configure the firewire card which is eth1.
and to save another boot grep dmesg for things like "thernet" "link" etc and see if there are any relevant error messages.
dmesg | grep "thernet"
(most likely it is Ethernet and not ethernet but by leaving off the E we capture both)
[root@Linux chris]# dmesg | grep "thernet" 8139too Fast Ethernet driver 0.9.27 eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
I do have a firewire card in the machine for video editing but it's been in there for several months and it's only recently that Mandrake started failing to connect so I ruled that out as a cause. I'd be happy to be proved wrong though if it meant that this thing worked ;-)
CDW (Linux) wrote:
Way back in August of last year, I reported my connection problem.
Wayne Stallwood wrote :-
Do you know what card (or chipset) it is.
I can find that from Windows which is where I am now and it's reported as Realtek RTL8139/810x Family Fast Ethernet NIC. But I also did it from Linux as requested in case it was being mis-described there. It doesn't appear to be as it's shown as :- 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
I did some google searches and found lots of people reporting the same thing. Quite a few of them and I had one thing in common, the chipset. So I binned the card, bought a D-Link gigabit card and so far touch wood, it's started first time every time.
Hi,
On 13/02/2008, CDW (Linux) cdw_alug@the-walker-household.co.uk wrote:
CDW (Linux) wrote:
Way back in August of last year, I reported my connection problem.
Wayne Stallwood wrote :-
Do you know what card (or chipset) it is.
I can find that from Windows which is where I am now and it's reported as Realtek RTL8139/810x Family Fast Ethernet NIC. But I also did it from Linux as requested in case it was being mis-described there. It doesn't appear to be as it's shown as :- 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
I did some google searches and found lots of people reporting the same thing. Quite a few of them and I had one thing in common, the chipset. So I binned the card, bought a D-Link gigabit card and so far touch wood, it's started first time every time.
The Realtek 8139 is one of the best cards i've used, and is very well supported. I can't believe that you would have problems due to the chipset. Could've been a damaged card (you said "it's only recently that Mandrake started failing to connect"). Shame you had to throw such a cool card in the bin, though.
-Srdj
On Wed, Feb 13, 2008 at 11:16:26AM +0000, Srdjan Todorovic wrote:
Hi,
On 13/02/2008, CDW (Linux) cdw_alug@the-walker-household.co.uk wrote:
CDW (Linux) wrote:
Way back in August of last year, I reported my connection problem.
Wayne Stallwood wrote :-
Do you know what card (or chipset) it is.
I can find that from Windows which is where I am now and it's reported as Realtek RTL8139/810x Family Fast Ethernet NIC. But I also did it from Linux as requested in case it was being mis-described there. It doesn't appear to be as it's shown as :- 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
I did some google searches and found lots of people reporting the same thing. Quite a few of them and I had one thing in common, the chipset. So I binned the card, bought a D-Link gigabit card and so far touch wood, it's started first time every time.
The Realtek 8139 is one of the best cards i've used, and is very well supported. I can't believe that you would have problems due to the chipset. Could've been a damaged card (you said "it's only recently that Mandrake started failing to connect"). Shame you had to throw such a cool card in the bin, though.
Yes, I've used 8139 based cards for quite a while with no issues at all, in fact I think my current Linux box has an 8139 card in it.
There were issues with the early drivers if I remember correctly (quickly looks at his notes on installation....) .... ah, no, that was the Realtek 8168 on-board chipset. It must have been an older system that had the 8139.
On Wed, Feb 13, 2008 at 11:16:26AM +0000, Srdjan Todorovic wrote:
The Realtek 8139 is one of the best cards i've used, and is very well supported. I can't believe that you would have problems due to the chipset.
!
Possibly the worst ethernet cards *ever* lots of different revisions of the chipsets, driver problems working around hardware bugs and most of them are built at such a price that they can cause real headaches. Most machines I've had with these cards have had them replaced with Intel etherexpress pro (i /think/ i got the name right).
Adam
-
Adam Bower -
CDW (Linux) -
Chris G -
Srdjan Todorovic