motherboard change

hillick01 · n00b Joined: 27 Mar 2007 Posts: 3

Hi All,

My old motherboard recently died and i had to replace which obviously led to some problems. i need to point out that im not a linux genius and am still learning.

my problem is this, when booting, i get the following errors

MySQL-500 not started (0)
ERROR: Cannot start sshd as net.eth0 could not start
ERROR: Cannot start apache2 as net.eth0 could not start
ERROR: Cannot start pure-ftpd as net.eth0 could not start
Starting vixie-cron...
/etc/init.d/net/Io: line34:/lib/rcscripts/net.modules.d/helpers.d/functions: no such file or directory
Starting
IPROUTE2 is not a valid module (missing provides)
ERROR: Cannot start netmount as net.eth0 could not start

i cannot afford to lose any data on this system hence i am nervous about doing anything...
Can someone tell me how to fix this safely? what commands do i run?

IQgryn · l33t Joined: 05 Sep 2005 Posts: 764 Location: WI, USA

It looks like you're missing a network driver for your new motherboard. How did you set up your kernel (manually or through genkernel)? Also, what is the new motherboard?

CrazyIvanMN · n00b Joined: 20 Feb 2007 Posts: 45

I had the same problem when I changed my mainboard.

the problem.. well it's not a problem it's a feature of Udev.

I'm sorta a n00b so someone correct me if I'm wrong.. Anyway

Udev when it first sees a kernel message or something with the name eth0 it goes and creates your first ethernet device as eth0, and identifies it with the mac address of that ethernet adaptor, so that it will always identify that ethernet adaptor as eth0..

Now, when it sees the new ethernet adpator on the new mainboard the kernel still calls it eth0 (since it's the first one) but udev sees it's not the same mac address, so renames it eth1.. and since eth0 doesn't exist anymore (since it's identified by mac address) it never sets that one up..

So two solutions, one is relink your net.eth0 to net.eth1 which is probably the 'wrong' solution since it'll never see eth0 ever again since you trashed that board..

The proper solution is to go into /etc/udev/rules.d/70-persistent-net.rules
And you'll see two rows that look something like this:

hillick01 · n00b Joined: 27 Mar 2007 Posts: 3

motherboard is gigabyte ga-81865gme

IQgryn · l33t Joined: 05 Sep 2005 Posts: 764 Location: WI, USA

Ok, crazyivan's probably right about the udev stuff--I keep forgetting about the persistent rules. It looks like your motherboard has a Via Rhine onboard NIC, so if you enable the following in your kernel, you should be covered there:

Gentoo613 · n00b Joined: 01 Jun 2006 Posts: 38 Location: NJ/NYC

Recently, I migrated to some new hardware, I required different SATA drivers (to be compiled in the kernel). It was easy enough to fix as I booted the new server using the Gentoo LiveCD and then ran lsmod. It will let you know which drivers you require.

hillick01 · n00b Joined: 27 Mar 2007 Posts: 3

IQgryn · l33t Joined: 05 Sep 2005 Posts: 764 Location: WI, USA

If you used genkernel, then you shouldn't need to change anything--it automatically compiles everything as a module anyway. If you don't remember configuring the kernel, then this is probably what you used.

If you built the kernel yourself, you need to use the same process as before. Your current config file will automatically be opened when you run

cruise · n00b Joined: 01 Dec 2003 Posts: 48

gsoe · Posted: Sat Jun 16, 2007 4:36 am Post subject:

Notice the