SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello
recently i changed my graphic card Nvdia Gtx 1060 with Amd Rx 580.
so I uninstalled the Nvidia Driver using the Binary driver from Nvidia
rebooting kde started and boom no sound , in pavucontrol all my hdmi profils look as unplugged I tried slackware live edition and the sound works fine.
I m using kernel 4.4.157 ; need I a new kernel ?
You could try clearing out your old pulseaudio config files with something like:
Code:
mv ~/.config/pulse ~/.config/pulse_old
And then restarting pulseaudio by killing it:
Code:
pulseaudio -k
Pulseaudio should restart automatically and remake the .config/pulse files (as long as you haven't disabled autospawning for pulse). If that works then you can remove the .config/pulse_old files. If it doesn't work then we will have to dig deeper.
You need 4.19.x or later (or perhaps 4.14.x) for the kernel drivers to properly work.
I'm not sure that matters if your userspace is too old. 14.2 based "current" is probably
your best chance.
You could try clearing out your old pulseaudio config files with something like:
Code:
mv ~/.config/pulse ~/.config/pulse_old
And then restarting pulseaudio by killing it:
Code:
pulseaudio -k
Pulseaudio should restart automatically and remake the .config/pulse files (as long as you haven't disabled autospawning for pulse). If that works then you can remove the .config/pulse_old files. If it doesn't work then we will have to dig deeper.
You need 4.19.x or later (or perhaps 4.14.x) for the kernel drivers to properly work.
I'm not sure that matters if your userspace is too old. 14.2 based "current" is probably
your best chance.
thank you , any help or suggestion howto build kernel ?.
You can grab a config file from -current's source tree on your favorite mirror, then just copy that into the directory of your extracted 4.19 kernel sources.
Full instructions can be found here, but simplified instructions are below. My instructions may not follow conventional practices, but they are simple and should work fine.
Code:
# Become root
su -
# Download the latest kernel and extract it to /usr/src
wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.19.81.tar.xz
cd /usr/src
tar xvf ~/linux-4.19.81.tar.xz
cd linux-4.19.81
# Now download -current's kernel config for 4.19.x and rename it to .config
wget https://mirror.slackbuilds.org/slackware/slackware64-current/source/k/kernel-configs/config-generic-4.19.80.x64
mv config-generic-4.19.80.x64 .config
# Build the kernel and modules and then install the modules
make bzImage modules
make modules_install
# Move your kernel to /boot and generate an initrd for the new kernel
cp arch/x86/boot/bzImage /boot/vmlinuz-generic-4.19.80
$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.19.80 -a -o /boot/initrd-4.19.80.gz)
# Update either /etc/lilo.conf to point to the new kernel and run lilo or run eliloconfig
# If you need help with this part, let us know what bootloader you have and we can provide additional guidance
But as rogan mentioned, the rest of 14.2 is probably too old to properly use that card. You'd likely need to run the proprietary amdgpu-pro drivers or upgrade to -current (which is the development version of Slackware that will eventually become 15.0)
You can grab a config file from -current's source tree on your favorite mirror, then just copy that into the directory of your extracted 4.19 kernel sources.
Full instructions can be found here, but simplified instructions are below. My instructions may not follow conventional practices, but they are simple and should work fine.
Code:
# Become root
su -
# Download the latest kernel and extract it to /usr/src
wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.19.81.tar.xz
cd /usr/src
tar xvf ~/linux-4.19.81.tar.xz
cd linux-4.19.81
# Now download -current's kernel config for 4.19.x and rename it to .config
wget https://mirror.slackbuilds.org/slackware/slackware64-current/source/k/kernel-configs/config-generic-4.19.80.x64
mv config-generic-4.19.80.x64 .config
# Build the kernel and modules and then install the modules
make bzImage modules
make modules_install
# Move your kernel to /boot and generate an initrd for the new kernel
cp arch/x86/boot/bzImage /boot/vmlinuz-generic-4.19.80
$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.19.80 -a -o /boot/initrd-4.19.80.gz)
# Update either /etc/lilo.conf to point to the new kernel and run lilo or run eliloconfig
# If you need help with this part, let us know what bootloader you have and we can provide additional guidance
But as rogan mentioned, the rest of 14.2 is probably too old to properly use that card. You'd likely need to run the proprietary amdgpu-pro drivers or upgrade to -current (which is the development version of Slackware that will eventually become 15.0)
Thank you very much for all suggestions and notes , I will try hopfly no breaking system IoI
for the Proprietary amdgpu-pro I dont know howto instal it at all.
I swith to Grub2 because lilo fall back to safe mode , it was first issue related to ma card rx 580.
I had some similar issues with my R9 Nano. I didn't want to switch to -current, don't want to risk any breakage. I just installed a fairly recent kernel package from current and that seemed to just work. Probably still does with the latest kernel package, although I can't offer any guarantees. I did update mesa, which was quite a chore on 14.2, although the worst of it, llvm-8.0, can be found in /extra in slackware. So, in my experience 14.2 can be made to work, but it does require quite some compilation to get good performance.
I had some similar issues with my R9 Nano. I didn't want to switch to -current, don't want to risk any breakage. I just installed a fairly recent kernel package from current and that seemed to just work. Probably still does with the latest kernel package, although I can't offer any guarantees. I did update mesa, which was quite a chore on 14.2, although the worst of it, llvm-8.0, can be found in /extra in slackware. So, in my experience 14.2 can be made to work, but it does require quite some compilation to get good performance.
Thank you so much for your reply and advise
I tried to install compile and install a new kernel 4.19
no sound also probably Something I mess up ... , but I will try again if not i will install the live edition of slackware.
thank you everyone for all your concerning and help
be safe.
I have tried the same ting as PJBrs talked about. I got the Frankenware to work in the end with a LOT of work.
All I got for the trouble was a unupgradeable system that required even more work. Just don't do it is My advice.
Running current is not going to be a bug-free experience. Already the installer usually has a few gremlins but you'll
have the "latest and the greatest" of the best, and all your hardware IS going to be supported.
I have tried the same ting as PJBrs talked about. I got the Frankenware to work in the end with a LOT of work.
All I got for the trouble was a unupgradeable system that required even more work. Just don't do it is My advice.
Running current is not going to be a bug-free experience. Already the installer usually has a few gremlins but you'll
have the "latest and the greatest" of the best, and all your hardware IS going to be supported.
Thank you very much , running current as it is non bug-free I prefer to stay away , I will try to install the live edition based on current less bugs I think .
Nothing is bug-free, and I dind't mean to imply that current is a buggy mess. It's relly quite ok. Try it!
If you happen to encounter something you percieve as a bug, then report it here. There's a lot of helpful
people here that usually helps you out with problems.
Nothing is bug-free, and I dind't mean to imply that current is a buggy mess. It's relly quite ok. Try it!
If you happen to encounter something you percieve as a bug, then report it here. There's a lot of helpful
people here that usually helps you out with problems.
Hello , writing from installed Live slackware edition ; sound work fine , and i m planning to try the current in futur. surely it is not buggy mess but for daily use I suspect to be a good choice correct me if I m wrrong
And I M sure that slack s users are a union community ready to help and this from my personel expriance.
Thank you veru much happy to be among slack s users.
After that, audio through HDMI works fine for me.
You might need to restart application.
NOTE: Your audio device might not be defined as HDMI, mine was named 'HDA ATI SB', but that will vary depending on your hardware.
Thank you I tried this also but the problem is that in pavucontrol it said the same thing ...Unplugged also in alsa it showen as S/PDIF so Amd/Ati is recognized and video worked only problem of sound.
I m working on slackware live edition Kde5 just installed and sound via hdmi and the built in work fine ,let explore this Slackware option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
