On Mon, Aug 12, Matthieu Herrb wrote: > On Sun, Aug 11, 2019 at 11:49:10PM +0000, ioh wrote: > > > > I have been able to successfully install OpenBSD Current Aug 06 > > 2019 on the Olimex Teres laptop. It has very similar hardware to > > the PineBook, arm64 allwinner, etc. I used u-boot-sunxi-with-spl.bin > > from u-boot v2019.07 (teres_i_defconfig) and Arm Trusted Firmware > > v2.1. The dtb (sun50i-a64-teres-i.dtb) is from the OpenBSD 6.5-release > > ports tree. > > > > To complete kernel initialization from either the install bsd.rd > > or bsd from an install, the ohci driver must be disabled. I have > > included the serial console output and dmesg of first a boot without > > the ohci driver disabled, and then the boot log of my successful > > install with ohci disabled. According to linux dmesg or the > > sun50i-a64-teres-i.dts, ohci is available so the driver is probed > > correctly - but even after several minutes the initialization process > > will not continue past the line "ohci0 at simplebus0". > > > > What works: the embedded mmc and external mmc, external usb ports, > > the serial line, and if xorg is running, the display. What does > > not: wifi (as expected, realtek 8723bs), keyboard and trackpad. > > > > Please let me know if there is anything I can do to help improve > > support for this platform. I tried building a DEBUG kernel and > > booting with "verbose" from the UKC> prompt but did not find any > > useful (afaik) information. I don't know how else to get more verbose > > information from the initialization process (add printf's to the > > driver code?). > > > umodem0 at uhub1 port 4 configuration 1 interface 2 "Olimex Ltd. TERES > > Keyboard+Touchpad (drv)" rev 1.10/0.01 addr 5 > > umodem0: data interface 3, has no CM over data, has break > > umodem0: status change notification available > > ucom0 at umodem0 > > That is a bit strange and explains why keyboard/touchpad don't work. > > On the pinebook there is an internal usb hub on which attaches ate uhub1 > and the keyboard and trackpad are uhid devices behind it. > > uhub4 at uhub1 port 1 configuration 1 interface 0 "Genesys Logic USB2.0 Hub" > rev 2.00/88.32 addr 2 > uhidev0 at uhub4 port 1 configuration 1 interface 0 "HAILUCK CO.,LTD USB > KEYBOARD" rev 1.10/1.00 addr 3 > uhidev0: iclass 3/1 > ukbd0 at uhidev0: 8 variable keys, 6 key codes > wskbd0 at ukbd0: console keyboard, using wsdisplay0 > uhidev1 at uhub4 port 1 configuration 1 interface 1 "HAILUCK CO.,LTD USB > KEYBOARD" rev 1.10/1.00 addr 3 > uhidev1: iclass 3/0, 9 report ids > ums0 at uhidev1 reportid 1: 5 buttons, Z and W dir > wsmouse0 at ums0 mux 0
This looks pretty similar to what happens on linux. Here is a section of the armbian dmesg: [ 5.356506] usb 2-1.4: new full-speed USB device number 5 using ehci-platform [ 5.471104] usb 2-1.4: New USB device found, idVendor=15ba, idProduct=003c, bcdDevice= 0.01 [ 5.471120] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=220 [ 5.471126] usb 2-1.4: Product: TERES Keyboard+Touchpad [ 5.471132] usb 2-1.4: Manufacturer: Olimex Ltd. [ 5.471138] usb 2-1.4: SerialNumber: A4138353330351F08041 [ 5.489383] input: Olimex Ltd. TERES Keyboard+Touchpad as /devices/platform/soc/1c1b000.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:15BA:003C.0002/input/input2 [ 5.549363] hid-generic 0003:15BA:003C.0002: input,hidraw0: USB HID v1.11 Keyboard [Olimex Ltd. TERES Keyboard+Touchpad] on usb-1c1b000.usb-1.4/input0 [ 5.558421] input: Olimex Ltd. TERES Keyboard+Touchpad as /devices/platform/soc/1c1b000.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:15BA:003C.0003/input/input3 [ 5.558859] hid-generic 0003:15BA:003C.0003: input,hidraw1: USB HID v1.11 Mouse [Olimex Ltd. TERES Keyboard+Touchpad] on usb-1c1b000.usb-1.4/input1 And the complete armbian boot logs if you're interested: http://ix.io/1xWt -- ioh
