Search Criteria
Package Details: binder_linux-dkms 6.8-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/binder_linux-dkms.git (read-only, click to copy) |
|---|---|
| Package Base: | binder_linux-dkms |
| Description: | Android kernel driver fork by @choff in DKMS format, binder only. |
| Upstream URL: | https://github.com/choff/anbox-modules |
| Keywords: | anbox binder binderfs waydroid |
| Licenses: | GPL3 |
| Conflicts: | anbox-modules-dkms |
| Submitter: | ZhangHua |
| Maintainer: | ZhangHua |
| Last Packager: | ZhangHua |
| Votes: | 19 |
| Popularity: | 0.97 |
| First Submitted: | 2022-10-14 05:45 (UTC) |
| Last Updated: | 2024-03-04 13:44 (UTC) |
Latest Comments
1 2 3 Next › Last »
zayn7lie commented on 2024-03-07 18:15 (UTC)
Problem solved: https://bbs.archlinux.org/viewtopic.php?pid=2155531#p2155531
zayn7lie commented on 2024-03-05 19:25 (UTC) (edited on 2024-03-05 19:52 (UTC) by zayn7lie)
@ZhangHua This is still not work, but there showed the error while mounting:
and this is what happen recording by
dmesg:And there are also errors happening while rebooting after I try to mount:
And the process of
182573seems to relate tosd-syncZhangHua commented on 2024-03-05 01:58 (UTC)
@zayn7lie Can you try to follow this document to mount /dev/binderfs manually? https://www.kernel.org/doc/html/latest/admin-guide/binderfs.html If this successes and waydroid starts working, I think it may because that something on your device stops mounting /dev/binderfs automatically.
zayn7lie commented on 2024-03-04 22:22 (UTC) (edited on 2024-03-05 19:27 (UTC) by zayn7lie)
While using
# waydroid init, error shown:ERROR: [Errno 2] No such file or directory: '/dev/binderfs/binder-control'How can I solve that?@ZhangHua I think I have built this module successfully, and I have rebooted as well, but I still cannot found
/dev/binderfs. And it is wired that reboot would take a long timesyncing filesystem and devicesand it would time out.gitversion does not help as well.ZhangHua commented on 2024-03-03 00:42 (UTC)
@zayn7lie You should check if you have built this dkms module successfully. You must install your kernel's header(like
linux-headers) in order to let dkms build it successfully. After you built this module successfully, I think you can simply reboot your device to let waydroid load this module automatically.bkb commented on 2023-08-14 18:08 (UTC) (edited on 2023-08-14 18:37 (UTC) by bkb)
That binder thing is driving me crazy and is necessary in my case
aneesh61 commented on 2023-08-06 23:54 (UTC)
Please add aarch64 to supported architectures. Works great on aarch64. Tested on an ARM64 Chromebook running ArchLinuxARM
austinrojers commented on 2023-07-22 16:44 (UTC) (edited on 2023-07-22 16:46 (UTC) by austinrojers)
This is the solution for my previous comment:
It seems that if you first initialize and run Waydroid with a kernel and then later switch to another kernel, you will have to reinitialize Waydroid to work with the later kernel.
sudo waydroid init -fThe
waydroid init -fcommand initializes Waydroid. ( The -f flag tells Waydroid to force a reset.)This downloads the latest Android image (if there is an update), sets up the Waydroid configuration file and starts the Waydroid container.
jimnong commented on 2023-07-17 09:33 (UTC) (edited on 2023-07-17 09:37 (UTC) by jimnong)
I installed this to run Waydroid.
Works well with original arch-linux kernel 6.4.3-arch1-1.
Are there anybody who can unflag?
1 2 3 Next › Last »