LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Register
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 03-20-2025, 06:06 PM   #1
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Rep: Reputation: 220Reputation: 220Reputation: 220
switching from an intel to an amd system without reinstall?


Hi!
I got a new computer (a "mini gaming pc" with a Ryzen 8845, which is practically the laptop version of the Ryzen 8700G APU) today. I had thought it would be no problem to take the SSD with my Slackware64 15.0 install from my ThinkPad (8th gen intel) and stick it in there. But even after resolving UEFI troubles, there are problems.

I thought all of this stuff is detected at runtime, is there something about drivers fixed at install?

The biggest problem is that SDDM doesn't come up. I use Plasma/Wayland.

When I run startkwayland as user, Plasma comes up, but it doesn't use the right driver I think. I stuck the amdgpu module in the initrd, but I don't know if it does anything.

Another problem is that the wifi is not detected. (But I was planning to run a network cable eventually, so not a total dealbreaker. It's some chinese wifi card with a brand I've never seen before.)

I'd really like to avoid a new install. Should I do it anyway, or is there a way?

thanks for reading so far

Last edited by j12i; 03-20-2025 at 06:15 PM. Reason: wording
 
Old 03-20-2025, 09:05 PM   #2
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,053

Rep: Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179
Are you able to trawl the system logs for any errors? Is SDDM starting an Xorg server, or as a Wayland client?
 
Old 03-21-2025, 12:32 AM   #3
pan64
LQ Addict
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 26,460

Rep: Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608Reputation: 8608
The questions are: how the system was configured and how the new hardware is supported at all?
If you tied (hardcoded) anything on the old host which is invalid on the new one.
Yes need to check the logs.
 
Old 03-21-2025, 01:10 AM   #4
Petri Kaukasoina
Senior Member
 
Registered: Mar 2007
Posts: 3,144

Rep: Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770Reputation: 2770
At least, you need this:
Code:
rm /etc/udev/rules.d/70-persistent-net.rules
 
2 members found this post helpful.
Old 03-21-2025, 01:30 AM   #5
zuriel
Member
 
Registered: Aug 2012
Distribution: Slackware
Posts: 70

Rep: Reputation: 59
Slackware64 15.0? Is that still on the 5.15.x kernel series?

Kernel 5.15 was released in 2021, the Ryzen 8845 is a chip that launched in mid-2023. It wouldn't be surprising if Slackware 15.0 just plain didn't have driver support for the iGPU.

You could try grabbing the kernel from slackware64-current. You might need Mesa and other things too. Or just fully switch to -current.
 
1 members found this post helpful.
Old 03-21-2025, 06:01 AM   #6
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Thanks all!

sddm.log and Xorg.0.log were unhelpful. I also trawled /var/log/{messages,syslog}, but not thoroughly.

I tried to find out which kernel introduced the relevant support, but I guess it's not so clear cut. This article makes me want to at least go to 6.3, I also found an unsourced claim that I'll need at least kernel 6.7. But it doesn't matter so much in the end, I'll just go with the -current kernel.

I don't really want to go with current proper, I already did this in the last cycle and did get used to it, but living in the quieter world of stable was a relief after all.


PS: for anyone reading this in the future, just sticking the amdgpu module in the initrd is not fruitful.
 
Old 03-21-2025, 06:48 AM   #7
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Running kernel 6.12 now (still on the thinkpad for now).

As for Mesa, I want at least 23.3. What are mesa's dependencies, in terms of glibc etc? glu, obviously. I've played this game before, with my thinkpad's iGPU and Slackware 14.2, of trying to replace as little as necessary of Slackware stable to get to as high as possible a mesa version. Also I'd have to upgrade X and Wayland, for xf86-video-amdgpu, wouldn't I? Going to -current starts to sound better and better. *sigh*
 
Old 03-21-2025, 07:38 AM   #8
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Tried running mesa 23.3.4 from current (cumulative archives).

Parts of it are compiled against libLLVM 17 and glibc 2.38. (Slackware 15.0: 13 and 2.33.)

I guess I could try building this (or a newer) mesa myself… or go to current already. Any other options?
 
Old 03-21-2025, 08:06 AM   #9
nhattu1986
Member
 
Registered: Dec 2005
Distribution: slackware
Posts: 60

Rep: Reputation: 36
you can try to build latest mesa on slack15 and see what kind of error is happen.

according to mesa website,
https://docs.mesa3d.org/install.html

you need:
Quote:

Python - Python 3.6 or newer is required.

Python package packaging is required on Python 3.12+: pip install packaging

Python Mako module - Python Mako module is required. Version 0.8.0 or later should work.

Lex / Yacc - for building the Mesa IR and GLSL compiler.

On Linux systems, Flex and Bison versions 2.5.35 and 2.4.1, respectively, (or later) should work. On Windows with MinGW, install Flex and Bison with:

slackware 15 should be able to build mesa.
 
Old 03-21-2025, 08:52 AM   #10
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Compiling the current mesa (25.0.2) from current has so far needed me to:
  • install python3-meson-opt from SBo (already had that)
  • install rust16 from SBo (for both of these, follow the README to put them on the PATH for subsequent mesa compilation)
  • install rust-bindgen from extra/
  • (I upgraded llvm-19 from extra/ too, for good measure. If you do that, you also need to install llvm13-compat from extra/!)
  • compile libdrm with SlackBuild/version from current (short compile, this made more sense to me than installing the compiled package)
  • compile spirv-llvm-translator from current – this failed because it wants LLVM 20

This is where I give up for now.

The cumulative archive on slackware.uk doesn't include source/ (for disk space reasons, iirc). Can I find these older versions of official SlackBuilds anywhere? Then I could try this process again with an older mesa version.
 
Old 03-21-2025, 09:09 AM   #11
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Ok I didn't give up just yet. I was able to build spirv-llvm-translator for llvm 19 with the recent -current SlackBuild. But it's too old still to compile this mesa. From mesa configure:
Quote:
Dependency SPIRV-Tools found: NO. Found 2021.0.0 but need: '>= 2022.1'
So now I could try walking back mesa versions, if they build with the most recent SlackBuild.
 
Old 03-21-2025, 10:23 AM   #12
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Mesa 24.3 has the same error as 25.0. Mesa 23.3 won't compile with the SlackBuild for 25.0. I can still try 24.{0,1,2}. Else to go ahead I'd need to get my hands on an older version of PV's build script, or figure out the build options to mesa myself.

I've looked btw, the binary packages don't include the SlackBuild.

ETA: same error on 24.0

Last edited by j12i; 03-21-2025 at 10:35 AM.
 
Old 03-21-2025, 04:09 PM   #13
j12i
Member
 
Registered: Nov 2013
Location: UTC+1
Distribution: Slackware64-current & -15.0
Posts: 465

Original Poster
Rep: Reputation: 220Reputation: 220Reputation: 220
Marking as solved as I'm upgrading to current.

Still, feel free to answer open questions.
 
  


Reply



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
LXer: Intel hires former-AMD Radeon Chief, Raja Koduri, Intel planning high-end discrete graphics solutions LXer Syndicated Linux News 0 11-10-2017 05:12 AM
Will "yum reinstall httpd" and "yum reinstall php" mess with my settings? trvo Linux - Server 2 03-30-2012 05:02 AM
Reinstall Slack's LILO after WIndows XP reinstall __spc__ Linux - Newbie 3 02-15-2009 09:04 AM
To reinstall or not to reinstall...that's the question.. minike Slackware 3 09-17-2005 06:24 PM
reinstall windows, reinstall GRUB too? leupi Linux - Software 1 05-07-2005 10:50 AM

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

All times are GMT -5. The time now is 06:14 PM.

Contact Us - Advertising Info - Rules - Privacy - Donations - Contributing Member - LQ Sitemap - "Weather apps tell you it'll rain. Wyndo tells you when to go."
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