Slashdot Mirror


Linux 4.5 Adds Raspberry Pi 2 Support, AMD GPU Re-Clocking, Intel Kaby Lake (phoronix.com)

The Linux 4.5 merge window has been open for the last two weeks; that means that the 4.5-rc1 kernel is expected to emerge, with the official kernel following in about eight weeks. An anonymous reader writes with this top-level list of changes to look for, from Phoronix: Linux 4.5 is set to bring many new features across the kernel's 20 million line code-base. Among the new/improved features are Raspberry Pi 2 support, open-source Raspberry Pi 3D support, NVIDIA Tegra X1 / Jetson TX1 support, an open-source Vivante graphics driver, AMDGPU PowerPlay/re-clocking support, Intel Kaby Lake enablement, a Logitech racing wheel driver, improvements for handling suspended USB devices, new F2FS file-system features, and better Xbox One controller handling.

6 of 147 comments (clear)

  1. Re:Has the systemd problem been addressed? by Anonymous Coward · · Score: 1, Informative

    I was totally agnostic about it, not really caring either way. Well, I was, up until one of my three systems that has been running Linux fine since forever no longer boots under systemd, and the command it gives me to produce a log output gives no hints whatsoever about what is wrong.

    This system still boots fine under older OSs.

    I have no idea whether systemd will be fine once it's ready, but currently it is NOT ready for prime time release.

  2. They've moved to that distro: it's called FreeBSD. by Anonymous Coward · · Score: 3, Informative

    The solution is for all the systemd haters to band together into one distro and move on.

    This has already happened. The most talented and experienced Linux users have already moved to FreeBSD. Maybe you don't realize it, but this is the worst thing that could have happened to Linux. Now Linux and its community will no longer benefit from the decades of experience these users each tend to have. They're the unsung heroes who kept the Linux community going. Now their contributions benefit the FreeBSD community instead.

    The exact same thing is happening to Linux that has happened to the Firefox web browser. In the case of Firefox, it was the awful and unwanted UI changes (especially Australis) which drove away Firefox's most important users. Without their support, Firefox's overall share of the market has dropped to only around 7% today. Systemd is the equivalent when it comes to Linux. It's an unwanted and awful change for many users, and it has forced them to abandon Linux completely.

    Systemd has harmed Linux and its community way more than Microsoft, SCO, Apple, or any other company could have. Linux's collapse has come from within. It has come from people like you, who tell the best Linux users to basically "fuck off and die". Well, those users have listened, and now they're happy, productive, proud and helpful FreeBSD users, and they make absolutely no contributions to the Linux community any longer.

  3. Re:RPi2 support? by Anonymous Coward · · Score: 4, Informative

    It wasn't using an upstream kernel in Raspbian and others but an older kernel plus extra patches. Now all of the support is mainlined.

  4. Re: RPi2 support? by omkhar · · Score: 3, Informative

    It adds additional support for the graphics portion which weren't previously included in the main line kernel.

  5. Re:Has the systemd problem been addressed? by thegarbz · · Score: 1, Informative

    Many Linux users just cannot use systemd. ... Systemd's use of binary logging is one of the most obvious problems with it.

    Found the guy who can't read the fucking manual.

  6. Re:Has the systemd problem been addressed? by Xtifr · · Score: 1, Informative

    If systemd "doesn't even have usable logs", then neither does sysvinit. Because systemd can log to exactly the same places sysvinit does, in exactly the same way! And on my system it does. Systemd also has other options, which I may explore later at my leisure. But for now, nothing about my logs has changed with systemd!

    Of course, I'm using Debian, and this whole thing is reminding me very much of the glibc transition, back in the day. Lots of people were screaming about how glibc was breaking everything, because certain vendors (no names will be mentioned...rdht) rushed the transition out the door. Debian took their time and did it right, and Debian users barely even noticed the transition.