From: Giorgio T. <de...@ip...> - 2002-10-12 09:58:00
|
Alle 14:50, venerd=EC 11 ottobre 2002, Michel D=E4nzer ha scritto: > Will these modifications also work with older firmware or whatever make= s > the difference? Oops, you're right, i haven't tried this, i will try it (downgrading the=20 firmware) this weekend.=20 Test results will follow. > > The warbled text problem i signaled succedes only in the X text windo= ws > > as Xterm or Mozilla and so on. I think this is a driver's limitation > > because with 1024x768x16 resolution this succedes only when the machi= ne > > is very stressed but with 1152x864x16 and over this succedes everytim= e i > > open a window. With these high resolutions it warbles also the graphi= cs. > > Sounds like bus contention and/or synchronization problems in the 2D > acceleration code. I think that what you are saying is also (or something near) the reason why the framebuffer crashes after a vterm exchange from X . Is it possible that X is not signalled to release its resources and go to= =20 sleep ? The few times that i am able to exchange vterms, X is completely killed=20 (also its child tasks) by the system and the Xdm task that remains alive is not able to re-open another X task.=20 I can test it, could you suggest me where to put the hands :-) ? Regards Giorgio Post Scriptum. In my last mail i forgotten to say that after the migration of my Linux=20 partitions from IDE to SCSI hdisks, a strange bug seems disappeared: Sometimes, when connected to internet and using X, something hanged the X task or the whole machine. Now seems solved... (I cross my fingers... :-) ). |