New network config won't stick

[Pierre]

Made a previous post on this subject but it got screwd up and its not there any more so I make another try.

 

 

Had a perfectly working system with Mdk 9.1/KDE now moved to new to new MB

and not so perfect any more.

 

During first startup on the new MB all new hardware is found and system starts OK,

but no modem (LT Winmodem) and no network.

 

Manually reconfigure modem and network and get them to work. Restart, but back to square one, no modem and no network.

 

Why is the new settings not saved? How can I get it to stick?

 

Managed to get one reply on the old posting before it disappeared suggesting I do an upgrade with the original CD's. Have done that but no change.

 

The new network card (ReakTek8139) is found but shows up with the old driver (VIARhine) ! How can the system from the old network files? Mabe this will install the correct drver?

[roland]

May be You've already checked that but I don't know your Linux knowledge:

- have you checked /etc/modules .conf ? how doe it looks like ?

- what does /val/log/messages says about your network and modem driveres ?

 

roland

[pmpatrick]

You can do it by hand if you need to; it's pretty simple, just edit two files. The first is /ect/modules.conf. Add this line to the file:

 

alias eth0 8139too

 

That will load your driver on boot and create the eth0 interface. If there is another line with the incorrrect VIArhine driver, remove it or comment it out by putting a "#" in front of the line. Don't know why your driver is being misidentified. Does your new motherboard have an onboard nic?

 

The second file you'll probably have to create if you haven't got one there already. It should be placed in /etc/sysconfig/network-scripts and should be named "ifcfg-eth0". It's just a text configuration file and should look like:

 

DEVICE=eth0
BOOTPROTO=dhcp
NETMASK=255.255.255.0
ONBOOT=yes

 

This is the config file for eth0; the above assumes your using dhcp and you want eth0 to load on boot.

 

If these files already look like this then something else is going on preventing eth0 from loading. Post back if that's the case.

Edited November 3, 2003 by pmpatrick

[Pierre]

Edited my module.conf to

 

alias eth0 8139too from the incorrect

 

alias eth0 via-rhine

 

and now everything works fine again.

 

Thanks pmpatrick!