Skip to contentSkip to conversation

booting with quik off hard disk on 7220

DISCUSSION Steven Hanley 2 participants 4 messages Nov 11, 2000

lore
Share & tools
lore
#0 lore raw

All

well I got past the problem with the video mode thanks to ethan benson's suggestions of using a hex editor to set vmode.

Anyway the problem I now have is that I cant get the machine to boot off hard disk with quik. (BootX worked when I used the machine with macos and ydl, however I wanted to get rid of macos now I have debian)

I have the quik.conf
partition=6
root=/dev/hda6
timeout=1
image=/boot/vmlinux-2.2.17
label=linux
read-only
append="video=atyfb:vmode:6"

the only real change from the quik.conf deb install generated is I added the append line and I changed the image to point to /boot/vmlinux-2/2/17 rather than /vmlinux as I read in a post ethan benson wrote to debian-powerpc (in the archive somewhere) saying that symlinks are not reliable with quik on these computers.

I have got a debian base install on the machine now but cant continue with the install as I am still booting off the hfs debian boot floppy and root floppy.

So I have a file I run when i boot off floppy that does some nvsetenv stuff this is
nvsetenv boot-device ata/ata-disk@0:0
nvsetenv input-device kbd
nvsetenv output-device screen
nvsetenv boot-file ' /boot/vmlinux-2.2.17 root=/dev/hda6'
quik

the boot device seems to be correct, although that ofpath script when I run ./ofpath /dev/hda reports "This machine is not suhpported: AAPL,e826" I looked through /proc/device-tree myself and the ata and ata-disk things are there where it seems they should be.

I dont get output from OF on this machine when I enter OF at bootup (7200 dont get OF display or something) but if I dont set the input and output device I dont see anything from quik, when they are set I see the grey screen for the quik second stage loader.

If I dont have the boot-file set quik asks me every time to enter the boot-file argument. I have the space infront of /boot as I read in some post to debian-powerpc that the 7200 series needed the space there.

the partition map for the machine has hda[1234] as the apple partitions for drivers and such. Then it has Swap on hda5
/dev/hda5 Apple_UNIX_SVR2 Swap 262144 @ 704 (128.0M) Linux Swap and / on hda6
/dev/hda6 Apple_UNIX_SVR2 Linux_Root 2097152 @ 262848 ( 1.0G) Linux Native

and then some free space after that.

Now when I boot up I get the quik second stage loader and it has a spinning | / - \ thing briefly and then the screen goes entirely blank wnad there is no hard disk activity or anything.

I am wondering how to get the machine to boot.

I have seen in many places mentions of the 7200 with scsi not spinning the disks up fast enough for booting and the quik boot fails, so there are small scripts to make it wait around on maling lists, however I have seen mention of the fact this only affects scsi and that ide doesnt have the slow spin up problem. So for now I have discounted that as being the cause.

I am guessing I may need to get a serial cable link up to have a look and play around in OF to get this running. (unless someone can tell me how to get it running with out this) Though it would be good to be able to see OF I suppose and thus I am wondering what cables I need to hook up the little round modem or printer port on the back of the machine to an x86 box, I have a null modem cable and all, but not something that will speak to the little modem or printer ports on the mac. I saw the details in some list post yesterday arvo but didnt make a note of it and now cant find that post again searching for likely keywords on google.

I am using google a lot more than the new search capability on debian mailing lists it seems as the debian mailing list searcher seems to return no matches more often than not for most searches. And yet I find those same things often when reading through the debian powerpc archives manually. Alas...

Thanks

See You
Steve

--
[email protected] http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#1 lore raw
Quoted 9 lines · Steven Hanley

I have the quik.conf
partition=6
root=/dev/hda6
timeout=1
image=/boot/vmlinux-2.2.17
label=linux
read-only
append="video=atyfb:vmode:6"

looks ok, though i think it would be easier to read if you format it with the indented image section:

partition=6
root=/dev/hda6
timeout=10

image=/boot/vmlinux-2.2.17
label=linux
read-only
append="video=atyfb:vmode:6"

but then im just a nitpicker ;-)

btw i think you want timeout=10 not 1, that is in tenths of seconds.

Quoted 3 lines

So I have a file I run when i boot off floppy that does some nvsetenv stuff this is
nvsetenv boot-device ata/ata-disk@0:0

should be close..

Quoted 2 lines

nvsetenv input-device kbd
nvsetenv output-device screen

this may or may not do you any good if your machine lacks a OF video driver.

Quoted 1 line

nvsetenv boot-file ' /boot/vmlinux-2.2.17 root=/dev/hda6'

this is redunant, when you have a proper quik.conf you don't need the boot-file variable, in fact it seems to bork things up in my experience helping someone with a 7200. i would null out the boot-file variable.

Quoted 6 lines

quik

the boot device seems to be correct, although that ofpath script when I run ./ofpath /dev/hda reports "This machine is not suhpported: AAPL,e826" I looked through /proc/device-tree myself and the ata and ata-disk things are there where it seems they should be.

yeah that is basically what ofpath does, would it be possible for you to give me temporary shell access so i could add support to ofpath for it? if not i can ask you some questions and figure it out. more then likely its exactly the same as a 7200 or a 7300 but has a different compatible entry.

Quoted 4 lines

I dont get output from OF on this machine when I enter OF at bootup (7200 dont get OF display or something) but if I dont set the input and output device I dont see anything from quik, when they are set I see the grey screen for the quik second stage loader.

hmm im not sure i understand this...

Quoted 3 lines

If I dont have the boot-file set quik asks me every time to enter the boot-file argument. I have the space infront of /boot as I read in some post to debian-powerpc that the 7200 series needed the space there.

really? i have a friend booting a 7200 with no boot-file variable set and it boots just fine. boot-file overrides /etc/quik.conf iirc.

Quoted 2 lines

the partition map for the machine has hda[1234] as the apple partitions for drivers and such. Then it has Swap on hda5

just a note you don't need all that driver crap with quik booting.

Quoted 3 lines

/dev/hda5 Apple_UNIX_SVR2 Swap 262144 @ 704 (128.0M) Linux Swap and / on hda6
/dev/hda6 Apple_UNIX_SVR2 Linux_Root 2097152 @ 262848 ( 1.0G) Linux Native

its better to name these swap' and root' respectivly as that is what the kernel actually looks for, but if you specify root= in quik.conf it doesn't really matter.

Quoted 5 lines

and then some free space after that.

Now when I boot up I get the quik second stage loader and it has a spinning | / - \ thing briefly and then the screen goes entirely blank wnad there is no hard disk activity or anything.

ah it sounds like its loading the kernel but the kernel is hanging. that is how my friends 7200 always failed with 2.2.15/16 kernels.

Quoted 7 lines

I am wondering how to get the machine to boot.

I have seen in many places mentions of the 7200 with scsi not spinning the disks up fast enough for booting and the quik boot fails, so there are small scripts to make it wait around on maling lists, however I have seen mention of the fact this only affects scsi and that ide doesnt have the slow spin up problem. So for now I have discounted that as being the cause.

yeah the spinup problem usually results in quik barfing with DEFAULT CACHE type errors.

Quoted 9 lines

I am guessing I may need to get a serial cable link up to have a look and play around in OF to get this running. (unless someone can tell me how to get it running with out this) Though it would be good to be able to see OF I suppose and thus I am wondering what cables I need to hook up the little round modem or printer port on the back of the machine to an x86 box, I have a null modem cable and all, but not something that will speak to the little modem or printer ports on the mac. I saw the details in some list post yesterday arvo but didnt make a note of it and now cant find that post again searching for likely keywords on google.

i think you just need an ordinary mac serial cable, like you use for printers and such, then use a comm program like minicom or Zterm if your stuck with MacOS on the other box.

Signature · 2 lines
Ethan Benson
http://www.alaska.net/~erbenson/
#2 lore raw
Quoted 6 lines · Ethan Benson
Quoted 1 line

nvsetenv boot-file ' /boot/vmlinux-2.2.17 root=/dev/hda6'

this is redunant, when you have a proper quik.conf you don't need the boot-file variable, in fact it seems to bork things up in my experience helping someone with a 7200. i would null out the boot-file variable.

hmm so what should be in quik.conf instead? With my current quik.conf if I dont have that variable set quik stops on the grey screen where the boot:
prompt is and asks me to enter a [device:][partno]/path which if I enter device and boot-file vairable settings in will then boot into the blank screen with no hard disk activity just like it does now.

Quoted 7 lines
Quoted 6 lines

quik

the boot device seems to be correct, although that ofpath script when I run ./ofpath /dev/hda reports "This machine is not suhpported: AAPL,e826" I looked through /proc/device-tree myself and the ata and ata-disk things are there where it seems they should be.

Quoted 5 lines

yeah that is basically what ofpath does, would it be possible for you to give me temporary shell access so i could add support to ofpath for it? if not i can ask you some questions and figure it out. more then likely its exactly the same as a 7200 or a 7300 but has a different compatible entry.

yeah happy to give you shell access to the machine as soon as I have debian installed and working, I can take the computer and put it online somewhere for a while.

Quoted 6 lines
Quoted 4 lines

I dont get output from OF on this machine when I enter OF at bootup (7200 dont get OF display or something) but if I dont set the input and output device I dont see anything from quik, when they are set I see the grey screen for the quik second stage loader.

hmm im not sure i understand this...

oh well the grey screen with the second stage boot loader and the
boot: prompt for quik, this doesnt show up unless I set the output device, the computer on power on or reboot without setting theoutput device after I have done a command option p r just sits there with a black screen and no disk activity (kind of like I am either in OF or have gotten past the quik
boot: prompt and have that blank screen there.)

Quoted 11 lines
Quoted 3 lines

If I dont have the boot-file set quik asks me every time to enter the boot-file argument. I have the space infront of /boot as I read in some post to debian-powerpc that the 7200 series needed the space there.

