Gentoo Error network interface eth0 does not exist. . .
aambi...@yahoo.com
and I've been trying to fix my network settings ever since. The only
way I can get online is if i boot up the cd but otherwise I keep
getting this. .
ERROR network interface eth0 does not exist
Please verify hardware or kernel module (drivers)
Now I'm not lazy, I looked up the subject to try and fix it and this
is what I've done so far, I setup the network by making a symbolic
link between net.lo and net.eth0
I configured the network interface by going to /etc/conf.d/net which
looks like
config_eth0=("192.168.0.7 netmask 255.255.255.0")
routes_eth0=("default via 192.168.0.1")
And I've tried to start it with # /etc/init.d/net.eth0 start
but it still says eth0 doesn't exist. I also tried erasing /etc/udev/
rules.d/70-persistent-net.rules and restarting but that didn't work so
what else can i do?
Heres some other details, I called my PC manufacturer (Gateway) to get
my NIC info and they said I don't have one, its integrated with the
motherboard or something like that and the maker is Foxcom but when I
put in ifconfig instead of seeing eth0 plus all the info I see dummy0
so what does that mean?? Please help . .
Graham Murray
> Heres some other details, I called my PC manufacturer (Gateway) to get
> my NIC info and they said I don't have one, its integrated with the
> motherboard or something like that and the maker is Foxcom but when I
> put in ifconfig instead of seeing eth0 plus all the info I see dummy0
> so what does that mean?? Please help . .
It probably means that the driver for your NIC is neither built into the
kernel nor as a module. Install sys-apps/pciutils, if you have not
already done so, and run 'lspci'. From this you should be able to
identify the NIC on your motherboard, then update your kernel
configuration to include the driver for the NIC and rebuild the kernel.
Unruh
> Ok well I just installed linux gentoo from a livecd a couple days ago
>and I've been trying to fix my network settings ever since. The only
>way I can get online is if i boot up the cd but otherwise I keep
>getting this. .
> ERROR network interface eth0 does not exist
> Please verify hardware or kernel module (drivers)
Well, you need to do what it says.
First run
ifconfig
and show us everything that is listed. Not what you think is relevant,
since by your admission you do not know what is relevant, -- everything.
Then do
dmesg|grep eth
and show us what is listed.
>Now I'm not lazy, I looked up the subject to try and fix it and this
>is what I've done so far, I setup the network by making a symbolic
>link between net.lo and net.eth0
No idea what you are talking about, and that is certainly wrong anyway.
eth0 has nothing to do with lo, and trying to force it is certain to mess
up everything.
>I configured the network interface by going to /etc/conf.d/net which
>looks like
>config_eth0=("192.168.0.7 netmask 255.255.255.0")
>routes_eth0=("default via 192.168.0.1")
It looks like you are using dhcp-- or if not tell us. If you are then those
are almost certainly wrong.
>And I've tried to start it with # /etc/init.d/net.eth0 start
Since you linked net.eth0 to net.lo this will NOT give you eth0 starting
up.
Does your distro really stuff net.* into /etc/init.d?
>but it still says eth0 doesn't exist. I also tried erasing /etc/udev/
>rules.d/70-persistent-net.rules and restarting but that didn't work so
>what else can i do?
>Heres some other details, I called my PC manufacturer (Gateway) to get
>my NIC info and they said I don't have one, its integrated with the
>motherboard or something like that and the maker is Foxcom but when I
>put in ifconfig instead of seeing eth0 plus all the info I see dummy0
>so what does that mean?? Please help . .
NO idea. You certainly do have a nic, whether built in or not.
Are you sure it is not disabled in the bios?
J.O. Aho
> Ok well I just installed linux gentoo from a livecd a couple days ago
> and I've been trying to fix my network settings ever since. The only
> way I can get online is if i boot up the cd but otherwise I keep
> getting this. .
When you use the LiveCD there is a probe your hardware service that detects
all your hardware (or at least tries to do so), but it's not used in a real
install, as that do take time and you usually don't change all your hardware
between the reboots.
Edit your /etc/modules.autoload.d/kernel-2.6 and add your NICs driver alone on
one of the lines.
--
//Aho
Arthur Hagen
> aambi...@yahoo.com writes:
>
> >Now I'm not lazy, I looked up the subject to try and fix it and this
> >is what I've done so far, I setup the network by making a symbolic
> >link between net.lo and net.eth0
>
> No idea what you are talking about, and that is certainly wrong anyway.
> eth0 has nothing to do with lo, and trying to force it is certain to mess
> up everything.
It's clear that you have no idea what he's talking about, because a
symlink to net.lo is the CORRECT way of setting up additional network
interfaces in Gentoo.
ls -d /etc/init.d/net.*
lrwxrwxrwx+ 1 root root 6 Oct 1 13:58 /etc/init.d/net.eth0 ->
net.lo
lrwxrwxrwx+ 1 root root 6 Mar 21 2007 /etc/init.d/net.eth1 ->
net.lo
-rwxr-xr-x+ 1 root root 30696 Oct 1 13:58 /etc/init.d/net.lo
The script will look at the name it's called with, and set up that
interface.
However, that's just the first part of the battle. If a network
connection is needed by another start-up script, it will automatically
start the FIRST /etc/init.d/net.* script found (besides .lo), but that
might not be what you want, especially not if you have multiple
interfaces (ethernet, wifi...). So to specify which ones should be
started, create the symlink and then:
rc-update add eth0 default
rc-update add eth1 default
... et cetera, for all interfaces you need.
If you have additional pseudo-runlevels (like "gui"), add them there
too. Note that the interfaces must neither be started in the "boot" nor
"nonetwork" pseudorunlevels. "rc-update show" will show you the current
configuration.
You also should configure the parameters for the interfaces
in /etc/conf.d/net unless defaulting to dhcp is fine, and I see below
that you've done this.
If you depend on more than one of them coming up before other services
starting, make sure that RC_NET_STRICT_CHECKING="yes" is set
in /etc/conf.d/rc. For a laptop, this should normally be set to
"no" (it doesn't matter whether you're connected through ethernet or
wifi -- if you're connected, network dependent services should start).
> >I configured the network interface by going to /etc/conf.d/net which
> >looks like
>
> >config_eth0=("192.168.0.7 netmask 255.255.255.0")
> >routes_eth0=("default via 192.168.0.1")
>
> It looks like you are using dhcp-- or if not tell us. If you are then those
> are almost certainly wrong.
Why does it look to you like he's using dhcp? These are static entries,
making it look like he's NOT using dhcp.
> >And I've tried to start it with # /etc/init.d/net.eth0 start
>
> Since you linked net.eth0 to net.lo this will NOT give you eth0 starting
> up.
Yes, it will. It's the correct way.
> Does your distro really stuff net.* into /etc/init.d?
Ah. You're not even a Gentoo user? Then what are you doing here giving
incorrect advice?
> >but it still says eth0 doesn't exist. I also tried erasing /etc/udev/
> >rules.d/70-persistent-net.rules and restarting but that didn't work so
> >what else can i do?
Here's the problem. If it says that eth0 doesn't exist, it means that
the interface can't be seen by the system.
Do "lspci | grep -i eth".
If this lists your interface, at least your system can see it.
You then need to have support for this interface in the kernel, either
through a module or directly compiled in. If it's a permanently
attached interface, make it compiled in instead of a module, because
it's less overhead.
If it is a module, make sure it gets loaded at boot time. Add a line
to /etc/modules.autoload.d/kernel-2.6
Now reboot, and check the boot time kernel log (through "dmesg", or
better, look at /var/log/dmesg) for messages stating that the device was
set up, or what the problem was.
If successful, you should be able to do "ls -l /sys/class/net" and see
all your network interfaces. This should correspond to "ifconfig -ai"
and "netstat -ai".
And don't listen to Unruh. This is Gentoo, which he has no knowledge
of.
Regards,
--
*Art
Michael Mauch
> rc-update add eth0 default
> rc-update add eth1 default
> ... et cetera, for all interfaces you need.
Shouldn't these be
rc-update add net.eth0 default
rc-update add net.eth1 default
?
"rc-update show" shows "net.eth0 | default" here.
Regards...
Michael
Arthur Hagen
> Arthur Hagen wrote:
>
> > rc-update add eth0 default
> > rc-update add eth1 default
> > ... et cetera, for all interfaces you need.
>
> Shouldn't these be
>
> rc-update add net.eth0 default
> rc-update add net.eth1 default
Yes, they should. I was obviously typing too quickly :-)
> "rc-update show" shows "net.eth0 | default" here.
Good -- that's what it should show.
Regards,
--
*Art
aambi...@yahoo.com
> On Tue, 2008-10-07 at 16:10 +0000, Unruh wrote:
>
>
> Here's the problem. If it says that eth0 doesn't exist, it means that
> the interface can't be seen by the system.
>
> Do "lspci | grep -i eth".
> > >is what I've done so far, I setup the network by making a symbolic
> > >link between net.lo and net.eth0
Have you heard about anything being wrong with the Gentoo amd64
liveCD? I say that because it doesn't seem to be seeing anything. I do
have all the info got saved to my pc because when it tells me a file
does not exist I go check but its telling me kernels dont exist too
but i've checked and they're there. Its starts up but I realize I have
the Gentoo installer which I see running most of the boot commands
that I see in the set-up guide. So do I have to re-do all the commands
in the guide to start everything up? I think I might have to start
from scratch so do you know of any others user friendly linux versions
that install the best, what about knoppix, any common set-up troubles
with that?