[gbinder] WARNING: Service manager /dev/binder has died
I am having trouble with Waydroid on Manjaro (arch based)
I had Anbox working, but the best I can do on Waydroid is get the splash screen to show up for a few seconds (waydroid show-full-ui)
Seems to be a problem with binder
I run
sudo systemctl start waydroid-container
waydroid session start
And it seems to be okay, but as soon as I issue any command to waydroid, I get this error:
[gbinder] WARNING: Service manager /dev/binder has died
And then the session ends
I've attached a dmesg log Waydroid Crash Log.txt
Same here
pro@Asus:~$ sudo systemctl start waydroid-container
pro@Asus:~$ waydroid session start
[11:12:08] Failed to start Clipboard manager service, check logs
[gbinder] WARNING: Service manager /dev/anbox-binder has died
Linux Asus 5.14.0-9.5-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.14-11ubuntu1~impish (2021-10-03) x86_64 x86_64 x86_64 GNU/Linux
Booting with ubuntu's generic kernel (default) worked, as you can see above I was using liquorix/zen kernel
I am now having this issue here https://github.com/waydroid/waydroid/issues/61
I was under the impression that a kernel with ashmem and binder support was necessary (I am using Xanmod kernel on Manjaro)
Same here, Arch Linux with Kernel: 5.14.11-xanmod1-1, Anbox working but if I run
sudo systemctl start waydroid-container
waydroid session start
and gets
[gbinder] Service manager /dev/binder has appeared
[gbinder] WARNING: Service manager /dev/binder has died
diedbydisgust@laptop:~$ zcat /proc/config.gz | grep 'ANDROID_BINDER_DEVICES\|ASHMEM'
CONFIG_ASHMEM=m
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line.
default Kernel config for this feature is
CONFIG_PSI=y
CONFIG_PSI_DEFAULT_DISABLED=y
so you need to enable PSI. i hope works for you all
Thank you, @zergio91! I can confirm this fixes the issue! (I also had to apply the Nvidia Gpu fix from the Arch Wiki for my RX 6900 XT)
I have still this kernel parameter:
RPI-4B kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=E4:5F:01:48:60:0E vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 root=PARTUUID=628b4c08-02 rw rootwait console=ttyS0,115200 console=tty3 selinux=0 quiet splash plymouth.ignore-serial-consoles smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyS0,115200 usbhid.mousepoll=8 audit=0 psi=1
i got this.
sudo waydroid session start XDG Session is not "wayland" [gbinder] Service manager /dev/binder has appeared [gbinder] WARNING: Service manager /dev/binder has died
When on my Pinephone pro I do:
$ cat /proc/pressure/cpu
some avg10=0.00 avg60=0.00 avg300=0.00 total=113067992
full avg10=0.00 avg60=0.00 avg300=0.00 total=61452400
So PSI is already enabled. Still, waydroid fails after:
[gbinder] WARNING: Service manager /dev/binder has died
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line.
default Kernel config for this feature is
CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=yso you need to enable PSI. i hope works for you all
this fixed
[gbinder] WARNING: Service manager /dev/binder has died
but now i get
[15:11:11] Starting waydroid session
[15:11:12] Failed to add service waydroidusermonitor: -1
[15:11:12] Failed to start Clipboard manager service, check logs
Fedora silverblue 35 Xanmod kernel 5.16.10-xm1.0.fc35.x86_64
oh well something happened and it works
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line. default Kernel config for this feature is
CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=yso you need to enable PSI. i hope works for you all
this fixed
[gbinder] WARNING: Service manager /dev/binder has diedbut now i get[15:11:11] Starting waydroid session [15:11:12] Failed to add service waydroidusermonitor: -1 [15:11:12] Failed to start Clipboard manager service, check logsFedora silverblue 35 Xanmod kernel 5.16.10-xm1.0.fc35.x86_64
How do you go about adding psi=1 to the kernel command line? I'm runinng Fedora 35 and I'm a bit lost. Thanks for any help.
@timothykim It depends on your boot loader. A quick search tells me that Fedora's default boot loader is GRUB. See this article in Arch Wiki for details about how to add or modify kernel parameters.
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line. default Kernel config for this feature is
CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=yso you need to enable PSI. i hope works for you all
this fixed
[gbinder] WARNING: Service manager /dev/binder has diedbut now i get[15:11:11] Starting waydroid session [15:11:12] Failed to add service waydroidusermonitor: -1 [15:11:12] Failed to start Clipboard manager service, check logsFedora silverblue 35 Xanmod kernel 5.16.10-xm1.0.fc35.x86_64
How do you go about adding psi=1 to the kernel command line? I'm runinng Fedora 35 and I'm a bit lost. Thanks for any help.
On silverblue its
rpm-ostree kargs
On the normal fedora i believe its editing /etc/default/grub,
changing the CMDLINE_DEFAULT
And regenerating the config
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line.
default Kernel config for this feature is
CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=yso you need to enable PSI. i hope works for you all
It works.
I'm seeing the same issue as OP except my kernel already had psi=1 enabled.
running on postmarketOS on aarch64
$ zcat /proc/config.gz | grep -Ei 'psi|binder'
CONFIG_PSI=y
# CONFIG_PSI_DEFAULT_DISABLED is not set
CONFIG_ANDROID_BINDER_IPC=y
# CONFIG_ANDROID_BINDERFS is not set
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"
CONFIG_ANDROID_BINDER_IPC_SELFTEST=y
dmesg is full of logs like this:
1703.734499] binder_debug: 7 callbacks suppressed
[ 1703.734530] binder: 1463:5055 cannot find target node
[ 1703.734558] binder: 5055:1463 transaction call to 0:0 failed 3550/29189/-22, size 0-0 line 3030
[ 1704.735764] binder: 1511:1400 cannot find target node
[ 1704.735768] binder: 1463:5055 cannot find target node
[ 1704.735800] binder: 5055:1463 transaction call to 0:0 failed 3553/29189/-22, size 0-0 line 3030
[ 1704.735809] binder: 1400:1511 transaction call to 0:0 failed 3552/29189/-22, size 0-0 line 3030
[ 1705.737109] binder: 1463:5055 cannot find target node
[ 1705.737109] binder: 1511:1400 cannot find target node
[ 1705.737142] binder: 1400:1511 transaction call to 0:0 failed 3555/29189/-22, size 0-0 line 3030
[ 1705.737151] binder: 5055:1463 transaction call to 0:0 failed 3554/29189/-22, size 0-0 line 3030
[ 1708.741454] binder_debug: 8 callbacks suppressed
[ 1708.741522] binder: 1511:1400 cannot find target node
[ 1708.741540] binder: 1400:1511 transaction call to 0:0 failed 3561/29189/-22, size 0-0 line 3030
[ 1709.742916] binder: 1463:5055 cannot find target node
[ 1709.742938] binder: 1511:1400 cannot find target node
[ 1709.742952] binder: 1400:1511 transaction call to 0:0 failed 3563/29189/-22, size 0-0 line 3030
[ 1709.742959] binder: 5055:1463 transaction call to 0:0 failed 3562/29189/-22, size 0-0 line 3030
[ 1710.744415] binder: 1463:5055 cannot find target node
[ 1710.744415] binder: 1511:1400 cannot find target node
[ 1710.744448] binder: 1400:1511 transaction call to 0:0 failed 3564/29189/-22, size 0-0 line 3030
[ 1710.744458] binder: 5055:1463 transaction call to 0:0 failed 3565/29189/-22, size 0-0 line 3030
I'm seeing the same issue as OP except my kernel already had psi=1 enabled.
running on postmarketOS on aarch64
$ zcat /proc/config.gz | grep -Ei 'psi|binder' CONFIG_PSI=y # CONFIG_PSI_DEFAULT_DISABLED is not set CONFIG_ANDROID_BINDER_IPC=y # CONFIG_ANDROID_BINDERFS is not set CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" CONFIG_ANDROID_BINDER_IPC_SELFTEST=ydmesg is full of logs like this:
1703.734499] binder_debug: 7 callbacks suppressed [ 1703.734530] binder: 1463:5055 cannot find target node [ 1703.734558] binder: 5055:1463 transaction call to 0:0 failed 3550/29189/-22, size 0-0 line 3030 [ 1704.735764] binder: 1511:1400 cannot find target node [ 1704.735768] binder: 1463:5055 cannot find target node [ 1704.735800] binder: 5055:1463 transaction call to 0:0 failed 3553/29189/-22, size 0-0 line 3030 [ 1704.735809] binder: 1400:1511 transaction call to 0:0 failed 3552/29189/-22, size 0-0 line 3030 [ 1705.737109] binder: 1463:5055 cannot find target node [ 1705.737109] binder: 1511:1400 cannot find target node [ 1705.737142] binder: 1400:1511 transaction call to 0:0 failed 3555/29189/-22, size 0-0 line 3030 [ 1705.737151] binder: 5055:1463 transaction call to 0:0 failed 3554/29189/-22, size 0-0 line 3030 [ 1708.741454] binder_debug: 8 callbacks suppressed [ 1708.741522] binder: 1511:1400 cannot find target node [ 1708.741540] binder: 1400:1511 transaction call to 0:0 failed 3561/29189/-22, size 0-0 line 3030 [ 1709.742916] binder: 1463:5055 cannot find target node [ 1709.742938] binder: 1511:1400 cannot find target node [ 1709.742952] binder: 1400:1511 transaction call to 0:0 failed 3563/29189/-22, size 0-0 line 3030 [ 1709.742959] binder: 5055:1463 transaction call to 0:0 failed 3562/29189/-22, size 0-0 line 3030 [ 1710.744415] binder: 1463:5055 cannot find target node [ 1710.744415] binder: 1511:1400 cannot find target node [ 1710.744448] binder: 1400:1511 transaction call to 0:0 failed 3564/29189/-22, size 0-0 line 3030 [ 1710.744458] binder: 5055:1463 transaction call to 0:0 failed 3565/29189/-22, size 0-0 line 3030
Same here. It works fine with a mainline kernel, but I don't intend to use those.
Please report downstream issues downstream. As far as I know postmarketOS hasn't updated to a recent version of waydroid yet
But guyz what is Waydroid
Reeh
On Tue, 29 Nov 2022, 2:34 am Alessandro Astone, @.***> wrote:
Closed #136 https://github.com/waydroid/waydroid/issues/136 as not planned.
— Reply to this email directly, view it on GitHub https://github.com/waydroid/waydroid/issues/136#event-7907657261, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVBD25BEL7YNVBFUGBX2VB3WKU6RDANCNFSM5FNJI33A . You are receiving this because you are subscribed to this thread.Message ID: @.***>
To add the psi=1 kernel opt for the current kernel with grubby:
sudo grubby --update-kernel="/boot/vmlinuz-$(uname -r)" --args="psi=1"
sudo bash -c "cat /boot/loader/entries/*.conf" | grep psi=1 -C 5
To add the psi=1 kernel opt for ALL kernels with grubby e.g. after you've already confirmed that booting with psi=1 works and you know that you can edit kernel opts to remove it if necessary:
sudo grubby --update-kernel="ALL" --args="psi=1"
sudo bash -c "cat /boot/loader/entries/*.conf" | grep psi=1 -C 5
PostmarketOS
https://www.google.com/search?q=grub+aarch64
- https://gist.github.com/tstellanova/dea7593a7dfe4f48432a58cb007e7056
- https://github.com/Tow-Boot/Tow-Boot/issues/110#issuecomment-1048408706
So, to boot GRUB, make sure your distro installs it, or a shim, at
ESP:\BOOT\EFI\bootaa64.efiassuming this is for AArch64.
Leaving this here as this is a top search result for those symptoms. For me the solution for those binder issues was echo 1 > /proc/sys/abi/vsyscall32
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line.
default Kernel config for this feature is
CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=yso you need to enable PSI. i hope works for you all
@dev implement plz
I can confirm the same issue running on 5.14.13-xanmod1-1 anbox (from AUR)
Solved by adding "psi=1" to kernel command line. default Kernel config for this feature is
CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=yso you need to enable PSI. i hope works for you all
@dev implement plz
This fix is ridiculous CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=y -> this means PSI is disabled and enabled by the command line during boot if ps=1 is set I had CONFIG_PSI=y CONFIG_PSI_DEFAULT_DISABLED=n -> which means it is enabled by default but still got the same error
but i don't get the error anymore
CONFIG_PSI_DEFAULT_DISABLED=n
This is not valid syntax for a kernel config file.
To disable it you should have written # CONFIG_PSI_DEFAULT_DISABLED is not set
CONFIG_PSI_DEFAULT_DISABLED=n
This is not valid syntax for a kernel config file. To disable it you should have written
# CONFIG_PSI_DEFAULT_DISABLED is not set
What i meant is if CONFIG_PSI_DEFAULT is not set to y
CONFIG_PSI_DEFAULT_DISABLED=n
If you paid attention to the original message, they wrote that the default kernel config is
CONFIG_PSI_DEFAULT_DISABLED=y
and that they had to add psi=1 to the command line to enable.
CONFIG_PSI_DEFAULT_DISABLED=n
If you paid attention to the original message, they wrote that the default kernel config is
CONFIG_PSI_DEFAULT_DISABLED=yand that they had to add psi=1 to the command line to enable.
Well someone woke up on the wrong side of the bed, but since we are being pedantic
CONFIG_PSI_DEFAULT_DISABLED=y
Does not exist, it is simply not set
2nd it does not change the point that the implementation is garbage since the combination of kernel flags and bootline parameters is obviously an issue