From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ur; Thu Nov 16 13:29:15 EST 2017
Message-ID: <0250877A5D5322478B4F79215D9905A9@felloff.net>
Date: Thu, 16 Nov 2017 19:29:06 +0100
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] usb hid defunct?
In-Reply-To: 1510774330.2709780.1173718520.3473DF18@webmail.messagingengine.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: deep-learning shader 

ok, given that you don't see any output from /dev/usbevents,
i'd start with debugging usbd which handles device attaches/detaches.
if that doesnt work, then nusb/kb isnt even started and we do not
have to look into it until this is resolved.

change /sys/src/9/boot/nusbrc like:

- if(! nusb/usbd)
+ if(! nusb/usbd $usbdebug)
	exit

build a new kernel and reboot with boot parameter: usbdebug=-ddd

then post the output when you attach the usb keyboard.

alternatively, you can boot with boot parameter: nousbrc=1
and then start nusb/usbd -ddd manually and get some debug
output.

--
cinap