Page MenuHomeSolus

Solus USB drive won't boot: amd-vi unable to write to iommu perf counter
Open, Needs More InfoPublic

Description

Hello, I've installed Solus on my desktop PC last week and it works perfectly.
Today I've tried to install it on my laptop, but the USB drive won't boot.
It stops before reaching the installer and returns this error:
"amd-vi unable to write to iommu perf counter"
It won't let me proceed or type anything, the only thing I can do is forcedly shutdown the PC.
My laptop is an Acer Aspire 3 A315-42-R3E0 with an AMD Ryzen3 3200U CPU and an AMD Radeon Vega 3 GPU.
According to some posts I've found online, it could mean that the kernel doesn't support the CPU very well.
However, I've managed to install Ubuntu on the same PC just fine, even though it has an older kernel.
Some people also suggested to disable IOMMU in the BIOS, but my PC has a very basic BIOS and no option to do that.
So, how can I install Solus on that PC?

Event Timeline

DataDrake triaged this task as Needs More Info priority.Mar 1 2020, 2:11 PM
DataDrake edited projects, added Hardware; removed Lacks Project.
DataDrake added a subscriber: DataDrake.

That's probably a red-herring. Not everything printed to the kernel log that looks like an error, is actually a fatal one.

Can you try booting without "quiet" and "splash" set so that you can see what other errors are printed?

That's probably a red-herring. Not everything printed to the kernel log that looks like an error, is actually a fatal one.

Can you try booting without "quiet" and "splash" set so that you can see what other errors are printed?

Solus isn't installed yet, so how do I boot without quiet and splash?
Do I need to modify the GRUB file inside the Solus ISO?
Meanwhile, I've updated the BIOS (I had to install Windows 10 just to do that, because Acer only provides BIOS updates through Windows) and then tried again to install Solus.
This time, the IOMMU error is still there, but is followed by this:
"a start job is running for rebuild dynamic linker cache"
The start job keeps running forever, as it has no time limit.
I've Googled this error and found out that a lot of people are having this issue with the same laptop, so it's probably Acer's fault.
BTW, Secure Boot is disabled, otherwise it wouldn't even let me get to this point.

@moonglow , does this issue still happen with an up to date Solus ISO (4.4) and that laptop? There have been many updates and bug fixes since this issue was last updated.