Re: restorecd, fdisk problems on cobalt

["Erik Berls" <cyber%netbsd.org@localhost>]

When you say starting, do you mean it says "executing bootloader
kernel..." then hangs, or something else?

fdisk and disklabel partitions match up?

/boot in the linux partition contains the right bits?  <-- this should
get  you to the NetBSD bootstrap prompt.  Realistically, I'd first
worry about getting there then the rest of the disk.

-=erik.


On 1/1/08, Eric Auge <eau%phear.org@localhost> wrote:
> Izumi Tsutsui wrote:
> >> Cobalt: bfd
> >> BOOTLOADER ramcode: selected partition /dev/hda1
> >> Decompressing done
> >> Executing bootloader kernel...
> >> Jump_to_Real_Kernel: disk error, trying BFD again
> >> BOOTLOADER ramcode: selected partition /dev/hdc1
> >> Decompressing - done
> >> Executing bootloader kernel...
> >> Jump_to_Real_Kernel: disk error, trying BFD again
> >> get_root_dev: nr_boot_failures 0x00000002 exceeds maxtries 0x00000002
> >> for boot_index 0x00000000
> >
> > This means the cobalt firmware fails to load a boot file
> > from Linux ext2fs partition, i.e.
> > - no Linux Root partition in MBR
> > - no valid ext2fs partition
> > - no valid boot file (/boot/vmlinux.gz or so)
> > etc.
> >
> >> # fdisk wd0
> >> [1]   Trace/BPT trap          fdisk wd0
> >  :
> >
> > Hmm, I can't test it right now because I've been in my hometown
> > during new year holidays, but I'll see how the problem can be
> > reproduced.
>
> I sent the PR about fdisk including the small fix.
> however the installation went good no more trap, but machine never comes
> up after the installation.
>
> bfd on the bios say it's starting but it stays here without showing
> anything..or may be it does but it does not display a thing...
>
> Any ideas how I can debug that ?!
>
> Thanks,
> Regards,
> Eric.
> > ---
> > Izumi Tsutsui
> >
>
>
>
>


-- 
"Too bad $VOLUNTEERS don't get their act together and provide
$SOLUTION_TO_VERY_DIFFICULT_PROBLEM in a decent fashion"  -- from IRC,
#netbsd, EFNet