Announcement

Collapse
No announcement yet.

Intel GPU Driver Tries To Rip Out FBDEV Support

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

  • #21
    Originally posted by curaga View Post
    Currently, no matter how bad the situation, I can switch to the console X was started from, and CTRL-C X. No new processes are started, it's a VT switch to the existing terminal.
    Have you ever tried this? Does it work for you that way?
    My experience is very different. I could switch eventually, but it was far away from what I would call a reasonable fast response.

    Comment


    • #22
      Seems like a daring move, but if it's just a config setting to flip it back on I don't think it's a big deal yet...

      Comment


      • #23
        Originally posted by Ericg View Post
        VirtualBox gets off its ass and makes a proper KMS driver like VMWare is working on/did

        EDIT: Oh hey, guess they are. http://www.phoronix.com/scan.php?pag...tem&px=MTAxOTk Shouldn't be an issue then.
        It seems to only be in the additions once you install them. not mainline Mesa, or the mainline Linux kernel.

        Live CD's won't work on VirtualBox. (or the graphical installers...)

        Comment


        • #24
          Originally posted by nerdopolis View Post
          It seems to only be in the additions once you install them. not mainline Mesa, or the mainline Linux kernel.

          Live CD's won't work on VirtualBox. (or the graphical installers...)

          Then we are back to my original point.

          Comment


          • #25
            Originally posted by Ericg View Post
            Does anyone really use console decorations? And high res is still supported, you just do a straight up DRM console instead of FBDEV console (See KMSCon)
            Well, I use fbsplash, but mostly just for the boot splash. Plymouth doesnt work well in gentoo, so fbsplash is the only good alternative.

            Comment


            • #26
              Ha, silly Intel, this means all Linux users will be left with blank screen, might as well remove support for keyboards!

              Comment


              • #27
                Originally posted by curaga View Post
                Yes, and kmscon is userspace, which means less reliability in tough situations like OOM conditions.
                In general, only a serial console is more-or-less a fail-safe method to get (OOPS/OOM) messages from the kernel. All other solutions (VT, net-console, etc) are unreliable by design.

                - Gilboa
                DEV: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB + 2x3TB, GTX780, F21/x86_64, Dell U2711.
                SRV: Intel S5520SC, 2xX5680, 36GB, 4x2TB, GTX550, F21/x86_64, Dell U2412..
                BACK: Tyan Tempest i5400XT, 2xE5335, 8GB, 3x1.5TB, 9800GTX, F21/x86-64.
                LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F21/x86_64.

                Comment


                • #28
                  True, VT switch is not 100% reliable, but still moving to userspace would decrease reliability.

                  Comment


                  • #29
                    Originally posted by curaga View Post
                    True, VT switch is not 100% reliable, but still moving to userspace would decrease reliability.
                    But VT switch is essentially in userspace today. Or rather it depends on userspace for the hand-off from X. So it is already as unreliable as it's going to get.

                    Comment


                    • #30
                      Originally posted by duby229 View Post
                      Well, I use fbsplash, but mostly just for the boot splash. Plymouth doesnt work well in gentoo, so fbsplash is the only good alternative.

                      Interesting, any particular reason it doesnt work well with Gentoo? you've piqued my curiosity haha

                      Comment

                      Working...
                      X