On Tuesday 06 January 2009 02:02:16 Francisco Ares wrote: > This is a snippet of the end of the boot screen: > > * Setting framebuffer console images ... [ ok ] > * Starting gpm ... [ ok ] > * Setting up kdm ... [ ok ] > * Loading ALSA modules ... > * Loading: snd-seq-oss ... [ ok ] > * Loading: snd-pcm-oss ... [ ok ] > * Restoring Mixer Levels ... [ ok ] > * Starting > * no interface module has been loaded
That looks suspicious to me. Init seems to be trying to run an (in effect) empty file in /etc/init.d/. What else have you got in there that doesn't belong? This is mine: $ ls -w 76 /etc/init.d acpid dbus lm_sensors numlock spamd alsasound depscan.sh local pwcheck sshd bootmisc dnsextd localmount pydoc-2.4 syslog-ng checkfs fancontrol mdnsd pydoc-2.5 udev-postmount checkroot functions.sh mDNSResponderPosix reboot.sh urandom chronyd gkrellmd modules rmnologin vixie-cron clock gpm net.eth0 rsyncd xdm consolefont halt.sh net.lo runscript.sh crypto-loop hostname netmount saslauthd cupsd keymaps nscd shutdown.sh Four of those are soft links: depscan.sh, functions.sh, net.eth0 and runscript.sh, thus: $ (cd /etc/init.d && ls -l depscan.sh functions.sh net.eth0 runscript.sh) lrwxrwxrwx 1 [...] depscan.sh -> ../../sbin/depscan.sh lrwxrwxrwx 1 [...] functions.sh -> ../../sbin/functions.sh lrwxrwxrwx 1 [...] net.eth0 -> net.lo lrwxrwxrwx 1 [...] runscript.sh -> ../../sbin/runscript.sh Your script execution order doesn't look right to me. This is what happens on my system: INIT: Entering runlevel: 3 * Starting eth0 * Bringing up eth0 * 192.168.2.6 [ ok ] * Adding routes * default via 192.168.2.1 ... [ ok ] * Mounting network filesystems ... [ ok ] * Setting up kdm ... [ ok ] * Loading ALSA modules ... * Loading: snd-pcm-oss ... [ ok ] * Loading: snd-seq-oss ... [ ok ] * Restoring Mixer Levels ... [ ok ] * Starting chronyd ... [ ok ] * Starting D-BUS system messagebus ... [ ok ] * Starting cupsd ... [ ok ] * Loading lm_sensors modules... * Loading i2c-nforce2 ... [ ok ] * Loading adm1026 ... [ ok ] * Loading w83627hf ... [ ok ] * Loading k8temp ... [ ok ] * Initializing sensors ... [ ok ] * Starting sshd ... [ ok ] * Starting vixie-cron ... [ ok ] * Starting local ... [ ok ] (I don't run gpm if I'm starting X; I have a separate soft-level for console operation, and it does run there.) Have you sync'd recently? Which profile did you install from? This is mine: $ ls -l /etc/make.profile lrwxrwxrwx 1 root root 50 2008-12-10 11:24 /etc/make.profile -> ../usr/portage/profiles/default/linux/amd64/2008.0 You might like to look at these again, as they also affect the execution order: $ grep PLUG /etc/conf.d/rc | grep -v \# RC_HOTPLUG="yes" RC_COLDPLUG="yes" RC_PLUG_SERVICES="!*" -- Rgds Peter
