| Summary: | blank screen with 3dfx voodoo 3000 pci | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dr. David Alan Gilbert <gentoo> |
| Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | alpha |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | Alpha | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Log from starting X
Configuration file I used Log from starting X (6.8.99.15) |
||
|
Description
Dr. David Alan Gilbert
2004-09-19 10:54:02 UTC
Created attachment 39925 [details]
Log from starting X
Created attachment 39926 [details]
Configuration file I used
Can you reproduce this with >=6.8.99.15, or with 6.8.2 on USE=dlloader? Please reopen if so. Created attachment 71209 [details]
Log from starting X (6.8.99.15)
Still does it on 6.8.99.15 from a emerge --verbose =x11-base/xorg-x11-6.8.99.15-r4 What happens when you try and start X as root? The last line in attachment of the 6.8.99.15 config makes me think that perhaps xdm/gdm/kdm is not allowing your X client to talk to your X server. Starting things as root to see if it even comes up may work around this. (In reply to comment #6) > What happens when you try and start X as root? The last line in attachment of > the 6.8.99.15 config makes me think that perhaps xdm/gdm/kdm is not allowing > your X client to talk to your X server. Starting things as root to see if it > even comes up may work around this. (Suggest close). Nope wasn't that - xlsclients showed stuff running - but I have found it. It was just trying to run in too high a mode for something - it was in the range of the monitor sync's. I found it with an xvidtune -show and it showed it running at 2048x1536 (at 95KHz/60Hz) - 266MHz dot clock; knocked it down to the next one down and it was fine. I'm still not sure why it didn't show anything (completely black); the board specs seem to suggest the DAC is 350MHz, I did find in the X logs the line: (II) TDFX(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 110 kHz, PixClock max 240 MHz Now I think that is coming from the id read of the monitor? If so it looks like the driver was ignoring the max pixclock of 240MHz - although I still don't know why this left it fully blank since I assume it is something that a CRT monitor can't actually detect. I suggest this is closed - unless someone else finds a problem at that type of clock rate. Since it seems to have been a configuration issue, I'll close as INVALID. If someone finds this to be an issue with the driver feel free to let us (or upstream) know. |
