My system runs perfectly fine, but I noticed that udev was not installed. So I tried running yay -S udev and that seemed to install systemD, which got a bunch of errors and warnings along the installation. Very unexpected coming from such a foundational package. Here is the output from yay -S systemd (there is some german in there, but only at the not so important places)
:: Installation fortsetzen? [J/n] j (1/1) Schlüssel im Schlüsselbund werden geprüft [####################################################################] 100% (1/1) Paket-Integrität wird überprüft [####################################################################] 100% (1/1) Paket-Dateien werden geladen [####################################################################] 100% (1/1) Auf Dateikonflikte wird geprüft [####################################################################] 100% (1/1) Verfügbarer Festplattenspeicher wird ermittelt [####################################################################] 100% :: Pre-transaction-Hooks werden gestartet … (1/1) Creating Timeshift snapshot before upgrade... ==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE. :: Paketänderungen werden verarbeitet … (1/1) Reinstalliert wird systemd [####################################################################] 100% :: Post-transaction-Hooks werden gestartet … ( 1/10) Creating system user accounts... ( 2/10) Updating journal message catalog... ( 3/10) Reloading system manager configuration... ( 4/10) Updating udev hardware database... ( 5/10) Applying kernel sysctl settings... ( 6/10) Creating temporary files... ( 7/10) Reloading device manager configuration... ( 8/10) Arming ConditionNeedsUpdate... ( 9/10) Updating linux initcpios... ==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default' ==> Using configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img ==> Starting build: '4.14.280-1-MANJARO' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [consolefont] ==> WARNING: consolefont: no font found in configuration -> Running build hook: [filesystems] -> Running build hook: [fsck] ==> Generating module dependencies ==> ERROR: file not found: '/lib/modules/4.14.280-1-MANJARO/modules.builtin.modinfo' depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.d1yVxw/root/lib/modules/4.14.280-1-MANJARO: No such file or directory ==> Creating gzip-compressed initcpio image: '/boot/initramfs-4.14-x86_64.img' ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback' ==> Using configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect ==> Starting build: '4.14.280-1-MANJARO' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] ==> WARNING: Possibly missing firmware for module: 'qed' ==> WARNING: Possibly missing firmware for module: 'qla1280' ==> WARNING: Possibly missing firmware for module: 'qla2xxx' ==> WARNING: Possibly missing firmware for module: 'bfa' -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [consolefont] ==> WARNING: consolefont: no font found in configuration -> Running build hook: [filesystems] -> Running build hook: [fsck] ==> Generating module dependencies ==> ERROR: file not found: '/lib/modules/4.14.280-1-MANJARO/modules.builtin.modinfo' depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.eoiCZc/root/lib/modules/4.14.280-1-MANJARO: No such file or directory ==> Creating gzip-compressed initcpio image: '/boot/initramfs-4.14-x86_64-fallback.img' ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default' ==> Using configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img ==> Starting build: '5.15.125-1-MANJARO' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] sort: Lesen unmöglich: '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/uevent': Datei oder Verzeichnis nicht gefunden modprobe: ERROR: missing parameters. See -h. -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [consolefont] ==> WARNING: consolefont: no font found in configuration -> Running build hook: [filesystems] -> Running build hook: [fsck] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img' ==> Image generation successful ==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback' ==> Using configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect ==> Starting build: '5.15.125-1-MANJARO' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] ==> WARNING: Possibly missing firmware for module: 'qed' ==> WARNING: Possibly missing firmware for module: 'qla1280' ==> WARNING: Possibly missing firmware for module: 'qla2xxx' ==> WARNING: Possibly missing firmware for module: 'bfa' -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [consolefont] ==> WARNING: consolefont: no font found in configuration -> Running build hook: [filesystems] -> Running build hook: [fsck] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img' ==> Image generation successful Fehler: Befehl konnte nicht korrekt ausgeführt werden (10/10) Reloading system bus configuration...
Does anyone have any idea on what is going wrong here?
The actual reason I even noticed that udev was missing, was me trying to connect my phone to the laptop for game developement in Godot. One can send the game directly to the phone via usb, but the phone didn’t even show up, so that’s how I noticed there was something off.
there is no way you are missing udev
Arch Linux (and Manjaro) have it inside the systemd package (which you already has as stated from pacmanPaketänderungen werden verarbeitet … (1/1) Reinstalliert wird systemd)the thing you are probably is missing are android specific udev rules
Arch Linux has them inside the packageandroid-udevbut I don’t really know if Manjaro does the same
https://wiki.archlinux.org/title/Android_Debug_Bridge#Usage
try to connect your phone via adb before you try anything with Godot or Android Studio for that matterIch würde dir aber empfehlen vorher mal einen Neustart zu machen, es fehlen wohl kernel modules bei dir (?) was wohl auf ein Kernel update ohne kernel modules reload (oder noch einfacher: ein Neustart) schließt
Thank you very much for explaining. I will pursue as you said and look into the link you provided.
That’s just how mkinitcpio looks, happens every time you install something related to the kernel, nothing to worry about. systemd is always installed on Manjaro and most other distros, you can see near the top that it’s being reinstalled, not installed. It probably told you that before asking for confirmation. udev is part of systemd and thus was also already installed.
What you’re probably missing is android-tools or android-udev, needed to connect your phone to your Linux box. You may also have to enable something like Allow App installation via USB or USB Debugging in your phone’s developer settings.
Thing is, when I just run “udev”, it says that udev wasn’t found.
How am I supposed to use udev, for example to reload the rules?
udev provides the command udevadm and you don’t need to use it because the android-udev package provides the rules that you need.
Time to Debian XD
