Angus, I don't have an immediate answer for using fglrx but now at least I know what question to ask. Our dev team (Matthew actually) is aware of the BIOS problems and they were the ones who suggested testing with <4GB to confirm the problem, but in general they have seen the problem go away once the mobo vendor provides an upgrade that properly handles 4GB support.
That said, if the VESA driver works then it's possible that the problem is only related to (say) acceleration, in which case (a) disabling DRI on fglrx might help and (b) there's a good chance that one of the open drivers might work, and they would definitely give you reliable 1680x1050 operation.
So:
1. Try disabling DRI on fglrx - I don't have the option in front of me, hopefully someone can jump in.
2. Give radeonhd a try - I think you should be able to download a package for release 1.1 if you don't feel like downloading from git and building from source.
You should definitely be able to add 1GB back in (total 3GB) and the suggestion above about setting RAM to 4095K would also be worth tryng. Obviously continuing to look for mobo BIOS upgrades would be good too.
I don't think we have a good driver workaround for this particular BIOS issue but will check to see if anything new has turned up.
That said, if the VESA driver works then it's possible that the problem is only related to (say) acceleration, in which case (a) disabling DRI on fglrx might help and (b) there's a good chance that one of the open drivers might work, and they would definitely give you reliable 1680x1050 operation.
So:
1. Try disabling DRI on fglrx - I don't have the option in front of me, hopefully someone can jump in.
2. Give radeonhd a try - I think you should be able to download a package for release 1.1 if you don't feel like downloading from git and building from source.
You should definitely be able to add 1GB back in (total 3GB) and the suggestion above about setting RAM to 4095K would also be worth tryng. Obviously continuing to look for mobo BIOS upgrades would be good too.
I don't think we have a good driver workaround for this particular BIOS issue but will check to see if anything new has turned up.
Comment