Announcement

Collapse
No announcement yet.

Linux 5.0-rc1 Debuts With New Hardware Support, FreeSync, I3C, High-Res Scrolling

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

  • Linux 5.0-rc1 Debuts With New Hardware Support, FreeSync, I3C, High-Res Scrolling

    Phoronix: Linux 5.0-rc1 Debuts With New Hardware Support, FreeSync, I3C, High-Res Scrolling

    Linus Torvalds ended the Linux 4.21 merge window on Sunday evening and decided to go ahead and rename it to Linux 5.0. Linux 5.0-rc1 is now available to begin the testing process for this next kernel release that will officially debut around the end of February or early March...

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

  • #2
    My reason is Linus is a Speed Racer fan from the 70's thus Linux 5

    Comment


    • #3
      So, no 'Give me Five' codename... dissapointed

      Comment


      • #4
        I like how MAME versiong going, they are after 22 years just at 0.205 version currently, which gives them a century to reach version 1.0 These also does not have stable ABI, so break people ROMs often - same like with Linux

        As of version 0.204 they could emulate even X Window System terminal emulators

        But Linus is predictable, in year 2011. he bump 3.0 for not particular reason, then in year 2015. again to 4.0 and now in 2019. we got 5.0... so on 4 years on average numbers get boring it seems
        Last edited by dungeon; 01-06-2019, 11:18 PM.

        Comment


        • #5
          The kernel 5.0-rc1 has support fort the Astrometa DVB-T2 usb stick with the Sony demodulator. The kernel works but I have these errors at boot:
          Code:
          [    1.910264] WARNING: CPU: 8 PID: 1253 at drivers/pci/msi.c:1269 pci_irq_get_a
          ffinity+0x36/0x80
          [    1.910265] Modules linked in: realtek r8169 xhci_pci nvme xhci_hcd nvme_core
          [    1.910269] CPU: 8 PID: 1253 Comm: kworker/u32:7 Not tainted 5.0.0-rc1 #1
          [    1.910270] Hardware name: System manufacturer System Product Name/PRIME B350
          M-K, BIOS 4207 12/07/2018
          [    1.910274] Workqueue: nvme-reset-wq nvme_reset_work [nvme]
          [    1.910276] RIP: 0010:pci_irq_get_affinity+0x36/0x80
          [    1.910277] Code: 48 8b 87 88 02 00 00 48 81 c7 88 02 00 00 48 39 c7 74 17 85
           f6 74 4e 31 d2 eb 04 39 d6 74 46 48 8b 00 83 c2 01 48 39 f8 75 f1 <0f> 0b 31 c0
           c3 83 e2 02 48 c7 c0 28 d6 29 82 74 29 48 8b 97 88 02
          [    1.910278] RSP: 0018:ffffc90001f0fcf8 EFLAGS: 00010246
          [    1.910279] RAX: ffff88821444a288 RBX: 000000000000000f RCX: 0000000000000040
          [    1.910279] RDX: 0000000000000010 RSI: 0000000000000010 RDI: ffff88821444a288
          [    1.910280] RBP: ffff888214e3d240 R08: ffff888216c22400 R09: ffff8882151bbd80
          [    1.910280] R10: ffffc90001f0fc28 R11: ffffffff82239108 R12: 0000000000000001
          [    1.910281] R13: ffff88821444a000 R14: 00000000ffffffff R15: ffff888214d29008
          [    1.910281] FS:  0000000000000000(0000) GS:ffff888216c00000(0000) knlGS:00000
          00000000000
          [    1.910282] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
          [    1.910283] CR2: 00007fb3f4602441 CR3: 000000000220e000 CR4: 00000000003406e0
          [    1.910283] Call Trace:
          [    1.910286]  blk_mq_pci_map_queues+0x32/0xc0
          [    1.910289]  nvme_pci_map_queues+0x7b/0xb0 [nvme]
          [    1.910292]  blk_mq_alloc_tag_set+0x113/0x2c0
          [    1.910294]  nvme_reset_work+0xfb5/0x161a [nvme]
          [    1.910297]  process_one_work+0x1c9/0x350
          [    1.910298]  worker_thread+0x210/0x3c0
          [    1.910299]  ? rescuer_thread+0x320/0x320
          [    1.910300]  kthread+0x106/0x120
          [    1.910302]  ? kthread_create_on_node+0x60/0x60
          [    1.910304]  ret_from_fork+0x1f/0x30
          [    1.910306] ---[ end trace 949afdd8dfbbc0cf ]---
          [    1.910311] WARNING: CPU: 8 PID: 1253 at block/blk-mq-pci.c:52 blk_mq_pci_map
          _queues+0xb9/0xc0
          [    1.910311] Modules linked in: realtek r8169 xhci_pci nvme xhci_hcd nvme_core
          [    1.910313] CPU: 8 PID: 1253 Comm: kworker/u32:7 Tainted: G        W         
          5.0.0-rc1 #1
          [    1.910314] Hardware name: System manufacturer System Product Name/PRIME B350
          M-K, BIOS 4207 12/07/2018
          [    1.910316] Workqueue: nvme-reset-wq nvme_reset_work [nvme]
          [    1.910318] RIP: 0010:blk_mq_pci_map_queues+0xb9/0xc0
          [    1.910319] Code: d0 c7 04 91 00 00 00 00 48 89 de 89 c7 e8 5f e3 46 00 3b 05
           4d d6 fb 00 72 e1 5b 31 c0 5d 41 5c 41 5d 41 5e 41 5f c3 31 c0 c3 <0f> 0b eb c4
           90 90 90 41 57 49 89 ff 41 56 41 55 41 54 55 53 48 8b
          [    1.910319] RSP: 0018:ffffc90001f0fd00 EFLAGS: 00010216
          [    1.910320] RAX: 00000000ffffffff RBX: 000000000000000f RCX: 0000000000000040
          [    1.910320] RDX: 0000000000000010 RSI: 0000000000000010 RDI: ffff88821444a288
          [    1.910321] RBP: 0000000000000000 R08: ffff888216c22400 R09: ffff8882151bbd80
          [    1.910321] R10: ffffc90001f0fc28 R11: ffffffff82239108 R12: 0000000000000001
          [    1.910321] R13: ffff88821444a000 R14: 00000000ffffffff R15: ffff888214d29008
          [    1.910322] FS:  0000000000000000(0000) GS:ffff888216c00000(0000) knlGS:00000
          00000000000
          [    1.910323] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
          [    1.910323] CR2: 00007fb3f4602441 CR3: 000000000220e000 CR4: 00000000003406e0
          [    1.910323] Call Trace:
          [    1.910326]  nvme_pci_map_queues+0x7b/0xb0 [nvme]
          [    1.910327]  blk_mq_alloc_tag_set+0x113/0x2c0
          [    1.910329]  nvme_reset_work+0xfb5/0x161a [nvme]
          [    1.910331]  process_one_work+0x1c9/0x350
          [    1.910331]  worker_thread+0x210/0x3c0
          [    1.910332]  ? rescuer_thread+0x320/0x320
          [    1.910333]  kthread+0x106/0x120
          [    1.910335]  ? kthread_create_on_node+0x60/0x60
          [    1.910336]  ret_from_fork+0x1f/0x30
          [    1.910337] ---[ end trace 949afdd8dfbbc0d0 ]---
          Code:
          System:
            Host: ryzenpc Kernel: 5.0.0-rc1 x86_64 bits: 64 Desktop: Xfce 4.12.4 
            Distro: Debian GNU/Linux buster/sid 
          Machine:
            Type: Desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x 
            serial: <root required> UEFI [Legacy]: American Megatrends v: 4207 
            date: 12/07/2018 
          CPU:
            6-Core: AMD Ryzen 5 1600 type: MT MCP speed: 2965 MHz 
          Graphics:
            Device-1: AMD Ellesmere [Radeon RX 470/480] driver: amdgpu v: kernel 
            Display: x11 server: X.Org 1.20.3 driver: amdgpu 
            resolution: 3840x2160~60Hz 
            OpenGL: 
            renderer: Radeon RX 570 Series (POLARIS10 DRM 3.27.0 5.0.0-rc1 LLVM 7.0.1) 
            v: 4.5 Mesa 19.0.0-devel (git-70be9af 2019-01-02 cosmic-oibaf-ppa)

          Comment


          • #6
            Originally posted by debianxfce View Post
            The kernel works but I have these errors at boot:
            These NVMes seems keep breaking Now go and install amdgpu-wip which would be rebased on this rc

            BTW, your definition of "works" is weird
            Last edited by dungeon; 01-06-2019, 11:58 PM.

            Comment


            • #7
              Originally posted by dungeon View Post

              These NVMes seems keep breaking Now go and install amdgpu-wip which would be rebased on this rc

              BTW, your definition of "works" is weird
              I lol'd. BTW, I already have a pretty good reason not to run the current 4.21/5.0 kernels atm https://bugs.freedesktop.org/show_bug.cgi?id=109234
              Freesync is tempting but also far from production-ready, when it works its sometimes stuttery and flashes blank screens very often, I remember the earlier implementations worked way better.

              Comment


              • #8
                Originally posted by clapbr View Post

                I lol'd. BTW, I already have a pretty good reason not to run the current 4.21/5.0 kernels atm https://bugs.freedesktop.org/show_bug.cgi?id=109234
                Well in you case, you should. As you have fairly new B450 chipset and remember to keep BIOS version up to date there

                There is Version 0604 available and you have 0601:

                https://www.asus.com/us/Motherboards...Desk_Download/

                Now, that mention "Improve compatibility and performance for Athlon™ with Radeon™ Vega Graphics Processors" and you don't have APU there, but you never know as these blobie guys have tendency to never write proper changelogs

                Comment


                • #9
                  Originally posted by dungeon View Post
                  Well in you case, you should. As you have fairly new B450 chipset and remember to keep BIOS version up to date there
                  I strongly disagree. If your current BIOS works fine then it's fine and you should keep it. If you want to disagree then that's fine, upgrade your BIOS and find that you can't boot your machine anymore: https://bugzilla.redhat.com/show_bug.cgi?id=1608242

                  Yes, this happened to me. Current kernels don't hang at boot with the latest AMD BIOSes but things like older LiveUSB/LiveCDs and some distros using older kernels still do. Then there's the matter of suspend to RAM breaking on the latest BIOS on some Gigabyte motherboards...

                  If it's broken, then sure, go ahead and fix it. But don't break it by "fixing it" when it's not broken..

                  Comment


                  • #10
                    Originally posted by xiando View Post

                    I strongly disagree. If your current BIOS works fine then it's fine and you should keep it.
                    BIOS versions are easy revertable on new ASUS boards, so it hurts nothing to try

                    On first 2 years there is a possibilty that BIOS is an issue, that is on average how much support is there too (i don't speak in general but speaking for ASUS mobos, situation with other mobo vendors might be different) So, BIOS updates are recommended particulary for new chipsets. Of course, in case of an issue with some just revert to your working version.
                    Last edited by dungeon; 01-07-2019, 01:37 AM.

                    Comment

                    Working...
                    X