PowerBook G3 (Pismo/Firewire) Install CD Hangs

[Mike Cochran]

Sorry about that, I just couldn't seem to remember how to boot
verbose. Should know better than trying to think so late at night...

The last 10 lines of a verbose boot (boot -v):
ata0: stat0=50 err=0x01 lab=0x00 msb=0x00
ata0: stat1=00 err=0x01 lsb=0x00 msb=0x00
ata0: reset tp2 stat0=50 stat1=00 devices=0x1
(aprobe0:ata0:0:0:0): SIGNATURE: 0000
ata1: reset tp1 mask=03 ostat0=00 ostat1=00
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00
ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
ata1: reset tp2 stat0=00 stat1=00 devices=0x0

On Sun, Jan 8, 2012 at 9:04 AM, Nathan Whitehorn <nwhitehorn at freebsd.org> wrote:
> On 01/07/12 23:48, Mike Cochran wrote:
>>
>> Hi all, I'm hoping someone can help point me in the right direction.
>>
>> I'm trying to install FreeBSD 9.0-RELEASE on my PowerBook G3 Pismo,
>> but every time I boot the CD (which matches the MD5 hash, first thing
>> I checked...) it never finishes booting. The last couple of messages
>> on screen are below, then the cd stops spinning:
>>
>> gem0: 10kB RX FIFO, 4kB TX FIFO
>> gem0: Ethernet address: (mac address...)
>> sc0<System console>  on nexus0
>> sc0: Unknown<16 virtual consoles, flags=0x300>
>>
>> My thinking at first was possibly DMA trouble with the ATA controller,
>> because I've noticed some people have had some issues on PowerMacs,
>> but disabling DMA (set hw.ata.atapi_dma=0) didn't change anything.
>> I'm at a loss as to what to do, any help would be appreciated. I'm
>> hoping to breathe some fresh life into this laptop.
>>
>> Thanks for any help or suggestions you guys might have,
>> Mike Cochran
>> _______________________________________________
>> freebsd-ppc at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
>
>
> Can you try a verbose boot (boot -v from the loader prompt)? That should at
> least give us some more information to work with.
> -Nathan