Re: xserver-xfree86 4.0.2-1 and S3 ViRGE/MX problems
Robert Norris wrote:
>
>
> > Okay, that rules out a couple obvious possibilities. I've put up a
> > purely test version on my page (ver 1.6.2) which does incremental
> > startup, pausing for a couple seconds at various points in the init.
> > sequence. Would you give it a try and post or mail me the log? Wait
> > about 30 seconds before killing the machine if it appears to lock,
> > that's how long it takes to start with the added delays on my machine.
>
> Log file is up .. no change that I can see though.
>
> Regards,
> Rob.
>
Yeah... Thanks for all the testing. I shouldn't have assumed the
lockup was later in the init sequence. Ready for another round?
There's a new version up on my web page (ver 1.6.3). It's another
incremental start version which _will_ show a difference in the log. (I
promise!) Would you try it out? It takes a little longer to start
fully, ~4 seconds, so allow 30-35 total.
After trying it normally, add
Option "s3v_debug" "1"
to your driver section and let me know if that makes any difference. (I
don't need to see logs for this or the next case. Although you'll
notice this disables the register dump diagnostic printouts in the log.)
If no improvement, try Option "s3v_debug" "2". This disables a
different printout, which is printing register which don't exist on the
MX.
--
Kevin
Reply to: