Open Stoppedpuma opened 1 month ago
How is it not working? Can you confirm you have the binder module available: modinfo binder_linux
. If yes, you should be able to load it has usual. If not, you should remove /var/lib/dkms/binder
and install it again (while you ensure that pacman-hook-dkms is on complain mode).
filename: /lib/modules/6.8.9-273-tkg-eevdf-llvm/updates/dkms/binder_linux.ko.zst modinfo: ERROR: could not get modinfo from 'binder_linux': No such file or directory
This seems to be an issue only with binder as ZFS works perfectly fine, removing /var/lib/dkms/binder
and reinstalling with pacman-hook-dkms in complain mode doesn't fix this.
what do you get with sudo dkms status
?
After reinstalling again in teardown it now shows under dkms status, the problem still occurs though. No idea why it didn't prior to the most recent install.
binder/1, 6.7.6-273-tkg-eevdf, x86_64: installed binder/1, 6.8.9-273-tkg-eevdf-llvm, x86_64: installed zfs/2.2.4, 6.7.6-273-tkg-eevdf, x86_64: installed zfs/2.2.4, 6.8.9-273-tkg-eevdf-llvm, x86_64: installed
If the module is here, you should be able to use it. Try to manually load and mount it:
modinfo binder_linux
sudo modprobe binder-linux device=binder,hwbinder,vndbinder
sudo mount -t binder binder /dev/binderfs
And check for any logs.
Still nothing. searching for any differences in journalctl is nearly impossible as well since even being ran for one second fills hundreds of lines with the /dev/binder not found issue. The closest I can get to a log besides that is errors of /acct and /system being read-only but I'm not sure it's helpful as it isn't new.
Did the command in my previous comments returned any error? If not, the directory /dev/binder
should exist, and therefore, waydroid should work.
Did the command in my previous comments returned any error?
The command doesn't return any errors
the directory /dev/binder should exist, and therefore, waydroid should work.
/dev/binder doesn't exist is the problem, this is where apparmor,d is the culprit as starting without apparmor loaded or just uninstalling apparmor.d solves this problem.
Try to manually created it (sudo mkdir /dev/binder
), and run modprobe again.
Binder is supposed to be a file apparently
[gbinder] ERROR: Can't open /dev/binder: Is a directory
Linking /dev/binderfs/anbox-binder to /dev/binder doesn't work either.
Partially moved from #377
No logs besides this:
[gbinder] ERROR: Can't open /dev/binder: No such file or directory
Failed to add presence handler: None
A teardown doesn't fix this issue but uninstalling apparmor.d or just not loading apparmor on startup does.