eth0 - services, netmount problem after boot

Shrekkie · n00b Joined: 22 May 2003 Posts: 64 Location: Belgium

First of all , my apologies if this ahs been posted many times before...

Anyway here's my prob.

I installed gentoo, everything seems to work fine, no problems at all, but when i boot the system not off the gentoo cd, the only error i got on boot is "needing services, netmount not started" as result the eth0 is down, only localloop is up.

So I booted back of the cd, mounted back via /mnt/.. en chroot, to discover what modules he uses there. A dmesg | grep eth gives me an AMDTek Comet Rev17 (although the nic is sitecom), and an lsmod here doesn't show any module refering to the nic loaded. Is it maybe just a driver ? dunno. So i went into the kernel , searched this driver, but the closest thing is a AMD Pcnet32 which i choose and re made the kernel, did the eth0 update and rebooted. Still ain't working...
So i tried the Realtek module cause it seems to support lots of *unknown* nics, didn't work either.
Oh yes i saw the dummy net driver support moduled ( actually what is this), but unmoduling this didn't work neither.

It can't be a big prob cause the whole installation itself went just fine, i know the nic works, my thoughts it's just a driver issue.

Anyway I'm a little desperate here and i really want that gentoo...

Hope you guys can help...

Shrekkie · n00b Joined: 22 May 2003 Posts: 64 Location: Belgium

Anyway i read up some other similar threads here, and they practically all refer to a driver problem.

There's also another prob that crossed my mind.
When I do an lsmod of the livecd he gives a small list of modules, ordinary booted I can't see any modules loaded.

Greetz,

Shrekkie · n00b Joined: 22 May 2003 Posts: 64 Location: Belgium

Just me putting in some extra info here...

Anyway like I said via livecd I get a AMDtek Comet Rev17 back via dmesg. Which driver is most compatible with the AMDtek ?

Makaveli[FIN] · n00b Joined: 31 Oct 2002 Posts: 31 Location: Pori, Finland

I have/had the same problem. So I just made this little script which i run every time after the booting:

/etc/netti:

ifconfig eth0 down
ifconfig eth0 192.168.0.2 broadcast 192.168.1.255 netmask 255.255.255.0
route add -net default gw 192.168.0.1 netmask 0.0.0.0 metric 1

After that, my eth0 works again.
_________________
https://niko.nwps.fi

Shrekkie · n00b Joined: 22 May 2003 Posts: 64 Location: Belgium

Anyway this may be for future people with same prob....

I found my solution :

1. I emerged the vanilla-sources kernel instead of the gentoo-sources
2. make a symbolic link to the new kernel
3. cd /usr/src/linux and make menuconfig to configure in the kernel
4. choose the tulip under network device support (not module)
5. rc-update add net.eth0 default
6. reset LILO ( if you got lilo of course) and reboot

With me after the reboot it went up immediately , could ping google , etc...

Greetz,

JorBond · n00b Joined: 21 May 2003 Posts: 11

Shrekkie · n00b Joined: 22 May 2003 Posts: 64 Location: Belgium

go into the dir /usr/sr/

ln -sf 2.**** /linux

Now you've told the system to use the new kernel.
anyway where 2.**** is you should put the kernel, you can look it up in that dir.

Hope that helps,