On Feb 26, 2005, at 2:59 AM, Sven Luther wrote:
On Fri, Feb 25, 2005 at 06:15:25PM -0600, Jeff Green wrote:Comments/Problems:
- Shell escaping with the installer presents a difficult situation for mounting other partitions since /dev/hd[ab]* is not recognized.
Sure, it uses devfs, so you need /dev/ide/host0/.../disc
Sorry. Just so used to the old ways....
- install kernel-2.6.8-powerpc as part of the standard install.
Ok.
- installed 2.6.10 & 11-rc4 (both from ppckernel.org) kernels onto hda5
because I know what's coming.
Well, that is something that you should do post-reboot. Not during the install
like you did.
I apologize again. However this is the 2nd (actually 4th counting the two install hangs previously due to the root partition filling up. I was getting a little tired of it. Besides I don't think
copying the vmlinux and sysmap to /boot and the kernel mods to /lib/modules really will create an
issue. (If it does, something is wacky.) However, the thing that did create a problem was attempting to install a deb there (your 2.6.10-powermac kernel plus extras) which created the problems
in the "select and install" step after rebooting into the base-install. I effectively just removed it, i.e.
did a re-install of 2.6.10-powermac and then a de-install. That indeed should have been installed after everything was up and working okay.
Just a note though, the very first time I did this install (last weekend), the installer (rc2 ?) did put in its own boot info into the boot partition, and booted into kernel 2.6.8. No fiddlin' there, exactly (iirc) the same thing happened. (I was not happy about it wiping out my boot partition.)
- nb: 2.6.10 won't startx, and 2.6.11 will with fb driver config though
w/o working wacom support.
Would really like to use my wacom mouse and pen (if possible). I'm back to the hockey puck at this point. May have to do a kernel build myself.....
- also (tried to) install sven's 2.6.10-3-powerpc before rebooting but see below.... - (NEED to sync yaboot.conf again between the two systems.) - REBOOT into base system: - kernel 2.6.8 hangs (with the following as the tail of the boot process:) TCP: Hash tables configured (established 262144 bind 65536) VFS: Cannot open root device "hda5" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) <0>Rebooting in 180 seconds..
This should not happen, i think your hardware is well suppported, but for some
reason the ide driver is not loaded in the initrd. I suspect this may be due
to you doing unorthodoxe kernel things during the install though, or is a bug
in initrd-tools. Mmm, maybe you simply forget to add the initrd entry in your
yaboot.conf ?
As above, it happened also with the installer doing everything on its own, yaboot.conf too. I did try 2.6.8 with my own yaboot.conf and with the initrd entry, same result. However the current status of yaboot.conf may or may not have good 2.6.8 setup status if it's in there at all. I'll grab it and attach at the end.
I would like :
1) a lspci and lspci -n output of your hardware.
Wasn't that part of the install report that I submitted? It came along in the debian mail that I received. I think you received the same mail. Or are you asking for something different?
2) if you could mount the initrd (both 2.6.10 and 2.6.8), and run a find on
it to check for the presence or absence of modules with the above list.
Hmmm, you mean an "lsmod" after the kernel is running? Or something else? I'm not totally familiar with initrd images and what they do. (A small gap in my kernel knowledge, maybe you could fill it in real quick...25 words or less, or point me to a doc file in the kernel documentation, please not too long right now...short on time. My _present_ knowledge ends at putting the initrd= line into the yaboot.conf file.)
3) just to be on the safe side, the content of your yaboot.conf.
Smart man. I'll attach. May be at the bottom of the msg. The partition 5 items are the current install that I did yesterday. The partition 7 group is the install from last week. The orb has an ancient linuxppc install on it and I use it for my rescue disk. (Probably should update that baby.)
- retry with 2.6.10 from ppckernel.org => comes up - needed to edit /etc/network/interfaces to change eth1 to eth0, networking wouldn't work otherwise - In the 'select and install' step, after selecting, the list of packages flies by and then a dialog saying one or more packages failed to install. - moved the /v/c/apt to /usr/v/c/apt, but still had the error (due to kernel-2.6.10-powerpc bad install)
Err, you seem to say there is a bad install, and see below for details, but i
am missing the details in question. So, please provide detailed info on that
too.
Like I said (way) above, that was probably my mistake. I just "undid" it. But now I have to re-install your 2.6.10. (Need to get outside right now to do some birding...migration time...sandhill cranes...that kind of thing.)
yaboot.conf
Description: Binary data
