On Thu, Feb 06, 2003 at 03:31:44PM +0100, Kai Lorenz wrote:
> thank You very much for Your patience.
No problem. Once I've got the data I need, it is often easy to help.
> I'm sorry for being inconvenient but I'm a newbie and try to use the
> information I've got. My german DEBIAN manual seems to be a little bit
> cryptic in explaining how to construe a bug report.
Hmm, you might want to complain to the authors/translators of that manual,
then. :)
> My ISDN card isn't yet > properly installed on Linux so I can't use the
reportbug routine.
My condolences. I know how painful it is to not have net access.
> Problem: When calling startx or xdm or similiar X routines the monitor is
> flickering three times and afterwards I get an error report: "Screen(s)
> found, but none have a usable configuration." I've attached the
> corresponding XFree86.0.log.
>
> Configuration: The configuration of my monitor, video card and mouse may be
> seen at the XF86Config-4 file attached too.
Yes, thank you for sending it along.
> Remarks:
> 1. The video card "ELSA Erazor III LT" and the monitor "Medion MD 1772JC"
> work very well on WinNT4.0 SP6 at 1024x768, 85 Hz, 65536 colours.
Sounds fine. This card is supported as far as I know.
> 2. The X server has been installed by using 'tasksel'.
Also fine.
> 3. I set the bus id to "PCI:01:00:00" because the 'lspci' routine told me
> it has found a "nVidia" driver at "01:00.0". In the attached log file You
> will see that the video card chip "RIVATNT2" has been found there. This is
> the correct one for an "ELSA Erazor III LT".
This was probably unnecessary. Generally the X server can find the card on its
own. The only exceptions I know of are some (not all) NewWorld
PowerMacs.
> 4. I've chosen the "nv" driver corresponding to
> http://www.xfree86.org/4.1.0/nv.4.html .
This is the correct choice as far as I know.
> I hope I've made it a little bit better than before. If not please be so
> kind as to let me know.
Yes, much. I think I may know what your problem is.
Here is your Device section:
Section "Device"
Identifier "ELSA Erazor III LT"
Driver "nv"
BusID "PCI:01:00:00"
VideoRam 32768
Option "UseFBDev" "true"
EndSection
I don't think any of the last 3 lines are necessary, and I suspect the
last:
Option "UseFBDev" "true"
is what is causing you trouble. If your kernel is not using the
framebuffer console, this simply will not work. Try commenting out this
line, or running "dpkg-reconfigure xserver-xfree86" and disabling it.
Then try to start the X server again.
If you *are* using a framebuffer console, the following command will
return some information, instead of failing or returning nothing.
cat /proc/fb
The VideoRam setting is likely also unnecessary; generally the driver
("nv") can autodetect the amount of RAM on the video card. Again, you
can comment this out or use "dpkg-reconfigure xserver-xfree86" to
disable it (by entering a blank value).
And as I stated above, the BusID is likely also unnecessary, and will
only cause you grief if you change which slot the card is in. Again,
you can comment this out or use "dpkg-reconfigure xserver-xfree86" to
disable it (by entering a blank value).
--
G. Branden Robinson | If a man ate a pound of pasta and a
Debian GNU/Linux | pound of antipasto, would they
branden@debian.org | cancel out, leaving him still
http://people.debian.org/~branden/ | hungry? -- Scott Adams
Attachment:
pgp9GKqxmTd7L.pgp
Description: PGP signature