Your message dated Fri, 27 Mar 2009 15:55:11 +0100
with message-id <49cce8cf.10...@debian.org>
and subject line Re: Bug#521437: Reinstalled Hal, now can't boot.
has caused the Debian Bug report #521437,
regarding Reinstalled Hal, now can't boot.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
521437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hal, bootchart
Version: unknown.
Severity: critical
I ran "sudo aptitude reinstall hal", and as per the command, hal
reinstalled. Followed by some weird messages, which made absolutely no sense
to me, and unfortunately I forgot to copy them...
Anyway, the next couple of reboots worked fine, until I tried to run a
bootchart. I added init=/sbin/bootchartd to the appropiate place in menu.lst
in /boot/grub/ and rebooted (a note, bootchart was running fine before the
hal reinstall) - I can't get past booting now, X, gdm, hal and pretty much
every other package fail to initialize in a massive string of errors most of
which say 'rm: cannot remove ....." (I can't ever see the ...... it scrolls
away too quickly). After everything fails I'm still given a console login,
but the entire system is still in read-only mode (probably why all the rm's
failed).
I can't find any of these messages in any of the log files in /var/log/ and
have no idea what I can to try and fix this - nor do I have any idea which
log I should submit to assist with investigating this. I've run a live USB
install which has allowed me to remove the init=/sbin/bootchartd from grub,
but this makes no difference...
I'm running the debian EEEpc distribution, on an EEE 701 with 4gb SSD.
help?
--- End Message ---
--- Begin Message ---
Cody Christopher wrote:
> Package: hal, bootchart
> Version: unknown.
> Severity: critical
>
> I ran "sudo aptitude reinstall hal", and as per the command, hal
> reinstalled. Followed by some weird messages, which made absolutely no sense
> to me, and unfortunately I forgot to copy them...
>
> Anyway, the next couple of reboots worked fine, until I tried to run a
> bootchart. I added init=/sbin/bootchartd to the appropiate place in menu.lst
> in /boot/grub/ and rebooted (a note, bootchart was running fine before the
> hal reinstall) - I can't get past booting now, X, gdm, hal and pretty much
> every other package fail to initialize in a massive string of errors most of
> which say 'rm: cannot remove ....." (I can't ever see the ...... it scrolls
> away too quickly). After everything fails I'm still given a console login,
> but the entire system is still in read-only mode (probably why all the rm's
> failed).
>
> I can't find any of these messages in any of the log files in /var/log/ and
> have no idea what I can to try and fix this - nor do I have any idea which
> log I should submit to assist with investigating this. I've run a live USB
> install which has allowed me to remove the init=/sbin/bootchartd from grub,
> but this makes no difference...
>
> I'm running the debian EEEpc distribution, on an EEE 701 with 4gb SSD.
Seems to have nothing to do with hal. Maybe when bootchart was installed, your
initramfs was messed up. I can't see, how hal can affect your boot process, when
it start as S24 in rc2, so closing.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
