On Mon, Jan 5, 2009 at 11:21 PM, Nick Cunningham <[email protected]>wrote:
> > Sorry to answer a question with another one, but how do I know to which >> group the services should be added? >> >> That really might be the solution of my problem. And, yes, it is really X >> . >> >> This is the output from rc-uptate -s : >> acpid | default >> alsasound | default >> apcupsd | default >> bootmisc | boot >> bootsplash | default >> checkfs | boot >> checkroot | boot >> clock | boot >> consolefont | boot >> consolekit | default >> cupsd | default >> dbus | default >> ddclient | default >> fbcondecor | default >> gpm | default >> hald | default >> hdparm | default >> hostname | boot >> keymaps | boot >> kmyfirewall | default >> lm_sensors | default >> local | default nonetwork >> localmount | boot >> modules | boot >> net.eth2 | default >> net.lo | boot >> numlock | default >> rdate | default >> rmnologin | boot >> serial | boot >> smartd | default >> sysklogd | default >> urandom | boot >> vixie-cron | default >> xdm | default >> >> Thanks again >> Francisco >> > > Looking over those everything seems fine, i was hoping an obvious problem > like xdm being in the boot group could have been a cause. > > Again, just to rule out the obvious, your sure your seeing xdm start up > early and not the framebuffer splash? > > One other thing to check is whether you have parallel startup enabled, > depending on whether your using openrc or not, this may be in /etc/rc.conf > or /etc/conf.d/rc (or a similar location, i dont quite remember it exactly). > Look for the following (or similar incase its changed): > # Set to "YES" if you want the rc system to try and start services > # in parallel for a slight speed improvement. When running in parallel we > # prefix the service output with it's name as the output will get > # jumbled up. > # WARNING: whilst we have improved parallel, it can still potentially lock > # the boot process. Don't file bugs about this unless you can supply > # patches that fix it without breaking other things! > rc_parallel="NO" > > Ideally you want it set to NO to ensure everything starts when it is meant > to. > > Hopefully one of these suggestions will help, if not the next idea is to > move to openrc if your not already as that may help, although there is some > risk involved in the upgrade. > > - Nick > rc_parallel="NO" (I have tried once, but gave up) and it is really X, I use "verbose" framebuffer images Gonna check that openrc, though. But, while re-emerging sysvinit: " * WARNING: You have older net.* files in /etc/init.d/ * They need to be converted to symlinks to net.lo. If you haven't * made personal changes to those files, you can update with the * following command: ... " Do the net.* also belong to the boot group of init scripts? 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 * Starting eth2 * Bringing up eth2 * adsl * Starting ADSL for eth2 [ ok ] * Starting APC UPS daemon ... [ ok ] * Starting cupsd ... [ ok ] * Starting ddclient ... [ ok ] Clearing iptables (created by KMyFirewall)... Done. Starting iptables (created by KMyFirewall)... Done. [ ok ] * Loading lm_sensors modules... * Loading coretemp ... [ ok ] * Initializing sensors ... [ ok ] * Enabling numlock on ttys ... [ ok ] * Setting clock via rdate ... [ ok ] * Starting S.M.A.R.T. monitoring daemon ... [ ok ] * Starting vixie-cron ... [ ok ] * Starting local ... [ ok ] This is ... " Thanks a lot! Francisco
