Since I already have some experience with Gentoo I'm not surprised it
just cowardly refuses to do something but this is one I don't know so
here we go... :-)
A while ago I replaced my old motherboard by another old one but the
replacement board was still 100% crash free.
I went from a P4 based Medion MD 5000 board
(http://217.110.237.67/Manuals/Medion%20MD5000.pdf) to another similar
one being an ASRock P4VT8+
(http://www.asrock.com/mb/overview.asp?Model=P4VT8%2B).
So I compiled my kernel before the switch with all the needed drivers
and all is working fine but one thing: eth0 does not exist.
I don't understand since all the stuff is in the kernel (basically the
VIA Rhine II driver) and it's even detected at boot time but it can't be
brought up.
This is the relevant kernel snippet:
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_IP_FIB_HASH=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_PCI=y
CONFIG_VIA_RHINE=y
CONFIG_VIA_RHINE_MMIO=y
CONFIG_VIA_RHINE_NAPI=y
And this is what dmesg has to say:
eth0: VIA Rhine II at 0xdfffb900, 00:0b:6a:73:04:f1, IRQ 16.
eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
But when I manually run /etc/init.d/net.eth0 start I get:
* Starting eth0
* Bringing up eth0
* dhcp
* network interface eth0 does not exist
* Please verify hardware or kernel module (driver)
I'm quite sure I forgot something stupid but I don't know what, so if I
need to do more elaboration please tell me since I've been using Windows
since... :-/
Thanks,
Wimmy
> But when I manually run /etc/init.d/net.eth0 start I get:
>
> * Starting eth0
> * Bringing up eth0
> * dhcp
> * network interface eth0 does not exist
> * Please verify hardware or kernel module (driver)
>
> I'm quite sure I forgot something stupid but I don't know what, so if I
> need to do more elaboration please tell me since I've been using Windows
> since... :-/
As Aragorn correctly said, it's probably a udev-related problem, since your
new ethernet card has a different MAC address. Try removing the
file /etc/udev/rules.d/70-persistent-net.rules (udev will recreate it with
sane values at next boot), reboot and see what happens.
Regards
Yay, it works! :-)
Thanks!