Slashdot Mirror
Linux 4.4 Kernel To Bring Raspberry Pi Graphics Driver, Open-Channel SSD Support (phoronix.com)
An anonymous reader writes: Linux 4.4-rc1 has been released. New features of Linux 4.4 include a Raspberry Pi kernel mode-setting driver, support for 3D acceleration by QEMU guest virtual machines, AMD Stoney APU support, Qualcomm Snapdragon 820 support, expanded eBPF virtual machine programs, new hardware peripheral support, file-system fixes, faster SHA crypto support on Intel hardware, and LightNVM / Open-Channel SSD support.
This is actually kind of cool, especially if the performance isn't terrible.
no, new drivers get included with kernel updates. What do you think this is, Microsoft Windows?
I built it just a few hours ago... and /dev/video0 (or /dev/video or /dev/video[0-9]) are all missing. And mknod will create it, but it doesn't fly if you do. And dmesg shows that its not quite there. And so you have to wait till 4.4.1-rc2 or -rc3. So run an old kernel (I keep several old ones around and the last was 4.3.0). So all is well for now, we will test 4.4 kernel in another week or two. To be fair the kernel build showed that not all kernel modules were built (and that *is* quite rare).
Meanwhile, every single major revision of the kernel has been announced on Slashdot for at least as far back as I can remember (2.2 something).
So how you can't "expect" it to happen is a mystery indeed.
May we live long and die out
Shut the fuck up about systemd. You all sound like old, grumpy men that can't adapt to any sort of change.
Read up on systemd and learn how to use it. If you spent half the amount of time learning systemd as you do complaining on the internet, you might find it's actually really good. It's like SMF, but even more flexible.
The Solaris people pissed and moaned about SMF, but now its considered a distinguishing feature of the OS, and I doubt any Solaris admin would trade SMF for SysV init.
If you don't want to read about such things, you're on the wrong page, mate. Perhaps Facebook or Newgrounds would suit you better.
Oh man, are you behind or what? That got sorted out at least half a decade ago. (Also, XKCD is on 1604 by now.)
Just for reference, KMS is something you shouldn't mention and hope that people forget how ridiculously behind Linux is in this area compared to ... Well everyone else that does anything other that 80x24 text.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Because the typical experience is not like that.
Because that isn't the typical experience. For a start, the guy gets into driver parameters, testing kernels, and compiling from git. None of that is typical at all, hence why the Ubuntu etc. installation instructions say nothing about that. All a newbie user would know would be that some of his hardware isn't picked up in one particular distro. Maybe some older kernels work - who knows, did they test? What about the kernels in a STABLE version of a Linux distro that's aimed at first-time users? Did that work? I'm guessing you have no answer because you haven't tried.
(And, most importantly here, if that person was you, DID YOU REPORT THE BUGS? No? Thanks a lot for smearing bad news across the Internet without even giving people a chance to fix it).
However, it's like comparing my latest foray into IBM BladeCenter servers. On boot from a standard Windows 2012R2 install disk, they crash. That's it. BSOD and end of game. With a 10-minute BIOS boot, it doesn't matter how long you try, it still just crashes before it gets into Windows.
You have to create the support DVD from IBM-supplied drivers yourself. They don't supply one. This involves several HOURS of downloading, lots of disk space and knowing exactly what components you have in your blade server. Down to the difference between an HS23 (1506) blade and an HS23 (8883) blade, for example.
Then you have to burn that to a DVD (because it's too large for CD). Boot EVERY blade from that one by one, which runs off and updates 20-30 items of firmware on the blades and server and RAID card and AMM, and network card and all kinds of other internal hardware. It can take a day for a fully occupied BladeCenter. Then it lets you chain-boot into a Server 2012R2 install CD that you've got to slipstream the latest patches into.
Then AND ONLY THEN does it allow you to boot up into plain Windows without BSOD on bootup, so you can get on with actually installing the proper Windows drivers instead of the Microsoft-supplied ones, configuring the damn thing in terms of network, storage,etc.
Sounds like a horror story? It is. But it's got nothing to do with the Windows CD that Microsoft supply, in the same way that latest-laptop-model-with-Windows-support-only-not-yet-supported-on-Linux has nothing to do with some inherent flaw in Linux.
Typical experience with Linux is more generally "Okay. That seems to have worked. What do I do now?" (which is pretty much Linux use in a nutshell) while sitting at an unaccelerated login screen. I know, I've deployed Linux in schools, and we do it as part of some courses, and I've shown lots of people how to use it.
P.S. If I grab the latest laptop off the production line and slap plain Windows on it, likely I will have similar problems. How do I know? I do it all day long. Best ones are when the wireless or network just won't work, so it can't get to Windows Update to get the rest of the drivers for the machine. And sometimes even the Windows Update drivers just crash the thing or don't work at all. The newer the laptop, the bigger the problem you get.
Would you like me to describe the problem with a brand-new B5400 Lenovo laptop I had that consisted of ONLY joining open wireless networks and not encrypted ones, where only the left half of the touchpad worked properly, the network card didn't work, and the graphics were stuck in 1998 in terms of screen resolutions? Windows is JUST as bad in similar circumstances.
If you want smooth video playback on any platform and choose to use Flash, you're doing it wrong.
Escher was the first MC and Giger invented the HR department.
I thought that sort of run around ended with Itanium. Wow.
deleting the extra space after periods so i can stay relevant, yeah.
I think you guys are using different definitions of "major".