Taketoshi Sano <[EMAIL PROTECTED]> writes: > Maybe another C&T driver problem. Trying 4.0.1e, or rebuild with DEBUG > defined of chips_drv.o and libvgahw.a from the source would be recommended > in order to track the cause of this problem.
What is 4.0.1e? Does it have relevant fixes for C&T chips? Dan
