With today's sync, we are delivering the latest in the 5.11 series (at least as of today), which is 5.11.6. With the 5.11 series, I've performed the following enablement in our config for new device and feature support:

  • Enabled Intel Software Guard Extensions (SGX)
  • Enabled XFM protocol support for 802.1Q support
  • Enabled CONFIG_DM_MULTIPATH_IOA. For more details, see https://cateee.net/lkddb/web-lkddb/DM_MULTIPATH_IOA.html and https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-multipath.html (note, SUSE's documentation should really only be read up to the end of the "Understanding Multipath I/O" section, the rest is primarily related to SLES)
  • Enabled RTL8153 ECM support
  • Enabled Intel Alderlake, Elkhart Lake, and Lakefield PINCTRL
  • Enabled Corsair PSU sensor support
  • Enabled more sound ALSA SoCs
  • Enabled AMD Sensor Fusion Hub HID and power management controller (CONFIG_AMD_PMC) support
  • Enabled Intel integrated memory controller error detection and correction via CONFIG_EDAC_IGEN6
  • Improved WIMAX support
  • Improved Microsoft Surface support
  • Enabled CIPS SWN (Service Witness Protocol) support

If you have any serious regressions with 5.11 compared to 5.10 series, I encourage you to post here. If you are uncertain, I ask that instead of immediately commenting, you follow our documentation linked below to check 5.10 (if possible, depending on your use of proprietary drivers) and perform more testing.

https://getsol.us/articles/troubleshooting/general-troubleshooting/en/#boot-into-previous-kernel

Keep the noise to a minimum and please refrain from "me too" comments on other people's remarks.

Thanks!

How do I delete the old ones?

When I clr-boot-manager update, I receive an error saying no space left on the device.

'No irq handler' and system doesn't starting. System with old kernel showed me this message, but with boot I hasn't any problem.

Update: with older kernel I hasn't this this problem

If you have any idea please wrote me on this topic

    When the screen is locked and I press a key to woke up the system crash (also keyboard doesn't respond), it is the same with the older kernel. I have an amd graphics card, I read that amdgpu has problems in that regard.

    I updated and rebooted the system right afterwards. It hung on reboot, so I had to power it off manually and start it again. Not noticing any other problems now.

    Josh, if this gets too long and you think it better for me to start an independent thread, please let me know.

    AMD Ryzen 5 4650G (integrated graphics) - ASRock A520m-itz/ac board - After running sudo eopkg up and rebooting:

    Expected: Prompted for LUKS passphrase. It shows on a single screen as B&W, flickers, and then shows B&W on both screens.
    Unexpected: Prompted for LUKS passphrase. It shows on single screen as B&W, flickers, and then I had a lovely green background on both screen and the text became very difficult to read. This carried on through to my desktop including flipping to TTY. Also happened with only one monitor connected.

    I have full logs from dmesg and journalctl for both instances and can provide them if that would be helpful. Unfortunately, I don't know enough to pin down what might be the actual culprit. I did notice this error/line on the "green" log as one difference: amdgpu 0000:08:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR - According to this issue the "message is harmless".

    Anyway, 5.10 still works fine, but you asked for feedback.

    Gentlemen, Upgrade to 5.11 is unsuccessful. Laptop failed to boot getting blank screen. Set-kernel back to 5.10 reboot laptop. If any guidance let us know. Thanks

    The only thing I noticed is that my graphic card is running hotter. From 36c idle now 46-48c.
    I don't if it has to do with the update but that could be the case. Thanks

    • [deleted]

    • Post #10

    All good here. RX 580 and Ivy Bridge i7.

    did something change with schedutil? it behaves like ondemand now, both in terms of temepratures and frequencies. it never goes below 3.9 ghz now for the highest freq core

    no biggie, but definite change

    Everything working perfectly.Dell optiplex 390.Thank you.

    Everything worked fine here, for about 10 machines and spare SSDs updated. Eopkg only needed to be restarted once, and it's possible that was just because I misjudged how long it would take for one of the upgrades. If I'd been more patient, the score might have been 100%.

    No complaints on this end either. Update went flawless, as usual, on my Intel NUC.

    Sucess on my Lenovo S340 laptop with Ryzen 3500u processor.

    fresh install Solus Plasma everything seems "gucci" atm will reply again if anything happens

    🙂 Kernel 5.11.6-174.current is working fine with my VAIO.

    For those of you having issues, it would be appreciated if you would provide information about your hardware. I appreciate you saying you have issues, but I can't even start investigating it without knowing your hardware, let alone having logs from the likes of systemd (boot into 5.11, let it fail, boot back into 5.10, do sudo journalctl --boot=-1 > boot-log then put the log on pastebin).

    Thanks @Leandros_Adigard, will take a look. Your possible issue here maybe, can cook a build next week for you to test.

      After the updates I have a permission problem with my samba share. The share is mounted via fstab:

      # Openwrt Transfer
      //192.168.3.2/transfer /mnt/transfer cifs guest,uid=1000,_netdev,noauto,x-systemd.automount,user,vers=1.0 0 0

      After the update the permissons of user shown in dolphin is "65534", group is "nobody".
      So, I'm unable to create or copy anything on the share.
      I rollback the updates and everythings fine again.

      But, I don't know, if this is a problem with the kernel or an other update.