New motherboard

danielblanche54
Posts: 15
Joined: Wed Jun 06, 2012 9:57 pm

New motherboard

Postby danielblanche54 » Wed Jun 06, 2012 10:03 pm

Hey,
So I moved my installation to a new motherboard but ifconfig doesn't list any of my network interfaces (internal ethernet, and I tried 3 different pci network cards) all with no prevail. I don't want to make a new installation as I have a comfortable setup. I just want to get it back on the network again. Ps the installation is headless (cli only)

If someone could help me get the server back online I would greatly appreciate it :)
Thank you

User avatar
sgtfoo
Posts: 419
Joined: Sun Jul 18, 2010 8:27 pm

Re: New motherboard

Postby sgtfoo » Thu Jun 07, 2012 5:46 am

If your installation is headless, but you currently have no working NIC on the server, then there's no way to troubleshoot it. You will need to connect a keyboard/mouse/monitor for a little while to fix things.

The likely issue, is that the new motherboard's NIC is likely addressed as eth1 instead of eth0, which is the default interface Amahi uses.

There's a way to change it, but it's a bit involved. Google it .. sure it can't be too far away.

in the meantime, check to see that Linux can at least see your NIC with a

Code: Select all

sudo lspci
(hoping it's part of the pci decice tree)
SgtFoo
HDA: VM inside oVirt FX-8300 95w (2 cores for HDA), 32GB RAM (2GB for HDA)
My PC: FX-8300, 16GB RAM, 3x 1TB HDDs, Radeon HD6970 2GB video; Win10 Pro x64
Other: PC, Asus 1215n (LXLE), Debian openZFS server (3x(2x2tb) mirrors)
Modem&Network: Thomson DCM475; Asus RT-AC66U; HP 1800-24G switch

danielblanche54
Posts: 15
Joined: Wed Jun 06, 2012 9:57 pm

Re: New motherboard

Postby danielblanche54 » Thu Jun 07, 2012 7:21 am

Thanks for the quick response.
I am familiar with linux, although I don't know much about linux and networking.
I ran lspci (naturally I can't copy and paste the output) but the internal network card and the dlink pci one I last installed in the server are listed there.
Is there any way I can see what the network cards are mapped as (as in eth1, eth0 etc) I always assumed that ifconfig would list all of them on a system but I could easily be wrong.
Was this the method to change the network interface you were talking about?
http://wiki.amahi.org/index.php/ETH1

I'm currently in class at the university so I'll give it an attempt to fix when I get home tonight if it is.
Thank you for your help, it is deeply appreciated,

Daniel

User avatar
sgtfoo
Posts: 419
Joined: Sun Jul 18, 2010 8:27 pm

Re: New motherboard

Postby sgtfoo » Thu Jun 07, 2012 9:58 am

Found it:

http://wiki.amahi.org/index.php/Binding_Network_Devices

Yea be very careful.

As for seeing what's found/bound .. look at the network menu item from the fedora desktop... or even the control panel items. There's bound to be a listing of your interfaces.
The other commands for finding interfaces, I'm not quite familiar with. May need some more homework to find em.
SgtFoo
HDA: VM inside oVirt FX-8300 95w (2 cores for HDA), 32GB RAM (2GB for HDA)
My PC: FX-8300, 16GB RAM, 3x 1TB HDDs, Radeon HD6970 2GB video; Win10 Pro x64
Other: PC, Asus 1215n (LXLE), Debian openZFS server (3x(2x2tb) mirrors)
Modem&Network: Thomson DCM475; Asus RT-AC66U; HP 1800-24G switch

danielblanche54
Posts: 15
Joined: Wed Jun 06, 2012 9:57 pm

Re: New motherboard

Postby danielblanche54 » Thu Jun 07, 2012 4:12 pm

I changed the bind name for the network card I want to use to eth0 but when I run
/etc/init.d/network restart
I get the error
Device eth0 has different MAC address then expected. I got the feeling there is another file I need to change the address in.

Update

I fixed it. I went into /etc/sysconfig/networking/devices and edited the file ifcfg-eth0 to comment out the line starting HWADDR=
Restarted and works like a charm. Thank you so much for your help

Who is online

Users browsing this forum: No registered users and 12 guests