Problem with yabootconfig

[Soetji Anto]

I tried to install FC3 along with OSX on my iBook G3 following instructions on
http://www.bytebot.net/geekdocs/ibook/fedorappc.html. I broke out into a shell with
Ctrl+Alt+Fn+F2 at the end of the CD installation when it asked for reboot.

I didn't find /etc/yaboot.conf instead I found it at /mnt/sysimages/etc/yaboot.conf.
The file has already:
initrd=/boot/initrd-2.6.9-1.667.img

When I run:
yabootconfig -r /dev/hda11 -b /dev/hda13

I got the following error:
id: unknown group name: 0
/mnt/sysimage/sbin/yabootconfig: line 455: [: != unary operator expected
yabootconfig: / does not appear to be a valid root filesystem

Please help.

Thanks,
Soetji

[Christian Walther]

Soetji Anto wrote:

>  I didn't find /etc/yaboot.conf instead I found it at 
>  /mnt/sysimages/etc/yaboot.conf. The file has already:
>  initrd=/boot/initrd-2.6.9-1.667.img
>
>  When I run:
>  yabootconfig -r /dev/hda11 -b /dev/hda13
>
>  I got the following error:
>  id: unknown group name: 0
>  /mnt/sysimage/sbin/yabootconfig: line 455: [: != unary operator 
>  expected
>  yabootconfig: / does not appear to be a valid root filesystem 
Try
yabootconfig -r /dev/hda11 -b /dev/hda13 -t /mnt/sysimage

While we're at it, here's my own experience with yabootconfig in a HD 
install from the re1115.0 ISOs I did yesterday:
o At the end of the install, there's no yaboot.conf anywhere
o Running yabootconfig fails because it expects the device from which 
/mnt/sysimage is mounted to be in /dev/, but it is /tmp/hda13. After a 
few failed attempts at fixing yabootconfig to cope with this situation, 
I got it to work by just hardcoding the right values into yabootconfig.

  -Christian

[Soetji Anto]

I tried:
yabootconfig -r /dev/hda11 -b /dev/hda13 -t /mnt/sysimage

and got this:
id: unknown group name: 0
/mnt/sysimage/sbin/yabootconfig: line 455: [: != unary operator expected
Install yaboot bootstrap on /dev/hda13 to boot from Linux from /dev/hda11? [Yes]
Creating a simple /mnt/sysimage/etc/yaboot.conf
yabootconfig: Cannot find a kernel, please locate one
Enter path to a kernet image:

When I entered "/boot/initrd-2.6.9-1.667.img" I got "No such file or
directory"
Then I entered "/mtn/sysimage/boot/initrd-2.6.9-1.667.img" I got:
yabootconfig: Unable to determine OpenFirmware device name to /dev/hda, aborting...

Any thoughts?

Thanks,
Soetji

Christian Walther wrote:
>  Soetji Anto wrote:
>  
> > I didn't find /etc/yaboot.conf instead I found it at 
> > /mnt/sysimages/etc/yaboot.conf. The file has already:
> > initrd=/boot/initrd-2.6.9-1.667.img
> >
> > When I run:
> > yabootconfig -r /dev/hda11 -b /dev/hda13
> >
> > I got the following error:
> > id: unknown group name: 0
> > /mnt/sysimage/sbin/yabootconfig: line 455: [: != unary operator expected
> > yabootconfig: / does not appear to be a valid root filesystem
>  
>  
>  Try
>  yabootconfig -r /dev/hda11 -b /dev/hda13 -t /mnt/sysimage
>  
>  While we're at it, here's my own experience with yabootconfig in a HD 
>  install from the re1115.0 ISOs I did yesterday:
>  o At the end of the install, there's no yaboot.conf anywhere
>  o Running yabootconfig fails because it expects the device from which 
>  /mnt/sysimage is mounted to be in /dev/, but it is /tmp/hda13. After a 
>  few failed attempts at fixing yabootconfig to cope with this situation, 
>  I got it to work by just hardcoding the right values into yabootconfig.
>  
>   -Christian
>  
>  
>  _______________________________________________
>  Fedora-ppc mailing list
>  Fedora-ppc(a)lists.infradead.org
>  http://lists.infradead.org/mailman/listinfo/fedora-ppc
>

[Christian Walther]

Soetji Anto wrote:

>  yabootconfig: Cannot find a kernel, please locate one
>  Enter path to a kernet image:
>
>  When I entered "/boot/initrd-2.6.9-1.667.img" I got "No such file or 
>  directory"
>  Then I entered "/mtn/sysimage/boot/initrd-2.6.9-1.667.img" 
"Kernel image" here means the kernel itself, not the initrd. So, enter 
"/mnt/sysimage/boot/vmlinuz-2.6.9-1.667". You have to add the initrd to 
yaboot.conf yourself afterwards.

>  I got:
>  yabootconfig: Unable to determine OpenFirmware device name to 
>  /dev/hda, aborting... 
Are you sure it says "/dev/hda", not "/tmp/hda"? Because that was the

problem I had. I'd guess it should work with "/dev/hda". If not, what's

the output of "ofpath /dev/hda"? If it says something like "no such 
file", what's the output of "ls /dev/hd*"? And what's the output of

"mount | grep sysimage"?

If it does say "/tmp/hda" (like it did in my ISO install), then we 
should probably file a bug report against either yabootconfig or 
Anaconda (or whatever). Does anyone know what the reason for mounting 
/mnt/sysimage from /tmp/hda<x> instead of /dev/hda<x> is?

  -Christian

[Soetji Anto]

Christian Walther wrote:
>  Soetji Anto wrote:
>  
> > yabootconfig: Cannot find a kernel, please locate one
> > Enter path to a kernet image:
> >
> > When I entered "/boot/initrd-2.6.9-1.667.img" I got "No such file or 
> > directory"
> > Then I entered "/mtn/sysimage/boot/initrd-2.6.9-1.667.img"
>  
>  
>  "Kernel image" here means the kernel itself, not the initrd. So, enter 
>  "/mnt/sysimage/boot/vmlinuz-2.6.9-1.667". You have to add the initrd to 
>  yaboot.conf yourself afterwards.
>   
I tried also "/mnt/sysimage/boot/vmlinuz-2.6.9-1.667" and got the same error.

> > I got:
> > yabootconfig: Unable to determine OpenFirmware device name to 
> > /dev/hda, aborting...
>  
>  
>  Are you sure it says "/dev/hda", not "/tmp/hda"? Because that was the
>
>  problem I had. I'd guess it should work with "/dev/hda". If not, what's
>
>  the output of "ofpath /dev/hda"? If it says something like "no such 
>  file", what's the output of "ls /dev/hd*"? And what's the output
> of 
>  "mount | grep sysimage"?
>   
I am pretty sure it said "/dev/had". I can't reproduce it now since yaboot
worked after I did the following. I re-ran the install CDs and updated FC3. Then I edited
"/etc/fstab" with "/dev/hda11" instead of "LABEL=/" in the
first line and did "chroot /mnt/sysimage". After that yaboot worked.

Now if only I can get the gui work on my iBook G3...

Thanks,
Soetji

Soetji Anto wrote:

>  Now if only I can get the gui work on my iBook G3...  

as root
# system-config-display --reconfig

or remove your xorg.conf
# mv /etc/X11/xorg.conf  ~/xorg.conf.postinstall
# system-config-display

generic-lcd 800x600 or 1024x768 ?

i had a similiar problem with my powerbook g4

-- 
shrek-m

[Soetji Anto]

>  as root
>  # system-config-display --reconfig
>   
Tried that after booting with "Linux 3" and got this error:
Trying with card: ATI Rage 128 Mobility
Couldn't start X server on card 0
Error, failed to start X server

>  or remove your xorg.conf
>  # mv /etc/X11/xorg.conf  ~/xorg.conf.postinstall
>  # system-config-display
>   
This one worked! Thank you. Thank you. Now I have GUI!

I wonder what's wrong with the original xorg.conf. I see some differences in the
"Monitor" Section.

>  generic-lcd 800x600 or 1024x768 ?
>   
1024x768

Thanks,
Soetji

Soetji Anto wrote:

>  I wonder what's wrong with the original xorg.conf. I see some 
>  differences in the "Monitor" Section. 

i do not know.

created by
"pyxf86config"  vs  "system-config-display"

ModelName
"Unknown monitor"  vs  "LCD Panel 1024x768"

Driver
"fbdev"  vs  "nv"

BoardName
"Framebuffer driver (generic)"  vs  "NVIDIA GeForce FX (generic)"

Depth
"8"  vs  "24"

Modes
"640x480"  vs  "1024x768" "800x600" "640x480"

-- 
shrek-m