![]() Ii libwayland-cursor0:amd64 1.18.0-1 amd64 wayland compositor infrastructure - cursor library Ii libwayland-client0:amd64 1.18.0-1 amd64 wayland compositor infrastructure - client library Ii libwayland-bin 1.18.0-1 amd64 wayland compositor infrastructure - binary utilities Ii libva-wayland2:amd64 2.7.0-2 amd64 Video Acceleration (VA) API for Linux - Wayland runtime Ii libqt5waylandcompositor5:amd64 5.12.8-0ubuntu1 amd64 QtWayland compositor library Ii libqt5waylandclient5:amd64 5.12.8-0ubuntu1 amd64 QtWayland client library Ii libkf5waylandclient5:amd64 4:5.68.0-0ubuntu1 amd64 Qt library wrapper for Wayland libraries Ii kwayland-integration:amd64 4:5.18.4.1-0ubuntu1 amd64 kwayland runtime integration plugins Ii kwayland-data 4:5.68.0-0ubuntu1 all Qt library wrapper for Wayland libraries - data files I can, however, SSH just fine into the server.īooting into it with no splash it is failing on Nothing has worked, all it does is after doing nomodeset or installing drivers, it will boot into said black screen right after it sets the hostname, even with nomodeset turned on. I have tried all sorts of solutions, I have Googled this and followed this issue for about a month now trying solutions when I have free time. The server does not have any form of Secure Boot options in its BIOS and it is installed through legacy BIOS since the server doesn't support UEFI. However, I would really prefer to fix this without having to completely reinstall, because of the amount of data I have on this server, it would take me hours to back everything up for a reinstall. I am entirely unsure what I should install to get the proper drivers or whether I should downgrade from the latest Ubuntu version and try that. The ones I installed were xserver-xorg-video-amdgpu and mesa-vdpau-drivers I do have the proprietary AMD drivers installed, which I installed trying to get my server to display on the monitor. I am completely unsure of what I should do to get my server to boot up. If installing the NVIDIA drivers messes up the OS (e.g.0e:0d.0 VGA compatible controller : Advanced Micro Devices, Inc. The BusID should match what the lspci command above returned. Option "AllowEmptyInitialConfiguration" "on" Mine looks like this: Section "ServerLayout" Modify or create the file /etx/X11/nf to specify that the NVIDIA GPU should be used for a secondary screen so that it has entries in nvidia-settings. ![]() Respond "no" when asked "Install NVIDIA accelerated Graphics Driver for Linux-x86_65 375.26?". It's important to download the "runfile (local)" file so that we can explicitly prevent from overwriting the driver that was just installed. NVIDIA-Linux-x86_64-375.26.run -no-opengl-filesĭownload the CUDA installation runfile from their website. Run the script with the option -no-opengl-files: sudo. Install the NVIDIA driversĭownload the driver installation runfile from their website (e.g. The solution is described in the answer from this post. This happened regardless if I installed the drivers from the "Additional Drivers" tab in "System Settings" or the ppa:graphics-drivers/ppa in the command-line. ![]() In my case, Ubuntu would get stuck in a login loop after installing the NVIDIA drivers. This was tested on a ThinkPad P70 laptop with an Intel integrated graphics and an NVIDIA GPU: lspci | egrep 'VGA|3D'Ġ0:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06)Ġ1:00.0 VGA compatible controller: NVIDIA Corporation GM204GLM (rev a1)Ī reason to use the integrated graphics for display is if installing the NVIDIA drivers causes the display to stop working properly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |