Description of problem: After install dkms-anbox when you reboot the binder_linux module is not loaded and if you load by hand the module not all the devices are created (https://bugs.mageia.org/show_bug.cgi?id=32467#c23) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install dkms-anbox 2. Reboot the computer 3. Run lsmod|grep bin binfmt_misc 28672 1 4. After run modprobe binder_linux lsmod|grep bin binder_linux 221184 0 binfmt_misc 28672 1 Description of problem: After install dkms-anbox when you reboot the binder_linux module is not loaded and if you load by hand the module not all the devices are created (https://bugs.mageia.org/show_bug.cgi?id=32467#c23) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install dkms-anbox 2. Reboot the computer 3. Run lsmod|grep bin binfmt_misc 28672 1 4. After run modprobe binder_linux lsmod|grep bin binder_linux 221184 0 binfmt_misc 28672 1 5. ls -l /dev/binder* crw------- 1 root root 10, 122 nov 5 14:03 /dev/binder Expected crw------- 1 root root 10, 122 nov 5 14:03 /dev/binder /dev/binderfs: total 0 crw------- 1 root root 243, 4 nov 5 14:03 anbox-binder crw------- 1 root root 243, 5 nov 5 14:03 anbox-hwbinder crw------- 1 root root 243, 6 nov 5 14:03 anbox-vndbinder crw------- 1 root root 243, 1 nov 5 14:03 binder crw------- 1 root root 243, 0 nov 5 14:03 binder-control crw------- 1 root root 243, 2 nov 5 14:03 hwbinder crw------- 1 root root 243, 3 nov 5 14:03 vndbinder
CC: (none) => ngompa13
Created attachment 14133 [details] Changes done to load binder_linux and all components These changes allow binder_linux and all their components to load when the computer reboot
Created attachment 14134 [details] Update dkms-anbox to new commit These changes updates dkms-anbox and keep the enhances about the module load at reboot
Created attachment 14135 [details] Patch to use full name of the module Upstream use binder* in the udev rule, that not works in my test
Created attachment 14136 [details] Patch to disable ashmen in udev rule and anbox.conf
Whiteboard: (none) => MGA9TOO
Created attachment 14137 [details] Add rules to other components
Attachment 14135 is obsolete: 0 => 1
Created attachment 14138 [details] New version to work with the changes in udev rule
Attachment 14136 is obsolete: 0 => 1
Thank you for all your work on this. (In reply to katnatek from comment #5) > Created attachment 14137 [details] > Add rules to other components Given that the first 2 attachments apply to the SRPM indicated, where is this? : anbox-modules-abead1debfae56e8d0307c642865ec23aaa854d3/99-anbox.rules for the last two. BTAIM assigning to Buchan who has been the main committer of dkms-anbox; CC'ing ChrisD who did the latest update. Note that NeilG is already CC'd.
CC: (none) => eatdirtSource RPM: (none) => dkms-anbox-0.0.3-1.1.mga9.src.rpmAssignee: bugsquad => bgmilne
(In reply to Lewis Smith from comment #7) > Thank you for all your work on this. > > (In reply to katnatek from comment #5) > > Created attachment 14137 [details] > > Add rules to other components > Given that the first 2 attachments apply to the SRPM indicated, where is > this? : > anbox-modules-abead1debfae56e8d0307c642865ec23aaa854d3/99-anbox.rules > for the last two. > Are created when the module is loaded, that come from one of my modifications to the spec And the patches can be used with both changes to the spec (the one that updates current version and the one that updates to new commit), I hope this answer your question
(In reply to Lewis Smith from comment #7) > Thank you for all your work on this. > > (In reply to katnatek from comment #5) > > Created attachment 14137 [details] > > Add rules to other components > Given that the first 2 attachments apply to the SRPM indicated, where is > this? : > anbox-modules-abead1debfae56e8d0307c642865ec23aaa854d3/99-anbox.rules > for the last two. > More information: are devices created when the module is loaded as must, I found information about that in https://forum.garudalinux.org/t/ultimate-guide-to-install-anbox-in-any-arch-based-distro-especially-garuda/7453 and in AUR https://aur.archlinux.org/packages/anbox-modules-dkms-git#comment-828655, I use that information and examples of mageia's /etc/modprobe.d/*.conf files to make these lines: echo "options binder_linux devices=binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder" > anbox-options.conf +install -D -m0644 anbox-options.conf %{buildroot}/etc/modprobe.d/anbox-options.conf
from installation procedur https://github.com/choff/anbox-modules , I can read that ashmem_linux pust be loaded but I can't find it
CC: (none) => saveurlinux
The procedure to start waydroid is detailed in another bug: https://bugs.mageia.org/show_bug.cgi?id=32467 There is no need of the ashmem module (it does not build anyway).
I note that binderfs still not load when reboot the computer but that require modify /etc/fstab, I don't like the idea of make that in the package and I don't think is necessary, because other binder and anbox-*binder devices are created on /dev @Chris Denice, I can provide a custom package with any of the proposed versions of dkms-anbox, let me know if you want test one of them
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=32467
I am a bit busy now, but I'll push a new version with your modifs. It is ok to add an anbox-options.conf. Also, it could just be a missing udev.d conf file. No need to send me your package, I think you have explained well enough how to fix the no-loading, thanks!
(In reply to Chris Denice from comment #13) > I am a bit busy now, but I'll push a new version with your modifs. It is ok > to add an anbox-options.conf. Also, it could just be a missing udev.d conf > file. I did try just with udev rules, believe me, not load the devices after reboot
Hi there, I did push an update on updates_testing of dkms-anbox, now ashmem is building and I added config files to ensure modules are loading! Cheers.
Advisory: ########################################## dkms-anbox not load the binder module neither creates the devices when the system is rebooted this update fix the issue and restore the ashmem module missing in previous versions because it was failing to build Packages in 9/core/updates_testing ########################################## dkms-anbox-0.0.3-1.2.mga9.noarch.rpm From SRPM ########################################## dkms-anbox-0.0.3-1.2.mga9
Assignee: bgmilne => qa-bugs
Status comment: (none) => Advisory and packages in comment#16
Tested in real hardware mageia 9 x86_64 The package install without issues and ashmen and binder modules are loaded at boot time
Whiteboard: MGA9TOO => MGA9TOO MGA9-64-OK
CC: (none) => marja11
Marja, please upload advisory for this bug
CC: (none) => mageia
(In reply to katnatek from comment #18) > Marja, please upload advisory for this bug done
Keywords: (none) => advisory
Blocks: (none) => 32467
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
Assuming this issue was fixed in cauldron, too, because dkms-anbox-0.0.3-2.mga10 was pushed around the same time as dkms-anbox-0.0.3-1.2.mga9
Whiteboard: MGA9TOO MGA9-64-OK => MGA9-64-OKVersion: Cauldron => 9
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0007.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED