hutyerah, Good get , how did you know I am not in Melbourne Florida ?
"You mean NB5, not NB%" (still had the shift key down I guess)
It's the old see what you think you see with IPv6 routers. Routers didn't register and I thought it was refering to IP tables V6. Even on Linux I like to run a firewall (Arno's).
I like the idea of a hardware problem - gives me an excuse to buy a new box.
Certainly haven't need to go looking for it before.
Well I will now go and try disconnecting the Ethernet cable and let you know what happens.
Cheers
Col

Hi,

If you had the usb connection from the router/modem and the eth device for the router/modem to the same machine then of course that's part of the problem.

When you disconnect the usb from the router/modem, do you still see the MAC of the on board NIC changing?

As stated before the IPV6 error is not relevant at this point. Your not using IPV6 at this time are you?

I don't like intermittent hardware issues! They are like dominoes that tumble, one to another.

What happened was:
I think I have found my problem with Firefox. It appears that dhcpcd creates a new /etc/resolv.conf and puts in it "nameserver 192.168.1.1" whereas as far as I can tell Firefox needs the actual address of my isp "203.88.87.1" in resov.conf.
I booted with just the USB cable connected and ping & Konquerer worked Firefox didn't.
I booted with just the Ethernet cable and had no eth0.
I disconnected the Ethernet cable, replaced the USB cable and rebooted Slk 12. lsconfig says I have eth0,eth1 & still an increasing number. ping worked.
I booted into Slk 11 to talk to you and guess what? No internet connection.
I turned it off, re-connected the Ethernet so now I have both cables connected and after another reboot I can send this message.

Zen and the art of computer maintainence.

seems like I have to run as static ip because
line by line I removed the comment from /etc/rc.d/rc.inet1.conf until it looked like this
before I rebooted I set /etc/resolve.conf to this
after rebooting every time /etc/resove.conf was changed to this

Hi,

The DNS nameserver is reset by the DHCP server presenting that to your system when you request a IP.

If you indeed want to use a static IP then you will need to setup the device information in the '/etc/rc.d/rc.inet1.conf' file. You will need to answer no to the
'USE_DHCP[0]="no"' for said device.

Be sure to set your Gateway.

This line from /etc/rc.d/rc.inet1.conf
specifically says my /etc/resolv.conf should not change
so why does it?

Hi,

That is for device [4]. I thought you were using device [0].

"There is none so blind as he who will not see"
dhcpcd is working thanks


To add to life's rich tapestry I managed to cut the tip of my index finger which has made my hunt and peck typing even slower.
I am down to one cable, the Ethernet one. I even went as far as booting the xp partition (shudder) and it says I have Nvidia NVENET.sys, I remember installing Ethernet into the modem but don't remember doing USB, I am doing this with only the Ethernat cable connected to the modem so I'm betting the modem is set for Ethernet.
But I can't guarantee it hasn't also had USB installed.

I re-installed Slk 12, with static ip because I know Firefox will work without me forgetting to edit a file.
The first boot after install Firefox works.
The next boot eth0 is gone.
So I fiddle around a bit and found that if I delete the network rules file before rebooting I am ok.
If I set eth0 to 00:30:0a:44:7a:14 in the rules file I can only access the net with the USB cable re-connected.
In fact I had to put the USB cable in to get the rules file to include that address.

Seems I'm looking at dodgy hardware.
Can I get you any more info?

Cheers
Col

That's because that interface is the USB interface- it will only appear when you have the USB plugged in. If you're using one of the ethernet interfaces, then you need to set up the network with the hardware address "00:11:2F:82:19:30" which is your offboard ethernet card. That is, map eth0 to that in the network rules, then set DHCP on that in rc.inet1.conf etc etc.

If you have an ASUS motherboard, try googling "linux IOAPIC ASUS" because I have been through three motherboards with AM2 sockets (AMD dual core), nforce2 chipsets or AMD chipsets. None will successfully handle the APIC and so are confused on interrupts and i/o. Apparently this results in ethernet cards just not working. The problem is discussed in some forums. I have reverted to my old via motherboard so I don't have the details at hand. Do not flash your BIOS.

I've tried lots of different combinations and all I can say is if I delete /etc/udev/rules.d/75-network-devices.rules before rebooting I can access the internet after rebooting.Nothing else I tried made any difference.

Hi,

I hate when I get to threads describing a problem I have, with no final conclusion.

I therefore want to confirm to nyloc and anyone else interested, that there seems to be a bug with the driver and/or nVidia Ethernet controller.

I'm on a Fedora Core 7 and have had the very same experience, that the onboard NIC worked at first boot, maybe on the first few reboots - not sure if I didn't reboot more than once after upgrading to FC7, and then it ceases to run.

I have tracked the problem as far down as to being my system not accepting the offered IP from DHCP. My DHCP server offers me an IP the dhcpclient doesn't want to install for some reason (the strange changing MACs?).

If I setup the system with a static IP it runs like a charm.

This is a new problem I have got on a system that ran and rebooted frequently for many months on FC4. Maybe it's a problem with FC7, maybe with the kernel (I'm on 2.6.22.1-33.fc7).

So to put a conclusion in my contribution: If the onboard nVidia Ethernet Controller works at first boot, but not at the next boot, and you use DHCP, change to a static IP unless you have time to fix the problem in the driver, which I for one will appreciate if you do :-).

I have updated the kernel on my FC7 to the current release (2.6.22.1-41.fc7) and afterwards rebooted multiple times with DHCP enabled, without any problem.

Either it's luck and Murphy will hit me some day, or a bug has actually been fixed.