Yes, I know that the criteria used to enable the workaround in gnome-power-manager probably does detect every variation of the MSI Wind U100. It use the same criteria as the patch to hal-info proposed in comment #95.
As I said, a correct correction would be to move the dection in xrandr, configurable by a config file, and this configuration file should be derived from the hal-configuration (of xrandr should query hal).
So what is also needed is a survey of affected hardware and the associated criteria that can be used to identify them. This bug tracking is probably not the right place to do it, a wiki page may be more appropriate.
@Kychot
Yes, I know that the criteria used to enable the workaround in gnome-power-manager probably does detect every variation of the MSI Wind U100. It use the same criteria as the patch to hal-info proposed in comment #95.
As I said, a correct correction would be to move the dection in xrandr, configurable by a config file, and this configuration file should be derived from the hal-configuration (of xrandr should query hal).
However, concerning your mivvy m310, this wouldn't solve the problem, as the hal information does not set the "laptop_ panel.brightnes s_in_hardware" property. You can see the lastest hal configuration file here : http:// cgit.freedeskto p.org/hal- info/tree/ fdi/information /10freedesktop/ 10-laptop- panel-hardware. fdi
So what is also needed is a survey of affected hardware and the associated criteria that can be used to identify them. This bug tracking is probably not the right place to do it, a wiki page may be more appropriate.