Cfxtrjtrk

This is the Ryzen 7 2700u version. Ubuntu 18.04 nor Ubuntu Daily will boot. What can I do? Here's the screen when I boot from Ubuntu 18.04 USB.

[0.000000] ACPI Error: [_SB_.PCI0.LPC0.EC0_] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)

[0.000000] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)

[0.000000] ACPI Exception: AE_NOT_FOUND, (SSDT:AmdTable) while loading table (20170831/tbxfload-228)

[0.000000] ACPI Error: 1table load failures, 7 successful (20170831/tbxfload-246)

[0.000000] [Firmware Bug] AMD-Vi: IOAPIC[4] not in IVRS table

[0.000000] [Firmware Bug] AMD-Vi: IOAPIC[5] not in IVRS table

[0.000000] [Firmware Bug] AMD-VI: No southbridge IOAPIC found

[0.000000] AMD-Vi: Disabling interrupt remapping

[0.716275] i2c_designware AMDI0010:01: Unknown Synopsys component type: 0xffffffff

[6.718168] AMD-Vi: Unable to write to IOMMU perf counter.

I have the Ryzen 2700U Inspiron 7375 as well. I managed to get this working pretty well, however I had to get it installed using Antergos. I wasn't able to get it reliably booting under Ubuntu 18.04 unless I left acpi=off set in the kernel parameters and it wouldn't boot at all to the 4.17 kernel. I started trying different distributions and Antergos worked perfectly the first time (though I may have been lucky since afterwards it seemed 50/50).

After logs of digging and experimenting, I finally found these kernel parameters to be the key (using with linux kernel 4.17.2-1-zen from the Antergos linux-zen package):

amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

Under Antergos I added these to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub then ran

sudo grub-mkconfig -o /boot/grub/grub.cfg

Now things are working pretty well! Maybe these options will help get things working under Ubuntu as well.

update: I just downloaded the 18.04 installer and tried to boot from it again (which comes with the 4.15 kernel). When I added the parameters above (by hitting 'e' on the bootloader) it was able to boot and work correctly. I didn't want to try an install over again so I didn't proceed further, but it appears to work correctly off of the live USB at least.

Looking through Dell's supported machines, there is an exclusivity towards intel machines. I have been attempting to get the same model machine with the Ryzen5 2500u to install any Debian based OS with no success. It may be that the new AMD architecture is still being incorporated into the Kernel. Additional research is required.

I'm hoping to get more answers as the Ryzen mobile series expands in popularity across vendors. It's actually the reason I bought a new laptop; I wanted to ride the new wave as AMD rushes to the field against the old king Intel.

Update

The ubuntu shipping kernel (4.15) does not have good support for AMD Raven Ridge CPUs. Supposedly 4.16 has better support but is not actively being shipped with Ubuntu.

I've been working on my own Inspiron 7375, and I've run through several distros that all failed in one way or another (certainly, some may have been my fault, but I didn't catch them if it was). Then I got Ubuntu 16.04 to work, with the 4.15 kernel, so I tried 18.04.

Wouldn't work. I fiddled around and tried adding acpi=off to the kernel arguments. Ta da! Worked. Brought up everything, seemed to work well. After I installed everything, however, I found that the system didn't recognize the monitor(while still writing to it reasonably well), and that it only recognized one of the eight CPU cores. Back to more fiddling.

Where I'm at now is that I've changed the default arguments from "quiet splash" to "pci=noacpi splash" . This seems to work, when I run it, most of the time it comes up fine.

Hope that helps.

Now I'm finding that it boots right when I boot it to Windows, reboot from there, and go into Ubuntu. So the Windows shutdown sequence seems to be resetting something that allows the linux display setup to work. I don't know what.

I have run into the same issue I put noapic in the kernel boot options. I don't think it's an APCI issue directly. I think it's something with interrupts and sleeping cores and the kernel not being able to wake up the cores. If you take out quiet and splash you can see more detail.