Well, blacklisting Bluetooth didn’t work. Bootup still falls down at *Starting Bluetooth services.
Aldeby (see comments in previous post) doubted that Bluetooth was the culprit, and it appears that he’s right.
The good news is that wireless worked out of the box, again as Aldeby predicted, so I’m inclined to listen to him!
The bad news is that Gutsy didn’t recognise my external usb hard disk, and froze after a while, probably because of that. The other bad news is that there is no logout icon on the logoff menu.
So I’m rapidly coming to the conclusion that Adleby was right about the faulty disc, too. The only trouble is I’ve tried that several times now. I can only hope with the experience gleaned so far that I won’t make as many mistakes next time.
But can you make a clean install without wiping out the grub menu?
Update: it’s the simple things that an experienced user takes for granted that can flummox a new user or even someone who’s a linux user but hasn’t had to deal with the term before. Here’s a simple explanation of clean install.
Philip,
startx is a way to invoke the GUI, however that isn’t the standard way. If you invoke the GUI via startx you probably are in Runlevel 1 (you selected fail safe / recovery from GRUB menu didn’t you?).
In this case you are already logged in, that’s why the logout menu does not prompt you with the logout button. To log out you have to terminate the X server by CTRL+ALT+BACKSPACE.
Anyway as I wrote you that isn’t the standard way, no surprise if you cannot access a whole bunch of features such as the automounting of external devices. Runlevel 1 is only for fail safe/maintenance purposes, thus it is just a minimal system.
You better try typing “sudo telinit 5″ after you have logged in via the fail safe/recovery. This command tells Linux to switch to Runlevel 5 which is the features full normal multiuser graphical one. The GUI should start automatically and prompt you with the login screen.
It should, but since your system normally crashes with standard boot maybe a faulty service invoked by Runlevel 5 will prevent it from reaching the target.
If so first try with “sudo telinit 3″ which is the full functional multiuser shell only level. Than we will have a look to Runlevel 3 to 5 only scripts.
Please, try also function key F8, I missed to mention it before, but it is indeed a working terminal during the bootup sequence.
You should switch between the consolles via ALT+Fn after your system has stuck during normal boot sequence.
Once I had problems with the shutdown sequence and only thanks to this trick I managed to figure out that it was the wireless driver that prevented me to shutdown cleanly.
Also I would ask you to attach /var/log/syslog /var/log/bootlog and dmesg.txt output from “dmesg > dmesg.txt” this AFTER trying to switch to runlevel 5 or trying to do a normal boot.
Philip,
notice that removing all hidden directories threatens your bookmarks and emails (.mozilla .evolution etc) which are harmless to the system.
I would instead suggest you to create another user so that the new home directory will be freshly populated automatically by linux, then you would be able to import (also by simply copying and pasting) the data you need from the old directory.
Uhm Philip,
We have to make sure 2 things actually work as expected since you experience also random freezes:
1) your RAM memory is not faulty.
At the boot menu select Memtest 86 and leave it testing your memory for a few hours (at least until it has ended the first cycle of tests).
2) you have good setup CDs.
Do a whole media check via the boot menu utility. It should say there are no problems, if not you have to work out this issue first by ensuring to have checked your RAM memory with memtest86 and the MD5 of the image you downloaded and burn it with a brand new medium.
You could also try downloading the Alternate CD and at the boot menu select System Recovery and then the Automatic Recovery (there should be something that sounds like this… I’m sorry but I don’t remember exactly its name)
Philip,
Did you solve the Bluetooth “hang” issue when booting? I’m seeing the exact same issue with my dv9000t.
If you solved it can you give me any tips / clues?
thanks,
Eric
I have a new dv9700z. Seeing the exact same problem. Seems as if HP and Ubuntu do not agree. Anyone find a solution?
[...] this subject, as promised on December 15. If you’ve read my previous entry on this subject, Starting Bluetooth Services: Gutsy bootup problem from December 4, you’ll have read that my attempts to blacklist Bluetooth [...]