For A , try with thes options on boot kernel
processor.max_cstate=5 rcu_nocbs=0-7 iommu=pt
or iommu=soft
for B , use ventoy for USB iso manjaro
Thank you stephane
where do I have to put these options ?
in /etc/default/grub
on line GRUB_CMDLINE_LINUX_DEFAULT=
sudo nano /etc/default/grub
sudo update-grubThanks again.
I tried all what you suggested. Here my results.
@ A. Regarding the installed Manjaro system:
I could install a fresh Manjaro version; this time wifi was available during installation. After the installation the initial restart was not successful, so I changed the /etc/default/grub as mentioned, trying both iommu=pt and iommu=soft. The latter one doesn’t work at all. With pt Grub starts. For Manjaro the “normal” boot mode doesn’t work: no boot process starts.
By selecting the “fallback initramfs” the boot sequence starts always, but still gets stuck. So I still can’t boot into the system, however it now stops at many different points. I restarted several times and collected a few:
[ OK ] Started Load/Save RF Kill Switch Status...[ OK ] Finished TLP system startup/shutdown...[ OK ] Started Light Display Manager.[ 5.830449] kfd kfd: error getting iommu info. is the iommu enable?[ 5.830506] kfd kfd: Error initializing iommun2[ 5.830604] kfd kfd: device 1002:15dd NOT added due to errors[ OK ] Reached target Graphical Interface.[ ***] A start job is running for Daily man-db regeneration (1m 552 / no limit)[ OK ] Started User Login Management.
Hopefully this provides some deeper insights.
@ B. The live media
First of all the good. Ventoy - I had never heard of it - is really easy to use and saves so much time spent for the formatting and flashing process before.
It assures further that the live media is starting to boot, however the boot process still fails in almost all cases.
Manjaro gets stuck constantly at Started Load/Save RF Kill Switch Status no matter what edition or configuration I chose.
For curiosity I tested
Artix. When using Runit it first stoped at
:: Waiting for udev uevents to be processed [busy]
In the second boot attempt it started the live system successfully and wifi was also available.
With OpenRC it hangs at
mtab |* Updating /etc/mtab ...
and at
bootmisc |* Creating user login records ...
Both print in the very first line:
[ 1.428217] pci 0000:00:00.2 : AMD-Vi: Unable to read/write to IOMMU perf counter
EndeavourOS and elementaryOS do not work any more.
Maybe these observations can help.
can you report then
inxi -Fzayou can also check on this site
first a little addition: I tested the two settings for iommu more extensively and cannot see a difference any more as reported in my last post.
So, set to soft shows the same behavior as pt does. pt showed right now a distorted screen / screen tearing and then restarted itself instead of just getting stuck.
Here the report of inxi -Fza
[stjerne@reiknar default]$ inxi -Fza
System: Kernel: 5.10.23-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 root=UUID=2ed44c5c-7587-4c08-9f5d-a7f01c695674 rw
processor.max_cstate=5 rcu_nocbs=0-7 iommu=soft
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 vt: 7 dm: LightDM 1.30.0 Distro: Manjaro Linux
base: Arch Linux
Machine: Type: Desktop System: HP product: HP EliteDesk 705 G4 DM 65W v: DBXEnabled serial: <filter> Chassis: type: 3
serial: <filter>
Mobo: HP model: 83E9 v: KBC Version 07.D0.00 serial: <filter> UEFI: HP v: Q26 Ver. 02.13.00 date: 08/05/2020
CPU: Info: Quad Core model: AMD Ryzen 5 PRO 2400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen
family: 17 (23) model-id: 11 (17) stepping: N/A microcode: 8101016 cache: L2: 2 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 57518
Speed: 1420 MHz min/max: 1600/3600 MHz boost: enabled Core speeds (MHz): 1: 1420 2: 1423 3: 1421 4: 1424 5: 1422
6: 1422 7: 1500 8: 1593
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu
v: kernel bus-ID: 0a:00.0 chip-ID: 1002:15dd class-ID: 0300
Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 7680x2160 s-dpi: 96 s-size: 2032x571mm (80.0x22.5") s-diag: 2111mm (83.1")
Monitor-1: DisplayPort-1 res: 3840x2160 hz: 60 dpi: 157 size: 621x341mm (24.4x13.4") diag: 708mm (27.9")
Monitor-2: DisplayPort-3 res: 3840x2160 hz: 60 dpi: 157 size: 621x341mm (24.4x13.4") diag: 708mm (27.9")
OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.10.23-1-MANJARO LLVM 11.1.0) v: 4.6 Mesa 20.3.4
direct render: Yes
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus-ID: 0a:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus-ID: 0a:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.10.23-1-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.23 running: no
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel
port: 3300 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Intel Wireless-AC 9260 driver: N/A modules: iwlwifi port: 3000 bus-ID: 06:00.0 chip-ID: 8086:2526
class-ID: 0280
Bluetooth: Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb v: 0.8 bus-ID: 2-10:3 chip-ID: 8087:0025
class-ID: e001
Report: This feature requires one of these tools: hciconfig/bt-adapter
Drives: Local Storage: total: 1.4 TiB used: 6.32 GiB (0.4%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLB512HBJQ-000H1 size: 476.94 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: HPS0NEXF temp: 48.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB block-size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: GPT
Partition: ID-1: / raw-size: 244.14 GiB size: 239.25 GiB (98.00%) used: 6.29 GiB (2.6%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%) used: 316 KiB (0.0%) fs: vfat dev: /dev/sda1
maj-min: 8:1
ID-3: /home raw-size: 664.06 GiB size: 652.57 GiB (98.27%) used: 30 MiB (0.0%) fs: ext4 dev: /dev/sda3 maj-min: 8:3
Swap: Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 22.31 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4 maj-min: 8:4
Sensors: System Temperatures: cpu: 47.5 C mobo: N/A gpu: amdgpu temp: 47.0 C
Fan Speeds (RPM): N/A
Info: Processes: 243 Uptime: 18m wakeups: 1 Memory: 14.58 GiB used: 1.08 GiB (7.4%) Init: systemd v: 247 tool: systemctl
Compilers: gcc: N/A Packages: pacman: 1058 lib: 297 flatpak: 0 Shell: Bash v: 5.1.0 running-in: xfce4-terminal
inxi: 3.3.03
[stjerne@reiknar default]$
Regarding the hw-probe: I’m just working on it. It’s a bit tricky since I can’t get wifi access any more.
have you checked in the log ?
sudo journalctl -b0 -p4
sudo journalctl -b -1 -p4I wonder if next time you get it to work again, install both kernels 5.11 and 5.12, and see if those would fix anything.
Or, if you install Manjaro via Manjaro Architect, you can just select multiple kernels to install.
Good news: regarding hw-probe and journal-ctl I could produce some output.
Bad news: during the last 15 to 20 attempts non of the Manjaro systems had started; neither the installed one, nor any of the live systems. So I couldn’t install hw-probe.
Therefore all results below are created under ArcoLinuxB running as live system (proposed as Live CD2 on the linux-hardware homepage ).
So are these results meaningful at all? I will redo them with my Manjaro system as soon as it boots up again, or I could reinstall it with Manjaro Architect. I will then try include other Kernels too - thanks for the suggestion.
Results
-
hw-probe: please find them at https://linux-hardware.org/?probe=d9a6f8bf8f
-
sudo journalctl -b0 -p4reports as follows:
[liveuser@ArcoLinuxB-awesome ~]$ sudo journalctl -b0 -p4
-- Journal begins at Sat 2021-04-24 00:12:17 UTC, ends at Sat 2021-04-24 00:28:43 UTC. --
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: pci 0000:00:00.2: PCI INT A: no GSI
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: PPR NX GT IA GA PC GA_vAPIC
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: nvme nvme0: missing or invalid SUBNQN field.
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: ata1.00: supports DRM functions and may not be fully accessible
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: ata1.00: supports DRM functions and may not be fully accessible
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:02: duplicate WMI GUID 2B814318-4BE8-4707-9D84-A190A859B5D0 (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:02: duplicate WMI GUID 41227C2D-80E1-423F-8B8E-87E32755A0EB (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: caller pci_map_rom+0x68/0x190 mapping multiple BARs
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: ipmi_si: Unable to find any System Interface(s)
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B06 (\_SB.PCI0.SMBS.SMBO) (20201113/utaddress-204)
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: hp_wmi: query 0x4 returned error 0x5
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: hp_wmi: query 0xd returned error 0x5
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: hp_wmi: query 0x1b returned error 0x5
Apr 24 00:12:18 ArcoLinuxB-awesome systemd-udevd[491]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 0
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 1
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 2
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 3
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 4
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 6
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 8
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 9
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 10
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 11
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 15
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 16
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 18
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 19
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 20
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 21
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 28
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: wl: loading out-of-tree module taints kernel.
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: wl: module license 'MIXED/Proprietary' taints kernel.
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: Disabling lock debugging due to kernel taint
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Apr 24 00:12:18 ArcoLinuxB-awesome systemd-udevd[504]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Apr 24 00:12:18 ArcoLinuxB-awesome systemd-udevd[503]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Apr 24 00:12:23 ArcoLinuxB-awesome kernel: kauditd_printk_skb: 1 callbacks suppressed
Apr 24 00:12:24 ArcoLinuxB-awesome NetworkManager[591]: <warn> [1619223144.2540] sup-iface[52aaa093fd697481,0,wlp6s0]: call-p2p-cancel: failed with P2P cancel failed
Apr 24 00:12:27 ArcoLinuxB-awesome ntpd[652]: bind(23) AF_INET6 fe80::6472:a0de:4278:fa8a%2#123 flags 0x11 failed: Cannot assign requested address
Apr 24 00:12:27 ArcoLinuxB-awesome ntpd[652]: unable to create socket on eno1 (4) for fe80::6472:a0de:4278:fa8a%2#123
Apr 24 00:12:30 ArcoLinuxB-awesome sddm-helper[874]: gkr-pam: no password is available for user
Apr 24 00:12:30 ArcoLinuxB-awesome kernel: kauditd_printk_skb: 58 callbacks suppressed
Apr 24 00:12:31 ArcoLinuxB-awesome systemd[881]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied
Apr 24 00:12:38 ArcoLinuxB-awesome kernel: kauditd_printk_skb: 11 callbacks suppressed
Apr 24 00:12:39 ArcoLinuxB-awesome xdg-desktop-por[1337]: Locale not supported by C library.
Using the fallback 'C' locale.
Apr 24 00:12:40 ArcoLinuxB-awesome pulseaudio[1102]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Apr 24 00:12:40 ArcoLinuxB-awesome pulseaudio[1102]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Apr 24 00:12:40 ArcoLinuxB-awesome pulseaudio[1102]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Apr 24 00:12:40 ArcoLinuxB-awesome upowerd[1388]: did not recognise USB path /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001, please report
Apr 24 00:13:10 ArcoLinuxB-awesome xdg-desktop-por[1314]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Apr 24 00:16:06 ArcoLinuxB-awesome kernel: r8169 0000:05:00.0: invalid short VPD tag 00 at offset 1
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: serial 0000:05:00.1: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: serial 0000:05:00.2: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: pci 0000:05:00.3: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: ehci-pci 0000:05:00.4: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:27:54 ArcoLinuxB-awesome systemd-coredump[9197]: Process 8828 (urxvt) of user 1000 dumped core.
Stack trace of thread 8828:
#0 0x00007fb79236adcd getenv (libc.so.6 + 0x3edcd)
#1 0x00007fb79258d546 perl_destruct (libperl.so + 0x73546)
#2 0x0000557a1cf52336 _ZN16rxvt_perl_interpD1Ev (urxvt + 0x4d336)
#3 0x00007fb79236b697 __run_exit_handlers (libc.so.6 + 0x3f697)
#4 0x00007fb79236b83e exit (libc.so.6 + 0x3f83e)
#5 0x00007fb792353b2c __libc_start_main (libc.so.6 + 0x27b2c)
#6 0x0000557a1cf33cfe _start (urxvt + 0x2ecfe)
- and
sudo journalctl -b -l -p4gives:
[liveuser@ArcoLinuxB-awesome ~]$ sudo journalctl -b -l -p4
-- Journal begins at Sat 2021-04-24 00:12:17 UTC, ends at Sat 2021-04-24 00:30:08 UTC. --
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: pci 0000:00:00.2: PCI INT A: no GSI
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: PPR NX GT IA GA PC GA_vAPIC
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: nvme nvme0: missing or invalid SUBNQN field.
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: ata1.00: supports DRM functions and may not be fully accessible
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: ata1.00: supports DRM functions and may not be fully accessible
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:02: duplicate WMI GUID 2B814318-4BE8-4707-9D84-A190A859B5D0 (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:02: duplicate WMI GUID 41227C2D-80E1-423F-8B8E-87E32755A0EB (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: caller pci_map_rom+0x68/0x190 mapping multiple BARs
Apr 24 00:12:17 ArcoLinuxB-awesome kernel: ipmi_si: Unable to find any System Interface(s)
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B06 (\_SB.PCI0.SMBS.SMBO) (20201113/utaddress-204)
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: hp_wmi: query 0x4 returned error 0x5
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: hp_wmi: query 0xd returned error 0x5
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: hp_wmi: query 0x1b returned error 0x5
Apr 24 00:12:18 ArcoLinuxB-awesome systemd-udevd[491]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 0
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 1
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 2
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 3
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 4
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 6
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 8
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 9
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 10
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 11
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 15
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 16
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 18
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 19
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 20
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 21
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: iwlwifi 0000:06:00.0: WRT: Overriding region id 28
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: wl: loading out-of-tree module taints kernel.
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: wl: module license 'MIXED/Proprietary' taints kernel.
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: Disabling lock debugging due to kernel taint
Apr 24 00:12:18 ArcoLinuxB-awesome kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Apr 24 00:12:18 ArcoLinuxB-awesome systemd-udevd[504]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Apr 24 00:12:18 ArcoLinuxB-awesome systemd-udevd[503]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Apr 24 00:12:23 ArcoLinuxB-awesome kernel: kauditd_printk_skb: 1 callbacks suppressed
Apr 24 00:12:24 ArcoLinuxB-awesome NetworkManager[591]: <warn> [1619223144.2540] sup-iface[52aaa093fd697481,0,wlp6s0]: call-p2p-cancel: failed with P2P cancel failed
Apr 24 00:12:27 ArcoLinuxB-awesome ntpd[652]: bind(23) AF_INET6 fe80::6472:a0de:4278:fa8a%2#123 flags 0x11 failed: Cannot assign requested address
Apr 24 00:12:27 ArcoLinuxB-awesome ntpd[652]: unable to create socket on eno1 (4) for fe80::6472:a0de:4278:fa8a%2#123
Apr 24 00:12:30 ArcoLinuxB-awesome sddm-helper[874]: gkr-pam: no password is available for user
Apr 24 00:12:30 ArcoLinuxB-awesome kernel: kauditd_printk_skb: 58 callbacks suppressed
Apr 24 00:12:31 ArcoLinuxB-awesome systemd[881]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied
Apr 24 00:12:38 ArcoLinuxB-awesome kernel: kauditd_printk_skb: 11 callbacks suppressed
Apr 24 00:12:39 ArcoLinuxB-awesome xdg-desktop-por[1337]: Locale not supported by C library.
Using the fallback 'C' locale.
Apr 24 00:12:40 ArcoLinuxB-awesome pulseaudio[1102]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Apr 24 00:12:40 ArcoLinuxB-awesome pulseaudio[1102]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Apr 24 00:12:40 ArcoLinuxB-awesome pulseaudio[1102]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Apr 24 00:12:40 ArcoLinuxB-awesome upowerd[1388]: did not recognise USB path /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001, please report
Apr 24 00:13:10 ArcoLinuxB-awesome xdg-desktop-por[1314]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Apr 24 00:16:06 ArcoLinuxB-awesome kernel: r8169 0000:05:00.0: invalid short VPD tag 00 at offset 1
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: serial 0000:05:00.1: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: serial 0000:05:00.2: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: pci 0000:05:00.3: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:16:07 ArcoLinuxB-awesome kernel: ehci-pci 0000:05:00.4: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Apr 24 00:27:54 ArcoLinuxB-awesome systemd-coredump[9197]: Process 8828 (urxvt) of user 1000 dumped core.
Stack trace of thread 8828:
#0 0x00007fb79236adcd getenv (libc.so.6 + 0x3edcd)
#1 0x00007fb79258d546 perl_destruct (libperl.so + 0x73546)
#2 0x0000557a1cf52336 _ZN16rxvt_perl_interpD1Ev (urxvt + 0x4d336)
#3 0x00007fb79236b697 __run_exit_handlers (libc.so.6 + 0x3f697)
#4 0x00007fb79236b83e exit (libc.so.6 + 0x3f83e)
#5 0x00007fb792353b2c __libc_start_main (libc.so.6 + 0x27b2c)
#6 0x0000557a1cf33cfe _start (urxvt + 0x2ecfe)
for adding kernels
sudo mhwd-kernel -i linux511
sudo mhwd-kernel -i linux512
sudo pacman -S linux511-headers linux512-headerspress Esc on boot for grub , go in advanced an select another version kernel
on report hwdb
- iommu is not recognized
- [drm] BIOS signature incorrect 0 0
Hello
during the weekend I installed the two newer Kernels (5.11.14-1 and 5.12.rc7) and tried to boot with them.
Unfortunately switching kernels doesn’t change anything. No matter if in normal or in fallback mode. Problems remain the same.
Furthermore, I finally found where the
[drm] BIOS signature incorrect 0 0
message was reported and tried to understand what it means.
But it goes far beyond my technical knowledge. Here’s what I get 'til now: drm is the abbreviation for digital right management? So whenever booting Linux the bios is regarded as being not correct, and the bios is a more fundamental part of the PC, so it causes errors and malfunction because some other functionalites are denied.
on report hwdb
iommu is not recognized
I haven’t found that entry yet, but again I don’t understand the details but I understand that iommu is a crucial part in managing the memory in the PC.
Anyway, I googled both entries as well, but couldn’t find any solution I was able to understand or to perform on myself.
What would you recommend to do next?
Is there a solution to make Linux work?
Greetings
there is theses errors
pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[drm] BIOS signature incorrect 0 0
amdgpu 0000:30:00.0: amdgpu: RAS: optional ras ta ucode is not available
amdgpu 0000:30:00.0: amdgpu: RAP: optional rap ta ucode is not available
amdgpu 0000:30:00.0: [drm] fb0: amdgpudrmfb frame buffer device
@Manjaro-Team , can you check in microcode Amd & firmware linux 5.12 if there is info about any Ryzen Pro ?
omg I didn’t see the wood for the trees… thanks.
I changed /etc/default/grub by adding amd_iommu and setting iommu=pt.
This seems to get rid of the iommo thing - but I’m not sure yet.
The main problem remains.
So I guess the main problem is caused by the drm thing, correct?
Meanwhile I found that “drm” is the abbreviation for “direct rendering model” too. What does “drm” stands for in the [drm] BIOS signature incorrect 0 0 context?
More important:
What can I do to correct the BIOS signature? Is this possible at all?
I updated the BIOS to the most recent version and disable everything that looked to me somehow security related. However a “digital right management” option is not provided.
But again nothing has even the slightest effect. The system remains getting stuck in the boot process.
Everytime you use team handle you ping 16 people, only one person deals with kernel things, did you think about using gitlab to open a issue, also IOMMU does not come active by default.
since 2 stable versions
- many users have freeze ( many in Kde )
- some have errors in amdgpu drivers
then it 's a better advice from mine to stop for the moment
The issue is not always revealed in boot output, post your xorg.log file.
Also this is not arcolinux forum, that is a different system with different configurations and most likely kernel patches and as such you should go there for questions.
post your xorg.log file
Getting the xorg file will be the next challenge. Meanwhile the Grub menu has disappeared completely as well 
.
Btw: not even the Arch installer launches…
As soon as I can read it out I’ll post xorg immediately. Maybe Manjaro gives me a chance…
Also this is not arcolinux forum, that is a different system with different configurations and most likely kernel patches and as such you should go there for questions.
@codesardine
I’m definetely a noob when it comes to all the technical stuff, but I can distinguish between different Linux distributions and their forums respectively 
. But my problem is affecting Manjaro: it hardly ever starts and gets stuck already during the boot process. No matter if an installed system or a live system is booted and no matter what edition is chosen. So unfortunately chances to gather information are very limited. I chose Arcolinux because
a. it was recommended by hw-probe (as “Live CD2”)
b. it worked (that time)
c. I hoped it might provide more valuable insights in a Manjaro related problem since both share the Arch base. Ubuntu and derivates boot insignificantly more frequently, but the differences here should be even bigger.
However if the system booted up it seems to run fine. Only wifi is not always recognized. But sound, video, graphics etc. everythings runs smooth without any issues. So I’m wondering because it shows that the hardware can work absolutely fine.
If the xorg file reveals no new aspects, I think you’re right, and stopping here is the best.
Thank you very much for your hints and ideas!
I’m still a bit irritated because the hardware is not bleeding etch any more (it’s around three years old now), so I had not expected to face issues that severe - on many Linux distros.
Manjaro also does not have arch linux installer, what are we debugging here, manjaro, arcolinux or archlinux?
I have not seen one manjaro issue on this post yet, you need to be specific about what the issue is.
The last linux distro you installed will override the grub menu from the last, about ryzen the only thing i can tell you is only kernel510 and above might work, iommu is also not active by default on manjaro as I mention above.
iommu is something that is hard to configure and it could cause issues if not done correctly, my first bet is start by disabling that on the kernel and after you solve this issue open another post on how to configure iommu for PCI passthrough.
without correct information is impossible to make sense and try to debug this issue.
files you may want to check:
/home/username/.xsession.errors
/home/username/.local/share/xorg/Xorg.1.log
can you also try with theses parameters
from
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html?highlight=amd_iommu
amd_iommu= [HW,X86-64]
Pass parameters to the AMD IOMMU driver in the system.
Possible values are:
fullflush - enable flushing of IO/TLB entries when
they are unmapped. Otherwise they are
flushed before they will be reused, which
is a lot of faster
off - do not initialize any AMD IOMMU found in
the system
force_isolation - Force device isolation for all
devices. The IOMMU driver is not
allowed anymore to lift isolation
requirements as needed. This option
does not override iommu=pt