In some of OEM's AMD platforms,
open "System setting"->"Details"->"Graphics" from control center,
find the Graphics Driver show VESA: XXXXXX strings ,
not as accurate as what glxinfo -l | grep "OpenGL renderer string" shows.
The "VESA:XXXX" string displayed in "System Settings-->Details->Graphics" was because unity-control-center will find the driver information via:
(1) parse /var/log/Xorg.0.log and find "VESA VBE OEM Product:" String
(2) if (1) is not found, parse the result of "glxinfo -l" and find "OpenGL renderer string", and use this info as the string being shown.
There're some of AMD's fglrx driver will show "VESA VBE OEM Product: XXXXX" string in /var/log/Xorg.0.log,
I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control.
Curently this "VESA:XXXXX" string instead of the more accurate string from glxinfo was being shown in the panel.
I think Use glxinfo's information (when available) first is more accurate.
A private bug is filed at: https://bugs.launchpad.net/bugs/1369859
A merge proposal is submitted.
In some of OEM's AMD platforms,
open "System setting" ->"Details" ->"Graphics" from control center,
find the Graphics Driver show VESA: XXXXXX strings ,
not as accurate as what glxinfo -l | grep "OpenGL renderer string" shows.
The "VESA:XXXX" string displayed in "System Settings- ->Details- >Graphics" was because center will find the driver information via:
unity-control-
(1) parse /var/log/Xorg.0.log and find "VESA VBE OEM Product:" String
(2) if (1) is not found, parse the result of "glxinfo -l" and find "OpenGL renderer string", and use this info as the string being shown.
There're some of AMD's fglrx driver will show "VESA VBE OEM Product: XXXXX" string in /var/log/ Xorg.0. log,
I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control.
Curently this "VESA:XXXXX" string instead of the more accurate string from glxinfo was being shown in the panel.
I think Use glxinfo's information (when available) first is more accurate.
A private bug is filed at: https:/ /bugs.launchpad .net/bugs/ 1369859
A merge proposal is submitted.