Garuda-nix Help

Yada · 16 January 2024 17:59

Hello everyone :),
Hey I am trying to use the garuda nix subsystem , but the instillation is failing.
After running

garuda-nix-subsytem install

I get the error

mount: /dev/binderfs: unknown filesystem type 'binder'.
       dmesg(1) may have more information after failed mount system call.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.

System:
  Kernel: 6.6.11-hardened1-1-hardened arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm parameters: pti=on page_alloc.shuffle=1
    BOOT_IMAGE=/@/boot/vmlinuz-linux-hardened root=UUID=5cdaaea7-2d12-4fc9-8004-fda5bae9be22 rw
    rootflags=subvol=@ quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
  Desktop: Hyprland info: waybar vt: 1 dm: 1: LightDM v: 1.32.0 note: stopped 2: SDDM
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G2 v: A3009D510203
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Hewlett-Packard model: 2216 v: KBC Version 96.56 serial: <superuser required>
    UEFI: Hewlett-Packard v: M71 Ver. 01.09 date: 09/01/2015
Battery:
  ID-1: BAT0 charge: 15.6 Wh (80.8%) condition: 19.3/19.3 Wh (100.0%) volts: 13.0 min: 11.4
    model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: charging
CPU:
  Info: model: Intel Core i5-5300U bits: 64 type: MT MCP arch: Broadwell gen: core 5 level: v3
    note: check built: 2015-18 process: Intel 14nm family: 6 model-id: 0x3D (61) stepping: 4
    microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2694 min/max: 500/2900 scaling: driver: intel_cpufreq governor: schedutil
    cores: 1: 2694 2: 2694 3: 2694 4: 2694 bogomips: 18361
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Hewlett-Packard ZBook 15u G2 Mobile Workstation
    driver: i915 v: kernel arch: Gen-8 process: Intel 14nm built: 2014-15 ports: active: eDP-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300
  Device-2: Cheng Uei Precision Industry (Foxlink) HP EliteBook integrated HD Webcam
    driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-7:5
    chip-ID: 05c8:0374 class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.10 with: Xwayland v: 23.2.3 compositor: Hyprland
    driver: X: loaded: modesetting unloaded: vesa alternate: fbdev,intel dri: iris gpu: i915
    display-ID: 1
  Monitor-1: eDP-1 model: AU Optronics 0x233e built: 2012 res: 1600x900 dpi: 132 gamma: 1.2
    size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1600x900
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris device: 1 drv: swrast
    surfaceless: drv: iris wayland: drv: iris x11: drv: iris inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.3-arch1.1 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 5500 (BDW GT2) device-ID: 8086:1616
    memory: 11.3 GiB unified: yes
  API: Vulkan v: 1.3.274 layers: 9 device: 0 type: integrated-gpu name: Intel HD Graphics 5500
    (BDW GT2) driver: mesa intel v: 23.3.3-arch1.1 device-ID: 8086:1616 surfaces: xcb,xlib,wayland
    device: 1 type: cpu name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
    v: 23.3.3-arch1.1 (LLVM 16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 class-ID: 0403
  API: ALSA v: k6.6.11-hardened1-1-hardened status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.1 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: 5080
    bus-ID: 00:19.0 chip-ID: 8086:15a2 class-ID: 0200
  IF: enp0s25 state: down mac
: <filter>
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-4:3 chip-ID: 8087:0a2a class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 7 state: up address: <filter> bt-v: 4.0 lmp-v: 6 status:
    discoverable: yes pairing: yes class-ID: 6c010c
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 5060
    bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 931.51 GiB used: 667.05 GiB (71.6%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: RSM7 scheme: GPT
Partition:
  ID-1: / raw-size: 491.68 GiB size: 491.68 GiB (100.00%) used: 377.09 GiB (76.7%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 296 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 491.68 GiB size: 491.68 GiB (100.00%) used: 377.09 GiB (76.7%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 491.68 GiB size: 491.68 GiB (100.00%) used: 377.09 GiB (76.7%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 491.68 GiB size: 491.68 GiB (100.00%) used: 377.09 GiB (76.7%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 11.57 GiB used: 377.9 MiB (3.2%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 65.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 268 Uptime: 21h 42m wakeups: 6 Memory: total: 12 GiB available: 11.57 GiB
  used: 5.93 GiB (51.2%) Init: systemd v: 255 default: graphical tool: systemctl Compilers:
  gcc: 13.2.1 clang: 16.0.6 Packages: 2564 pm: pacman pkgs: 2538 libs: 521
  tools: aura,pamac,paru,yay pm: flatpak pkgs: 14 pm: snap pkgs: 12 Client: shell wrapper
  v: 5.2.21-release inxi: 3.3.31
Garuda (2.6.22-1):
  System install date:     2022-01-22
  Last full system update: 2024-01-15
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       No/Undetected
  Failed units:            archlinux-keyring-wkd-sync.service systemd-networkd-wait-online.service 
```
```

I have had issues before with /dev/binderfs ....so I need some assistance... First time trying nix,..

NaN · 16 January 2024 18:13

from what I know binder is a module that can be installed. Look here,

Ultimate Guide to install Waydroid in any Arch-based distro(especially Garuda)

.1 Install binder_linux-dkms , which provides binder_linux.

(i) sudo pacman -S binder_linux-dkms

This installs the required binder modules if a kernel doesn’t include them with it, like Arch Linux’s default kernel (or any other kernel)

(check out the above hyperlink link for more information, recent updates and prevailing issues, if any, regarding binder modules)

Install binder_linux-dkms, only if your kernel doesn’t have binder modules inbuilt.

You can check by using the modprobe command:
(The binder module is present by the name binder or binder_linux)

sudo modprobe -a binder or sudo modprobe -a binder_linux

If either of the above command returns a blank output, your kernel already has the binder modules inbuilt.

3. Setting up Kernel Modules

You probably won’t require this step as of now. It was required for earlier versions. You may take a look to have an idea of how it works under the hood.

i) To automatically load the binder modules on boot(Kernel module - ArchWiki ):
Create a file inside /etc/modules-load.d/, which contains the lines:
(sudo nano /etc/modules-load.d/waydroid.conf)
/etc/modules-load.d/waydroid.conf

binder_linux
( it could be simply binder instead of binder_linux depending on the output of modprobe command as used above)

(Save and exit)

ii) To automatically create a mount point for the binder modules at boot
(systemd - ArchWiki ):
Create a file in /etc/tmpfiles.d/ with the content:
(sudo nano /etc/tmpfiles.d/waydroid.conf)
/etc/tmpfiles.d/waydroid.conf

d! /dev/binderfs 0755 root root
(Save and exit)

iii) To automatically mount the binder modules on boot, add a line in the fstab . Using the option nofail here will not greet you with a recovery shell when you are booting a kernel without binderfs support (such as the standard kernel):
(sudo nano /etc/fstab)
/etc/fstab

none                         /dev/binderfs binder   nofail  0      0
(Save and exit)

You can skip the iv) step if you reboot after the iii) one.

iv) Mount the binder modules:
Load the binder modules (Kernel module - ArchWiki )
(mkdir(1) — Arch manual pages )
(mount(8) — Arch manual pages )

sudo modprobe -a binder_linux

(it could be simply binder instead of binder_linux)

sudo mkdir -p /dev/binderfs

sudo mount -t binder none /dev/binderfs

This guide is generously setup by Austin on setting up binder for waydroid however similar steps can be used for you as well to get /dev/binderfs setup.

Yada · 16 January 2024 18:47

I have had issues with binderfs while using Anbox (Crashes the whole system) a while back,… Is it worth installing it for garuda-nix? will it be stable?

NaN · 16 January 2024 18:51

I haven’t used anything android on linux in a short while but I did try waydroid and set it up no problem. You can just try and find out if it doesn’t workout just remove the temp file and fstab entry and remove the package.

TNE · 16 January 2024 20:55

You fix this issue by removing binderfs from /etc/fstab. The reason you are having this issue is that the binderfs issue has been there ever since you last used Android.

Yada · 17 January 2024 10:03

Thanks.

SGS · 17 January 2024 10:08

Btw.

Rather than posting “Thank you”, “+1” or “Agreed”, use the like button .

system · 19 January 2024 10:09

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.