Now Advanced Options > Recovery > dpkg Repair.Īnd wow, it revived the system with the 396.26 driver!Īfter failures I went back from Ubuntu 18.04 (chosen as it’s the new LTS and it has the most recent Kernel 4.15 - to be on the safe side for eGPU support problems with Wayland and Snappy)… As the installation was ***** up anyway it couldn´t get worse, so I went for it and commented out several IFs around timeout=30. So as remedy I wanted to edit /etc/default/grub, but as this was not the active system and I couldn´t run update-grub on it afterwards I had to go for /boot/grub/grub.cfg directly. ![]() ![]() Decided to dig into GRUB AND boot repair.Īlways had wondered why some of my Linux installations didn´t show a boot menu and occassionally went on my *ss by stating that timeout = 0 is no longer supported (or so). So it was the old story again: Help yourself to get help. and the step back to 17.10 (Wayland default trap) because 18.04 (Xorg default) is not yet supported for CUDA. So regarding the Kernel supporting Thunderbolt 3, after days of reading up and weighing the merit of the posts I learned that there is sth like Ubuntu LTS or Hardware Enablement Kernels which let me stay on 16.04 with the minimum 4.13 Kernel for TB3 in 16.04.4.Ĭould have avoided the callow / immature Snappy and Wayland BS, etc. One should think that things get better / easier with technological advances, but when I look at the NUC BIOS it’s intimidating. I could have started to compile a new Kernel for Ubuntu 16.04 or try 18.04. On the Dell the Ubuntu 18.04 is just a trial, but on the NUC6i7KYK with the Thunderbolt 3 HP Omen Accelerator eGPU I needed a more recent Ubuntu / Kernel for the TB3 eGPU to get recognized. Worse, when I wanted to send the bug report it said “It´s not ours. It´s “interesting” that there is no official support for the overwhelmingly important Linux MONTHS after release. #2 hang w/ eGPU on “started gnome display manager and dealing with any system changes” still waiting for solution (will start new thread) Under the password in the cogwheel switch to “Ubuntu on Xorg” #1 took me “just” an hour or two, not calculating the additional installs and configs: With the eGPU off I get to the login. The procurement issue is more that the corporate structure that I am beholden to could take an unnecessarily long time to make a licence happen, and I was wondering if there was an easier way to accomplish this with the tools I have available.Edit1: toned down: From decades of experience: More often than not things work though “not supported”.Īctually it turns out supported 17.10 chokes as well with at least two Canonical snake-pit idiosyncrasies: Running the build using Nvcc.exe (through cmake) produces the error " Cannot find compiler cl.exe in path ", which I assume is something relating to the integrations, as it works fine with the full IDE. ![]() ![]() My problem is that the whole rest of the project is built with VS2019 compilers and without the IDE, the CUDA install cannot install the Visual Studio integration scripts. This is how all the other C++ builds are currently done for windows in this environment, with no full IDE Visual Studio installation. These Build Tools allow you to build Visual Studio projects from a command-line interface. By MSVC build tools I meant “Build Tools for Visual Studio 2019”. For context, I am porting a linux CUDA application over to Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |