Linux 5.0 Kernel Released With Long-Awaited FreeSync Support, Many New/Improved Features

[phoronix]

Phoronix: Linux 5.0 Kernel Released With Long-Awaited FreeSync Support, Many New/Improved Features

Linus Torvalds has gone ahead and just issued the Linux 5.0 stable kernel for what originally began as the Linux 4.21 kernel cycle. The Linux 5.0 kernel cycle delivers on the mainline AMD Radeon FreeSync support, continued work on bringing up Intel Icelake and other new CPU features, Logitech high-resolution scrolling capabilities, network improvements, and much more...

http://www.phoronix.com/scan.php?page=news_item&px=Linux-5.0-Kernel-Released

[RussianNeuroMancer]

Beware, possibly there is btrfs stability issue: https://www.phoronix.com/forums/foru...58#post1081958

[NateHubbard]

Beware, possibly there is btrfs stability issue: https://www.phoronix.com/forums/foru...58#post1081958

I wonder if that's specific to 5.0 though. Especially when saying things like, "I hope that because my SSD is dying or issues between NVME and eGPU connected via TB3, or something like that".

[dkasak]

Beware, possibly there is btrfs stability issue: https://www.phoronix.com/forums/foru...58#post1081958

Yikes I've been on 5.0-rc kernels since they started, and I have BTRFS on NVME. Not a single BTRFS issue here.

By the way, kernel.org doesn't seem to be updated yet - I still only see rc kernels.

[Mangix]

Beware, possibly there is btrfs stability issue: https://www.phoronix.com/forums/foru...58#post1081958

Don't use btrfs. It gets limited testing compared to say, ext4.

I speak from personal experience as I have gotten burned at least 5 times.

edit: to clarify a little, big endian to little endian compatibility is a joke. For my purposes, I migrate between both types of systems. The big endian one has always been problematic. The last time that I used btrfs on it the filesystem got corrupted. "btrfs filesystem check" could not fix the problem even on a little endian device (where it could not be mounted one corrupted).

[starshipeleven]

edit: to clarify a little, big endian to little endian compatibility is a joke.

Also one of the issues of F2fs.

Still, given that ARM, x86 and Power are little-endian (Power can technically be both but on Linux it is commonly used as little-endian because of obvious reasons), plus a sizeable chunk of mips are also little endian, I'd rather replace whatever is Big Endian than change filesystem.

[pcxmac]

Don't use btrfs. It gets limited testing compared to say, ext4.

I speak from personal experience as I have gotten burned at least 5 times.

edit: to clarify a little, big endian to little endian compatibility is a joke. For my purposes, I migrate between both types of systems. The big endian one has always been problematic. The last time that I used btrfs on it the filesystem got corrupted. "btrfs filesystem check" could not fix the problem even on a little endian device (where it could not be mounted one corrupted).

Don't use any file system exclusively, and don't believe any file system will keep a hold on your data. Backup at least once. ZFS has lost far more data for me, FAR more than BTRFS, in fact, I don't believe I have ever lost data from BTRFS, and I run it in RAID. ZFS, not all it's cracked up to be, and easy to zap if you do something foolish.

However, all my large stores are ZFS But I know to back up at least twice. I use btrfs for all my generic userspace, and for special applications like Virtualization, I run more highperformant file systems, and back up, as well as use snapshotting with virtual disk images. BTRFS aint perfect, and it can be horribly slow sometimes, but it's great to use in some use cases.

[pcxmac]

It can take 10 hours before the kernel 5.0 is released actually. Monday is in the future there.
https://www.timeanddate.com/worldclo.../san-francisco

https://git.kernel.org/pub/scm/linux...lds/linux.git/ - 8 hours ago. Looking forward to seeing it in gentoo-sources soon.

[theriddick]

To get this freesync working with AMD cards and this kernel driver, do you need to disable your secondary(s) screens and only have a single display connected? That's one of the MAJOR issues I have with NVIDIA's gsync.

[birdie]

https://git.kernel.org/pub/scm/linux...lds/linux.git/ - 8 hours ago. Looking forward to seeing it in gentoo-sources soon.

It's great we have so many willing beta testers who are willing to sacrifice the integrity of their systems, so that others could use stable bugs-free kernels. I for one will not update until 5.0.4 gets released. I vividly remember the data corruption issue in one of the recent kernels.