Alpha LX164 with voodoo 3000 PCI card - had it working fine on Debian. Using the xorg-x11 package; I used X -configure to generate a config file, changed the monitor sync ranges. I start X and get it running the BIOS (under emulation) and then get a black screen - exiting X with ctrl-alt-backspace gets me back to the console. I also see ELF_relocation errors - but that is also reported by others in a seperate bug with very different results. Reproducible: Always Steps to Reproduce: 1. X -configure to generate config file 2. X Actual Results: black screen Portage 2.0.50-r11 (default-alpha-2004.0, gcc-3.3.2, glibc-2.3.2-r11, 2.4.21-alpha-r12) ================================================================= System uname: 2.4.21-alpha-r12 alpha EV56 Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="alpha" AUTOCLEAN="yes" CFLAGS="-mieee -O2 -mcpu=ev56" CHOST="alphaev56-unknown-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mieee -O2 -mcpu=ev56" DISTDIR="/usr/portage/distfiles" FEATURES="ccache" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/ ftp://gentoo.inode.at/source/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alpha arts avi berkdb bitmap-fonts crypt cups encode foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl tcpd truetype voodoo3 xml2 xmms xprint xv zlib"
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.
