Jaap-Jan,
I hope you will get the information soon.
I would like to know more about it.
thanks in advance
dragan
Jaap-Jan Boor wrote:
>
> Dragan,
>
> It doesn't work out of the box on my iMac (flower power). I'm still
> contacting Suse
>
> Jaap-Jan
>
> On Thursday, June 21, 2001, at 10:29 AM, DRagan wrote:
>
> > Hello,
> >
> > I need some information about iMac modem.
> > Does it work without problem with SuSE linux 7.1?
> >
> > Is there any istallation problem?
> >
> > thanks
> >
> >
> >
> > best regards
> > dragan
> >
> >
LILO on Mac does nothing but parses lilo.conf and updates os-chooser and
yaboot.conf, it is not a real bootloader like on PC. You can safely
remove it. SuSE did PPC LILO for IBM PowerPC workstations and to make PC
people feel more comfortable on Mac..
During normal startup procedure yaboot pick ups kernel from /boot
directory on Linux partition. vmlinux and ramdisk on HFS boot partition
are actually needed ONLY for installtion and/or update of base system if
startup CD does not work or do not exists. If you load vmlinux and
ramdisk from HFS boot partition you can install or update base system
from NFS or FTP.
>>
>> The problem people encounter while trying to configure dual
>> boot is they
>> try different approaches while not completely understanding technical
>> background of this process.
>>
>
>Precisely. The annoying thing is that it's really not that difficult so why
>are the instructions so ridiculous? It's such a fundamental part of the
>installation that it really should have taken a high priority. Some people
>would abandon the whole idea of Linux because they can't get this working.
>
>>
>> PS. Procedure described in SuSE manual is rather too
>> complicated and not
>> clear. Basically you just need open firmware to evaluate os-chooser
>> script. After that, either yaboot either MacOS will be started up.
>> However, yaboot needs valid yaboot.conf file to load proper kernel.
>> That's only two files to edit!
>>
>> I did dual-boot without LILO and editing open firmware variables.
>>
>
>I still don't understand how LILO enters the equation? I haven't touched
>LILO and my system is working fine. I'm worried that I've missed something
>though. I think perhaps that Linux is picking up its kernel from my HFS
>partition or possibly even a ramdisk on my HFS partition?
>
>An explanation of how Open Firmware, os-chooser, yaboot, yaboot.conf, lilo
>and lilo.conf all interract would be invaluable.
********************************************************
* Best Regards --- Andrei Verovski *
* e-mail --- andrei.verovski(a)bigfoot.com *
* *
* Personal Home Page *
* http://homepage.mac.com/macgurutemple/ *
********************************************************
Hello,
I need some information about iMac modem.
Does it work without problem with SuSE linux 7.1?
Is there any istallation problem?
thanks
best regards
dragan
>
> The problem people encounter while trying to configure dual
> boot is they
> try different approaches while not completely understanding technical
> background of this process.
>
Precisely. The annoying thing is that it's really not that difficult so why
are the instructions so ridiculous? It's such a fundamental part of the
installation that it really should have taken a high priority. Some people
would abandon the whole idea of Linux because they can't get this working.
>
> PS. Procedure described in SuSE manual is rather too
> complicated and not
> clear. Basically you just need open firmware to evaluate os-chooser
> script. After that, either yaboot either MacOS will be started up.
> However, yaboot needs valid yaboot.conf file to load proper kernel.
> That's only two files to edit!
>
> I did dual-boot without LILO and editing open firmware variables.
>
I still don't understand how LILO enters the equation? I haven't touched
LILO and my system is working fine. I'm worried that I've missed something
though. I think perhaps that Linux is picking up its kernel from my HFS
partition or possibly even a ramdisk on my HFS partition?
An explanation of how Open Firmware, os-chooser, yaboot, yaboot.conf, lilo
and lilo.conf all interract would be invaluable.
Brad
Hi,
The problem people encounter while trying to configure dual boot is they
try different approaches while not completely understanding technical
background of this process.
PS. Procedure described in SuSE manual is rather too complicated and not
clear. Basically you just need open firmware to evaluate os-chooser
script. After that, either yaboot either MacOS will be started up.
However, yaboot needs valid yaboot.conf file to load proper kernel.
That's only two files to edit!
I did dual-boot without LILO and editing open firmware variables.
********************************************************
* Best Regards --- Andrei Verovski *
* e-mail --- andrei.verovski(a)bigfoot.com *
* *
* Personal Home Page *
* http://homepage.mac.com/macgurutemple/ *
********************************************************
Okay, this is roughly how I did it (supplied instructions do not work on my
system).
1. Copy the SuSE boot folder onto the HFS formatted Linux Boot partition
2. I deleted all the stuff to do with BootX
3. Delete the Mac OS Rom file (note case)
4. Leave the Yaboot.inf file alone
5. Rename the os-chooser.example file to os-chooser
6. Edit os-chooser file to point to the correct partitions for booting MacOS
or Linux
7. I swapped the 2 around so that it boots MacOS by default (keep my
girlfriend happy)
8. Run the Make os-chooser bootable script
9. Rename os-chooser to Mac OS ROM
That's it. Now, when I hold down space at bootup I get the yaboot menu (oh,
made "linux" the default label - this makes it use the latest kernel),
whereas if I don't hold the space bar I get MacOS 9.1
Hope this might help someone. The point is that I tried what it said in the
manual and also everything I could find on the SuSE site but none of that
worked. I think the instructions must be wrong. I'll make more specific
instructions soon if anyone wants them.
Brad
Hello,
I seem to have acceleration running fine with 7.1 and latest Linux
kernel with latest Xfree but the OpenGL features of XMMS no longer
work. As far as I know all the latest Mesa libs are intsalled. What
should I be looking for to fix this.
Best Regards,
Ola Olsson
hello,
I'm wondering if there is a SUSE package with rpm-python in it. I
thought it should be either a separate package or already compiled
into RPM, but it is nowhere to be seen.
Thank you
Joss
