Re: B&W G3 + Yellow Dog... close, but not bootin' yet.

[Sam Pogany <samp@pogany.net>]

On Oct 23, 2005, at 6:05 PM, Ethan Benson wrote:

> On Sun, Oct 23, 2005 at 10:44:54AM -0400, Sam Pogany wrote:
>
>>> this makes no sense, clearly OF is capable of reading your slave
>>> device since it sucessfully loads the first stage, and the first  
>>> stage
>>> successfully loads yaboot (second stage), but yaboot then cannot  
>>> read
>>> its config file from what seems to be a perfectly valid device  
>>> path...
>>>
>>             Agree, seems inconsistent.  Is there a way to manually
>> reformat
>>             bootstrap partition and reinstall those files?  Am
>> thinking maybe
>>             there was some hiccup with YDL installer.  The rest of
>> the install
>>             seems fine, I can do any Linux stuff I want once it's
>> booted
>>             from the CD-ROM.
>>
>
> mkofboot does the exact same thing as ybin, except it completly zeros
> the bootstrap partition before rebuilding the fs.
             Ran mkofboot instead of ybin, it asks if you want to  
format as HFS, said yes.
             Install onto bootstrap partition apparently OK, no  
difference in results.
...............

>>>
>>> enter:  setenv boot-device ultra1:\\:tbxi
>>>        boot
>>>
>>> and see if that changes anything.
>>>
>>             Did those things, boot-device setting now reads:
>>             boot-device        ultra1:,\\:tbxi        hd:,\\:tbxi
>>             (ie, there are 2 values on that line, only the first one
>> changed)
>>
>
> the second is the OF default.
>
> try ultra1:2,\\:tbxi
             No difference, same errors as below.  Tried 'ide1:' and  
'hd1:', they are
             obviously also not right, got blinking ? at startup.

             Sorry I can't give you more to go on, behavior just  
doesn't seem to change.
             What really gets me is that I can boot from CD-ROM, so  
YDL partitions
             on the disk must be readable.

             I'm tempted to change disk setup so I'm installing  
everything onto ultra0/hda,
             but if I'm going to that much trouble, I'm going to add  
bigger drive.boot=/dev/hdb2

             FWIW, yaboot.conf looks like this at the moment:

# yaboot.conf generated by anaconda
bgcolor=green
device=ultra1:
boot=/dev/hdb2
init-message="Welcome to Yellow Dog Linux! Hit <TAB> for boot options."
partition=5
timeout=50
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
delay=10
enablecdboot
macosx=/dev/hda6
macos=/dev/hdb3
defaultos=macosx

image=/boot/vmlinux-2.6.10-1.ydl.1
     label=linux
     read-only
     initrd=/boot/initrd-2.6.10-1.ydl.1.img
     root=/dev/hdb5
     append="rhgb quiet"

>>
>>             Here's the startup screen (blue):
>>
>>             First stage Yellow Dog Linux bootstrap
>>             Press l for Yellow Dog Linux
>>                      m for MacOS
>>                      x for MacOSX
>>                     c for CDROM
>>             Stage 1 Boot:
>>
>>             When I choose 'l', I get this (black screen):
>>
>>                 Can't open device </pci@80000000/pci-bridge@d/pci-
>> ata@1/@0/disk@1:0>
>>
>
> yaboot tries to open the raw disk device here (equiv to /dev/hdb in  
> unix)
>
> which actually I think it shouldn't be doing for the config file, it
> should only do this when its trying to read a non-apple partition.
>
>
>>                 /pci@80000000/pci-bridge@d/pci-ata@1/@0/disk@1:2,\
>> \yaboot.conf: Unable to open file, Invalid device
>>
>
> complains about previous error here.
>
>
>>                 Can't open config file
>>                 Welcome to yaboot version 1.3.11
>>                 Enter "help" to get some basic usage information
>>                 boot:
>>
>>                 'x' -- works, boots OSX
>>                 'c' -- works, boots installer from CDROM
>>                 'm' -- odd, screen blacks out for a second, then
>> returns to blue menu, no error
>>
>
> something is wrong with the macos= boot entry it seems.
>
> -- 
> Ethan Benson
> http://www.alaska.net/~erbenson/
>