2.6.14-1 ok but since 2.6.14-2 hardware not detected and thus modules not loaded
I have a sid based system which runs fine with kernel 2.6.14-1 but which
will not find/initialize the network card with any 2.6.14-2 and above
kernel. I have updated the 2.6.14-2 kernel through version -2, -3, -4
and now -5 with similar results.
I think the problem may be with the hardware detection. The boot.log for
2.6.14-1 shows e1000 NIC (and other hardware) detected and modules
loaded. The boot.log for 2.6.14-2 does not seem to detect most of the
hardware.
Does anyone know what changed between 2.6.14-1 and 1.6.14-2 which may be
causing this?
When booting from 2.6.14-1 the same segment from /var/log/boot looks
like this:
=============================
Wed Dec 14 16:48:18 2005: Detecting hardware...Discovered hardware for
these modules: agpgart parport_pc e1000 via82cxxx aic7xxx emu10k1 usb_uhci
Wed Dec 14 16:48:19 2005: Loading agpgart module...
Wed Dec 14 16:48:20 2005: Loading parport_pc module...
Wed Dec 14 16:48:20 2005: Loading e1000 module...
Wed Dec 14 16:48:21 2005: ^[[33m*^[[39;49m Skipping already loaded
module via82cxxx.
Wed Dec 14 16:48:21 2005: Loading aic7xxx module...
Wed Dec 14 16:48:40 2005: ^[[33m*^[[39;49m emu10k1 disabled in
configuration.
Wed Dec 14 16:48:40 2005: Loading uhci_hcd module...
Wed Dec 14 16:48:41 2005: Setting sensors limits: done.
Wed Dec 14 16:48:41 2005: Running 0dns-down to make sure resolv.conf is
ok...done.
Wed Dec 14 16:48:41 2005: Setting up networking...done.
Wed Dec 14 16:48:41 2005: Setting hostname 'n3'...done.
Wed Dec 14 16:48:41 2005: Configuring network interfaces...done.
=============================
When booting from 2.6.14-1 it appears hardware is detected and modules
loaded ok
When booting from 2.6.14-5 the segment of /var/log/boot related to
hardware detection/module-loading looks like this:
=============================
Wed Dec 14 16:43:21 2005: Detecting hardware...Discovered hardware for
these modules: ide_scsi
Wed Dec 14 16:43:22 2005: ^[[33m*^[[39;49m Skipping unavailable/built-in
ide_scsi module.
Wed Dec 14 16:43:22 2005: Setting sensors limits: done.
Wed Dec 14 16:43:22 2005: Running 0dns-down to make sure resolv.conf is
ok...done.
Wed Dec 14 16:43:22 2005: Setting up networking...done.
Wed Dec 14 16:43:22 2005: Setting hostname 'n3'...done.
Wed Dec 14 16:43:22 2005: Configuring network interfaces...SIOCSIFADDR:
No such device
Wed Dec 14 16:43:33 2005: eth0: ERROR while getting interface flags: No
such device
Wed Dec 14 16:43:33 2005: SIOCSIFNETMASK: No such device
Wed Dec 14 16:43:33 2005: SIOCSIFBRDADDR: No such device
Wed Dec 14 16:43:33 2005: eth0: ERROR while getting interface flags: No
such device
Wed Dec 14 16:43:33 2005: eth0: ERROR while getting interface flags: No
such device
Wed Dec 14 16:43:33 2005: Failed to bring up eth0.
Wed Dec 14 16:43:34 2005: SIOCSIFADDR: No such device
Wed Dec 14 16:43:34 2005: eth0:1: ERROR while getting interface flags:
No such device
Wed Dec 14 16:43:34 2005: SIOCSIFNETMASK: No such device
Wed Dec 14 16:43:34 2005: eth0:1: ERROR while getting interface flags:
No such device
Wed Dec 14 16:43:34 2005: Failed to bring up eth0:1.
Wed Dec 14 16:43:34 2005: done.
===============================
I can load the module manually but still get similar eth0 / SIO...
messages when tryting to reinitialize the network.
Any help greatly appreciated.
R.Parr, RHCE, Temporal Arts
Reply to: