Kernel – 5.1 Released, OK with latest NVIDIA, and Patched VMware
Kernel 5.1 is out, and brief details are here: http://lkml.iu.edu/hypermail/linux/kernel/1905.0/03532.html
The latest NVIDIA driver (430.09) and patched VMware 15.0.4 both compile and run OK.
One odd quirk, is that the behaviour of # make xconfig has changed, and if you have your custom configs saved out-of-tree, then the save option tries to save them back to the out-of-tree location again, rather than to the correct in-tree ~/.config file, as before.. Not sure this is a feature or bug, but it is certainly a nuisance!
Robert Gadsdon. May 5th 2019.
Sounds like intentional change which is part of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8741908b3e29
390.116 fails with kernel 5.1 Debian 9.8
Seems they are forcing video card update or returning to nouveau.
I did get the ‘5.1 fix’ to apply to 390.116 – see latest article.
RG.
I am getting an error with Fedora 30 and Workstation 14.1.7 and I cannot open Network Configuration to define my networks. When I run vmware-netcfg with sudo I get this:
No protocol specified
** (vmware-netcfg:14043): WARNING **: Could not open X display
No protocol specified
(vmware-netcfg:14043): Gtk-WARNING **: cannot open display: :0
If I try to open it with my own user, it says it cannot execute that without root. If I try to open the vmware-netcfg with sudo, I get the same error as above.
I have found this solution and it works fine but after reboot, I get the same situration: https://www.linuxquestions.org/questions/fedora-35/error-on-fedora-26-could-not-open-x-display-4175625820/
Does anybody else have this problem?
Humm… try “su -c” and then your command, for example
su -c ‘vmware-config.sh’
Use ‘ ‘ for safety if the path would have spaces or whatnot