[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: IBM RS/6000 B50 problems

Thorsten Sauter said:
> I'm trying to install Debian Stable (or unstable) on a new IBM RS/6000
> B50. But I'm unable to boot any kernel (or the installation system).
> As I know, the Debian boot-floppies doesn't support this hardware type
> directly, so I have create my own floppies:
> 1. downloaded the rescue image, and dd'ed to a floppy (vfat format) [1]
> 2. downloaded the root image, and dd'ed to a floppy (ext2?)         [1]
> 3. replace the kernel image in the rescue floppy with a kernel image,
> which should boot on a rs/6000 [2] (google was my friend here).
> 	mount -t vfat /dev/fd0 /mnt; cp linux.bin /mnt; umount /mnt
> I'm able to boot the kernel with the following kernel arguments from the
> Openfirmware prompt:
>> boot floppy:,\linux.bin root=/dev/fd0 load_ramdisk=1 video=ofonly
> the kernel boots fine, and detect all internet disks, the matrix
> card, and a floppy drive (fd0).
> After two or tree seconds the kernel stops, and display the message,
> that I should insert the next floppy disk (root floppy).
> And here, the problems starts:
> I replace the disk and hit enter. But the kernel *doesn't* try to access
> the floppy drive (or the cdrom-drive), it simply dies with the following
> (well known message :-( ):
> Cannot open root device "fd0" or 02:00
> Rebooting in 180 seconds....
> The RS/6000 status display is now: 7777 (very bad) :-(

Pah.  Not at all, just somebody's misguided coding.  The patch at the
end would make things a bit less confusing for those without a text
LCD display.

I think you need to make a bootable CD using yaboot.  I've heard that
CHRPs don't support loading ramdisks from floppy, although I've no
idea why.



--- arch/ppc/platforms/chrp_setup.c.orig	2003-12-08 10:25:50.000000000 +0000
+++ arch/ppc/platforms/chrp_setup.c	2003-12-08 10:26:04.000000000 +0000
@@ -512,9 +512,6 @@
 	request_region(0x80,0x10,"dma page reg");

-	if (ppc_md.progress)
-		ppc_md.progress("  Have fun!    ", 0x7777);
 #if defined(CONFIG_VT) && (defined(CONFIG_ADB_KEYBOARD) ||
 	/* see if there is a keyboard in the device tree
 	   with a parent of type "adb" */

Reply to: