[graphics/generator_*] Tests did not check graphic driver before testing

[Yung Shen]

After hybrid graphics system installed the proprietary graphic driver,
In most case, proprietary graphic driver will loaded by default.
In order to use inegrated graphic (UMA) may requires manual switch.

But current generated local jobs follows the order based on the information given by udev_resource,
that means the index are different from systems, this also means checkbox will not know which graphic driver is currently being tested.

To have addtional graphic driver check will also help to avoid unexpected situation,
eg. Nvidia optimus disabled in BIOS setting or AMD Discricte got disabled on Intel platform.

[Zygmunt Krynicki (zyga)]

Assigning to Sam as he's working on the GPU tests now.

[Po-Hsu Lin (cypressyew)]

Hello Yung,

Do you mean that:
On a I+N platform with proprietary driver installed and running on the nVidia GPU, but the Intel GPU got index 1 as given by the information from udev_resource.
And base on our current test plan, user will be ask to test the GPU with index 1 first, causing the issue that you mentioned here?
(Do we have a sample for this?)

BTW, I am curious that if the discrete card got disabled in the BIOS, will it still be detected in udev?

[Yung Shen (kaxing)]

Please allow me to rephrase my concerns back in 3months ago:

To prevent tester to execute graphic job that is generated for performance mode on power-saving mode, vice versa.

On hybrid graphics system, will generate job like this: 1_FirstGraphic_1st_job, 2_SecondGraphic_1st_job, in a linear ordering, and only being distinguish by a switch_card job, so if anything happen then messed up graphic mode settings, it would be a nice to have a way to help tester avoid testing on wrong graphic chip.