[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

PB G4 12" power-down during debian kernel boot for install



(yes, the laptop is plugged in and has a full battery ;) )

Basically certain kernels can boot, but the others I have tried to use begin to boot, then the powerbook powers-down.

According to this helpful page by Matthias Schmidt: http://www.mathematik.uni-marburg.de/~schmidtm/apple/powerbook.en.php I need to use "the kernel from Orion Buckminster Montoya, which I renamed to linux.bin. You have to take his kernel, because the debian default kernel doesn't support ATA 100. The ATA chipset is the "intrepid chipset, which is UniNorth bridge and KeyLargo IS ASIC merged in one chip.""

Orion Buckminster Montoya's kernel (it appears to be a recomplied 2-4-20ben5 with ATA100 support for all known chipsets):
http://valla.uchicago.edu/ppc/vmlinux-pbg412.bz2 ->download
http://valla.uchicago.edu/ppc/PBG412.html ->info on the kernel

I did try the normal install kernel, from
http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/ current/new-powermac/ It booted fine, and guess what! I couldn't see the hard drive, exactly as expected (no ATA 100 support).

Booting was done from one of my HFS volumes.

When trying to boot into the debian install system, I can get the kernel loading from yaboot 1.3.10, and then I get:

Welcome to the linux kernel 2-4-20ben5

linked :0xc0000000
framebuffer at :0x94000400 (phys) 0xd0004000 (log)
klimit :0xc0358820
HSR :0x00003030
HIDO :0x8410c0bc

pcmach_init():done
idmach():done
MMU:enter
MMU:hwinit
hash:enter
hash:findpiece
hash:patch
hash:done
MMU:mapin
MMU:setio
MMU:exit
xmon uses screen and keyboard
setup arch :enter
setup arch:bootmem
arch :exit
openpic :enter
openpic :timer
openpic :ext
openpic :spurious
openpic :exit

<at this point (about 1.5-2 seconds into the kernel boot) (before tux appears) the laptop abruptly powers down.> The above was as best as I could make it out, but since the whole thing just turns off after a few sec, I had to reboot about 20 times to write it down. (It made me feel like I was shortening the life of the PB through torture, but everything still seems to work fine in OSX after all that.)

This leads me to believe that the kernel & or firmware is the issue, and not my hardware... but this problem is not new to me..

Background...
This problem first cropped up when I was running YDL, and _accidentally_ :( installed the 10.2.8 OSX update on another (OSX) partition. (This apparently also did a firmware upgrade, and a few folks on one of the YDL lists also found their PB G4 12" Linux systems unbootable after the update and people had to re-complie their kernels (i think it was a benh one) to get them to boot {searched their lists but couldn't find it] ) I didn't have another system capable of building a kernel nor did I have a way to get it onto the ext2 partition. In the case of YDL the symptom was almost identical except it happened maybe 1 second earlier, right after OF's "quiescing(sp)" line. The kernel I was using then was vmlinux-2.4.20-8d. Back in the fall, I basically wrote the partition and install off.

I had used the YDL as my primary workspace and had Mac On Linux running for certain OSX apps. OSX couldn't even see the ext2 partition, and I had to use this utility to mount the ext2 partition: Ext2FS_1.1b1.dmg (a bit funky, but let me mount and recover my files from the ext2 partition, plus gave me some command line goodies for ext2 in OS X)
http://gd.tuwien.ac.at/opsys/linux/sf/e/ext2fsx/ ->(download)

I also used yaboot to try booting from the ext2 partition and achieved the same results as above. I also used yaboot to try booting from the existing Apple_bootstrap partition (old YDL) and met with the same results as above.


System: powerbook G4 12" 867Mhz
640 MB RAM
60 Gig HD
10/100 Ethernet
CD-RW/DVD-ROM
FW 400
2x USB 1.1
etc..

OS'es
OSX 10.3.2
OSX 10.2.8
YDL (broken)-> now trying to replace it with Debian.

Anyone have a kernel that will boot me into the Debian installation w/ATA100 support or any ideas on what the heck is happening here?
Sorry for the long post
Thanks again,

-Andrew Crawford



Reply to: