Linux 3.19 Kernel To Start 2015 With Many New Features 66
An anonymous reader writes Linux 3.18 was recently released, thus making Linux 3.19 the version under development as the year comes to a close. Linux 3.19 as the first big kernel update of 2015 is bringing in the new year with many new features: among them are AMDKFD HSA kernel driver, Intel "Skylake" graphics support, Radeon and NVIDIA driver improvements, RAID5/6 improvements for Btrfs, LZ4 compression for SquashFS, better multi-touch support, new input drivers, x86 laptop improvements, etc.
Re: (Score:2)
Really curious to know how this is "Flamebait".
Re: (Score:2)
Re: (Score:2)
System Hardware. Or yum install hardinfo (Score:4, Informative)
The kernel and friends manage hotplug devices quite nicely.
I take that to mean you want a clickity-click GUI, so you can see what the system has already detected and handled properly for you, and do things without needing to understand what you're doing. If that's what you're looking for, hardinfo is a well-known option. Your choice of graphical desktop environment probably has one it provides by default as well. Look under "System" or similar.
Re: (Score:2)
Not really : "hardinfo" itself is not known or not known under that name, and a report about the installed hardware is a bit worthless (lspci and lsusb do about that).
The Device Manager is not only a unique GUI (stable during two decades of Windows versions), it allows to choose or install drivers and even to configure the drivers. You can do things that are seemingly impossible in linux like limiting a wireless card to a maximum speed (to get a connection "slower" but more stable), or other things. It woul
Re: (Score:2)
Manual override of connection speed is via the 'iwconfig' command. I've done it before. I don't know if you can set a maximum speed, but you can set a fixed speed.
Re: (Score:3, Insightful)
Re:systemd? (Score:5, Funny)
The Linux kernel is depricated[sic] - systemd will take over its functionality.
+1 hilarious.
Re: (Score:1)
I'm glad to hear that systemd is being reimplemented in Emacs Lisp so it can run seamlessly, as all functionality should, as part of Emacs.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
are they using -march or -mtune?
I do understand that many won't run out of the box with less than a 586-class processor now, but I don't think P4 is common yet
Re: (Score:1)
Red Hat is why shitstemd exists...
Re: (Score:1)
Re: (Score:1)
Have you actually taken a look at the log format that journald uses? Text is stored verbatim in them, so you can even dig through them with grep. Binary meta-data being added to it makes wonderful things possible - getting logs by unit, time and other parameters without whipping out a mile-long regexp. So please read up on the topic you attempt to bash or you will end up looking pretty stupid to anyone with a clue. Just like you did now.
Re: (Score:1, Interesting)
Re: (Score:3)
"SystemD is pioneering the idea" - surely Sun, Apple and Ubuntu have similar in place before systemd came about.
Re: (Score:2)
The point is that that's the opinion of people who dislike systemd. That doesn't automatically mean they'll also dislike "a Systemd like init".
People like that might not (those who think it's implemented poorly). The people who will are the ones who insist on an init system that follows the "Unix philosophy". They're not going to be satisfied with anything other than sysvinit.
Re: (Score:2)
Great, we look forward to seeing your new upstart-based distro, since everyone else has abandoned it.
Re: (Score:1)
Great, we look forward to seeing your new upstart-based distro.
That'd be Debian. Jessie will support systemd, upstart or sysvinit.
Re: (Score:2)
It would be nice to have an adult discussion of the pro/co
Will RTL8192 still be broken? (Score:1)
It worked always great, then I think after 3.12 it doesn't work anymore. The problem is that most distributions I tried installed with 3.08 or something below, and they all want to upgrade to a newer kernel and all probably want to upgrade utilities - that also could be broken for that chipset. So long story short, due to linux being broken one piece at time, I had to buy a mac :(
Re: (Score:2)
Sounds somewhat worrying. That's a very popular chip.
There's always a few things you can do:
- Talk to LKML.
- Post a bug report in bugzilla.kernel.org.
- Find the specific patch which caused the regression with git bisect. Canonical has a good guide on the topic [ubuntu.com] (use "man git-bisect" for more info).
Re: Will RTL8192 still be broken? (Score:1)
Could you be more specific on a device that isn't working. I'm pretty sure I have run a device with a version of this chip not long ago without issue. Knowing a specific device might help track down any issues.
old hardware left behind (Score:2)
One of my PCs is a Gateway GT5628 PC with an Intel Q6600 chipset. Shutdown used to work every time on this PC, with kernels around the 2.6.32 version. By 2.6.38, shutdown was unreliable. About half the time shutdown works, and the other half the computer goes through the shutdown process successfully and at the very end, fails to turn itself off, sitting on the text screen with "power down" displayed on the monitor. I have to hold the power button for 4 seconds to complete the shutdown.
I haven't submit
Re: (Score:1)
It worked always great, then I think after 3.12 it doesn't work anymore.
Seems to be working for me with Debian's 3.16.
Bug report numbers?
"New Features" (Score:1)
Not sure "new features" is the right summary of changes.
Re: (Score:2)
Re: (Score:2)
http://www.phoronix.com/scan.p... [phoronix.com]
Re: (Score:2)
x86/64, but with a ton of stuff crammed into the ACPI interface, some of which is actually there for power management, none of which is properly documented because every manufacturer likes to put their hotkeys and screen close sensor on a different ACPI event.
Lockup issue (Score:3, Interesting)
Has the lockup issue been solved?
http://www.phoronix.com/scan.p... [phoronix.com]
Re: (Score:3)
yes:
http://lkml.iu.edu/hypermail/linux/kernel/1411.3/04672.html/ [iu.edu]
https://bugzilla.kernel.org/show_bug.cgi?id=85941/ [kernel.org]
Re: (Score:3)
That's something different.
See this LKML page [iu.edu]. Search with CTRL+F for "frequent lockups in 3.18rc4".
The thread is clearly still going on. As far as I can tell, the bug has not been fixed.
Re: (Score:2, Informative)
As far as I know, they found the cause (it seems the kernel doesn't handle well some clock issues and clock overflow), and Linus send a RFC-like patch that kinda "fixes" the thing but it is so hackish that it needs to be discussed, generalized and ironed out. DaveJ doesn't have access to the hardware triggering the issue anymore, so it may be a while before they can actually fix it in a proper manner.
On the way to figuring out the cause for that bug, they found other lockup issues with similar symptoms but