eth0: unknown interface: No such device
OK here's the deal I'm trying to make a bare-bonez floppy distribution with networking capability. I'm testing it on my usual workstation. This machine uses the 3c59x driver for eth0. Now, I've compiled the 3c59x driver into the kernel on the floppy distro, but when I run ifconfig I get: eth0: unknown interface: No such device. I've tried adding ether=10,0xb000,eth0 as arguments to the kernel, but no go (I've also tried ether=0,0,eth0). I've also tried compiling the driver as a module but no luck with this either (Device or resource busy). Again, both approaches work fine on this same machine as far as the O/S on my hard drive is concerned. It's only in the context of the boot floppies that it bombs. The distro on these floppies is home-brewed and very minimal: basically /sbin/init, /bin/sh, /proc, and not much else. So maybe I'm missing some user-space binary/config-file which is failing silently. Any suggestions? -chris
SOLVED: eth0: unknown interface
It is fine now. My /etc/init.d/network looks like this #! /bin/sh ifconfig lo 127.0.0.1 route add -net 127.0.0.0 netmask 255.255.255.0 lo I added the netmask to avoid the SIOCADDRT: invalid argument message at boot time. This has been a last years subject. Thank you. Armin
eth0: unknown interface
Hi, At boot potato gives me this message eth0: unknown interface: No such device I guess that eth0 is an interface for ethernet cards. I don't have one. So I don't need this message. What can I do against it? Is there a package which I can delete? Armin
Re: eth0: unknown interface
That has nothing to do with it and won't work (by the way, there are a lot
more network cards then just ne compatible ones).
What you should do is edit your /etc/init.d/network, you should make it
look like something like this:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
If you want to you could let your system think it's on a LAN by adding the
following lines:
IPADDR=10.10.10.10
NETMASK=255.255.255.0
NETWORK=255.255.255.0
BROADCAST=10.10.10.255
GATEWAY=
ifconfig lo ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
I never actually tried that, but I guess it should work (take notice of
the lo after ifconfig, in your /etc/init.d/network it will probably be
eth0 (ip adresses can of course also be altered (that is: 10.10.10.10 and
with it 10.10.10.255).
Ron
On Mon, 21 Feb 2000 [EMAIL PROTECTED] wrote:
eth0: unknown interface: No such device
I guess that eth0 is an interface for ethernet cards. I don't have
one. So I don't need this message. What can I do against it? Is there
a package which I can delete?
Maybe it's enough to deactivate the following line in your
/etc/conf.modules:
# alias eth0 ne
^--- deactivating
Uwe
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: eth0: unknown interface
That has nothing to do with it and won't work (by the way, there are a lot
more network cards then just ne compatible ones).
What you should do is edit your /etc/init.d/network, you should make it
look like something like this:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
If you want to you could let your system think it's on a LAN by adding the
following lines:
IPADDR=10.10.10.10
NETMASK=255.255.255.0
NETWORK=255.255.255.0
BROADCAST=10.10.10.255
GATEWAY=
ifconfig lo ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
I never actually tried that, but I guess it should work (take notice of
the lo after ifconfig, in your /etc/init.d/network it will probably be
eth0 (ip adresses can of course also be altered (that is: 10.10.10.10 and
with it 10.10.10.255).
Ok, I think your right, because it could be possible that some daemons
need a network card to work properly. All of our computers which are
running Linux have a card, because they are connected in a network. I
have never tried to setup a computer with Linux but without NIC.
Uwe
Re: eth0: unknown interface
Well, what you said about the modules.conf would only prevent the computer
from loading the module for the network card when booting. By loading in
this module the interface (eth0, or if there are more network cards eth1,
eth2 etc.) is known, later during boot the init.d scripts are being called
(when switching to runlevel 2, as specified in /etc/rc.2) and the
/etc/init.d/network script is also called, that script configures the
network and uses the interface eth0 to do so. That's where the error
occurs, the script tries to bring eth0 up (using ifconfig) where the
interface does not exist.
Ron
On Mon, 21 Feb 2000 [EMAIL PROTECTED] wrote:
That has nothing to do with it and won't work (by the way, there are a lot
more network cards then just ne compatible ones).
What you should do is edit your /etc/init.d/network, you should make it
look like something like this:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
If you want to you could let your system think it's on a LAN by adding the
following lines:
IPADDR=10.10.10.10
NETMASK=255.255.255.0
NETWORK=255.255.255.0
BROADCAST=10.10.10.255
GATEWAY=
ifconfig lo ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
I never actually tried that, but I guess it should work (take notice of
the lo after ifconfig, in your /etc/init.d/network it will probably be
eth0 (ip adresses can of course also be altered (that is: 10.10.10.10 and
with it 10.10.10.255).
Ok, I think your right, because it could be possible that some daemons
need a network card to work properly. All of our computers which are
running Linux have a card, because they are connected in a network. I
have never tried to setup a computer with Linux but without NIC.
Uwe
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: eth0: unknown interface
Well, what you said about the modules.conf would only prevent the computer from loading the module for the network card when booting. By loading in this module the interface (eth0, or if there are more network cards eth1, eth2 etc.) is known, later during boot the init.d scripts are being called (when switching to runlevel 2, as specified in /etc/rc.2) and the /etc/init.d/network script is also called, that script configures the network and uses the interface eth0 to do so. That's where the error occurs, the script tries to bring eth0 up (using ifconfig) where the interface does not exist. So I think there are only two ways to stop an unnecessary network card form starting up at bootup. 1) Start the installation program from CD and remove the unwanted modul 2) Deactivate any unwanted startup job in /etc/init.d/ and you can later activate it if you want. There are several files in know which must be stoped from starting network jobs. /etc/init.d/netstd_init /etc/init.d/netstd_misc /etc/init.d/network Am I right? Uwe
Re: eth0: unknown interface
Removing the module won't work, because bye removing the module the interface eth0 still won't exist (you could say it exists even less) and the error will still occur. Renaming the scripts will work, along with editing /etc/init.d/network and another possible solution is reconfiguring the network (the way you did installing debian). Ron On Mon, 21 Feb 2000 [EMAIL PROTECTED] wrote: Well, what you said about the modules.conf would only prevent the computer from loading the module for the network card when booting. By loading in this module the interface (eth0, or if there are more network cards eth1, eth2 etc.) is known, later during boot the init.d scripts are being called (when switching to runlevel 2, as specified in /etc/rc.2) and the /etc/init.d/network script is also called, that script configures the network and uses the interface eth0 to do so. That's where the error occurs, the script tries to bring eth0 up (using ifconfig) where the interface does not exist. So I think there are only two ways to stop an unnecessary network card form starting up at bootup. 1) Start the installation program from CD and remove the unwanted modul 2) Deactivate any unwanted startup job in /etc/init.d/ and you can later activate it if you want. There are several files in know which must be stoped from starting network jobs. /etc/init.d/netstd_init /etc/init.d/netstd_misc /etc/init.d/network Am I right? Uwe
Re: eth0: unknown interface...
It may not help, but I installed debian on my laptop using a laplink cable and it was not too difficult to set up. I was planning on using an ethernet card, but I couldn't get one right away... so I spent $10 on a laplink cable instead. Hugo van der Merwe wrote: Hello, I have installed the debian base system on a laptop, but now I need to install the rest over a network (from another brilliant working Debian machine). For this to work, I must get the pcmcia network card working... I installed the same kernel package I installed on anther laptop, and the pcmcia-modules package that was compiled with it, and am using the same network card. However, even with this kernel, eth0 is still an unknown device. How does Debian Linux get to know eth0? I though it was only in the kernel, but clearly it isn't. Or what modules must I load with modprobe? Thanks in advance, Hugo van der Merwe -- ps. Please ensure replies are also sent to [EMAIL PROTECTED] - I do not subscribe to the mailing list, and I mistrust the news server I read the list through. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
eth0: unknown interface...
Hello, I have installed the debian base system on a laptop, but now I need to install the rest over a network (from another brilliant working Debian machine). For this to work, I must get the pcmcia network card working... I installed the same kernel package I installed on anther laptop, and the pcmcia-modules package that was compiled with it, and am using the same network card. However, even with this kernel, eth0 is still an unknown device. How does Debian Linux get to know eth0? I though it was only in the kernel, but clearly it isn't. Or what modules must I load with modprobe? Thanks in advance, Hugo van der Merwe -- ps. Please ensure replies are also sent to [EMAIL PROTECTED] - I do not subscribe to the mailing list, and I mistrust the news server I read the list through.
Re: eth0: unknown interface...
I have installed the debian base system on a laptop, but now I need to install the rest over a network (from another brilliant working Debian machine). For this to work, I must get the pcmcia network card working... I just realised, I think I didn't make use of the menu item Configure PCMCIA Support. Is there an easy way of configuring PCMCIA support for installation once I've already installed the base system? Can I run dbootstrap again? Where do I get it (the boot disks aren't mountable, right?) Or is it easier to reinstall from scratch? I installed the same kernel package I installed on anther laptop, and the pcmcia-modules package that was compiled with it, and am using the same network card. However, even with this kernel, eth0 is still an unknown device. How does Debian Linux get to know eth0? I though it was only in the kernel, but clearly it isn't. Or what modules must I load with modprobe? As I just mentioned, I think the pcmcia card isn't properly configured/initialised. Thanks in advance, Hugo van der Merwe -- ps. Please ensure replies are also sent to [EMAIL PROTECTED] - I do not subscribe to the mailing list, and I mistrust the news server I read the list through.
Re: eth0: unknown interface...
Hugo van der Merwe [EMAIL PROTECTED] writes: I have installed the debian base system on a laptop, but now I need to install the rest over a network (from another brilliant working Debian machine). For this to work, I must get the pcmcia network card working... I just realised, I think I didn't make use of the menu item Configure PCMCIA Support. Is there an easy way of configuring PCMCIA support for installation once I've already installed the base system? Can I run dbootstrap again? Where do I get it (the boot disks aren't mountable, right?) Or is it easier to reinstall from scratch? Please have a look at pcnetconfig(8) part of pcmcia-cs. (Sorry I don´t use pcmcia, this turned up using zgrep config Contents-i386.gz |grep pcmcia) HTH, Jens -- P.S.: Please vote against Spam! At http://www.politik-digital.de/spam/ (Sorry Europeans only) --- [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 2048/E451C639 Jens Ritter Key fingerprint: 5F 3D 43 1E 24 1E CC 48 1E 05 93 3A A7 10 73 37
Re: eth0: unknown interface
How does one have a compiled AND module driver? Where can I look to find out what other modules are being loaded? -Original Message- From: John Stevenson [EMAIL PROTECTED] To: Rino Mardo [EMAIL PROTECTED] Cc: Debby Ian debian-user@lists.debian.org Date: Tuesday, December 08, 1998 7:24 PM Subject: Re: eth0: unknown interface One of the easiest ways to configure the network is to use the install program on the Rescue Disk / CDRom. You can mount an already initialised swap and linux partition and then move on to configure the network. This will create all the right files for you (/etc/networks /etc/resolv.conf). If you still have problems it may be due to the drivers, either compiled into the kernel or a module, be careful not to have the 3com driver compiled into the kernel and as a module, I did that once and had the problem as you describe. Rino Mardo wrote: 486/66 with 8 MB RAM, 630 MB hard disk, 3C509B-combo NIC My problem is during initial installation I wasn't able to setup the NIC so now here I am in the # prompt not knowing how to add/configure it. I read thru all the HOWTOs and mini-HOWTOs (relevant ones of course), recompiled the kernel with 3C509 support but still it would give me: eth0: unknown interface as the error message. In SCO UNIX there's this netconfig command to add a NIC and assign protocols and ip address before recompiling the kernel. What's the equivalent command/steps in Linux? TIA. BEGIN:VCARD VERSION:2.1 N:Mardo;Rino FN:Rino Mardo ORG:Obaid Humaid Al-Tayer;IT Department TITLE:Network and Systems Administrator NOTE:Certified Lotus Professional, R4 Administrator TEL;WORK;VOICE:+971 4 825000 TEL;WORK;FAX:+971 4 824901 ADR;WORK:;;P.O. Box 2623;Dubai;;;United Arab Emirates LABEL;WORK;ENCODING=QUOTED-PRINTABLE:P.O. Box 2623=0D=0ADubai=0D=0AUnited Arab Emirates URL:http://members.tripod.com/~rinom/ EMAIL;PREF;INTERNET:[EMAIL PROTECTED] EMAIL;INTERNET:[EMAIL PROTECTED] EMAIL;INTERNET:[EMAIL PROTECTED] EMAIL;INTERNET:[EMAIL PROTECTED] REV:19981209T043805Z END:VCARD
Re: eth0: unknown interface
Ethernet dirvers are not included in default kernel (as far as I am aware) so unless you have re-compiled your kernel then you shouldn't have any in. If you want to check, well I guess you could just look at the screen output during boot time and see if there is any repeated info about setting up your network card (this is how I noticed last time). Not sure if 'dmesg' will give you all the info you need. If the boot message Alternatives include using 'modconf' which allows you to add and remove modules, or you can just have a look in the /etc/modules file (probably quicker). Either of these should tell you if you have a module installed for your network device. Hope this helps Rino Mardo wrote: How does one have a compiled AND module driver? Where can I look to find out what other modules are being loaded? -Original Message- snip
eth0: unknown interface
Hi! I just got my trusty Debian Linux installed and here's my hardware setup: 486/66 with 8 MB RAM, 630 MB hard disk, 3C509B-combo NIC My problem is during initial installation I wasn't able to setup the NIC so now here I am in the # prompt not knowing how to add/configure it. I read thru all the HOWTOs and mini-HOWTOs (relevant ones of course), recompiled the kernel with 3C509 support but still it would give me: eth0: unknown interface as the error message. In SCO UNIX there's this netconfig command to add a NIC and assign protocols and ip address before recompiling the kernel. What's the equivalent command/steps in Linux? TIA.
Re: eth0: unknown interface
One of the easiest ways to configure the network is to use the install program on the Rescue Disk / CDRom. You can mount an already initialised swap and linux partition and then move on to configure the network. This will create all the right files for you (/etc/networks /etc/resolv.conf). If you still have problems it may be due to the drivers, either compiled into the kernel or a module, be careful not to have the 3com driver compiled into the kernel and as a module, I did that once and had the problem as you describe. Rino Mardo wrote: 486/66 with 8 MB RAM, 630 MB hard disk, 3C509B-combo NIC My problem is during initial installation I wasn't able to setup the NIC so now here I am in the # prompt not knowing how to add/configure it. I read thru all the HOWTOs and mini-HOWTOs (relevant ones of course), recompiled the kernel with 3C509 support but still it would give me: eth0: unknown interface as the error message. In SCO UNIX there's this netconfig command to add a NIC and assign protocols and ip address before recompiling the kernel. What's the equivalent command/steps in Linux? TIA.
