Installing Anbox modules (for it to work) causes the system to not boot


In detail, when I try to install Anbox (my cousin wants an Android emulator) I would install the anbox-support package from the AUR, sudo modprobe -a ashmem_linux binder_linux and after the binderfs creation and adding it to /etc/fstab/ with the nofail option and then Anbox would work! yay! sort of. It would be glitchy

(that’s always got to happen with smth I put ages into installing, snaps suck, so I avoid them)

and then I’d reboot, and then it just shows GRUB, but then it just won’t go past this:

Loading kernel linux...
loading initial ramdisk...

and it just stops dead.

I am now reinstalling (btrfs snapshots nor fallback initramfs helped) and wrote this from the live env. By the time I wake up it should be done.

inxi -Fxza

[liveuser@eos-2022.06.23 ~]$ inxi -Fxza
  Kernel: 5.18.5-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: initrd=\arch\boot\intel-ucode.img
    initrd=\arch\boot\x86_64\initramfs-linux.img archisobasedir=arch
    archisolabel=EOS_202206 cow_spacesize=10G
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 nvme_load=yes
  Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
    v: 4.16.1 vt: 1 dm: LightDM v: 1.30.0 Distro: EndeavourOS base: Arch Linux
  Type: Laptop System: Hewlett-Packard product: HP ProBook 4540s
    v: A1018C1100 serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: Hewlett-Packard model: 17F6 v: KBC Version 58.21
    serial: <superuser required> UEFI: Hewlett-Packard v: 68IRR Ver. F.67
    date: 05/30/2018
  ID-1: BAT0 charge: 0.0 Wh (0.0%) condition: 47.5/47.5 Wh (100.0%)
    volts: 10.8 min: 10.8 model: Hewlett-Packard Primary type: Li-ion
    serial: <filter> status: N/A
  Info: model: Intel Core i5-3230M bits: 64 type: MT MCP arch: Ivy Bridge
    gen: core 3 built: 2012-15 process: Intel 22nm family: 6
    model-id: 0x3A (58) stepping: 9 microcode: 0x21
  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: 1665 high: 1856 min/max: 1200/3200 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1554 2: 1856 3: 1812
    4: 1439 bogomips: 20759
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen7 process: Intel 22nm built: 2012-13 ports:
    active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0166 class-ID: 0300
  Device-2: Chicony HP HD Webcam [Fixed] type: USB driver: uvcvideo
    bus-ID: 1-1.3:4 chip-ID: 04f2:b372 class-ID: 0e02
  Display: server: X.Org v: 21.1.3 compositor: xfwm v: 4.16.1 driver: X:
    loaded: intel unloaded: modesetting alternate: fbdev,vesa gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: LVDS-1 mapped: LVDS1 model: Chi Mei Opto 0x15a1 built: 2011
    res: 1366x768 hz: 60 dpi: 102 gamma: 1.2 size: 340x190mm (13.39x7.48")
    diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    v: 4.2 Mesa 22.1.2 direct render: Yes
  Device-1: Intel 7 Series/C216 Family High Definition Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1e20 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.5-arch1-1 running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.52 running: yes
  Device-1: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard
    driver: rt2800pci v: 2.3.0 modules: wl pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 bus-ID: 03:00.0 chip-ID: 1814:3290 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
  Device-1: Ralink RT3290 Bluetooth vendor: Hewlett-Packard driver: N/A pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.1 chip-ID: 1814:3298
    class-ID: 0d11
  Report: bt-service: enabled,stopped note: tool can't run
  Local Storage: total: 494.67 GiB used: 2 GiB (0.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS725050A7E630
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
    speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A440
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: PNY model: USB 2.0 FD
    size: 28.91 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-1: / raw-size: N/A size: 10 GiB used: 704.3 MiB (6.9%) fs: overlay
    source: ERR-102
  Alert: No swap data was found.
  System Temperatures: cpu: 48.0 C mobo: 0.0 C
  Fan Speeds (RPM): N/A
  Processes: 221 Uptime: 50m wakeups: 2 Memory: 3.72 GiB
  used: 2.61 GiB (70.2%) Init: systemd v: 251 default: multi-user
  tool: systemctl Compilers: gcc: 12.1.0 Packages: pacman: 898 lib: 212
  Shell: Bash v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.18
[liveuser@eos-2022.06.23 ~]$ 

Just noticed that the motherboard firmware seems to have an update, date May 14, 2019.
But check it yourself to make sure it is the correct one if you plan to update it.

Was going to suggest installing into a virtual machine, but your system would not run it well.

Sorry that I can’t be more helpful as I don’t use Android emulator.
Hopefully someone more knowledgeable will chime in! :sweat_smile: