nVidia driver problem with MDK10 OE

June 24, 2004

I have managed to get a dual boot MDK10 OE and Win98SE installed on a system comprising of:-

Athlon 2000+,

ECS 741GX-M mobo

512Mb PC2100 RAM

GeForce4 MX 420

2x 40Gb HDDs

SB PCI128

USB wireless mouse.

I installed everything I could from the 4 CDs,

set up the system to boot to the command line,

read the FAQ on this site regarding nVidia driver installation,

installed the nVidia linux 5336 driver (it had to rebuild a module as it said I did not have a stock kernel),

used the emacs editor to edit the XF86Config-4 file as instructed by the nVidia readme file, and the rebooted the PC.

After logging in to the command line as a normal used, I typed in "kde" ( I proved that this would work prior to installing the driver) at which point the screen went black and nothing except the off and reset switches would do anything.

The last time I saw this type of problem was with Win98SE and an Alladin V chipset when I installed the then latest nVidia drivers without first installing the required AliGart.vxd file.

I can't get to try glxgears 'cos I can't boot KDE.

Is this an AGP/GART problem ?

Can anyone help ?

Ixthusdan · June 24, 2004

Instead of using the kde execute, type "startx" and tell us what the error report looks like.

bvc · June 24, 2004

use;

startx

instead of;

kde

what are the errors?

GreenBandit · June 24, 2004

Unfortunately there are many lines that briefly appear befor the screen goes black, but they are too fast to see. I tries slowing down the FSB but it still did not let me read what appeared before the screen went black, it was that fast.

Is there a log file that will give the required info, or another way forward ? :help:

illogic-al · June 24, 2004

the file is ~/.xsession-errors where ~ = you home directory

cat ~/.xsession-errors | less

will print it to screen in a console.

You can always open it with Kwrite or some other GUI editors. Just make sure that View hidden files is selected in the File Browser.

Edited June 24, 2004 by illogic-al

bvc · June 24, 2004

When the screen goes black can you do Ctrl+Alt+F1 and see the errors?

The log file you want is

/var/log/XFree86.0.log

Edited June 24, 2004 by bvc

GreenBandit · June 25, 2004

I can't boot in to the GUI, so I don't know how to get to any GUI editor

The XFree86.0.log file is attached to this post - it was formatted better when viewed on the linux machine using "cat", but on this W98 machine it is not very clear.

Does it give any clues as to the problem ?

I have attached the file, but can't see it on the preview, so here is the end of it (posting it all exceed the no of emoticons allowed )

(II) Loading extension GLX

(II) LoadModule: "nvidia"

