On Sunday 18 December 2005 02:12, आनंद wrote:

When i try to install the driver using "sudo apt-get install nvidia-glx" (as in ubuntuguide.org) everything installs ...but then when i restart x (ctrl+alt+backspace) or restart the comp ... the machine reboots at the point when x is trying to come up.

So then i tried installing the official nvidia drivers. Since it didnt have precompiled module for the kernel (i'm using the one that came with 5.10) it build it (i downloaded gcc 3.4 for that and kernel headers), but the same thing happens again. Every time it tries to start x it reboots.

I could do with some help here.

Anand.

On second thought... does your machine startup with X by default? If so, please paste the line from your /etc/inittab that mentions the X startup. The easiest way to spot this line would be, that the second field (runlevel) would have 5 as the value. The first field would probably be named x and the final field which actually mentions the command to be executed should have the X startup script as the value.

Mrugesh

On second thought... does your machine startup with X by default? If so, please paste the line from your /etc/inittab that mentions the X startup. The easiest way to spot this line would be, that the second field (runlevel) would have 5 as the value. The first field would probably be named x and the final field which actually mentions the command to be executed should have the X startup script as the value.

Mrugesh

I couldn't find that line .. i'm pasting the entire contents of the file

# /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel. id:2:initdefault:

# Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS

# What to do in single-user mode. ~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop

# /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

is there any other file that i need to look at ??

Hi Anand

I dunno if this helps since I don't use Ubuntu.I've had similar problems on my Debian unstable.I'm using the GE Force MX 400 too.

While I don't recall the exact steps I took to get things working I think the problem lay in the fact that Debian was making changes in their C/C++ ABI support. Therefore compiling and using the latest NVIDIA drivers was giving me probs for a very long time.I was only able to resolve things once Debian stabilized with their ABI transition and l compiled the latest driver from nvidia.

Since Ubuntu is basically Deb Unstable maybe what you're using still has some of these issues.Try using the latest version of your distrib and compiling the latest drivers and yes one thing I can confidently say is that the MX 400 is supported by the current drivers.Check the docs nonetheless.

Cheers Jeetu

then had to tweak the xorg.conf for the monitor settings and resolution for my monitor,

Could u tell what tweak u had to do ?? I have a samsung 753s (17'' monitor - CRT).

Maybe thats causing a problem.

Hi Anand

-Which distro are u using currently... and are ur drivers working in it ?

Am using Debian unstable dist-upgraded to the current package set.Am using kernel 2.6.12.1.The NVIDIA drivers work for me although didn't work for a long time probably because ofthe Debian ABI transition.What kernel are u using? Check you give it the proper path for source and module dirs during compile of the drivers.

Good luck Jeetu