Slackware64 and Ryzen

bassmadrigal · 07-12-2017, 11:04 PM

Those are the steps I would take as well. However, I would also look at converting your devices in your bootloader and fstab to use persistent names. Otherwise, the new motherboard may label them differently (suddenly your boot drive is now /dev/sdb) and now the system won't boot. If you use persistent names, then that won't be an issue. I wrote a SlackDocs article on the process.

Richard Cranium · 07-12-2017, 11:09 PM

Quote:

Originally Posted by MarcT

I'm not normally one for posting PC specs, but since there I couldn't find any Slackware on Ryzen information, here's the specs of my new Ryzen 7 workstation[...]

Pool of drool forms on the floor.

I'm looking at an upgrade within a year or so (building a new house). I'll certainly get a MB able to hold 64G of RAM if at all possible simply to run docker images as needed.

None of the above is any help to you, of course, but I should live up to my handle every now and then.

MarcT · 07-13-2017, 07:14 AM

If your Linux workload involves a lot of compiling code, be aware that there is an issue with "random" gcc segfaults on Ryzen under very heavy compilation load.

See the following links for more details:

https://community.amd.com/thread/215773
https://forums.gentoo.org/viewtopic-t-1061546.html

I ran into it on Slackware trying to compile LibreOffice from source (but note that I can compile Linux kernels and my own small projects and never see the problem).
There are a few things which can be done to mitigate/workaround the issue, most notably to disable kernel address space randomisation with "sysctl kernel.randomize_va_space=0"
Doing this allowed my LibreOffice build to complete. I've also read disabling the uOP cache helps a lot too. Not tried that yet.

It particularly affects the Gentoo community because they tend to compile everything.

My system freezes have not re-occured since updating to the latest UEFI (2.40 for ASRock x370 Taichi) containing AMD's AGESA 1.0.0.6.
I'd recommend anyone on Ryzen to upgrade the kernel to 4.11.9 or greater as there were a slew of Ryzen fixes in that version. I've not tried 4.12 as yet.

MarcT · 07-13-2017, 07:32 AM

Quote:

Originally Posted by slackerDude

Just ordered MSI Gaming Plus, Ryzen 1700 and Corsair LPX 3200 16GB (2x8) RAM.

My plan was:
-build/install latest kernel on existing machine
-swap mboard/CPU/RAM into existing machine
-try to boot
-hope for the best

Anything else I need to do? Keeping the same video card, so hopefully that won't be an issue.

Sounds like a plan. Do check the RAM you propose to use is on the qualified list for the new motherboard. Ryzen is particularly fussy about RAM.

I would build a bootable Slackware USB stick before you start, as it might be easier to boot from that initially.
First thing to do is update the UEFI (BIOS) to the latest rev, as the motherboard will probably ship with an older one. The latest UEFIs enable better RAM timing, etc.

The only Slackware specific thing concerns the bootloader. My old system was using LILO to boot, but I switched to ELILO for the new. This was easier as I was installing fresh "-current", so the setup utility could configure it. You may need to investigate "efibootmgr" if you're re-using an existing install and switching from BIOS/LILO to EFI/ELILO.
Alternatively you might be able to enable "legacy boot" in the UEFI if your system has that option.

Enjoy!

slackerDude · 07-13-2017, 01:53 PM

Thanks for all the advice. Will try the persistent naming.

I did read up on the Linux compilation issue, and I don't compile that much. It sounds like there are workarounds for most people. I don't expect it to be a big problem.

I didn't check the qualified list for the RAM, but there are reports of people getting the LPX ram to run @ at least 2933, some at 3200. I'm hoping for the best in this case.

I guess worst case, if I can't get it to work reliably, return everything, take a little hit to the wallet and get a 7700k..

Can I keep my old (MBR) partitioning with EFI? Or do I now need to transition 100% to a new partitioning scheme? Can I use my spare SSD to set up a new (U)EFI-style boot setup, and then mount my old MBR partitions? Or is this a case of having to convert 100%?

bassmadrigal · 07-13-2017, 01:59 PM

Quote:

Originally Posted by slackerDude

I guess worst case, if I can't get it to work reliably, return everything, take a little hit to the wallet and get a 7700k..

Or sell it to me at a discount

MarcT · 07-14-2017, 05:55 AM

Quote:

Originally Posted by slackerDude

Can I keep my old (MBR) partitioning with EFI? Or do I now need to transition 100% to a new partitioning scheme? Can I use my spare SSD to set up a new (U)EFI-style boot setup, and then mount my old MBR partitions? Or is this a case of having to convert 100%?

You can keep the old partitions and probably still boot from them, but you may need a new boot loader (ie LILO replacement). If the UEFI supports legacy booting, LILO will probably work.

You could also use your spare SSD as a boot device, but it may not be needed.

In terms of partitions, the only case where you absolutely require new GPT partitions is for devices larger than 2.1TB. Some older BIOSes are not able to boot from GPT disks, but that's not relevant here.

I wouldn't worry about this now, it will all become clear when you do have to it. If you run into problems, I'm sure we'll be able to help.

Fat_Elvis · 07-14-2017, 10:22 AM

The PSU wattage makes me cringe. I have had the best experience with 850+ watts with a powerful desktop.

I think the new stuff from AMD is very exciting. I'm lukewarm about Intel, but Nvidia is seriously ticking me off these days. Whenever I upgrade my GPU, it's definitely going to be an AMD card.

mrapathy · 07-14-2017, 10:52 PM

I wish I could afford Ryzen but I am happily running a 8125 FX cpu which stays ice cold most of the time with
stock cooler. overclocked to 4000mhz though use on demand governor for cpu freq utils.

Quote:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 1
Model name: AMD FX(tm)-8120 Eight-Core Processor
Stepping: 2
CPU MHz: 1400.000
CPU max MHz: 4000.0000
CPU min MHz: 1400.0000
BogoMIPS: 8053.03
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
L3 cache: 8192K
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall

my last video card was ati/amd I upgraded to nvidia 1050 and didnt look back. nvidia support is better.
AMD has ditched legacy support and has a short product life. used nvidia for years but decided to try AMD/ATI.

I made my current system over 2 years ago and its working great. not much has happened over last 2 years.
using EVGA 650 modular power supply. did have a corsair 700watt psu.
Gigabyte mobo with dual bios using legacy mode no uefi as long as I can.

larrystorch · 07-15-2017, 07:24 AM

Quote:

Originally Posted by MarcT

You can keep the old partitions and probably still boot from them, but you may need a new boot loader (ie LILO replacement). If the UEFI supports legacy booting, LILO will probably work.

You could also use your spare SSD as a boot device, but it may not be needed.

In terms of partitions, the only case where you absolutely require new GPT partitions is for devices larger than 2.1TB. Some older BIOSes are not able to boot from GPT disks, but that's not relevant here.

I wouldn't worry about this now, it will all become clear when you do have to it. If you run into problems, I'm sure we'll be able to help.

I can't believe I missed this thread. I was one of those impulsive idiots that jumped on the ryzen bandwagon a few days after launch upgrading from an FX8350. Here's what I did:

Assemble new ryzen system: 1700, 32GB, MSI Pro Carbon, M.2 nvme drive; Boot to bios to make sure everything at least works; Memtest+
Transplant sda (boot:lilo & system), sdb(home), sdc (data) to new case
Boot into slackware 14.2 install USB
Partition new nvme drive.
Copy sda partitions to nvme
Try to install boot loaders on nvme drive.... elilo.....fail....lilo...fail.....get really frustrated...
Throw in towel....modify lilo & fstab to boot from sda using nvme .
Boot into slackware and it works....except for kernel issues...
Compile 4.10 kernel
Profit

Except for nvme efi boot support and needing a 4.10+ kernel, I really didn't have any major issues. I'll just wait for nvme boot support in the (hopefully) next Slackware release. Not really comfortable trying out the patches that were posted. The only hassle now is during kernel upgrades. I have to mount & chroot to my old sda / partition to edit and update lilo.

Fat_Elvis · 07-15-2017, 09:37 AM

Quote:

Originally Posted by larrystorch

I can't believe I missed this thread. I was one of those impulsive idiots that jumped on the ryzen bandwagon a few days after launch upgrading from an FX8350. Here's what I did:

Assemble new ryzen system: 1700, 32GB, MSI Pro Carbon, M.2 nvme drive; Boot to bios to make sure everything at least works; Memtest+
Transplant sda (boot:lilo & system), sdb(home), sdc (data) to new case
Boot into slackware 14.2 install USB
Partition new nvme drive.
Copy sda partitions to nvme
Try to install boot loaders on nvme drive.... elilo.....fail....lilo...fail.....get really frustrated...
Throw in towel....modify lilo & fstab to boot from sda using nvme .
Boot into slackware and it works....except for kernel issues...
Compile 4.10 kernel
Profit

Except for nvme efi boot support and needing a 4.10+ kernel, I really didn't have any major issues. I'll just wait for nvme boot support in the (hopefully) next Slackware release. Not really comfortable trying out the patches that were posted. The only hassle now is during kernel upgrades. I have to mount & chroot to my old sda / partition to edit and update lilo.

Hey, if you compile your own Kernel, NVMe support is super easy. Could try with Patrick Volkerding's sources and config files as well. I started with his config file from the TESTING branch. (Might be wrong about the file location, poke around your FTP mirror of choice.)

Stock kernel from kernel.org:

Code:

< CONFIG_NVME_CORE=y
< CONFIG_BLK_DEV_NVME=y
---
< # CONFIG_NVME_RDMA is not set
< # CONFIG_NVME_TARGET is not set

Works flawlessly since 4.8 or so. On 4.12 right now. No problems with a PCIe M.2 NGFF drive.

larrystorch · 07-15-2017, 09:48 AM

I should have been a bit more clear in post, but it was early morning when I did it. I have no problem using the nvme drive once I'm booted into slackware, my problem is getting a bootloader installed on it. Lilo can't use it all, elilo needs patches at this point and I couldn't get grub installed either, though that just might be a user error on my part. I just use my ssd that has lilo installed on it like an overpriced usb boot disk. Once installing a uefi bootloader on nvme drives gets better support, then I'll move to that.

slackerDude · 07-15-2017, 09:57 AM

Quote:

Originally Posted by larrystorch

I can't believe I missed this thread. I was one of those impulsive idiots that jumped on the ryzen bandwagon a few days after launch upgrading from an FX8350. Here's what I did:

Assemble new ryzen system: 1700, 32GB, MSI Pro Carbon, M.2 nvme drive; Boot to bios to make sure everything at least works; Memtest+
Transplant sda (boot:lilo & system), sdb(home), sdc (data) to new case
Boot into slackware 14.2 install USB
...

Thanks! I just built a slackware64-current DVD.. Now to convert to USB and get ready for the install (just in case). Hmm.. Looks like the kernel is 4.9.37.. Were you able to compile 4.10+ using Ryzen? Or did you have to pre-compile on another machine?

I'll see if I can get the original SSD/lilo combination to boot. Otherwise, install on a spare SSD and maybe re-arrange some space on my current "user files" SSD. Didn't go all the way for an M.2 drive yet - I figure just going to a 6GBit SSD will be a bit of a speed boost for me (currently running on 3GBit sata ports).

larrystorch · 07-15-2017, 10:08 AM

Now that I think more about it, I think I had already moved on to 4.10 before ryzen came out due to other needs.

I just checked and idlemoor is offering a 4.12 series of kernel packages (big thanks dude) that might suit you better: https://dusk.idlemoor.tk/linux-4.12/x86_64/

Fat_Elvis · 07-15-2017, 10:16 AM

Quote:

Originally Posted by larrystorch

I should have been a bit more clear in post, but it was early morning when I did it. I have no problem using the nvme drive once I'm booted into slackware, my problem is getting a bootloader installed on it. Lilo can't use it all, elilo needs patches at this point and I couldn't get grub installed either, though that just might be a user error on my part. I just use my ssd that has lilo installed on it like an overpriced usb boot disk. Once installing a uefi bootloader on nvme drives gets better support, then I'll move to that.

I have had that problem. The issue is the bootloader selection in Slack 14.2.

GRUB 2.0 does not work with an NVME drive, IME. (Eh, it might after modifying the grub-install script.)

GRUB 2.02 b3 works flawlessly. I think it's in Slack-current already. Also, I can help with the specifics of installing GRUB, if you are unfamiliar with it, or with efibootmgr if you are booting in UEFI mode.

I would just post my install scripts, but they have a ton of peripheral stuff that no-one would be interested in.

The oddball naming convention "/dev/nvme0n1p1" can cause a bit of a headache.