Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 33

Thread: Problem with Nvidia Drivers after upgrade to Hardy 8.04

  1. #21
    Join Date
    Apr 2008
    Beans
    12

    Angry Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    More info:

    I printed out the current active kernel modules. Nvidia does not appear, nor does lrm. Perhaps this is the issue? Any ideas how to fix this?

    Thanks!

    Code:
    Module                  Size  Used by
    af_packet              27272  2 
    binfmt_misc            14860  1 
    rfcomm                 47392  2 
    l2cap                  28800  13 rfcomm
    bluetooth              67748  4 rfcomm,l2cap
    ppdev                  11400  0 
    parport_pc             41128  0 
    lp                     14916  0 
    parport                44300  3 ppdev,parport_pc,lp
    ipv6                  311720  18 
    acpi_cpufreq           10832  1 
    cpufreq_userspace       6180  0 
    cpufreq_stats           8416  0 
    cpufreq_powersave       3200  0 
    cpufreq_ondemand       11152  2 
    freq_table              6464  3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
    cpufreq_conservative    10632  0 
    video                  23444  0 
    output                  5632  1 video
    sbs                    17808  0 
    sbshc                   8960  1 sbs
    dock                   12960  0 
    container               6656  0 
    battery                16776  0 
    iptable_filter          4608  0 
    ip_tables              24104  1 iptable_filter
    x_tables               23560  1 ip_tables
    aes_x86_64             26920  0 
    dm_crypt               16776  0 
    ac                      8328  0 
    coretemp                9856  0 
    w83627ehf              27272  0 
    hwmon_vid               5120  1 w83627ehf
    arc4                    3456  2 
    ecb                     5248  2 
    blkcipher               9476  1 ecb
    rtl8187                37248  0 
    mac80211              192532  1 rtl8187
    cfg80211               17680  1 mac80211
    joydev                 15488  0 
    usblp                  17664  0 
    eeprom_93cx6            3840  1 rtl8187
    sky2                   53892  0 
    snd_hda_intel         440408  3 
    snd_hwdep              12552  1 snd_hda_intel
    snd_pcm_oss            47648  0 
    snd_pcm                92168  2 snd_hda_intel,snd_pcm_oss
    snd_page_alloc         13200  2 snd_hda_intel,snd_pcm
    snd_mixer_oss          20224  1 snd_pcm_oss
    i2c_core               28544  0 
    snd_seq_dummy           5764  0 
    snd_seq_oss            38912  0 
    snd_seq_midi           10688  0 
    snd_rawmidi            29856  1 snd_seq_midi
    snd_seq_midi_event     10112  2 snd_seq_oss,snd_seq_midi
    snd_seq                63232  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
    psmouse                46236  0 
    snd_timer              27912  2 snd_pcm,snd_seq
    snd_seq_device         10644  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
    serio_raw               9092  0 
    button                 10912  0 
    intel_agp              30624  0 
    snd                    70856  17 snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
    iTCO_wdt               15312  0 
    shpchp                 38172  0 
    pci_hotplug            34608  1 shpchp
    soundcore              10400  1 snd
    iTCO_vendor_support     5764  1 iTCO_wdt
    evdev                  14976  4 
    pcspkr                  4992  0 
    ext3                  149264  1 
    jbd                    57000  1 ext3
    mbcache                11392  1 ext3
    dm_mirror              26368  0 
    dm_mod                 71160  16 dm_crypt,dm_mirror
    sr_mod                 20132  0 
    cdrom                  41512  1 sr_mod
    pata_jmicron            8448  0 
    pata_acpi               9856  0 
    sg                     41880  0 
    sd_mod                 33280  2 
    usbhid                 35168  0 
    hid                    44992  1 usbhid
    skge                   47888  0 
    ohci1394               36532  0 
    ieee1394              106968  1 ohci1394
    ata_generic             9988  0 
    ahci                   33028  2 
    libata                176304  4 pata_jmicron,pata_acpi,ata_generic,ahci
    scsi_mod              178488  4 sr_mod,sg,sd_mod,libata
    ehci_hcd               41996  0 
    uhci_hcd               29856  0 
    usbcore               169904  6 rtl8187,usblp,usbhid,ehci_hcd,uhci_hcd
    thermal                19744  0 
    processor              41448  2 acpi_cpufreq,thermal
    fan                     6792  0 
    fbcon                  46336  0 
    tileblit                4096  1 fbcon
    font                   10112  1 fbcon
    bitblit                 7424  1 fbcon
    softcursor              3712  1 bitblit
    fuse                   56112  9

  2. #22
    Join Date
    Apr 2008
    Beans
    12

    Smile Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    I figured it out! The problem was the kernel module was not being inserted.
    To fix it:

    Code:
    sudo /etc/init.d/gdm stop
    sudo insmod /lib/modules/`uname -r`/volatile/nvidia_new.ko
    sudo /etc/init.d/gdm start
    Thanks to everyone for all your help!

    --ifedeli

  3. #23
    Join Date
    Oct 2005
    Location
    Martinez, Ca
    Beans
    35
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    Quote Originally Posted by ifedeli View Post
    I figured it out! The problem was the kernel module was not being inserted.
    To fix it:

    Code:
    sudo /etc/init.d/gdm stop
    sudo insmod /lib/modules/`uname -r`/volatile/nvidia_new.ko
    sudo /etc/init.d/gdm start
    Thanks to everyone for all your help!

    --ifedeli
    Now the question is, does it still load when the machine is rebooted? Manually inserting the kernel module worked for me, but how do I guarentee that it will load on next boot of the laptop?

  4. #24
    Join Date
    Mar 2008
    Location
    Scottish Borders
    Beans
    27
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    Quote Originally Posted by ifedeli View Post
    I figured it out! The problem was the kernel module was not being inserted.
    To fix it:

    Code:
    sudo /etc/init.d/gdm stop
    sudo insmod /lib/modules/`uname -r`/volatile/nvidia_new.ko
    sudo /etc/init.d/gdm start
    Thanks to everyone for all your help!

    --ifedeli
    I'm having a similar problem with an nvidia 7600GT.
    It worked fine under Gutsy with the restricted driver, but neither this nor Envyng seem to work under Hardy.

    I'm not sure if it's anything to do with kernels in my case?
    How would I find out, and when should I apply your solution to test it out?
    Should I apply the restricted driver then restart in Recovery mode to use your command?

    Under Gutsy I used to use "sudo dpkg-reconfigure -phigh xserver-xorg" to get the correct driver for xorg.conf, but that command doesn't seem to have any effect in Hardy?

    Another problem I have now is that although I'm able to get back to the correct resolution (1440x900) using the nv driver, my login screen is messed up. It is huge, and I can only see my user name in the bottom right corner. I can click on it and type my password to get to my desktop, but the other users can't get to theirs.
    However, I presume if I can get nvidia-glx-new to work, then that would sort that out?

  5. #25
    Join Date
    Apr 2008
    Beans
    12

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    Now the question is, does it still load when the machine is rebooted? Manually inserting the kernel module worked for me, but how do I guarentee that it will load on next boot of the laptop?
    @ghstridr

    Manually inserting th kernel module will only work for the current boot session. However, you can script it to insert every time before you start GNOME. This is *not* official or even probably the best way to do it, but it worked for me.

    At the beginning of /etc/init.d/gdm, I inserted the middle line from before. I believe this will cause it to run every time GNOME is started or stopped, but there doesn't seem to be any detrimental effect from running it too many times.

    Code:
    #! /bin/sh
    #
    # Originally based on:
    # Version:	@(#)skeleton  1.8  03-Mar-1998  miquels@cistron.nl
    #
    # Modified for gdm, Steve Haslam <steve@arise.dmeon.co.uk> 14mar99
    # modified to remove --exec, as it does not work on upgrades. 18jan2000
    # modified to use --name, to detect stale PID files 18mar2000
    # sleep until gdm dies, then restart it 16jul2000
    # get along with other display managers (Branden Robinson, Ryan Murray) 05sep2001
    
    #INSERTED BY IFEDELI
    insmod /lib/modules/`uname -r`/volatile/nvidia_new.ko
    
    set -e
    
    # To start gdm even if it is not the default display manager, change
    # HEED_DEFAULT_DISPLAY_MANAGER to "false."
    HEED_DEFAULT_DISPLAY_MANAGER=true
    DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
    PATH=/sbin:/bin:/usr/sbin:/usr/bin
    DAEMON=/usr/sbin/gdm
    PIDFILE=/var/run/gdm.pid
    UPGRADEFILE=/var/run/gdm.upgrade
    
    <snip>
    I'm having a similar problem with an nvidia 7600GT.
    It worked fine under Gutsy with the restricted driver, but neither this nor Envyng seem to work under Hardy.

    I'm not sure if it's anything to do with kernels in my case?
    How would I find out, and when should I apply your solution to test it out?
    Should I apply the restricted driver then restart in Recovery mode to use your command?
    @emptybox

    To find out if the kernel module is currently inserted, run this:

    Code:
    sudo lsmod | grep nvidia
    If it returns something like this:

    Code:
    nvidia               8858052  34
    then the module is inserted and this is not your problem. If it returns nothing, this could be it.

    Heres what I would do:
    1. Remove any beta drivers (sh NVIDIA*.run --uninstall)
    2. Undo anything from EnvyNG by uninstalling
    3. Open up synaptic, search for nvidia, and remove completely nvidia-glx-new, nvidia-kernel-common and linux-restricted-modules for your kernel, if they are there.
    4. run
    Code:
     sudo find /lib/modules/`uname -r` -name "*nvidia*"
    This will produce of list of kernel modules that are still there. I don't know why they are still there. If you want to be safe, move them to some folder for safe keeping. I just deleted them.
    5. Open up synaptic again and install nvidia-glx-new, nvidia-kernel-common and linux-restricted-modules. Close synaptic.
    6. Switch to the terminal (CTRL-ALT-F1). Ensure your /etc/X11/xorg.conf has something like this:

    Code:
    Section "Device"
        Identifier     "Configured Video Device"
        Driver         "nvidia"
        BoardName      "vesa"
        BusID          "PCI:1:0:0"
        Screen          0
    EndSection
    The important part is the Driver "nvidia" part.

    7. run
    Code:
    sudo /etc/init.d/gdm stop
    sudo insmod /lib/modules/`uname -r`/volatile/nvidia_new.ko
    sudo /etc/init.d/gdm start
    8. Switch back to GNOME (CTRL-ALT-F7). Hopefully it works now!
    9. To make the insert happen on every start up, follow the instructions above (or if you know a better way, do that and let me know!)

    Under Gutsy I used to use "sudo dpkg-reconfigure -phigh xserver-xorg" to get the correct driver for xorg.conf, but that command doesn't seem to have any effect in Hardy?
    I think i read somewhere this doesn't work any more. I would try rebooting in recovery mode and running xfix. That seems to give a decent xorg.conf.

    Another problem I have now is that although I'm able to get back to the correct resolution (1440x900) using the nv driver, my login screen is messed up. It is huge, and I can only see my user name in the bottom right corner. I can click on it and type my password to get to my desktop, but the other users can't get to theirs.
    However, I presume if I can get nvidia-glx-new to work, then that would sort that out?
    I'm really not sure on this one. I would hope that problem sorts itself out when nvidia-glx-new is working.

    Hope this helps. Let me know if I can give more info.

    --ifedeli

  6. #26
    Join Date
    Apr 2008
    Beans
    5

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    Quote Originally Posted by emptybox View Post
    I'm having a similar problem with an nvidia 7600GT.
    It worked fine under Gutsy with the restricted driver, but neither this nor Envyng seem to work under Hardy.

    I'm not sure if it's anything to do with kernels in my case?
    How would I find out, and when should I apply your solution to test it out?
    Should I apply the restricted driver then restart in Recovery mode to use your command?

    Under Gutsy I used to use "sudo dpkg-reconfigure -phigh xserver-xorg" to get the correct driver for xorg.conf, but that command doesn't seem to have any effect in Hardy?

    Another problem I have now is that although I'm able to get back to the correct resolution (1440x900) using the nv driver, my login screen is messed up. It is huge, and I can only see my user name in the bottom right corner. I can click on it and type my password to get to my desktop, but the other users can't get to theirs.
    However, I presume if I can get nvidia-glx-new to work, then that would sort that out?
    I'm had the same exact issue with my 7600GT, so I've been sticking to the 'nv' driver for now. But I can't use any other driver, such as the one envyng downloads, which may be why Warzone 2100 runs horribly slow and Urban Terror freezes my x.

    As for the login screen, I believe it's related to your x.org configuration (or something like that, I'm still a linux noob). I found a solution here for that.

    I hope this gets figured out, because I really don't want to have to do a clean install -- but alas, if I have to I will.

  7. #27
    Join Date
    Mar 2008
    Location
    Scottish Borders
    Beans
    27
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    @ ifedeli
    Unfortunately that doesn't seem to be my problem?
    I went through all your steps, but I still couldn't get it to run at more than 800x600 using the nvidia-glx-new driver, and the desktop effects didn't work either.

    I've reverted to the nv drivers, and will run with those for a few days, and if no other solution presents itself, then I'll try a fresh install of 8.04. And if that doesn't work then it's back to good stable Gutsy.

    @ astepintothedark
    The only good news is that my login screen has righted itself.


    BTW Ctrl-Alt-F1 has never worked on this machine for some reason?
    Or Ctrl-Alt-F anything for that matter?
    I can only get to a shell terminal by booting into Recovery mode, unless someone knows another way?

    In Hardy when you go into Recovery mode, instead of ending at the command prompt, a box come up with 3 options.
    1. continue to boot normally
    2. drop down to a command prompt (or wtte)
    3. xfix

    Using xfix seems to restore the default Hardy xorg.conf which doesn't have any mention of video drivers in it.
    It still only allowed me 1024x768 though. To get back to my native 1440x900 res I had to enable then disable the nvidia-glx-new.

    Will look on the forum for more solutions Tomorrow.

  8. #28
    Join Date
    Apr 2008
    Beans
    12

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    @emptybox
    Sorry I couldn't be more help. Good luck!

  9. #29
    Join Date
    Apr 2008
    Beans
    5

    Talking Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    So I think I might have found a solution.

    What happened to me since I last posted is that I did a fresh install of Ubuntu, but I tried playing urban terror and I had the same issues as before. So I got the envyng pkg and tried installing the nvidia drivers, but to no avail. A bug error was reported, so I went to the link mentioned above and some wrote that I need to type in this code:
    Code:
    sudo apt-get install linux-headers-server linux-headers-$(uname -r)
    I typed in the code, then ran envyng again, installed the drivers, restarted and bam! Fixed.

    It worked for me, hopefully it can work for you guys.

  10. #30
    Join Date
    Oct 2005
    Location
    Martinez, Ca
    Beans
    35
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: Problem with Nvidia Drivers after upgrade to Hardy 8.04

    Quote Originally Posted by ifedeli View Post
    @ghstridr

    Manually inserting th kernel module will only work for the current boot session. However, you can script it to insert every time before you start GNOME. This is *not* official or even probably the best way to do it, but it worked for me.

    At the beginning of /etc/init.d/gdm, I inserted the middle line from before. I believe this will cause it to run every time GNOME is started or stopped, but there doesn't seem to be any detrimental effect from running it too many times.
    I tried that and it was still failing to vesa safe mode.
    I did fix that though, found that 'nvidia' was being black listed in /etc/modprobe.d/blacklist-restricted. Commenting out the 'nvidia' statement allowed me finally to use the Nvidia driver.
    I found this out by looking in /var/log/daemon.log

    Code:
    # This file is used to disable restricted drivers
    #blacklist nvidia
    blacklist nvidia.bad
    blacklist nvidia_legacy.bad
    blacklist nvidia_new
    blacklist nvidia_new.bad
    Now I'm just trying to figure out why the Gnome Settings Daemon is issuing a warnign on login to the desktop:
    There was an error starting the GNOME Settings Daemon.

    Some things, such as themes, sounds, or background settings may not work correctly.

    Code:
    The last error message was:
    
    Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    
    GNOME will still try to restart the Settings Daemon next time you log in.

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •