Page 1 of 1

Stuck in Software Rendering Mode - driver not loaded?

Posted: Sun Apr 01, 2018 9:04 pm
by Fahrenheit
I've had a Fitlet-iA10 for a couple years, running on Linux Mint 17.3. I followed the instructions on the wiki to load the RadeonSI driver, and hardware acceleration and everything else worked fine.

However recently, something happened and the driver doesn't appear to be loaded properly. When I log in, I get a message saying "Running in software rendering mode." I've tried uninstalling\reinstalling the drivers from the wiki, tried installing Mate, neither of which worked. Some troubleshooting info:
mint_driver_manager.png
mint_driver_manager.png (166.5 KiB) Viewed 34364 times

Code: Select all

fahrenheit@fitmint:~ $ inxi -Fx
System:    Host: fitmint Kernel: 4.4.0-116-generic x86_64 (64 bit gcc: 4.8.4) Console: tty 0
           Distro: Linux Mint 17.3 Rosa
Machine:   System: CompuLab product: sbc-flt1 v: 1.2
           Mobo: CompuLab model: fitlet v: 1.0 Bios: American Megatrends v: SBCFLT_0.08.08 date: 11/30/2015
CPU:       Quad core AMD A10 Micro-6700T APU+AMD Radeon R6 Graphics (-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 9582
           clock speeds: max: 1200 MHz 1: 1000 MHz 2: 1200 MHz 3: 1000 MHz 4: 1000 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R6 Graphics] bus-ID: 00:01.0
           Display Server: X.org 1.17.1 drivers: fbdev,ati (unloaded: vesa,radeon)
           tty size: 120x30 Advanced Data: N/A out of X

Code: Select all

fahrenheit@fitmint:~ $ lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R6 Graphics] (rev 02)

Code: Select all

fahrenheit@fitmint:~ $ find /dev -group video
/dev/fb0

Code: Select all

fahrenheit@fitmint:~ $ glxinfo | grep -i vendor
Error: unable to open display

Code: Select all

fahrenheit@fitmint:~ $ vainfo
libva info: VA-API version 0.35.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit

Code: Select all

fahrenheit@fitmint:~ $ vdpauinfo
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
display: :0   screen: 0
Tried manually setting environment variables in /etc/environment:

Code: Select all

LIBVA_DRIVER_NAME="radeonsi"
VDPAU_DRIVER="radeonsi"
Then get this:

Code: Select all

fahrenheit@fitmint:~ $ vdpauinfo
Error creating VDPAU device: 23
display: :0   screen: 0
Any ideas on how else I can troubleshoot this and get hardware acceleration working again?

Re: Stuck in Software Rendering Mode - driver not loaded?

Posted: Wed Apr 04, 2018 1:48 pm
by tamir
We are investigating this and get back to you asap.

Thank you.

Re: Stuck in Software Rendering Mode - driver not loaded?

Posted: Sun Apr 08, 2018 5:34 am
by Denis
Hi,
Please follow the updated wiki:
http://www.fit-pc.com/wiki/index.php/AM ... ux_Mint_18

Denis

Re: Stuck in Software Rendering Mode - driver not loaded?

Posted: Tue Apr 10, 2018 7:11 pm
by Fahrenheit
This seems to be a step in the right direction. Since I'm running Linux Mint 17.3, I had to load other dependencies before running the new commands, but I got them installed. Now when I reboot, it seems to detect the monitor and makes the text small. But the graphical UI never loads. If I login and type: sudo startx, it loads a black screen with a mouse cursor.

Some of the options return different results now:

Code: Select all

fahrenheit@fitmint:~ $ vainfo
error: can't connect to X server!
libva info: VA-API version 0.35.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit

fahrenheit@fitmint:~ $ vdpauinfo
vdpauinfo: cannot connect to X server 
Any ideas? Thanks!

Re: Stuck in Software Rendering Mode - driver not loaded?

Posted: Wed Apr 11, 2018 7:53 am
by tamir
you could either update the kernel, or install a newer distribution.