Files for BootX
Hi, I am on my sixth attempt to install Debian on a Powerbook G3 (Wallstreet). I am out of ideas. I have OpenFirmware < 3.0, so I tried the following: 1. boot from floppies. four floppies, two different writing methods; I think my floppy drive is too picky. 2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from Debian, but, now I go back and cannot find it. I made it the farthest with this method. I got to the point where it asks for the installation CD, but, then the installer could not find the files rescue.bin and powermac/drivers.tgz. I could not find these anywhere on the CD, either. 3. yaboot. Did not work as the documentation said it would not. 4. Quik: I could not figure out how to create a unix partition for this program to use. I tried the Apple "Linux Home" partition, but that did not work. I was skeptical that Apple would support Linux anyhow. Acutely aware of the patience of the readership, I present the following questions in decreasing order of importance: a) Where do I get the ramdisk.img.gz and linux.bin files BootX is looking for? The installation CD and the ftp site seem to be pushing yaboot and floppies. b) Is BootX the way to go? I would like to have both MacOS9 and Sarge on the same machine. It seems reasonable and, like I wrote previously, it seemed to work the best for my setup. Thank you for your time. I appreciate any help you can offer. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Files for BootX
On Mon, 2006-01-09 at 18:11 -0500, Chris Fisichella wrote: > a) Where do I get the ramdisk.img.gz and linux.bin files BootX is > looking for? The installation CD and the ftp site seem to be pushing > yaboot and floppies. > > b) Is BootX the way to go? I would like to have both MacOS9 and Sarge > on the same machine. It seems reasonable and, like I wrote previously, > it seemed to work the best for my setup. Yes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Files for BootX
On (09/01/06 18:11), Chris Fisichella wrote: > I am on my sixth attempt to install Debian on a Powerbook G3 > (Wallstreet). I am out of ideas. I have OpenFirmware < 3.0, so I tried > the following: > > 1. boot from floppies. four floppies, two different writing methods; I > think my floppy drive is too picky. > > 2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from > Debian, but, now I go back and cannot find it. I made it the farthest > with this method. I got to the point where it asks for the installation > CD, but, then the installer could not find the files rescue.bin and > powermac/drivers.tgz. I could not find these anywhere on the CD, either. > > 3. yaboot. Did not work as the documentation said it would not. > > 4. Quik: I could not figure out how to create a unix partition for this > program to use. I tried the Apple "Linux Home" partition, but that did > not work. I was skeptical that Apple would support Linux anyhow. > > Acutely aware of the patience of the readership, I present the > following questions in decreasing order of importance: > > a) Where do I get the ramdisk.img.gz and linux.bin files BootX is > looking for? The installation CD and the ftp site seem to be pushing > yaboot and floppies. Get BootX from here: http://penguinppc.org/historical/benh/ It's a while since i did this but it was pretty straight forward and quite a few people have documented the process ... google around, you should find loads. Here's one: http://www.ppcnux.de/modules.php?name=Content&pa=showpage&pid=79 Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Files for BootX
On Mon, Jan 09, 2006 at 06:11:31PM -0500, Chris Fisichella wrote: > Hi, > > I am on my sixth attempt to install Debian on a Powerbook G3 > (Wallstreet). I am out of ideas. I have OpenFirmware < 3.0, so I tried > the following: > > 1. boot from floppies. four floppies, two different writing methods; I > think my floppy drive is too picky. > > 2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from > Debian, but, now I go back and cannot find it. I made it the farthest > with this method. I got to the point where it asks for the installation > CD, but, then the installer could not find the files rescue.bin and > powermac/drivers.tgz. I could not find these anywhere on the CD, either. > > 3. yaboot. Did not work as the documentation said it would not. > > 4. Quik: I could not figure out how to create a unix partition for this > program to use. I tried the Apple "Linux Home" partition, but that did > not work. I was skeptical that Apple would support Linux anyhow. Quik can only work after you have completed the installation. It is not useful to start an installation. > Acutely aware of the patience of the readership, I present the > following questions in decreasing order of importance: > > a) Where do I get the ramdisk.img.gz and linux.bin files BootX is > looking for? The installation CD and the ftp site seem to be pushing > yaboot and floppies. These filenames are not used anymore, the installation manual still mentions them, but that is a known bug in the installation manual (bug #344477). The new filenames are "vmlinux" and "initrd.gz" I you aim for an installation started with BootX and loading the rest from an installation-CD, you should use the "cdrom" flavour of the "vmlinux/initrd.gz" files, located at: http://ftp.debian.org/debian/dists/sarge/main/installer-powerpc/current/images/powerpc/cdrom/ I don't know where on the installation-cd these files are located. > b) Is BootX the way to go? I would like to have both MacOS9 and Sarge > on the same machine. It seems reasonable and, like I wrote previously, > it seemed to work the best for my setup. Yes. -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> Signature generated by Signify v1.14. For this and more, visit http://www.debian.org/ signature.asc Description: Digital signature
Re: Files for BootX
On Tue, Jan 10, 2006 at 11:29:26AM +, Clive Menzies wrote: > On (09/01/06 18:11), Chris Fisichella wrote: [...] > > 2. BootX: I could have sworn I downloaded the ramdisk.img.gz file from > > Debian, but, now I go back and cannot find it. I made it the farthest > > with this method. I got to the point where it asks for the installation > > CD, but, then the installer could not find the files rescue.bin and > > powermac/drivers.tgz. I could not find these anywhere on the CD, either. [...] > > a) Where do I get the ramdisk.img.gz and linux.bin files BootX is > > looking for? The installation CD and the ftp site seem to be pushing > > yaboot and floppies. > Get BootX from here: > > http://penguinppc.org/historical/benh/ The OP already goot BootX working, se point #2 above. The OP wants to know where to get the kernel and initrd that starts (or is) the debian-installer. -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Re: Files for BootX
Gentlemen, Thank you very much for clearing up the file naming issue for me. Using vmlinux and initrd.gz is definitely the way to go. I certainly feel indebted to you all. Perhaps I could help update the fine Debian PowerPC installation manual if I can ever get this OS booted? Speaking of installation problems, I am 99% sure Debian is sitting on my hard disk. The installation goes fine. I choose not to install Quik because I am fairly sure BootX is the "manual boot loader" the installer is referring to. Unfortunately, I can not boot into Debian. I certainly apologize for the delay in my response to your original postings, but I was trying different permutations of the boot parameters and disk partitioning options to somehow get around this re-occuring message: VFS: cannot open root device "hda12" or unknown-block(0,0) please append a correct 'root=" boot option kernel panic: VFS: unable to mount root fs on unknown-block(0,0) <0>rebooting in 180 seconds.._ In BootX, I have always left the vmlinux kernel selected. I tried deselecting the initrd.gz ramdisk file. When I did that, I would enter hda12 into the BootX "/dev/" text box. I did that because the Debian installer said: "You will need to boot manually with the /boot/vmlinux kernel on partition /dev/hda12 and root=/dev/hda12 passed as kernel argument. I tried adding root=/dev/hda12 with and without the compressed ramdisk image. I also reviewed the installation manual and the www.ppcnux.de BootX tutorial that was given to me by Clive . They, apparently kept both their vmlinux file and the compressed ramdisk image. They also added the following additional kernel arguments root=/dev/hda12 devfs=mount,all rw In Boot X, my additional kernel arguments text box now contains: root=/dev/hda12 devfs=mount,all rw video=atyfb:vmode:14,cmode:32,mclk:63 And I end up with the same kernel panic. Once again, I appeal to you all for help. If you have any thoughts on this, I would welcome any feedback. I have a Powerbook G3 "Wallstreet", OldWorld. My disk has MacOS9.0 on one partition, I have a 10.5 GB partition reserved for Debian and two essentially empty partitions. i used the Debian "Guided partition->Use largest unused block->multi-user workstation. -Chris On Tuesday, January 10, 2006, at 07:00 AM, Hans, Benjamin and Clive wrote: The OP already goot BootX working, se point #2 above. The OP wants to know where to get the kernel and initrd that starts (or is) the debian-installer. -- Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Files for BootX
On Fri, Jan 13, 2006 at 08:15:42PM -0500, Chris Fisichella wrote: > Gentlemen, > > Thank you very much for clearing up the file naming issue for me. Using > vmlinux and initrd.gz is definitely the way to go. I certainly feel > indebted to you all. Perhaps I could help update the fine Debian > PowerPC installation manual if I can ever get this OS booted? That sounds nice. I have sent a patch for the problem you (and others) have met, but I welcome any enhancements to that patch. The bug I filed is #344477, available here: http://bugs.debian.org/344477 > Speaking of installation problems, I am 99% sure Debian is sitting on > my hard disk. The installation goes fine. I choose not to install Quik > because I am fairly sure BootX is the "manual boot loader" the > installer is referring to. Correct. > Unfortunately, I can not boot into Debian. I certainly apologize for > the delay in my response to your original postings, but I was trying > different permutations of the boot parameters and disk partitioning > options to somehow get around this re-occuring message: > > VFS: cannot open root device "hda12" or unknown-block(0,0) > please append a correct 'root=" boot option > kernel panic: VFS: unable to mount root fs on unknown-block(0,0) > <0>rebooting in 180 seconds.._ > > In BootX, I have always left the vmlinux kernel selected. I tried > deselecting the initrd.gz ramdisk file. When I did that, I would enter > hda12 into the BootX "/dev/" text box. I did that because the Debian > installer said: > > "You will need to boot manually with the /boot/vmlinux kernel on > partition /dev/hda12 and root=/dev/hda12 passed as kernel argument. This is an error in the installer manual. The kernel in the 3.1 release of Debian requires an initrd, and that excludes any root=/dev/hdXX boot argument. > I tried adding root=/dev/hda12 with and without the compressed ramdisk > image. If any root device is to be set, it would be root=/dev/ram, but I think that BootX will automatically set that when a ramdisk (initrd) is choosen. > I also reviewed the installation manual and the www.ppcnux.de BootX > tutorial that was given to me by Clive . They, apparently kept both > their vmlinux file and the compressed ramdisk image. They also added > the following additional kernel arguments > root=/dev/hda12 devfs=mount,all rw That is old, obsolete, incorrect information. > In Boot X, my additional kernel arguments text box now contains: > root=/dev/hda12 devfs=mount,all rw video=atyfb:vmode:14,cmode:32,mclk:63 > > And I end up with the same kernel panic. Yeah, because the kernel has not the drivers to the harddisk compiled in, they are compiled as modules and exists in the ramdisk (initrd) to be loaded at the first stage of the boot process. > Once again, I appeal to you > all for help. If you have any thoughts on this, I would welcome any > feedback. Even if you have already installed Debian, you need to start the debian-installer again. You will not need to reinstall, but there are files (a new kernel and a new initrd) on the partition that you installed Debian on that you need to copy to the MacOS partition so those files can be loaded by BootX. So, restart the debian-installer, and run it until it has identified your hardware (detected the harddisk). At that point you should get a shell prompt. (Either from the debian-installer menu, or by pressing Alt-F2). Now you must mount the partition where debian was installed, something like this: # mount /dev/hda12 /mnt Then "go into" that partition by the following: # chroot /mnt then mount the MacOS partition, below I asume it is at /dev/hda11. # mount /dev/hda11 /mnt Now copy the kernel and initrd to that partition: # cp /boot/vmlinux* /boot/initrd* /mnt Now, exit the chroot, and the shell. Cancel the debian-installer and reboot to MacOS. Within BootX choose the kernel and initrd you copied. Try boot into "Linux". Good luck -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? signature.asc Description: Digital signature
Re: Files for BootX
On Saturday, January 14, 2006, at 06:13 PM, Hans Ekbrand wrote: That sounds nice. I have sent a patch for the problem you (and others) have met, but I welcome any enhancements to that patch. The bug I filed is #344477, available here: http://bugs.debian.org/344477 Oh, good idea! LIke I said, if I can get this thing to boot up, I would be glad to detail my experiences. I was thinking of putting them on LinuxQuestions.org also. Even if you have already installed Debian, you need to start the debian-installer again. You will not need to reinstall, but there are files (a new kernel and a new initrd) on the partition that you installed Debian on that you need to copy to the MacOS partition so those files can be loaded by BootX. So, restart the debian-installer, and run it until it has identified your hardware (detected the harddisk). At that point you should get a shell prompt. (Either from the debian-installer menu, or by pressing Alt-F2). Now you must mount the partition where debian was installed, something like this: # mount /dev/hda12 /mnt # mkdir /mnt # mount /dev/ide/host0/bus0/target0/lun0/part12 /mnt Then "go into" that partition by the following: # chroot /mnt # chroot /mnt then mount the MacOS partition, below I asume it is at /dev/hda11. # mount /dev/hda11 /mnt # mount /dev/hda10 /mnt mount /dev/hda10 has wrong device number or fs type hfs not supported. Hans, thanks for the help! I _NEVER_ would thought to do that. But, I think I see where you are going with this. Those two files: initrd.img-2.6.8-powerpc vmlinux-2.6.8-powerpc need to be used by BootX to boot my machine. I thought Debian supported hfs volumes. Oh well, I guess not! :) Moving those files off of that filesystem is a bit tricky at this point. I can't ftp because network services are not up and running. It looks like the software infrastructure is not in place for those files to be transferred to a place where BootX can use them. Perhaps I should install Quik, boot into Debian (finally!), ftp those files out to a convenient machine and then wipe the hard drive. I could then install MacOS, use "Fetch" to bring those two files back, and install them for BootX to use. Then, for the eighth time, I could install Debian! :) Sound reasonable? Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Files for BootX
On Sun, Jan 15, 2006 at 04:09:51PM -0500, Chris Fisichella wrote: > > On Saturday, January 14, 2006, at 06:13 PM, Hans Ekbrand wrote: > > > > >That sounds nice. I have sent a patch for the problem you (and others) > >have met, but I welcome any enhancements to that patch. The bug I > >filed is #344477, available here: > > > >http://bugs.debian.org/344477 > > Oh, good idea! LIke I said, if I can get this thing to boot up, I would > be glad to detail my experiences. I was thinking of putting them on > LinuxQuestions.org also. > > > >Even if you have already installed Debian, you need to start the > >debian-installer again. You will not need to reinstall, but there are > >files (a new kernel and a new initrd) on the partition that you > >installed Debian on that you need to copy to the MacOS partition so > >those files can be loaded by BootX. > > > >So, restart the debian-installer, and run it until it has identified > >your hardware (detected the harddisk). At that point you should get a > >shell prompt. (Either from the debian-installer menu, or by pressing > >Alt-F2). Now you must mount the partition where debian was installed, > >something like this: > > > ># mount /dev/hda12 /mnt > > # mkdir /mnt > # mount /dev/ide/host0/bus0/target0/lun0/part12 /mnt > > > >Then "go into" that partition by the following: > > > ># chroot /mnt > > # chroot /mnt > > > > >then mount the MacOS partition, below I asume it is at /dev/hda11. > > > ># mount /dev/hda11 /mnt > > # mount /dev/hda10 /mnt > mount /dev/hda10 has wrong device number or fs type hfs not supported. > > Hans, thanks for the help! I _NEVER_ would thought to do that. But, I > think I see where you are going with this. Those two files: > > initrd.img-2.6.8-powerpc > vmlinux-2.6.8-powerpc > > need to be used by BootX to boot my machine. I thought Debian supported > hfs volumes. Oh well, I guess not! :) Yes it does! there is a kernel-module for hfs (and even for hfs+). Try # ls -lR /lib/modules/2.6.8*-powerpc/kernel/fs/hfs* It might not be loaded automatically in the chroot, though. Try # modprobe hfs and then # mount /dev/hda10 /mnt > Moving those files off of that filesystem is a bit tricky at this > point. Copying them from the chroot is a known working method (e.g. see http://lists.debian.org/debian-powerpc/2005/12/msg00293.html) Good Luck (you're really close now :) -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Re: Files for BootX
On Sunday, January 15, 2006, at 05:31 PM, Hans Ekbrand wrote: need to be used by BootX to boot my machine. I thought Debian supported hfs volumes. Oh well, I guess not! :) Yes it does! there is a kernel-module for hfs (and even for hfs+). Try # ls -lR /lib/modules/2.6.8*-powerpc/kernel/fs/hfs* It might not be loaded automatically in the chroot, though. Try # modprobe hfs and then # mount /dev/hda10 /mnt Those commands worked perfectly. Indeed, you were correct, I was very close. Debian is a very nice distro! As a small token of my thanks, I would like to help out with the manual. I think I should document my experience before it fades from my mind. How would you suggest I do that? Should I start with your bug report? Thanks very much, Hans, Clive and Ben. You were all a great help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Files for BootX
On Sun, Jan 15, 2006 at 10:37:33PM -0500, Chris Fisichella wrote: > On Sunday, January 15, 2006, at 05:31 PM, Hans Ekbrand wrote: [...] > >It might not be loaded automatically in the chroot, though. Try > > > ># modprobe hfs > > > >and then > > > ># mount /dev/hda10 /mnt > > Those commands worked perfectly. Indeed, you were correct, I was very > close. Debian is a very nice distro! As a small token of my thanks, I > would like to help out with the manual. I think I should document my > experience before it fades from my mind. How would you suggest I do > that? Should I start with your bug report? Yes, the text in the patched is file is rather terse, and it assumes that you do the right thing at the first try. The trick of running the installer a second time and chroot into the installed system and copy the kernel and initrd perhaps should be documented also (even if that trick not will be necessary as often, when the installation manual is corrected). I suggest that you describe it in the boot-new-xml file just below the paragraph that reads: If you use BootX to boot into the installed system, you should have copied the kernel and initrd from /boot to the MacOS partition before finishing the installer as described in . Post your additions as patches to the bug. Mail to [EMAIL PROTECTED], and cc: to me. -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> GnuPG key: 1024D/7050614E Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E Learn about secure email at http://www.gnupg.org signature.asc Description: Digital signature
Re: Files for BootX
Title: Re: Files for BootX HI Chris, I am trying to do a similar project of loading Debian Sarge on to a Mac 6500 old world powerpc using BootX. Your serious of discussions has been most supportive. I have encountered the same problems, but have not yet solved them all. I first tried and succeeded in using BootX to load Yellow Dog Linux 3.1 which worlds OK on this older mac but is slow because I only have 64 Mb of ram. But I got the idea of how to use BootX. Once I realized that the Debian initrd.gz was to be stored in the mac partition (OS 9.1) as ramdisk.image.gz then I was able to start the Sarge installation from the CDs. I learned the renaming technique from the Ubuntu lists but saw it repeated in your series of discussions. Like you I could not reboot into Sarge once the first part of the installation had completed. I was able to use the YDL vmlinux kernal to reboot and finish the Sarge setup. So for a while I had a fully functional Sarge system running. But then I turned off the computer. It rebooted into Mac OS 9.1 and I open BootX to start Sarge. The YDL kernel no longer worked but produced a kernal panic. So I was happy to see that you worked out a sytem to actually copy back to the mac a working reboot kernel. I'm having trouble following your example. The line # chroot /mnt is followed by an error that there is no such directory. But I can see it listed in the root director after # mkdir /mnt, # ls commands. Also # modprobe hfs doesn't work it also errors. I've probably missed a step. Have you been able to put together a list of steps that you followed to install Sarge? I am wondering if I have mucked up my previous installation by going back in a second time to try the steps to mount the hfs partition. Is there a way to check that? Any reference that includes hfs seems to come back as no such directory. Bye for now, George --Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. If you are not the intended recipient(s), you are hereby notified that any dissemination, unauthorized review, use, disclosure, copying, or distribution of the contents of this email and/or any materials contained in any attachments is prohibited. If you have received this message in error, or are not the intended recipient(s), please immediately notify the sender by email and destroy all copies of the original message, including attachments.
Re: Files for BootX
On Wednesday, January 18, 2006, at 10:25 AM, Dombi, George wrote: HI Chris, I am trying to do a similar project of loading Debian Sarge on to a Mac 6500 old world powerpc using BootX. Your serious of discussions has been most supportive. I have encountered the same problems, but have not yet solved them all. I first tried and succeeded in using BootX to load Yellow Dog Linux 3.1 which worlds OK on this older mac but is slow because I only have 64 Mb of ram. But I got the idea of how to use BootX. Once I realized that the Debian initrd.gz was to be stored in the mac partition (OS 9.1) as ramdisk.image.gz then I was able to start the Sarge installation from the CDs. I learned the renaming technique from the Ubuntu lists but saw it repeated in your series of discussions. Like you I could not reboot into Sarge once the first part of the installation had completed. I was able to use the YDL vmlinux kernal to reboot and finish the Sarge setup. So for a while I had a fully functional Sarge system running. But then I turned off the computer. It rebooted into Mac OS 9.1 and I open BootX to start Sarge. The YDL kernel no longer worked but produced a kernal panic. So I was happy to see that you worked out a sytem to actually copy back to the mac a working reboot kernel. I'm having trouble following your example. The line # chroot /mnt is followed by an error that there is no such directory. But I can see it listed in the root director after # mkdir /mnt, # ls commands. Also # modprobe hfs doesn't work it also errors. I've probably missed a step. Have you been able to put together a list of steps that you followed to install Sarge? I am wondering if I have mucked up my previous installation by going back in a second time to try the steps to mount the hfs partition. Is there a way to check that? Any reference that includes hfs seems to come back as no such directory. Bye for now, George HI George, I am, indeed, in the process of writing up a fairly detailed account of my experiences in installing Debian on my powerbook G3. I have in front of me the notes I took as I was working through the "second install." That Hans was nice enough to help me with. The following assume you have MacOS installed, a separate HFS partition and a Debian partition. In my case, I used the Debian Installer partition tool to tell me what partition was what. Here is what I did: BusyBox v1.0.0 pre10 (Debian 20040623-1) Built in shell (ash) Enter 'help' for a list of built in commands ~# mkdir mnt ~#mount /dev/ide/host0/bus0/target0/lun0/part12 /mnt ~#chroot /mnt sh-2.05b# ls -IR /lib/modules/2.6.8&*-powerpc/kernel/fs/hfs* /lib/modules/2.6.8-powerpc/kernel/hfs: hfs.ko /lib/modules/2.6.8-powerpc/kernel/hfsplus: hfsplus.ko sh-2.05b# modprobe hfs sh-2.05b# mount /dev/hda10 /mnt sh-2.05b# cp /boot/vmlinux* /boot/intrd* /mnt sh-2.05b# exit ~#exit So, you'll need to manually traverse the /dev/ide/... tree to find out exactly what path to use. Mine is for a powerbook. Yours will probably be different. Maybe something went wrong in that line. As for the modprobe. I don't know. Okay, I have to run. Good luck- Chris
Re: Files for BootX
On Jan 18, 2006, at 10:25 AM, Dombi, George wrote: Also # modprobe hfs doesn't work it also errors. Try "modprobe hfsplus" Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Files for BootX
Hi Rick, I tried your suggestion with # modprobe hfsplus but the same failure occurred. I will have to put this project down for awhile since I'm not proceeding with the reboot at all. All mention of hfs in any form seems to cause an inability for Linux to find that mac partition. I know I used mac in the hfs and not hfsplus format to install Mac OS 9.1. Bye for now, George -Original Message- From: Rick Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 3:42 PM To: Dombi, George Cc: [EMAIL PROTECTED]; debian-powerpc@lists.debian.org Subject: Re: Files for BootX On Jan 18, 2006, at 10:25 AM, Dombi, George wrote: > Also # modprobe hfs doesn't work it also errors. Try "modprobe hfsplus" Rick -- Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. If you are not the intended recipient(s), you are hereby notified that any dissemination, unauthorized review, use, disclosure, copying, or distribution of the contents of this email and/or any materials contained in any attachments is prohibited. If you have received this message in error, or are not the intended recipient(s), please immediately notify the sender by email and destroy all copies of the original message, including attachments.
