HELP Re-compiled new kernel won't boot ...

Bernard Mentink yellowdog-general@lists.terrasoftsolutions.com
Wed Oct 2 14:43:01 2002


Hi,

I tried "cd-linux root=/devhda14" at the boot: prompt but got this error:
"cd-linux:2,/vmlinux: unable to open file invalid device"

Any help much appreciated.

Cheers,
Bernie.

On Thursday, October 3, 2002, at 02:07  AM, ghannon@cspi.com wrote:

>
> Hi Bernie,
>
>      Try hitting tab as the install CD boots to get the yaboot prompt
> then try
>
>      cd-linux root=/dev/hdaX
>
> or sdaX    where X is your / partition.
>
> That worked on YDL 2.1 and probably still does.   Then you can
> change yaboot.conf and run ybin.   I always (now)  make the
> "safe" option and point it at a copy of the original kernel before
> changing the symlink.
> ( But obviously I've been there and done that! )
>
> Here's a sample yaboot.conf.
>
> # ybin options
> boot=/dev/sda8
> macos=/dev/sda6
> magicboot=/usr/lib/yaboot/ofboot
> delay=10
> defaultos=linux
> enablecdboot
>
> # yaboot options
> init-message="\nWelcome to Yellow Dog Linux\n\n"
> timeout=50
> default=linux-novideo
> partition=7
>
> # yaboot images
> image=/boot/vmlinux
>         label=linux
>         root=/dev/sda7
> #       video=aty128fb:1280x1024@60
>
> image=/boot/vmlinux
>         label=linux-novideo
>         root=/dev/sda7
>         novideo
>
> image=/boot/vmlinux_orig
>         label=safe
>         root=/dev/sda7
>         novideo
>
> image=/boot/vmlinux-2.4.19-pre4
>         label=2_4_19
>         root=/dev/sda7
>
>
> HTH
>
> Gary Hannon
> CSPI
> ghannon@cspi.com
>
>
>
>
>
> Bernard Mentink <ebike@paradise.net.nz> on 10/02/2002 03:00:26 AM
>
> Please respond to yellowdog-general@lists.terrasoftsolutions.com
>
> To:   yellowdog-general@lists.terrasoftsolutions.com
> cc:    (bcc: Gary Hannon/CSP)
> Subject:  HELP Re-compiled new kernel won't boot ...
>
>
>
>
> Hi All,
>
> I have just re-compiled the 2.4.19 kernel as per the insructions on the
> Yellowdog HOWTO page, and now cannot boot
> into linux. (It fail's at ADB mouse at 3,handler set to 4 ...) next
> should be RAMDISK init, it's hanging there I think.
>
> I cannot get back to boot the old kernel (and yes I did keep it in
> boot), however I did not make a seperate entry on yaboot for it.
> Instead, as suggested in the HOWTO, left it as is, as it used the
> vmlinux symbolic link, which is pointing to my new kernel.
>
> I cannot understand the instruction in yaboot to boot an image that is
> not named in the list.
>
> Can anyone help me do that, so I can at least boot the old kernel.
>
> I see there is no option in the install disk to get to a terminal 
> window.
>
> Please help, I miss Linux allready (am typing this in OS X).....
>
> Cheers,
> Bernie.
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
>
>
>
>
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>