Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Thu, Oct 7, 2010 at 10:34 AM, Joseph Jezak jos...@gentoo.org wrote: Okay, so we fixed the first thing. That's good. :) Can you attach your whole kernel config? I'm wondering if maybe udev isn't running properly due to a misconfiguration. -Joe Attached unless GMail does something to it. Thanks, Mark Another busy week, but I think we might have your answer. Disable these options in your kernel config, recompile and give it a try: CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y I think these options interfere with udev. -Joe Thank you Joe. For the first time in a couple of months the machine just booted. Note that I didn't easily find CONFIG_SYSFS_DEPRECATED in make menuconfig so I only disabled CONFIG_SYSFS_DEPRECATED_V2 which was enough to allow it to boot. I took a quick look at the PPC install guide and frankly I don't see instructions there to disable this option, although I have done this on other machines. Is it just me or are the instructions actually not in the kernel config section. If they are truly missing then it would be great if someone could update that. Anyway, it seems completely unreasonable for me, after all this, to just say thanks for the help. It doesn't begin to represent how appreciative I am of the time you spent looking into this with me. I really am indebted. Cheers, Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Sun, Sep 26, 2010 at 10:36 AM, Joseph Jezak jos...@gentoo.org wrote: On 09/25/10 16:40, Mark Knecht wrote: SNIP Okay, let's try a few things now that we can boot the machine (even if it's not all the way!). First, lets mount proc: # mount -t procfs none /proc OK - to me this doesn't look good: # mount -t procfs none /proc mount:none has wrong device number or fs type procfs not supported on the off chance you menat proc instead of procfs I tried it that way and got a slightly more reasonable message: # mount -t proc none /proc can't create lock file /etc/mtab~1038: Read-only file system (use -n flag to override) Now, try fsck.ext3 again. Does it work? Worked fine. fsck.ext3 said it was clean Next, let's remount the root file system read/write so we can modify files: # mount -o remount,rw / Seemed to work. Got this message: EXT3-fs: (hda4):using internal journal We'll copy the current mount information from proc to /etc/mtab and see if that helps: # cp /proc/self/mounts /etc/mtab # mount -o remount,ro / Now, try fsck.ext3 again. Does it work? If so, try rebooting the system again. Does it boot now? Didn't boot but got a little farther. Doesn't complain about mtab anymore but still complains: * Checking root filesystem... fsck.ext3: No such file or directory while trying to open /dev/hda4 /dev/hda4: The superblock could not be read.. SNIP 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. The old PMAC_IDE driver is getting picked before the PATA_MACIO driver. If you'd like to try the newer driver, you'll need to disable the old one first. OK - I'll go back in and look at my kernel config again. Thought I'd post these results for now. Please remember, I'm extremely thankful for all your help and the help of others on this frustrating little problem. Cheers, Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Sun, Sep 26, 2010 at 1:52 PM, Mark Knecht markkne...@gmail.com wrote: On Sun, Sep 26, 2010 at 10:36 AM, Joseph Jezak jos...@gentoo.org wrote: SNIP The old PMAC_IDE driver is getting picked before the PATA_MACIO driver. If you'd like to try the newer driver, you'll need to disable the old one first. OK - I'll go back in and look at my kernel config again. Thought I'd post these results for now. OK, I switched to the newer PMAC_MACIO driver built into the kernel. Names changed but the result is the same - now it fails /dev/sda4 * Checking root filesystem... fsck.ext3: No such file or directory while trying to open /dev/sda4 /dev/sda4: The superblock could not be read or does not describe... Note one interesting difference with the newer driver is that I couldn't run fsck.ext3 until I rebuilt the kernel without all the power management stuff. Seems that by default fsck thought we were using the battery and deferred the check. Possibly I could have used fsck -f but I didn't want to take any chances. Anyway, the current state is that /dev/sda4 fails to mount. With the newer driver and modified kernel I had no problems with your bash instructions other than the procfs issue. Can I go further booting the machine by hand? If booting using the init=/sbin/bash allows me to check the disk but booting automatically does then it seems I should be able to walk through by hand doing all the steps until I get to the same failure point, correct? I think I'll Google around for web pages that describe that sort of thing. Sounds like an interesting thing to get educated on after using Linux for more than a decade... :-) Here's my current yaboot.conf and fstab files. Note that for now the use of /dev/hda2 is due to using the install CD. I suppose those will have to change to 'sd' if I ever get this machine to boot Gentoo again. (Still hoping Klaus' comment this morning about bad drives isn't the root cause here. The MacMini doesn't look easy to open for disk replacements...) Again, thanks for the ideas. Cheers, Mark (chroot) livecd / # cat /etc/yaboot.conf ## yaboot.conf generated by yabootconfig 1.0.8 ## ## run: man yaboot.conf for details. Do not make changes until you have!! ## ## For a dual-boot menu, add one or more of: ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ boot=/dev/hda2 #device=/p...@f400/at...@d/d...@0: device=hd: timeout=30 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot image=/boot/kernel-2.6.34-gentoo-r1 label=Gentoo-2.6.34-r1 #append=init=/bin/bash partition=4 root=/dev/sda4 read-only (chroot) livecd / # (chroot) livecd / # cat /etc/fstab /dev/sda4 /ext3noatime 0 1 /dev/sda3 none swapsw 0 0 /dev/cdrom /mnt/cdrom autonoauto,user 0 0 proc/procprocdefaults 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 (chroot) livecd / #
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
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 got USB working and with the append=init=/bin/bash in I can at least do cd and ls commands. All the devices you asked about exist - /dev/hda1 through 20, /dev/hdb1 through 20, /dev/null and /dev/zero - all exist. Doing know if it's a clue but in this append=init=/bin/bash state I was unable to do a reboot or a shutdown as it complained about missing initctl I think? Being that I made a number of changes to the kernel config to get USB working I remove the append line from yaboot.conf and tried booting into Gentoo proper but it's still stopping at the same place with the same message about no mtab file. I'll put the append back in and wait for further ideas. Thanks for sticking with me! Cheers, Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Fri, Sep 24, 2010 at 3:43 PM, Enlightened User li...@nc.rr.com wrote: On Sep 24, 2010, at 4:30 PM, Mark Knecht wrote: 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 got USB working and with the append=init=/bin/bash in I can at least do cd and ls commands. All the devices you asked about exist - /dev/hda1 through 20, /dev/hdb1 through 20, /dev/null and /dev/zero - all exist. Doing know if it's a clue but in this append=init=/bin/bash state I was unable to do a reboot or a shutdown as it complained about missing initctl I think? Being that I made a number of changes to the kernel config to get USB working I remove the append line from yaboot.conf and tried booting into Gentoo proper but it's still stopping at the same place with the same message about no mtab file. I'll put the append back in and wait for further ideas. Thanks for sticking with me! Cheers, Mark Assuming you are still stopping near: fsck.ext3... Can you confirm that /sbin/fsck.ext3 exists? If not, then emerge e2fsprogs. Barry The chroot is currently doing an emerge -e @world so I've shelled into the machine and am showing from that perspective. All the typical fsck programs are there and I rebuilt e2fsprogs a couple of days ago. livecd gentoo # ls /mnt/gentoo/sbin/fsck* fsck fsck.ext2 fsck.ext4 fsck.minix fsck.cramfs fsck.ext3 fsck.ext4dev livecd gentoo # When emerge -e @world completes I'll give it a reboot but somehow I don't have much faith that it will have fixed anything. Right now I feel it's either something missing from my kernel config, or some critical install step that I keep missing because of the way I read the document and maybe some step that listed inside a paragraph instead of being called out in purple like most of them are. (They are in there, like the locale-gen step and a few others...) I'll check back later when the rebuild is complete. Thanks! Cheers, Mark
Re: [gentoo-ppc-user] Re: Unsubscribe request
On Thu, Sep 23, 2010 at 7:48 AM, Dr John Krane jkr...@netzero.net wrote: You should be able to unsubscribe by sending an email to: gentoo-powerpc-user+unsubscr...@lists.gentoo.org *FROM* the email address you'd like to unsubscribe (this is how you tell it what address you're using). If you're getting mail from other addresses forwarded to you account, check the email header to see where they're being sent from so you can sent it from the right address. I do not have administrator access to the mailing lists and can't unsubscribe you. -Joe NO KIDDDING I have tried that only 30 or 40 times! It doesn't work! Can somebody please help me? - John John, There is almost certainly no one on this list that can just do this for you. You have to do it yourself or find someone in Gentoo.org who manages these things and convince them to do it for you. Something that comes up once in awhile is that you might have subscribed originally from a different ISP who was acquired by NetZero. The list could still be mailing to that original address and NEtZero is forwarding it to you at this new address. Since you are replying from a different one than you subscribed then the list server thinks you're not the same person and does nothing. That's a hard one to get out of in my experience unless you find a real person to look into it. Assuming that you are actually subscribed from the account you are currently using then sending a message to gentoo-ppc-user+unsubscr...@lists.gentoo.org should work. (I think Joe might have written the email address wrong above, but possibly I've got it wrong myself.) If by any chance you are actually subscribed to the digest then use this: gentoo-ppc-user+unsubscribe-dig...@lists.gentoo.org Good luck, Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Thu, Sep 23, 2010 at 5:05 AM, k...@cas.mcmaster.ca wrote: Mark, However I note that I cannot run updatedb for slocate without also getting a message about /etc/mtab not existing. Should mtab exist withing the chroot? For certain things, it seems to be needed --- the amd64 handbook includes a way to get it among the grub instructions. By the way, if I recall correctly, you once mentioned you had an ubuntu on that machine with grub working --- I would just reuse that grub for booting gentoo. (I have done this before on amd64, but not on any Mac.) Wolfram Wolfram, On first reading I would have said 'he's crazy!' because grub is for x86/PC architecture only, right? At least I think that's the case with the original grub. However apparently grub2 does now run (sort of) on PowerPC: http://grub.enbug.org/TestingOnPowerPC I think it's more in a testing phase, and if Joe or others help me work out what I'm doing wrong then I won't need grub2, but given a bit of time it might be interesting to try out. Unfortunately the known bug list might make it hard for someone at my experience level. Looking in portage it doesn't seem to be available so I'd have to look for an overlay that might have it. Thanks, Mark
Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
On Wed, Sep 22, 2010 at 6:33 PM, Joseph Jezak jos...@gentoo.org wrote: On 09/22/10 18:59, Mark Knecht wrote: Hi, OK, I'm dead tired. I admit it - yaboot has kicked my butt this time around. Can anyone help? I did post this problem here 2-3 weeks ago but still haven't been able to solve the problem so I'm back to the well for another drink. The machine is the original 80GB PPC Mac Mini. I used to run Gentoo on it and it ran great for years so I know at one time yaboot worked just fine. For various reasons I hadn't updated it in a long, long time (2 years) and instead of trying to go through the Gentoo update process which is difficult after that much time I decided to just do a new install. I saved copies of my kernel config and etc/make.conf but unfortunately, being primarily an x86 guy didn't think to save yaboot.conf and fstab. I've now done 5 complete Gentoo installs, starting over from scratch in case something I was doing was messing things up but so far I cannot get the machine to boot. Every time, no matter what I do at install time, I get a message Can't check if filesystem is mounted due to a missing mtab file A somewhat out of focus screen shot is shown here: http://www.flickr.com/photos/29328...@n03/5014227831 Generally speaking I'm following the Gentoo PPC install guide located here: http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=1chap=10 SNIP After looking at the screen shot, I think I have a different idea as to why it might be failing and I don't think it's Yaboot. If you've gotten to init, yaboot's job is already done. Can you boot the install CD and chroot into the install again? When you get it up and running, check to see if fsck.ext3 exists. Even if it does, re-emerge e2fsprogs and see if that helps. -Joe Very interesting. OK - I'm in the chroot now and reinstalling e2fsprogs as you suggest. I'll reboot in a minute and check if it helped. (OK - I rebooted and it didn't fix anything unfortunately. Too bad. Thanks for the idea though.) I was wondering if this was one of those things where device names were changing. They were hda all through the install, which is different from the Install Guide. I've tried to adjust my yaboot.conf file accordingly but maybe it cannot find the disk at that point because the name changed or something. I cannot see anything in the boot screen to indicate that but I suppose it's possible. While I'm here in the chroot I decided to poke around a bit. Note that section 9d of the install guide says that e2fsprogs is already installed as part of the system and indeed it appears to be as shown below. However I note that I cannot run updatedb for slocate without also getting a message about /etc/mtab not existing. Should mtab exist withing the chroot? (chroot) livecd / # emerge -pv e2fsprogs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-fs/e2fsprogs-1.41.11 USE=nls 4,368 kB Total: 1 package (1 reinstall), Size of downloads: 4,368 kB (chroot) livecd / # slocate fsck.* slocate: fatal error: Could not find user database '/var/lib/slocate/slocate.db': No such file or directory (chroot) livecd / # updatedb updatedb: fatal error: load_file: Could not open file: /etc/mtab: No such file or directory updatedb: fatal error: parse_fs_exclude: Could not load file data: /etc/mtab ^C (chroot) livecd / # Indeed, on a different system /etc/mtab exists: gandalf ~ # cat /etc/mtab /dev/sda3 / ext3 rw,noatime,commit=0 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev tmpfs rw,nosuid,relatime,size=10240k,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0 /dev/sda5 /home/herb ext3 rw,noatime,commit=0 0 0 shm /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0 none /proc/fs/vmblock/mountPoint vmblock rw 0 0 gandalf ~ # However on my MacMini it simply doesn't exist: (chroot) livecd / # ls -la /etc/mtab ls: cannot access /etc/mtab: No such file or directory (chroot) livecd / # So the question is what provides mtab? Have I missed some step in the install process 5 times? Man, that would be embarrassing but I'd gladly suffer the shame if I got the machine working! ;-) Thanks for your help. Still looking. Cheers, Mark
[gentoo-ppc-user] What should I copy from Ubuntu
Hi, Sorry for a semi-cross post between the yaboot list and Gentoo-ppc-users. I'm hoping to get this worked out today. I had trouble a week ago getting a new Gentoo PPC install to boot on my Mac Mini so for kicks I tried Ubuntu which booted fine. I'd like to get back to running Gentoo and I'm wondering what information I should retain from my Ubuntu installation. The new Gentoo install is back on the Mac Mini and completely up to date, so if I can work out the booting issue I should be good to go. I have not emerge yaboot as of yet as I don't want to break Ubuntu until the last moment if possible. To boot do I need anything beyond the info contained in the Ubuntu yaboot.conf, the hard drive partitioning and fstab to get Gentoo working? That's should be enough to somehow construct things correctly in Gentoo, correct? Also, the Ubuntu install used an initrd. I presume this is because their one-size-fits-all approach probably requires drivers to boot a lot of different machines. Previously when I had this Mac Mini running Gentoo I didn't use one. I don't need to, correct? (Assuming I can find and build in the right drivers?) Is there anything about yaboot vs grub that makes it prefer an initrd? For now I used the Ubuntu .config for my Gentoo kernel and figured I'd trim it down later after I get the machine at least booting. Thanks, Mark m...@macmini:~$ cat /etc/yaboot.conf ## yaboot.conf generated by the Ubuntu installer ## ## run: man yaboot.conf for details. Do not make changes until you have!! ## see also: /usr/share/doc/yaboot/examples for example configurations. ## ## For a dual-boot menu, add one or more of: ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ boot=/dev/hda2 device=/p...@f400/at...@d/d...@0: partition=3 root=/dev/hda3 timeout=50 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img append=quiet splash image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old append=quiet splash m...@macmini:~$ m...@macmini:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procnodev,noexec,nosuid 0 0 # / was on /dev/hda3 during installation UUID=3d688258-e950-4dd7-87cb-48fa887bb493 / ext4 errors=remount-ro 0 1 # swap was on /dev/hda4 during installation UUID=a56e05b7-6e4a-4239-83a2-df7e7115a9e8 noneswapsw 0 0 /dev/sda1 /media/USB1/video ext2rw 0 0 m...@macmini:~$ m...@macmini:~$ sudo mac-fdisk /dev/hda /dev/hda Command (? for help): p /dev/hda #type name length base ( size ) system /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_Bootstrap untitled2048 @ 2048 ( 1.0M) NewWorld bootblock /dev/hda3 Apple_UNIX_SVR2 untitled39061504 @ 4096 ( 18.6G) Linux native /dev/hda4 Apple_UNIX_SVR2 swap 3905536 @ 39065600 ( 1.9G) Linux swap /dev/hda5 Apple_Free Extra 1984 @ 64 (992.0k) Free space /dev/hda6 Apple_UNIX_SVR2 gentoo 41943040 @ 42971136 ( 20.0G) Linux native /dev/hda7 Apple_Free Extra 71387312 @ 84914176 ( 34.0G) Free space Block size=512, Number of Blocks=156301488 DeviceType=0x0, DeviceId=0x0 Command (? for help):
Re: [gentoo-ppc-user] Re: New install - Unable to get my ppc Mac Mini to boot the root partition
On Fri, Sep 3, 2010 at 2:42 PM, Enlightened User li...@nc.rr.com wrote: http://www.debian.org/ports/powerpc/inst/yaboot-howto/ch9.en.html Sections 9.2 and 9.3 show how to boot to the yaboot 'boot:' prompt and start the kernel with parameters. Hope that helps you get started. If you do change the yaboot.conf file don't forget to run ybin to update the boot partition. I would suggest increasing delay and timeout values (section 6.6 of the previous web document) so the default image is not automatically loaded so quickly. You should then be able to enter something like: hd:4,/vmlinux root=/dev/sda4 ro at the boot: prompt. Another thought would be to remove SCSI support from your kernel build, unless you have a mac mini with an SCSI interface, you should not need SCSI support. That should not require any changes to the yaboot configuration you are currently using. Barry Thanks for the info. OK - as a test I'm going a very different direction. As there is a prebuilt Ubuntu PowerPC version I've just written a CD and it boots fine. I'm right now in the process of letting it blow away my non-functional Gentoo install and install Ubuntu. If that boots then I can see what they did and redo Gentoo later with that knowledge. As for using Gentoo on this box I'm not sure it's really worth it any more. My main machines now are all x86_64 - as is probably true for most people - but fast ones - an i5-661, i7-920 and an i7-980x where I run 5 copies of Windows 7 at the same time in different VMWare jails. I found I wasn't updating this old Mac Mini because it was too slow and took too much of what I call 'Gentoo effort'. If I can find a prepackaged version of MythTV for this machine then likely I'd be better off just to run Ubuntu. I don't really need performance for a MythTV backend server. Anyway, I'll report back more when I know more. Thanks! Cheers, Mark
[gentoo-ppc-user] X on an older PPC-based Mac Mini?
Hi, Are there any known issues setting up X with xorgconfig on a older Mac Mini? I've done it more or less like I do on my x86 machines. I can use startx and see things (xterm, xclock, etc.) in 'top' but I only get a black screen. There are no error messages in the X log file. I've tried two monitors. Same results on both. In make.cong I've got VIDEO_CARDS=radeon fbdev. What about hal? Is that only x86? Maybe someone with a similar first round Mac Mini has a known-good config file? I'm really a noob on this platform, but have used Gentoo for quite awhile. I'm not sure what info to provide so let me know what you need and I'll get it quickly. Thanks, Mark
Re: [gentoo-ppc-user] Mac Mini PPC - Is this the right list?
On Thu, Apr 17, 2008 at 11:16 AM, Mark Knecht [EMAIL PROTECTED] wrote: SNIP Macintosh non-volatile memory driver v1.1 PCI: Enabling device :00:10.0 (0006 - 0007) radeonfb (:00:10.0): Invalid ROM signature 0 should be 0xaa55 radeonfb: Retrieved PLL infos from Open Firmware radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=190.00 Mhz, System=250.00 MHz radeonfb: PLL min 12000 max 35000 i2c-adapter i2c-2: unable to read EDID block. i2c-adapter i2c-2: unable to read EDID block. i2c-adapter i2c-2: unable to read EDID block. radeonfb: Monitor 1 type CRT found radeonfb: EDID probed radeonfb: Monitor 2 type CRT found radeonfb: EDID probed Console: switching to colour frame buffer device 90x25 radeonfb (:00:10.0): ATI Radeon Yb vga16fb: initializing vga16fb: mapped to 0x000a fb1: VGA16 VGA frame buffer device I rebooted with the install CD to look at the dmesg data when the monitor is set up and working correctly. There is one difference which is mode the frame buffer switched into: Macintosh non-volatile memory driver v1.1 PCI: Enabling device :00:10.0 (0006 - 0007) radeonfb (:00:10.0): Invalid ROM signature 0 should be 0xaa55 radeonfb: Retrieved PLL infos from Open Firmware radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=190.00 Mhz, System=250.00 MHz radeonfb: PLL min 12000 max 35000 i2c_adapter i2c-2: unable to read EDID block. i2c_adapter i2c-2: unable to read EDID block. i2c_adapter i2c-2: unable to read EDID block. radeonfb: Monitor 1 type CRT found radeonfb: EDID probed radeonfb: Monitor 2 type CRT found radeonfb: EDID probed Console: switching to colour frame buffer device 128x48 radeonfb (:00:10.0): ATI Radeon Yb vga16fb: initializing vga16fb: mapped to 0x000a fb1: VGA16 VGA frame buffer device - Mark -- gentoo-ppc-user@lists.gentoo.org mailing list
Re: [gentoo-ppc-user] Mac Mini PPC - Is this the right list?
Hi all, I'm starting to look into putting Gentoo on our older PowerPC-based Mac Mini. I wanted to know if this is the right list to ask a few questions about doing an install. Thanks, Mark On Wed, Apr 16, 2008 at 9:29 AM, Terin Stock [EMAIL PROTECTED] wrote: yep, you got the right list. it's kind of slow, but someone will answer your question Thanks Terin, I got a little bored waiting for a response so I got started on my install. Things are going fine so far. I'm into the chroot and downloading a new kernel now. This is my first PPC machine. I have used Gentoo for years as a user type so I've probably built 30 x86 boxes but never a PPC so I wasn't sure how to configure the kernel by hand so I swiped the /proc/config.gz fine from the CD boot environment and pushed it down into the chroot to use to configure my first PPC kernel. Does that sound reasonable for a Mac Mini? I ran make oldconfig and just hit enter until it finished. I figured if that kernel config could boot the machine from the CD it should be OK for a first kernel from the hard drive. Would you agree? Cheers, Mark -- gentoo-ppc-user@lists.gentoo.org mailing list
Re: [gentoo-ppc-user] Mac Mini PPC - Is this the right list?
On Wed, Apr 16, 2008 at 1:15 PM, matt hull [EMAIL PROTECTED] wrote: This is my first PPC machine. I have used Gentoo for years as a user type so I've probably built 30 x86 boxes but never a PPC so I wasn't sure how to configure the kernel by hand so I swiped the /proc/config.gz fine from the CD boot environment and pushed it down into the chroot to use to configure my first PPC kernel. Does that sound reasonable for a Mac Mini? I ran make oldconfig and just hit enter until it finished. I figured if that kernel config could boot the machine from the CD it should be OK for a first kernel from the hard drive. Would you agree the gentoo handbook tells you how to configure the kernel. http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=1chap=7 Code Listing 3.1: Invoking menuconfig # cd /usr/src/linux # make pmac32_defconfig # make menuconfig the default enables most if not all the ppc options you might need. after you get it working you will probably want to start removing some. matt Thanks Matt. I have the system built and running at this point. I had some trouble with yaboot, and still am to some extent, but the machine is booting and I can ssh in so I'm in pretty good shape at this point. My question at this time is how to append kernel boot options in /etc/yaboot.conf. When I boot the apple kernel from the Gentoo CD then when it switches to (I guess) the framebuffer where I see Tux the text on my monitor is jerky and not too readable. However if I use the suggested version apple video=ofonly then the text is fine. Scanning around on the web I found this example of how to do the same thing in yaboot.conf: image=/boot/kernel-2.4.26-gentoo-r3 label=2.4.26-gentoo-r3 root=/dev/hda4 append=video=ofonly read-only I have added this to my /etc/yaboot.conf file but the video is still jumping around and isn't too readable. None the less the machine is completely up and running and doing an emerge -DuN system so this machine, which has sat on the shelf untouched for over a year, is not usable hardware thanks to Gentoo. Cheers, Mark -- gentoo-ppc-user@lists.gentoo.org mailing list
Re: [gentoo-ppc-user] Mac Mini PPC - Is this the right list?
On Wed, Apr 16, 2008 at 3:59 PM, matt hull [EMAIL PROTECTED] wrote: apple kernel ? that would be darwin. i think you mean linux kernel ? Well, yes, it's a Linux kernel but named 'apple' I think. The instructions you see when you boot from the Gentoo 2007.0 universal install CD say to execute essentially one of these two commands: boot: apple or boot: apple video=ofonly when I boot without ofonly I get messed up text. I've got OpenFirmware frame buffer, nvidia and ATI compiled in. EDID also. The machine is acting like it's just not choosing them, assuming the problem I'm seeing is the same one I see booting the kernel on the install CD. How does one make the kernel choose or not choose the FB at boot time? I'm familiar with doing this stuff in grub but this is my first experience with yaboot. My kernel is 2.6.24-gentoo-r3. It boots fine and the machine is working great at least from an ssh session where I'm not looking at this frame buffer stuff. that's fine for the next day or two as I let it build stuff I might want to run on it. Note that if it matters I had to use the 2007.0 CD since the current ISO image for the 2008.0 beta is too large to fit on a 700MB CD-R, at least according to K3b. I don't have any larger CD-Rs available right now. The processor in this machine is a 7447A, clock-1.5GHz. lspci says it's a RV280 [Radeon 9200] graphics chip. Thanks, Mark i dont append any kernel options. you want open firmware framebuffer and radeonfb or nvidiafb compiled in the kernel. not sure if enabling the edid or ddc options will help. i dont have a mac mini, just 2 ibook g4's, not sure how different they are. matt there is also #gentoo-powerpc on freenode too :) My question at this time is how to append kernel boot options in /etc/yaboot.conf. When I boot the apple kernel from the Gentoo CD then when it switches to (I guess) the framebuffer where I see Tux the text on my monitor is jerky and not too readable. However if I use the suggested version apple video=ofonly then the text is fine. Scanning around on the web I found this example of how to do the same thing in yaboot.conf: image=/boot/kernel-2.4.26-gentoo-r3 label=2.4.26-gentoo-r3 root=/dev/hda4 append=video=ofonly read-only I have added this to my /etc/yaboot.conf file but the video is still jumping around and isn't too readable. None the less the machine is completely up and running and doing an emerge -DuN system so this machine, which has sat on the shelf untouched for over a year, is not usable hardware thanks to Gentoo. Cheers, Mark -- gentoo-ppc-user@lists.gentoo.org mailing list -- gentoo-ppc-user@lists.gentoo.org mailing list -- gentoo-ppc-user@lists.gentoo.org mailing list
[gentoo-ppc-user] Mac Mini PPC - Is this the right list?
Hi all, I'm starting to look into putting Gentoo on our older PowerPC-based Mac Mini. I wanted to know if this is the right list to ask a few questions about doing an install. Thanks, Mark -- gentoo-ppc-user@lists.gentoo.org mailing list
