** Description changed: 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 + Private bugs were filed at: + https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted.
** Description changed: 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. Private bugs were filed at: - https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 - A merge proposal is submitted. + A merge proposal is submitted at https://code.launchpad.net/~timchen119 + /unity-control-center/unity-control-center.lp1417034/+merge/248220 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for "Details" -> "Overview" -> "Graphics" info in control center. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in unity-control-center package in Ubuntu: New Bug description: 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. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted at https://code.launchpad.net/~timchen119/unity-control-center/unity- control-center.lp1417034/+merge/248220 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
