nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   startx problem "screen found, but none have usable configuration." (http://www.nvnews.net/vbulletin/showthread.php?t=12191)

rawkstar59 05-21-03 02:15 PM

startx problem "screen found, but none have usable configuration."
 
When I startx, it gives me an error that says "screen found, but none have usable configuration."

When I "lsmod", i can see that the "NVdriver" is loaded (but nothing is "using" it)...so i'm assuming that its not a kernel source problem.....or is it?

XFree86 Version 4.1.0.1 / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: 21 December 2001
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems. (See <http://www.XFree86.Org/FAQ>)
Build Operating System: Linux 2.4.17 i686 [ELF]
Module Loader present
(==) Log file: "/var/log/XFree86.0.log", Time: Wed May 21 12:31:54 2003
(==) Using config file: "/etc/X11/XF86Config-4"

(II) Setting vga for screen 0.
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
compiled for 4.1.0.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.4
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xE0000000
(--) NVIDIA(0): MMIO registers at 0xEC000000
(WW) System lacks support for changing MTRRs
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

----------------------------------


Using Debian 3.0, kernel 2.4.20 Don't know why it says 2.4.17 in the log file; Could I be loading the driver in the wrong kernel? I did compile a new one a few days ago, but that was from 2.2.16 (I think).

Using the nForce mother board which has the vidcard intergrated.

Using this driver: http://www.nvidia.com/view.asp?IO=l...y_ia32_1.0-4363 <http://www.nvidia.com/view.asp?IO=li..._ia32_1.0-4363>

Hope thats enough information.
I'll take ANY suggestions!

bwkaz 05-21-03 05:00 PM

If NVdriver is loaded, then your driver update didn't finish successfully. The kernel module is no longer named NVdriver in drivers 4191, 4349, or 4363; it's now named just "nvidia"(.o, but the .o should be ignored in modprobe or insmod commands) instead.

Try to modprobe nvidia (as root, obviously) -- if you get a module not found error, then rerun the installer, and make sure you check the nvidia-installer.log when you're done. The installer should delete the old NVdriver kernel module for you, so it almost sounds like it didn't even start up correctly.

It says 2.4.17 in the log file because that's the build operating system, not the version it's running under. It just means that whoever (at Debian) built the XFree86 package, was using kernel 2.4.17 at the time -- it shouldn't matter.

rawkstar59 05-21-03 06:22 PM

ok, now I'm getting somewhere....

When I insmod or modprobe, it says this: nvidia.o:init_modulesevice or resource busy. Incorrect module paramters, irq or i/o

I tried inserting the irq of my vid card when i insmod, but it says "invalid parameters".

Does anyone know how I can fix this?

bwkaz 05-22-03 05:54 PM

You can try turning PnP OS off in your BIOS.


All times are GMT -5. The time now is 12:11 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.