Chris Walker cdw_alug@the-walker-household.co.uk
It offers a failsafe and another kernel option - 2.6.39 (I think) and the 2.6 option works which is how I'm writing this. But how can I faultfind the main kernel non-starting?
The above doesn't say what distribution is in use, but generally, if it uses grub, press e to edit the command-line, edit the boot lines to try to disable all graphical splash stuff that hides the debugging output and then b to let it boot. When it fails, note any errors or whatever (maybe use a digital camera?) and then those should help you find help on search engines or forums, if it's not obvious (which it often isn't).
Hope that helps,
On 20/12/11 16:54, MJ Ray wrote:
Chris Walkercdw_alug@the-walker-household.co.uk
It offers a failsafe and another kernel option - 2.6.39 (I think) and the 2.6 option works which is how I'm writing this. But how can I faultfind the main kernel non-starting?
The above doesn't say what distribution is in use, but generally, if it uses grub, press e to edit the command-line, edit the boot lines to try to disable all graphical splash stuff that hides the debugging output and then b to let it boot.
It's Mandriva 2011 64 bit.
When it fails, note any errors or whatever (maybe use a digital camera?) and then those should help you find help on search engines or forums, if it's not obvious (which it often isn't).
It's easy enough to note down what happens as nothing happens. It just sits there displaying this message :-
kernel (h1m0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID61c .... nokmsboot logo.nologo quiet resume=UUIDd7728016... splash=silent vga=788
It then displays another couple of lines - but if I go to the working option, that's using kernel 2.6.39.4-4.2-desktop and shows this (taken from a camera shot as you suggested) :-
kernel (hd1,0)/boot/vmlinuz-2.6.39.4-4.2-desktop BOOT_IMAGE=2.6.39.4-4.2-desktop root=UUID61c... nokmsboot logo.nologo quiet resume=UUID47728016.. splash=silent vga=788
It also displays a similar couple of lines (I say similar as I didn't note them down) but then proceeds to boot as normal and the machine works.
If I look at /etc/fstab, I can see that UUID7728016 is /dev/sdb5 (sda is the Windows7 drive with linux on sdb) and UUID61c is sdb1.
Not having anything to compare it to, I have no idea whether that all looks ok. Certainly I can see both of the 2 hard drives on the machine from Dolphin and navigate round them.
Is fstab invoked at that early stage or is there some other configuration I need to check?
Once I have that information, I can hopefully go off and do some searching but at the moment, I don't know where to look and the right questions to search for.
Hope that helps,
Yep. Sure does. Ta.
-
Chris Walker -
MJ Ray