Open divad42 opened 4 years ago
The #42 workaround does seem to work for Debian sid's latest version of the kernel (5.7.0), so it must be a linux-libre/Parabola-specific issue. I don't think any other Linux-libre distros are on 5.7, so I'm not sure if this is a kernel issue, or a function of the Arch dealy in #42 messing with linux-libre detecting the ibridge. In any case, I will change the title to reflect this.
Uninstalling usbmuxd fixed this, so it looks like it is the same issue as Arch and Manjaro are having, except for some reason it is not fixed by the echo '1-3' | sudo tee /sys/bus/usb/drivers/usb/bind
dealy. Should I close this issue, since it has the same underlying cause, despite the different symptoms? I don't know of any other distros that use both linux-libre and usbmuxd 1.1.1, since most fully free distros just use Debian's deblobbed kernel and/or don't have an up-to-date usbmuxd, so this is probably a Parabola-specific thing.
I have tried using the latest linux-libre and linux-libre-lts kernels on Parabola on a Macbook Pro 14,3. I assume it is a kernel update that caused this, but I'm not sure. I am pretty sure this is not a duplicate of #42 since the whole ibridge is not working (touchbar does not display anything and the camera is not detected) despite the modules being loaded, the touchbar does not flicker, and the
echo '1-3' | sudo tee /sys/bus/usb/drivers/usb/bind
part of the workaround for Arch returns an error sayingtee: /sys/bus/usb/drivers/usb/bind: No such device
. Keyboard and touchpad work just fine. I will test this on Arch or Manjaro (which use regular linux) and see if the same thing happens with the latest kernel and lts kernel. I find this odd since just yesterday my touchbar was working fine.