Re: keyboard failure (#2)

hi nick -

>> problem description:
>>
>> scenario 1
>> keyboard (details below) plugged into either one of the two available
>> ADB ports on Mac. the remaining one is used by mouse/trackball 
>> (details
>> below). system boots, but halts at:
>>
>> OpenBSD 3.2-stable (GENERIC) #0: Wed Jan  1 09:25:22 PST 2003
>>      root@XXXXX:/sys/arch/mac68k/compile/GENERIC
>> Apple Macintosh Quadra 800, 68040 CPU+MMU+FPU, 4k on-chip physical I/D
>> caches
>> real mem = 41943040 (40960K)
>> avail mem = 35172352 (34348K)
>> using 537 buffers containing 2199552 bytes (2148K) of memory
>> mrg: 'Quadra/Centris ROMs' ROM glue, tracing off, debug off, silent
>> traps
>> mrg: I/O map kludge for ROMs that use hardware addresses directly.
>> adb: bus subsystem
>> mrg: skipping egret setup
>> adb: calling ADBReInit
>> adb: using II series hardware support
>> adb: cleanup: nothing returned
>> adb: ADBReInit complete
>> adb: extended keyboard at 2
>> adb:
>>
>> hit any key and boot continues. full keyboard response. i am able to
>> log in.
>
> This, I was not able to reproduce on either my Quadra 610 or Quadra
> 650.

just for the records: if i plug in an Apple Desktop Bus Mouse II either 
directly into the Mac or the extra ADB port on the keyboard, i am 
getting the same result. here's the only difference:
...
adb: extended keyboard at 2
adb:
<hit any key on the keyboard and the boot continues with>
adb: 100 dpi mouse at 3

which then looks exactly like your dmesg output.
weird isn't it.

>
>> scenario 2
>> keyboard (details below) plugged into either one of the two available
>> ADB ports on Mac. no mouse/trackball is attached. the system boots
>> without halting. no keyboard response. i am not able to log in.
>
> THIS, I *was* able to reproduce!
> Both my OpenBSD-compatable Quadras demonstrated this issue.
>
> Very facinating problem, and I'm surprised I never noticed it before.
> Obviously, I've always had my mouse plugged in on my Quadras...
>
> This gives me grounds for some WAGs (Wild...guesses), though.
> If you look at your dmesg below, and compare it with the ADB section
> of mine:
>
> adb: bus subsystem
> mrg: skipping egret setup
> adb: calling ADBReInit
> adb: using II series hardware support
> adb: cleanup: nothing returned
> adb: ADBReInit complete
> adb: extended keyboard at 2
> adb: 100 dpi mouse at 3
>
> (-current as of today, in fact), you see my mouse comes through with
> nice, logical info.  Mine is an official Apple mouse -- one of the
> "newer" rounded ones, not the older, more angular ones.
>
> Yours, however, came through with this:
>
>> adb: extended mouse <KMW> 0-button 6031 dpi unknown device at 15
>> adb: relative positioning device (mouse?) (50) at 3
>
> It *looks* to me like your mouse (I'm guessing that was one of the
> Kensington devices) isn't 100% Apple Compatable, and OpenBSD is
> confused.
>
> So...if there is no mouse attached, the keyboard system doesn't work,
> as your mouse seems a little strange, that might explain your first
> problem...
>
> Do you happen to have a Apple-brand ADB mouse?  I would be very
> curious if using it resolved your first problem, based on what I am
> seeing, I would guess it would.

sigh, ... i tried this a while back and it didn't.

>
> I would also be curious if plugging it into the side of the keyboard
> instead of the back of the machine changed anything, I would guess it
> won't (but if I was wrong, it would be an easy "fix")

nope. same behavior - i tried this a while ago too.


>
> Also try a -current kernel from the FTP site, see if that changes
> anything.  I wouldn't bet on it, but beats trying to fix an already
> solved problem.  Just download, unpack bsd.tgz, rename it bsdcurr (or
> whatever) and change your boot file name to "bsdcurr" (or whatever),
> put it in /, reboot the machine.  If/when it doesn't work, just
> reboot, you will be back to your -stable kernel.

i will try. although i am skeptical - just a gut feeling. i'll keep you 
posted.

>
>
>> details:
>>
>> OpenBSD 3.2-stable (GENERIC) #0: Wed Jan  1 09:25:22 PST 2003
>>      root@XXXXX:/sys/arch/mac68k/compile/GENERIC
>> Apple Macintosh Quadra 800, 68040 CPU+MMU+FPU, 4k on-chip physical I/D
>> caches
>> real mem = 41943040 (40960K)
>> avail mem = 35172352 (34348K)
>> using 537 buffers containing 2199552 bytes (2148K) of memory
>> mrg: 'Quadra/Centris ROMs' ROM glue, tracing off, debug off, silent
>> traps
>> mrg: I/O map kludge for ROMs that use hardware addresses directly.
>> adb: bus subsystem
>> mrg: skipping egret setup
>> adb: calling ADBReInit
>> adb: using II series hardware support
>> adb: cleanup: nothing returned
>> adb: ADBReInit complete
>> adb: extended keyboard at 2
>> adb: extended mouse <KMW> 0-button 6031 dpi unknown device at 15
>> adb: relative positioning device (mouse?) (50) at 3
>> mainbus0 (root)
>> obio0 at mainbus0
>> adb0 at obio0 (ADB event device)
>> asc0 at obio0: Apple Sound Chip
>> intvid0 at obio0: DAFB: Monitor sense 1.
>> intvid0: 640 x 480, monochrome
>> grf0 at intvid0
>> ite0 at grf0 (minimal console)
>> sn0 at obio0: integrated ethernet adapter, address XX:XX:XX:XX:XX:XX
>> esp0 at obio0: address 0x898000: NCR53C96, 16MHz, SCSI ID 7
>> scsibus0 at esp0: 8 targets
>> sd0 at scsibus0 targ 1 lun 0: <QUANTUM, FIREBALL_TM1280S, 300X> SCSI2
>> 0/direct fixed
>> sd0: 1222MB, 6810 cyl, 2 head, 183 sec, 512 bytes/sec, 2503872 sec 
>> total
>> cd0 at scsibus0 targ 3 lun 0: <MATSHITA, CD-ROM CR-8004, 1.0p> SCSI2
>> 5/cdrom removable
>> zsc0 at obio0 chip type 0
>> zstty0 at zsc0 channel 0
>> zstty1 at zsc0 channel 1
>> nubus0 at mainbus0
>> ae0 at nubus0: address XX:XX:XX:XX:XX:XX, type MacCon Ethernet, 32KB
>> memory
>> ae0: length does not match next packet pointer
>> ae0: len 0000 nlen ff00 start 0c first 00 curr 08 next 00 stop 80
>> ae0: NIC memory corrupt - invalid packet length 65280
>> root on sd0a swap on sd0b
>> PRAM: 0x3e33c546, macos_boottime: 0x3e33c483.
>>
>> keyboards
>> AppleDesign Keyboard or Apple Keyboard II or Apple Extended Keyboard 
>> II
>>
>> mice
>> Power Computing (single button) or Kensington (two button)
>>
>> trackball
>> Kensington Turbo Mouse
>>
>> sidenote:
>>
>> i experienced the same problem intermittently on a Quadra 650 under
>> OBSD 3.0. i am also running OBSD 3.2 on a Quadra 610 without any
>> problems.
>> firstly, if this is not the right forum to ask questions like this,
>> please let me know. secondly, if any of this is documented elsewhere
>> (FAQ, man pages, mailing list archive, etc.), i would like to know
>> about it.
>
> This is a good error report in a good place for it -- enough info for
> me to have some idea what is going on and to attempt to reproduce the
> conditions. 8-)

merci. i was just being lazy the first time around - shooting from my 
hip.

>
> Sorry for the delay in getting back to you -- had to get a time when I
> and my Quadras are all not busy doing something...and the quadras move
> even slower than me... 8-)

no problem - i know the feeling.

thanks.

>
> Nick.
> -- 
> http://www.holland-consulting.net
>
>
--
Timo Ochmann