hey,

i just upgraded from mdk9.2 to 10.0.
no probs, except my nic.
I'm using an ADMtek/ADM983 Linksys ethernet 10/100 card. - model LNE100TX ver. 5.1 - via my eth1; its a single comp, on my cable modem. [btw, which is dhcp; aka my ip isnt static - it changes every 6 months or so]

10.0 detects my card [in the control center] and my driver, tulip, but still i cant connect to the the internet.

when i tried to ping google.com; i came with this result:
unknown host google.com

when i pinged an ip, this came up:
connect:network is unreachable

It seems to be something specific with 10.0, as i didnt change anything, hardware-wise before/after the upgrade, and my nic is automatically detected and connects me to the internet during the bootup using knoppix 3.3 and in windows xp pro.

Also, i check my services; and i have the services network, internet, iptables all started up during boot. [though i noticed routed wasn't started, but what i've read, it doesnt seem that essential]

Here's some more info, if it helps [some from IRC said this would be helpful, they didnt solve my prob...]

the driver tulip is located in:
/lib/modules/2.4.22-10mdk/kernel/drivers/net/tulip


/etc/sysconfig/networking/devices
folder is empty

/etc/resolve.conf
didnt exist

my 'host.conf :
'
order hosts,bind
multi on


[info on my eth1 card]
[i realize its not on eth0, as my comp came with a 3com card, but i decided to use my linksys one instead, and it worked flawlessly on 9.2 and never looked back]

/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
BOOTPROTO=dhcp
onBOOT=yes
MII_NOT_SUPPORTED=no
WIRELESS_ENC_KEY=""
NEEDHOSTNAME=no

/etc/sysconfig/networking
has a file ifcfg-lo

[also in /etc/sysconfig/network-scripts/]
has in it:
DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
onBOOT=yes
=====================================================
I've already posted this on another forum, a couple times on IRC, with no avail. If you could help, it'd be very appreciated.


thanks in advance,
keyshawn

i had the same problem. using a LinkSys 10/100 eth0 card with ADSL. i have 2 installs going (one 10.0 stable, one 10.0 for testing). what i did to correct the problem is edit my ifcfg-eth0 config file & the eth0 is now detected during boot. i don't know if this will apply to all situations, but it might be worth a try. just back up your old ifcfg-eth0 file first.

go to /etc/sysconfig/network-scripts/ & open the ifcfg-eth0 file with a text editor. (you'll need to be root to edit this, so in a terminal as root type konqueror (enter) to open Konqueror file manager in superuser mode) make the contents of the file to read like this............



save it, reboot.

for comparison, here's what it looked like before the edit..........



notice the boot protocal line somehow was detected as DHCP during the install, which i don't have. i also removed the netmask line because it still wouldn't work with that in there.

otis

I have the exact same card...I hope the above fix works because mine isn't working either. I'll try it soon...

thanks for the help otis,
though I tried that out, and still ended up with the same result as before...

regards,
keyshawn

For mandrake 10, you'll have to solve the problem with that NIC with one simple fix. As root, open up this file: /etc/modprobe.preload

On a line by its own, type the name of the module you need, tulip.

Therefore:

nano -w /etc/modprobe.preload
<scroll down to free space in the file>
tulip
ctrl+x
"y"
enter

reboot


EDITED TO ADD THE FOLLOWING:

I realized that my post really veered off in another direction and people may be a bit confused as to what I was doing. Here's the thing - its a hardware problem with this particular card. You can configure the network everytime you boot if you want, but Mandrake won't "keep" the settings, so you think. For DHCP, /etc/resolv.conf would be empty if it didn't have a nameserver assigned. If you do a "lsmod" you'll find the module isn't loaded, but if you "modprobe tulip" its there and your internet settings are still there (ifconfig will confirm it). This is why you "force" the module to load so that when the network is "brought up", it will actually work (you may see that in the boot messages that it failed, but you'll still get online because it tries again (read /var/log/messages to see this). It will work as intended then. Probably, this is something small like the clone chip on the card not having a proper device ID, confusing the driver.

since i didnt have nano installed on my distro, i used gedit instead.

All i did though was just add the line

tulip

to the file, and it still came up with the same problem, after restarting my computer....

thanks for the help, though,
keyshawn

So, there's more to the problem, then. What does lsmod say?

tulip 4248 0


[note the spacing in between 8 and 0 ]

Can you do uname -r and see if that's the kernel you're using, or if you're booting to a 2.6.3 kernel? Does your modem have a login page? See if you can log in to its IP at all. Can you post the full ifconfig?

sry for the long delay, but i did uname -r and it says:
2.6.3-7mdk
for the kernel that i'm using...

hmm..i wonder why those paths above dont correspond to my new kernel ver.


cya - thanks,
keyshawn

Often you'd have to manually add the new kernel to your /etc/lilo.conf and then run /sbin/lilo to make the change go into effect. If you don't do that, for sure you won't be booting to it.

woot !!!!!!!!!!!!!!!!!!
I really don't know how - for sure, but the internet now works

I was tinkering with the drakconf, when i suddenly noticed that my linksys card got switched to eth0.
[dont know how, seriously]
I redid the settings, seeing that new eth0, and then it pretty much works now...

strange..

btw,
here's my ifconfig now:
======================================

eth0 Link encap:Ethernet HWaddr 00:04:5A:8B:F4:24
inet addr:68.170.222.5 Bcast:68.170.222.255 Mask:255.255.255.0
inet6 addr: fe80::204:5aff:fe8b:f424/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:81322 errors:0 dropped:0 overruns:0 frame:0
TX packets:53091 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:80656181 (76.9 Mb) TX bytes:16022396 (15.2 Mb)
Interrupt:21 Base address:0xd400

eth1 Link encap:Ethernet HWaddr 00:0C:6E:56:CF:65
inet6 addr: fe80::20c:6eff:fe56:cf65/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Memory:feafc000-0

eth1:9 Link encap:Ethernet HWaddr 00:0C:6E:56:CF:65
inet addr:127.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Memory:feafc000-0

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:621 errors:0 dropped:0 overruns:0 frame:0
TX packets:621 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:64308 (62.8 Kb) TX bytes:64308 (62.8 Kb)
==========================================================

vectordrake and everyone else,
thanks for all your help.
keyshawn

Excellent! back online is good! Usually its the little things, eh? I once went through what you were going through all over a bad cable. Spent hours! Now you're cooking with gas!