What is happening in centos 5 with network config files???
I have a machine with 2 network cards.
ifcfg-eth1 keeps changing to DHCP. All my static setup is gone.
Why is it doing this? How can I stop it?
I run "netconfig -d eth1" and re-setup my static information. I reboot and now I am back to DHCP.
I have a gigabyte motherboard, nvidia chipset. forcedeth driver. eth0 is e1000.
Jerry
On 4/25/07, Jerry Geis geisj@pagestation.com wrote:
What is happening in centos 5 with network config files???
Who knows, but lets find out.
I have a machine with 2 network cards.
ifcfg-eth1 keeps changing to DHCP. All my static setup is gone.
Why is it doing this? How can I stop it?
I run "netconfig -d eth1" and re-setup my static information. I reboot and now I am back to DHCP.
I have a gigabyte motherboard, nvidia chipset. forcedeth driver. eth0 is e1000.
Jerry Geis wrote:
What is happening in centos 5 with network config files???
I have a machine with 2 network cards.
ifcfg-eth1 keeps changing to DHCP. All my static setup is gone.
Why is it doing this? How can I stop it?
I run "netconfig -d eth1" and re-setup my static information. I reboot and now I am back to DHCP.
I have a gigabyte motherboard, nvidia chipset. forcedeth driver. eth0 is e1000.
Do you have files under /etc/sysconfig/networking/profiles/default/?
Jerry Geis wrote: / What is happening in centos 5 with network config files???
/>>/ />>/ I have a machine with 2 network cards. />>/ />>/ ifcfg-eth1 keeps changing to DHCP. All my static setup is gone. />>/ />>/ Why is it doing this? How can I stop it? />>/ />>/ I run "netconfig -d eth1" and re-setup my static information. I reboot and />>/ now I am back to DHCP. />>/ />>/ I have a gigabyte motherboard, nvidia chipset. forcedeth driver. eth0 is />>/ e1000. /
Do you have files under /etc/sysconfig/networking/profiles/default/?
there are no files under this directory.
Jerry
On 4/25/07, Jerry Geis geisj@pagestation.com wrote:
ifcfg-eth1 keeps changing to DHCP. All my static setup is gone.
Why is it doing this? How can I stop it?
I had exactly this problem with CentOS 4 on a machine that has 2 onboard NICs plus a third NIC on a card. Now if I can just remember what I did ...
The problem (as I recall) is that on each reboot the onboard NICs are being discovered in a different order, so the MAC addresses in /etc/sysconfig/hwconf don't match what is recorded in /etc/sysconfig/network-scripts/ifcfg-eth*.
I believe what I had to do (I should have written it down, damn it) was hand-edit /etc/sysconfig/hwconf to completely remove all the references to the NICs (there may be more than one entry for each NIC because of the flip-flopping), edit ifcfg-eth* to remove all references to HWADDR, reboot again to let the cards be rediscovered, and then again hand-edit ifcfg-eth* to insert HWADDR lines that match the device assignments in the regenerated /etc/sysconfig/hwconf.
However, I may have at least the last step of that wrong.
Bart Schaefer wrote:
On 4/25/07, Jerry Geis geisj@pagestation.com wrote:
ifcfg-eth1 keeps changing to DHCP. All my static setup is gone.
Why is it doing this? How can I stop it?
I had exactly this problem with CentOS 4 on a machine that has 2 onboard NICs plus a third NIC on a card. Now if I can just remember what I did ...
The problem (as I recall) is that on each reboot the onboard NICs are being discovered in a different order, so the MAC addresses in /etc/sysconfig/hwconf don't match what is recorded in /etc/sysconfig/network-scripts/ifcfg-eth*.
I believe what I had to do (I should have written it down, damn it) was hand-edit /etc/sysconfig/hwconf to completely remove all the references to the NICs (there may be more than one entry for each NIC because of the flip-flopping), edit ifcfg-eth* to remove all references to HWADDR, reboot again to let the cards be rediscovered, and then again hand-edit ifcfg-eth* to insert HWADDR lines that match the device assignments in the regenerated /etc/sysconfig/hwconf.
However, I may have at least the last step of that wrong.
I would disable the onboard NIC(s), plug in a decent card and get on with my life.
Jerry Geis spake the following on 4/25/2007 4:53 AM:
What is happening in centos 5 with network config files???
I have a machine with 2 network cards.
ifcfg-eth1 keeps changing to DHCP. All my static setup is gone.
Why is it doing this? How can I stop it?
I run "netconfig -d eth1" and re-setup my static information. I reboot and now I am back to DHCP.
I have a gigabyte motherboard, nvidia chipset. forcedeth driver. eth0 is e1000.
Jerry
I have seen this problem with Asus MB's and the forcedeth driver. It was being blamed on Asus bios issues, but it might be a bug in the forcedeth driver. The suggestions I have seen involved putting a fixed MAC address into that interfaces config file.
i believe i had mentioned this already on this list:
have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos-
the fedora way goes:
1. move or delete /etc/sysconfig/hwconf 2. move or delete /etc/modprobe.conf 3. run kudzu afterwards => this writes new hwconf, modprobe.conf 4. bring your nic's down: ifdown ethx 5. remove the driver via modprobe -rv <your-nic-driver> (forcedepth) 5a. maybe to be sure: lsmod|grep -i <your-nic-driver> 6. reload the driver via modprobe -sv ... 7. fix your mac-addr-settings via system-config-network 8. compare your mac's in hwconf _and_ via ifconfig
steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), but your are able to exclude if this files were changed again after step 3. (ls -l /etc/sysconfig/hwconf => date/time !) a hint of another problem !
if there are still diff's, then it's another problem i don't know a solution for, yet, but i remember ethx order changes and therefore mac mismatches at late fedora 5/early fedora 6 kernels.
try and report ! okay ?
i believe i had mentioned this already on this list:
have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos-
the fedora way goes:
- move or delete /etc/sysconfig/hwconf
- move or delete /etc/modprobe.conf
- run kudzu afterwards => this writes new hwconf, modprobe.conf
- bring your nic's down: ifdown ethx
- remove the driver via modprobe -rv <your-nic-driver> (forcedepth)
5a. maybe to be sure: lsmod|grep -i <your-nic-driver> 6. reload the driver via modprobe -sv ... 7. fix your mac-addr-settings via system-config-network 8. compare your mac's in hwconf _and_ via ifconfig
steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), but your are able to exclude if this files were changed again after step 3. (ls -l /etc/sysconfig/hwconf => date/time !) a hint of another problem !
if there are still diff's, then it's another problem i don't know a solution for, yet, but i remember ethx order changes and therefore mac mismatches at late fedora 5/early fedora 6 kernels.
try and report ! okay ?
-- ronald
Ronald,
Thanks for the above. However, sadly it did not work. Also I see no way in the system-config-network to set a MAC address. I was in the character mode here not X.
This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. One was giving the invalid MAC address and one seemed OK. Both had the forcedeth driver loaded for onboard network.
I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same issue. One board is working and the other is giving the invalid MAC address. Both gigabytes have the forcedeth driver.
I tried loading centos 4 but it does not even recognize the forcedeth device at all. even manually loading.
I'm at a loss. I have a script file that runs and sets things up the way I want after boot up. Not pretty - but I guess it works.
Jerry
Jerry Geis spake the following on 4/26/2007 11:53 AM:
i believe i had mentioned this already on this list:
have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos-
the fedora way goes:
- move or delete /etc/sysconfig/hwconf
- move or delete /etc/modprobe.conf
- run kudzu afterwards => this writes new hwconf, modprobe.conf
- bring your nic's down: ifdown ethx
- remove the driver via modprobe -rv <your-nic-driver> (forcedepth)
5a. maybe to be sure: lsmod|grep -i <your-nic-driver> 6. reload the driver via modprobe -sv ... 7. fix your mac-addr-settings via system-config-network 8. compare your mac's in hwconf _and_ via ifconfig
steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), but your are able to exclude if this files were changed again after step 3. (ls -l /etc/sysconfig/hwconf => date/time !) a hint of another problem !
if there are still diff's, then it's another problem i don't know a solution for, yet, but i remember ethx order changes and therefore mac mismatches at late fedora 5/early fedora 6 kernels.
try and report ! okay ?
-- ronald
Ronald,
Thanks for the above. However, sadly it did not work. Also I see no way in the system-config-network to set a MAC address. I was in the character mode here not X.
This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. One was giving the invalid MAC address and one seemed OK. Both had the forcedeth driver loaded for onboard network.
I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same issue. One board is working and the other is giving the invalid MAC address. Both gigabytes have the forcedeth driver.
I tried loading centos 4 but it does not even recognize the forcedeth device at all. even manually loading.
I'm at a loss. I have a script file that runs and sets things up the way I want after boot up. Not pretty - but I guess it works.
Jerry
This appears to be a bug in the forcedeth driver and the chipset. The driver seems to pull the current MAC address from a register, and writes it back differently. The systems with the trouble must allow this write to take place, and it changes the MAC address for the next boot. I think if you add a HWADDR: xx:xx:xx:xx:xx:xx command to the ifcfg script, it might stick. You will have to find your real MAC address on your own, but it might be on a sticker somewhere on the board, or in a service tag on the equipment.
Scott Silva spake the following on 4/26/2007 12:04 PM:
Jerry Geis spake the following on 4/26/2007 11:53 AM:
i believe i had mentioned this already on this list: have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos- the fedora way goes:
- move or delete /etc/sysconfig/hwconf
- move or delete /etc/modprobe.conf
- run kudzu afterwards => this writes new hwconf, modprobe.conf
- bring your nic's down: ifdown ethx
- remove the driver via modprobe -rv <your-nic-driver> (forcedepth)
5a. maybe to be sure: lsmod|grep -i <your-nic-driver> 6. reload the driver via modprobe -sv ... 7. fix your mac-addr-settings via system-config-network 8. compare your mac's in hwconf _and_ via ifconfig steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), but your are able to exclude if this files were changed again after step 3. (ls -l /etc/sysconfig/hwconf => date/time !) a hint of another problem ! if there are still diff's, then it's another problem i don't know a solution for, yet, but i remember ethx order changes and therefore mac mismatches at late fedora 5/early fedora 6 kernels. try and report ! okay ? -- ronald
Ronald,
Thanks for the above. However, sadly it did not work. Also I see no way in the system-config-network to set a MAC address. I was in the character mode here not X.
This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. One was giving the invalid MAC address and one seemed OK. Both had the forcedeth driver loaded for onboard network.
I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same issue. One board is working and the other is giving the invalid MAC address. Both gigabytes have the forcedeth driver.
I tried loading centos 4 but it does not even recognize the forcedeth device at all. even manually loading.
I'm at a loss. I have a script file that runs and sets things up the way I want after boot up. Not pretty - but I guess it works.
Jerry
This appears to be a bug in the forcedeth driver and the chipset. The driver seems to pull the current MAC address from a register, and writes it back differently. The systems with the trouble must allow this write to take place, and it changes the MAC address for the next boot. I think if you add a HWADDR: xx:xx:xx:xx:xx:xx command to the ifcfg script, it might stick. You will have to find your real MAC address on your own, but it might be on a sticker somewhere on the board, or in a service tag on the equipment.
Ignore the HWADDR line. I am pretty sure that is the wrong command, but I can't find the right one anywhere.
You could try the NVidia network driver, or manually compile the forcedeth 0.60 driver, which is reported to fix this. Maybe upstream will add this driver to their kernels so it can flow back to CentOS.
Scott Silva spake the following on 4/26/2007 12:25 PM:
Scott Silva spake the following on 4/26/2007 12:04 PM:
Jerry Geis spake the following on 4/26/2007 11:53 AM:
i believe i had mentioned this already on this list: have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos- the fedora way goes:
- move or delete /etc/sysconfig/hwconf
- move or delete /etc/modprobe.conf
- run kudzu afterwards => this writes new hwconf, modprobe.conf
- bring your nic's down: ifdown ethx
- remove the driver via modprobe -rv <your-nic-driver> (forcedepth)
5a. maybe to be sure: lsmod|grep -i <your-nic-driver> 6. reload the driver via modprobe -sv ... 7. fix your mac-addr-settings via system-config-network 8. compare your mac's in hwconf _and_ via ifconfig steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), but your are able to exclude if this files were changed again after step 3. (ls -l /etc/sysconfig/hwconf => date/time !) a hint of another problem ! if there are still diff's, then it's another problem i don't know a solution for, yet, but i remember ethx order changes and therefore mac mismatches at late fedora 5/early fedora 6 kernels. try and report ! okay ? -- ronald
Ronald,
Thanks for the above. However, sadly it did not work. Also I see no way in the system-config-network to set a MAC address. I was in the character mode here not X.
This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. One was giving the invalid MAC address and one seemed OK. Both had the forcedeth driver loaded for onboard network.
I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same issue. One board is working and the other is giving the invalid MAC address. Both gigabytes have the forcedeth driver.
I tried loading centos 4 but it does not even recognize the forcedeth device at all. even manually loading.
I'm at a loss. I have a script file that runs and sets things up the way I want after boot up. Not pretty - but I guess it works.
Jerry
This appears to be a bug in the forcedeth driver and the chipset. The driver seems to pull the current MAC address from a register, and writes it back differently. The systems with the trouble must allow this write to take place, and it changes the MAC address for the next boot. I think if you add a HWADDR: xx:xx:xx:xx:xx:xx command to the ifcfg script, it might stick. You will have to find your real MAC address on your own, but it might be on a sticker somewhere on the board, or in a service tag on the equipment.
Ignore the HWADDR line. I am pretty sure that is the wrong command, but I can't find the right one anywhere.
You could try the NVidia network driver, or manually compile the forcedeth 0.60 driver, which is reported to fix this. Maybe upstream will add this driver to their kernels so it can flow back to CentOS.
I found the command just as I hit send. Try MACADDR=<MAC-address> in the if-cfg file. Look at this page for more details. http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide...
Scott Silva spake the following on 4/26/2007 12:25 PM:
/ Scott Silva spake the following on 4/26/2007 12:04 PM:
/>>>/ Jerry Geis spake the following on 4/26/2007 11:53 AM: />>>>>/ i believe i had mentioned this already on this list: />>>>>/ have had same problems with my asus m2npv-vm board (onboard />>>>>/ forcedepth nic) the first days with the board under fedora 6 - would />>>>>/ say no big diff's to centos- />>>>>/ the fedora way goes: />>>>>/ 1. move or delete /etc/sysconfig/hwconf />>>>>/ 2. move or delete /etc/modprobe.conf />>>>>/ 3. run kudzu afterwards => this writes new hwconf, modprobe.conf />>>>>/ 4. bring your nic's down: ifdown ethx />>>>>/ 5. remove the driver via modprobe -rv <your-nic-driver> (forcedepth) />>>>>/ 5a. maybe to be sure: lsmod|grep -i <your-nic-driver> />>>>>/ 6. reload the driver via modprobe -sv ... />>>>>/ 7. fix your mac-addr-settings via system-config-network />>>>>/ 8. compare your mac's in hwconf _and_ via ifconfig />>>>>/ steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), />>>>>/ but your are able to exclude if this files were changed again after />>>>>/ step 3. (ls -l /etc/sysconfig/hwconf => date/time !) />>>>>/ a hint of another problem ! />>>>>/ if there are still diff's, then it's another problem i don't know a />>>>>/ solution for, yet, but i remember ethx order changes and therefore mac />>>>>/ mismatches at late fedora 5/early fedora 6 kernels. />>>>>/ try and report ! />>>>>/ okay ? />>>>>/ -- />>>>>/ ronald />>>>/ Ronald, />>>>/ />>>>/ Thanks for the above. However, sadly it did not work. />>>>/ Also I see no way in the system-config-network to set a MAC address. />>>>/ I was in the character mode here not X. />>>>/ />>>>/ This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. />>>>/ One was giving the invalid MAC address and one seemed OK. />>>>/ Both had the forcedeth driver loaded for onboard network. />>>>/ />>>>/ I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same />>>>/ issue. One board is working and the other is giving the invalid MAC />>>>/ address. />>>>/ Both gigabytes have the forcedeth driver. />>>>/ />>>>/ I tried loading centos 4 but it does not even recognize the forcedeth />>>>/ device at all. />>>>/ even manually loading. />>>>/ />>>>/ I'm at a loss. I have a script file that runs and sets things up the way />>>>/ I want after boot up. Not pretty - but I guess it works. />>>>/ />>>>/ Jerry />>>/ This appears to be a bug in the forcedeth driver and the chipset. The driver />>>/ seems to pull the current MAC address from a register, and writes it back />>>/ differently. The systems with the trouble must allow this write to take place, />>>/ and it changes the MAC address for the next boot. />>>/ I think if you add a HWADDR: xx:xx:xx:xx:xx:xx command to the ifcfg script, />>>/ it might stick. You will have to find your real MAC address on your own, but />>>/ it might be on a sticker somewhere on the board, or in a service tag on the />>>/ equipment. />>>/ />>/ Ignore the HWADDR line. I am pretty sure that is the wrong command, but I />>/ can't find the right one anywhere. />>/ />>/ You could try the NVidia network driver, or manually compile the forcedeth />>/ 0.60 driver, which is reported to fix this. Maybe upstream will add this />>/ driver to their kernels so it can flow back to CentOS. />>/ />I found the command just as I hit send.
Try MACADDR=<MAC-address> in the if-cfg file. Look at this page for more details. http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide...
Scott,
THanks - I tried this just now and it did not work... The new kernel is working but iptables is not compiled in???
Jerry
Jerry Geis spake the following on 4/26/2007 1:23 PM:
Scott Silva spake the following on 4/26/2007 12:25 PM:
/ Scott Silva spake the following on 4/26/2007 12:04 PM:
/>>>/ Jerry Geis spake the following on 4/26/2007 11:53 AM: />>>>>/ i believe i had mentioned this already on this list: />>>>>/ have had same problems with my asus m2npv-vm board (onboard />>>>>/ forcedepth nic) the first days with the board under fedora 6 - would />>>>>/ say no big diff's to centos- />>>>>/ the fedora way goes: />>>>>/ 1. move or delete /etc/sysconfig/hwconf />>>>>/ 2. move or delete /etc/modprobe.conf />>>>>/ 3. run kudzu afterwards => this writes new hwconf, modprobe.conf />>>>>/ 4. bring your nic's down: ifdown ethx />>>>>/ 5. remove the driver via modprobe -rv <your-nic-driver> (forcedepth) />>>>>/ 5a. maybe to be sure: lsmod|grep -i <your-nic-driver> />>>>>/ 6. reload the driver via modprobe -sv ... />>>>>/ 7. fix your mac-addr-settings via system-config-network />>>>>/ 8. compare your mac's in hwconf _and_ via ifconfig />>>>>/ steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), />>>>>/ but your are able to exclude if this files were changed again after />>>>>/ step 3. (ls -l /etc/sysconfig/hwconf => date/time !) />>>>>/ a hint of another problem ! />>>>>/ if there are still diff's, then it's another problem i don't know a />>>>>/ solution for, yet, but i remember ethx order changes and therefore mac />>>>>/ mismatches at late fedora 5/early fedora 6 kernels. />>>>>/ try and report ! />>>>>/ okay ? />>>>>/ -- />>>>>/ ronald />>>>/ Ronald, />>>>/ />>>>/ Thanks for the above. However, sadly it did not work. />>>>/ Also I see no way in the system-config-network to set a MAC address. />>>>/ I was in the character mode here not X. />>>>/ />>>>/ This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. />>>>/ One was giving the invalid MAC address and one seemed OK. />>>>/ Both had the forcedeth driver loaded for onboard network. />>>>/ />>>>/ I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same />>>>/ issue. One board is working and the other is giving the invalid MAC />>>>/ address. />>>>/ Both gigabytes have the forcedeth driver. />>>>/ />>>>/ I tried loading centos 4 but it does not even recognize the forcedeth />>>>/ device at all. />>>>/ even manually loading. />>>>/ />>>>/ I'm at a loss. I have a script file that runs and sets things up the way />>>>/ I want after boot up. Not pretty - but I guess it works. />>>>/ />>>>/ Jerry />>>/ This appears to be a bug in the forcedeth driver and the chipset. The driver />>>/ seems to pull the current MAC address from a register, and writes it back />>>/ differently. The systems with the trouble must allow this write to take place, />>>/ and it changes the MAC address for the next boot. />>>/ I think if you add a HWADDR: xx:xx:xx:xx:xx:xx command to the ifcfg script, />>>/ it might stick. You will have to find your real MAC address on your own, but />>>/ it might be on a sticker somewhere on the board, or in a service tag on the />>>/ equipment. />>>/ />>/ Ignore the HWADDR line. I am pretty sure that is the wrong command, but I />>/ can't find the right one anywhere. />>/ />>/ You could try the NVidia network driver, or manually compile the forcedeth />>/ 0.60 driver, which is reported to fix this. Maybe upstream will add this />>/ driver to their kernels so it can flow back to CentOS. />>/ />I found the command just as I hit send.
Try MACADDR=<MAC-address> in the if-cfg file. Look at this page for more details. http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide...
Scott,
THanks - I tried this just now and it did not work... The new kernel is working but iptables is not compiled in???
Jerry
This was in response to using the original kernel. Using the newest kernel source will leave you out in the cold as far as support is concerned. It might just be more prudent to add another card and wait to see if redhat updates the forcedeth code in the next kernel.
You could look at the kernel source rpm to see what patches are added by redhat. That might give you some clue on what is missing.
On Thu, Apr 26, 2007 at 12:04:46PM -0700, Scott Silva said:
Jerry Geis spake the following on 4/26/2007 11:53 AM:
have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos-
I tried loading centos 4 but it does not even recognize the forcedeth device at all. even manually loading.
I'm at a loss. I have a script file that runs and sets things up the way I want after boot up. Not pretty - but I guess it works.
Jerry
This appears to be a bug in the forcedeth driver and the chipset. The driver seems to pull the current MAC address from a register, and writes it back differently. The systems with the trouble must allow this write to take place, and it changes the MAC address for the next boot. I think if you add a HWADDR: xx:xx:xx:xx:xx:xx command to the ifcfg script, it might stick. You will have to find your real MAC address on your own, but it might be on a sticker somewhere on the board, or in a service tag on the equipment.
I would go farther and suggest just installing a real Intel ethernet card and be done with it if at all possible.
I also have an asus board with the nvidia / realtek / forthdeth driver chip and have had nothing but problems no matter what distro I run.
It's not worth messing with a device that the manufacturer supports so poorly. I'm going to make sure that any motherboard I buy in the future does NOT have that crappy ethernet chipset in it.
Walt Reed wrote:
I would go farther and suggest just installing a real Intel ethernet card and be done with it if at all possible.
I also have an asus board with the nvidia / realtek / forthdeth driver chip and have had nothing but problems no matter what distro I run.
It's not worth messing with a device that the manufacturer supports so poorly. I'm going to make sure that any motherboard I buy in the future does NOT have that crappy ethernet chipset in it.
Here is a link to a company that makes Linux systems. You can use their systems as a reference to build your GNU/Linux-compatible systems.
Got it from another mailing list. I am going to use it this way, myself in the future. :-)
Jerry Geis wrote:
i believe i had mentioned this already on this list:
have had same problems with my asus m2npv-vm board (onboard forcedepth nic) the first days with the board under fedora 6 - would say no big diff's to centos-
the fedora way goes:
- move or delete /etc/sysconfig/hwconf
- move or delete /etc/modprobe.conf
- run kudzu afterwards => this writes new hwconf, modprobe.conf
- bring your nic's down: ifdown ethx
- remove the driver via modprobe -rv <your-nic-driver> (forcedepth)
5a. maybe to be sure: lsmod|grep -i <your-nic-driver> 6. reload the driver via modprobe -sv ... 7. fix your mac-addr-settings via system-config-network 8. compare your mac's in hwconf _and_ via ifconfig
steps 4-6 are also performed via reboot (grrrrrrrrrr: m$ world tasks), but your are able to exclude if this files were changed again after step 3. (ls -l /etc/sysconfig/hwconf => date/time !) a hint of another problem !
if there are still diff's, then it's another problem i don't know a solution for, yet, but i remember ethx order changes and therefore mac mismatches at late fedora 5/early fedora 6 kernels.
try and report ! okay ?
-- ronald
Ronald,
Thanks for the above. However, sadly it did not work. Also I see no way in the system-config-network to set a MAC address. I was in the character mode here not X.
vi /etc/sysconfig/networking/devices/ifcfg-ethx HWADDR=.... same as ifconfig reports ?
this files are hardlinked and i currently don't know what could break if you write them - had it down often, without trouble -
This is SOOO bizzar. Again, when I started I had 2 Asus M2N-MX boards. One was giving the invalid MAC address and one seemed OK. Both had the forcedeth driver loaded for onboard network.
I bought 2 gigabyte motherboards (DIFFERENT BIOS) and I have the same issue. One board is working and the other is giving the invalid MAC address. Both gigabytes have the forcedeth driver.
I tried loading centos 4 but it does not even recognize the forcedeth device at all. even manually loading.
I'm at a loss. I have a script file that runs and sets things up the way I want after boot up. Not pretty - but I guess it works.
Jerry
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Bart Schaefer -
Ioannis Vranos -
Jerry Geis -
Jim Perrin -
Les Mikesell -
Robert -
Robert Moskowitz -
Ronald Warsow -
Scott Silva -
Walt Reed