[Solved] [error] 0.020000 AMD-Vi Command Buffer Timeout

[jk9]

USB Disk with 2 partitions
First: Grub4Dos + Slitaz + Porteus/Kiosk/initrd.xz + vmlinuz
Second: Kiosk 4.6 (dd command)

Everything works flawlessly on A BIOS system (Samsung laptop)
However, on my new UEFI system (Asrock Fatal1ty AB350 ITX/ac / Ryzen 5 2400G / Noctua NH-L9a M4 / G.Skill Flare X DIMM Kit 16GB, DDR4-3200 / Samsung M.2 960 Evo):
Booting Slitaz works.
Booting Kiosk 4.6 throws the above mentioned error. The thing is, I can see the booting process starting normally for a couple of seconds then I get the error message.

Any advice?

[fanthom]

Hi jk9,

Add 'amd_iommu=off' kernel parameter to your grub4dos config for kiosk.
Let us know if that helped.

Thanks

[jk9]

Thanks very much for the prompt reply.

Code: Select all

title Porteus Kiosk 4.6
kernel /Porteus/Kiosk/vmlinuz amd_iommu=off
initrd /Porteus/Kiosk/initrd.xz  

However, the boot process seems to be "more complete" as far as I can tell but no GUI
Merely a black screen, nothing else ....

[fanthom]

Just realized this is Ryzen APU.

You'll have to wait for next kiosk release with new LTS kernel as our current 4.14.x does not support this GPU yet.
Unless you would be interested in a paid customized build?
http://porteus-kiosk.org/builds.html

If this is for a private use then better wait.

If VESA driver is good enough for you then your could replace 'amd_iommu=off' with:

Code: Select all

debug modprobe.blacklist=amdgpu,radeon

Thanks

[jk9]

Replacing "amd_iommu=off'" with "debug modprobe.blacklist=amdgpu,radeon" throws the same error (i.e. 0.020000 AMD-Vi Command Buffer Timeout)
Using both lines at the same time makes the booting process go all through till it states "Starting Kiosk 4.6" then it goes black screen.

This is for private use, so I'll have to wait for the next build then.
Thank you very much for your help and for all the efforts involved in making this project

[Ed_P]

I wasn't aware that grub4dos worked with EFI systems!! When did that happen?

When the screen goes black what happens if you press Ctrl+Alt+F1?

[jk9]

When the screen goes black what happens if you press Ctrl+Alt+F1?

Well, nothing happens actually ...

[Ed_P]

It was a wild guess. Sorry.

[jk9]

It was a wild guess. Sorry.

No worries mate

[jk9]

Unfortunately, still having issues as the new Kiosk 4.7 won't boot .....

Code: Select all

[error] 0.016000 AMD-Vi Command Buffer Timeout

[fanthom]

Thats because we are still on 4.14.x LTS kernel.

Next LTS should be 4.19.x (hopefully) so we could do the switch in October/November.

[jk9]

Thats because we are still on 4.14.x LTS kernel.
Next LTS should be 4.19.x (hopefully) so we could do the switch in October/November.

Thanks for the explanation and for all the efforts put in this project

[fanthom]

Hi jk9,

It took longer than expected but new kiosk version is out (with latest LTS kernel) so please test it when you get a chance:
https://porteus-kiosk.org/news.html#190121

Hopefully everything will work ootb on your hardware.

Thanks

[jk9]

It took longer than expected but new kiosk version is out (with latest LTS kernel) so please test it when you get a chance:

Hi fanthom,
Thank you very much for all the efforts involved, honestly.

I hate to say it but it doesn't resolve the problem. There's a difference though ..
Instead of

Code: Select all

0.020000 AMD-Vi Command Buffer Timeout

I'm having this now

Code: Select all

0.010000 AMD-Vi Command Buffer Timeout

Best regards.

[fanthom]

Please boot latest Ubuntu live (18.10), download and run this script:
https://porteus-kiosk.org/public/files/debug.sh

Please use following command:

Code: Select all

sudo bash debug.sh

then send generated /tmp/debug.txt report to [email protected] and i'll have a look on this.