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.
VLC, obs, scide, and frescobaldi (four of the qt5 apps I could think of off the top of my head) work for me the morning after. Can you be a bit more specific? Did you log out/log back in again?
Sun Jun 25 19:11:02 UTC 2023
l/freetype-2.13.1-x86_64-1.txz: Upgraded.
NOTE: Infinality mode has been removed. If you've enabled it in your
/etc/profile.d/freetype.{csh,sh} script, you'll need to make sure that
either all of the available choices are commented out, or enable one of
the two remaining choices.
9 updates (x86_64). Including a (* Security fix *)! : 7 upgraded, 2 rebuilt
Code:
Mon Jun 26 19:44:44 UTC 2023
ap/vim-9.0.1667-x86_64-1.txz: Upgraded.
This fixes a rare divide-by-zero bug that could cause vim to crash. In an
interactive program such as vim, I can't really see this qualifying as a
security issue, but since it was brought up as such on LQ we'll just go
along with it this time. :)
Thanks to marav for the heads-up.
(* Security fix *)
l/freetype-2.13.1-x86_64-2.txz: Rebuilt.
The profile scripts still mentioned three options to choose from when there
are now only two. This has been fixed.
Thanks to burdi01.
l/gegl-0.4.46-x86_64-1.txz: Upgraded.
l/imagemagick-7.1.1_12-x86_64-1.txz: Upgraded.
l/librsvg-2.56.1-x86_64-1.txz: Upgraded.
l/openexr-3.1.9-x86_64-1.txz: Upgraded.
l/pipewire-0.3.72-x86_64-1.txz: Upgraded.
n/network-scripts-15.0-noarch-19.txz: Rebuilt.
This update fixes a bug and adds a new feature:
Re-add support for the DHCP_IPADDR parameter from rc.inet1.conf.
Expand the help text for DHCP_IPADDR in rc.inet1.conf.
Add support for a DHCP_OPTS parameter.
Thanks to ljb643 and Darren 'Tadgy' Austin.
xap/vim-gvim-9.0.1667-x86_64-1.txz: Upgraded.
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: PCI dev 2723/4080, rev=0x340, rfid=0x10a100
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-78.ucode failed with error -2
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: loading /lib/firmware/iwlwifi-cc-a0-77.ucode failed with error -22
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-77.ucode failed with error -22
< idem for all firmware between 76 and 40 >
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-39.ucode failed with error -2
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: no suitable firmware found!
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: minimum version required: iwlwifi-cc-a0-39
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-cc-a0-78
[jeu. 29 juin 00:24:22 2023] iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
kernel-firmware-20230625_ee91452 completely broke all my network stuff (wifi, bluetooth...)
Revert to : kernel-firmware-20230620_045b213
and everything is back to normal
EDIT
It also broke my X session
Code:
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: Direct firmware load for amdgpu/renoir_asd.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <psp> failed -19
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: loading /lib/firmware/amdgpu/renoir_dmcub.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: Direct firmware load for amdgpu/renoir_dmcub.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] [drm:dm_early_init [amdgpu]] *ERROR* DMUB firmware loading failed: -19
[jeu. 29 juin 00:24:23 2023] [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <dm> failed -19
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: loading /lib/firmware/amdgpu/renoir_pfp.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: Direct firmware load for amdgpu/renoir_pfp.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <gfx_v9_0> failed -19
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: loading /lib/firmware/amdgpu/renoir_sdma.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] amdgpu 0000:03:00.0: Direct firmware load for amdgpu/renoir_sdma.bin failed with error -22
[jeu. 29 juin 00:24:23 2023] [drm:sdma_v4_0_early_init [amdgpu]] *ERROR* Failed to load sdma firmware!
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,199
Rep:
I can confirm the above.
On this box, no available WiFi connections were shown in network manager. At first I thought that was the fault of the new network manager update, but after reading the post above I reverted to the previous version of kernel-firmware and that cured the problem.
Thanks Marav.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,101
Rep:
Lost wifi, X session OK but an odd error when trying to run vivaldi (sorted after chmod 7455), can't figure out if/how that's related to today's upgrades:
Code:
[2017:2017:0629/103041.238125:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/vivaldi/vivaldi-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap
kgha@darkstar:~$ [2027:2027:0100/000000.260943:ERROR:zygote_linux.cc(661)] write: Broken pipe (32)
Rebuilding the firmware package right now, with marav's patch - will see how that works out.
EDIT: the rebuilt firmware package (244.8 M) seems to work just fine. At first login from the sddm screen I encountered the "Could not create ICE listening socket" error message, but second attempt worked as did the next login after reboot.
Deeply grateful for the knowledge (and the knowledgeable people) here at the forum, and for the slackware.uk/cumulative repo.
the "culprit" is copy-firmware.sh
They made few changes in order to support xz/zstd compression, but they also change the way firmware is copied
Especially, they replace "cp -d $f ..." with "cat $f > ..."
I revert to the previous version of the script with the patch attached, and there is no need to modify "cd $PKG" in the SlackBuild
Code:
--- kernel-firmware.SlackBuild 2023-06-29 04:24:29.696133631 +0200
+++ kernel-firmware.SlackBuild.1 2023-06-29 11:36:37.174925427 +0200
@@ -60,6 +60,7 @@
mv linux-firmware lib/firmware
# Make sure that symlinks are created by running "make install":
( cd lib/firmware
+ cat $CWD/copy-firmware.patch | patch -p1 --verbose || exit 1
echo "Running make DESTDIR=$PKG install..."
make DESTDIR=$PKG install 2> /dev/null
)
The result is a pkg with the right size
Code:
$ ls -lh /tmp/kernel-firmware-20230625_ee91452-noarch-1.txz
-rw-r--r-- 1 root root 245M Jun 29 11:40 /tmp/kernel-firmware-20230625_ee91452-noarch-1.txz
But the best practice is probably to change the build directory, and leave the source untouched.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
