I still have add ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 to even boot. Ubuntu 18.10 works great so long as I add those in GRUBs editor before boot or permanently add to grub.cfg after install. Also, hiding the AE_ALREADY_EXISTS errors doesn't mean they're gone. Fedora is experimenting with a cool feature that freezes an image in the framebuffer (similar to what windows 10 does during the loading screen and circling dots), this hides the flicker to console, then flicker to plymouth bootscreen. It goes straight from BIOS image to plymouth (very awesome). a journalctl -xe and possibly dmesg should still show those errors.
As a side note, ACER has contacted me back again. They did a little research and noticed there was indeed a community of people who are experiencing this issue and the community did seem large enough to warrant being looked into and possibly fixed for Linux Users! Customer support has been pretty awesome about all this so far. I'm very impressed. They've asked that I pull together some info to better explain the issues so they can forward them up to the engineers for review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
