I added this kernel to updates_testing which is the latest of 6.5.x series. Files list will follow, as well as the kernel-linus companion for 6.5.13 and vbox modules. It mainly fixes a freeze on VT switching with nvidia (part of #52541), amongs other upstream updates. Worthwhile an update.
The version in updates testing is currently only 6.5.13-1 I have been running 6.5.13-2 from backport testing for a while. And confirm it fixes VT switching with nvidia drivers. Should i reinstall it from updates testing when it appear there, to be sure it is the same? BTW there are several kernels to clean from backport testing.
CC: (none) => fri
(In reply to Morgan Leijström from comment #1) > The version in updates testing is currently only 6.5.13-1 > Yes, correcting, thanks. vbox kmod et al. will follow. > I have been running 6.5.13-2 from backport testing for a while. > And confirm it fixes VT switching with nvidia drivers. > Should i reinstall it from updates testing when it appear there, to be sure > it is the same? > 6.5.13-2 from backports_testing and 6.5.13-1 in updates_testing are the same as features. They differs only in naming scheme: versioned in backports_testing, so more practical for installing/uninstalling/bumping version, etc.) and non versioned for the one in updatest_testing (so to preserve the original scheme as in mga9, for now). > BTW there are several kernels to clean from backport testing. Yes (mostly everything except last one, and ditto for cauldron).
Summary: Update request: kernel-6.5.13-2.mga9 => Update request: kernel-6.5.13-1.mga9
Blocks: (none) => 31994
mga9-64 OK HW: Intel i7-870, P55 chipset GPU: GTX750Ti with nvidia nvidia470 470.223.02-1 SW: Plasma X11, Normal desktop apps § All normal desktop apps OK - have been using for a few days and will keep using this. § VirtualBox 7.0.12, using dkms built module: MSW7 guest with guest additions 7.0.13 OK: internet videos, dynamic guest window resizing, USB2 flashstick, host folder sharing, bidirectional clipboard, and drag file from Dolphin to Explorer.
Working fine real hw intel core i5 and ig intel graphics 8gb ram, 1tb usb hdd usb 3 install Mga9....
Now on same system I tried modesetting driver but after a couple minutes while using Firefox it hang the desktop, had to issue the "REI" part of REISUB, got back to sddm login. From journal: dec 14 14:35:29 svarten.tribun kernel: nouveau 0000:07:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] dec 14 14:35:29 svarten.tribun kernel: nouveau 0000:07:00.0: fifo:000000:0021:[firefox[19138]] rc scheduled dec 14 14:35:29 svarten.tribun kernel: nouveau 0000:07:00.0: fifo:000000: rc scheduled dec 14 14:35:29 svarten.tribun kernel: nouveau 0000:07:00.0: fifo:000000:0021:0021:[firefox[19138]] errored - disabling channel dec 14 14:35:29 svarten.tribun kernel: nouveau 0000:07:00.0: Xorg[5231]: channel 33 killed! dec 14 14:37:25 svarten.tribun kernel: sysrq: Keyboard mode set to system default dec 14 14:37:25 svarten.tribun systemd-journald[850]: Journal stopped dec 14 14:37:26 svarten.tribun kernel: sysrq: Terminate All Tasks Web search "SCHED_ERROR 0a [CTXSW_TIMEOUT]", I only found old bugs on nouveau. Anyway... still using same driver as i write this... so seem not frequent.
Created attachment 14215 [details] List of files for kernel-6.5.13-1 Giuseppe, here is the list of files, I let the advisory to you
See also bug 32624 : realtek RTL8125 broke with kernel 6.5.11 Hope the new kernel fixes that. This bug should either be with 'kernel' or 'QA'. Starting with the first until all the update packages are in updates_testing.
Assignee: bugsquad => kernel
I see backport desktop kernel 6.5.13-3, maybe change to test that? Stemming from https://bugs.mageia.org/show_bug.cgi?id=31965#c36 No bug for backport. And linus bug? I run kernel-linus-6.5.13-1 since two days, good :)
(In reply to Morgan Leijström from comment #8) > I see backport desktop kernel 6.5.13-3, maybe change to test that? > Stemming from https://bugs.mageia.org/show_bug.cgi?id=31965#c36 if that works for 8812au it could be worthwhile to have only a 6.5.13-3.mga9 final of 6.5.x. But there isn't yet any feedback. > No bug for backport. > > And linus bug? I run kernel-linus-6.5.13-1 since two days, good :) Not yet opened for kernel-linus bug. Feel free to precede me. I think also the newer kernel-firmware|firmware-nonfree should be bundled with this current.
(In reply to Giuseppe Ghibò from comment #9) > (In reply to Morgan Leijström from comment #8) > > > I see backport desktop kernel 6.5.13-3, maybe change to test that? > > Stemming from https://bugs.mageia.org/show_bug.cgi?id=31965#c36 > > if that works for 8812au it could be worthwhile to have only a 6.5.13-3.mga9 > final of 6.5.x. But there isn't yet any feedback. OK so I am running desktop 6.5.13-3 now to get some mileage, will feedback here in a while. (otherwise unrelated to bug 31965) > Not yet opened for kernel-linus bug. Feel free to precede me. Bug 32628 - Update request: kernel-linus-6.5.13-1.mga9 > I think also the newer kernel-firmware|firmware-nonfree should be bundled > with this current. Used them now for linus and now for desktop 6.5.13-3. Both including also nvidia-current and sddm from testing.
(In reply to Giuseppe Ghibò from comment #9) > I think also the newer kernel-firmware|firmware-nonfree should be bundled > with this current. Sounds sane. Open a bug for them, and make both kernel bugs depend on it? -making sure both kernels are validated before validating it. or can they depend bidirectionally? Maybe more clean to have a oordinating no-packages bug that all depen don, and when that bug is validated all are released. What about the new nvidia-current in testing? (i am using it) (nvidia-newfeature waiting for drakx11 Bug 32579)
Running 6.5.13-*3* OK mga9-64; HW: Intel i7-870, P55 chipset GPU: GTX750Ti -driver: nvidia-current 535.146.02-1 (from testing) Some more from testing: sddm-0.20.0-5, and some firmware: $ rpm -qa | grep firmware alsa-sof-firmware-2.2.5-1.mga9.nonfree kernel-firmware-nonfree-20231111-1.mga9.nonfree kernel-firmware-20231111-1.mga9 ralink-firmware-20231111-1.mga9.nonfree radeon-firmware-20231111-1.mga9.nonfree iwlwifi-firmware-20231111-1.mga9.nonfree rtlwifi-firmware-20231111-1.mga9.nonfree $ uname -a Linux svarten.tribun 6.5.13-desktop-3.mga9 #1 SMP PREEMPT_DYNAMIC Thu Dec 14 14:59:27 UTC 2023 x86_64 GNU/Linux $ dkms status | grep "6.5.13-d" virtualbox, 7.0.12-2.mga9, 6.5.13-desktop-3.mga9, x86_64: installed nvidia-current, 535.146.02-1.mga9.nonfree, 6.5.13-desktop-3.mga9, x86_64: installed § swap, and ext4 / and /home as LVM partitions on a LUKS partition, separate ext4 /boot. SATA SSD. § OK: Plasma, X11 § OK: desktop apps OK - have been using a few hours. § OK: VirtualBox 7.0.12: MSW7 guest with guest additions 7.0.13 OK: internet videos, windows update, dynamic guest window resizing, USB2 flashstick, host folder sharing, bidirectional clipboard, and drag file from Dolphin to Explorer. § OK: freeze on VT switching with nvidia is fixed § As expected: Bug 32541 suspend-resume fail to wake up my monitor (like earlier 6.5 desktop kernels, as opposed to linus 6.5.13 and earlier linus kernels) with mentioned Nvidia drivers
(In reply to Morgan Leijström from comment #12) > § As expected: Bug 32541 suspend-resume fail to wake up my monitor (like > earlier 6.5 desktop kernels, as opposed to linus 6.5.13 and earlier linus > kernels) with mentioned Nvidia drivers That would require another round of testing with multiple kernel building in COPR with half patches removed to find at least the offending one...later next week maybe.
(In reply to Giuseppe Ghibò from comment #13) Lets do that in 32541 when we have time. I just wanted to note it here.
Due to the progress in Bug 31965 - bluetooth Realtek mageia9 does not work ...I have now also tested that kernel from backports_testing too, performing same tests and received same positive result as in Comment 12 above. $ dkms status | grep "6.5.13-desktop-5" virtualbox, 7.0.12-2.mga9, 6.5.13-desktop-5.mga9, x86_64: installed nvidia-current, 535.146.02-1.mga9.nonfree, 6.5.13-desktop-5.mga9, x86_64: installed Hah, while writing this I read in that other bug -6 version coming for this bug in updates_testing.
Blocks: (none) => 31965Summary: Update request: kernel-6.5.13-1.mga9 => Update request: kernel-6.5.13-6.mga9
I have now also tested kernel-desktop-6.5.13-6.mga9 (x86_64), performing same tests and received same positive result as in Comment 12 above. Per Bug 31965 Comment 47 this is final version for this update so other testers please have a go! :)
Packager: time for vbox kmod et al.
Installed and tested without issues. Minimal testing done. Booted this system with the new kernel and all services are working. It is doing home server duties and has lots of server stuff in it with plenty of customization. No issues for now. Will post an update if any issues are found. System: Mageia 9, x86_64, Intel Core i5-4590. # uname -a Linux marte 6.5.13-desktop-6.mga9 #1 SMP PREEMPT_DYNAMIC Sun Dec 17 22:42:25 UTC 2023 x86_64 GNU/Linux # rpm -qa | grep 6.5.13 | sort cpupower-6.5.13-6.mga9 kernel-desktop-6.5.13-6.mga9 kernel-desktop-latest-6.5.13-6.mga9 kernel-userspace-headers-6.5.13-6.mga9 lib64bpf1-6.5.13-6.mga9 perf-6.5.13-6.mga9 # lscpu | grep name Model name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz BIOS Model name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Fill By OEM CPU @ 3.3GHz # hostnamectl Static hostname: marte Icon name: computer-desktop Chassis: desktop 🖥️ Machine ID: 3e3550fbdf6449aa82856685fbd05ad5 Boot ID: 9703b2f61ad9454784d6e68daa419cd9 Operating System: Mageia 9 Kernel: Linux 6.5.13-desktop-6.mga9 Architecture: x86-64 Hardware Vendor: Hewlett-Packard Hardware Model: HP EliteDesk 800 G1 SFF Firmware Version: L01 v02.65 Firmware Date: Mon 2015-07-13 # lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Q87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
CC: (none) => mageia
Continued Test from comment 16: 1) OK: pre-built VirtualBox kernel module virtualbox-kernel-desktop-latest-7.0.12-40.mga9.x86_64 Repeated my usual VB test see comment 12. (in comment 16 it was using dkms built module) 2) OK: nvidia-newfeature 545.29.06-1 from testing. After install quirk see Bug 32579 - switching nvidia driver, next boot fail graphical mode for the kernel that was running comments 5 (install fail) & 6 one workaround
MGA9-64 Plasma on an HP Probook 6550b, i3 350M, Intel graphics, Broadcom wifi. I used katnatek's file list in qarepo with the "fuzzy version" feature activated to get the latest packages, which installed without issues. It was then that I noticed that the pre-built virtualbox kmods weren't on that list, so I went back with qarepo and got those, using the wildcard option. They also installed without issues. I did not go after any firmware updates, fearing that if issues came up when testing them that it would be much more difficult to isolate the cause, be it kernel or firmware. No obvious issues noted after the reboot, with a quick run of VirtualBox, vlc, Dolphin, and Firefox. Housekeeping note: There are still several old unused virtualbox kmods cluttering up the testing repos.
CC: (none) => andrewsfarm
MGA9-64, Mate, Nvidia 1650 Super, Ryzen 2600 The following 7 packages are going to be installed: - cpupower-6.5.13-1.mga9.x86_64 - kernel-desktop-6.5.13-1.mga9.x86_64 - kernel-desktop-devel-6.5.13-1.mga9.x86_64 - kernel-desktop-devel-latest-6.5.13-1.mga9.x86_64 - kernel-desktop-latest-6.5.13-1.mga9.x86_64 - kernel-userspace-headers-6.5.13-1.mga9.x86_64 - lib64bpf1-6.5.13-1.mga9.x86_64 149MB of additional disk space will be used. --- Working as expected - nvidia 535 working - video and audio working - firefox working works for me.
CC: (none) => brtians1
Please test 6.5.13-*6* --- Assigning to QA We need an up to date file list, and Advisory proposal.
Assignee: kernel => qa-bugs
MGA9-64, Xfce, Asus Laptop AMD A6-9225 RADEON R4 RTL8723BE Bluetooth The following 5 packages are going to be installed: - cpupower-6.5.13-6.mga9.x86_64 - kernel-desktop-6.5.13-6.mga9.x86_64 - kernel-desktop-latest-6.5.13-6.mga9.x86_64 - kernel-userspace-headers-6.5.13-6.mga9.x86_64 - lib64bpf1-6.5.13-6.mga9.x86_64 93MB of additional disk space will be used. ---- restarted $ uname -a Linux localhost 6.5.13-desktop-6.mga9 #1 SMP PREEMPT_DYNAMIC Sun Dec 17 22:42:25 UTC 2023 x86_64 GNU/Linux lived with it the last 6 hours wifi works text editor works libreoffice works sound works firefox works suspend works
Created attachment 14227 [details] List of files for kernel-6.5.13-6 Updated list of files for kernel-6.5.13-6.mga9.
Attachment 14215 is obsolete: 0 => 1
(In reply to Thomas Andrews from comment #20) > Housekeeping note: There are still several old unused virtualbox kmods > cluttering up the testing repos. Except for kmods for kernel-6.5.13-1.mga9, I've issued a cleanup request for such debris in sysadmin-discuss@ml some days ago.
(In reply to Giuseppe Ghibò from comment #25) > (In reply to Thomas Andrews from comment #20) > > > Housekeeping note: There are still several old unused virtualbox kmods > > cluttering up the testing repos. > > Except for kmods for kernel-6.5.13-1.mga9, I've issued a cleanup request for > such debris in sysadmin-discuss@ml some days ago. Yes, the sysadmins haven't been as responsive to special requests as usual for the last few days.
I neglected to mention in comment 20 that the dkms-broadcom-wl module built successfully.
Source RPM: (none) => kernel, kmod-virtualbox, kmod-xtables-addonsCC: (none) => marja11
Advisory with SRPMs from attachment 14227 [details] added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"
Keywords: (none) => advisory
MGA9-32 Xfce on Foolishness, my aging Dell Inspiron 5100, P4, Radeon RV200 graphics, using the i686 desktop kernel. No installation issues, and no obvious issues after the reboot.
MGA9-64 Plasma on an i5-2500, Intel graphics, wired Internet. This system has both desktop and server kernels installed, and dkms-rtl8192eu as well. Downloaded all packages with qarepo, and updated both kernels at once. Both rtl8192eu modules were built and installed, and there were no installation issues. I booted into each kernel in turn, and tried this and that, including VirtualBox. There were no obvious issues to report.
(In reply to Giuseppe Ghibò from comment #9) > I think also the newer kernel-firmware|firmware-nonfree should be bundled > with this current. Remider: § We testers should also test with theese (i did) § And there need to be a bug opened for them, incl file list and advisory. Example bug 30749 to look at
Hi all, Mageia 9 Plasma x86_64, AMD processor and graphics. Works fine for the moment. Internet, banks, audio, video, apps, everything I've tried works fine. Greetings!
CC: (none) => joselp
(In reply to Morgan Leijström from comment #31) > (In reply to Giuseppe Ghibò from comment #9) > > I think also the newer kernel-firmware|firmware-nonfree should be bundled > > with this current. > > Remider: > > § We testers should also test with theese (i did) > > § And there need to be a bug opened for them, incl file list and advisory. > Example bug 30749 to look at Not that I anticipate problems (though I think that's a vital part of what QA does), but just to be thorough the firmware should be tested with our current kernel 6.5.11 as well, just in case users for some reason need to drop back to that kernel once this one is pushed.
(In reply to Thomas Andrews from comment #33) > (In reply to Morgan Leijström from comment #31) > > (In reply to Giuseppe Ghibò from comment #9) > > > I think also the newer kernel-firmware|firmware-nonfree should be bundled > > > with this current. > > > > Remider: > > > > § We testers should also test with theese (i did) > > > > § And there need to be a bug opened for them, incl file list and advisory. > > Example bug 30749 to look at > > Not that I anticipate problems (though I think that's a vital part of what > QA does), but just to be thorough the firmware should be tested with our > current kernel 6.5.11 as well, just in case users for some reason need to > drop back to that kernel once this one is pushed. Yep, I forgot also to add to the kernel-firmware to the files list. Thanks for noticing.
What is the kernel firmware package name? Also, in the past we usually posted that as a separate bug for QA to test. This makes testing flexible for validation against prod kernel and also the next version kernel in QA testing. Just a suggestion. Thanks, Brian
I too think firmwares should be separate, like example Bug 30749, because as TJ mentionned they need to work also with our elder kernels, and be installed with backport and linus kernels without needing to install desktop or server kernels. Here is what my system have now - i updated olny what was already installed. $ rpm -qa|grep firmware alsa-sof-firmware-2.2.5-1.mga9.nonfree kernel-firmware-nonfree-20231111-1.mga9.nonfree kernel-firmware-20231111-1.mga9 ralink-firmware-20231111-1.mga9.nonfree radeon-firmware-20231111-1.mga9.nonfree iwlwifi-firmware-20231111-1.mga9.nonfree rtlwifi-firmware-20231111-1.mga9.nonfree
Tested: update firmwares in Real Hardware System: Kernel: 6.5.11-desktop-5.mga9 arch: i686 bits: 32 Desktop: LXQt v: 1.4.0 Distro: Mageia 9 Network: Device-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter driver: ath5k Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too Reboot, not issues with the internet on both cards
firmware real hardware MGA9-64, AMD 3015e APU, laptop WIFI: Intel Wi-Fi 6 AX200 uname -a Linux localhost 6.5.11-desktop-5.mga9 #1 SMP PREEMPT_DYNAMIC Sun Nov 19 01:09:14 UTC 2023 x86_64 GNU/Linux The following 4 packages are going to be installed: - iwlwifi-firmware-20231111-1.mga9.nonfree.noarch - kernel-firmware-20231111-1.mga9.noarch - kernel-firmware-nonfree-20231111-1.mga9.nonfree.noarch - rtlwifi-firmware-20231111-1.mga9.nonfree.noarch 112MB of additional disk space will be used. -- rebooted no issues wifi works, etc.
MGA 9 64 GNOME on Mac Mini Core I5, 16GO RAM. WiFi BCM4331 802.11a/b/g/n with broadcom-wl-common-6.30.223.271-66.mga9.nonfree and dkms-broadcom-wl-6.30.223.271-66.mga9.nonfree drivers Updated with QA repo and RPM's: cpupower 6.5.13 6.mga9 x86_64 kernel-desktop 6.5.13 6.mga9 x86_64 kernel-desktop-devel 6.5.13 6.mga9 x86_64 kernel-userspace-headers 6.5.13 6.mga9 x86_64 lib64bpf1 6.5.13 6.mga9 x86_64 virtualbox-kernel-6.5.13-desk> 7.0.12 40.mga9 x86_64 virtualbox-kernel-desktop-lat> 7.0.12 40.mga9 x86_64 No issues after installation: WiFi Ok, Sound Ok, Bluetooth Ok, Browsing with FF Ok VB with Linux Mint functional
CC: (none) => guillaume.royer
Tested kernel server System: Kernel: 6.5.13-server-6.mga9 arch: i686 bits: 32 Desktop: LXQt v: 1.4.0 Distro: Mageia 9 boot ok wifi ok sound ok integrated webcam ok browse ok
Tested kernel desktop System: Kernel: 6.5.13-desktop-6.mga9 arch: i686 bits: 32 Desktop: LXQt v: 1.4.0 Distro: Mageia 9 boot ok wifi ok sound ok integrated webcam ok browse ok
Crash with kernel-desktop586 https://www.imagebam.com/view/MEQWLFG
(In reply to katnatek from comment #42) > Crash with kernel-desktop586 > https://www.imagebam.com/view/MEQWLFG It seems missed the initrd image. Check it has. Can't reproduce in a VM.
(In reply to Giuseppe Ghibò from comment #43) > (In reply to katnatek from comment #42) > > > Crash with kernel-desktop586 > > https://www.imagebam.com/view/MEQWLFG > > It seems missed the initrd image. Check it has. Can't reproduce in a VM. I will see but i have to downgrade the testing firmware packages to recover my wifi
(In reply to Giuseppe Ghibò from comment #43) > (In reply to katnatek from comment #42) > > > Crash with kernel-desktop586 > > https://www.imagebam.com/view/MEQWLFG > > It seems missed the initrd image. Check it has. Can't reproduce in a VM. After run dracut --regenerate-all -f System: Kernel: 6.5.13-desktop586-6.mga9 arch: i686 bits: 32 Desktop: LXQt v: 1.4.0 Distro: Mageia 9 But not look good, after the crash I lost the wifi and I have to downgrade the testing firmware packages to recover wifi :s
New test, I uninstall all the kernel except desktop, upgrade firmwares and instal kernel-desktop586 and kernel-desktop586-devel, not crash this time and not loss my wifi System: Kernel: 6.5.13-desktop586-6.mga9 arch: i686 bits: 32 Desktop: LXQt v: 1.4.0 Distro: Mageia 9
Whiteboard: (none) => MGA9-32-OK MGA9-64-OK
@Marja the advisory need other src.rpms kernel-firmware-nonfree-20231111-1.mga9.nonfree kernel-firmware-20231111-1.mga9 radeon-firmware-20231111-1.mga9.nonfree
Keywords: advisory => (none)
Or do you want to split kernel-firmwareé2023111-1 from this round?
Source RPM: kernel, kmod-virtualbox, kmod-xtables-addons => kernel, kmod-virtualbox, kmod-xtables-addons,kernel-firmware,kernel-firmware-nonfree,radeon-firmware
(In reply to Morgan Leijström from comment #36) > I too think firmwares should be separate, like example Bug 30749, > because as TJ mentionned they need to work also with our elder kernels, and > be installed with backport and linus kernels without needing to install > desktop or server kernels. > Ok, let's keep kernel-firmware et al. separate from this bug, so to have better tracking. So the files list will remain the current (already attached) one.
(In reply to Giuseppe Ghibò from comment #49) > (In reply to Morgan Leijström from comment #36) > > I too think firmwares should be separate, like example Bug 30749, > > because as TJ mentionned they need to work also with our elder kernels, and > > be installed with backport and linus kernels without needing to install > > desktop or server kernels. > > > > Ok, let's keep kernel-firmware et al. separate from this bug, so to have > better tracking. So the files list will remain the current (already > attached) one. Restoring advisory keyword
Source RPM: kernel, kmod-virtualbox, kmod-xtables-addons,kernel-firmware,kernel-firmware-nonfree,radeon-firmware => kernel, kmod-virtualbox, kmod-xtables-addonsKeywords: (none) => advisory
(In reply to Giuseppe Ghibò from comment #49) > (In reply to Morgan Leijström from comment #36) > > I too think firmwares should be separate, like example Bug 30749, > > because as TJ mentionned they need to work also with our elder kernels, and > > be installed with backport and linus kernels without needing to install > > desktop or server kernels. > > Welllll... If we bundle the firmware with these kernels, that doesn't mean that users will *have* to install desktop or server kernels to get them. Whatever they have installed already will be updated, leaving the rest. What I meant was that we shouldn't bundle too much stuff together for testing purposes, if it's not necessary. If something goes wrong during testing, say a kernel panic, it will be easier to isolate the cause if fewer things were updated at a time. > > Ok, let's keep kernel-firmware et al. separate from this bug, so to have > better tracking. So the files list will remain the current (already > attached) one. I really hate to keep saying this, but that's the way TMB always did it - firmware had its own bug. I'm not saying we should keep doing things the way he did them just because that's the way he did them. But, I'm sure he had his reasons for doing them that way, and we should pay some attention to what those reasons were before changing things too much. Perhaps we can avoid a pitfall or two by doing so.
I am all with you TJ Now the question should we optimally release updates to firmwares at the same time as the kernels (server, desktop, linus), or fefore, or after. And how to set bugs dependencies to do secure that?
(In reply to Morgan Leijström from comment #52) > I am all with you TJ > > Now the question should we optimally release updates to firmwares at the > same time as the kernels (server, desktop, linus), or fefore, or after. > Yes, however the current (old) firmware was out at the period of 6.4.x series, not 6.5.x. Also upèstream are not just adding newer firmware but sometimes some fixes, e.g. fix the position of non-existant path or filename for firmware code. From what I could see it's not bundled with a specific kernel release, only it's updated CI and tagged from time to time on a certain date, generally monthly. Of course there could be cases where it fixes usage on some hw, while could also break some other.
Agreed. I don't think the relative timing is critical, nor do I expect the firmware to work properly with one kernel and not the other. It's just that the remote possibility is there, and it's a relatively easy thing to check. And I know well about a firmware update breaking some hardware but fixing others. About a year after joining QA, shortly after buying my Probook I installed Mageia 5 on it from the CI, and went after the then-many updates. Afterward, the Intel wifi was practically unusable. This was just as the Mageia 5.1 isos were being tested. I filed a bug report, and labeled it a release blocker. Turned out to be the firmware update, something TMB said was his fault without going into details. He soon fixed it, and the bug was closed. I also had a cheap usb wifi dongle for another machine that refused to work with Mageia 3 or 4, so I threw it in a drawer and forgot about it. I think it was Mageia 5.1 or maybe 6 when I dug it back out and tried it again, only to have it now "just work."
mga9-64 OK on my laptop Dell Precision M6300; CPU: Intel(R) Core(TM)2 Duo CPU T7500 GPU: G84GLM [Quadro FX 1600M], using kernel modesetting Wifi: PRO/Wireless 3945ABG [Golan] firmware files updated Plasma X11, desktop apps, Firefox internet video, suspend-resume
mga9-64 OK on laptop Acer Aspire7 A717-71G; Intel EFI, LVM on LUKS on NVMe, i5-7300HQ, using the intel GPU, wifi=QCA6174 firmware files updated Plasma X11, desktop apps, Firefox internet video, suspend-resume
I think it's OK this one at this point, isn't it?
For kernels, firmware, systemd, drivers, etc I really would want more people/systems trying it. System crucial packages all users depend on. Something like twenty different systems, but i know it is not going to happen here. I believe, at least hope, several more QA people and dev use it than those that report here.
MGA9-64 Plasma with an AMD Phenom II X4 910, AMD HD 8490 graphics, ath9 wifi. No installation issues, and it looks OK after the reboot.
Morgan, I think this is as many tests as we are going to get. Sending it on... Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Testing on Fujitsu Lifebook, everything seems to be working as it should. boot ok wifi ok sound ok usb ok webcam integrated and external ok External display ok
MGA9-64, AMD Ryzen 5 2600, Nvidia 1650 super, GNOME, virtualbox host - cpupower-6.5.13-6.mga9.x86_64 - kernel-desktop-devel-6.5.13-6.mga9.x86_64 - kernel-firmware-20231111-1.mga9.noarch - kernel-firmware-nonfree-20231111-1.mga9.nonfree.noarch - kernel-server-6.5.13-6.mga9.x86_64 - kernel-server-devel-6.5.13-6.mga9.x86_64 - kernel-server-devel-latest-6.5.13-6.mga9.x86_64 - kernel-server-latest-6.5.13-6.mga9.x86_64 - kernel-userspace-headers-6.5.13-6.mga9.x86_64 - lib64bpf1-6.5.13-6.mga9.x86_64 rebooted sound working virtualbox working networking is fine works for me
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0153.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
(In reply to Morgan Leijström from comment #11) > (In reply to Giuseppe Ghibò from comment #9) > > I think also the newer kernel-firmware|firmware-nonfree should be bundled > > with this current. > > Sounds sane. Did not happen, so now i opened Bug 32680 - kernel-firmware and kernel-nonfree-firmware and Bug 32679 - nonfree firmware updates