Re: Call for info: slave drives bootable from OpenFirmware (OldWorld)
> Hi,
>
> Does anyone know what OldWorld machines can boot from slave disks? if
> any, from OpenFirmware only. (i am not interested in miboot/BootX). =20
>
> The reason I am asking is for ofpath, i currently attempt to guess
> OpenFirmware paths to slave disks as well as primary, but if they are
> not bootable perhaps its better to just consider slave devices
> unsupported.
>
> I would appreciate any comments on this, i have no OldWorld hardware
> so ofpath's support for finding OF paths for disk devices is
> completely dependent on what device-trees i can find, and people
> testing it for both accuracy and compatibility. =20
>
> Something else i am interested in is the OpenFirmware configuration
> required to successfully boot with quik on various models. If enough
> machines can be documented I would like to write a tool which will
> identify a particular model and configure its OpenFirmware
> appropriatly. it would act as a wrapper around quik. =20
I can boot my Apple 9500-120 from Open Firmware (v1.05), but i have to use a
terminal to do it. When I change the input and output devices, it doesn't
use them for OF, it still talks only to the serial terminal.
I use the OF boot command
boot scsi/sd@6:0
and that's all I need to do for it to boot. The kernel is actually on
partition 7, but putting anything other than :0 results in a DEFAULT CATCH!.
My quik.conf contains
root=/dev/sdb7
partition=7
image=/boot/vmlinux-2.2.19
I did confirm that using boot: /vmlinux from the Quik second-stage loader
results in an unknown image format error, while using boot:
/boot/vmlinux-2.2.19 works. With the quik.conf above, if I just press return
at the boot: prompt, it works too.
Here's the device tree for my 9500:
0 > dev / ls
FF828F80: /PowerPC,604@0
FF829230: /l2-cache@0,0
FF8299F0: /chosen@0
FF829B20: /memory@0
FF829C68: /openprom@0
FF829D28: /AAPL,ROM@FFC00000
FF829F40: /options@0
FF82A618: /aliases@0
FF82A858: /packages@0
FF82A8E0: /deblocker@0,0
FF82B0E0: /disk-label@0,0
FF82B620: /obp-tftp@0,0
FF82DA60: /mac-files@0,0
FF82E258: /mac-parts@0,0
FF82E9B8: /aix-boot@0,0
FF82EE30: /fat-files@0,0
FF830400: /iso-9660-files@0,0
FF830D48: /xcoff-loader@0,0
FF831708: /terminal-emulator@0,0
FF8317A0: /bandit@F2000000
FF832990: /gc@10
FF832DC8: /53c94@10000
FF834650: /sd@0,0
FF835280: /st@0,0
FF835EF8: /mace@11000
FF836D70: /escc@13000
FF836EC8: /ch-a@13020
FF837578: /ch-b@13000
FF837C28: /awacs@14000
FF837D10: /swim3@15000
FF838E18: /via-cuda@16000
FF8399A8: /adb@0,0
FF839A98: /keyboard@0,0
FF83A1E8: /mouse@1,0
FF83A298: /pram@0,0
FF83A348: /rtc@0,0
FF83A810: /power-mgt@0,0
FF83A930: /mesh@18000
FF83C498: /sd@0,0
FF83D0C8: /st@0,0
FF83DDD0: /nvram@1D000
FF83FB70: /pci106b,1@B
FF83FD48: /ATY,mach64@F
FF83DF68: /bandit@F4000000
FF848330: /pci106b,1@B
FF848508: /FWB,JackHammer@D
FF84B538: /FWB,JackHammer@E
FF83F1C0: /hammerhead@F8000000
ok
For the PowerBase 180 (OF v2.0), I can boot off the same drive as the 9500.
I have another scsi disk connected to the PowerBase, though, but that works
out because it has an IDE internal; so the Linux device alias is still sdb.
The input-device and output-device settings work, unlike the 9500, and I
have them set to kbd and /bandit/ATY,mach64_3D_pcc.
In order to boot from OF, I type boot scsi/sd@6:7
Then in the Quik second-stage loader, /boot/vmlinux-2.2.19.
Here's the device tree and other info for the PowerBase:
0 > dev / ls
FF827B20: /PowerPC,603@0
FF828398: /chosen@0
FF828570: /garytina@0
FF8294D0: /memory@0
FF829618: /openprom@0
FF8296D8: /AAPL,ROM@FFC00000
FF8298F0: /options@0
FF829D90: /aliases@0
FF82A020: /packages@0
FF82A0A8: /deblocker@0,0
FF82A7D0: /disk-label@0,0
FF82AD48: /obp-tftp@0,0
FF82CFB8: /mac-files@0,0
FF82D6C8: /mac-parts@0,0
FF82DE30: /aix-boot@0,0
FF82E280: /fat-files@0,0
FF82F898: /iso-9660-files@0,0
FF830200: /xcoff-loader@0,0
FF830AB8: /terminal-emulator@0,0
FF830B50: /bandit@F2000000
FF831E38: /ohare@10
FF832278: /mesh@10000
FF833EA8: /sd@0,0
FF834A30: /st@0,0
FF8356A8: /escc@13000
FF835800: /ch-a@13020
FF835E40: /ch-b@13000
FF836480: /awacs@14000
FF836568: /swim3@15000
FF837690: /nvram@60000
FF837760: /via-cuda@16000
FF8382F0: /adb@0,0
FF8383E0: /keyboard@0,0
FF838C08: /mouse@1,0
FF838EC8: /pram@0,0
FF838F78: /rtc@0,0
FF839418: /power-mgt@0,0
FF8394D8: /ATA@20000
FF83A798: /ATA-Disk@0,0
FF83BE90: /pci106b,1@B
FF83C068: /pci10ec,8139@F
FF83C388: /ATY,mach64_3D_pcc@11
ok
0 >0 > devalias
pci1 /bandit@F2000000
fd /bandit/ohare/swim3
kbd /bandit/ohare/via-cuda/adb/keyboard
mouse /bandit/ohare/via-cuda/adb/mouse
ttya /bandit/ohare/escc/ch-a
ttyb /bandit/ohare/escc/ch-b
scsi /bandit/ohare/mesh
scsi-int /bandit/ohare/mesh
ata /bandit/ohare/ATA
ata-int /bandit/ohare/ATA
screen /valkyrie
ok
0 > printenv
little-endian? false false
real-mode? false false
auto-boot? true true
diag-switch? false false
fcode-debug? false false
oem-banner? false false
oem-logo? false false
use-nvramrc? false false
real-base -1 -1
real-size 100000 100000
virt-base -1 -1
virt-size 100000 100000
load-base 4000 4000
pci-probe-list -1 -1
screen-#columns 64 64
screen-#rows 28 28
selftest-#megs 0 0
boot-device /AAPL,ROM /AAPL,ROM
boot-file
diag-device fd:diags fd:diags
diag-file
input-device kbd ttya
output-device /bandit/ATY,mach64_3D_pcc ttya
oem-banner
oem-logo
nvramrc
boot-command boot boot
--
Chris Tillman
tillman@azstarnet.com
Reply to: