Re: Kernel 2.4.18-powerpc using BooxX
Does anybody know what I'm doing wrong?
Yup! At least I think I may, since I had the exact problem on a 7500 an
got it fixed. You most probably need to work with the settings in the
open firmware (OF) and in quik.config.
However, getting your 6500 to do exactly what you want is not straight
forward. Try some of this of you like:
1) Boot the 6500 into Mac OS. If you can't, zap the PRAM (boot
<control-command-powerkey> then press <option-command-p-r> until you
here the second chime).
2) Now try to Boot into your original (or working) Linux, with BootX.
The 2.2 Kernel is fine. If that won't work, you can do the changes in
the next steps from Mac OS with BootVars (get that over
http://penguinppc.org/projects/quik/)
3) When in Linux, have a look at the nvsetenv values (and read the
nvsetenv man page!). You will have to change some of them. I'll make a
good (?) guess at the "correct" values, but depending on the device
tree of your 6500 I may be off.
Set your box up to boot into OF, so you can preserve and debug changes
nvsetenv auto-boot? false
nvsetenv input-device kbd
nvsetenv output-device /bandit/ATY,264GT-B
You may also need to change the load base (see
http://penguinppc.org/projects/quik/quirks.shtml). If so, then
nvsetenc load-base 0x100000
should do the trick. I just don't know if you need to?!?
Typing 'bye' at the OF prompt will boot you into Mac OS, overwriting
your changes, so don't for now. Type 'boot' will try to boot whatever
default was set by quik.
4) Now have a look at the file /etc/quik.conf. If you never executed
quikconfig, then this should still show you the right values. It should
look something like this:
## This file is generated during installation
## Debian GNU/Linux PowerPC (or similar)
init-message=" (some text) "
default=Linux
timeout=100
root=/dev/sda3 (since you're booting from an IDE HHD will differ!)
partition=3
## Do not point image= to symlink, quik can't follow symlinks
image=/boot/vmlinux-2.2.20-pmac (again this may differ)
label=Linux
read-only
If it looks very different then quikconfig was probably executed. (This
killed me - I think - since it set image=/boot/vmlinux, which didn't
exsist, thus stalling the boot with a black screen.) In either case the
values for root= and partition= should be right, even if commented out
with #.
I suggest you edit /etc/quik.conf to look like the what the installer
wrote (you can skip the comments ##)
-Leave root= and partition= at your preset values.
-Put your own text into (some text).
-Change image= to the kernel you want e.g.
image=/boot/vmlinux-2.4.18-powerpc
or add
image=/boot/vmlinux-2.4.18-powerpc (kernel you want)
label=Debian (or what you like)
read-only
-Maybe change default= to your new label e.g. default=Debian
execute quik -v
ALMOST DONE....
This should do the trick, at least until the next boot into Mac OS :(
6) Rebooting will get you into OF. You should get an OF prompt, and
some text telling you to type 'bye' or 'boot'. Don't yet!
Type 'devalias' <return>, and try to see what device your IDE HHD is in
OF syntax. Write it down (!) you'll need it. The internal SCSI on a
7500 is /bandit/gc/mesh for example.
Next type 'dev / ls' to look at the complete device tree and find your
IDE HHD. Again, on the 7500 the first internal SCSSI HHD lists as
/bandit/gc/mesh/sd@0,0. Write it down.
7) Ready? Type 'boot'. You should get your init-message. Type 'Linux',
'Debian' or wait for the default to boot....
You should be where you wanted to got ;)
5) Last thoughts. If it worked - GREAT! The only problem is booting
into Mac OS without it overwriting all your changes in the OF. Seems
that can't be done :(
To boot into Linux form Mac OS I'd use BootVars (not BootX) to set the
boot-device to what you determined in step 6). But be careful to
replace the ',' with a ':' i.e. in my case.
/bandit/gc/mesh/sd@0:0 and NOT /bandit/gc/mesh/sd0,0
Using the devalias instead, like BootVar suggests, may work e.g.
scsi-int/sd@0:0
but I think the ata syntax in the documentation is for onboard ata
only. How is your IDE HDD conencted, PCI?
Also you must change the default output-device, input-device,
auto-boot? and maybe load-base values every time, if you want to boot
into OF....
Good luck, let me know if it works :)
Christian
Reply to: