On Sunday 05 April 2009, Harry Putnam wrote: > Once again I find myself with a big mess following an update world. > This time I was probably out of date by more than 1 mnth, probably > less than 2. > > On first reboot the bootup proceeds well into level 3, right up to > starting hal daemon. > > There is sets.... forever. > > Since its past the point where sshd is started I can ssh into the > machine. > > I thought to maybe stop hald then attempt a restart. It appears > halting hald did allow the boot to continue, but it will not start. > > Consequently I have no mouse or keyboard at the login prompt. > > But I can ssh into the box. > > What should I supply here to allow someone to help diagnose the > problem? > > Recent info on hal from `qlop --list|grep hal' > > Sun Feb 15 10:52:16 2009 >>> app-misc/hal-info-20090202 > Sun Feb 15 10:54:45 2009 >>> sys-apps/hal-0.5.11-r8 > Fri Apr 3 09:23:58 2009 >>> sys-apps/hal-0.5.12_rc1 > Fri Apr 3 09:24:12 2009 >>> app-misc/hal-info-20090330 > > Running 2.6.28-r1 kernel for currently. > > I wasn't sure what to look for in in dmesg but saw nothing that > appeared related. > > There was trouble during the update with glibc. > > When I added --skip-first --keep-going to the command line: > > emerge -vuD --skip-first --keep-going world > > Then the update completed. > > I actually didn't really intend to reboot when I did, I was working on > a different machine and forgot I'd just completed an update so > shutdown by ssh from a remote when I quit for the day. I do know the > update had finished since I did look in on it from time to time. > > On next boot, the problem with hal daemon reported above started.
and you did etc-update/cfg-update after the update? Have you read the messages with elogv? Same hal versions here - no problems at all.
