Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Thu, Sep 23, 2010 at 10:04 PM, Joseph Jezak jos...@gentoo.org wrote: My responses are inline this time. It's easier when there's so much going on! On 09/23/10 16:41, Mark Knecht wrote: Two pictures posted: Top half of boot screen: http://www.flickr.com/photos/29328...@n03/5018717650/ Bottom half of boot screen http://www.flickr.com/photos/29328...@n03/5018718202/ Okay, these look exactly as expected. You've booted into the shell fine and the kernel does detect the hard drive fine. It appears that the disk was not cleanly unmounted, which is what the messages in the bottom picture indicate. Once you get USB working so we can type into the console, we'll take a look at what's actually going on. Full USB HID support is built as modular. I don't seem to be able to change it to built in. make menuconfig is only giving me modular or not set. (Kernel config USB info this is set is at the end) If you use menuconfig and you go to the Help option, it will tell you what dependencies need to be set in order to build the module. Most likely, you did not set the USB subsystem itself to be built in. lspci says the controller is an Apple controller and the driver is 'macio' which seems sensible. I see it in the boot screen I think. That driver is built in, but the PATA_MACIO driver is not: (chroot) livecd linux # cat .config | grep MACIO # CONFIG_PATA_MACIO is not set CONFIG_ADB_MACIO=y (chroot) livecd linux # Maybe I've mistakenly left the right disk driver out of the kernel thinking the hardware was SATA based? Does the PATA_MACIO option need to be set for the Mac Mini? I don't understand how this kernel config would have ever worked befor unless I'm confusing where it came from. You're using the old style driver which results in devices named hdX#. It's called IDE_PMAC. The new driver which uses the sdX# naming convention (and uses libpata), is called PATA_MACIO. Does the append=init=/bin/bash command allow the kernel to load drivers or do I need to build USBHID into the kernel to get the keyboard to work at this level of boot? I would built it in for now, it'll be easier since there's no good way to get into the system to tell it to load the drivers. -Joe Hi Joe, OK, I finished the emerge -e @world. No changes. Still doesn't boot. I've put the append=init=/bin/bash back in and booted. I'm at the console and this is confusing. It seems that /dev/hda4 is probably mounted. I can do ls -al / I see all the stuff I'd expect to see - /bin, /boot, etc. - and also the two downloads necessary to do the install - portage-latest.tar.bz2 stage3-ppc-20100919.tar.bz2 - so I must be looking at the right physical hard drive. However even though I see that stuff simple commands like df don't work yielding something like this: (none)/ #df df: cannot read table of mounted file systems: No such file or directory Additionally, there is nothing at all under /proc. It's empty! Cheers, Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Sat, Sep 25, 2010 at 8:12 AM, Joseph Jezak jos...@gentoo.org wrote: SNIP None of these things are weird, they're expected! Really? OK - cool then. When you start the system with init=/bin/bash, the only thing your system does is start bash as the only process. Things like mounting proc, remounting the root file system r/w (and setting up mtab) aren't done because they're part of the normal startup process. I need to find a good _SIMPLE_ book on how Linux boots. I'm just a long time use with no real sys admin background so for a decade or longer I just want the things go by at boot and then use my system. Can you run fsck.ext3 from the shell that starts when you replace init? I cannot due to the same sort of message I get when trying to boot: e2fsck_check_if_mount: Can't check if filesystem is mounted due to missing mtab file fsck.ext3: Device or resource busy while trying to open /dev/hda4 Filesystem mounted or opened exclusively by another program? For kicks I tried umount /dev/hda4 but that complains about the missing mtab file also. It seems from the man page I could force it but I didn't want to do that, and again if I did and it even worked then where would the system read fsck.ext3 from to do the check since it's on /dev/hda4 itself? Also, which version of udev are you using? I forgot to ask if you're running ~ppc instead of ppc, you may want to try switching to the PATA_MACIO driver in order for the system to work properly. udev would be whatever comes with a stable ppc system these days. Other than running ~ppc portage and sandbox the machine is currently all stable with no USE flags. The make.conf file is pretty much empty other than the stuff the install has me put in. (Which mirrors to sync from, etc.) I've gone back and done a couple more experiments: 1) So far anything I try that refers to the drive as /dev/sda4 results in a VFS not syncing type error so at least as far as the boot process goes hda4 seems to be the right device. 2) I tried building in the PATA_MACIO driver but that by itself didn't change anything: (chroot) livecd / # cat /usr/src/linux/.config | grep MACIO CONFIG_PATA_MACIO=y CONFIG_ADB_MACIO=y (chroot) livecd / # The boot still fails at the same point with the same message. Possibly some other ATA driver is being selected ahead of this one and maybe it needs to be removed from the kernel? I don't know what to remove though so I'm sort of stuck on that account. 3) If this is a kernel config issue - and it seem plausible that it is - then I'll point out that the kernel config page of the Gentoo PPC Istall Guide had a possible command that didn't work for me: http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=1chap=7 Specifically: make pmac32_defconfig which supposedly will make a config file that would boot most 32-bit machines. Unfortunately the command doesn't work for me on current kernels. The install guide should be updated to either remove this or make it more clear if I need to do anything more than that command in the /usr/src/linux directory. I've looked around at lots more stuff in my kernel config and compared it to what the Install guide says. I don't see any differences but I suspect there probably are. Thanks! - Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Sat, Sep 25, 2010 at 1:40 PM, Mark Knecht markkne...@gmail.com wrote: SNIP 3) If this is a kernel config issue - and it seem plausible that it is - then I'll point out that the kernel config page of the Gentoo PPC Istall Guide had a possible command that didn't work for me: http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=1chap=7 Specifically: make pmac32_defconfig which supposedly will make a config file that would boot most 32-bit machines. Unfortunately the command doesn't work for me on current kernels. The install guide should be updated to either remove this or make it more clear if I need to do anything more than that command in the /usr/src/linux directory. SNIP Nix this comment. I got the command to work and am going back to ground zero on the kernel config. We'll see what happens. Sorry for the noise. Just frustrated after weeks of this. Mac is just harder than PC I suppose... Thanks, Mark
