Announcement

Collapse
No announcement yet.

Chrome/Chromium To Require Newer Version Of Linux Kernel

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

  • Chrome/Chromium To Require Newer Version Of Linux Kernel

    Phoronix: Chrome/Chromium To Require Newer Version Of Linux Kernel

    Those using the bleeding-edge version of Google's Chrome/Chromium web-browser are discovering you need to be using a relatively new version of the Linux kernel to avoid issues...

    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

  • #2
    Well, this is bad news for me. I still run the older Fedora19 kernel (3.14 I believe) because the newer radeon kernel driver crashes my Xorg regularly.

    Comment


    • #3
      Chrome 40.0.2214.115-1 actually works good on Linux 3.15.10 (zen-686).

      Comment


      • #4
        wtf

        chrome 41 with linux kernel 3.14.34-lts-ck everything works fine

        Comment


        • #5
          Originally posted by Ancurio View Post
          Well, this is bad news for me. I still run the older Fedora19 kernel (3.14 I believe) because the newer radeon kernel driver crashes my Xorg regularly.
          What Radeon GPU is this? I don't have any problems with a 4870, 6850, 7950, R9 270X, A4-5000, A8-6400K or A8-7600 with any recent kernels.

          Comment


          • #6
            lol - not sure what they're talking about

            running chromium 42 here on 3.19-based kernel

            and there's no SECCOMP_FILTER_FLAG_TSYNC

            Comment


            • #7
              Ubuntu 14.04 (trusty) has the necessary change since November
              Ubuntu 14.04.2 + 14.10 (utopic) have the necessary change since October

              So Ubuntu is fine...

              Comment


              • #8
                Too bad it 3.17 wasn't the linux 4.0 release. That would have made it very easy to differentiate.

                Comment


                • #9
                  Originally posted by kernelOfTruth View Post
                  lol - not sure what they're talking about

                  running chromium 42 here on 3.19-based kernel

                  and there's no SECCOMP_FILTER_FLAG_TSYNC
                  just took a look in the source code - it already seems to be there


                  @davidbepo:

                  perhaps that feature flag already got backported ?

                  Comment


                  • #10
                    3.4.63!

                    Hmm, running chrome 40.0.2214.115 (64-bit) under openSUSE 12.2 "Mantis", Linux 3.4.63-2.44-desktop just works!?!

                    Comment

                    Working...
                    X