LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-13-2017, 11:58 AM   #1
MarcT
Member
 
Registered: Jan 2009
Location: UK
Distribution: Slackware 14.2
Posts: 106

Rep: Reputation: 44
Slackware64 and Ryzen


Since there's a Slackware64 and Kaby Lake thread, I thought we could do with a Slackware64 and Ryzen thread.

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:

Code:
CPU: Ryzen 7 1800x (8 core, 16 threads)
CPU Cooling: Thermaltake Contac Silent 12 AM4 PWM
Motherboard: ASRock X370 Taichi ATX
RAM:	Crucial CT2K16G4WFD824A 32GB (2 x 16GB with ECC, 2400MHz)
SSD:	1TB Intel 600p Series PCIe Gen3 x4 M.2 (SSDPEKKW010T7X1)
HDD:	WD 4TB WD4000FYYZ RE 24x7 Enterprise 3.5" SATA 6Gb/s HDD 7200rpm x QTY 2
PSU:	Seasonic SS-650RM 650W Hybrid Modular
Graphics:	4G Sapphire Nitro+ RX480 AMD Polaris Graphics Card 1306MHz
Optical Drive:	LG Internal Blu Ray Writer WH14NS40 + M-Disc Support
Case:	Fractal Design R5
PS/2 Y-Cable for keyboard & mouse (eBay) for use with KVM switch.
Slackware64-current. Updated to Kernel 4.10.15.
Why these parts?
This is a workstation build, to eventually become my daily driver. I use lots of temporary virtual machines in my day job, and this PC should allow me to have many of these running locally, rather than on our remote ESXi farm.

I wanted ECC RAM support. The ASRock x370 Taichi was (at the time of ordering) the only AM4 board to support ECC. AMD confirmed the Ryzen CPUs do support ECC, but it's up to the motherboard vendors to implement it. NB: I had to update the board's UEFI before Linux's EDAC ECC implementation would detect the ECC RAM (was running in non-ECC mode initially).

Slackware Install Experience:
I've installed Slackware64-current on this machine twice now, via a bootable USB stick. The first time was on 30th April, this had a 4.4.38 kernel (I think), which actually booted and mostly ran OK. However the installer did not properly recognise the NVMe boot drive, so a lot of manual steps were required to get elilo to boot the machine. I did eventually get X/KDE running.

The second attempt was on May 9th/10th after Didier Spaier's installer patches for NVMe had been merged in. The install just worked this time.

TIP: The x370 Taichi can boot a USB stick in "legacy" or UEFI mode. Legacy seems to be the default. In this mode the kernel doesn't detect UEFI/EFI firmware and the Slackware installer EFI boot setup steps doesn't work. To workaround, you must hit F11 during boot and and pick the EFI option of the USB stick.

Impression so far:
Daily use - I have booted one of my SuSE11 temporary VMs under Oracle VirtualBox. It works very well and it's fast!
I compiled the 4.10.15 kernel modules (time make modules -j15) in 7 mins. On my old Phenom workstation, this takes > 35 minutes.
The only minor niggle: I can't get audio out over HDMI working. This is probably an issue with the RX480 card. However audio out via the 3.5mm jack is fine.

"lscpu" & "uname -a":
Code:
root@deepthought:~# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                16
On-line CPU(s) list:   0-15
Thread(s) per core:    2
Core(s) per socket:    8
Socket(s):             1
Vendor ID:             AuthenticAMD
CPU family:            23
Model:                 1
Model name:            AMD Ryzen 7 1800X Eight-Core Processor
Stepping:              1
CPU MHz:               2200.000
CPU max MHz:           3600.0000
CPU min MHz:           2200.0000
BogoMIPS:              7200.55
Virtualization:        AMD-V
L1d cache:             32K
L1i cache:             64K
L2 cache:              512K
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 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic overflow_recov succor smca
root@deepthought:~# uname -a
Linux deepthought 4.10.15 #1 SMP Tue May 9 02:08:57 BST 2017 x86_64 AMD Ryzen 7 1800X Eight-Core Processor AuthenticAMD GNU/Linux
dmesg output:
Code:
Removed - post too long.
There's a lot of these messages in the middle of the above, which is why I filtered them out:
Code:
root@deepthought:~# dmesg | egrep 'AMD-Vi: Event logged|IO_PAGE_FAULT' | head
[    9.374500] AMD-Vi: Event logged [
[    9.374504] IO_PAGE_FAULT device=0e:00.0 domain=0x0003 address=0x000000f4001f4600 flags=0x0010]
[    9.374524] AMD-Vi: Event logged [
[    9.374526] IO_PAGE_FAULT device=0e:00.0 domain=0x0003 address=0x000000f4001f63c0 flags=0x0010]
[    9.374549] AMD-Vi: Event logged [
[    9.374551] IO_PAGE_FAULT device=0e:00.0 domain=0x0003 address=0x000000f4001f66c0 flags=0x0010]
[    9.374567] AMD-Vi: Event logged [
[    9.374569] IO_PAGE_FAULT device=0e:00.0 domain=0x0003 address=0x000000f4001f8600 flags=0x0010]
[    9.374585] AMD-Vi: Event logged [
[    9.374586] IO_PAGE_FAULT device=0e:00.0 domain=0x0003 address=0x000000f4001f48c0 flags=0x0010]
Also, I've had one hard lockup in X windows / KDE. Unsure of the cause.

So, is anyone else running Slackware on Ryzen yet?

Last edited by MarcT; 05-13-2017 at 11:59 AM. Reason: Formatting
 
Old 05-13-2017, 05:48 PM   #2
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 397

Rep: Reputation: 127Reputation: 127
HDMI audio doesn't work by default with the open source AMDGPU drivers you need DC (DAL) support for that.
https://cgit.freedesktop.org/~hwentl...staging-dc-4.9
Some Ryzen motherboards comes with an Realtek ALC299/ALC1220 audio codec and it's not supported before kernel 4.11 but your audio seems to work already.

Last edited by Nille_kungen; 05-13-2017 at 05:50 PM.
 
2 members found this post helpful.
Old 05-13-2017, 06:02 PM   #3
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,302

Rep: Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278
Unfortunately, I can't comment on running Ryzen in Slackware yet because I haven't bought the hardware yet. But I'll be watching this thread closely because I'm hoping to get it within a few months. I really only need the processor and motherboard, because I have 32GB (16GBx2) DDR4 Corsair non-ECC RAM and a Corsair HXi 1000w PSU. I am also looking at an ASRock Taichi motherboard due to ASRock having the only boards with 10 SATA ports (and I don't need the extra features of the Fatal1ty board). I want to get a new case too, but that could wait.

As for the error messages on boot, it seems it is due to poor support of IOMMU (gathered from here and here). Most of the reports are based on device 24:00.0, but it could just be the specific motherboard. It'd be interesting to see what lspci lists device 0e:00.0 is.

However, I do have a question for you based on your input on Didier's NVMe thread. I have a Samsung EVO 960 1TB M.2 stick that is in my current computer unformatted. My plan is to install Slackware 14.2 onto it along with all my required programs before rebooting out of my 14.1 install (to make the upgrade nice and quick). However, I saw that you recommended adding nvme-cli to the initrd in the installer to allow formatting. Can you not format the device with something like gdisk? What else does nvme-cli offer? I had a look at the manpage, but nothing really stood out (in fact, I completely missed that it even allows you to format using it until I just re-looked at it). I tried finding more information online, but even Arch's wiki doesn't have much information on it. I'm just looking for the best way to manage my device, and information on NVMe is lacking with distros (or my google-fu is weak and I just can't find it). If you feel this will derail your thread, you don't have to worry about answering it.
 
2 members found this post helpful.
Old 05-13-2017, 08:14 PM   #4
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.2 (4.13.9) UEFI enabled
Posts: 432

Rep: Reputation: 113Reputation: 113
Quote:
Originally Posted by bassmadrigal View Post
... However, I saw that you recommended adding nvme-cli to the initrd in the installer to allow formatting. Can you not format the device with something like gdisk? ...
I can confirm that nvme devices can be formatted using gdisk. I used it under Slackware64-14.2 to format my nvme device prior to Didier's patches. Mine is connected to a PCI slot. I don't have an M2 connector on my motherboard.
John
PS if my memory serves me I believe fdisk also say the device.
confirmed
Code:
fdisk -l /dev/nvme0n1p2
Disk /dev/nvme0n1p2: 128 GiB, 137438953472 bytes, 268435456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

gdisk -l /dev/nvme0n1p3
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.
Disk /dev/nvme0n1p3: 536870912 sectors, 256.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): D76972F2-1188-42AE-BFF3-78591E461B09
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 536870878
Partitions will be aligned on 2048-sector boundaries
Total free space is 536870845 sectors (256.0 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name

Last edited by AlleyTrotter; 05-13-2017 at 08:34 PM.
 
2 members found this post helpful.
Old 05-13-2017, 10:13 PM   #5
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,302

Rep: Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278
Quote:
Originally Posted by AlleyTrotter View Post
PS if my memory serves me I believe fdisk also say the device.
Thanks for the confirmation. And yeah, I figured fdisk should see it, but I knew I was going to go with a GPT partition, so that's why I mentioned gdisk. But thanks for the confirmation.

I'm just curious what some other beneficial features are of nvme-cli. I suppose I could try and dig through the man pages, but I was hoping someone could just provide a few ideas
 
Old 05-15-2017, 03:05 AM   #6
MarcT
Member
 
Registered: Jan 2009
Location: UK
Distribution: Slackware 14.2
Posts: 106

Original Poster
Rep: Reputation: 44
Quote:
Originally Posted by Nille_kungen View Post
HDMI audio doesn't work by default with the open source AMDGPU drivers you need DC (DAL) support for that.
https://cgit.freedesktop.org/~hwentl...staging-dc-4.9
Some Ryzen motherboards comes with an Realtek ALC299/ALC1220 audio codec and it's not supported before kernel 4.11 but your audio seems to work already.
Ah - many thanks for that! I'm going to try the closed source RX480 drivers today - mainly to see if they eliminate a lockup when running firefox:

I discovered the cause of my hard lockups. If I start firefox and leave it idle with no webpage displayed, within a few minutes the machine locks up. Any SSH sessions into it freeze entirely, and there's no clues in the logs as to what happened. I tried a Magic-SysReq sequence, and it attempted to reboot but the UEFI never started. This makes me think it's a GPU/driver related issue.


Quote:
Originally Posted by bassmadrigal View Post
As for the error messages on boot, it seems it is due to poor support of IOMMU (gathered from here and here). Most of the reports are based on device 24:00.0, but it could just be the specific motherboard. It'd be interesting to see what lspci lists device 0e:00.0 is.
Thanks - I'll be looking into that as well, in case it's related to the lockups. lspci output as below:
Code:
root@deepthought:~# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1450
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 1451
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1460
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1461
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1462
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1463
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1464
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1465
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1466
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1467
01:00.0 Non-Volatile memory controller: Intel Corporation Device f1a5 (rev 03)
03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02)
03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02)
03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02)
04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
04:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
04:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
04:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
07:00.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:01.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:03.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:05.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:07.0 PCI bridge: ASMedia Technology Inc. Device 1184
09:00.0 Network controller: Intel Corporation Device 24fb (rev 10)
0b:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev c7)
0e:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf0
11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a
11:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1456
11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 145c
12:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455
12:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457

Quote:
Originally Posted by bassmadrigal View Post
However, I do have a question for you based on your input on Didier's NVMe thread. I have a Samsung EVO 960 1TB M.2 stick that is in my current computer unformatted. My plan is to install Slackware 14.2 onto it along with all my required programs before rebooting out of my 14.1 install (to make the upgrade nice and quick). However, I saw that you recommended adding nvme-cli to the initrd in the installer to allow formatting. Can you not format the device with something like gdisk? What else does nvme-cli offer? I had a look at the manpage, but nothing really stood out (in fact, I completely missed that it even allows you to format using it until I just re-looked at it). I tried finding more information online, but even Arch's wiki doesn't have much information on it. I'm just looking for the best way to manage my device, and information on NVMe is lacking with distros (or my google-fu is weak and I just can't find it). If you feel this will derail your thread, you don't have to worry about answering it.
Happy to discuss NVMe here; all the AM4 boards I've seen have at least one M.2 socket for an NVMe.

Quote:
Originally Posted by AlleyTrotter View Post
I can confirm that nvme devices can be formatted using gdisk. I used it under Slackware64-14.2 to format my nvme device prior to Didier's patches. Mine is connected to a PCI slot. I don't have an M2 connector on my motherboard.
Quote:
Originally Posted by bassmadrigal View Post
I'm just curious what some other beneficial features are of nvme-cli. I suppose I could try and dig through the man pages, but I was hoping someone could just provide a few ideas
Yep - gdisk (or fdisk, etc) is used to partition an nvme "namespace". A namespace is equivalent of a virtual disk or LUN. When you get a new NVMe out of the box, it will be pre-formatted with one namespace which occupies the entire device.

The nvme "format" (from nvme-cli) is used to setup/erase an entire namespace. Think of it as the equivalent of "ATA Secure Erase". It's a way of telling the flash controller that you want to securely destroy (discard) the entire contents of a namespace (without needing to manually overwrite it, which is bad for flash storage). So, it's useful for wiping any data already present so you can start again with a clean sheet.

Here's how I setup my NVMe:
Code:
root@deepthought:~# ls -l /dev/nvme*
crw------- 1 root root 247, 0 May 15 08:20 /dev/nvme0
brw-rw---- 1 root disk 259, 0 May 15 08:21 /dev/nvme0n1
brw-rw---- 1 root disk 259, 1 May 15 08:21 /dev/nvme0n1p1
brw-rw---- 1 root disk 259, 2 May 15 08:21 /dev/nvme0n1p2
brw-rw---- 1 root disk 259, 3 May 15 08:21 /dev/nvme0n1p3
root@deepthought:~# 
root@deepthought:~# gdisk -l /dev/nvme0n1
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/nvme0n1: 2000409264 sectors, 953.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): F1664F2A-6AD3-4772-B76F-C77279BE6128
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2000409230
Partitions will be aligned on 2048-sector boundaries
Total free space is 3406 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          206847   100.0 MiB   EF00  EFI System
   2          206848      1966854799   937.8 GiB   FD00  Linux RAID
   3      1966856192      2000409230   16.0 GiB    8200  Linux swap
...though I'm thinking of changing it to have two RAID partitions. If/when I do this, I'll format namespace /dev/nvme0n1 to wipe it and start again.

So, nvme0 is the first nvme in the system. n1 is namespace one, and p1-3 are the partitions.


Ok, enough for now. I'll update this thread later with my findings.
 
1 members found this post helpful.
Old 05-15-2017, 05:43 AM   #7
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,703

Rep: Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620Reputation: 2620
Slightly off-topic: As far as few testing here can tell, recent versions of fdisk can handle gpt just fine, not only dos partition tables.

Last edited by Didier Spaier; 05-15-2017 at 07:10 AM. Reason: remved useless last sentence.
 
Old 05-15-2017, 07:01 AM   #8
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,302

Rep: Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278
Quote:
Originally Posted by MarcT View Post
Ah - many thanks for that! I'm going to try the closed source RX480 drivers today - mainly to see if they eliminate a lockup when running firefox:
If you're not aware, I have a *possibly* functional 17.10 amdgpu-pro driver available on my github. I say "possibly" because I don't know if anyone has tested it, and AMD still hasn't added support for either of my two early GCN-era cards. If that doesn't work, the 16.60 driver should work (just go up a directory, as I've kept all the different versions in separate folders), as that had a lot of testing done on this thread.

Quote:
Originally Posted by MarcT View Post
I discovered the cause of my hard lockups. If I start firefox and leave it idle with no webpage displayed, within a few minutes the machine locks up. Any SSH sessions into it freeze entirely, and there's no clues in the logs as to what happened. I tried a Magic-SysReq sequence, and it attempted to reboot but the UEFI never started. This makes me think it's a GPU/driver related issue.

Thanks - I'll be looking into that as well, in case it's related to the lockups. lspci output as below:
Code:
root@deepthought:~# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1450
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 1451
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1460
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1461
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1462
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1463
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1464
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1465
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1466
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1467
01:00.0 Non-Volatile memory controller: Intel Corporation Device f1a5 (rev 03)
03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02)
03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02)
03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02)
04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
04:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
04:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
04:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
07:00.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:01.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:03.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:05.0 PCI bridge: ASMedia Technology Inc. Device 1184
08:07.0 PCI bridge: ASMedia Technology Inc. Device 1184
09:00.0 Network controller: Intel Corporation Device 24fb (rev 10)
0b:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev c7)
0e:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf0
11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a
11:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1456
11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 145c
12:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455
12:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457
Based on that, your 0e: device is your video card, so hopefully switching to the proprietary drivers will fix your lockups and possibly your error messages on boot.

Quote:
Originally Posted by MarcT View Post
Happy to discuss NVMe here; all the AM4 boards I've seen have at least one M.2 socket for an NVMe.

Yep - gdisk (or fdisk, etc) is used to partition an nvme "namespace". A namespace is equivalent of a virtual disk or LUN. When you get a new NVMe out of the box, it will be pre-formatted with one namespace which occupies the entire device.

The nvme "format" (from nvme-cli) is used to setup/erase an entire namespace. Think of it as the equivalent of "ATA Secure Erase". It's a way of telling the flash controller that you want to securely destroy (discard) the entire contents of a namespace (without needing to manually overwrite it, which is bad for flash storage). So, it's useful for wiping any data already present so you can start again with a clean sheet.
Ok, that makes a lot more sense. I was trying to understand what namespaces were, but the only thing I could find were technical papers, and it was late enough that I just wasn't grasping what they were trying to teach me.

EDIT: I just remembered you're running -current. Unfortunately, AMD still hasn't added support for Xorg 1.19 yet, so the pro driver won't work on -current
 
Old 05-15-2017, 10:11 AM   #9
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64-current (started with 13.37(32))
Posts: 328

Rep: Reputation: 89
About IOMMU and message
Code:
[    9.374585] AMD-Vi: Event logged [
[    9.374586] IO_PAGE_FAULT device=0e:00.0 domain=0x0003 address=0x000000f4001f48c0 flags=0x0010]
I had problems with that in my new machine FX-8320E/Gigabyte 970A-DS3P (not so 'new' ) I assembled in September last year.
Boot was stuck for ~20 seconds at those messages. I found the solution was adding iommu=soft at the append line in lilo.conf.
Also, there is an option in BIOS 'IOMMU Controller', it must be enabled.
 
3 members found this post helpful.
Old 05-15-2017, 11:53 AM   #10
MarcT
Member
 
Registered: Jan 2009
Location: UK
Distribution: Slackware 14.2
Posts: 106

Original Poster
Rep: Reputation: 44
Quote:
Originally Posted by bassmadrigal View Post
EDIT: I just remembered you're running -current. Unfortunately, AMD still hasn't added support for Xorg 1.19 yet, so the pro driver won't work on -current
Thanks - I've just come to that same conclusion!

However, trying to install the AMDGPU-PRO driver and then removing it seems to have "cured" the hangs in firefox. I'm sure I've broken something else (like UVD or Mesa) instead, as I've not reinstalled the X or Mesa packages.

Anyhow, I think I'm going to do a fresh install of -current and perhaps try kernel 4.11.1.
 
Old 05-15-2017, 12:42 PM   #11
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,302

