Hello,
I'm looking at what's happening during a boot in the /var/log/boot file: First /etc/modules is read:
Wed Aug 11 09:54:58 2004: Calculating module dependencies... done. Wed Aug 11 09:54:58 2004: Loading modules... Wed Aug 11 09:54:58 2004: dmfe Wed Aug 11 09:54:58 2004: usblp Wed Aug 11 09:54:58 2004: uhci_hcd Wed Aug 11 09:54:59 2004: usbhid Wed Aug 11 09:54:59 2004: usbcore Wed Aug 11 09:54:59 2004: All modules loaded.
Good, that makes sence (you see I'm using a 2.6.x kernel, named 2.6.7.040630)
Then some other stuff comes around, and (I think) someone tries to load 2.4.x modules (? no idea what'd cause this!) :
Wed Aug 11 09:55:01 2004: Detecting hardware: agpgart dmfe emu10k1 usb_uhci Wed Aug 11 09:55:01 2004: Skipping unavailable/built-in agpgart module. Wed Aug 11 09:55:01 2004: Skipping already loaded module dmfe. Wed Aug 11 09:55:01 2004: Skipping unavailable/built-in emu10k1 module. Wed Aug 11 09:55:01 2004: Skipping unavailable/built-in usb_uhci module.
Then other stuff is done again; Finally, hotplug jumps in:
Wed Aug 11 09:55:02 2004: Starting hotplug subsystem: Wed Aug 11 09:55:02 2004: input Wed Aug 11 09:55:02 2004: input [success] Wed Aug 11 09:55:02 2004: isapnp Wed Aug 11 09:55:02 2004: isapnp [success] Wed Aug 11 09:55:02 2004: net Wed Aug 11 09:55:02 2004: net [success] Wed Aug 11 09:55:02 2004: pci Wed Aug 11 09:55:02 2004: uhci-hcd: already loaded Wed Aug 11 09:55:02 2004: uhci-hcd: already loaded Wed Aug 11 09:55:02 2004: ignoring pci display device on 01:00.0 Wed Aug 11 09:55:03 2004: snd-emu10k1: loaded successfully Wed Aug 11 09:55:03 2004: dmfe: already loaded Wed Aug 11 09:55:03 2004: pci [success] Wed Aug 11 09:55:03 2004: usb Wed Aug 11 09:55:04 2004: usb [success] Wed Aug 11 09:55:05 2004: done
Now, why is it doing everything twice? I see the same happening when the computer is shut down;
Also, I've no idea where discover went, I upgraded discover packages that had a weird problem; I logged that:
debian:/home/jorishuizer# apt-get -u dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages have been kept back: libdiscover1 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. debian:/home/jorishuizer# apt-get install libdiscover1 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: discover1-data The following packages will be REMOVED: discover discover-data libdiscover2 The following NEW packages will be installed: discover1-data The following packages will be upgraded: libdiscover1 1 upgraded, 1 newly installed, 3 to remove and 0 not upgraded.
I thought it'd be smart to let apt-get do what it thought was smart, but ever since discover doesn't start during boot (though I probably don't even need it as everything still functions)
Can anyone tell me what this module weirdness and stuff is? This is not urgent (the computer is working fine) but it just bugs me that I don't understand what it tries to do in the different stages of booting
Thanks for any help finding out, (if you need logs and stuff just tell me were to get them ;) )
Joris
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