(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o

(II) Module nvidia: vendor="NVIDIA Corporation"

compiled for 4.0.2, module version = 1.0.5336

Module class: XFree86 Video Driver

(II) LoadModule: "mouse"

(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o

(II) Module mouse: vendor="The XFree86 Project"

compiled for 4.3.0.1, module version = 1.0.0

Module class: XFree86 XInput Driver

ABI class: XFree86 XInput driver, version 0.4

(II) v4l driver for Video4Linux

(II) NVIDIA XFree86 Driver 1.0-5336 Wed Jan 14 18:30:46 PST 2004

(II) NVIDIA Unified Driver for all NVIDIA GPUs

(II) Primary Device is: PCI 01:00:0

(--) Assigning device section with no busID to primary device

(--) Chipset NVIDIA GPU found

(II) resource ranges after xf86ClaimFixedResources() call:

[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX(B)

[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MXE(B)

[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX

[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX

[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX

[5] -1 0 0xe3003000 - 0xe3003fff (0x1000) MX

[6] -1 0 0xe3002000 - 0xe3002fff (0x1000) MX

[7] -1 0 0xe3001000 - 0xe3001fff (0x1000) MX

[8] -1 0 0xe3000000 - 0xe3000fff (0x1000) MX

[9] -1 0 0xe3004000 - 0xe3004fff (0x1000) MX

[10] -1 0 0xd0000000 - 0xcfffffff (0x0) MXO

[11] -1 0 0xdc000000 - 0xdc07ffff (0x80000) MX(B)

[12] -1 0 0xd8000000 - 0xdbffffff (0x4000000) MX(B)

[13] -1 0 0xe0000000 - 0xe0ffffff (0x1000000) MX(B)

[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX

[15] -1 0 0x00000000 - 0x000000ff (0x100) IX

[16] -1 0 0x0000e400 - 0x0000e43f (0x40) IX

[17] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX

[18] -1 0 0x00004000 - 0x0000400f (0x10) IX

(II) resource ranges after probing:

[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX(B)

[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MXE(B)

[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX

[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX

[4]

XFree86.0.log

Ixthusdan · June 25, 2004

Are you over-clocked? If you are, go back to default.

Boot to console, and edit your /etc/X11/XF86Config-4 file back to "nv" instead of "nvidia"

so that you can get into x. If the log file is gibberish, perhaps the nvidia installer is corrupt and you need to download it again.

GreenBandit · June 27, 2004

I've made some progress, but not there yet.

The PC is not overclocked, & the W98SE system is able to run OpenGL & D3d demos like Tirtanium.

I set the XF86Config-4 file back to original, but the "startx" command still gave a total PC freeze, just as it did when using the nVidia driver.

I downloaded the nVidia driver again. It had the same MD5SUM as the one used for the last install, but I had to check.

I reinstalled MDK 10 OE onto its own 40Gb drive (hdb) with partitioning based on MDKs /usr option but with /usr set to about 10Gb (so I could install everything to ensure that the kernel would recompile).

I entered "urpmi binutils", then "urpmi kernel-source", but in both cases I was told everything already installed (I understand why now).

I then installed the nVidia driver, it recompiled the kernel, editing XF8Config-4, and typing in "startx". It crashed & froze.

At least this time editing the XF86Config file back to standard allows KDE to run again AND the XFree86.0.log file is not corrupted.

Does this attached log file give any clues ?

:help:

XFree86.0.log

Ixthusdan · June 27, 2004

Well, this is interesting. X seems to not be the crash. If it is, it was left off of the file. I don't see an X crash here. You may be having a mouse problem, since that is the last item installed. It is also interesting that you installed the same cd's and have a slightly different out come. Maybe the file is corrupt on the disk. Unless somebody else sees what I don't, I would try to install X again from a server. In other words, get the x files seperate from your media..

iphitus · June 27, 2004

Just a shot in the dark, are you loading the kernel module?

bvc · June 27, 2004

Just a shot in the dark, are you loading the kernel module?

not according to the log.....nv is being used, or trying to be used....but I'm confused :P because GreenBandit said XFree86-4 was edited then XFee86Config was edited and kde starts with the nv?

GreenBandit, we need a log from when nvidia is the driver.

GreenBandit · June 27, 2004

In answer to am I loading the kernel module, the answer is not knowingly. If it doesn't happen automatically when I start Linux, then its not happening.

The first time I installed MDK10, and the nVidia drivers including the Load "glx" and Driver "nvidia" mods to XF86Config-4, "startx" gave a total freeze. That time re-editing XF86Config-4 back to its original (###Load "glx" & Driver "nv") would not then let me start KDE. The other funny was the garbage in the middle of the XFree86.0.log file.

MDK 10 was re-installed, and the nVidia drivers were also re-installed after checking their MD5SUM. MKD10 was set up to not auto login & not start the GUI, so that I could login as "root" & use bash commands.

The XFree86.0.log file that was last posted was copied to floppy after a reboot, before the XF86Config-4 was re-edited to allow me to start KDE.

I'm going to go back, use a standard serial port mouse, delete the existing XFree86.0.log file, edit XF86Config-4 to use the nVidia driver, and after the crash, use a TOMSRTBT linux floppy to copy the new XFree86.0.log. If I have taken onboard what people have said, this should make sure it is the required log file from when .

I'm afraid I don't understand the comment " get the x files seperate from your media.. ". I am fairly sure the installation CDs are good because of earlier attempts with an nForce2 mobo.

bvc · June 27, 2004

before you

startx

do;

modprobe nvidia

In your log

(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2, Vanta,
RIVA TNT2 Ultra, RIVA TNT2 Model 64, Aladdin TNT2, GeForce 256,
GeForce DDR, Quadro, GeForce2 MX/MX 400, GeForce2 MX 100/200,
GeForce2 Go, Quadro2 MXR/EX/Go, GeForce2 Integrated GPU,
GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra, Quadro2 Pro,
GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, GeForce4 440 Go 64M,
GeForce4 410 Go 16M, Quadro4 500 GoGL, Quadro4 550 XGL, Quadro4 NVS,
GeForce4 MX 440 with AGP8X, GeForce4 MX 440SE with AGP8X,
GeForce4 MX 420 with AGP8X, GeForce4 448 Go, GeForce4 488 Go,
Quadro4 580 XGL, Quadro4 280 NVS, Quadro4 380 XGL,
GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200,
GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400,
0x0252, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, 0x0300, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000, 0x0311, 0x0312,
0x0316, 0x0317, 0x0318, 0x0319, 0x031A, 0x031B, 0x031C, 0x031D,
0x031E, 0x031F, 0x0321, 0x0322, 0x0323, 0x0326, 0x032A, 0x032B,
0x032E

mine

(II) LoadModule: "nvidia"

yours

(II) NV(0): I2C bus "DDC" initialized.
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0): DDC Monitor info: 0x837e3d8
(II) NV(0): Manufacturer: IBM  Model: 1999  Serial#: 2369524
(II) NV(0): Year: 1996  Week: 4
(II) NV(0): EDID Version: 1.0
(II) NV(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
(II) NV(0): Sync:  Separate  Composite  SyncOnGreen
(II) NV(0): Max H-Image Size [cm]: horiz.: 29  vert.: 21
(II) NV(0): Gamma: 2.86
(II) NV(0): DPMS capabilities: Suspend Off; RGB/Color Display
(II) NV(0): redX: 0.625 redY: 0.340   greenX: 0.280 greenY: 0.595
(II) NV(0): blueX: 0.155 blueY: 0.070   whiteX: 0.303 whiteY: 0.317
(II) NV(0): Supported VESA Video Modes:
(II) NV(0): 720x400@70Hz
(II) NV(0): 640x480@60Hz
(II) NV(0): 640x480@75Hz
(II) NV(0): 800x600@72Hz
(II) NV(0): 800x600@75Hz
(II) NV(0): 1024x768@87Hz (interlaced)
(II) NV(0): 1024x768@75Hz
(II) NV(0): Manufacturer's mask: 0
(II) NV(0): Supported Future Video Modes:
(II) NV(0): #0: hsize: 1024  vsize 768  refresh: 85  vid: 22881
(II) NV(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
(II) NV(0): #2: hsize: 640  vsize 480  refresh: 85  vid: 22833
(II) NV(0): end of DDC Monitor info

see all the NV's?

mine

(**) 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 0xD0000000
(--) NVIDIA(0): MMIO registers at 0xE4000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 MX 440
(--) NVIDIA(0): VideoBIOS: 04.17.00.69.00
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): CRT-0, TV-0
(--) NVIDIA(0): Detected TV Encoder: NVIDIA
(WW) NVIDIA(0): Multiple displays connected, but only one display allowed;
(WW) NVIDIA(0):      using first display
(--) NVIDIA(0): Display device CRT-0: maximum pixel clock at  8 bpp: 350 MHz
(--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 16 bpp: 350 MHz
(--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 32 bpp: 350 MHz
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a

see all the NVIDIA's?

yours

(WW) NV(0): Failed to set up write-combining range (0xd8000000,0x4000000)
(II) NV(0): Using XFree86 Acceleration Architecture (XAA)

mine

(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1280x1024"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture

GreenBandit · June 27, 2004

bvc, I do see what you mean about the nv entries in my file & the nvidia entries in yours. I did a "modprobe nvidia" & it did not give an error or generate any other text, just went back to a healthy console prompt (sorry I'm not sure about correct terminology).

The result of the last test, which was to delete the XFree96.0.log file before doing a startx with the nvidia drivers called up is that no XFree86.0.log file was there when rebooted. So I would agree with Ixthusdan's comment that X is not the problem.

Here's a bit of info, during the boot up there was a line something like no config file generating one. Use Kcontrol as root to customise. I did run Kcontrol & got the error

"KUniqueapplication: Can't determine DISPLAY. Aborting."

I changed the mouse to a PS2 connected wheel mouse & went into the Control Centre to configure it. With the nvidia driver selected, startx caused a crash, but again, no XFree86.0.log file was created.

So, when nvidia is the driver, no XFree86.0.log file is created !

Does tha fact that my linux PC does not have internet access affect me being able to " install X again from a server. In other words, get the x files seperate from your media.. " as suggested by Ixthusdan ?

Could this be anything to do with the fact that Mandrake do not list the Elitegroup 741GX-m mobo as being supported ? Could this be a 741GX AGP driver problem ?

Could it be worth retrying my nForce2 mobo ?

Did I cover all the suggestions made ? Any other ideas ?

(Thanks for the help so far)

:wall:

nVidia driver problem with MDK10 OE

Recommended Posts

Guest GreenBanditAtWork

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation