thanks a lot for your work. So this
1. seems to be a completly new issue that was not known before
2. there is not even a way (to my knowledge) to prevent this as the boot options don't get propagated until module load time
so blacklisting it for the release looks like the best option.
Okay as I don't see a way to propagate the boot options to viafb could you please blacklist it for now and test whether
sudo modprobe viafb viafb_accel=0
behaves different? This will tell us whether this is a hardware acceleration problem (most likely) or not. I need only the result for one of those 2.6.32 or later kernels. Sorry but I need to locate the problem somehow. Thanks.
Hi Leo,
thanks a lot for your work. So this
1. seems to be a completly new issue that was not known before
2. there is not even a way (to my knowledge) to prevent this as the boot options don't get propagated until module load time
so blacklisting it for the release looks like the best option.
Okay as I don't see a way to propagate the boot options to viafb could you please blacklist it for now and test whether
sudo modprobe viafb viafb_accel=0
behaves different? This will tell us whether this is a hardware acceleration problem (most likely) or not. I need only the result for one of those 2.6.32 or later kernels. Sorry but I need to locate the problem somehow. Thanks.