Got new notebook ACER Nitro AN515-42 with AMD Ryzen 5 2400U processor and Radeon Vega 8 Mobile Gfx.
Original OS on SSD is Linpus Lite.
uname -a# Linux 4.2.01p_mmc #5 SMP i686 athlon i386 GNU/Linux
Linpus is running in text mode only.
GRUB parameters are : kernel /boot/vmlinuz ro root= nolapic_timer loglevel=0 acpi_osi=Linux pcie_aspm=off acpi=copy_dsdt pci=nocrs irqpoll quiet
I've decided to install UBUNTU MATE 18.04 on laptop.
Image ubuntu-mate-18.04-desktop-amd64.iso had been downloaded and installed on flash drive with rufus.
Laptop doesn't have a CD/DVD drive.
Secure boot was switched off in BIOS and boot from flash drive was selected.
I've selected UBUNTU try option in GRUB to test on my laptop.
Boot of kernel fails with many similar messages on screen about "soft lockup - CPU#4 stuck for 23s".
UBUNTU Mate install option had produced same error.
I've installed Windows 10 trial to test the laptop - it is working good.
I've downloaded BIOS update utility, which is for Windows 10 only, from ACER and I'd updated BIOS from v1.05 to v.1.08. No changes in Windows.
The UBUNTU MATE setup still is making same errors.
I've tested ubuntu-mate-16.04-desktop-amd64.iso and ubuntu-mate-18.04.1-desktop-amd64.iso with same errors.
I've search WEB and found working solution for me with GRUB startup option "rcu_nocbs=0-7" cause my AMD got 4 cores/ 8 threads.
Second error during installation is related to ACER BIOS ACPI. UBUNTU startup fails again.
GRUB boot option acpi=off didn't work.
GRUB boot options from original Linpus above didn't work.
Found in WEB working solution for me with GRUB startup option ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
I've managed to install UBUNTU MATE 18.04.1 on my laptop.
I've managed to install proprietary AMD driver 18.20 for Vega video chipset.
GRUB boot options are "ro rcu_nocbs=0-7 ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=1".
UBUNTU MAte is running but still is getting some errors and X freeze some time - I will make extra bug report.
I'm reporting from my new laptop.
Copy of LOG files are attached.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: romkuz 1576 F.... pulseaudio
/dev/snd/controlC0: romkuz 1576 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=28e39be2-4c03-4cef-b100-37b42b56620b
InstallationDate: Installed on 2018-08-07 (1 days ago)
InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Acer Nitro AN515-42
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=d40acc90-785a-4efc-8b97-8060f5cad8c0 ro rcu_nocbs=0-7 ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-30-generic N/A
linux-backports-modules-4.15.0-30-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip fax lpadmin netdev plugdev sambashare scanner sudo video
_MarkForUpload: True
dmi.bios.date: 05/23/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Freed_RRS
dmi.board.vendor: RR
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd05/23/2018:svnAcer:pnNitroAN515-42:pvrV1.08:rvnRR:rnFreed_RRS:rvrV1.08:cvnAcer:ct10:cvrV1.08:
dmi.product.family: Acer Nitro 5
dmi.product.name: Nitro AN515-42
dmi.product.version: V1.08
dmi.sys.vendor: Acer
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1786241
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.