Subject: Re: YDL install w/ multiple drives
From: C.L. Simco (clsimco@random-specific.com)
Date: Fri Jan 04 2002 - 00:28:44 MST
Avinash and Juan,
Thank you both, and all else who have
taken an interest in this thread/ challenge.
Specific reply in order of receipt:
1. Avinash
2. Juan
-----------------------
Avinash,
Things are in reality a bit (lot?) more complicated
since that command did not solve the situation.
I appreciate the resource URL you provided greatly, and will
be spending time in the coming days doing as you suggest.
As well, I am endeavoring to find a comprehensive "dictionary"
for the terms/ names and commands in Linux [root] and GUI.
That, in an effort to communicate more intelligently in this
great forum, with those of you kind enough to share time and resources.
I've learned a great deal from you.
Highest Regards
CL
Avinash Gupta wrote:
> You may want to try running the following command from a konsole:
>
> ofpath /dev/hde8
>
> This should tell you the "real" Open firmware path. But if this does not
> work, then things are a bit (a lot?) more complicated ...
>
> Look at the following yaboot FAQ:
>
> http://www.alaska.net/~erbenson/doc/yaboot-faq.html#scsi_boot_path
>
> read the whole section very carefully and try to see if you can get this
> working. I am afraid I cannot help you out more here since this is getting
> too complicated and I would have to be physically there at your machine to be
> more helpful :)
>
> But I am sure you will figure it out!
>
> Best of Luck.
>
> -- Avinash Gupta (agupta@mediaone.net)
Mr.Palacios,
Or if I may, Juan, please, call me CL ;-))
I spent about 5 hours tonight, after reading the posts from you and
Avinash, doing as you and he suggested, in [root]. Thank you for the info
you supplied as it does allow for a more comprehensive examination of
system status. Regretfully, however, I have not resolved the situation
with a "magic bullet"
As referenced above in the note to Avinash, I intend to spend the next
days (nights) at least, becoming more familiar with the terminology
and methodology of Linux before posting further. During that time I will
also take your suggestion re: device positioning/ jumpering, and if necessary
reconstruct the entire configuration and installation of all drives.
Also, I can see that you will make a most gracious and valuable
contribution to this group.
Sincerest appreciation,
CL
Juan Manuel Palacios wrote:
Hello Mr. Simco. I've been following your thread and I think I have
a couple of things to suggest. Traditionally the Linux kernel has had
problems dealing with drives that have more than 16 partitions, it can't
even read past the 15th. I don't think that's bugging you since I read
you only had a "couple" of partitions in your Mac OS drive. But I'm
afraid we could be in front of a similar scenario with the number of
drives. I'm not sure about this since I've not encountered myself, but
is a possibility. You said that the drive was being recognized as "hde",
so maybe Linux has problems getting that far. Why don't you first issue
the following command at the console prompt:
dmesg >> dmesg.txt
That generates a text file with the output of the boot-up sequence.
That is, you'll read there the practically unreadable text you see upon
Linux boot-up, which gives you practically all the information you need
about how Linux sees your hardware. Then you can read it with either one:
more dmesg.txt
less dmesg.txt
I personally prefer "less" since it lets you scroll up AND down the
text with the arrow keys, since "more" only lets you scroll down. Read
carefully and try to spot any messages there that refers to the
recognition of your ide (that was VERY ingenious Avinash) drives. If you
do see any type of problem with the drives (maybe due to the excess in
number of them) try re-jumpering them in order to make your Mac OS
partition "hdb". Is this possible? At least try making it anything
smaller than "e". Then edit your yaboot.conf file and see how it goes
from there. Let me know your luck.
I'll leave you now to it. I hope I was helpful. Sincerely,...
Juan.
This archive was generated by hypermail 2a24 : Fri Jan 04 2002 - 00:42:25 MST