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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,139
Original Poster
Rep:
Quote:
A Fix Is On The Way For AMD HDMI Audio Being Broken With Linux 6.1+
Michael Larabel. 28 December 2022.
More than a few Phoronix readers have written in that have been early adopters to the Linux 6.1 kernel released as stable earlier this month and now finding their HDMI audio outputs no longer working. Fortunately, the issue has been sorted out by upstream developers and a fix is on the way..........
the issue has been analyzed as only affecting the HD audio HDMI codec driver for AMD/ATI hardware when using PulseAudio or PipeWire. If you are using direct audio output via ALSA raw access, that isn't affected by this Linux 6.1 regression.........
Testing some 64bit laptop kernel 6.1.1 today. Been using CONFIG_PCIEASPM_POWER_SUPERSAVE=y for about a week.
What it did, well it reduced the voltage, and the fan RPM, slowed the battery drain, and basically silenced this laptop.
It's one of those machine specific things/quirks, and the generic distribution kernel doesn't provide it for various reasons.
If you have a laptop which supports ASPM and doesn't expose it in BIOS, it's great that the kernel can expose it.
Kernel 6.1.2 does not play well with NVIDIA-Linux-x86_64-525.60.11. Startx will start an X session, but when I exit back to runlevel 3 the system no longer works: my monitors are no longer recognized and I have to reboot. Removing the Nvidia driver and going back to Nouveau restores operation.
Kernel 6.1.2 does not play well with NVIDIA-Linux-x86_64-525.60.11. Startx will start an X session, but when I exit back to runlevel 3 the system no longer works: my monitors are no longer recognized and I have to reboot. Removing the Nvidia driver and going back to Nouveau restores operation.
I know it will get fixed.
After reading your post I dropped back to run level 3 and all was fine with terminals, monitor. Did a startx and am now back in KDE.
Kernel 6.1.2 does not play well with NVIDIA-Linux-x86_64-525.60.11. Startx will start an X session, but when I exit back to runlevel 3 the system no longer works: my monitors are no longer recognized and I have to reboot. Removing the Nvidia driver and going back to Nouveau restores operation.
I know it will get fixed.
Is this the drop-back-to-console issue others were having with 5.19 and above? Seems like it's been a common problem for awhile. Which card do you have? (1050ti, 525.60.11, still on 5.19.17, no problems.) UEFI? I seem to recall a framebuffer issue, as well. (Yes, I'm booting UEFI, not legacy.)
p.s. I've built 6.1.2 ( huge, generic, modules ) Packages and I'll install them 'soon' but I've got to keep my LapTop Available for Customer Support until later today.
In addition I've got VMware-Workstation-Full-16.2.5-20904516.x86_64.bundle and VMware-Workstation-Full-17.0.0-20800274.x86_64.bundle ready to go but one thing at a time
Is this the drop-back-to-console issue others were having with 5.19 and above? Seems like it's been a common problem for awhile. Which card do you have? (1050ti, 525.60.11, still on 5.19.17, no problems.) UEFI? I seem to recall a framebuffer issue, as well. (Yes, I'm booting UEFI, not legacy.)
I dropped back to 5.19.17 and things are again happy enough to run in a wayland session.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,139
Original Poster
Rep:
The 6.1.2 kernel from -current/testing* is working perfectly on this box with the NVIDIA-Linux-x86_64-470.161.03 driver and VirtualBox-7.0.4-154605-Linux_amd64.
Generic Kernel Version 6.1.2.kjh is running fine on my Slackware64 15.0 + Multilib LapTop.
I used Pat's Configs after editing the gcc version.
No problems with NVidia but I did have to uninstall then reinstall VMWare to avoid an 'already installed error' after upgrading to VMWare-17.0.0 on linux-5.15.86.
I'll run 6.1.2 until something breaks or I'll abandon 5.15.y, except Pat's Official Kernel later this week.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.