Subject: Re: got it! yaboot is back!
From: Keary Suska (hierophant@pcisys.net)
Date: Wed Dec 05 2001 - 09:49:42 MST
I doubt that MOL had anything to do with it, but there are a lot of odd
things that seem to effect open firmware. I recently had a problem where
faulty RAM caused my G4 to apparently reset the firmware, or at least mangle
it to the point that it wouldn't boot off the bootloader partition.
The act of installing shouldn't cause anything, but since the Mac OS (and
hence MOL) uses OF to drive devices, it is possible that a faulty,
malconfigured, or inappropriate driver could have confused OF sufficiently
to cause this problem. If you can boot and use Mac OS and Linux over the
next several days without problem, then you could attempt to boot MOL and
see if the problem returns. Be sure to redirect stdout & stderr to a file so
you can examine it later. It may give clues as to what is happening.
Keary Suska
Esoteritech, Inc.
"Leveraging Open Source for a better Internet"
From: darren david <darrendavid@thebomb.com>
Reply-To: mol-general@lists.maconlinux.org
Date: Wed, 5 Dec 2001 00:40:59 -0800
To: mol-general@lists.maconlinux.org
Subject: Re: got it! yaboot is back!
so go ahead and add everything that i did before to the list, plus tack on
changing yaboot.conf back to its original state prior to this whole mess
(which is basically to remove all of the open firmware paths):
# ybin options
boot=/dev/hdb9
macos=/dev/hda
so that ybin would seek out the proper paths on its own.
Phew!
Big thanks to Keary for getting me on the right path, and to Google for
showing me the way. <<grin>>.
Now the only question that remains is: was it installing mac-on-linux that
caused this problem in the first place?
d.
so... when i run "mkofboot -v" I get:
mkofboot: Warning: Incompatible version of 'nvsetenv', nvram will not be
updated
mkofboot: Warning: Unknown archetecture [sic], /dev/hdb9 may not be bootable
on this machine
actually, i just fixed this my migrating /proc/device-tree and /proc/cpuinfo
into /proc in my mounted filesystem (/templinux)... but i still can't get
out of the loop. I can get into the "First Stage GNU/Linux Bootstrap" but
selecting "linux" just brings me back to where i started...
<<sigh>>
darren
There are two things you can do: 1) boot off the YDL CD (or the rescue CD),
and boot Linux from the prompt--the choice might be "linux" or "linux-text";
2) Tell open firware to boot off the second drive, instructions following.
WARNING: if you choose to do the following you do so at your own risk. It is
possible that your computer could be rendered unbootable by this action, and
you agree by following these instructions that you understand this risk and
agree to hold Keary Suska and Esoteritech, Inc. free of any liability
resulting from such instructions.
That out of the way, you want to tell open firmware which device to attempt
to boot from.
0) Boot into OF by holding down CMD-OPT-O-F.
1) At the prompt, type "printenv" <enter>
2) Look in the list for "boot-device". Take note of the format. The number
following "hda" is the partition to boot from. If there is no number (just a
comma), the number would go before the comma. You may have two "listings"
for the variable--use the one with a partition number for the following
instructions.
3) Where "boot_device_param" is the boot device line exactly as seen in step
#2 except using "hdb" instead of "hda" and specifying the boot partition
number, type "setenv boot-device: boot_device_param" <enter>
4) type "boot" <enter>
If your mac doesn't boot at all, or you get the dreaded question mark, boot
back into open firmware and double check your variable setting. Make sure it
is syntactically correct according to what there was before you changed it.
You can type "reset-all" <enter> to reset your firmware or CMD-OPT-P-R for
two boings. You should then at least get back to your original state of
booting only into Mac OS.
Additionally, there may be particular issues when using separate drives
under yabooot. I am not familiar with these, but perhaps someone else is.
Keary Suska
Esoteritech, Inc.
"Leveraging Open Source for a better Internet"
> From: darren david <darrendavid@thebomb.com>
> Reply-To: mol-general@lists.maconlinux.org
> Date: Sun, 2 Dec 2001 19:28:18 -0800
> To: mol-general@lists.maconlinux.org
> Subject: Re: help! yaboot is gone!
>
> That was a start, but I can't see my linux partition at all - i've
> got two drives in the machine, and it's only showing the bootable
> partition on /dev/hda (mac os) - /dev/hdb is conspicuously missing...
> and since i can't get into linux, i can't run mkofboot. any other
> thoughts?
>
> Thanks,
> Darren David
>
>> It sounds like somehow your firmware was reset, such as by by holding down
>> CMD-OPT-P-R for two boings. To get back into the boot loader, hold down the
>> option key when booting. You will then be presented with icons for each
>> bootable partition. Select the Linux boot icon. When you get the text menu,
>> boot into either system and restart to see if you get the menu again. If
>> not, you will probably have to re-install the bootloader using mkofboot.
>>
>> Keary Suska
>> Esoteritech, Inc.
>> "Leveraging Open Source for a better Internet"
>>
>>> From: darren david <darrendavid@thebomb.com>
>>> Reply-To: mol-general@lists.maconlinux.org
>>> Date: Sun, 02 Dec 2001 15:42:00 -0800
>>> To: mol-general@lists.maconlinux.org
>>> Subject: help! yaboot is gone!
>>>
>>> hi-
>>>
>>> i recently got mac-on-linux up and running on my YDL 2.0 box...
>>> everything was peachy until i rebooted the box, and now it appears
>>> that yaboot is missing, and the box just boots directly into Mac OS.
>>> How do I get back into my linux system which is on another partition?
>>>
>>> for the record, any idea why or how this might have happened? i'd
>>> like to avoid it in the future. ;p
>>>
>>> thanks,
>>> darren david.
>>> --
>>>
>>>
>>>
>>> ___________________________________________________
>>> Darren David | darrendavid@thebomb.com
>>>
>
> --
>
>
>
> ___________________________________________________
> Darren David | darrendavid@thebomb.com
>
--___________________________________________________ Darren David | darrendavid@thebomb.com
--
___________________________________________________ Darren David | darrendavid@thebomb.com
--
___________________________________________________ Darren David | darrendavid@thebomb.com
This archive was generated by hypermail 2a24 : Wed Dec 05 2001 - 10:03:13 MST