Hi Jörg, I'm using version 0.10~svn407-3.
Yes, I use an initrd, currently my boot option is "initrd /boot/initrd.img-2.6.26-1-686" /bin/sh points to bash (which is odd because I have told it to install dash as /bin/sh multiple times). echo $SHELL returns bash. starting the kernel with init=/sbin/init seems to have no effect. I'm no longer getting the error messages with regards to the rm commands, rather, everything up until the machine goes to activate swap is fine, after that I get: * Activating swap... return: 24: Illegal number: Activating *Starting early crypto disks... return: 24: Illegal number: Activating and so and so forth with that same return statement for everything (ifupdown, kernerl modules, remaining crypto) slighly modified for what was just tried (that is, Illegal number: Cleaning for *Cleaning up ifupdown). So it doesn't look like a bootchart problem anymore. Slightly later on in the boot I get: *Starting OpenBSD Secure Shell server sshd return: 24: Illegal number: Starting + PATH= (code omitted) + DEAMON= + PIDDIR= // etc.... // until *Can't start Hardware abstraction layer - please ensure dbus is running // (why I logged this is a potentially involving hal as well) + exit 0 *Starting.... //(back to what I had before for avahi, dhcdbd, wicd and gdm) then i can finally log into the shell. In conclusion; I have no idea whatsoever is now wrong with this machine... Cheers, Cody On Sun, Apr 5, 2009 at 9:31 PM, Jörg Sommer <jo...@alea.gnuu.de> wrote: > reassign 521437 bootchart > reopen 521437 > stop > > Hello Cody, > > Cody Christopher hat am Sat 28. Mar, 01:46 (+1100) geschrieben: > > Package: hal, bootchart > > Version: unknown. > > Severity: critical > > > > 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 ....." > > This sound like bootchart. > > > (I can't ever see the ...... it scrolls away too quickly). > > You can press Ctrl+s to stop the messages and Ctrl+q to reenable them. > > Which version of bootchart do you use? > > Do you use an initrd? > > What's your shell, i.e. where points the link /bin/sh to? > > > 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, > > Doesn't grub allow you to give the init command at the promt, i.e. > start the kernel with init=/sbin/init? > > > but this makes no difference... > > So, that's not a problem of bootchart. If you disable bootchart and > still have problems, it might something else that causes your problems. > But let's see. > > Bye, Jörg. > -- > Der Wunsch, klug zu erscheinen, verhindert oft, es zu werden. > (Francois de la Rochefoucauld) > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAknYlqMACgkQwe0mZwH1VIAoqgCfW4y0kWubk7Bw75ClBpl7rLI8 > +DgAmwVP4ZKMoeSFpJMvItkjZhIruMxQ > =8UdB > -----END PGP SIGNATURE----- > > -- "History Abhors A Paradox"
