Announcement

Collapse
No announcement yet.

Linux 6.11 Kernel Released With Some Snapdragon X1 Laptop Support & Other New Hardware

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Linux 6.11 Kernel Released With Some Snapdragon X1 Laptop Support & Other New Hardware

    Phoronix: Linux 6.11 Kernel Released With Some Snapdragon X1 Laptop Support & Other New Hardware

    As expected the Linux 6.11 kernel has been promoted to stable and in time for appearing in the likes of Ubuntu 24.10, Fedora 41, and other autumn Linux distribution releases...

    Linux 6.11 Kernel Released With Some Snapdragon X1 Laptop Support & Other New Hardware - Phoronix
    https://www.phoronix.com/news/Linux-6.11
    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
    Tags: None
  • #2
    Those who hate ACPI must buy Qualcomm laptops, it's their salvation. Praise Qualcomm! Praise Snapdragon! Praise DeviceTree!
    • Likes 4

    Comment

    • #3
      I was wondering, why doesn't Snapdragon 865 have support, I kinda remember that they do in the kernel but no linux on samsung phones or phones running older snapdragons yet.

      Comment

      • #4
        There is time for 6.12 to be LTS.
        • Likes 1

        Comment

        • #5
          6.11 running fine on FC40 for me.
          • Likes 1

          Comment

          • #6
            Cool, nvidia 560.35.03 driver didn't break with 6.11
            • Likes 2

            Comment

            • #7
              Originally posted by Eriks View Post
              Cool, nvidia 560.35.03 driver didn't break with 6.11
              Yeah, because they were already broken with 6.10:

              Multiple kernel oopses before suspending caused by nvidia-sleep.sh, Linux 6.10 regression? WARNING: CPU: PID: at include/linux/rwsem.h:80 follow_pte
              https://forums.developer.nvidia.com/t/multiple-kernel-oopses-before-suspending-caused-by-nvidia-sleep-sh-linux-6-10-regression-warning-cpu-pid-at-include-linux-rwsem-h-80-follow-pte/303669
              System: Fedora 40 Linux 6.10.4 vanilla ASUS X570 motherboard 64GB of RAM, no swap RTX 4070S XFCE4/Xorg options nvidia-drm modeset=1 NVIDIA 555.58.02, closed source drivers I’ve never seen this before but then I only used Linux kernel 6.9 with this GPU. Right before suspending I get this: ------------[ cut here ]------------ WARNING: CPU: 11 PID: 61283 at include/linux/rwsem.h:80 follow_pte+0xf8/0x120 Modules linked in: rfcomm snd_hrtimer nvidia_uvm(PO) tun cmac algif_hash algif_skcipher af_al...


              This bug was reported to NVIDIA at least two months ago and they still haven't fixed it. I'm kinda disappointed. Don't mind the "closed" source drivers in the topic, I'm now running the open driver and it's equally affected.

              The issue is not just multiple oopses on suspend, for many people the system enters an unstable state after resume.
              Last edited by avis; 16 September 2024, 04:09 AM.
              • Likes 1

              Comment

              • #8
                Originally posted by mrg666 View Post
                6.11 running fine on FC40 for me.
                same here, but since I only have quite boring and old hardware, there's actually no visible benefits against the good old 6.6 I usually run.
                Last edited by cynic; 16 September 2024, 09:03 AM. Reason: edit: added "visible"
                • Likes 1

                Comment

                • #9
                  Originally posted by cynic View Post

                  same here, but since I only have quite boring and old hardware, there's actually no visible benefits against the good old 6.6 I usually run.
                  I agree, 6.11 release is not that different unless there is the latest AMD hardware or X1 Snapdragon which I don't have either. Nevertheless, I am running it on all devices I have now just fine.

                  Comment

                  Previous template Next
                  Working...
                  X