Lenovo N20P Clapper/Baytrail no mouse or touchscreen

[HoneyGiant]

Hello,

I have a Lenovo N20P with Mrchromebox full UEFI replacement when trying Galliumos 3 nightly from a live USB stick I have no touchscreen or mouse, going into settings the device panels are blank as if it is not seeing them. I'll try and list the steps I've already taken and tested below.

• I tried a full install and then updated the system but nothing changed.

• Tried using the older v2 of GalliumOS also had no touchscreen or mouse.

• I then put the chromebook back to stock firmware and everything started working again.

• Then tried legacy boot with stock firmware and the mouse and touchscreen works.

• Afterwards I tried full UEFI replacement again and the same result as the first time, no mouse or touchscreen.

• I tried Manjaro as I had a live usb stick handy and that was the same.

• I also tried a Window 10 install stick and that crashed before setup can start saying ACPI bios error

• I've also noticed if I boot from the usb on the right hand side of the laptop, the machine wont fully boot from the Galliumos usb. It drops to a shell. If I use the left side ports, I get to the desktop environment but no input devices. The right side port will then work if I plug a USB mouse into it.

Do you have any ideas on why the mouse and touchscreen are not being detected with a UEFI install? I've attached some logs which I think is hinting at USB hub problems which I assume the mouse and touchscreen are attached to.

Many thanks.

lsusb.txt usb-devices.txt dmesg.txt

[MrChromebox]

please provide dmesg and 'cat /proc/interrupts' for both UEFI and stock firmware so I can see what's up and make corrections. No other Baytrail devices have issues with the UEFI firmware to my knowledge (but I'll retest on Swanky)

edit: the touchpad/touchscreen are I2C devices, not USB, so the USB-related boot issues are unrelated.

[HoneyGiant]

Hello, thanks for the reply. I started afresh and have the command outputs you asked for in Chromeos using stock firmware and GalliumOS live using your UEFI replacement. After running dmesg on normal Chromeos, I can see those USB errors appear there as well. So appears to be a red hearing as you have mentioned.

Thank you for taking the time to look into this.

chromeos-74.0.3729.159-dmesg.txt chromeos-74.0.3729.159 -interrupts.txt galliumlive-interrupts.txt galliumlive-dmesg.txt

[MrChromebox]

@HoneyGiant sorry, what I was looking for was dmesg/interrupts from GalliumOS 3.0b booted with the stock ChromeOS firmware + RW_LEGACY, so I can compare the outputs of the same booted OS with the different firmware

[HoneyGiant]

No problem, I've rerun with stock ChromeOS firmware + RW_Legacy booted off a GalliumOS live USB.

Thanks again.

chromeos+rw_legacy+galliumoslive_interrupts.txt chromeos+rw_legacy+galliumlive_dmesg.txt

[MrChromebox]

thanks, I'll see what I can determine from this. At first glance, there's nothing wrong with the Clapper UEFI firmware / not set up any differently than other Baytrail devices.

[MrChromebox]

can you also pull the firmware boot log for the UEFI firmware for me? You'll need to download/extract https://mrchromebox.tech/files/util/cbmem.tar.gz and run 'sudo ./cbmem -c > cbmem.log'

Need to figure out what's going on with the I2C init/devices since they appear to be defined properly

[HoneyGiant]

Before changing over to UEFI I ran it on stock firmware with RW_Legacy using the GalliumOS live USB in case you wanted that to compare with. I then ran it as you asked with your UEFI version.

Thanks.

UEFI_galliumoslive_cbmem.log stockfirmware+rw_legacy_galliumoslive_cbmem.log

[MrChromebox]

@HoneyGiant think I found the issue, shoot me an email (@gmail) or msg me on IRC/Hangsouts etc and I'll provide a UEFI firmware update for you to test

[HoneyGiant]

Thanks. I've sent you an email.

[MrChromebox]

fixed with UEFI firmware update