Hi all y'all,

I am having a really irritating problem with Mandrake 10 Community release: my internet connection parameters are not saved properly and I have to set up a new connection (which I do via the Mandrake Control Center) everytime I boot up! Here is the associated log:

21:11:13 drakconnect[2133]: ### Program is starting ###
21:11:24 drakconnect[2133]: launched command: /sbin/chkconfig --add internet
21:11:24 drakconnect[2133]: modified file /etc/sysconfig/network
21:11:24 drakconnect[2133]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0
21:11:24 drakconnect[2133]: written eth0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth0
21:11:24 drakconnect[2133]: writing host information to /etc/hosts
21:11:24 drakconnect[2133]: created file /etc/hosts
21:11:24 drakconnect[2133]: modified file /etc/tmdns.conf
21:11:24 drakconnect[2133]: launched command: /sbin/chkconfig --add internet
21:11:24 drakconnect[2133]: modified file /etc/sysconfig/network
21:11:24 drakconnect[2133]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0
21:11:24 drakconnect[2133]: written eth0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth0
21:11:24 drakconnect[2133]: writing host information to /etc/hosts
21:11:24 drakconnect[2133]: created file /etc/hosts
21:11:24 drakconnect[2133]: modified file /etc/tmdns.conf

I was having problems with the files /etc/sysconfig/network-scripts/net_cnx_up and /etc/sysconfig/network-scripts/net_cnx_down (they spat out a "Usage" message) so I installed the latest drakxtools package (version 10-34.2.100mdk). Now the unsightly error messages have disappeared yet it doesn't help...

Cheers,

Jan

I suspect you have the same common problem as I just answered a minute ago. Probably your NIC module is not being picked up by hotplug and is not loading. When you boot up, look to see if it loads, by hitting "esc" and watching the boot messages. It should have a "bringing up the network" section. When you are booted, you should be able to see the module for your NIC in the results of typing (as root) lsmod. If not, If that's it, add the name of your module to the config file /etc/modprobe.preload with your favorite text editor (as root) and it should force the module to load at boot. I had the same problem with my card on MDK10 beta2. The IP info, etc was still there, so it was just the hardware recognition. I'll cross my fingers for ya.

I'm a very happy camper right about now! Following your advice I added the last line below

[root@tux jan]# cat /etc/modprobe.preload
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules

scsi_hostadapter
intel-agp
8139too
[root@tux jan]#

and it works like a charm. In another thread somebody told someone with a related problem to add "alias eth0 8139too' to /etc/modules.conf. I had done it as well but that clearly wasn't enough.

Many thanks again.

Jan

The comments in this file pretty much tell why that is. Times are a-changin' I think this i s some kind of glitch in the hotplugging system. My card is activated without that line now, but with kernels (the generic MDK one - not recompiled) up to 2.6.3-13mdk, it still showed as "failed" on the bootup messages being echoes to my screen, but with the 2.6.7.0-rc2-1, which I am crazy enough to be running, the message is good now.