Done. But I used Mousepad (sudo mousepad /etc/default/grub), I know how to edit configuration files, thank you very much for your patience and instructions :)
dmesg-2.txt (105 KB)
Looks like a corrupted vbios, nouveau is complaining about bad checksum, header and signature. So the nvidia driver is probably rejecting it.
You can remove the nouveau debug entry from grub and run update-grub now.
Really fixing this would involve fixing the vbios and reflashing it, maybe using some OC’s tools and even a hardware programmer. That’s beyond my knowledge and interests.
But maybe the workaround is useable, try to load it using nvafakebios. The tricky part is that the vbios has to be loaded before the nvidia driver is (re-)loaded. Build instructions:
[url]https://github.com/envytools/envytools[/url]
Steps to test then would be:
install nvidia-drivers and nvidia-modprobe
disable X (systemctl disable display-manager or maybe lightdm)
reboot
You should be at text console
log in, get a root shell
modprobe -r nvidia
check if nvidia modules really are unloaded (lsmod)
nvafakebios vbios.rom (the file you extracted earlier)
modprobe nvidia
systemctl start display-manager (or lightdm)
Hope the nvidia driver accepts the vbios and X comes up…
- How to install envytools ? I have tried, but have had no success.
- Maybe, we can fix nouveau ? How this nvafakebios can be useful in this case ?
- I don’t find any manuals, instructions how to use envytools. Is it a unique project or maybe there are similar software ?
https://github.com/envytools/envytools
contains build instructions, scroll down a bit. You have to git clone it first, of course.
envytools are unique
Description of tools in nva directory, also scroll down a bit:
https://github.com/envytools/envytools/tree/master/nva
short version:
https://gist.github.com/karolherbst/4341e3c33b85640eaaa56ff69a094713
Envytools are not needed for nouveau, maybe the shadowfb option will improve your experience:
Either create a xorg.conf with that device section or put a file containing it into /etc/X11/xorg.conf.d
Section "Device"
Identifier "NvidiaGraphics"
Driver "nouveau"
Option "ShadowFB" "1"
EndSection
This xorg file crashed system (black screen).
xorg.conf.zip (824 Bytes)
‘Identifier’ and ‘Driver’ line is twice in it.
Did that xorg.conf work before you added the extra lines?
As you know there is no xorg.conf by default, I created xorg.conf for my experiments with graphics. Yes, it was ok.
So you needed to add just the shadowfb line. Does that alone crash the xserver?
Man ! Looks like artifacts disappeared ! It’s so cool. I tried to enable hardware acceleration in Chromium, but such applications like Blender, TuxRacer are working very slow. What’s a trick ?
xorg.conf.zip (626 Bytes)
attach output of glxinfo and /var/log/Xorg.0.log
Done
glxinfo_xorg.0.log.zip (11.4 KB)
Software rendering is active. Maybe there are leftovers from the nvidia driver, what’s the output of
ldd /usr/lib/libGL.so
Might also come from the shadowfb option. Please attach a Xorg.0.log while running without it.
Just checked, shadowfb option disables 3d accel.
No chances, because i used system restored from backup, which has’t any traces from nvidia installer.
I did’t find this file /usr/lib/libGL.so .
- I moved my xorg.file with enabled shadofd optin from /etc/X11 to /home/user
- Attached Xorg.0.log
Xorg.0.log.zip (6.65 KB)
Fantastic !
I couldn’t install envytools.
CMakeOutput.log.zip (3.89 KB)
The cmakeoutput.log just contains what worked, need the cmakeerror.log to see whats wrong.
Compiles fine on my system.
What about Xorg.0.log ?
nikolay@nikolay-Lenovo-IdeaPad-Y550:~/downloads/envytools-master$ cmake . -G Ninja
– The C compiler identification is GNU 6.3.0
– The CXX compiler identification is GNU 6.3.0
– Check for working C compiler: /usr/bin/cc
– Check for working C compiler: /usr/bin/cc – works
– Detecting C compiler ABI info
– Detecting C compiler ABI info - done
– Detecting C compile features
– Detecting C compile features - done
– Check for working CXX compiler: /usr/bin/c++
– Check for working CXX compiler: /usr/bin/c++ – works
– Detecting CXX compiler ABI info
– Detecting CXX compiler ABI info - done
– Detecting CXX compile features
– Detecting CXX compile features - done
CMake Error at /usr/share/cmake-3.7/Modules/FindPackageHandleStandardArgs.cmake:138 (message):
Could NOT find FLEX (missing: FLEX_EXECUTABLE)
Call Stack (most recent call first):
/usr/share/cmake-3.7/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.7/Modules/FindFLEX.cmake:219 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
easm/CMakeLists.txt:4 (find_package)
– Configuring incomplete, errors occurred!
See also “/home/nikolay/downloads/envytools-master/CMakeFiles/CMakeOutput.log”.
CMakeOutput.log.zip (3.35 KB)
The xorg.log just confirmed that the shadowfb option disables hardware acceleration.
So using nouveau, you can only choose between having a distorted screen or slow 3d.
Concerning envytools, you don’t need to use ninja.
Just download sources, open terminal, then
cmake .
make
The error just says that you have to install flex.
- I installed (probably) envytools, i’m an idiot because before that is needed to install dependencies (bison, flex e.t.c.). Well, how can i check this out ? I mean that the envytools installed ?
- lsmod . Which parameter have i to see ? I have got a photo of the list.
- When i tried to run nvafakebios vbios.com - command not find.
- I removed nvidia. sudo apt-get remove --purge nvidia-*