Today we are proud to release siduction 2017.1.0 with the flavours KDE, LXQt, GNOME, Cinnamon, MATE, XFCE, LXDE, Xorg and noX. The fact that Debian is in deep freeze for Debian 9 »Stretch« allows us to release the whole stack. As I posted before not too long ago, we planned the release before going to CLT-Conference on 11./12. of March, and voila – here it is.
The released images are a snapshot of Debian unstable, that also goes by the name of Sid, from 2017-05-03. They are enhanced with some useful packages and scripts, a brand new installer and a custom patched version of the linux-kernel 4.10, accompanied by X-Server 1.19.2-1 and systemd 232-19.
Litebook, a small hardware manufacturer that we never heard of before, has recently released a new Linux-powered laptop that's cheap, slim, fast, elegant, light, and designed to rival Chromebooks.
The Alpha Litebook is a 14.1-inch Full HD (1920x1080) laptop that runs the Ubuntu-based elementary OS distribution and ships with some of the most popular open source applications, including Google Chrome, Steam for Linux, Spotify, Skype, PlayOnLinux, WPS Office office suite, and much more.
It seems Razer have been getting a lot of requests for Linux support on their 'Razer Blade' laptop line, so they are looking for feedback.
Many Phoronix readers appear rather intrigued by the AMD Ryzen 7 1700 on Linux as it offers good multi-threaded performance with eight cores / 16 threads and retails for just $329 USD. Making the Ryzen 7 1700 even more appealing to enthusiasts is that it overclocks well. For those curious, here are benchmarks of the Ryzen 7 1700 on Ubuntu Linux running at 4.0GHz.
This guide tells some of our story, but mostly tries to give you ideas on how to make a Linux club work where you are.
With the recent roll-out of Mesa's on-disk shader cache, an initial limitation was that the entire cache would be erased if a user switched between 32-bit and 64-bit applications. That's now been fixed. And now the OpenGL GLSL shader cache is enabled by default.
I'm sure plenty of you will be happy with this, as Mesa now has the shader cache enabled by default in Mesa-git to allow for wider testing. It may be turned off for Mesa 17.1, if wider testing shows issues with it.
So two weeks have passed, the merge window is over, and 4.11-rc1 has
been tagged and pushed out.
This looks like a fairly regular release. It's on the smallish side,
but mainly just compared to 4.9 and 4.10 - so it's not really
_unusually_ small (in recent kernels, 4.1, 4.3, 4.5, 4.7 and now 4.11
all had about the same number of commits in the merge window).
It _does_ feel like there was more stuff that I was asked to pull than
was in linux-next. That always happens, but seems to have happened
more now than usually. Comparing to the linux-next tree at the time of
the 4.10 release, almost 18% of the non-merge commits were not in
Linux-next. That seems higher than usual, although I guess Stephen
Rothwell has actual numbers from past merges.
Now, about a quarter of the patches that weren't in linux-next do end
up having the same patch ID as something that was, so some of it was
due to just rebasing. But still - we have about 13% of the merge
window that wasn't in linux-next when 4.10 was released.
Looking at the sources of that, there's a few different classes:
This is obviously ok and inevitable. I don't expect everything to
have been in linux-next, after all.
- the statx() systen call thing.
Yeah, I'll allow this one too, because quite frankly, the first
version of that patch was posted over six years ago.
- there's the quite noticeable
This one was posted and discussed before the merge window, and
needed to be merged late (and even then caused some conflicts). So it
had real reasons for late inclusion.
- a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out.
That last case is what I found rather annoying this merge window.
In particular, if you cannot follow the simple merge window rules
(this whole two-week merge window and linux-next process has been in
place over a decade), at least make the end result look good. Make it
all look easy and problem-free. Make it look like you know what you're
doing, and make damn sure the code was tested exhaustively some other
Because if you bypass the linux-next sanity checks, you had better
have your own sanity checks that you replaced them with. Or you just
need to be _so_ good that nobody minds you bypassing them, and nobody
ever notices your shortcuts.
Saying "screw all the rules and processes we have in place to verify
things", and then sending me crap that doesn't even build for me is
You people know who you are. Next merge window I will not accept
anything even remotely like that. Things that haven't been in
linux-next will be rejected, and since you're already on my shit-list
you'll get shouted at again.
Just a few moments ago, Linus Torvalds announced the availability of the first Release Candidate (RC) development build of the upcoming Linux 4.11 kernel series, which users can download, compile, and test on their GNU/Linux distributions.
Linus Torvalds has announced the first test release of the upcoming Linux 4.11 kernel.
Torvalds' release announcement that just hit the mailing list mostly talks about the size of the merges and a fair amount of material that was merged but hadn't been staged in linux-next, upsetting him some. Beginning with Linux 4.12, Linus will become more strict about seeing that big changes be staged in linux-next for testing.
Linux 4.11 is worthwhile in that it's bringing ALC1220 audio support, the codec used by many Ryzen (and Intel Kabylake) motherboards, but this next kernel version doesn't appear to change Ryzen's performance.
I didn't see anything notable this Linux 4.11 merge window with regard to Ryzen for potentially affecting its performance, but I ran some benchmarks this weekend just to confirm.
Intel's "SWR" software rasterizer living within Mesa now has support for OpenGL geometry shaders.
Thanks to work that landed today by Intel's Tim Rowley, there is now support for OpenGL geometry shaders in this software rasterizer. The code amounts to over 700 lines of new code to implement GL GS support.
Kwort 4.3.2 is available for download
We would like to start this update by thanking our dedicated fans and community members who have shown us nothing but support over the 3 years that we have worked on Trenta OS and Trenta.io. Today we will make some possibly unpopular announcements. Our goal of providing you with the best looking open-source desktop experience has not changed. Though, we do need to make some critical changes at this time.
TL;DR: Trenta OS ISO release schedule has been put on hold. Rainier UI and Trenta OS testing packages will be installable on existing Ubuntu Gnome installations and possibly more distros for testing. There will be more community interaction.
The Cloud Native Computing Foundation (CNCF) has accepted the CoreDNS networking project into its project roster. CoreDNS had been trying to become hosted CNCF project since at least October 2016, though it's first attempt was not successful.
The CNCF itself is a Linux Foundation Collaborative Project and first got started back in July 2015. The first project to come over to the CNCF was Google's Kubernetes, open-source container orchestration platform. Since then the CNCF has added five other projects including: Prometheus monitoring, OpenTracing, Fluentd logging, LinkerD and the gRPC projects.
Chris Mason has sent in a secondary pull request of Btrfs material for the Linux 4.11 merge window.
Last week Mason sent in the main Btrfs pull request for 4.11 and it basically amounted to fixes. With the secondary pull request mailed in on Thursday, there are more fixes and performance improvements.
Submitted earlier in the Linux 4.11 merge window were the big ARM SoC and platform changes for this next kernel version while some last-minute ARM changes have just arrived.
Arnd Bergmann sent in some last-minute ARM SoC updates for the Linux 4.11 kernel. These late changes include USB 3.0 support for Samsung's Exynos 7, some Samsung power management updates, WeTek set-top box support, and some fixes.
Intel's set to enable atomic mode-setting by default with code slated to land for the Linux 4.12 kernel.
The initial patches for enabling atomic mode-setting by default turned it on for Gen5 (Ironlake) hardware and newer, but left out Valleyview and Cherryview hardware due to problems. But now it looks like for Linux 4.12 the Cherryview/Valleyview problems could be addressed and see those mobile platforms go atomic too.
Besides recent Intel graphics hardware making use of firmware binary blobs now for the GuC/HuC functionality, Intel audio hardware continues in making use of firmware binary-only blobs for audio support.