ASUS F3S laptop nvidia GeForce 8400M G fails to start x
Hi all
I have a very similar problem to https:/
The reason I went the nvidia driver route was it is too new for 7.04, that is to be expected.
However, I have followed all the instruction regarding installing the NVIDIA-
I did the purge removes, restricted disables, source downloads, telinit 3, step by step.
Yet the only xorg.conf setting that works is for vesa.
Looking for any new ideas, one I did see in the similar question 7303 was
sudo apt-get install nvidia-
Just wondering if somwthing like that would work for 100.14.09.
Oh, and I have lodged a bug report with nvidia and ubuntu, both have been very helpful - thank you to the people I have met there.
Regards
Gerard
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Gerard
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
The only way you're going to get a card as new as a GeForce 8400M going with binary drivers is by using drivers _newer_ than the ones that ship with Ubuntu Feisty (and just so you know Ubuntu won't be packaging newer binary drivers until Gusty comes out in October). The list cards supported by the Ubuntu shipped drivers can be found as link on https:/
Gerard:
Tell me very carefully what you have attempted to do so far and in what order, what you have currently installed along with the output of
dpkg -l nvidia\* | grep ii
cat /etc/default/
sudo modprobe nvidia
dmesg | tail
lspci | grep -i nv
ls -l /usr/lib/libGL*
Do not make any changes to your system at this stage. It is very easy to end up with a system no one will help you fix the moment you step away from .deb packages because there is no longer one system in charge of checking for conflicts.
Be warned! Installing the binary drivers "by hand" can leave your system in a state which may not be upgradable to Gusty. Further, EVERY time a kernel update comes out you and you switch to running the new kernel you will HAVE to recompile the kernel module part of the driver yourself. Also due to the way the libraries in the NVIDIA pkg install themselves when an update to Mesa is released the GL library part of the package will have to be reinstalled.
Revision history for this message
|
#2 |
I will try yo be brief, yet complete.
As it stands right now, since our last conversation I have started from scratch.
I have created a dual boot so I could manage the bios, I now have Vista on a 20 Gb partition, Kubuntu on the remaining 100 Gb.
I used the Kubuntu alternative CD as the Live CD does not work - off topic.
I followed the instructions from here:
http://
with minor differences. I did this.
</instructions>
sudo apt-get install linux-headers-
sudo apt-get --purge remove nvidia-glx nvidia-settings nvidia-glx-legacy
sudo /etc/init.d/kdm stop
<my difference>
</my difference>
sudo cp /etc/X11/xorg.conf /etc/X11/
cd /home/gerard/
sudo sh NVIDIA-
sudo nvidia-xconfig --no-composite
sudo nano -w /etc/default/
edited so DISABLED_
[Ctrl X]
[Y]
sudo /etc/init.d/kdm restart
</instructions>
This produced the nvidia splash screen.
But when it went away, it was still using vesa.
So I rebooted
Same symptoms as before.
The Kubuntu startup screen displays as normal, a status bar that fills in with a light blue indicator, right through to the end.
What should happen:
It would go black for a millisecond or two, then display the log in screen.
What does happen
It would go black for a millisecond or two, then displays the Kubuntu startup screen, with the status bar empty, as if starting from scratch.
This stays on the screen for maybe five seconds without altering.
It then goes away, leaving a black screen, with a white blinking cursor, as if in console mode. But one where all it does is display what you type in, similar to a text editor, no actions.
[Alt + F1] brings up a working login console prompt.
I logged in, ran sudo nvidia-
I have experienced the pain of hand building then upgrading, my move from Dapper to Edgy was... a learning experience. I am prepared for the problems associated with kernel updates, I have been there before with USB TV under Edgy.
I am prepared at this stage to keep on reinstalling Kubuntu in a effort to keep things as vanilla as possible, I hope to be able to pass something useful on to others, and to get a working version for myself of course.
In the spirit of this, if you wanted this to be test machine for Gutsy, I would be more than happy to assist, because that is where I would like to see this going.
Right, back to your request:
I ran these using vesa so I had a GUI.
:~$dpkg -l nvidia\* | grep ii
ii nvidia-
:~$cat /etc/default/
# This file is sourced from the linux-restricte
# script and is used to disable the link-on-boot feature, one module
# at a time. This can be useful if you want to use hand-compiled
# versions of one or more modules, but keep linux-restricte
# installed on your system, or just to disable modules you don't use
# and speed up your boot process by a second or two.
#
# Use a space-separated list of modules you wish to not have linked
# on boot. The following example shows a (condensed) list of all
# modules shipped in the linux-restricte
#
# DISABLED_
#
# Note that disabling "fc" disables all fcdsl drivers, "ltm" disables
# ltmodem and ltserial, and "nv" disables both the nvidia drivers.
# You can also name each module individually, if you prefer a subset.
DISABLED_
:~$sudo modprobe nvidia
:~$Not loading nvidia module; not used in /etc/X11/xorg.conf
<note>
Seeing this I then
:~$sudo nano -w /etc/X11/xorg.conf
changed
driver = "nvidia"
:~$sudo modprobe nvidia
:~$
Being ever hopeful I left it like that, when I rebooted, no change.
</note>
:~$ dmesg | tail
[ 37.116000] Bluetooth: HCI socket layer initialized
[ 37.144000] Bluetooth: L2CAP ver 2.8
[ 37.144000] Bluetooth: L2CAP socket layer initialized
[ 37.352000] Bluetooth: RFCOMM socket layer initialized
[ 37.352000] Bluetooth: RFCOMM TTY layer initialized
[ 37.352000] Bluetooth: RFCOMM ver 1.8
[ 474.296000] nvidia: module license 'NVIDIA' taints kernel.
[ 474.556000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 474.556000] PCI: Setting latency timer of device 0000:01:00.0 to 64
[ 474.556000] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.09 Sat May 26 00:47:07 PDT 2007
:~$ lspci | grep -i nv
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0428 (rev a1)
:~$ ls -l /usr/lib/libGL*
lrwxrwxrwx 1 root root 22 2007-06-14 06:53 /usr/lib/
-rwxr-xr-x 1 root root 10080488 2007-06-14 06:53 /usr/lib/
lrwxrwxrwx 1 root root 16 2007-06-13 16:11 /usr/lib/
-rw-r--r-- 1 root root 199848 2007-03-05 14:16 /usr/lib/
-rw-r--r-- 1 root root 659 2007-06-14 06:53 /usr/lib/libGL.la
lrwxrwxrwx 1 root root 10 2007-06-14 06:53 /usr/lib/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root 18 2007-06-14 06:53 /usr/lib/libGL.so.1 -> libGL.so.100.14.09
-rwxr-xr-x 1 root root 607632 2007-06-14 06:53 /usr/lib/
lrwxrwxrwx 1 root root 20 2007-06-12 23:38 /usr/lib/
-rw-r--r-- 1 root root 521000 2007-03-31 07:07 /usr/lib/
Revision history for this message
|
#3 |
I use the same drivers for my GeForce 8500 GT. The driver comes with its share of issues... so far I have had to reinstall the drivers (simply by running the Nvidia install file (the .run file) as root) each time i reboot. If you've installed the drivers using the script, as you have seem to have done seeing the line -
sudo sh NVIDIA-
then at the end of the install process after compiling and installing your kernel module, it would have asked you if you wanted it to modify your xorg.conf. In case you said yes there, it would have automatically set your xorg.conf to use to nvidia driver. I presume the nvidia-xconfig command you run does somewaht the same function. You could try letting the script modify the xorg.conf on its own and see if it does a better job for some reason.
Since the last line of your dmesg is the one talking about loading the Nvidia module, then you dont seem to have issues with the module itself.
The nVidia corporation unknown device in the lspci seems to happen with all the geForce8 GPUs.
Revision history for this message
|
#4 |
Gerard:
In /etc/default/
DISABLED_
to
DISABLED_
. Reboot. Can you then add the output of doing
sudo modprobe nvidia
dmesg | tail
Edit xorg.conf to use the nvidia driver and try to start X by using
/etc/init.d/kdm restart
When X crashes copy the file
/var/log/Xorg.0.log
to your home directory. Change xorg.conf back to vesa and attach (using the launchpad web interface) the copy of the /var/log/Xorg.0.log file. Please also attach the file that nvidia-
Revision history for this message
|
#5 |
With /etc/default/
and /etc/X11/xorg.conf Driver "vesa"
reboot
:~$ sudo modprobe nvidia
Password:
Not loading nvidia module; not used in /etc/X11/xorg.conf
:~$ dmesg | tail
[ 28.548000] Bluetooth: Core ver 2.11
[ 28.548000] NET: Registered protocol family 31
[ 28.548000] Bluetooth: HCI device and connection manager initialized
[ 28.548000] Bluetooth: HCI socket layer initialized
[ 28.580000] Bluetooth: L2CAP ver 2.8
[ 28.580000] Bluetooth: L2CAP socket layer initialized
[ 28.748000] Bluetooth: RFCOMM socket layer initialized
[ 28.748000] Bluetooth: RFCOMM TTY layer initialized
[ 28.748000] Bluetooth: RFCOMM ver 1.8
[ 31.248000] eth0: no IPv6 routers present
:~$ sudo /etc/init.d/kdm restart
I do not see a way of attaching files here, I am a new user of Answers so I could be missing something.
I have placed the files here:
http://
But this is unsatisfactory as this link will be dead at some point, creating a 404 for some poor lost soul.
If there is a way to attach, please let me know, I will do that.
Cheers
Gerard
Revision history for this message
|
#6 |
On re-reading this, I must confirm it was in fact /etc/default/
NOT what I typed 7 seconds ago.
Revision history for this message
|
#7 |
Gees I really should read my posts more closely.
I need to also confirm I am trying to use NVIDIA-
Revision history for this message
|
#8 |
OK - Played with it some more: now it works, not sure what I did that was different.
This time I did this, even though they did not exist.
rm -f /etc/init.
rm -f /etc/init.
rm -f /lib/linux-
I also added automake, autoconf.
I made sure /etc/default/
And for good measure I added /etc/default/
I followed the normal script deal, telinit 3 etc through to the end.
This time I sudo modprobe nvidia before restarting.
I did not even notice a change in screen quality as it was still using 1024x768, I thought it was still using vesa & I had missed a step.
The only hint was the big nvidia splash screen on startup.
I went to the display panel (sorry not at home, using windows box, forgotten correct terminology) and under hardware is still said vesa, checked xorg.conf, definitely says nvidia...
I then noticed the nvidia settings icon in the K menu, click it, and lo and behold, all the setting were there.
I changed resolution to 1440x900, beautiful.
I sit here somewhat mystified.
Shutdown, bootup. restarted. still there. Solved?
I can not honestly click the button below [I Solved the Problem on My Own] as it wasn't down to me.
Thank you Lonni J Friedman from nvidia and a big thank you to Sitsofe Wheeler both showed more patience than I had any right to expect.
Ciao
Gerard