| IO | INFO | 10:13:36,495 | RED InitializeSdk with library path at /opt/resolve/libs | Main | INFO | 10:13:36,495 | Setting LsManager.3.DisplayGPUBusID = 96 | Main | INFO | 10:13:36,495 | Setting LsManager.3.DisplayGPUIndex = 0 | Main | INFO | 10:13:36,495 | Setting LsManager.3.DisplayGPUName = NVIDIA GeForce GT 640 Auto mapping, CUDA processing, main display not on external GPU. GPUs: 1 discrete, 0 integrated, 0 external. | Main | INFO | 10:13:36,495 | Only 1 NVIDIA display GPU found. | Main | INFO | 10:13:36,349 | GPU Name = 'NVIDIA GeForce GT 640', Main display = 1 | Main | INFO | 10:13:36,348 | Fallback process to detect main display has finished | Main | INFO | 10:13:36,294 | Process to detect main display has finished | Main | INFO | 10:13:36,266 | Detecting Main Display properties | Main | INFO | 10:13:35,950 | Updating display GPU information. Please see the entire log file "ResolveDebug.txt" :Ĭode: Select all | Main | INFO | 10:13:35,909 | Running DaVinci Resolve v16.0.0b.022 (Linux/Clang) | DVIP | INFO | 10:13:45,804 | Unable to load libcuda from /usr/lib64/libcuda.so opt/resolve/bin/BlackmagicRawAPI/libBlackmagicRawAPI.so: cannot open shared object file: No such file or directory opt/resolve/bin/libBlackmagicRawAPI.so: cannot open shared object file: No such file or directory "Let There Be CUDA Light, Done!!"in the log file suggests that the GPU is correctly detected, in spite of these error messages: Note that it does run under Windows 10 on the same computer. Trying to run Resolve 16.0b2 on Linux Mint 19.1, it crashes after the splash screen and displays the "Resolve quit unexpectedly" window. a new windows installation will always unsolicitedly wipe out the the linux boot mechanism, and you usually have to restore the dual boot capabilities manually by utilizing a rescue disks or sticks, etc. Sure - both bootup control mechnism can not coexist/work at the same time, but both are somehow able to boot the other operating system to some degree.īut if you for example install debian on a free partition or disk on your machine and an already existing windows partition or boot loader is found by the installer, you will still get the advice to install (=overwrite it by) grub2, but it will be automatically configured providing a working boot menu entry for windows as well - i.e. So Windows might disable grub or Linux might disable the equivalent Windows tools. Seth Goldin wrote:My understanding is that if you partition the one disk and have both Windows and Linux on the same one, the init systems will interfere with one another. it's a very powerful tool, but a little bit hard to master even for long term unix addicts. Modern linux distributions on standard PC hardware and X86 based server boards nowadays usually utilize grub2 for dual boot configuration and similar tasks. Installing resolve on one of this more common and very well working/documented standard distributions, isn't always trivial and straight forward, but it's IMHO easier to workaround all of resolves installer glitches, than to be trapped and handicapped by the shortcomings of BMDs provided base system otherwise. intels clear linux is another interesting but still rather uncommon choice, if you want a super optimized distribution, which in most benchmarks will have a significant lead. I'll never advice anyone to work with this horrible outdated, incomplete and inefficient installation media provided by blackmagic! a clean ubuntu/debian/mint installation is IMHO a much more promising user friendly and efficient base for serious migration to linux. how much freedom you have to control and customize the actual installation process. you can boot from your preferred boot images by this kind of emulation and evaluate how well it works resp. Perhaps you should try this installation scenarios within a save sandbox environment provided by virtual machines (virtualbox, qemu/kvm etc.).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |