Hi, I'm having problems setting up yaboot for dual-booting. The generate_os_chooser script on CD 1 doesn't seem to work, it set up my partitions as ultra0:X (which designates a slave drive) when they should've been hd:X. I fixed this, but it still doesn't work right. My machine boots into yaboot if the space bar isn't pressed at startup, but the keyboard doesn't work. Pressing space at startup has no affect (should boot into Mac OS, but still boots into yaboot). My machine is a rev A iMac with a 14.5 gig hard drive partitioned as follows: 2.5 gig, hfs+, hda6 (Mac OS) 50 meg, hfs, hda7 (linux boot) 128 meg, swap, hda8 (linux swap) 2 gig, ext2, hda9 (linux root) 10 gig, hfs, hda10 (mp3 :) My os-chooser <BOOT-SCRIPT> part looks like this: <BOOT-SCRIPT> " get-key-map" " keyboard" open-dev $call-method dup 20 dump 5 + c@ 08 = if " Booting MacOS ..." cr " boot hd:6,\\:tbxi" eval else " Booting Yaboot ..." cr " boot hd:7,\\yaboot" eval then </BOOT-SCRIPT> Any help with this would be great, --Rasmus
Hi there, This is a very quiet list so here is my setup. 1. If you want MacOS to boot first, you will have to adjust yaboot to 5 + c@ 08 = if " Booting Yaboot ..." cr " boot hd:7,\\yaboot" eval else " Booting MacOS ..." cr " boot hd:6,\\:tbxi" eval then After that, did you run 'mark os-chooser bootable' in the tools folder. This makes os-chooser a bootable resource. Try setting it ot MacOS default and then starting yaboot by holding down the space bar. If the boot prompt comes up hit the tab key to get the bootable options. Then start changing os-chooser around. On top of that, the Manula is a bit misle4ading. ALL system resources appear to HAVE to be at the top level of the Linux Boot partition - ie not in the suseboot folder. So system, finder os-chooser, ramdisk.image.gz,vmlinux,yaboot, yaboot.conf and the tools folder at the top level. This works for me on a PowerBook G3 500 which is just a bloated iMac. As for the partition names, yes I tried lots but hd:10,... works fine. in yaboot,conf use hdx,/boot/vmlinuxname Regards, Bruce, Melbourne Australia mailto:bruce@toorak.com
Hi,
I'm having problems setting up yaboot for dual-booting. The generate_os_chooser script on CD 1 doesn't seem to work, it set up my partitions as ultra0:X (which designates a slave drive) when they should've been hd:X. I fixed this, but it still doesn't work right. My machine boots into yaboot if the space bar isn't pressed at startup, but the keyboard doesn't work. Pressing space at startup has no affect (should boot into Mac OS, but still boots into yaboot). My machine is a rev A iMac with a 14.5 gig hard drive partitioned as follows:
2.5 gig, hfs+, hda6 (Mac OS) 50 meg, hfs, hda7 (linux boot) 128 meg, swap, hda8 (linux swap) 2 gig, ext2, hda9 (linux root) 10 gig, hfs, hda10 (mp3 :)
My os-chooser <BOOT-SCRIPT> part looks like this:
<BOOT-SCRIPT> " get-key-map" " keyboard" open-dev $call-method dup 20 dump 5 + c@ 08 = if " Booting MacOS ..." cr " boot hd:6,\\:tbxi" eval else " Booting Yaboot ..." cr " boot hd:7,\\yaboot" eval then </BOOT-SCRIPT>
Any help with this would be great,
--Rasmus
Thanks for responding Bruce. Running the generate_os_chooser script marks os-chooser as bootable. I tried switching the boot script lines, but this only affects which os is booted when space isn't held down at startup. Pressing space still doesn't boot into the other os. I also tried moving all the files from suseboot to the top level of the boot partition, but this had no perceivable effect. I'm not sure I understand your last suggestion, though. Do you refer to the image = vmlinux part, and that it should be changed to image = hd:7,/boot/vmlinux for the linux label. Regards, --Rasmus
Hi there, This is a very quiet list so here is my setup. 1. If you want MacOS to boot first, you will have to adjust yaboot to
5 + c@ 08 = if " Booting Yaboot ..." cr " boot hd:7,\\yaboot" eval else " Booting MacOS ..." cr " boot hd:6,\\:tbxi" eval then
After that, did you run 'mark os-chooser bootable' in the tools folder. This makes os-chooser a bootable resource.
Try setting it ot MacOS default and then starting yaboot by holding down the space bar. If the boot prompt comes up hit the tab key to get the bootable options.
Then start changing os-chooser around.
On top of that, the Manula is a bit misle4ading. ALL system resources appear to HAVE to be at the top level of the Linux Boot partition - ie not in the suseboot folder. So system, finder os-chooser, ramdisk.image.gz,vmlinux,yaboot, yaboot.conf and the tools folder at the top level. This works for me on a PowerBook G3 500 which is just a bloated iMac. As for the partition names, yes I tried lots but hd:10,... works fine. in yaboot,conf use hdx,/boot/vmlinuxname
Regards, Bruce, Melbourne Australia mailto:bruce@toorak.com
On Tue, Aug 08, Rasmus Back wrote:
Thanks for responding Bruce.
Running the generate_os_chooser script marks os-chooser as bootable. I tried switching the boot script lines, but this only affects which os is booted when space isn't held down at startup. Pressing space still doesn't boot into the other os. I also tried moving all the files from suseboot to the top level of the boot partition, but this had no perceivable effect. I'm not sure I understand your last suggestion, though. Do you refer to the image = vmlinux part, and that it should be changed to image = hd:7,/boot/vmlinux for the linux label.
That all sounds a little strange. I created a lilo for ppc, its currently beta software, so be careful. It can be found at ftp://ftp.suse.com/pub/projects/powerpc/ In your case point the boot= value to the partition that contains the suseboot folder. Point the other= value to your real boot partition. Modify the /etc/lilo.conf until it fits and run `lilo`. It will create a new folder "linuxboot" on the boot partition and mark it bootable. If it still doesnt work, paste the output of pdisk -l /dev/hda and proably the lilo output. lilo > output 2>&1 Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Hi Olaf. Well I tried it but no change :(. Lilo appearently uses ultra0 for hard drives. This, as I understand it, only works for slave drives. After running lilo on my iMac it didn't boot into anything, but after I changed all occurences of ultra0 to hd, I had the same functionality as before: Space doens't affect which os is booted and the keyboard doesn't work at the yaboot prompt. I'll paste the output of lilo and pdisk below. lilo output: bash-2.03# lilo rm: /tmp/ppc_lilo/ramdisk: is a directory !!!!!!!!!! unkown option apped !!!!!!!!!!!!! ERROR: initrd = /boot/initdisk7.gz ist not a regular file bash-2.03# lilo rm: /tmp/ppc_lilo/ramdisk: is a directory !!!!!!!!!! unkown option apped !!!!!!!!!!!!! running on pmac_new cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory BOOT_DEVICEPATH = ultra0:7, OTHER_DEVICEPATH = ultra0:6, Volume name is "SuSE" Volume was created on Sun Jul 23 20:00:23 2000 Volume was last modified on Tue Aug 8 22:59:50 2000 Volume has 46945280 bytes free SuSE:linuxboot: f FNDR/MACS 286 0 Sep 14 1999 Finder f zsys/MACS 92862 0 Aug 3 11:52 System f tbxi/chrp 0 416 Aug 8 23:18 os-chooser f BINA/UNIX 0 251811 Aug 8 23:18 yaboot f TEXT/R*ch 0 272 Aug 8 23:18 yaboot.conf f ????/UNIX 0 2821572 Aug 8 23:18 vmlinux f ????/UNIX 0 107109 Aug 8 23:18 initrd.pmacold.gz and pdisk: bash-2.03# pdisk -l /dev/hda Partition map (with 512 byte blocks) on '/dev/hda' #: type name length base ( size ) 1: Apple_partition_map Apple 63 @ 1 2: Apple_Driver_ATA*Macintosh 54 @ 64 3: Apple_Driver_ATA*Macintosh 74 @ 118 4: Apple_Driver_IOKit Macintosh 512 @ 192 5: Apple_Patches Patch Partition 512 @ 704 6: Apple_HFS untitled 5120000 @ 1216 ( 2.4G) 7: Apple_HFS untitled 2 102400 @ 5121216 ( 50.0M) 8: Apple_UNIX_SVR2 Swap 262144 @ 5223616 (128.0M) 9: Apple_UNIX_SVR2 A/UX Root 4096000 @ 5485760 ( 2.0G) 10: Apple_HFS untitled 5 20451328 @ 9581760 ( 9.8G) 11: Apple_Free Extra 272 @ 30033088 Device block size=512, Number of Blocks=30033359 (14.3G) DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 21, type=0x701 2: @ 118 for 33, type=0xf8ff Regards, Rasmus
That all sounds a little strange. I created a lilo for ppc, its currently beta software, so be careful. It can be found at ftp://ftp.suse.com/pub/projects/powerpc/
In your case point the boot= value to the partition that contains the suseboot folder. Point the other= value to your real boot partition. Modify the /etc/lilo.conf until it fits and run `lilo`.
It will create a new folder "linuxboot" on the boot partition and mark it bootable. If it still doesnt work, paste the output of pdisk -l /dev/hda and proably the lilo output.
lilo > output 2>&1
Gruss Olaf
-- $ man clone
BUGS Main feature not yet implemented...
On Tue, Aug 08, Rasmus Back wrote:
Well I tried it but no change :(. Lilo appearently uses ultra0 for hard drives. This, as I understand it, only works for slave drives. After running lilo on my iMac it didn't boot into anything, but after I changed all occurences of ultra0 to hd, I had the same functionality as before: Space doens't affect which os is booted and the keyboard doesn't work at the yaboot prompt. I'll paste the output of lilo and pdisk below.
Ok, I will update my show_of_path.sh script to handle hda always as hd and not ultra0. That the os-chooser script doesnt work sounds a little bit strange. So it can be a wrong value that simply doesn't match the space bar keycode, or the OF simple can't be used that way to get the keyboard input. The latter needs a little more work, so lets try the first one: Please create a new os-chooser file with the same contents as the current file and call it myfile. It should have this content: <CHRP-BOOT> <COMPATIBLE> iMac,1 PowerMac1,1 PowerBook1,1 PowerMac2,1 PowerMac3,1 PowerBook2,1 PowerBook3,1 </COMPATIBLE> <DESCRIPTION> Linux/PPC Yaboot bootloader </DESCRIPTION> <BOOT-SCRIPT> " get-key-map" " keyboard" open-dev $call-method dup 20 dump 5 + c@ 08 = if " Booting MacOS ..." cr " boot hd:7,\\myfile" eval else " Booting Yaboot ..." cr " boot hd:7,\\myfile" eval then </BOOT-SCRIPT> </CHRP-BOOT> This means it should boot itself. Safe it in the new linuxboot folder on the SuSE volume. The reboot and go to the OpenFirmware prompt with command+option+o+f printenv show you the current content of some variables, boot-device should be point to hd:7,\\:tbxi. Since hd is an alias it might be a long string to the device. Now type boot hd:7,\\myfile and press the space bar after you hit return. Keep the space bar pressed. My (newer) Macs boot then this file for a while, maybe a dozen times. Then it stops and it says that the OF can't open hd:7,\\myfile. but you should have two lines with 00. In the 6th field in the first line should be a 08. this line count starts with 0 and the number 5 is the space bar keycode. I guess you have something different here? Maybe a other value on another position? Please have a look at this support database article how a modified os-chooser script can look: http://sdb.suse.de/sdb/en/html/olh_ppc_macosx.html 3 + c@ 10 = if means the key x Please tell me if that helps. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Hi I tried what you described down below, but: In OF the slash: "/" gives just a space so I cant't type: hd:6,//myfile. It is strange because with the printenv command I see the forward slash in the param. I tried the line: boot hd:6,myfile and it didn't reboot many times as you said but very quickly the screen became blue and it said can't open hd:6,myfile. the 2 lines with 00 00 00's did come on the screen, but there were only zeros. I gues that OF didn't get as far as the myfile in the boot process. Oh, and the Imac was dead I had to use the paperclip to restart it. Gons on 08-08-2000 23:05, Olaf Hering at olh@suse.de wrote:
On Tue, Aug 08, Rasmus Back wrote:
Well I tried it but no change :(. Lilo appearently uses ultra0 for hard drives. This, as I understand it, only works for slave drives. After running lilo on my iMac it didn't boot into anything, but after I changed all occurences of ultra0 to hd, I had the same functionality as before: Space doens't affect which os is booted and the keyboard doesn't work at the yaboot prompt. I'll paste the output of lilo and pdisk below.
Ok, I will update my show_of_path.sh script to handle hda always as hd and not ultra0.
That the os-chooser script doesnt work sounds a little bit strange. So it can be a wrong value that simply doesn't match the space bar keycode, or the OF simple can't be used that way to get the keyboard input. The latter needs a little more work, so lets try the first one:
Please create a new os-chooser file with the same contents as the current file and call it myfile. It should have this content:
<CHRP-BOOT> <COMPATIBLE> iMac,1 PowerMac1,1 PowerBook1,1 PowerMac2,1 PowerMac3,1 PowerBook2,1 PowerBook3,1 </COMPATIBLE> <DESCRIPTION> Linux/PPC Yaboot bootloader </DESCRIPTION> <BOOT-SCRIPT> " get-key-map" " keyboard" open-dev $call-method dup 20 dump 5 + c@ 08 = if " Booting MacOS ..." cr " boot hd:7,\\myfile" eval else " Booting Yaboot ..." cr " boot hd:7,\\myfile" eval then </BOOT-SCRIPT> </CHRP-BOOT>
This means it should boot itself. Safe it in the new linuxboot folder on the SuSE volume. The reboot and go to the OpenFirmware prompt with command+option+o+f
printenv show you the current content of some variables, boot-device should be point to hd:7,\\:tbxi. Since hd is an alias it might be a long string to the device.
Now type boot hd:7,\\myfile and press the space bar after you hit return. Keep the space bar pressed. My (newer) Macs boot then this file for a while, maybe a dozen times. Then it stops and it says that the OF can't open hd:7,\\myfile.
but you should have two lines with 00. In the 6th field in the first line should be a 08. this line count starts with 0 and the number 5 is the space bar keycode. I guess you have something different here? Maybe a other value on another position?
Please have a look at this support database article how a modified os-chooser script can look: http://sdb.suse.de/sdb/en/html/olh_ppc_macosx.html
3 + c@ 10 = if means the key x
Please tell me if that helps.
Gruss Olaf
On Wed, Aug 09, Goncalo Nunes wrote:
Hi
I tried what you described down below, but:
In OF the slash: "/" gives just a space so I cant't type: hd:6,//myfile. It is strange because with the printenv command I see the forward slash in the param. I tried the line: boot hd:6,myfile and it didn't reboot many times as you said but very quickly the screen became blue and it said can't open hd:6,myfile. the 2 lines with 00 00 00's did come on the screen, but there were only zeros. I gues that OF didn't get as far as the myfile in the boot process.
There seem to be a bug in the first iMacs and B&W G3 machines, the keytable seems to be wrong. Place the file myfile in the toplevel directory of that boot partition. Remember to hold down space, or another key just for testing. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Hi, Hmmm, still no luck. I tried this with myfile at the top level, but like Goncalo my \ key just prints a space. I tried it with boot hd:7,myfile and that seemed to make it boot. The lines I get are just zeros 00 00 00 00 etc. I tried it with both space and 'x' held down. Rasmus
Ok, I will update my show_of_path.sh script to handle hda always as hd and not ultra0.
That the os-chooser script doesnt work sounds a little bit strange. So it can be a wrong value that simply doesn't match the space bar keycode, or the OF simple can't be used that way to get the keyboard input. The latter needs a little more work, so lets try the first one:
Please create a new os-chooser file with the same contents as the current file and call it myfile. It should have this content:
<CHRP-BOOT> <COMPATIBLE> iMac,1 PowerMac1,1 PowerBook1,1 PowerMac2,1 PowerMac3,1 PowerBook2,1 PowerBook3,1 </COMPATIBLE> <DESCRIPTION> Linux/PPC Yaboot bootloader </DESCRIPTION> <BOOT-SCRIPT> " get-key-map" " keyboard" open-dev $call-method dup 20 dump 5 + c@ 08 = if " Booting MacOS ..." cr " boot hd:7,\\myfile" eval else " Booting Yaboot ..." cr " boot hd:7,\\myfile" eval then </BOOT-SCRIPT> </CHRP-BOOT>
This means it should boot itself. Safe it in the new linuxboot folder on the SuSE volume. The reboot and go to the OpenFirmware prompt with command+option+o+f
printenv show you the current content of some variables, boot-device should be point to hd:7,\\:tbxi. Since hd is an alias it might be a long string to the device.
Now type boot hd:7,\\myfile and press the space bar after you hit return. Keep the space bar pressed. My (newer) Macs boot then this file for a while, maybe a dozen times. Then it stops and it says that the OF can't open hd:7,\\myfile.
but you should have two lines with 00. In the 6th field in the first line should be a 08. this line count starts with 0 and the number 5 is the space bar keycode. I guess you have something different here? Maybe a other value on another position?
Please have a look at this support database article how a modified os-chooser script can look: http://sdb.suse.de/sdb/en/html/olh_ppc_macosx.html
3 + c@ 10 = if means the key x
Please tell me if that helps.
Gruss Olaf
-- $ man clone
BUGS Main feature not yet implemented...
On Wed, Aug 09, Rasmus Back wrote:
Hmmm, still no luck. I tried this with myfile at the top level, but like Goncalo my \ key just prints a space. I tried it with boot hd:7,myfile and that seemed to make it boot. The lines I get are just zeros 00 00 00 00 etc. I tried it with both space and 'x' held down.
Appearently the script seems not to work on the iMacs with the string "iMac,1" in /proc/cpuinfo. I will try to get access to one of these machines to check it myself. I can only suggest the BootX Extension for now. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
OK, my final line was a bit of a flier - I'll try and explain. Sorry. First of all have you managed to get the INSTALL running? If not, then we don't have a valid yaboot.conf setup. I'll assume that os-chooser is working becasue if you can get a choice as to shich system boots first, that working!!! Now to the yaboot.conf. Try the following. On the PowerBook, the CDROM drive appears to want to map to /dev/hde in Unix. This MAY be the same for you on the iMac. Try this for yaboot.conf NOTE: YOU PROBABLY WON"T BE ABLE TO USE THIS DIRECTLY BECAUSE... you will have to change the video options. For a start try video="ofonly" <- This is Open Firmware Then as the INSTALL process is nooting, watch for a hint of your video card scolling past. vmode=17 is 1024x768x60Hz, leave out for a start. ideo=noautotune forces the drive to be read rather than cacheing so I am lead to believe!!! ------------ default = linux timeout = 100 # SuSE Linux 6.4 on partition hd11, (12 swap) and 13 (/usr) image = hd:11,/boot/vmlinux label = linux append = "video=aty128fb:vmode:17 ide0=autotune" root = /dev/hda11 # Installation fron CD - boot from vmlinux on Linux Boot Disk partition image = hd:10,vmlinux label = install append = "video=ofonly load_ramdisk=1 ramdisk_size = 20000" initrd = hd:10,ramdisk.image.gz # 0 image = hd:11,/boot/vmlinux.0 label = linux0 append = "video=aty128fb" root = /dev/hda11 # b image = hd:11,/boot/bvmlinux label = blinux append = "video=aty128fb ide0=noautotune" root = /dev/hda11 # la image = hd:11,/boot/vmlinux label = la append = "video=aty128fb" # lo image = hd:11,/boot/vmlinux label = lo append = "video=ofonly" # 4 image = hd:11,/boot/vmlinux label = linux4 # lai image = hd:11,/boot/vmlinux label = lai append = "video=aty128fb ide0=noautotune" # loi image = hd:11,/boot/vmlinux label = loi append = "video=ofonly ide0=noautotune" # append = "video=ofonly ide0=noautotune load_ramdisk=1 ramdisk_size = 20000" # append = "video=ofonly ide0=noautotune" # append = "video=ofonly" # root = /dev/hda11 #image = vmlinux # label = ide # add ide0=noautotune to the append line if your IDE drive doesn't work # append = "ide0=noautotune" # initrd = ramdisk.image.gz # root = /dev/fd0 # # your own kernel on the linux side, could look like this # image = ultra0:11,/boot/vmlinux # image = vmlinux # add ide0=noautotune to the append line if your IDE drive doesn't work # append = "video=aty128fb" # you want to set the valid root device # append = "video=aty128fb" ----------------- Now, obviously I have been experimenting so ignore my experiments and see if any of this will help. Cut and paste the sections required and then RUN os-chooser again afterwards. For some reason, os-chooser DOES alkter yaboot.conf Good luck from a lovely sunny but cool mid-winters day here in Melbourne! Bruce.
Hi Olaf.
Well I tried it but no change :(. Lilo appearently uses ultra0 for hard drives. This, as I understand it, only works for slave drives. After running lilo on my iMac it didn't boot into anything, but after I changed all occurences of ultra0 to hd, I had the same functionality as before: Space doens't affect which os is booted and the keyboard doesn't work at the yaboot prompt. I'll paste the output of lilo and pdisk below.
lilo output:
bash-2.03# lilo rm: /tmp/ppc_lilo/ramdisk: is a directory !!!!!!!!!! unkown option apped !!!!!!!!!!!!! ERROR: initrd = /boot/initdisk7.gz ist not a regular file bash-2.03# lilo rm: /tmp/ppc_lilo/ramdisk: is a directory !!!!!!!!!! unkown option apped !!!!!!!!!!!!! running on pmac_new cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory cat: /proc/device-tree/aliases/ultra0: No such file or directory BOOT_DEVICEPATH = ultra0:7, OTHER_DEVICEPATH = ultra0:6, Volume name is "SuSE" Volume was created on Sun Jul 23 20:00:23 2000 Volume was last modified on Tue Aug 8 22:59:50 2000 Volume has 46945280 bytes free SuSE:linuxboot: f FNDR/MACS 286 0 Sep 14 1999 Finder f zsys/MACS 92862 0 Aug 3 11:52 System f tbxi/chrp 0 416 Aug 8 23:18 os-chooser f BINA/UNIX 0 251811 Aug 8 23:18 yaboot f TEXT/R*ch 0 272 Aug 8 23:18 yaboot.conf f ????/UNIX 0 2821572 Aug 8 23:18 vmlinux f ????/UNIX 0 107109 Aug 8 23:18 initrd.pmacold.gz
and pdisk:
bash-2.03# pdisk -l /dev/hda
Partition map (with 512 byte blocks) on '/dev/hda' #: type name length base ( size ) 1: Apple_partition_map Apple 63 @ 1 2: Apple_Driver_ATA*Macintosh 54 @ 64 3: Apple_Driver_ATA*Macintosh 74 @ 118 4: Apple_Driver_IOKit Macintosh 512 @ 192 5: Apple_Patches Patch Partition 512 @ 704 6: Apple_HFS untitled 5120000 @ 1216 ( 2.4G) 7: Apple_HFS untitled 2 102400 @ 5121216 ( 50.0M) 8: Apple_UNIX_SVR2 Swap 262144 @ 5223616 (128.0M) 9: Apple_UNIX_SVR2 A/UX Root 4096000 @ 5485760 ( 2.0G) 10: Apple_HFS untitled 5 20451328 @ 9581760 ( 9.8G) 11: Apple_Free Extra 272 @ 30033088
Device block size=512, Number of Blocks=30033359 (14.3G) DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 21, type=0x701 2: @ 118 for 33, type=0xf8ff
Regards,
Rasmus
That all sounds a little strange. I created a lilo for ppc, its currently beta software, so be careful. It can be found at ftp://ftp.suse.com/pub/projects/powerpc/
In your case point the boot= value to the partition that contains the suseboot folder. Point the other= value to your real boot partition. Modify the /etc/lilo.conf until it fits and run `lilo`.
It will create a new folder "linuxboot" on the boot partition and mark it bootable. If it still doesnt work, paste the output of pdisk -l /dev/hda and proably the lilo output.
lilo > output 2>&1
Gruss Olaf
-- $ man clone
BUGS Main feature not yet implemented...
Hi I am using a rev c imac and am experiencing the exact same problems as Rasmus and I still haven't found a solution Gons on 08-08-2000 20:34, Rasmus Back at rasse@mac.com wrote:
Thanks for responding Bruce.
Running the generate_os_chooser script marks os-chooser as bootable. I tried switching the boot script lines, but this only affects which os is booted when space isn't held down at startup. Pressing space still doesn't boot into the other os. I also tried moving all the files from suseboot to the top level of the boot partition, but this had no perceivable effect. I'm not sure I understand your last suggestion, though. Do you refer to the image = vmlinux part, and that it should be changed to image = hd:7,/boot/vmlinux for the linux label.
Regards,
--Rasmus
On Tue, Aug 08, Goncalo Nunes wrote:
Hi I am using a rev c imac and am experiencing the exact same problems as Rasmus and I still haven't found a solution
Hmm, this is strange. Is it the original Apple USB keyboard? If you have an earlier version than MacOS 9.0.2 you should be able to use BootX as a workaround. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Yep its the original and indeed bootx works, but that is not ideal. At the moment I have yaboot bootable and don't use the os-chooser. The problem is that my wife wants to use the Mac-os and I Linux! Gons on 08-08-2000 23:08, Olaf Hering at olh@suse.de wrote:
On Tue, Aug 08, Goncalo Nunes wrote:
Hi I am using a rev c imac and am experiencing the exact same problems as Rasmus and I still haven't found a solution
Hmm, this is strange. Is it the original Apple USB keyboard? If you have an earlier version than MacOS 9.0.2 you should be able to use BootX as a workaround.
Gruss Olaf
Thats easy, use bootX and save MacOS as the deafult prefs and you will have to hit the tab key when Bootx starts!! Remember you can boot to Linux from Bootx Control Panel. Double click and tab return. (Doesn't work on the PowerBook G3500 firewire series though!!) Or in Yaboot, set the deafult to MacOS and you will have to hold down the space bar. Bruce.
Yep its the original and indeed bootx works, but that is not ideal. At the moment I have yaboot bootable and don't use the os-chooser. The problem is that my wife wants to use the Mac-os and I Linux!
Gons
on 08-08-2000 23:08, Olaf Hering at olh@suse.de wrote:
On Tue, Aug 08, Goncalo Nunes wrote:
Hi I am using a rev c imac and am experiencing the exact same problems as Rasmus and I still haven't found a solution
Hmm, this is strange. Is it the original Apple USB keyboard? If you have an earlier version than MacOS 9.0.2 you should be able to use BootX as a workaround.
Gruss Olaf
Am Die, 08 Aug 2000 schrieb Goncalo Nunes:
Hi I am using a rev c imac and am experiencing the exact same problems as Rasmus and I still haven't found a solution
Gons
on 08-08-2000 20:34, Rasmus Back at rasse@mac.com wrote:
Thanks for responding Bruce.
Running the generate_os_chooser script marks os-chooser as bootable. I tried switching the boot script lines, but this only affects which os is booted when space isn't held down at startup. Pressing space still doesn't boot into the other os. I also tried moving all the files from suseboot to the top level of the boot partition, but this had no perceivable effect. I'm not sure I understand your last suggestion, though. Do you refer to the image = vmlinux part, and that it should be changed to image = hd:7,/boot/vmlinux for the linux label.
Regards,
--Rasmus
Hi, I am using a B&W G3 and I had the exact same problems as Rasmus and Goncalo. I've just found a workaround for my machine: After updating my Firmware with "G3_Firmware_Update_1.1.smi.bin" found at http://asu.info.apple.com/swupdates.nsf/artnum/n11361 I was able to switch between the OSs at boottime with the Spacebar and later tapping input at yaboot bootpromt. I've still no access to my own kernel on the linux side: "boot: hd:7,/boot/vmlinux" isn't working. The only possibility to boot linux with yaboot is to use a kernel in the suseboot-folder. Has anyone a good idea? Ciao, Micha
On Fri, Aug 11, Michael Engel wrote:
Hi, I am using a B&W G3 and I had the exact same problems as Rasmus and Goncalo. I've just found a workaround for my machine: After updating my Firmware with "G3_Firmware_Update_1.1.smi.bin" found at http://asu.info.apple.com/swupdates.nsf/artnum/n11361 I was able to switch between the OSs at boottime with the Spacebar and later tapping input at yaboot bootpromt.
I will add this to our support database.
I've still no access to my own kernel on the linux side: "boot: hd:7,/boot/vmlinux" isn't working. The only possibility to boot linux with yaboot is to use a kernel in the suseboot-folder. Has anyone a good idea?
The OF can not access ext2 partitions. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Stuff I'm pretty sure is done right: 4 partitions: about 6GB HFS+ for MacOS 40MB HFS for booting Linux 128MB AUX Swap for Swap about 3GB AUX for Linux After that it kind of goes to pot. tried following directions from CD#1 - copy Suseboot to boot partition, set that as the Startup drive, and then reboot while holding c to boot of CD#1 That didn't work so well - screen goes properly black, penguin appears at top left, and a lot of text comes up saying it is doing stuff. One of the things that comes up says something to the effect that USB isn't working. It does keep trying to do stuff but eventually a blue/gray dialog comes up asking to make sure that the CD is in. That CD is definately in there. Since it doesn't see the CD nothing happens. Also tried reading the manual - this was frustrating since the manual, the readme, and the docs I printed off the support database on yaboot all say slightly different things. Using all of the Docs, and a Linux knowledgeable friend I tried setting yaboot up manually - no real joy there either. Is there one place with a unified set of installation instructions? Is my extremely new iMac too new for Suse PPC 6.4? Cameron .:. -- -- This mirror will show you your enemies. Cameron Bales .:. Sackville, New Brunswick, Canada work: (506)-364-1097 http://www.tantramar.com/ home: (506) 536-3613 http://i.am/cameronbales ---- The current decade shall be known as "The Naughties" ----
On Fri, Aug 11, Cameron Bales .:. wrote:
After that it kind of goes to pot. tried following directions from CD#1 - copy Suseboot to boot partition, set that as the Startup drive, and then reboot while holding c to boot of CD#1
That didn't work so well - screen goes properly black, penguin appears at top left, and a lot of text comes up saying it is doing stuff. One of the things that comes up says something to the effect that USB isn't working. It does keep trying to do stuff but eventually a blue/gray dialog comes up asking to make sure that the CD is in. That CD is definately in there. Since it doesn't see the CD nothing happens.
Also tried reading the manual - this was frustrating since the manual, the readme, and the docs I printed off the support database on yaboot all say slightly different things. Using all of the Docs, and a Linux knowledgeable friend I tried setting yaboot up manually - no real joy there either.
Is there one place with a unified set of installation instructions? Is my extremely new iMac too new for Suse PPC 6.4?
Only the kernel is too old for that machine ;=) I have one report of a successful boot into linuxrc. Please do it this way: Get the latest kernel from ppclinux.apple.com/~benh , download the vmlinux*.gz file, extract it with Mac Gunzip in the tools folder in suseboot. replace the old kernel "vmlinux" with the new one, keep the name "vmlinux". Edit the file yaboot.conf, there is a section like that: image = vmlinux root = /dev/fd0 # apppen = "something" label = install initrd = ramdisk.image.gz replace that something with ramdisk_size=50000. Then reboot, you don't need to hold down the key "c", the boot device is already set to your Linux Boot partition. Now choose YaST1 and try to install Linux. It *might* be possible that Yast2 works too, but I guess the newer ATI cards are not yet supported. If it works for you, please read the instructions at http://sdb.suse.de/sdb/en/html/usb2216.html and http://sdb.suse.de/sdb/en/html/keylist.POWERPC.html The newer kernels have a changed interface for the new USB drivers and you need to update at least the devs.rpm. If you still have trouble, please let me know. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Hi everybody, Is anybody using external speakers with suse 6.4. I'm trying to play mp3s with xmms 1.0.1, but the sound is very quiet. This probably isn't xmms fault, all sounds in linux are about half the volume i get when using the mac os. Fiddling around with kmix doesn't help much, the volume slider for line out does nothing as far as I can tell, the same goes for the volume slider in xmms. Yast2 just says unkown card/driver in its sound module and won't let me set any options. Alsaconf doesn't support my sound card either. My mac is a rev A iMac. And an international keyboard question: How do I type @, [, ], braces and \ on my finnish keyboard? Normally I would use SHIFT and/or ALT + some_key. Except for these special character my keyboard works fine. Any thoughts on either of these issues? TIA, Rasmus
participants (7)
-
Bruce -
Cameron Bales .:. -
Goncalo Nunes -
Michael Engel -
Olaf Hering -
Rasmus Back -
Rasmus Back