Announcement

Collapse
No announcement yet.

Linux 4.21 Is Going To Be A Big Release To Jump-Start The New Year

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 4.21 Is Going To Be A Big Release To Jump-Start The New Year

    Phoronix: Linux 4.21 Is Going To Be A Big Release To Jump-Start The New Year

    While Linux 4.20 isn't even expected for release until Sunday, which itself is is delivering many new features and hardware support, the Linux 4.21 release is another big one that will start off the new year...

    http://www.phoronix.com/scan.php?pag...ump-Start-2019

  • #2
    Typo:

    Originally posted by phoronix View Post

    Comment


    • #3
      high fps and now FreeSync for the desktop \o/ bye bye eye strain.

      Comment


      • #4
        Can't wait to see FreeSync working in mainline :-) This is nice! Hope wayland support is around the corner as well and it is not only limited to x11.

        Comment


        • #5
          Strange. No "4.21/5.0" version? Perhaps they will name it 5.0 after all... :P

          Comment


          • #6
            IOW, Freesync and video module updates ( drm stuff, I presume) for AMD and Intel camp, few similar driver updates for ARM crowd, and that's more or less, it...


            Comment


            • #7
              I was finally able to get some crash logs with the latest 4.20-rc7 and AMD WIP kernel from git, and filed a bug report with Xorg logs from a good boot with the last working kernel (4.18.20) and a crash boot log with 4.20-rc7. I also offered to compile any other post 4.18.20 kernels and add those logs as well.

              I was able to whittle down the R9 390 problem to DPM and DC, as amdgpu works without them, sans resuming from suspend and other control issues.

              For example, this grub line works with good kernels (4.18.20 and earlier):
              radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.modeset=1 amdgpu.dpm=1 amdgpu.dc=1

              But with anything after 4.18.20 you have to use the following, leaving out any mention of modeset/dpm/dc, to get any amdgpu functionality at all. Even setting them to 0 doesn't work, you have to not include them at all:
              radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1

              By the way, that last short grub line also works with 4.20.18 but DPM and DC seem to be automatically enabled. It seems that with later kernels it's automatically disabled though.

              And here's the relevant excerpt from the failed boot log (using early KMS doesn't change anything by the way):

              [ 5.559] (II) LoadModule: "glx"
              [ 5.560] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
              [ 5.562] (II) Module glx: vendor="X.Org Foundation"
              [ 5.562] compiled for 1.20.3, module version = 1.0.0
              [ 5.562] ABI class: X.Org Server Extension, version 10.0
              [ 5.562] (II) LoadModule: "amdgpu"
              [ 5.562] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
              [ 5.563] (II) Module amdgpu: vendor="X.Org Foundation"
              [ 5.563] compiled for 1.20.1, module version = 18.1.0
              [ 5.563] Module class: X.Org Video Driver
              [ 5.563] ABI class: X.Org Video Driver, version 24.0
              [ 5.563] (II) AMDGPU: Driver for AMD Radeon:
              All GPUs supported by the amdgpu kernel driver
              [ 5.563] (II) AMDGPU(0): [KMS] drm report modesetting isn't supported.
              [ 5.563] (EE) Screen 0 deleted because of no matching config section.
              [ 5.563] (II) UnloadModule: "amdgpu"
              [ 5.563] (EE) Device(s) detected, but none match those in the config file.

              Good boot logs look the same up until the surprising "AMDGPU(0): [KMS] drm report modesetting isn't supported." message.

              Comment

              Working...
              X