You are not logged in.
Pages: 1
Hi
i have run into this problem which is well documented here:
https://superuser.com/questions/1052023 … ivrs-table
There are a few kernel options to try, i tried upgrading the BIOS on my MSI motherboard: no luck.
Tried adding options within the ArchLInux USB key launcher, by entering "TAB" and adding things like iommu=off or the specific iommu details like "ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2", but still the same issue...
Any alternative on launchin the installer without these IOMMU settings ?
Offline
Welcome to the arch linux forums lebutter.
Just to be clear the boot does not continue because of the IVRS issue?
Offline
Hi,
yes correct. The solutions i find online do add certain kernel startup options, but to the existing OS already installed on the machine.
I'd like to add those options for the kernel that's booted on the USB and i'm not really sure. Hitting "<TAB>" to then append a few options didn't help at all.
Offline
Kernel_parameters Please see the first note, I am guessing your system is booting in EFI mode.
Offline
When i get to the prompt the command is:
> .linux boot/x86_64/vmlinuz archisobasedir=arch (...)
to which i append:
ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2
Then i run the same problem again.
Offline
With nomodeset it works though and boots all the way to the root prompt. SO my question is should i go ahead in that state ?
Offline
If you boot with iommu=off or iommu=soft does that also work? If not boot with nomodeset.
Then you can check the ivrs_ioapic values are correct from dmesg and lscpi.
Edit:
corrected iommu=nomodeset to nomodeset
Last edited by loqs (2019-07-21 22:35:56)
Offline
Only nomodeset works... the values i have tried are the correct ones, i got them from lspci from my current OS.
Offline
Possibly in addition to IVRS there is an issue with KMS which requires nomodeset if the following still indicates an IVRS issue I would continue with the installation for now
ivrs_ioapic[5]=00:14.0 ivrs_ioapic[6]=00:00.2 nomodeset
Just to note with nomodeset you will not able to use the X display drivers that require KMS such as modesetting.
Offline
Thanks for your help !
Offline
All my issues actually stem from this, setting nomodeset is only kicking the can down the road.
Setting manually the IVRS entry removes the boot error message mentionning it but there is still the "No southbridge IOAPIC found in IVRS" message...
What's weird is that the current Gentoo USB install image boots fine ! Is there a way to work out where the difference is in terms of setups to find out what's missing in the Arch one for my case ?
Offline
Boot the gentoo kernel the config should be available in /proc/config.gz. Are these the gentoo kernel patches?
Offline
I randomly grep a few things from that working Gentoo kernel on 4.19-57, do you know if i can access the Kernel config of the Arch boot image ?
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_IOMMU_SUPPORT=y
# Generic IOMMU Pagetable Support
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_AMD_IOMMU is not set
# CONFIG_INTEL_IOMMU is not set
CONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_DEBUG is not set
CONFIG_ACPI_HOTPLUG_IOAPIC=y
# CONFIG_FB_RADEON is not set
Here what i intend to do:
- boot on the Arch image, with nomodeset, perform a normal install
- bring in the config which is working from above, and compile a kernel with that config and "make oldconfig" to start from it
- finish the install with that new kernel compiled
Reboot and see...
Offline
The arch kernel's config can be accessed similarly to gentoo's from /proc/config.gz alternately from [1] -> View Changes -> (select the commit for the release you are interested in) -> tree -> config
If a kernel has been built with CONFIG_IKCONFIG then can be used to extract the config.
You could try linux-lts as that is 4.19 based the same as the gentoo kernel that worked.
[1] https://www.archlinux.org/packages/core/x86_64/linux/
Last edited by loqs (2019-07-27 20:52:44)
Offline
I confirm it's working this way, so, for any future reader of this thread, if all the kernel boot options do not work:
- find a bootable image that works (try other distributions)
- one you found it, copy its kernel config, and use this config to build your own new kernel within your original intended distributions install, using "make oldconfig" in order to reuse the working kernel's config.
Offline
Pages: 1