The original question:
I raise is because I brought an old U5 box, and noticed the box use a
standard IDE slot, so the only HDD I installed (ATA66) could not perform
maximum. Thus, I installed another Promise PDC 20262 IDE expension (or
extending, I am not sure of the English) card and moved the HDD to that
The problem is, as later pointed out by Keith M Wesolowski, U5 OBP could
not boot from external IDE device. This way I need to find a way to boot
up the box. Ferris McCormick helped me a lot in finding where is the
problem with his professional skill.
The final way to solve the problem: I installed a small HDD onto the IDE
slot on the mother board, installed SILO on it, let it boot up the OS
installed on the external IDE slot.
I tried to boot from floppy and failed. Here is how I failed in every
> After lots of work to shink kernel down to 1.2MB and teste the kernel
> is bootable, according to silo(1), these steps should create bootable
> genromfs -d directory/ -f device -a 512 -A 2048,/..
> mount -t romfs device mountpoint
> silo -r mountpoint -i /boot/fd.b -F
> umount mountpoint
> This is what I did: (the first fdisk operation is not necessary
> according to my knowledge, but I did it just to make sure)
> root # fdisk /dev/fd0
> Command (m for help): s
> Building a new sun disklabel. Changes will remain in memory only,
> until you decide to write them. After that, of course, the previous
> content won't be recoverable.
> Command (m for help): w
> The partition table has been altered!
> Calling ioctl() to re-read partition table.
> WARNING: Re-reading the partition table failed with error 22: Invalid
> The kernel still uses the old table.
> The new table will be used at the next reboot.
> Syncing disks.
> root # genromfs -d /boot/ -f /dev/fd0 -a 512 -A 2048,/..
> root # mount -t romfs /dev/fd0 /boot
> root # silo -r /boot -i /boot/fd.b -F
> silo.conf seems to be valid
> root # umount /boot
> And start the computer:
> [Enter OBP]
> ok boot floppy
> Boot device: /pci@1f,0/pci@1,1/ebus@1/fdthree File and args:
> Bad magic number in disk label
> Can't open disk label package
> Can't open boot device
> I created a sparc boot floppy image using dd(1) with the image I got
> This image, said should be able to boot, still produce the above error
> in OBP. I also googled around, lots of people are asking the same
> question (why cannot boot from floppy) and given no satisfying answer.
> Perhaps this is an UltraSparc natual problem.
email@example.com mailing list