really? i have a friend booting a 7200 with no boot-file variable set and it boots just fine. boot-file overrides /etc/quik.conf iirc.

Quoted 2 lines

the partition map for the machine has hda[1234] as the apple partitions for drivers and such. Then it has Swap on hda5

just a note you don't need all that driver crap with quik booting.

oh good, when I still had macos on the machine I thought it was probably safer to leave it there, but now I dnt need bootx I wont need them anymore either it seems :)

Quoted 7 lines
Quoted 3 lines

/dev/hda5 Apple_UNIX_SVR2 Swap 262144 @ 704 (128.0M) Linux Swap and / on hda6
/dev/hda6 Apple_UNIX_SVR2 Linux_Root 2097152 @ 262848 ( 1.0G) Linux Native

its better to name these swap' and root' respectivly as that is what the kernel actually looks for, but if you specify root= in quik.conf it doesn't really matter.

hmm okay well I shall try changing them anyway as there could be some need for them to be set if quik is not interacting as well as it should with this machine.

Quoted 6 lines
Quoted 3 lines

Now when I boot up I get the quik second stage loader and it has a spinning | / - \ thing briefly and then the screen goes entirely blank wnad there is no hard disk activity or anything.

ah it sounds like its loading the kernel but the kernel is hanging. that is how my friends 7200 always failed with 2.2.15/16 kernels.

hmm, okay well I just tried a 2.2.18pre18 kernel I had compiled (that worked on the machine with bootx) rsynced from paulus' stable tree a few days ago and it also gave me a black screen and no disk activity.

I will try to track down a tarball of 2.2.10 (I believe there is still one on ftp.linuxcare.com.au) and try it next and home it works. Will also try the changing of the partition labels to swap and root.

Quoted 3 lines

i think you just need an ordinary mac serial cable, like you use for printers and such, then use a comm program like minicom or Zterm if your stuck with MacOS on the other box.

hmm I dont have another mac around, I am wondering what sort of cables I have to go to a cable place and ask for to have one I can hook up to a null modem cable or something and speak to minicom on an x86 box.

Thanks

See You
Steve

--
[email protected] http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#3 lore raw
Quoted 8 lines · Steven Hanley
Quoted 6 lines · Ethan Benson
Quoted 1 line

nvsetenv boot-file ' /boot/vmlinux-2.2.17 root=/dev/hda6'

this is redunant, when you have a proper quik.conf you don't need the boot-file variable, in fact it seems to bork things up in my experience helping someone with a 7200. i would null out the boot-file variable.

Quoted 5 lines

hmm so what should be in quik.conf instead? With my current quik.conf if I dont have that variable set quik stops on the grey screen where the boot:
prompt is and asks me to enter a [device:][partno]/path which if I enter device and boot-file vairable settings in will then boot into the blank screen with no hard disk activity just like it does now.

odd that doesn't happen on my friend's 7200, maybe try adding device= to quik.conf with the correct OF device (but not the image name)

device=ata/ata@0:0 or something like that.

Quoted 3 lines

yeah happy to give you shell access to the machine as soon as I have debian installed and working, I can take the computer and put it online somewhere for a while.

cool, let me know when you have time.

Quoted 6 lines

oh well the grey screen with the second stage boot loader and the
boot: prompt for quik, this doesnt show up unless I set the output device, the computer on power on or reboot without setting theoutput device after I have done a command option p r just sits there with a black screen and no disk activity (kind of like I am either in OF or have gotten past the quik
boot: prompt and have that blank screen there.)

ah i see, interesting, sounds like quik has its own minimal video driver, this way OF itself won't show up since it has no driver, but quik will since it has its own. nifty.

Quoted 3 lines

oh good, when I still had macos on the machine I thought it was probably safer to leave it there, but now I dnt need bootx I wont need them anymore either it seems :)

yup ;)

Quoted 3 lines

hmm, okay well I just tried a 2.2.18pre18 kernel I had compiled (that worked on the machine with bootx) rsynced from paulus' stable tree a few days ago and it also gave me a black screen and no disk activity.

a serial terminal might help here, some OpenFirmware messages are usually printed but you can't see them unless you have serial term. whether they are helpful or not i don't know. a kernel hacker could help you better there.

Quoted 3 lines

I will try to track down a tarball of 2.2.10 (I believe there is still one on ftp.linuxcare.com.au) and try it next and home it works. Will also try the changing of the partition labels to swap and root.

try a 2.2.14 too. though 2.2.17 was the first since .14 that worked fine on my friend's 7200.

Quoted 3 lines

hmm I dont have another mac around, I am wondering what sort of cables I have to go to a cable place and ask for to have one I can hook up to a null modem cable or something and speak to minicom on an x86 box.

i think mac serial ports are identical to x86 serial ports, they just use a different type of plug, i think there are converters for mac->standard

Signature · 2 lines
Ethan Benson
http://www.alaska.net/~erbenson/