Subject: Re: YDL install w/ multiple drives
From: C.L. Simco (clsimco@random-specific.com)
Date: Fri Jan 04 2002 - 21:05:55 MST
Juan,
This is a little "off topic" of the thread here, but I'm hoping that by
asking
you this question, I'll be able to resume the thread and resolve the
situation
at a later date after doing some work as I stated in my last message to you
and Avinash.
As I stated, I realized that I need a much firmer grasp of the language of
the command line if I am to ask intelligent questions and do things once
I receive suggestions or answers. Also, the language that Open Firmware
speaks, seems more than invaluable.
So, am I looking for a book on Unix, or Linux? And will a comprehensive
volume include what I would call a "dictionary, or thesaurus" so to speak,
of the terms, files, filenames, commands etc.? Or would I be looking for
something of that nature, separately? As well, a similar volume or tutorial
re: Mac and or Linux OF. I realize that YDL is based on Red Hat, but
development on the two diverged at some point in the version history.
Which version of a Red Hat book would be most relevant and useful to
YDL? Are there books on Mac and Linux OF? Or is there a site on the
web that does the above, "dictionary" function?
Juan Manuel Palacios wrote:
> <snip>... Did you find anything interesting with "dmesg" after
> all, or are you still looking through the file? I suggest to swap the
> drives before you go any further. With that we can rule out many things
> like faulty jumpers, wires or connectors.
Yes I did indeed, find OF interesting and possibly something of a lead
but I don't understand the language well enough to be certain. I intend
to start by disconnecting all but the two drives that are important, this
weekend,
and see if that will simplify things a bit. Then later, I can add things back
if it is possible.
> Also, as Abinash suggested,
> try finding the OF path of your drives any time you change your physical
> setup. That will certainly teach you about your computer (also try
> rerunning the "dmesg" combo every time to see if you can spot important
> changes in configuration).
I will, and part of the reason for my questions to you above.
> Are you familiar with Open Firmware? Just in
> case you don't know, boot up holding "cmmd-opt-o-f" and you'll be taken
> to Open Firmware setup. That is the basest configuration and interaction
> you can have with your computer. It is software independent and it
> controls the hardware, so be VERY careful there!!! To begging with just
> type "printenv" at the prompt and have fun reading. You'll see a line
> about "default boot-device", followed by an amazingly long text that
> ends with "tbxi". That is what Linux refers to when it talks about the
> real OF path to the device.
It is not possible to "literally" use that line as the path Linux is asking
for, is it?
Linux speaks "French" while Mac speaks "English", (as an analogy) therefor
needing to find a way to translate what each are saying and understanding?
> Funny right? To exit Open Firmware just type
> "mac-boot" and the computer should keep on with the default device for
> start up.
>
> Again, as I said before, don't hesitate to write if you run into
> any rabbit holes. Sincerely,...
>
> Juan.
Thanks again,
CL
>
>
> On Friday, January 4, 2002, at 03:28 AM, C.L. Simco wrote:
>
> > 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 - 21:19:34 MST