Linux 6.14 To Introduce New DRM Boot Logger For Kernel Messages

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67377

    Linux 6.14 To Introduce New DRM Boot Logger For Kernel Messages

    Phoronix: Linux 6.14 To Introduce New DRM Boot Logger For Kernel Messages

    Sent out today was the latest drm-misc-next pull request of various Direct Rendering Manager (DRM) changes queuing up ahead of the Linux 6.14 kernel cycle. Most exciting this week is the DRM boot logger being queued for landing to better present kernel messages...

    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
  • Guest

    #2
    they are climbing somewhere ahead, without even solving the problems that go from year to year from version to version. there is a mess in loading video drivers. is no one paying attention to this? if you have installed, for example, a driver from the official NVIDIa website, then the kernel driver will load first, after which the driver installed by the user will load. all this is accompanied by changes in image quality and the size of elements on the screen, which kills aesthetics.

    Comment

    • rene
      Senior Member
      • Jul 2015
      • 1505

      #3
      the one simple boot message logging thing I want is simply being able to scroll back just a little, ... sooo I brought it back yesterday: https://www.youtube.com/watch?v=-4ouJXaphTk of course for the https://t2linux.com ;-)

      Comment

      • fitzie
        Senior Member
        • May 2012
        • 672

        #4
        if qr codes are good for panics, why not qr codes for boot logging?

        Comment

        • skeevy420
          Senior Member
          • May 2017
          • 8664

          #5
          Originally posted by rene View Post
          the one simple boot message logging thing I want is simply being able to scroll back just a little, ... sooo I brought it back yesterday: https://www.youtube.com/watch?v=-4ouJXaphTk

          6 hours? Blimey mate, there's a reason that TikTok took off... Not that any work on boot scrolling isn't appreciated, I was pissed about that, too, but a 5 or 10 minute video that goes into the history and the solution would be a better format to attract more people to watch so they can appreciate what you're doing and learn about T2SDE and Linux in the process.

          of course for the https://t2linux.com ;-)
          And no place else
          Last edited by skeevy420; 16 December 2024, 10:38 AM.

          Comment

          • skeevy420
            Senior Member
            • May 2017
            • 8664

            #6
            Originally posted by fitzie View Post
            if qr codes are good for panics, why not qr codes for boot logging?
            There would have to be a new QR code generated with every line of log added. 10000 lines of logging could mean 10000 QR codes...unless there was a QR on error only option, but fuck all mighty would verbose QR boot logging be a new benchmark and stress test.

            Comment

            • ayumu
              Senior Member
              • Oct 2008
              • 668

              #7
              Originally posted by rene View Post
              the one simple boot message logging thing I want is simply being able to scroll back just a little, ... sooo I brought it back yesterday: https://www.youtube.com/watch?v=-4ouJXaphTk of course for the https://t2linux.com ;-)
              In your shoes, I'd make it a rule that for every hour spent on Linux development, I'd spend x in non-Linux.

              Just because, as you already know, getting anything done on Linux does cost that much more effort, and drains your soul while at it.

              The Linux tarpit is why better architected OSs aren't taking off.

              So many candidates: https://www.microkernel.info/

              Comment

              • Old Grouch
                Senior Member
                • Apr 2020
                • 696

                #8
                Back in the days, boot-logging came automatically as the console was a teletype printer. Admittedly difficult to search.
                Then someone came up with monitoring/copying the logging data on the serial console to another system to keep a record - if you wanted, to a WORM disk.
                Not a lot of systems have easily accessible serial consoles these days,
                What about a non-blocking kernel driver for writing simultaneously to an USB device*? Plug it in, and have a record of boot. Perhaps some magic to write to a particular GPT partition UUID. Or assume it is a USB-to-serial convertor and leave capturing the serial output as 'Somebody Else's Problem'.


                *Write to a ring-buffer in L3 cache until you know you have some working DRAM, copy ring-buffer to larger ring buffer in DRAM and append additional entries until you get USB driver up and running, identify if relevant partition is available, then copy to partition - no filesystem, just dump from the first block onwards. The complexity of USB drivers might make it easier to implement as SD-card, but most systems have USB interfaces.

                Comment

                • NotMine999
                  Senior Member
                  • Feb 2014
                  • 1038

                  #9
                  Originally posted by fitzie View Post
                  if qr codes are good for panics, why not qr codes for boot logging?
                  OMG can you image ine this?

                  QR Boot Logging - The Movie

                  Comment

                  • FedFer
                    Junior Member
                    • Dec 2023
                    • 30

                    #10
                    Originally posted by fitzie View Post
                    if qr codes are good for panics, why not qr codes for boot logging?
                    Because a kernel panic log is static meaning the qr code is generated after having the entire stack trace and it is then shown until the machine powers off. If we were to do the same with boot there'd basically be a qr code for each frame, good luck scanning that.
                    I assume your comment was either intended as a joke or as a troll attempt.

                    Comment

                    Working...
                    X