Sorry for the trouble but viafb is currently undergoing heavy changes and as only a few people test -mm (resulting in only a very limited variety of VIA boards getting tested) and the datasheets are not as good as they could be these issues can't be avoided at the moment.
Just a word from the viafb maintainer: git.kernel. org/?p= linux/kernel/ git/torvalds/ linux-2. 6.git;a= commitdiff; h=97922b5462fa5 43484831d42ab0f e4562b9373fc git.kernel. org/?p= linux/kernel/ git/torvalds/ linux-2. 6.git;a= commitdiff; h=8a3a95c32f612 068be8dae74fa5f c4cf2db1592e git.kernel. org/?p= linux/kernel/ git/torvalds/ linux-2. 6.git;a= commitdiff; h=0b94190e1e60f 96962b82d35729d 7d44cf298ef8
This sounds like a known problem, fixed by
http://
(or alternatively by disabling hardware acceleration in viafb via the module parameter viafb_accel=0)
some other (less critical) hardware acceleration issues are
http://
http://
Sorry for the trouble but viafb is currently undergoing heavy changes and as only a few people test -mm (resulting in only a very limited variety of VIA boards getting tested) and the datasheets are not as good as they could be these issues can't be avoided at the moment.