Read so many other topics - but: eth0 still no such decive

Tuxuser · Last edited by Tuxuser on Fri Nov 01, 2002 5:33 pm; edited 1 time in total

Hi!

must be a 1000 times I compiled my kernel, tried many things that someone recomended somebody but my eth0 will not start.

During boot currently the message is:
Bringing eth0 up
SIOCSIFADDR: No such device
eth0: unknown interface:No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface:No such device
SIOCSIFNETADDR: No such device
eth0: unknown interface:No such device

cat /proc/pci shows my (old type) 3Com 3c905-TX card.
ifconfig shows only "lo" entry.

Tried it in kernel or module. Not the slightest chance. The modules were refused to be loaded and compiled in the kernel, I don't know what it actually does. By the way, a 8139 card didn't work as well.
Meanwhile I did a lot of desperate things in /etc/host and /etc/conf.d/net but nothing helped.

Who feels challenged to help?

Ciao

Some additional information: when compiled as module the error messages I get with modprobe are about 7 "unresolved symbol..." regardless of 3Com or 8139 card

phong · Posted: Fri Nov 01, 2002 4:11 pm Post subject:

You may have already tried this, but what does ifconfig -a say (that should list all interfaces, including those that aren't up for whatever reason).
_________________
"An empty head is not really empty; it is stuffed with rubbish. Hence the difficulty of forcing anything into an empty head."
-- Eric Hoffer

Tuxuser · Posted: Fri Nov 01, 2002 4:18 pm Post subject:

Yepp, ifconfig -a also shows only "lo" .

meteor · Posted: Fri Nov 01, 2002 4:25 pm Post subject:

Have you tried editing /etc/modules.autoload and adding the name of your eth0-module? Of course this requires that you compiled it as a module. Other than that you could try modprobe it and ifconfig eth0 up.

I had a problem much like this and the way I solved is was like this:
1. Compile 8139too
2. Modprobe 8139too
3. ifconfig -a
4. ifconfig eth0 hw ether <macaddress>
5. ifconfig eth0 u
6. dhcpcd
7. add 8139too to /etc/modules.autoload

I change the macaddress because my LAN admin has my old macaddress registered. So you can safely skip that step.

Tuxuser · Posted: Fri Nov 01, 2002 4:37 pm Post subject:

Thanks, but this doesn't help. If I have the networkdevice as module I'm getting errors while trying to load them (modprobe or insmod). Of course at all times ifconfig eth0 up returns "eth0: unknown interface: No such device"

However, your answer is surprising, because your macaddr is supposed to be hardcoded, i.e. you shouldn't be able to change it - but this is part of the network forum ;-)

fyerk · Posted: Fri Nov 01, 2002 6:49 pm Post subject:

does the command dmesg have your network card listed?
_________________
-David

Tuxuser · Posted: Sat Nov 02, 2002 4:46 pm Post subject: Finally

Okay, I'm back to close this thread. Now, I know what happend. I accidently wrote my kernel in the wrong partition without realizing. By that time I interfered with my live system which I had had to bring up again.

Dear reader with similar problems: Be sure where you're writing your kernel too. Mount the correct partition into /boot!

And: When I saw the fault I made I felt rather silly. :oops: