When I upgraded from xfree86-4.3.99.12 to 4.3.99.15, the display acted real strange, with what seemed like random graphical bits thrown all over the screen, and random graphical behavior. This is a rendering error in the "via" driver that is used for Nehemia M-10000 ITX boards. Thanks to Alan, the fix found at his site at http://www.linux.org.uk/via.tar.gz, and some hacking of the xfree-4.3.99.15.ebuild (adding the extra source and basically copying the SiS driver handling), it all now works perfectly. Just a tip if others look here.
Created attachment 20303 [details, diff] Just to show the (fugly) addition to the ebuild-script for the "via" driver
If you care to attach a patch against the 4.3.99.15 via driver, I would be happy to add it to the patchset.
The patch is not mine, but I downloaded it from the site stated in the original bug-report. From what I understand, this will be added to the 4.3.99.16 version of X (though I may have misunderstood Alans comments about the subject on xfree.org). The attachment I provided was merely an attempt to show what I did to get emerge to correctly download and build the xfree-4.3.99.15 with a working driver. My main aim of reporting this was to provide a way for other users of the Nehemia M10000 boards to upgrade to xfree-4.3.99.15 without getting weird-looking graphics thanks to the faulty driver contained in xfree-4.3.99.15.
4.3.99.16 is in portage. Please reopen if the issue is not fixed.
(Finally) Managed to install xfree-4.3.99.16 and also tested 4.3.99.902. In xfree-4.3.99.16, the same rendering problems as in the "unpatched" version of xfree-4.3.99.15 are evident, and the patch does not work (build fails). Xfree-4.3.99.902 doesn't work with mplayer. Whatever I do, it locks up the machine completely when QUITTING the mplayer, or when the movie is over. Playback of the movie itself works perfectly. Also tested with a fresh copy of xine, but the same problem was evident with it. Currently re-installing xfree-4.3.99.15 with the patch...
There were large numbers of commits to the via driver after 4.3.99.902. I suggest you wait for the next release/snapshot or build from current CVS and see what happens.
OK, that's what I'll do. I've got a working installation, so there's hardly an emergency... :-) Thanks for the reply. /Magnus
