Re: Re: Re: install 2nd HD G5
Hi everyone, I've just now gotten back to my G5 to see if I could make some progress. I've tried out everyone's suggestions and here's where I stand: I looked up the OpenFirmware aliases on my machine. The ones of interest are as follows: sata/ht/[EMAIL PROTECTED]/k2-sata-root hd /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 ultra0 /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 ultra1 /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 sd0 /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 sd1 /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 sd2 /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 sd3 /ht/[EMAIL PROTECTED]/k2-sata-root/[EMAIL PROTECTED]/disk0 k2-sata /ht/[EMAIL PROTECTED]/k2-sata-root pci0/[EMAIL PROTECTED],f000 first-boot /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/k2-sata second-boot /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/disk last-boot /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/ethernet From Paddy's suggestions to type in boot sdb1:,\\yaboot at the OF prompt, I was expecting to find an sdb1 alias, but I don't seem to have one. I'm not exactly sure which alias points to my 2nd HD, but I'd venture to guess ultra1 and sd1 both do but I'm unsure what sd2 and sd3 are. I also commented out the ofboot ine in my yaboot.conf. Here's its current state: boot=/dev/sdb2 device=/[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: partition=3 root=/dev/sdb3 timeout=100 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot ##ofboot=/[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2 enablecdboot enableofboot macosx=/dev/sda9 image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old And the debug trace: DEBUG: ofboot set to `/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2' ybin: DEBUG: macosx set to `/[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:9' from `/dev/sda9' ybin: DEBUG: OS=4 ybin: DEBUG: /bin/sh /usr/lib/yaboot/ofboot 4 bootyaboot 10 0 yaboot GNU l /[EMAIL PROTECTED]/[EMAIL PROTECTED]:2 ,\\yaboot macosx MacOSX x /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:9 ,\\:tbxi cd CDROM c cd: ,\\:tbxi of OpenFirmware o quit now ybin: DEBUG: set magicboot to /tmp/ofboot.O3xXhS ybin: DEBUG: boot-device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2,\\:tbxi This line in particular has changed since taking out the ofboot line: /bin/sh /usr/lib/yaboot/ofboot 4 bootyaboot 10 0 yaboot GNU l /[EMAIL PROTECTED]/[EMAIL PROTECTED]:2 ,\\yaboot macosx MacOSX x It now points to [EMAIL PROTECTED]/[EMAIL PROTECTED]:2 instead of the former /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2. I think this is the crux of my problem. Somehow, I need to figure out the exact path of the second partition on my second hard drive where yaboot lives. I'm not sure how to do this. Also, I tried to run pdisk, but it apparentlt isn't on the Ubuntu live CD. thanks, wes
Re: Re: Re: install 2nd HD G5
Hi again, Success! I readded the ofboot line to the yaboot as follows and changed it as follows: ofboot=sd1:2 I also modified the device line of yaboot.conf to: device=sd1: Now everything works as it should and I am current finishing up the Debian install. Muchas gracias for everyone's help, wes
Re: Re: Re: install 2nd HD G5
On Sat, 2005-06-04 at 20:50 -0700, Wesley Smith wrote: Please excuse the many messages...I tried the following at the openfirmware prompt: boot /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2,\yaboot What kind of partition map do you have on that disk ? What does pdisk -l /dev/sdb displays ? Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: install 2nd HD G5
You're right that I don't need to do the source thing. I do have a question about chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin however. By doing this command, will ybin now access the modified yaboot.conf in sdb3? What is it that chroot is doing in this command? I realize this is a basic question, but I'm kind of fuzzy on what the function of chroot is. thanks, wes On 6/4/05, Jeff Green [EMAIL PROTECTED] wrote: Wesley writes: Ok, after I mounted /dev/sdb3 I did: chroot /mnt/ubuntu /bin/bash source /etc/profile Is this what you mean by chroot with ybin? When you say ybin will take the yaboot.conf in the /etc of ubuntu are you referring to the yaboot.conf created by the live CD and not the one in /mnt/ubuntu where I mounted /dev/sdb3? thanks, wes Yes, but I'm not sure why you're doing the source. Do you need a particular environment? (Also...I'm a ksh person...I thought that bash used the sysV conventions, e.g. . /etc/profile) Anyway, you can also do it directly, e.g. chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin. jeff
Re: Re: install 2nd HD G5
Wesley writes: Ok, after I mounted /dev/sdb3 I did: chroot /mnt/ubuntu /bin/bash source /etc/profile Is this what you mean by chroot with ybin? When you say ybin will take the yaboot.conf in the /etc of ubuntu are you referring to the yaboot.conf created by the live CD and not the one in /mnt/ubuntu where I mounted /dev/sdb3? thanks, wes Yes, but I'm not sure why you're doing the source. Do you need a particular environment? (Also...I'm a ksh person...I thought that bash used the sysV conventions, e.g. . /etc/profile) Anyway, you can also do it directly, e.g. chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin. jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: install 2nd HD G5
Wesley writes: Ok, after I mounted /dev/sdb3 I did: chroot /mnt/ubuntu /bin/bash source /etc/profile Is this what you mean by chroot with ybin? When you say ybin will take the yaboot.conf in the /etc of ubuntu are you referring to the yaboot.conf created by the live CD and not the one in /mnt/ubuntu where I mounted /dev/sdb3? thanks, wes You can also try ybin -C /mnt/ur.mnt.pt/etc/yaboot.conf but then that mixes ubuntu stuff with your stuff. It'll probably work but sometimes it won't. jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: install 2nd HD G5
Wesley writes: You're right that I don't need to do the source thing. I do have a question about chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin however. By doing this command, will ybin now access the modified yaboot.conf in sdb3? What is it that chroot is doing in this command? I realize this is a basic question, but I'm kind of fuzzy on what the function of chroot is. thanks, wes Things get complicated, and chroot is a way of simplifying the situation. Most commands do not run in isolation, i.e. they're not statically compiled nor run independent of support files. As a consequence chroot allows you to run that command in the environment that it was intended to run. So by doing a chroot on the ybin, you not only selected the proper yaboot.conf, but also you used a different ybin, i.e. the one on your installed system and not the one on the ubuntu livecd. It then used the OF support files on *your* installed system and everything else that your yaboot.conf is implicitly relying upon. It's really pretty nifty. jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: install 2nd HD G5
Hi guys, thanks for the info. Here's what I've done: --mount sdb3 --edit yaboot.conf --chroot /mnt/sdb3 (where sdb3 is mounted) --mount -t proc none /proc --ybin -v I also tried --mount sdb3 --edit yaboot.conf --chroot /mnt/sdb3 (where sdb3 is mounted) --mount -t proc none /proc --exit --mount /mnt/sdb3 /usr/sbin/ybin neither of these have solved by booting problem. I am completely stumped here. Are there config files somewhere that ybin create that I can look for on sdb3 or sdb2 to see if my yaboot.conf changes are reflected in the ybin -v output? thanks, wes On 6/4/05, Jeff Green [EMAIL PROTECTED] wrote: Wesley writes: You're right that I don't need to do the source thing. I do have a question about chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin however. By doing this command, will ybin now access the modified yaboot.conf in sdb3? What is it that chroot is doing in this command? I realize this is a basic question, but I'm kind of fuzzy on what the function of chroot is. thanks, wes Things get complicated, and chroot is a way of simplifying the situation. Most commands do not run in isolation, i.e. they're not statically compiled nor run independent of support files. As a consequence chroot allows you to run that command in the environment that it was intended to run. So by doing a chroot on the ybin, you not only selected the proper yaboot.conf, but also you used a different ybin, i.e. the one on your installed system and not the one on the ubuntu livecd. It then used the OF support files on *your* installed system and everything else that your yaboot.conf is implicitly relying upon. It's really pretty nifty. jeff
Re: Re: Re: install 2nd HD G5
ps...here/s the output of ybin -debug where root is my sdb3 mount point: ybin: DEBUG: macosx set to `/[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] :9' from `/dev/sda9' ybin: DEBUG: OS=4 ybin: DEBUG: /bin/sh /usr/lib/yaboot/ofboot 4 bootyaboot 10 0 yaboot GNU l /ht@ 0.f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2 ,\\yaboot macosx MacOSX x / [EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:9 ,\\:tbxi cd CDROM c cd: , \\:tbxi of OpenFirmware o quit now ybin: DEBUG: set magicboot to /tmp/ofboot.ytmPmc ybin: DEBUG: boot-device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2, \\:tbxi On 6/5/05, Wesley Smith [EMAIL PROTECTED] wrote: Hi guys, thanks for the info. Here's what I've done: --mount sdb3 --edit yaboot.conf --chroot /mnt/sdb3 (where sdb3 is mounted) --mount -t proc none /proc --ybin -v I also tried --mount sdb3 --edit yaboot.conf --chroot /mnt/sdb3 (where sdb3 is mounted) --mount -t proc none /proc --exit --mount /mnt/sdb3 /usr/sbin/ybin neither of these have solved by booting problem. I am completely stumped here. Are there config files somewhere that ybin create that I can look for on sdb3 or sdb2 to see if my yaboot.conf changes are reflected in the ybin -v output? thanks, wes On 6/4/05, Jeff Green [EMAIL PROTECTED] wrote: Wesley writes: You're right that I don't need to do the source thing. I do have a question about chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin however. By doing this command, will ybin now access the modified yaboot.conf in sdb3? What is it that chroot is doing in this command? I realize this is a basic question, but I'm kind of fuzzy on what the function of chroot is. thanks, wes Things get complicated, and chroot is a way of simplifying the situation. Most commands do not run in isolation, i.e. they're not statically compiled nor run independent of support files. As a consequence chroot allows you to run that command in the environment that it was intended to run. So by doing a chroot on the ybin, you not only selected the proper yaboot.conf, but also you used a different ybin, i.e. the one on your installed system and not the one on the ubuntu livecd. It then used the OF support files on *your* installed system and everything else that your yaboot.conf is implicitly relying upon. It's really pretty nifty. jeff
Re: Re: Re: install 2nd HD G5
Please excuse the many messages...I tried the following at the openfirmware prompt: boot /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2,\yaboot and got the error MAC-PARTS: specified partition is not valid BOOTP/BSPD failed, no FILENAME specified|id any thoughts? wes On 6/4/05, Wesley Smith [EMAIL PROTECTED] wrote: ps...here/s the output of ybin -debug where root is my sdb3 mount point: ybin: DEBUG: macosx set to `/[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] :9' from `/dev/sda9' ybin: DEBUG: OS=4 ybin: DEBUG: /bin/sh /usr/lib/yaboot/ofboot 4 bootyaboot 10 0 yaboot GNU l /ht@ 0.f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2 ,\\yaboot macosx MacOSX x / [EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:9 ,\\:tbxi cd CDROM c cd: , \\:tbxi of OpenFirmware o quit now ybin: DEBUG: set magicboot to /tmp/ofboot.ytmPmc ybin: DEBUG: boot-device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:2, \\:tbxi On 6/5/05, Wesley Smith [EMAIL PROTECTED] wrote: Hi guys, thanks for the info. Here's what I've done: --mount sdb3 --edit yaboot.conf --chroot /mnt/sdb3 (where sdb3 is mounted) --mount -t proc none /proc --ybin -v I also tried --mount sdb3 --edit yaboot.conf --chroot /mnt/sdb3 (where sdb3 is mounted) --mount -t proc none /proc --exit --mount /mnt/sdb3 /usr/sbin/ybin neither of these have solved by booting problem. I am completely stumped here. Are there config files somewhere that ybin create that I can look for on sdb3 or sdb2 to see if my yaboot.conf changes are reflected in the ybin -v output? thanks, wes On 6/4/05, Jeff Green [EMAIL PROTECTED] wrote: Wesley writes: You're right that I don't need to do the source thing. I do have a question about chroot /mnt/ur.sdb3.mnt.pt /usr/sbin/ybin however. By doing this command, will ybin now access the modified yaboot.conf in sdb3? What is it that chroot is doing in this command? I realize this is a basic question, but I'm kind of fuzzy on what the function of chroot is. thanks, wes Things get complicated, and chroot is a way of simplifying the situation. Most commands do not run in isolation, i.e. they're not statically compiled nor run independent of support files. As a consequence chroot allows you to run that command in the environment that it was intended to run. So by doing a chroot on the ybin, you not only selected the proper yaboot.conf, but also you used a different ybin, i.e. the one on your installed system and not the one on the ubuntu livecd. It then used the OF support files on *your* installed system and everything else that your yaboot.conf is implicitly relying upon. It's really pretty nifty. jeff
