Are you running with PCI-e enable for GEN3?
lol eerrrrr maybe, maybe not. I don’t even know what that is. Is PCi for expansion slots? (squinting my eyes.)
Or do I check in the bios about that?
Is that for connecting 2 gpus?
Go into the Bios and see if PCIE Gen 3 is enabled. I’m sure the graphics card is PCI-E Gen 3?
Edit:
PCI-E Gen 3 is faster port speed for the pci express slot.
sorry for my lack of knowledge. I’ll go and check
It is.
I ask because i think it’s disabled by default.
I see you have the zen kernel installed and the output of the xHCI looks good.
yeah pcie is enabled.
Does it say Gen3?
yeah sorry I missed that it is enabled and gen 3
this is a new error I’ve just seen
DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x00000000585fb000-0x00000000585fdfff], contact BIOS vendor for fixes
There isn’t a firmware update for me to even get though if that is what I need for the Asmedia XMC
What is the deal with the watchdog? I have not done anything on my install related to anything with that?
Well on my thinkpad I got errors about it in the journal if I remember correctly. It was one of the first errors I learnt to deal with. But on this PC I’ve blacklisted it but it still shows when shutting down. I don’t get it. I’ll try to find the link @dalto gave me
https://wiki.archlinux.org/index.php/Improving_performance#Watchdogs
What does
lsmod | grep -e dog -e wdt
return?
[muj@Blackstone ~]$ lsmod | grep -e dog -e wdt
wdat_wdt 20480 0
Guys I’m seriously contemplating just sticking dirty windows back on here and sticking with my thinkpad to learn about linux
1 Like
What is the output of this?
dmesg | grep -i -e DMAR -e IOMMU
[muj@Blackstone ~]$ dmesg | grep -i -e DMAR -e IOMMU
[ 0.007725] ACPI: DMAR 0x000000005829F818 0000D8 (v01 ALWARE ALIENWRE 00000001 INTL 20091013)
[ 0.083252] DMAR: Host address width 46
[ 0.083253] DMAR: DRHD base: 0x000000b5ffc000 flags: 0x0
[ 0.083257] DMAR: dmar0: reg_base_addr b5ffc000 ver 1:0 cap 8d2078c106f0466 ecap f020df
[ 0.083258] DMAR: DRHD base: 0x000000d8ffc000 flags: 0x0
[ 0.083261] DMAR: dmar1: reg_base_addr d8ffc000 ver 1:0 cap 8d2078c106f0466 ecap f020df
[ 0.083262] DMAR: DRHD base: 0x000000fbffc000 flags: 0x0
[ 0.083265] DMAR: dmar2: reg_base_addr fbffc000 ver 1:0 cap 8d2078c106f0466 ecap f020df
[ 0.083265] DMAR: DRHD base: 0x00000092ffc000 flags: 0x1
[ 0.083268] DMAR: dmar3: reg_base_addr 92ffc000 ver 1:0 cap 8d2078c106f0466 ecap f020df
[ 0.083269] DMAR: RMRR base: 0x000000585fb000 end: 0x000000585fdfff
[ 0.083270] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x00000000585fb000-0x00000000585fdfff], contact BIOS vendor for fixes
[ 0.083271] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x00000000585fb000-0x00000000585fdfff]
[ 0.083272] DMAR: ATSR flags: 0x0
[ 0.083273] DMAR-IR: IOAPIC id 12 under DRHD base 0xfbffc000 IOMMU 2
[ 0.083274] DMAR-IR: IOAPIC id 11 under DRHD base 0xd8ffc000 IOMMU 1
[ 0.083274] DMAR-IR: IOAPIC id 10 under DRHD base 0xb5ffc000 IOMMU 0
[ 0.083275] DMAR-IR: IOAPIC id 8 under DRHD base 0x92ffc000 IOMMU 3
[ 0.083275] DMAR-IR: IOAPIC id 9 under DRHD base 0x92ffc000 IOMMU 3
[ 0.083276] DMAR-IR: HPET id 0 under DRHD base 0x92ffc000
[ 0.083277] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[ 0.083277] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[ 0.084173] DMAR-IR: Enabled IRQ remapping in xapic mode
[ 0.264213] iommu: Default domain type: Translated
[ 0.943127] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[ 0.943127] AMD-Vi: AMD IOMMUv2 functionality not available on this system
It’s just a Bios bug which can’t be fixed without changes to it. It’s not a problem. Some error messages are just informational. Unless there is some issue i wouldn’t be worrying about them. You can stick Windows back on but it doesn’t matter which Linux distro you use you will always have these types of error messages which some can be fixed with kernel parameters, or installing a module sometimes or Bios updates or they get fixed with kernel updates. That’s just the nature of the beast. The problem lies in the fact that most Bios is designed around Windows and that’s the problem! I don’t concern myself with every little error message. I do look at them and see if i can correct them or not. On my system i have some that can’t be either. It doesn’t affect the operation.
1 Like
How do you know if it’s an informational error message. Is just from seeing material problems effected by it?
I see you have blacklisted iTCO_wdt.
You might want to add another line in your blacklisted.conf file:
blacklist wdat_wdt
below the iTCO_wdt line; save, and regenerate mkinitcpio as you did before.
1 Like
It’s telling you there is an issue with the Bios. Or it tells you something else but usually it overrides or changes something because it can’t do what’s being asked. Some things cannot be fixed without changes to UEFI\Bios, Linux Firmware, Linux Kernel etc. Or changes in the code for the particular issue. Using kernel parameters sometimes can work but sometimes also can cause other problems. I am a big believer in UEFI\Bios Firmware updates and Kernels. Especially on newer hardware and that is why i use rolling release and the most current Kernel and or Zen-Kernel. I am not an lts kernel user unless the distro uses that. But that’s me! Others will do as they want, can, think or told based on their own needs. Everything i try to do is based on the hardware.
1 Like