You are not logged in.
Pages: 1
Afternoon everyone,
I did 3 installations of Arch on my Asus Zenbook S 13 OLED UM5302LA. The first and the last one as a standard installation, the second attemp using archinstall. With these 3 installations, I always get these warnings and errors in my journal:
-- Boot c08c809b7c4b48da9c31b242666a6ac8a --
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.1: can't derive routing for PCI INT A
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.1: PCI INT A: not connected
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.3: can't derive routing for PCI INT A
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.3: PCI INT A: not connected
Sep 11 15:06:02 archlucho kernel: pcieport 0000:00:08.2: can't derive routing for PCI INT A
Sep 11 15:06:02 archlucho kernel: pcieport 0000:00:08.2: PCI INT A: not connected
Sep 11 15:06:02 archlucho kernel: hpet_acpi_add: no adress or irqs in_CRS
Sep 11 15:06:02 archlucho kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot withi8042.nopnp
Sep 11 15:06:02 archlucho (udev-worker)[478]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Sep 11 15:06:02 archlucho kernel: cs35141-hda i2c-CSC3551:00-cs35141-hda.0: Cannot add Reset/Speaker ID/SPI CS GPIO Mapping, _DSD aleady exists
Sep 11 15:06:02 archlucho kernel: cs35141-hda i2c-CSC3551:00-cs35141-hda.1: Cannot add Reset/Speaker ID/SPI CS GPIO Mapping, _DSD aleady exists
Sep 11 15:06:02 archlucho kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Sep 11 15:06:07 archlucho kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Sep 11 15:06:08 archlucho kernel: Activation request for 'org.freedesktop.resolve1' failed: the systemd unit 'dbus-org.freedesktop.resolve.1.service' could not be found
Sep 11 15:10:24 archlucho dbus-broker-launch[554]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Sep 11 15:10:24 archlucho NetworkManager[556]: <warn> [1726052749.5344] dispatcher: (10) failed (after 0.126 sec): Could not activate remote peer 'org.freedesktop.nm_dispatcher': activation request failed: unit is invalid
Sep 11 15:10:24 archlucho dbus-broker-launch[554]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Sep 11 15:10:24 archlucho kernel: watchdog: watchdog0: watchdog did not stop!
From this there are two errors:
Sep 11 15:06:07 archlucho kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Sep 11 15:10:24 archlucho dbus-broker-launch[554]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
The first error, I did a lot of research where they were talking about nvidia, but hey, I have an AMD iGPU. I still installed mesa but the issue is still there. The second error seems related to debu-broker and I did not find anything on the forum or even google. There is a warning before this error.
The other logs are warnings. a big chunk of them seems related:
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.1: can't derive routing for PCI INT A
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.1: PCI INT A: not connected
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.3: can't derive routing for PCI INT A
Sep 11 15:06:02 archlucho kernel: pci 0000:00:08.3: PCI INT A: not connected
Sep 11 15:06:02 archlucho kernel: pcieport 0000:00:08.2: can't derive routing for PCI INT A
Sep 11 15:06:02 archlucho kernel: pcieport 0000:00:08.2: PCI INT A: not connected
Once again, I did not find anything.
Regarding the warnings for the speakers, despite having installed alsa, alsa-utils pulseaudio, my sound was working fine but these warnings were still showing. For the other warnings I did not find anything as well.
If usefull, here are the packaged I installed:
amd-ucode
base
linux
linux-firmware
mesa
networkmanager
sudo
vim
Please note that I thoroughly searched this forum, the wiki and google, did pacman -Syu. I don't have any issue with the system, everything is working fine. I am wondering if these are hardware related.
Thank you for your help,
Lucho
Last edited by luchodeco (2024-09-11 12:42:16)
Offline
If your machine is working, the errors may be meaningless. I get errors for both of my ASUS machines from both Arch and Debian, but both of my machines work fine.
Arch Linux with Openbox & Tint2
Offline
have you looked at the kernel boot parameters if they differ about the log level?
could be your non-archinstall variants throw them, too, but just not show them because different log ldvel just suppress them
I doubt that archinstall does anything fundamental different than you on your own which sould cause such differences
Offline
Pages: 1