Re: Kernel building
On Sat, 1 Dec 2001, Ryan Boder wrote: Hi, I am trying to build the latest kernel from penguinppc.org and having a problem. I am just wondering if there is some Mandrake specific configuration that I don't know about. I used to do this all the time when I used linuxppc but have never built one with Mandrake (or any other distro for that matter) Nope, nothing special for Mandrake. We do call the kernel vmlinuz to be consistant with the other arches for the install_kernel scripts etc. If you added an initrd line for your kernel in yaboot, did you creat an initrd to go with it with mkinitrd? The purpose here is slightly different than the installer or rescue image. Since our kernel as a distribtution, tries to be all things to all people we have one of 2 choices: make a monolithic kernel with drivers for everything = big kernel make a modular kernel with the core elements and make driver modules initrd loads modules you need early in the boot stage that you need to access your hardware or filesystem. typical use: scsi boot drive, or journalled / Try commenting out the initrd line if you don't think you need it. It's OK to ask here. We don't really have any other support channel for Mandrake PPC, aside from the forum, and I find it easier to use email than to go to the web page. Basically it seems to hang at the point where the scsi driver is being loaded for scsi emulation for my cd burner on an ibook2 (which also happens to be one of the first things that happens in the boot so the driver may not be significant). It complains a few times that / is not mounted and then stops booting. I followed the ibook specific instructions on ibooklinux.net so I think I haven't misconfigured the kernel. I also am fairly confident that I didn't screw up the yaboot.conf entry because I have written many a yaboot.conf when I used linuxppc and yaboot isn't even included in the install so you have to set it up yourself. I made the entry look exactly like the ones made by the install except changed the named of the image and label. I'm not sure why they use ramdisk because I thought that was for installs but I gave yaboot.conf the ramdisk entries just like the ones made by the install. So now that I've probably given too much information, is there something I don't know about in the Mandrake distro that I could screw up making my kernel never mount / that I didn't have to do back when I used linuxppc? Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Still have the same problem
I just ran the chroot stuff that you told me to and then tried to boot Mandrake. All I have on screen after the Welcome to Mandrake Linux! is: boot: (to which i typed) linux Loading kernel... and then it just sits there and sits there and sits there I got this far before and I know that it will sit there until I get tired and need to turn it off.:( - Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 6:35 AM Subject: Re: Still have the same problem On Fri, 30 Nov 2001, Aaron Stechesen wrote: here is the yaboot.conf details: init-message=\nWelcome to Mandrake Linux!\n boot=/dev/hda7 ofboot=hd:7 delay=30 timeout=50 install=/usr/local/lib/yaboot/yaboot magicboot=/usr/local/lib/yaboot/ofboot enablecdboot enableofboot defaultos=linux default=linux novram image=hd:8,/boot/vmlinuz label=failsafe root=/dev/hda8 initrd=hd:8./boot/initrd.img append= failsafe read-only macosx=hd:6 image=hd:8,/boot/vmlinuz label=linux root=/dev/hda8 initrd=hd:8,/boot/initrd.img read-write This looks mostly OK. This line is probably just a typo?: initrd=hd:8./boot/initrd.img Note the . instead of , Did you rerun ybin while you were in the chroot? And id so did you get the boot prompt? Also did you check the Open Firmware boot-device settings? To edit in rescue you would use vi. For that I'd suggest checking google, as I'd rather not get into a vi lesson here. Coming from MacOS, vi may seem a bit strange, but it's something you can count on being present on most any unix system you sit down at. Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re[2]: Still have the same problem
Just how would I launch it if I need to. Do I even need to? does the , need to be .? What he is saying is that with the yaboot.conf you have you will be unable to boot into failsafe mode because you have a '.' where you should have a ','. He was assuming this was a typo though in your email and that youe yaboot.conf is actually ok. The line for initrd in yaboot.conf for failsafe mode should read initrd=hd:8,/boot/initrd.img ^ | | (See the weird looking arrow I made trying to pint at the comma) If you have a dot there instead od a comma you will not be able to boot failsafe. Hope that helps. -- Ryan Boder http://www.ece.cmu.edu/~rtb
Re[2]: Kernel building
Nope, nothing special for Mandrake. We do call the kernel vmlinuz to be consistant with the other arches for the install_kernel scripts etc. If you added an initrd line for your kernel in yaboot, did you creat an initrd to go with it with mkinitrd? The purpose here is slightly different than the installer or rescue image. Since our kernel as a distribtution, tries to be all things to all people we have one of 2 choices: Ok, you got me on that one. I was trying to use the initrd that you made with your kernel. So this time I made my own initrd like you said with mkinitrd. I am still having the same problem but I think I may be screwing up this initrd thing. Here is how I made it... [root@toby rtb]# mkinitrd /boot/initrd-2.4.17-pre1 2.4.17-pre1 mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 [root@toby rtb]# Is this the right way to do it? I then of course changed my yaboot.conf to use this ram disk image and then re-ran ybin. typical use: scsi boot drive, or journalled / I am booting from an ide disk (the one that comes in the ibook2) and not using any jouranled file systems right now. My cd-rw is using scsi emulation but since I am booting for the hard disk I don't think that matters. Try commenting out the initrd line if you don't think you need it Well that is what I tried in the first place out of habit. Then when it didn't work I started messing with the initrd. It's OK to ask here. We don't really have any other support channel for Mandrake PPC, aside from the forum, and I find it easier to use email than to go to the web page. Ok, well I'll be a bit more specific. When I try to boot with my kernel it outputs the exact same stuff as whet I get from dmesg after booting with your kernel (except for the Stew Benedict and Mandrake stuff at the top). Then when it gets to the line that says SCSI subsystem driver Revision: 1.00 (Which is about line 66 of the dmesg output) It complains about 4 times that the Root file system is now mounted and then it hangs. So I never get to the next line about the Macintosh non-volatile memory driver v1.0 when I try to boot with my kernel. Your 2.4.4-6.2mdk kernel that comes with the install however continues past that point and boots just fine. Any ideas what might cause that? -- Ryan Boder http://www.ece.cmu.edu/~rtb
RE: Booting Mandrake After install
Any time -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Stechesen Sent: Thursday, November 29, 2001 1:43 AM To: [EMAIL PROTECTED] Subject: Re: Booting Mandrake After install On Wednesday, November 28, 2001, at 08:39 PM, Jonathan Sailor wrote: Comments on booting the rescue mode: You do see a yaboot prompt when booting off the cd, right? Yup! I will check it out. I want to split my remaining 11.1 GB into a Darwin partition followed by Mandrake. Also, sys-linux (the x86 cd bootloader) is a lot more developed to this kind of thing. Yaboot, well, it does work. Try hitting tab for a list of images. (Syslinux was designed for this, yaboot was designed for lilo-ish stuff.) Hope to help, good luck You did Jonathan and thanks! Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Stechesen Sent: Wednesday, November 28, 2001 5:58 PM To: [EMAIL PROTECTED] Subject: Re: Booting Mandrake After install On Wednesday, November 28, 2001, at 05:46 AM, Stew Benedict wrote: On Wed, 28 Nov 2001, Aaron Stechesen wrote: Hello! I have been driven over the edge with this problem. I can successfully install Mandrake 8.0 PPC on my Rev.B Bondi iMac and I can get the bootloader installed (yaboot). Yaboot can boot Mac OS, the CDROM, and the Open Firmware but I can never get Linux to boot. I either get Loading Image.(and it never loads) or the error message that it can't find the image. I have tried everything I could find on the web, in the document pages and I have posed this question on many Forums but I have not ever gotten answer. It seems that everyone can get the damn thing booted , and then have problems afterwards or have problems with the bootloader, but I don't have any troubles with install/configuration just booting. I am extremely frustrated and getting to wits end with Mandrake in general because of the endless problems I have been having with PPC 8.0 and the horrid PC 8.1 version. Please help me, after three months of frustration I need answers. I so much would like to run Mandrake on both my machines but I really need help getting going on my iMac. (The PC 8.0 runs just fine for me.) I own the same machine. I need to know some things about your partition setup and yaboot setup. Can you: 1) boot the rescue CD Rescue cd? Do I enter rescue from the yaboot prompt after the cd loads or what. On the pc it is an option right from the time the cd boots/mounts (press F1 if I am not mistaken). 2) tell me something about what /sbin/pdisk -l /dev/hda says I had it partitioned fine all three times that I laid out the hard drive. 3) If you know what partition you installed linux on, mount it on /mnt/disk in the rescue mode and send: the contents of yaboot.conf ls -l /boot Can't help you there right now because I removed Mandrake in place of Darwin. But I may be able to devote a few GB to mandrake after. Is there a way to avoid this continual problem at install? I may try reinstalling before i install Darwin. (You can bring up networking in rescue and ftp this stuff to another machine) It sounds like just a typo or something in yaboot.conf, although the installer should have set it up for you like it does for most everyone else. Is /boot a seperate partition (even if it is, we uncovered that issue in the beta and it should be fixed now)? Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/ _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
RE: Still have the same problem
VI Basics (I'm bored, why not?): run: vi filename type: I (w/o quotes) use arrows to move up/down/left/right, same as SimpleText except W/O a mouse. when done, ESC to exit editing mode, and ZZ to save/quit, or use :q!ENTER (w/o quotes). Example: vi /mnt/disk/etc/yaboot.conf DOWN DOWN RIGHT DELETE 2 ESC ZZ Used Vi to replcae the 1st character on the third line with a 2. Saved, and quit. Hope to help. Also, you may want to install pico on your system. It's a very useful editor, with help, all. Just pico filename, and everything else is pie. H2H, Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Stechesen Sent: Saturday, December 01, 2001 8:35 AM To: [EMAIL PROTECTED] Subject: Re: Still have the same problem I just ran the chroot stuff that you told me to and then tried to boot Mandrake. All I have on screen after the Welcome to Mandrake Linux! is: boot: (to which i typed) linux Loading kernel... and then it just sits there and sits there and sits there I got this far before and I know that it will sit there until I get tired and need to turn it off.:( - Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 6:35 AM Subject: Re: Still have the same problem On Fri, 30 Nov 2001, Aaron Stechesen wrote: here is the yaboot.conf details: init-message=\nWelcome to Mandrake Linux!\n boot=/dev/hda7 ofboot=hd:7 delay=30 timeout=50 install=/usr/local/lib/yaboot/yaboot magicboot=/usr/local/lib/yaboot/ofboot enablecdboot enableofboot defaultos=linux default=linux novram image=hd:8,/boot/vmlinuz label=failsafe root=/dev/hda8 initrd=hd:8./boot/initrd.img append= failsafe read-only macosx=hd:6 image=hd:8,/boot/vmlinuz label=linux root=/dev/hda8 initrd=hd:8,/boot/initrd.img read-write This looks mostly OK. This line is probably just a typo?: initrd=hd:8./boot/initrd.img Note the . instead of , Did you rerun ybin while you were in the chroot? And id so did you get the boot prompt? Also did you check the Open Firmware boot-device settings? To edit in rescue you would use vi. For that I'd suggest checking google, as I'd rather not get into a vi lesson here. Coming from MacOS, vi may seem a bit strange, but it's something you can count on being present on most any unix system you sit down at. Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/ _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Still have the same problem
Cool, thank you! - Original Message - From: Jonathan Sailor [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 11:20 AM Subject: RE: Still have the same problem VI Basics (I'm bored, why not?): run: vi filename type: I (w/o quotes) use arrows to move up/down/left/right, same as SimpleText except W/O a mouse. when done, ESC to exit editing mode, and ZZ to save/quit, or use :q!ENTER (w/o quotes). Example: vi /mnt/disk/etc/yaboot.conf DOWN DOWN RIGHT DELETE 2 ESC ZZ Used Vi to replcae the 1st character on the third line with a 2. Saved, and quit. Hope to help. Also, you may want to install pico on your system. It's a very useful editor, with help, all. Just pico filename, and everything else is pie. H2H, Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Stechesen Sent: Saturday, December 01, 2001 8:35 AM To: [EMAIL PROTECTED] Subject: Re: Still have the same problem I just ran the chroot stuff that you told me to and then tried to boot Mandrake. All I have on screen after the Welcome to Mandrake Linux! is: boot: (to which i typed) linux Loading kernel... and then it just sits there and sits there and sits there I got this far before and I know that it will sit there until I get tired and need to turn it off.:( - Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 6:35 AM Subject: Re: Still have the same problem On Fri, 30 Nov 2001, Aaron Stechesen wrote: here is the yaboot.conf details: init-message=\nWelcome to Mandrake Linux!\n boot=/dev/hda7 ofboot=hd:7 delay=30 timeout=50 install=/usr/local/lib/yaboot/yaboot magicboot=/usr/local/lib/yaboot/ofboot enablecdboot enableofboot defaultos=linux default=linux novram image=hd:8,/boot/vmlinuz label=failsafe root=/dev/hda8 initrd=hd:8./boot/initrd.img append= failsafe read-only macosx=hd:6 image=hd:8,/boot/vmlinuz label=linux root=/dev/hda8 initrd=hd:8,/boot/initrd.img read-write This looks mostly OK. This line is probably just a typo?: initrd=hd:8./boot/initrd.img Note the . instead of , Did you rerun ybin while you were in the chroot? And id so did you get the boot prompt? Also did you check the Open Firmware boot-device settings? To edit in rescue you would use vi. For that I'd suggest checking google, as I'd rather not get into a vi lesson here. Coming from MacOS, vi may seem a bit strange, but it's something you can count on being present on most any unix system you sit down at. Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/ _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
mandrake kernel and s900
I just checked and the s900 has a mesh controller at scsi 0 where my cd and hd are. Using 2.4.6 when I specify mesh controller I get insmod failed. Suse 7.1 works and says it is a mesh controller. I also tried the newest kernel I could find 2.4.13 and it also got the same error with all.gz the all.rz 2.4.13 kernel panicked btw immediately. So, I think there is a problem with the mandrake kernel and s900 (which looks like a 9500). Any hope.
Re: Still have the same problem
- Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 11:15 AM Subject: Re: Still have the same problem On Sat, 1 Dec 2001, Aaron Stechesen wrote: I just ran the chroot stuff that you told me to and then tried to boot Mandrake. All I have on screen after the Welcome to Mandrake Linux! is: boot: (to which i typed) linux Loading kernel... and then it just sits there and sits there and sits there I got this far before and I know that it will sit there until I get tired and need to turn it off.:( try hd:8,/boot/vmlinuz or hd:8,/boot/vmlinuz-2.4.4-6.2mdk can you forward: ls -l /mnt/disk/boot when you are in rescue mode with yoyr partition mounted The bootloader setup seems OK, but perhaps your kernel is missing or corrupted. This is a fresh install of 8.0? Yes sir it is. Installed it last night and this is the same result as the countless time before:( Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Still have the same problem
result of ls -l /mnt/disk/boot: total 3672 -rw-r--r-- 1 rootroot 455451 Jun 28 01:32 Sysytem.map-2.4.4-6.2mdk -rw-r--r-- 1 rootroot 28844 Jun 28 01:32 config-2.4.4-6.2mdk -rw-r--r-- 1 rootroot 521397 Nov 30 07:12 initrd-2.4.4-6.2mdk.img lrwxrwxrwx1 rootroot 23 Nov 30 07:12 initrd.img - initrd-2.4.4-6.2mdk.img lrwxrwxrwx1 rootroot 14 Nov 30 07:12 kernel.h - kernel.h-2.4.4 -rw-r--r-- 1 rootroot441 Nov 30 07:12 kernel.h-2.4.4 -rw-r--r-- 1 rootroot0 Nov 30 07:12 mac-us.ext.klt -rw-r--r-- 1 rootroot130 Nov 30 07:12 message lrwxrwxrwx1 rootroot 20 Nov 30 07:12 vmlinuz - vmlinuz-2.4.4-6.2mdk* -rwxr-xr-x 1 rootroot 2720888 Nov 30 07:12 vmlinuz-2.4.4-6.2mdk* the initrd.img in line four, the kernel.h in the next line, and vmlinuz in the second last line are in blue letters. the vmlinuz-2.4.4-6.2mdk in the last two lines are in green letters (not the hash marks though). - Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 11:15 AM Subject: Re: Still have the same problem On Sat, 1 Dec 2001, Aaron Stechesen wrote: I just ran the chroot stuff that you told me to and then tried to boot Mandrake. All I have on screen after the Welcome to Mandrake Linux! is: boot: (to which i typed) linux Loading kernel... and then it just sits there and sits there and sits there I got this far before and I know that it will sit there until I get tired and need to turn it off.:( try hd:8,/boot/vmlinuz or hd:8,/boot/vmlinuz-2.4.4-6.2mdk can you forward: ls -l /mnt/disk/boot when you are in rescue mode with yoyr partition mounted The bootloader setup seems OK, but perhaps your kernel is missing or corrupted. This is a fresh install of 8.0? Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Still have the same problem
On Sat, 1 Dec 2001, Aaron Stechesen wrote: try hd:8,/boot/vmlinuz or hd:8,/boot/vmlinuz-2.4.4-6.2mdk where would i put this? The initrd= line? Should I replace the , 's with . 's on the initrd= and image= lines? type it at the boot: prompt Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Still have the same problem
Thanks I'll try. Do you think that this could be one of those instances where the combination of the size of my hard drive and the OF make it impossible to boot past the 8 gig barrier? - Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 3:27 PM Subject: Re: Still have the same problem On Sat, 1 Dec 2001, Aaron Stechesen wrote: try hd:8,/boot/vmlinuz or hd:8,/boot/vmlinuz-2.4.4-6.2mdk where would i put this? The initrd= line? Should I replace the , 's with . 's on the initrd= and image= lines? type it at the boot: prompt Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
RE: Still have the same problem
Info on bootloader:
Open firmware booting is weird. First and foremost, there are actually three
files involved in a yaboot configuration. First is, obviously, the kernel.
Second and third are OFBOOT.B and yaboot. OFBOOT.B is some cryptic Forth
commands that instruct Open Firware to display the Mac, Linux, etc. Once an
option is selected, it chainloads to Mac, the CD, or loads Linux. To load
Linux, it calls yaboot. Yaboot is actual binary which does the loading of
Linux itself. Analogy for x86 users:
+-+
| Grub |
+-+
/ |'-\
++ ++ +-+
| {hda8} | | {hda9} | | {hda10} |
++ ++ +-+
|
++
| Linux |
++
In this, Grub is OFBOOT.B, hda8 and 9 are Mac and Darwin, and hda10 would be
Lilo in x86, but is yaboot in ppc. Linux is Linux.
H2H -Jonathan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Stechesen
Sent: Saturday, December 01, 2001 8:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Still have the same problem
- Original Message -
From: Stew Benedict [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, December 01, 2001 6:35 AM
Subject: Re: Still have the same problem
On Fri, 30 Nov 2001, Aaron Stechesen wrote:
here is the yaboot.conf details:
init-message=\nWelcome to Mandrake Linux!\n
boot=/dev/hda7
ofboot=hd:7
delay=30
timeout=50
install=/usr/local/lib/yaboot/yaboot
magicboot=/usr/local/lib/yaboot/ofboot
enablecdboot
enableofboot
defaultos=linux
default=linux
novram
image=hd:8,/boot/vmlinuz
label=failsafe
root=/dev/hda8
initrd=hd:8./boot/initrd.img
append= failsafe
read-only
macosx=hd:6
image=hd:8,/boot/vmlinuz
label=linux
root=/dev/hda8
initrd=hd:8,/boot/initrd.img
read-write
This looks mostly OK. This line is probably just a typo?:
initrd=hd:8./boot/initrd.img
Note the . instead of ,
No. I t is. in fact initrd=hd:8,/boot/initrd.img
Did you rerun ybin while you were in the chroot?
Not yet.
And id so did you get the
boot prompt?Also did you check the Open Firmware boot-device settings?
The setting is setenv boot-device hd:7,\\:tbxi
and the bootloader starts just fine. I boot into OS X, Firmware and CDROM
without troubles.
To edit in rescue you would use vi. For that I'd suggest checking google,
as I'd rather not get into a vi lesson here. Coming from MacOS, vi may
seem a bit strange, but it's something you can count on being present on
most any unix system you sit down at.
Just how would I launch it if I need to. Do I even need to? does the ,
need to be .?
Thanks alot for your assistance by the way. There is a serious lack of help
on the mandrake user site and not a heck of alot of info tothis problem
elsewhere.
Stew Benedict
--
MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/
PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Re: Still have the same problem
On Sat, 1 Dec 2001, Aaron Stechesen wrote: Thanks I'll try. Do you think that this could be one of those instances where the combination of the size of my hard drive and the OF make it impossible to boot past the 8 gig barrier? That's entirely possible and something I overlooked. I dropped a larger drive in my iMac and recall hitting a scenario in one of my tests where it would not boot. I think Ben or someone mentioned an issue with OF on the older machines that may be the limiting factor here. I don't suppose you have a way of getting /boot farther down in the partition table? Alternately, you could put the kernel on an HFS partition and boot it. Once the kernel is up I don't think it will matter. I hate to mix OS's like that, but it beats not booting at all. Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Still have the same problem
I think that I may try reinstalling everything but this time I will make three partitions within the first eight gigs. One of four for for OSX.1, two for Darwin, and two for Linux. The last twelve gigs I wil use for file storage. Is it possible to have my /home partition at the end of the drive, say in the last four gigs and evrything run alright? Is two gigs enough for my / and swap? - Original Message - From: Stew Benedict [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 01, 2001 7:06 PM Subject: Re: Still have the same problem On Sat, 1 Dec 2001, Aaron Stechesen wrote: Thanks I'll try. Do you think that this could be one of those instances where the combination of the size of my hard drive and the OF make it impossible to boot past the 8 gig barrier? That's entirely possible and something I overlooked. I dropped a larger drive in my iMac and recall hitting a scenario in one of my tests where it would not boot. I think Ben or someone mentioned an issue with OF on the older machines that may be the limiting factor here. I don't suppose you have a way of getting /boot farther down in the partition table? Alternately, you could put the kernel on an HFS partition and boot it. Once the kernel is up I don't think it will matter. I hate to mix OS's like that, but it beats not booting at all. Stew Benedict -- MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
New Airport Base Station
Just wanted to report that I think I have 128-bit encryption working with the new Airport Base Station (white, dual ethernet ports). I had been using the first generation Airport Base Station and I am still using my original Airport card which was presumably updated to support 128-bit encryption and possibly other goodies as part of the new Airport 2.0 software install. All I had to do was set up the new Airport Base Station in Mac OS (128-bit encryption was not enabled by default) then I wrote down the much longer equivalent network password and entered that into my ifcfg-eth1 script in Linux. I am able to get onto the net so it seems that everything magically works! Ron
