Announcement

Collapse
No announcement yet.

Mesa 19.3.3 Released With Many Fixes

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

  • Mesa 19.3.3 Released With Many Fixes

    Phoronix: Mesa 19.3.3 Released With Many Fixes

    While Mesa 20.0 will be entering its feature freeze this week and branching ahead of the stable release expected in about one month, for now the Mesa 19.3 series is the newest available for stable users...

    http://www.phoronix.com/scan.php?pag...9.3.3-Released

  • #2
    I'm 100% sure this won't fix the VA-API encode hang on AMD.

    Therefore I am not upgrading and staying in Mesa 19.0.






    ...Come on, Mesa developers, get your stuff together already and stop hiding compiler warnings!!

    Comment


    • #3
      Originally posted by tildearrow View Post
      I'm 100% sure this won't fix the VA-API encode hang on AMD.

      Therefore I am not upgrading and staying in Mesa 19.0.






      ...Come on, Mesa developers, get your stuff together already and stop hiding compiler warnings!!
      There are still other radeonSI benefits. Why not upgrade?

      Comment


      • #4
        Will there be OpenCL 1 2 or 2.0 support with Mesa? Rocm doesn't support integrated and GPUs (APU)

        Comment


        • #5
          Originally posted by schmidtbag View Post

          There are still other radeonSI benefits. Why not upgrade?
          "other benefits". Yeah, at the cost of losing the ability to record the screen (by grabbing the output plane and encoding it with VA-API, ReLive/ShadowPlay-style).
          I mean, this is what happens. After starting darmstadt under Mesa 19.3, I can only record a few seconds before it collapses and the card freaking hangs and the core clock is set to maximum.

          Look here.

          Code:
          [ 9583.901220] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901222] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101605000 from 27
          [ 9583.901223] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901226] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901227] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101601000 from 27
          [ 9583.901228] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901231] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901232] amdgpu 0000:03:00.0:   in page starting at address 0x000080010160a000 from 27
          [ 9583.901233] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901236] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901237] amdgpu 0000:03:00.0:   in page starting at address 0x000080010160d000 from 27
          [ 9583.901237] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901240] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901241] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101602000 from 27
          [ 9583.901242] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901245] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901246] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101606000 from 27
          [ 9583.901246] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901249] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901250] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101609000 from 27
          [ 9583.901251] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901254] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901254] amdgpu 0000:03:00.0:   in page starting at address 0x000080010160d000 from 27
          [ 9583.901255] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901258] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901259] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101609000 from 27
          [ 9583.901259] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.901262] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
          [ 9583.901263] amdgpu 0000:03:00.0:   in page starting at address 0x0000800101606000 from 27
          [ 9583.901264] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
          [ 9583.904682] amdgpu 0000:03:00.0: IH ring buffer overflow (0x00088720, 0x00006B40, 0x00008740)
          [ 9594.042405] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1698489, emitted seq=1698491
          [ 9594.042444] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process darmstadt pid 53316 thread darmstadt:cs0 pid 53322
          [ 9594.042446] amdgpu 0000:03:00.0: GPU reset begin!
          [ 9604.059082] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
          Like what in the world with those stupid page faults?! How in the heck did it break like that since Mesa 19.1?! Where did the quality control team go? Are they still in vacation or something?...

          I mean this is really disappointing to see. What. in. the. world. causes the thing to COLLAPSE in this version?!
          My stability timeline with this card has been a disgrace at times. I could spend a whole day ranting about this...

          And here is proof:

          Code:
          System:    Host: linux Kernel: 5.0.2-arch1-1-ARCH x86_64 bits: 64 Desktop: KDE Plasma 5.17.5  
                    Distro: Arch Linux  
          Machine:   Type: Desktop Mobo: MSI model: Z170A GAMING PRO (MS-7984) v: 1.0 serial: <root required>  
                    UEFI: American Megatrends v: 1.D0 date: 12/22/2016  
          CPU:       Quad Core: Intel Core i7-6700K type: MT MCP speed: 4000 MHz min/max: 800/4001 MHz  
          Graphics:  Device-1: Intel HD Graphics 530 driver: i915 v: kernel  
                    Device-2: Advanced Micro Devices [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition]  
                    driver: amdgpu v: kernel  
                    Device-3: NVIDIA GP107 [GeForce GTX 1050 3GB] driver: nvidia v: 440.44  
                    Display: x11 server: X.Org 1.20.7 driver: amdgpu resolution: 3840x2160~60Hz  
                    OpenGL: renderer: Radeon Vega Frontier Edition (VEGA10 DRM 3.27.0 5.0.2-arch1-1-ARCH LLVM 9.0.1)  
                    v: 4.5 Mesa 19.3.2  
          Network:   Device-1: Intel Ethernet I219-V driver: e1000e  
          Drives:    Local Storage: total: 7.28 TiB used: 1.50 TiB (20.6%)  
          Info:      Processes: 299 Uptime: 31m Memory: 15.59 GiB used: 2.27 GiB (14.6%) Shell: bash inxi: 3.0.26
          Last edited by tildearrow; 01-28-2020, 05:30 PM.

          Comment


          • #6
            Originally posted by tildearrow View Post

            "other benefits". Yeah, at the cost of losing the ability to record the screen (by grabbing the output plane and encoding it with VA-API, ReLive/ShadowPlay-style).
            I mean, this is what happens. After starting darmstadt under Mesa 19.3, I can only record a few seconds before it collapses and the card freaking hangs and the core clock is set to maximum.

            Look here.

            Code:
            [ 9583.901220] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901222] amdgpu 0000:03:00.0: in page starting at address 0x0000800101605000 from 27
            [ 9583.901223] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901226] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901227] amdgpu 0000:03:00.0: in page starting at address 0x0000800101601000 from 27
            [ 9583.901228] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901231] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901232] amdgpu 0000:03:00.0: in page starting at address 0x000080010160a000 from 27
            [ 9583.901233] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901236] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901237] amdgpu 0000:03:00.0: in page starting at address 0x000080010160d000 from 27
            [ 9583.901237] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901240] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901241] amdgpu 0000:03:00.0: in page starting at address 0x0000800101602000 from 27
            [ 9583.901242] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901245] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901246] amdgpu 0000:03:00.0: in page starting at address 0x0000800101606000 from 27
            [ 9583.901246] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901249] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901250] amdgpu 0000:03:00.0: in page starting at address 0x0000800101609000 from 27
            [ 9583.901251] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901254] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901254] amdgpu 0000:03:00.0: in page starting at address 0x000080010160d000 from 27
            [ 9583.901255] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901258] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901259] amdgpu 0000:03:00.0: in page starting at address 0x0000800101609000 from 27
            [ 9583.901259] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.901262] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
            [ 9583.901263] amdgpu 0000:03:00.0: in page starting at address 0x0000800101606000 from 27
            [ 9583.901264] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
            [ 9583.904682] amdgpu 0000:03:00.0: IH ring buffer overflow (0x00088720, 0x00006B40, 0x00008740)
            [ 9594.042405] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1698489, emitted seq=1698491
            [ 9594.042444] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process darmstadt pid 53316 thread darmstadt:cs0 pid 53322
            [ 9594.042446] amdgpu 0000:03:00.0: GPU reset begin!
            [ 9604.059082] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
            Like what in the world with those stupid page faults?! How in the heck did it break like that since Mesa 19.1?! Where did the quality control team go? Are they still in vacation or something?...

            I mean this is really disappointing to see. What. in. the. world. causes the thing to COLLAPSE in this version?!
            My stability timeline with this card has been a disgrace at times. I could spend a whole day ranting about this...

            And here is proof:

            Code:
            System: Host: linux Kernel: 5.0.2-arch1-1-ARCH x86_64 bits: 64 Desktop: KDE Plasma 5.17.5
            Distro: Arch Linux
            Machine: Type: Desktop Mobo: MSI model: Z170A GAMING PRO (MS-7984) v: 1.0 serial: <root required>
            UEFI: American Megatrends v: 1.D0 date: 12/22/2016
            CPU: Quad Core: Intel Core i7-6700K type: MT MCP speed: 4000 MHz min/max: 800/4001 MHz
            Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel
            Device-2: Advanced Micro Devices [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition]
            driver: amdgpu v: kernel
            Device-3: NVIDIA GP107 [GeForce GTX 1050 3GB] driver: nvidia v: 440.44
            Display: x11 server: X.Org 1.20.7 driver: amdgpu resolution: 3840x2160~60Hz
            OpenGL: renderer: Radeon Vega Frontier Edition (VEGA10 DRM 3.27.0 5.0.2-arch1-1-ARCH LLVM 9.0.1)
            v: 4.5 Mesa 19.3.2
            Network: Device-1: Intel Ethernet I219-V driver: e1000e
            Drives: Local Storage: total: 7.28 TiB used: 1.50 TiB (20.6%)
            Info: Processes: 299 Uptime: 31m Memory: 15.59 GiB used: 2.27 GiB (14.6%) Shell: bash inxi: 3.0.26
            Why for the love of Linus Tovalds are You still using Linux kernel version 5.0.2 ?

            Comment


            • #7
              Originally posted by tildearrow View Post

              "other benefits". Yeah, at the cost of losing the ability to record the screen (by grabbing the output plane and encoding it with VA-API, ReLive/ShadowPlay-style).
              I mean, this is what happens. After starting darmstadt under Mesa 19.3, I can only record a few seconds before it collapses and the card freaking hangs and the core clock is set to maximum.

              Look here.

              Code:
              [ 9583.901220] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901222] amdgpu 0000:03:00.0: in page starting at address 0x0000800101605000 from 27
              [ 9583.901223] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901226] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901227] amdgpu 0000:03:00.0: in page starting at address 0x0000800101601000 from 27
              [ 9583.901228] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901231] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901232] amdgpu 0000:03:00.0: in page starting at address 0x000080010160a000 from 27
              [ 9583.901233] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901236] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901237] amdgpu 0000:03:00.0: in page starting at address 0x000080010160d000 from 27
              [ 9583.901237] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901240] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901241] amdgpu 0000:03:00.0: in page starting at address 0x0000800101602000 from 27
              [ 9583.901242] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901245] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901246] amdgpu 0000:03:00.0: in page starting at address 0x0000800101606000 from 27
              [ 9583.901246] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901249] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901250] amdgpu 0000:03:00.0: in page starting at address 0x0000800101609000 from 27
              [ 9583.901251] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901254] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901254] amdgpu 0000:03:00.0: in page starting at address 0x000080010160d000 from 27
              [ 9583.901255] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901258] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901259] amdgpu 0000:03:00.0: in page starting at address 0x0000800101609000 from 27
              [ 9583.901259] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.901262] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:154 vmid:3 pasid:32776, for process darmstadt pid 53316 thread darmstadt:cs0 pid 53322)
              [ 9583.901263] amdgpu 0000:03:00.0: in page starting at address 0x0000800101606000 from 27
              [ 9583.901264] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301135
              [ 9583.904682] amdgpu 0000:03:00.0: IH ring buffer overflow (0x00088720, 0x00006B40, 0x00008740)
              [ 9594.042405] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1698489, emitted seq=1698491
              [ 9594.042444] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process darmstadt pid 53316 thread darmstadt:cs0 pid 53322
              [ 9594.042446] amdgpu 0000:03:00.0: GPU reset begin!
              [ 9604.059082] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
              Like what in the world with those stupid page faults?! How in the heck did it break like that since Mesa 19.1?! Where did the quality control team go? Are they still in vacation or something?...

              I mean this is really disappointing to see. What. in. the. world. causes the thing to COLLAPSE in this version?!
              My stability timeline with this card has been a disgrace at times. I could spend a whole day ranting about this...

              And here is proof:

              Code:
              System: Host: linux Kernel: 5.0.2-arch1-1-ARCH x86_64 bits: 64 Desktop: KDE Plasma 5.17.5
              Distro: Arch Linux
              Machine: Type: Desktop Mobo: MSI model: Z170A GAMING PRO (MS-7984) v: 1.0 serial: <root required>
              UEFI: American Megatrends v: 1.D0 date: 12/22/2016
              CPU: Quad Core: Intel Core i7-6700K type: MT MCP speed: 4000 MHz min/max: 800/4001 MHz
              Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel
              Device-2: Advanced Micro Devices [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition]
              driver: amdgpu v: kernel
              Device-3: NVIDIA GP107 [GeForce GTX 1050 3GB] driver: nvidia v: 440.44
              Display: x11 server: X.Org 1.20.7 driver: amdgpu resolution: 3840x2160~60Hz
              OpenGL: renderer: Radeon Vega Frontier Edition (VEGA10 DRM 3.27.0 5.0.2-arch1-1-ARCH LLVM 9.0.1)
              v: 4.5 Mesa 19.3.2
              Network: Device-1: Intel Ethernet I219-V driver: e1000e
              Drives: Local Storage: total: 7.28 TiB used: 1.50 TiB (20.6%)
              Info: Processes: 299 Uptime: 31m Memory: 15.59 GiB used: 2.27 GiB (14.6%) Shell: bash inxi: 3.0.26
              Have you tried the AMD Radeon Software for Linux package (the amdgpu-open)?
              I suggest you either use that or update your amdgpu kernel driver...
              Would be interested in outcome of those

              Comment


              • #8
                Typo:

                Originally posted by tildearrow View Post

                Are they still in vacation or something?...
                *hides away*

                Comment


                • #9
                  I need to see this on Fedora 31 for my 5500 Navi card. To lazy to build everything myself so I wait for Fedora to make a move.

                  as for my laptop I think it has finally died. Between Apple and HP I’m pretty burnt out with respect to the quality of laptop hardware. The Lenovo’s at work don’t impress either. Needless to say I’m not in a rush to buy new laptop hardware.

                  Comment


                  • #10
                    Originally posted by Linuxxx View Post

                    Why for the love of Linus Tovalds are You still using Linux kernel version 5.0.2 ?
                    Stability issues with a later point version of 5.0.
                    I had to fsck my drive due to corruption in 5.0.6 if I remember.

                    I just was scared to upgrade... but now I am using 5.4. The hang still reproduces though :l

                    Comment

                    Working...
                    X