Slackware64 and Ryzen

bassmadrigal · 07-18-2017, 10:54 AM

Quote:

Originally Posted by slackerDude

I now need to figure out sound..
root@kraken:~# lspci | grep -i audio
23:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1)
25:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457

This says that the kernel doesn't know what that device ID is. If memory serves, some audio drivers weren't available in Linux until the 4.11 kernel, so you'll want to run at least that. But 55020 has pre-built 4.12 kernels available on his site, so it might be worth trying those.

https://dusk.idlemoor.tk

slackerDude · 07-18-2017, 02:05 PM

After adding HD-Audio->realtek codec, sound was there too.. (saw that it was there originally in 4.9.37, so I figured it wasn't going to be too hard).

Was able to boot X, start chrome, play an 8k video (just for fun) in chrome with sound and sensors working.. A little disappointed it stuttered at 8k, but was fine in 4k (I guess webm isn't that great..). Was going to try with firefox/flash (what I usually use) and, got my first hang - not while watching, no.. Just after clicking "download flash" on adobe's site..

Every 60 seconds or so, I could move the mouse a bit, but network was down, etc.

Rebooted into BIOS and found CPU speed at 2.456 GHz (what?). Reset to 3.6 (my "basic" overclock) and RAM to 2800 GHz, and right now, trying to clear CMOS, because the machine refuses to even POST.. Why are CMOS reset jumpers always so hard to find, and why didn't MSI even include a basic jumper?? Had to steal one from another machine..

Ok, it POSTED. Back to trying with RAM at 2800, CPU stock..

MarcT · 07-18-2017, 04:02 PM

Quote:

Originally Posted by slackerDude

I now need to figure out sound..
root@kraken:~# lspci | grep -i audio
23:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1)
25:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457

That seems correct. However, when opening the kde multimedia config, no hardware is shown, only the "dummy" device. Started pulse and alsa, IIRC, but still nothing. IIRC, with my current machine, both nvidia and the built-in audio devices showed up in the list, I just had to play around with them until it worked..

Hmm. From my current machine, I see that KDE just needs to find pulseaudio, because it's set to "HDMI-out", but I use just the regular "line out" plug anyway (it goes into an external amp).

I rebuilt the kernel (again - like the 7th time now) because by default "tmpfs" wasn't turned on (really?), which caused pulseaudio to fail. Now it's complaining about missing module "module-alsa-card"..

Are you on -current? I think audio worked out of the box for me. Make sure your user is in the audio group.

This is my system:

Code:

root@deepthought:~# lspci -v | grep -i audio
0e:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf0
12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457

looks like the same motherboard audio device:

lspci

Code:

12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457
        Subsystem: ASRock Incorporation Device 1220
        Flags: bus master, fast devsel, latency 0, IRQ 325
        Memory at fe700000 (32-bit, non-prefetchable) [size=32K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [64] Express Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

...except the actual "line out" seems to be handled by "snd_hda_codec_realtek" (ALC1220):

Code:

root@deepthought:~# dmesg | grep -i audio
[    9.084974] snd_hda_intel 0000:0e:00.1: Handle vga_switcheroo audio client
[    9.144672] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[    9.144674] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    9.144675] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    9.144675] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[    9.144676] snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x1e/0x0
[    9.144676] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    9.144677] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
[    9.144678] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
[    9.144679] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
[    9.160699] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input11
[    9.160789] input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input12
[    9.160886] input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input13
[    9.161069] input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input14
[    9.161270] input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input15
[    9.161499] input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input16
[    9.161656] input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input17

Perhaps I'm just lucky it works!

MarcT · 07-18-2017, 04:10 PM

Quote:

Originally Posted by slackerDude

got my first hang - not while watching, no.. Just after clicking "download flash" on adobe's site..

Sounds about right - I was getting hard hangs with firefox idle. Not entirely sure what fixed it. Check these things:
1) Update UEFI to latest, make sure it contains AGESA 1.0.0.6a (The "a" release is the latest).
2) Check the "Command Rate" setting for your RAM. Lots of UEFI get this wrong - you may need to set manually (probably to 2T, if 1T is too tight on timing).

M

bassmadrigal · 07-18-2017, 04:33 PM

Quote:

Originally Posted by slackerDude

...why didn't MSI even include a basic jumper?? Had to steal one from another machine..

Likely because you can use anything to short it. I usually use a screwdriver (if I'm working on the computer, it's usually my phillips that I'm using to screw in the motherboard and other devices into the case).

MarcT · 07-18-2017, 04:41 PM

The ASRock motherboard has a nice "Clear CMOS" pushbutton on the back, so you don't even need to open the case.

BrZ · 08-26-2017, 07:42 PM

Hi Slackers! Long time no post. Nice to see people are fine and Slackware is kicking ass.
Upgraded my ASUS/FX-8350 to a Gigabyte/R7 1700. No sound for now. Alsa is pointing to the first GPU as default device instead of the onboard ALC1220.
Time to test my chip under single and multi-threaded heavy load to see if it was from the 'bad mask' batch and start to tune the system.
If I can't sort the audio I'll call for help ;]

bassmadrigal · 08-26-2017, 09:56 PM

Quote:

Originally Posted by BrZ

Hi Slackers! Long time no post. Nice to see people are fine and Slackware is kicking ass.
Upgraded my ASUS/FX-8350 to a Gigabyte/R7 1700. No sound for now. Alsa is pointing to the first GPU as default device instead of the onboard ALC1220.
Time to test my chip under single and multi-threaded heavy load to see if it was from the 'bad mask' batch and start to tune the system.
If I can't sort the audio I'll call for help ;]

You need at least the 4.11 kernel for the ALC1220. Since that is EOL, it'd probably be better to use the 4.12 kernel. Forum member 55020 has 4.12 builds available for Slackware through his dusk project.

BrZ · 08-27-2017, 01:34 PM

Quote:

Originally Posted by bassmadrigal

You need at least the 4.11 kernel for the ALC1220. Since that is EOL, it'd probably be better to use the 4.12 kernel. Forum member 55020 has 4.12 builds available for Slackware through his dusk project.

Thanks bassmadrigal. 4.12.9 compiled under 4 minutes =]
My problem is that this board have two ALC1220 chips. Sound is ok from the back outputs but the front is not working. I need headphones... fam don't like as much AC/DC and Sabbath as I do. Dual lan was worked, but the audio is being a pita. If I can't sort things out I'll open a new thread. Thanks for pointing to the 55020 scripts.

MarcT · 08-29-2017, 11:26 AM

Quote:

Originally Posted by BrZ

Time to test my chip under single and multi-threaded heavy load to see if it was from the 'bad mask' batch and start to tune the system.

As I understand it, it seems Ryzen CPUs manufactured from week 25 of 2017 are probably OK. I say probably because I've been away and haven't been following the latest discussions on the AMD forum.

The date code is engraved on the CPU itself, under the RYZEN logo. Mine says "UA 1711PGS" => Week 11 of 2017, so is affected (and does segfault if stressed).
It seems stable if I disable the uOP cache in the UEFI, so I'm pondering the RMA option.

Let us know how you get on with yours!

kjhambrick · 08-29-2017, 01:50 PM

All --

Not an AMD Guy myself, but this Slashdot Post:

New Ryzen Running Stable On Linux, Threadripper Builds Kernel In 36 Seconds

and the links within are still interesting.

-- kjh

onebuck · 08-29-2017, 04:20 PM

Hi,
Eric has been busy building a new box and everyone may find this interesting.

Quote:

From Build box: step 1, install Slackware

The new computer with its Ryzen CPU created some issues for me. To start with… I had not considered the possibility that a Ryzen CPU would not have an embedded GPU and so I did not order a graphics card. Bad idea!
I ended up ripping a GPU from one of my other computers (the only PCI-express card I could find) and plugging that into the new computer. That gave me a working video instead of a monitor that kept falling asleep. Next came Slackware. When I booted the Slackware 14.2 installer, it did not give me a network connection. The Slackware Live Edition (based on slackware-current) worked properly on the other hand. But the graphics card I plugged into the computer did not work too well with the nouveau driver – whenever I started Chromium, it was inevitable that the computer would lock up after some time. Initially I blamed this on the computer hardware and feared that I bought a dead duck, but once I stopped running Chromium in the graphical desktop of Slackware Live, the system would remain operational. Since it is not going to be used as a desktop system and I will access it only remotely, that buggy nouveau driver is not a big issue and I could still install the binary Nvidia blob if needed.

So, the question became: I want to run a stable Slackware release on my new build server, but how am I going to install it? I was facing two major issues:

The installer of Slackware 14.2 does not support NVMe boot devices (the new type of SSD hard drives with a M.2 PCI-express interface)
The Slackware 14.2 installer lacks network capability on this new hardware, so I would have to perform a local install

I could spend a USB stick, putting the Slackware 14.2 DVD ISO on it, but then I still would have to patch the installer and I would not have a network connection after reboot. Considering the fact that slackware-current’s kernel works much better and NVMe support was added to the -current installer recently, I decided on a different approach.

Good read with loads of information.
Hope this helps.
Have fun & enjoy!

slackerDude · 08-29-2017, 04:45 PM

Yeah, just ran "kill-ryzen.sh" and found my CPU does die after an hour or so at full load.. (well, ran it once - it may die sooner next time). Now debating about taking an 80% refund from Amazon (easier), or trying to RMA through AMD (get a new chip, but may take 2-3 weeks).

Lesson learned: AMD's still got some work to do..

1337_powerslacker · 08-31-2017, 08:22 PM

Quote:

Originally Posted by slackerDude

Yeah, just ran "kill-ryzen.sh" and found my CPU does die after an hour or so at full load.. (well, ran it once - it may die sooner next time). Now debating about taking an 80% refund from Amazon (easier), or trying to RMA through AMD (get a new chip, but may take 2-3 weeks).

Lesson learned: AMD's still got some work to do..

There will always be problems with first revisions of silicon, and Ryzen is no exception to the rule. The good news is that AMD has been hard at work resolving the issue.

The full article can be found here, but here is a pertinent excerpt:

Quote:

I've now been running this system all afternoon/evening with the kill-ryzen script and have not encountered any compiler segmentation faults or other problems for that matter. The same motherboard, cooling, BIOS, Linux installation, etc, were maintained the same as the previously affected configuration. Considering how easy it was to reproduce on the previous CPU, I feel pretty confident now this issue indeed is no more and just isolated to the CPU.

This stands as a good example of why it's generally not a good idea to adopt first revisions of silicon, as there are inevitably problems with it, despite the promises that are made.

onebuck · 09-04-2017, 10:15 AM

Hi,

I came across this article and think it is something other LQ members will find interesting; Ryzen Pro: AMD Resets Expectations on Commercial Desktops

Quote:

Rob Enderle

Earlier this week, I was at the Ryzen Pro launch in New York from AMD. I feel a tad vindicated because a few years back, I suggested that AMD resource a desktop processor to compete with Intel because Intel was focused on creating a smartphone part. I had severe doubts at that time that Intel would be successful because it lacked Microsoft support, but the effort was pulling so many resources from PCs that the PC market was stalling; it left an opening for a competitor like AMD to move in. Eventually, AMD came to that same conclusion and Ryzen consumer, Threadripper, and most recently Ryzen Pro resulted. At the event Dell, HP and Lenovo, the big three in terms of commercial desktops, were on stage in support of AMD’s efforts because they know that selling more desktops is tied to users needing something their existing machine doesn’t have, In this case, it’s all about cores.
Desktop PCs and Users
For those who don’t push the envelope in performance laptops, computers that are several years old continue to meet their needs. Email, Word and filling out expense reports don’t push the envelope in performance and the big reasons for those users to upgrade are battery life, carry weight and, increasingly, security. Desktop users are increasingly focused on performance. These are engineers, analysts, graphic artists, architects, and animators who use every ounce of performance and whose work is tied to the ability of the firm to meet timelines and objectives. For them, performance is often the difference between success and failure.

A very informative article!

Hope this helps.
Have fun & enjoy!