Rep: Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278
Quote:
Originally Posted by MarcT View Post
However, trying to install the AMDGPU-PRO driver and then removing it seems to have "cured" the hangs in firefox. I'm sure I've broken something else (like UVD or Mesa) instead, as I've not reinstalled the X or Mesa packages.
If you used my SlackBuild, I made great care to try and prevent any damage to the official packages. But, if you happen to find something messed up, I'd like to try and fix it (even if you can't use the package on -current).

I think the only thing that should be left is an entry in your /etc/ld.so.conf pointing to the now non-existent /opt/amdgpu-pro/lib/x86_64-linux-gnu/, but that shouldn't hurt anything since it will just move on down to the next entry.

And in verifying that path, I just realized that it is likely broken on 32bit Slackware (since the x86_64 is hardcoded rather than using $DRIARCH). So I'll have to fix and test it when I get home.
 
Old 05-16-2017, 07:24 PM   #12
MarcT
Member
 
Registered: Jan 2009
Location: UK
Distribution: Slackware 14.2
Posts: 106

Original Poster
Rep: Reputation: 44
Quote:
Originally Posted by bassmadrigal View Post
If you used my SlackBuild, I made great care to try and prevent any damage to the official packages. But, if you happen to find something messed up, I'd like to try and fix it (even if you can't use the package on -current).
Ah - I had already tried a ham-fisted approach before I knew about your packages. I had downloaded the RedHat AMDGPU-PRO drivers, ran rpm2tgz on them, and installed the resulting packages. This broke X badly (mismatched ABI, etc). It doesn't matter because I wanted to re-partition the NVMe anyway and re-install with the latest updates to -current.

I've also been testing converting ext3 to ext4 in-place, and running e4defrag. The time taken to fsck my /home went from > 9mins to ~1min.

Next-up: Kernel 4.11.1 with Ryzen.
 
Old 05-16-2017, 09:12 PM   #13
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,153
Blog Entries: 3

Rep: Reputation: 340Reputation: 340Reputation: 340Reputation: 340
Sorry did not read all replys. From the many years I have used slackware i am sure the -j7 told me Pat hqs been a a AMD USER a long time if you want to deal with ryzen as q tickle but many of us knew of the threadripper over a year ago. Many hardware people understand what is considered coming up. Because building the controller chip is 99 percent of the battle. IMB failed but Cray can build the controller. Nice rant or is AMD got the best thread. Winks at New York.
 
Old 05-16-2017, 10:17 PM   #14
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,302

Rep: Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278Reputation: 2278
Quote:
Originally Posted by MarcT View Post
Ah - I had already tried a ham-fisted approach before I knew about your packages. I had downloaded the RedHat AMDGPU-PRO drivers, ran rpm2tgz on them, and installed the resulting packages. This broke X badly (mismatched ABI, etc). It doesn't matter because I wanted to re-partition the NVMe anyway and re-install with the latest updates to -current.
Yeah, it took a lot of testing from me and a few others. There were a lot of commits to work through everything.
 
1 members found this post helpful.
Old 07-12-2017, 10:04 PM   #15
slackerDude
Member
 
Registered: Jan 2016
Posts: 44

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

This is to upgrade my q9550, because 8GB as a daily machine is really getting limiting (and my q6600 file server, already maxed out at 8GB as well is getting overloaded with some tasks - plan to offload some tasks to my main machine). Debated between a used i7 4790 desktop for $300 and a new Ryzen build for $500. Decided to bite the bullet.

Will be re-using GTX 950 and SATA SSD (with a bump to 6 GBit from my older IP-35 board which as 3 GBit SATA ports).

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.

If there's another thread I should look at instead, please point me to it.
 
  


Reply

Tags
ryzen, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ryzen processors quantumbb Linux - Hardware 4 03-06-2017 04:39 PM
LXer: AMD Ryzen 7 1700 Specs Confirmed, A $320 Rival To Intel’s $1099 i7 6900K – 8 Cores, 65W, 3.7Ghz With Unlimited Boost & Unlocked Multip LXer Syndicated Linux News 0 02-12-2017 10:43 AM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
[SOLVED] Slackware64-C client wont detect Slackware64-C Samba server slackass Slackware 5 08-07-2009 11:23 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration