The Lifebook P7010 that I have this bug on is configured with a single 512MB module.
So if UNR is not going to fix this, is it mesa or a driver that should be fixed? And if so, can we have this bug moved to that?
The Lifebook P7010 that I have this bug on is configured with a single 512MB module.
So if UNR is not going to fix this, is it mesa or a driver that should be fixed? And if so, can we have this bug moved to that?