The bug is still marked new...has the latest driver fixed the problem, or was it confirmed that it does not run on the PANV1?
The bug is still marked new...has the latest driver fixed the problem, or was it confirmed that it does not run on the PANV1?