Linux 5.11 Released With Intel Integer Scaling, AMD Performance Boost, RTX 30 KMS

[perpetually high]

that looks like a problem that you caused yourself. the package I linked to was built.

How is that a problem I caused though? All I did was attempt to install the packages on an LTS 20.04 release. If I change only one thing and that's reboot to the 5.4 kernel, it builds and installs fine.

[danoam]

511fps on performance governor in CS:GO benchmark vs 408fps with schedutil...

[hotaru]

Just to prove it to you:

that looks like a problem that you caused yourself. the package I linked to was built.

hotaru@panda:~ $ uname -a
Linux panda.thinkindifferent.net 5.10.16-arch1-1 #1 SMP PREEMPT Sat, 13 Feb 2021 20:50:18 +0000 x86_64 GNU/Linux
hotaru@panda:~ $ sudo modprobe vboxdrv
hotaru@panda:~ $ lsmod|grep vboxdrv
vboxdrv               528384  0
hotaru@panda:~ $ vboxmanage --version
6.1.18r142142

[perpetually high]

if it doesn't build, what's this?

Just to prove it to you:

opt ❯ uname -a
Linux ubuntu [B]5.10.15-051015[/B]+custom-generic #051015+202102100831 SMP PREEMPT Wed Feb 10 14:18:05 PST 2021 x86_64 x86_64 x86_64 GNU/Linux
[B]opt ❯ sudo dpkg -i virtualbox-6.1_6.1.18-142142\~Ubuntu\~eoan_amd64.deb[/B]
Selecting previously unselected package virtualbox-6.1.
(Reading database ... 1423543 files and directories currently installed.)
Preparing to unpack virtualbox-6.1_6.1.18-142142~Ubuntu~eoan_amd64.deb ...
Unpacking virtualbox-6.1 (6.1.18-142142~Ubuntu~eoan) ...
Setting up virtualbox-6.1 (6.1.18-142142~Ubuntu~eoan) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
[B]vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig[/B]
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
Processing triggers for systemd (245.4-4ubuntu3.4) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for shared-mime-info (1.15-1) ...
opt ❯ sudo apt purge virtualbox-6.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
virtualbox-6.1*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 216 MB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 1424292 files and directories currently installed.)
Removing virtualbox-6.1 (6.1.18-142142~Ubuntu~eoan) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for shared-mime-info (1.15-1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
(Reading database ... 1423543 files and directories currently installed.)
Purging configuration files for virtualbox-6.1 (6.1.18-142142~Ubuntu~eoan) ...
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit packagekit.service is masked.
[B]opt ❯ sudo ./VirtualBox-6.1.19-142777-Linux_amd64.run[/B]
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 6.1.19 r142777 (2021-02-11T22:08:09Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
[B]vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig[/B]
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

The installation log file is at /var/log/vbox-install.log.

Even the 6.1.18 version in the latest .deb doesn't work. Pulling the latest .run file version 6.1.19 r142777 doesn't work either. So I don't know what the hell they're talking about.

[Sanko]

With 5.11 on my 3900x, lscpu now reports 6078,5151Hz as max frequency. Something to worry about?

[aufkrawall]

I've noticed a CPU performance regression in Shadow of the Tomb Raider Vulkan port: While I got ~99fps before, it's now ~85 at that place in the game (5700 XT, vsync off).
Doesn't seem to be related to userspace drivers (nor CPU clock governors) and also current 5.10 versions show the performance loss. I guess I'd have to jump back some kernel versions and see if it gets better at some point...

[hotaru]

hotaru that changelog is bogus. I’m using the latest 6.1.19 release and it doesn’t build on the latest 5.10 point release.

if it doesn't build, what's this?

[kripteks]

My 5600x manual 4500mhz (performance governor) show that:

Iddle mode:
$ cat /proc/cpuinfo | grep -e MHz
cpu MHz : 5998.535
cpu MHz : 6336.914
cpu MHz : 5827.148
cpu MHz : 6169.921
cpu MHz : 4497.895
cpu MHz : 5655.761
cpu MHz : 4499.710
cpu MHz : 6336.914
cpu MHz : 5827.148
cpu MHz : 4497.691
cpu MHz : 6336.914
cpu MHz : 5655.761

$ lscpu | grep MHz
CPU MHz: 4496.039
CPU max MHz: 6336.9141
CPU min MHz: 2200.0000


No-Iddle mode allcore used:
$ cat /proc/cpuinfo | grep -e MHz
cpu MHz : 4499.986
cpu MHz : 4500.005
cpu MHz : 4500.009
cpu MHz : 4499.918
cpu MHz : 4500.003
cpu MHz : 4499.915
cpu MHz : 4499.978
cpu MHz : 4500.010
cpu MHz : 4499.873
cpu MHz : 4499.546
cpu MHz : 4500.007
cpu MHz : 4500.001

$ lscpu | grep MHz
CPU MHz: 4499.971
CPU max MHz: 6336.9141
CPU min MHz: 2200.0000

[perpetually high]

hotaru that changelog is bogus. I’m using the latest 6.1.19 release and it doesn’t build on the latest 5.10 point release.

[hotaru]

VirtualBox as of this date still doesn’t work with kernel 5.10

that hasn't been true for almost a month: https://www.virtualbox.org/wiki/Changelog

VirtualBox 6.1.18 (released January 19 2021)

This is a maintenance release. The following items were fixed and/or added:

...

• Linux host and guest: Support kernel version 5.10 (bug #20055)