On Sat, Dec 23, 2000 at 10:12:25PM -0800, Taro Fukunaga wrote: > > the install menus, putting the system on the hard drive. However, on > > reboot the system won't boot up to Debian, giving only the > > "questionmark-mac" display, which I presume means it doesn't know what > > it should be booting. correct, you need to set the boot-device variable in OF. you do this with the nvsetenv command in linux. you should be able to use the hfs-boot.img to boot then use ofpath and nvsetenv to set the correct value for boot-device. you also need to install quik on the hard disk. this is usually done by running the `make bootable from the hard disk' in dbootstrap. > > Many references I've read talk about changing OpenFirmware settings, but > > I am unable to access the OpenFirmware -- hotkey sequences have resulted > > in either no effect, or a black screen, and the Debian rescue disk > > doesn't give me anything in /proc/devicetree (I think that was the this is very odd if you don't have /proc/device-tree/ that will make it quite difficult to find the correct OF device path. (ofpath depends on /proc/device-tree) it sounds like your booting a kernel without CONFIG_PROC_DEVICETREE=y > > path), which surprised some people I spoke to on #debian. > > > > Others have told me I need to fool around in MacOS, but that no longer > > exists on this machine; and I'd like to be proud of the fact that I can > > use the machine with Debian alone, if possible. you can, you just need to use either a serial terminal to access and fix OF, or use the hfs-boot.img floppy to get a shell and use nvsetenv and ofpath to set boot-device. > > Any pointers, or requests for more info, would be appreciated. > > I am running Debian on a PowerCenter 120 as well. I posted to this > mailing list a few days ago but never got replies from the list. I did > however get some replies directly. This mailing list seems to be broken; > even the archives haven't been updated. i don't think this is true, i have recently used the archives and they were functioning. > If you go to www.netbsd.org and go to the website for netbsd/macppc, > you'll find a link to a tool written by Apple to patch OF and set some > input and output settings so that you can access OF on startup. Since > video is broken, I connect a printer cable to my other Mac and start > ZModem on it. Input device I set to ttyb; this lets me type commands on > my other Mac which gets sent to the PowerCenter through the printer > cable. I set output device to /bandit/ATY,XCLAIM3DPro since I have an > XClaim3D video card. This lets me see OF full screen when the monitor > cable is connected to the PowerCenter. You will probably have different > output device settings. There are several hints on NetBSD/macppc website. correct, you can often figure out your video card by looking through /proc/device-tree/ often there is a screen alias you can use. (check /proc/device-tree/aliases) > This is about as far as I've gone. I've compiled the kernel and made an > XCOFF and saved it to a floppy. I've tried 3 floppies so far and none > have worked whe I typed boot fd in OF. Even typing boot fd in OF won't > boot a MacOS boot floppy that works perfectly fine otherwise. did you try boot fd: ? also did you verify fd is the right device alias? use the devalias command to see all aliases. also did you dd the image to the floppy or put it on a msdos or hfs filesystem? if the latter then you need to use a command like this: boot fd:,vmlinux.coff i think anyway, im not as familier with oldworld OF. > All I can say is that I still need to do some hunting in this and other > mailing lists for an answer to how to tell OF too boot from a floppy. there are plenty of messages in the list archives for setting up quik to boot directly from the hard disk. -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgpEVrBTzlOM9.pgp
Description: PGP signature