Rob Taylor writes:
> attached is 2 possible outputs of scanpci -v
> 1st is before running server
> 2nd is after!
>
>
> the server hangs waiting for a vertial retrace before reading ddc1, and
> needs to be SIGSEGV'd.
> the trace from the xserver, verbose 10 is also attached
I had this happen to me too, once, however it turned out to be a
HW failure. After I commented out this code I ran into other problems.
You may comment out this code for testing, however one should try to
understand why this code is causing problems.
>
> so I correct myself. looks like its nothing to do with the kernel
> framebuffer driver. it mroe to do with the state the card gets left in after
> being half configured *phew*!! so thats makes life a bit easier - i just
> need to fix the card configuration!
>
This should not happen. It can only happen when the Xserver has the
ROM BIOS mapped. Judging from your log that shouldn't happen.
Can you find out where it happens? You can hardcode a test for the
relevant PCI config space register and PCI tag in the appropriate
PciWrite() function and call a function you can breakpoint from gdb.
There are three functions for this purpose: xf86Break1/2/3().
Cheers,
Egbert.
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
