Re: About yabootconfig
uh-oh.. :) sorry to hear about the recurring kernel problems - i've been
there many times before. i use yaboot on two new-world machines
(powerbook g3 pismo and lombard), and have had to boot using the yaboot
method a couple of times. your syntax looks fine to me, perhaps the
problem is in the partition number? you might try booting from your
debian install cd and looking at the partition table from the installer
to work out the correct number, then retry at the yaboot prompt? or
perhaps try hd:14,/vmlinux instead of the /boot/vmlinux-2.4.18 option?
the best way to avoid getting stuck is to keep a working entry in your
yaboot.conf that points to your old kernel. so you have the new kernel,
installed in /boot with a symlink from /vmlinux. then just add an entry
in yaboot like this:
image=/boot/vmlinux-old
label=linux-old
append="(whatever options you need for your kernel"
then rerun ybin as root to install the new bootloader. then if your new
kernel fails you should be able to type 'linux-old' at the prompt and
get back into linux on your old kernel.
does that help?
best,
nick
> Hi Nick,
> last night I did it again... :-)
>
> due to a bad kernel I lost control of my linuxbox after start and had
> to force a reboot as the system had frozen solid.
> Problem I couldn't see my ext2 partition from OSX so that possibility
> wasn't there anymore. I had however noted down the exact path to my
> working kernel (which, btw, is spelled vmlinux-2.4.18) and have tried
> to start from yaboot.
> Unfortunately that didn't work either as something along the path was
> wrong and couldn't boot from hd:14,/boot/vmlinux-2.4.18 which is my
> working kernel and relevant path.
>
> Any idea about the syntax? I have double checked the yaboot instruction
> and also tried ending the path with a, (comma) or no comma at the end.
>
> I found a usefull workaround to this situation by booting the debian
> installer cd and after monting the linux partition on /target I
> switched console and was able to cancel the symlink to the bad kernel
> and restore the old one.
> This worked flawlessy (very clever isn't it?? :-)) but there must be a
> better way....
>
> As for the ext2 possibility on the mac in OSX if you (or anybody else)
> are interested you can find it here:
> https://sourceforge.net/projects/ext2fsx/
>
> There still are some bugs but it works well
>
> Cheers
>
> Pieterjan
>
>
Reply to: