Dazog

this is in 6.6

I am running a 1920x on X399 Asrock Tai Chi with latest bios 3.30. 32 gigs of 3600 mhz ram. No problems so far.

Latest: https://snapshot.raintank.io/dashboard/snapshot/bUHqkj7sDstzaS5ZWCN6en6h9A8lgd6j Just have to fix CPU temps, they don't want to work with k10temp module and grafana yet!

Awesome work! Now for intel to get off there duffs and fix the 4.18 compile errors. Anyway one minor GUI issue on docker page with long repositories: The version tab is a little too close to the Application Field One last big request... Can we have an option in Display settings to Hide the ugly red version number below the awesome new Logo

Why aren't u running a VM on unraid with JUST chrome installed on it? Fully utilize unraid's POWER!

IE 11 isn't a supported browser anymore.

Unraid is using a very old squashfs version. Since that time a few CVE's have been patched: CVE-2012-4024 CVE-2012-4025 Unraid is using 4.0 Current version is 4.3

Google home and Alexa skills for controlling unraid. Right

QEMU 3.0 include Spectre V4 mitigation for x86 Intel/AMD Biggest reason for upgrade.

The ryzen/threadripper issues are a linux kernel thing. Not something UNRAID can solve. 6.6 will be on a newer kernel. It's just a matter of debate if it's 4.17 or 4.18. If you have issues submit a patch to help fix it in the kernel.

I don't think people are being impatient. It's just that it seems daily there are intel cpu hardware exploits being released and we are vulnerable. Since they have issued new micro code updates and QEMU 3.0 is out with spectre v4 mitigations. So I think it's more "worry" than OMG hurrrry up I am wondering if it's worth having live patching in a 6.6x release for updating the microcode in between releases? Or doing a security release once a month with JUST an update to the branch of kernel and microcode only???? Example 6.5.3.1 Update to latest 4.14 kernel and latest AMD and intel microcode. Then people can decide to update or wait.

Qemu 3.0 is now released

Well 4.17 will go EOL soonish... Why not 4.18 it has moar xfs fixes ?

New microcode out: https://downloadcenter.intel.com/download/28039/Linux-Processor-Microcode-Data-File?product=873

They can't give us a 6.6 RC yet. Linux Kernel 4.18 was pushed back a week

Shouldn't this just use the default DNS used by Unraid? I don't allow devices on my network to override what I set at my router. Which in my case is 1.1.1.1 and I use DNS over TLS to protect my query's from preying eyes.

5.9.16 is out: https://community.ubnt.com/t5/UniFi-Beta-Blog/UniFi-SDN-Controller-5-9-16-Testing-has-been-released/ba-p/2427840

https://community.ubnt.com/t5/UniFi-Beta-Blog/UniFi-SDN-Controller-5-9-12-Testing-has-been-released/ba-p/2418005 5.9.12 is out

https://cateee.net/lkddb/web-lkddb/BNXT.html It says since 4.4 it's in kernel. I would wait to try next unraid 6.6 with latest 4.17 kernel.

New microcode out: https://downloadcenter.intel.com/download/27945/Linux-Processor-Microcode-Data-File?v=t 20180703

Just when you think being on the latest kernel is awesome.. https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.18-XFS-Round-2 They start making xfs better! Never ends

Upgraded with no issues! Bring on 6.6 with linux 4.17?? I really want to see if get idle power consumption decrease on my unraid box!

No issues upgrading from 6.5.3 rc1 to rc2 Can't wait for 6.6 with kernel 4.17

https://www.phoronix.com/scan.php?page=news_item&px=Spectre-V3-V4-Vulnerabilities These new vulnerabilities affect all major CPU vendors just not AMD/Intel but also ARM and IBM / POWER Initial SSBD mitigation landed today in the Linux kernel and is being prepared for back-porting to supported stable series. Microcode CPU updates are also necessary.

https://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-Linux-Firmware-Add https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8