NetBSD Problem Report #24778

Received: (qmail 3973 invoked by uid 605); 14 Mar 2004 13:33:34 -0000
Message-Id: <20040314133332.D3CF211157@narn.netbsd.org>
Date: Sun, 14 Mar 2004 13:33:32 +0000 (UTC)
From: nopid@free.fr
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: nopid@free.fr
To: gnats-bugs@gnats.NetBSD.org
Subject: netbsd/macppc won't book on PowerBook G4 (12-inch DVI)
X-Send-Pr-Version: www-1.0

>Number:         24778
>Category:       port-macppc
>Synopsis:       netbsd/macppc won't book on PowerBook G4 (12-inch DVI)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    port-macppc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 14 13:34:01 +0000 2004
>Closed-Date:    
>Last-Modified:  Fri Apr 23 21:21:48 +0000 2004
>Originator:     Nicolas Ollinger
>Release:        1.6A (releng -current 20040312)
>Organization:
>Environment:
Model: PowerBook6,2
Processor: 1 GHz G4
RAM: 768Mb
HD: 80Gb Hitachi IC25N080ATMR04-0
CD: MATSHITA CD-RW CW-8122
>Description:
While trying to boot a GENERIC_MD kernel on my 12" PowerBook G4 DVI, I encounter the following problems:
(1) "wdc0:0:0 lost interrupt" several times
(2) "wdc1:0:0 lost interrupt" several times
(3) when asked for the terminal type, I have no keyboard... whereas console and keyboard appears to be ok from boot messages

The same system boots fine under GNU/Linux Gentoo 1.4 Live CD

The supported models page needs a fix:
http://www.netbsd.org/Ports/macppc/models.html

It would be nice to add support for the forthcoming 2.0

I have no clue how to fix this but I am ready to help fixing this.

Seems to be the same problem as Problem Report #22317
>How-To-Repeat:
Take a 12" PowerBook G4 DVI (new generation)
COMMAND-OPTION-O-F
boot hd:9,\netbsd\ofwboot.xcf netbsd\netbsd-GENERIC_MD.gz

that's it...

Rq. the problem remains the same with older snapshots/releases
>Fix:

>Release-Note:
>Audit-Trail:

From: Krister Walfridsson <cato@df.lth.se>
To: nopid@free.fr
Cc: gnats-bugs@gnats.NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: port-macppc/24778: netbsd/macppc won't book on PowerBook G4
 (12-inch DVI)
Date: Sat, 27 Mar 2004 20:23:23 +0100 (MET)

 On Sun, 14 Mar 2004 nopid@free.fr wrote:

 > While trying to boot a GENERIC_MD kernel on my 12" PowerBook G4 DVI, I encounter the following problems:
 > (1) "wdc0:0:0 lost interrupt" several times
 > (2) "wdc1:0:0 lost interrupt" several times
 > (3) when asked for the terminal type, I have no keyboard... whereas console and keyboard appears to be ok from boot messages

 I see the same keyboard problem on my 12" PowerBook.

 The reason is that the firmware (BootROM version 4.5.5f4) returns
 pseudo-hid as keyboard type, but the kernel fails the tests
 for usb and adb -kbd-ihandles, so it finally assumes it is a
 USB keyboard.

 As a work around, you can get a working keyboard by adding

    pseudo-device wsmux

 to your kernel config file:

 Index: INSTALL
 ===================================================================
 RCS file: /cvsroot/src/sys/arch/macppc/conf/INSTALL,v
 retrieving revision 1.73
 diff -u -r1.73 INSTALL
 --- INSTALL	14 Dec 2003 01:32:02 -0000	1.73
 +++ INSTALL	27 Mar 2004 19:11:02 -0000
 @@ -181,3 +181,4 @@
  pseudo-device	pty		2	# pseudo-terminals (Sysinst needs two)

  pseudo-device	rnd			# /dev/random and in-kernel generator
 +pseudo-device	wsmux			# mouse and keyboard multiplexor


    /Krister

From: Krister Walfridsson <kristerw@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:  
Subject: pr/24778 CVS commit: src/sys/arch/macppc/conf
Date: Mon, 29 Mar 2004 01:46:03 +0000 (UTC)

 Module Name:	src
 Committed By:	kristerw
 Date:		Mon Mar 29 01:46:03 UTC 2004

 Modified Files:
 	src/sys/arch/macppc/conf: INSTALL

 Log Message:
 Add the wsmux pseudo-device.  This will make the adb keyboard work
 even if the heuristics in the console attachment code fail to
 identify the keyboard type.

 This should fix PR 22317 and part of PR 24778.


 To generate a diff of this commit:
 cvs rdiff -r1.74 -r1.75 src/sys/arch/macppc/conf/INSTALL

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.


From: Aymeric Vincent <vincent@labri.fr>
To: Krister Walfridsson <cato@df.lth.se>
Cc: nopid@free.fr, gnats-bugs@gnats.NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: port-macppc/24778: netbsd/macppc won't book on PowerBook G4 (12-inch DVI)
Date: Mon, 29 Mar 2004 09:54:57 +0200

 Maybe we should stop relying only on the open firmware to determine the 
 console, since newer open firmwares don't seem to provide enough 
 information in this respect. In particular, if we have an akbd, we 
 should use it as console no matter what the openfirmware says.

 Currently, I suspect the wsmux trick doesn't let the adb keyboard be 
 recognized as the proper console and doesn't let you drop into DDB if 
 you hit Cmd-Opt-Power. I had to hack my kernel to hardcode that my 
 console is akbd.

   Aymeric

 Krister Walfridsson wrote:

 > As a work around, you can get a working keyboard by adding
 >
 >    pseudo-device wsmux
 >
 > to your kernel config file:


