I installed the 2020-02-23 daily image to the Ryzen 3/Vega 3 laptop. It looks great, like it’s the final release (not an unstable test image).
1. I encountered one strange thing in the Live desktop (when installing). I told it to erase the existing disk (which was formatted MBR, ext4). When I got to the point of committing changes made to the disk, it had an error saying it couldn’t partition the drive.
I rebooted, used the KDE Partition Manager to delete the existing partition. Then the install worked fine.
I tried that again. Booted the LiveUSB, started the install, chose erase entire disk. When I confirmed changes to the disk, I got the same error message:
The Installer failed to create a partition table on WDC WD50000LPLX-60ZNTT1.
Create a new partition table (type: gpt) on ‘/dev/sda’
Job: Create new partition table on device ‘/dev/sda’
Command: sfdisk /dev/sda
(Note: I don’t know why the quote markup is causing the above to be large/bolded.).
When I started to do that 2nd try, I thought that, to recreate the error I would have to delete the partition & create an MBR partition table. I thought the original state of the disk is why I got the first error. But, the disk is now GPT (from that last install). So, it seems like it can’t work with allocated partitions. I have to delete them in KDE Part. Mgr. Then the install works. It doesn’t matter if the existing partition table is MBR or GPT.
Should I open a bug report on that? (Seems like someone would have already encountered this. I read another recent post about Calamares having some issues.).
2. Inxi -Fxrz (installed with apt-get, just because I have that command memorized) shows the kernel is 5.4.0-14. The Mesa driver is 20.0.0. That’s interesting to me because MX Linux 19.1_AHS uses Mesa 19.2.1 & kernel 5.4.0-3 (and doesn’t work with Ryzen 3/3 nor 5/8).
Kubuntu 19.10 uses Mesa 19.2.8 & kernel 5.3.0-40. That works with both Ryzens.
I don’t understand how all that goes together (or, why some combos don’t).