Re: PowerBook 5,8 and keyboards

[netbsd%pckswarms.ch@localhost]

Hi,

I'll try with firewire once the powerbook mouse problem is sorted.
It's possible that the firewire doesn't work, since, it would
be odd that the oldest and newest PPC powerbooks don't work, and
the middle ones do.

Thanks for the DDB command.  I'll build a kernel tonight and 
try it.  I tried OpenBSD on the 15" g4 and it didn't even boot
the install kernel.  Sadly it powered off so I couldn't see which 
device was failing.

Linux doesn't work with the built in track pad either.

Thanks also for your help on this as well as your macppc work.
I'm sure that the port would be in much worse shape without
your work.  

cheers

bruce


On Sun, Aug 16, 2009 at 06:18:40PM -0400, Michael wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> On Aug 16, 2009, at 3:46 PM, netbsd%pckswarms.ch@localhost wrote:
> 
> >I had to remove all of the firewire devices like I did for the Pismo,
> >and, pbms, the PowerBook 15" mouse device.
> 
> This firewire problem, is weird. I have two UniNorth machines - a GigE  
> G4 and an 800MHz iBook G4 which should both have firewire controllers  
> very similar if not identical to yours.
> 
> >>trap: pid 0.32 (system): kernel MCHK trap @ 0x3efe70 (SRR1=0x149030)
> >>panic: trap
> >>Stopped in pid 0.32 (system) at netbsd:cpu_Debugger+0x10:  lwz r0,  
> >>r1, 0
> >>x14
> >>0xd50e89f0: at panic+0x210
> >>0xd50e8a40: at trap+0x108
> >>0xd50e8ad0: Kernel MCHK trap by cfdriver_get_iattr+0x58:  
> >>srr1=0x149030
> >>            r1=0xd50e8b90 cr=0x48002048 xer=0 ctr=0x4ae738
> >>saved LR(0x2800003e) is invalid
> >>db>
> >>
> >>alas the keyboard is non-functional so I can't get a traceback.
> >>
> >>Has someone seen this?
> 
> I don't have the hardware ( my iBook has an ADB touchpad ) - what was  
> the last device it tried to attach? Or rather, did the pbms driver  
> cause this?
> Also, could you build a kernel with
> options       DDB_COMMANDONENTER="bt"
> and watch it crash? This option should cause ddb to output a stack  
> trace automatically, all I need is which driver's attach method this  
> is coming from, no need to ten finger copy the whole trace.
> 
> have fun
> Michael
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> 
> iQEVAwUBSoiFwMpnzkX8Yg2nAQJF2Qf/SbQXiiqfNjpF1xuZDDH4czy/xV9y0p6L
> zH9tqJxUAKQsA0rCcWaT+cu7ycrTF+GZegtfjZcBdjXyADjkKvAwCvh2zKHvj7rr
> i9dfKYotmQH+CFCbt+JIOgiNgIttgrTJlGDlwaZCIHfhAvLCVbXyuHZ3EZA+p92l
> RpgX7ryq6hIE3Qo5fDRZDSgbJoRL8FcsVsHQ4E+lJp8WMk0Gd2N6WtktSljcZJvH
> 7aZbcjrj7qquopDN27H/A8roxnpZ2vdmLF+iN3jB5Ny7QSCCxQ53NAOimLFb74wQ
> Mfsgh7SZX7KQL0mNCYbfUUF0wKw5nE5B38jEBjOztXFGPxRvuupmLw==
> =RJw1
> -----END PGP SIGNATURE-----