From: Allen Briggs <briggs@wasabisystems.com>
To: Aymeric Vincent <vincent@labri.fr>
Cc: Krister Walfridsson <cato@df.lth.se>, nopid@free.fr,
  gnats-bugs@gnats.NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: port-macppc/24778: netbsd/macppc won't book on PowerBook G4 (12-inch DVI)
Date: Mon, 29 Mar 2004 11:21:33 -0500

 On Mon, Mar 29, 2004 at 09:54:57AM +0200, Aymeric Vincent wrote:
 > Maybe we should stop relying only on the open firmware to determine the 
 > console, since newer open firmwares don't seem to provide enough 
 > information in this respect. In particular, if we have an akbd, we 
 > should use it as console no matter what the openfirmware says.

 Aren't the akbd entries in OFW even if there is no apparent ADB
 keyboard?

 Another option is to start reading the system name and build a
 capabilities table in the kernel to work from.  We could then say
 that all PowerBook systems use ADB, or some such.  I had some hacks
 in a local tree to do that, but they got eaten by a hungry fsck.

 -allen

 -- 
  Allen Briggs                     briggs@wasabisystems.com
  Wasabi Systems, Inc.             http://www.wasabisystems.com/

From: Aymeric Vincent <vincent@labri.fr>
To: Allen Briggs <briggs@wasabisystems.com>
Cc: Krister Walfridsson <cato@df.lth.se>, nopid@free.fr,
  gnats-bugs@gnats.NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: port-macppc/24778: netbsd/macppc won't book on PowerBook G4 (12-inch DVI)
Date: Mon, 29 Mar 2004 18:58:49 +0200

 Allen Briggs wrote:

 > Aren't the akbd entries in OFW even if there is no apparent ADB
 > keyboard?

 Seen the code in akbd.c:akbdattach(), it looks like the adb driver 
 somehow gets enough information to get the type of keyboard. Isn't this 
 enough to make sure there is a true akbd? You mean even machines 
 without akbd's get some ghost akbd0 attached to them?
 Or is the point that we need to detect the console only using OFW 
 information?

 > Another option is to start reading the system name and build a
 > capabilities table in the kernel to work from.  We could then say
 > that all PowerBook systems use ADB, or some such.  I had some hacks
 > in a local tree to do that, but they got eaten by a hungry fsck.

 If we could avoid this, it would be better IMHO.

   Aymeric

State-Changed-From-To: open->feedback 
State-Changed-By: kristerw 
State-Changed-When: Sat Apr 17 20:31:02 UTC 2004 
State-Changed-Why:  
Thank you for your bug report.  I fixed the keyboard problem the day 
before 2.0 was branched.  I'd appriciate if you could test a 2.0 
snapshot to verify that you can use your keyboard. 

Regarding your wdc? lost interrupts: are those fatal or just occuring 
during the probing etc.?  Could you append your dmesg to the PR? 

From: Matthias Scheler <tron@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:  
Subject: pr/24778 CVS commit: [netbsd-1-6] src/sys/arch/macppc/conf
Date: Tue, 20 Apr 2004 06:19:31 +0000 (UTC)

 Module Name:	src
 Committed By:	tron
 Date:		Tue Apr 20 06:19:31 UTC 2004

 Modified Files:
 	src/sys/arch/macppc/conf [netbsd-1-6]: INSTALL

 Log Message:
 Pull up revision 1.75 (requested by kristerw in ticket #1676):
 Add the wsmux pseudo-device.  This will make the adb keyboard work
 even if the heuristics in the console attachment code fail to
 identify the keyboard type.
 This should fix PR 22317 and part of PR 24778.


 To generate a diff of this commit:
 cvs rdiff -r1.61.4.3 -r1.61.4.4 src/sys/arch/macppc/conf/INSTALL

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.


From: nopid <nopid@free.fr>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: Re: port-macppc/24778
Date: Tue, 20 Apr 2004 18:14:33 +0200

 Le 17 avr. 04, =E0 22:32, kristerw@netbsd.org a =E9crit :

 > Synopsis: netbsd/macppc won't book on PowerBook G4 (12-inch DVI)
 >
 > Thank you for your bug report.  I fixed the keyboard problem the day
 > before 2.0 was branched.  I'd appriciate if you could test a 2.0
 > snapshot to verify that you can use your keyboard.

 Unfortunately, the fix does not seems to work for me. I took a releng=20
 build for 2.0 of the 13 of april and had no success using keyboard.

 > Regarding your wdc? lost interrupts: are those fatal or just occuring
 > during the probing etc.?  Could you append your dmesg to the PR?

 As soon as I get keyboard access :-)
 Seems to me it appears not just during probing but afterwards.

State-Changed-From-To: feedback->open 
State-Changed-By: kristerw 
State-Changed-When: Fri Apr 23 21:19:43 UTC 2004 
State-Changed-Why:  
The problem is not solved... 
>Unformatted:

Home	PR Database Search