Hi!
I just installed Mandy 10 beta 2 , and I got the following trouble. I cannot connect to the internet. when I boot up, it looks for a network card and it waits for a long time, and finally gives me a failed status. I looked at my modem lights and they blink sometimes, just as normal in Mandy 9.2 or Win XP.

I checked in harddrake and my network card is there and working properly. I set up my ADSL connection right. Just like I did in Mandy 9.2 but no luck, always a failed status on boot up.

Any idea?

Thanks

Rich

I posted a bug report with bugzilla #7316 n this problem. One of 2 thing you can do to get your card to work. First thing try enabling and disabling hot plugging of the network. It seams the hot plug is buggy on install. If that dosn work copy the /etc/sysconfig/network-scripts directory from your 9.2 install. The second is what I did to get mine to work originally. After talking with the MDK team they told me to disable the hot plug but mine was already disabled to I enabled it rebooted and then disabled it rebooted and the network has been working fine since.

I was gonna create a thread about this, but you already have one, so I'll add to it here, since my issue mirrors yours closely.

I have a cable connection that I share with a Linksys router. I connect to the ISP with dhcp (handled by the router) and our computers connect via the router. They each have static IPs, for port forewarding purposes. The network card in my machine is a ‎ADM983 Linksys EtherFast 10/100. This card has a clone of the DEC 2104x chip, so the tulip driver works.

I have since updated my system with the 2.6.2-1mdk kernel (from cooker RPMs) and was wondering if the module was being called by the wrong kernel. I shouldn't have worried.

When I installed, I had networking. When I rebooted, i didn't. The card showed up with lspci. The module did not with lsmod. A quick "modprobe tulip" got me on the net. Or, conversely, I could 'create a new connection' with Mandrake control center and my settings were still there, ready for a few mouse clicks. So, the problem is autoloading of the module. I was about to recompile with it in the damn thing. Screw this module! But, I found the answer to the woes I have (and this may help all you other 2.6'er as well!) in a config file.

With the 2.4.x kernel, if you want to load a module a boot, there's a file in /etc/ that you can insert a module name into and it should load on boot. That file is /etc/modules . The comments inside the file are
I tried that. I entered tulip on its own line. Rebooted. Nothing new. Ifconfig gives me no card. I then started looking at the contents of every config file in /etc that looked useful to a module loader. I stumbled upon the solution: /etc/modprobe.preload

I fired up jed (my fave editor for small config stuff):

jed /etc/modprobe.preload

Lo and behold, I found this inside
Below the comments, I typed tulip and saved the file. rebooted, and there was my network. ifconfig came back with a healthy eth0 entry. lsmod proved that the tulip module was indeed loaded. The internet came back to me without extra work.

Despite this, a look at /var/log/dmesg showed that eth0 had failed to load
When booting, the message was plain as the light of day, a big red failed. Regardless, the interface was up. A long read into /var/log messages showed that indeed, the card was probed by ifplugd and came back as unable to load at one point. Another point, after (logged the next second - I guess after it was logged as failed) it was successful. Here are the relavent lines:

but,

Without the addition of that one word in the /etc/modprobe.preload I didn't get that part of the message. The interface stayed down until I manually inserted the module.

This is lengthy, but I figured that its an important 2.6 kernel issue, as the file is different. Now I surf like mad! Now for kde...