|
nVidia broke.
Hello all. I am running Ubuntustudio 10.10.
I installed using the lines from Webupd8. When installing it told me it failed to find the nvidia kernel headers or something like that. I remember that the nvidia drivers need to be reinstalled whenever the kernel is updated but it didn't hit me at first. Anyways the install didn't totally fail so I restarted the computer and selected liquorix fro the grub menu. I discovered that it wouldn't go into Gnome because of the drivers. So I did sudo aptitude reinstall nvidia-current And then they failed to compile! It complained about a missing file I think it was dkms.py. So I reset again, and selected the old kernel in grub. It failed to go into gnome again, so I figured it was because of the nvidia drivers. So I used the above line again to try to reinstall the nvidia drivers to this kernel, but instead of that they still tried to compile with liquorix. I need to know how to install the nvidia drivers and I also need to know how to make the video card work with the standard kernel so if liquorix breaks I have backup. Please help. Thanks, - keantoken PS I misspelled my username when I registered. :D Back to top |
|||||
|
try sgfxi, usually works fine. No idea why nvidia package wouldn't install on ubuntu, probably a kernel mismatch, maybe a nouveau issue, who knows.
Generally you are safest sticking with the defaults of frozen pool releases like Debian Stable or Ubuntu, since everything pretty much works together. It's not that releases responsibility to support later kernels, nvidia adds support for newer kernels or methods. I do not personally like dkms because it's confusing and complicated when it fails, I've never used it, nor do I plan to ever use it, unless maybe I ran nvidia on a stable kernel release, but even then I doubt I'd bother to be honest, sgfxi is too easy, and it is heavily tested and works. Try installing inxi, then show the output of: inxi -Fz here which gives a good idea of your system and hardware. inxi will also show some more information about the video drivers etc once you get X to start again. Back to top |
|||||
|
I went back to my computer and found the old kernel had magically started up, so it doesn't look like I broke the drivers. However I went to root and used sgfxi and it still gave a dkms error! Something about a file not being a valid dkms file.
Since sgfxi is trying to use dmks for something, it doesn't look like I have a choice! Thanks Back to top |
|||||
|
Okay, I did
sudo aptitude purge dkms And then I reinstalled it and all this happened: :: Code :: Ign http://security.ubuntu.com/ubuntu/ maverick-security/multiverse Translation-en
Ign http://security.ubuntu.com/ubuntu/ maverick-security/multiverse Translation-en_US Ign http://security.ubuntu.com/ubuntu/ maverick-security/restricted Translation-en Ign http://security.ubuntu.com/ubuntu/ maverick-security/restricted Translation-en_US Ign http://security.ubuntu.com/ubuntu/ maverick-security/universe Translation-en Ign http://security.ubuntu.com/ubuntu/ maverick-security/universe Translation-en_US Ign http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/ maverick/main Translation-en Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main Translation-en Hit http://security.ubuntu.com maverick-security Release Ign http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/ maverick/main Translation-en_US Hit http://ppa.launchpad.net maverick Release.gpg Hit http://archive.canonical.com maverick/partner Sources Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main Translation-en_US Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/multiverse Translation-en Ign http://extras.ubuntu.com maverick/main Sources/DiffIndex Ign http://ppa.launchpad.net/tehnick/tehnick/ubuntu/ maverick/main Translation-en Ign http://ppa.launchpad.net/tehnick/tehnick/ubuntu/ maverick/main Translation-en_US Hit http://ppa.launchpad.net maverick Release.gpg Ign http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu/ maverick/main Translation-en Ign http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu/ maverick/main Translation-en_US Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/multiverse Translation-en_US Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/restricted Translation-en Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/restricted Translation-en_US Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/universe Translation-en Ign http://us.archive.ubuntu.com/ubuntu/ maverick-updates/universe Translation-en_US Hit http://security.ubuntu.com maverick-security/main Sources Hit http://ppa.launchpad.net maverick Release.gpg Ign http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ maverick/main Translation-en Hit http://archive.canonical.com maverick/partner i386 Packages Hit http://us.archive.ubuntu.com maverick Release Ign http://extras.ubuntu.com maverick/main i386 Packages/DiffIndex Ign http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ maverick/main Translation-en_US Hit http://ppa.launchpad.net maverick Release Hit http://ppa.launchpad.net maverick Release Hit http://us.archive.ubuntu.com maverick-updates Release Hit http://security.ubuntu.com maverick-security/restricted Sources Hit http://security.ubuntu.com maverick-security/universe Sources Hit http://security.ubuntu.com maverick-security/multiverse Sources Hit http://security.ubuntu.com maverick-security/main i386 Packages Hit http://security.ubuntu.com maverick-security/restricted i386 Packages Hit http://security.ubuntu.com maverick-security/universe i386 Packages Hit http://extras.ubuntu.com maverick/main Sources Hit http://ppa.launchpad.net maverick Release Hit http://ppa.launchpad.net maverick Release Hit http://ppa.launchpad.net maverick Release Hit http://ppa.launchpad.net maverick Release Hit http://ppa.launchpad.net maverick Release Hit http://us.archive.ubuntu.com maverick/main Sources Hit http://us.archive.ubuntu.com maverick/restricted Sources Hit http://us.archive.ubuntu.com maverick/universe Sources Hit http://us.archive.ubuntu.com maverick/multiverse Sources Hit http://us.archive.ubuntu.com maverick/main i386 Packages Hit http://us.archive.ubuntu.com maverick/restricted i386 Packages Hit http://security.ubuntu.com maverick-security/multiverse i386 Packages Hit http://extras.ubuntu.com maverick/main i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Hit http://us.archive.ubuntu.com maverick/universe i386 Packages Hit http://us.archive.ubuntu.com maverick/multiverse i386 Packages Hit http://us.archive.ubuntu.com maverick-updates/main Sources Hit http://us.archive.ubuntu.com maverick-updates/restricted Sources Hit http://us.archive.ubuntu.com maverick-updates/universe Sources Hit http://us.archive.ubuntu.com maverick-updates/multiverse Sources Hit http://us.archive.ubuntu.com maverick-updates/main i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Hit http://us.archive.ubuntu.com maverick-updates/restricted i386 Packages Hit http://us.archive.ubuntu.com maverick-updates/universe i386 Packages Hit http://us.archive.ubuntu.com maverick-updates/multiverse i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Hit http://ppa.launchpad.net maverick/main Sources Hit http://ppa.launchpad.net maverick/main i386 Packages Fetched 73B in 1s (56B/s) Reading package lists... Done W: GPG error: http://extras.ubuntu.com maverick Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192 E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? keantoken@ubuntu:~$ sudo apt-get install linux-headers-2.6-liquorix-686 linux-image-2.6-liquorix-686 Reading package lists... Done Building dependency tree Reading state information... Done linux-headers-2.6-liquorix-686 is already the newest version. linux-image-2.6-liquorix-686 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up nvidia-current (260.19.06-0ubuntu1) ... update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-2.6.35-30-generic Removing old nvidia-current-260.19.06 DKMS files... dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified. dkms.conf: Error! No 'PACKAGE_NAME' directive specified. dkms.conf: Error! No 'PACKAGE_VERSION' directive specified. Error! Bad conf file. File: /var/lib/dkms/nvidia-current/260.19.06/source/dkms.conf does not represent a valid dkms.conf file. dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 5 Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.39-2.dmz.1-liquorix-686 Processing triggers for python-support ... Errors were encountered while processing: nvidia-current E: Sub-process /usr/bin/dpkg returned an error code (1) keantoken@ubuntu:~$ sudo aptitude purge dkms The following packages will be REMOVED: dkms{p} The following partially installed packages will be configured: nvidia-current{b} 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 487kB will be freed. The following packages have unmet dependencies: nvidia-current: Depends: dkms but it is not going to be installed. virtualbox-ose-dkms: Depends: dkms (>= 2.1.0.0) but it is not going to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) nvidia-current 2) python-pyopencl 3) virtualbox-ose-dkms Leave the following dependencies unresolved: 4) virtualbox-ose recommends virtualbox-ose-dkms (= 3.2.8-dfsg-2ubuntu1) Accept this solution? [Y/n/q/?] y The following packages will be REMOVED: dkms{p} nvidia-current{a} python-dateutil{u} python-decorator{u} python-matplotlib{u} python-matplotlib-data{u} python-opengl{u} python-pyopencl{a} python-pyparsing{u} python-pytools{u} python-tz{u} virtualbox-ose-dkms{a} 0 packages upgraded, 0 newly installed, 12 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 104MB will be freed. Do you want to continue? [Y/n/?] y (Reading database ... 399355 files and directories currently installed.) Removing python-pyopencl ... Removing nvidia-current ... Removing all DKMS Modules dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified. dkms.conf: Error! No 'PACKAGE_NAME' directive specified. dkms.conf: Error! No 'PACKAGE_VERSION' directive specified. Error! Bad conf file. File: /var/lib/dkms/nvidia-current/260.19.06/source/dkms.conf does not represent a valid dkms.conf file. Done. update-alternatives: removing manually selected alternative - switching gl_conf to auto mode update-alternatives: using /usr/lib/mesa/ld.so.conf to provide /etc/ld.so.conf.d/GL.conf (gl_conf) in auto mode. Removing virtualbox-ose-dkms ... -------- Uninstall Beginning -------- Module: virtualbox-ose Version: 3.2.8 Kernel: 2.6.35-30-generic (i686) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-30-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-30-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-30-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod....... DKMS: uninstall Completed. -------- Uninstall Beginning -------- Module: virtualbox-ose Version: 3.2.8 Kernel: 2.6.35-28-generic (i686) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-28-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-28-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-28-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod...... DKMS: uninstall Completed. ------------------------------ Deleting module version: 3.2.8 completely from the DKMS tree. ------------------------------ Done. Processing triggers for python-support ... Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for man-db ... Processing triggers for python-support ... (Reading database ... 398947 files and directories currently installed.) Removing dkms ... Purging configuration files for dkms ... dpkg: warning: while removing dkms, directory '/var/lib/dkms' not empty so not removed. Processing triggers for man-db ... (Reading database ... 398902 files and directories currently installed.) Removing python-pytools ... Removing python-matplotlib ... Removing python-dateutil ... Removing python-decorator ... Removing python-matplotlib-data ... Removing python-opengl ... Removing python-pyparsing ... Removing python-tz ... Processing triggers for python-support ... Processing triggers for man-db ... Processing triggers for doc-base ... Processing 1 removed doc-base file(s)... Registering documents with scrollkeeper... keantoken@ubuntu:~$ sudo aptitude install dkms python-pyopencl The following NEW packages will be installed: dkms nvidia-current{a} python-dateutil{a} python-decorator{a} python-matplotlib{a} python-matplotlib-data{a} python-opengl{a} python-pyopencl python-pyparsing{a} python-pytools{a} python-tz{a} 0 packages upgraded, 11 newly installed, 0 to remove and 0 not upgraded. Need to get 4,293kB/30.6MB of archives. After unpacking 100MB will be used. Do you want to continue? [Y/n/?] y Get:1 http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main dkms all 2.1.1.2-3ubuntu1.1 [71.3kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ maverick/main python-dateutil all 1.4.1-3 [54.2kB] Get:3 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-decorator all 3.2.0-1 [45.6kB] Get:4 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-matplotlib-data all 0.99.3-1ubuntu1 [1,026kB] Get:5 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-pyparsing all 1.5.2-2 [608kB] Get:6 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-tz all 2010b-1 [43.9kB] Get:7 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-matplotlib i386 0.99.3-1ubuntu1 [1,582kB] Get:8 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-opengl all 3.0.1~b2-1 [528kB] Get:9 http://us.archive.ubuntu.com/ubuntu/ maverick/universe python-pytools all 10-7 [30.1kB] Get:10 http://us.archive.ubuntu.com/ubuntu/ maverick/multiverse python-pyopencl i386 0.92~beta+git20100709-1ubuntu1 [305kB] Fetched 4,293kB in 13s (327kB/s) Selecting previously deselected package dkms. (Reading database ... 397417 files and directories currently installed.) Unpacking dkms (from .../dkms_2.1.1.2-3ubuntu1.1_all.deb) ... Selecting previously deselected package nvidia-current. Unpacking nvidia-current (from .../nvidia-current_260.19.06-0ubuntu1_i386.deb) ... Selecting previously deselected package python-dateutil. Unpacking python-dateutil (from .../python-dateutil_1.4.1-3_all.deb) ... Selecting previously deselected package python-decorator. Unpacking python-decorator (from .../python-decorator_3.2.0-1_all.deb) ... Selecting previously deselected package python-matplotlib-data. Unpacking python-matplotlib-data (from .../python-matplotlib-data_0.99.3-1ubuntu1_all.deb) ... Selecting previously deselected package python-pyparsing. Unpacking python-pyparsing (from .../python-pyparsing_1.5.2-2_all.deb) ... Selecting previously deselected package python-tz. Unpacking python-tz (from .../python-tz_2010b-1_all.deb) ... Selecting previously deselected package python-matplotlib. Unpacking python-matplotlib (from .../python-matplotlib_0.99.3-1ubuntu1_i386.deb) ... Selecting previously deselected package python-opengl. Unpacking python-opengl (from .../python-opengl_3.0.1~b2-1_all.deb) ... Selecting previously deselected package python-pytools. Unpacking python-pytools (from .../python-pytools_10-7_all.deb) ... Selecting previously deselected package python-pyopencl. Unpacking python-pyopencl (from .../python-pyopencl_0.92~beta+git20100709-1ubuntu1_i386.deb) ... Processing triggers for man-db ... Processing triggers for doc-base ... Processing 1 added doc-base file(s)... Registering documents with scrollkeeper... Setting up dkms (2.1.1.2-3ubuntu1.1) ... Setting up nvidia-current (260.19.06-0ubuntu1) ... update-alternatives: using /usr/lib/nvidia-current/ld.so.conf to provide /etc/ld.so.conf.d/GL.conf (gl_conf) in auto mode. update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so.1 (of link group gl_conf) doesn't exist. update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so (of link group gl_conf) doesn't exist. update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-2.6.35-30-generic Removing old nvidia-current-260.19.06 DKMS files... -------- Uninstall Beginning -------- Module: nvidia-current Version: 260.19.06 Kernel: 2.6.35-30-generic (i686) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-30-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod....... DKMS: uninstall Completed. ------------------------------ Deleting module version: 260.19.06 completely from the DKMS tree. ------------------------------ Done. Loading new nvidia-current-260.19.06 DKMS files... Building for 2.6.35-30-generic and 2.6.39-2.dmz.1-liquorix-686 Building for architecture i686 Building initial module for 2.6.35-30-generic Done. nvidia-current.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.35-30-generic/updates/dkms/ depmod.... DKMS: install Completed. Building initial module for 2.6.39-2.dmz.1-liquorix-686 Error! Bad return status for module build on kernel: 2.6.39-2.dmz.1-liquorix-686 (i686) Consult the make.log in the build directory /var/lib/dkms/nvidia-current/260.19.06/build/ for more information. Traceback (most recent call last): File "/usr/share/apport/package-hooks/dkms.py", line 57, in <module> report.write(open(apport.fileutils.make_report_path(report), 'w')) IOError: [Errno 2] No such file or directory: '/var/crash/nvidia-current.0.crash' dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 10 Setting up python-dateutil (1.4.1-3) ... Setting up python-decorator (3.2.0-1) ... Setting up python-matplotlib-data (0.99.3-1ubuntu1) ... Setting up python-pyparsing (1.5.2-2) ... Setting up python-tz (2010b-1) ... Setting up python-opengl (3.0.1~b2-1) ... dpkg: dependency problems prevent configuration of python-pyopencl: python-pyopencl depends on nvidia-current; however: Package nvidia-current is not configured yet. dpkg: error processing python-pyopencl (--configure): dependency problems - leaving unconfigured Processing triggers for python-central ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up python-matplotlib (0.99.3-1ubuntu1) ... Setting up python-pytools (10-7) ... Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.39-2.dmz.1-liquorix-686 Processing triggers for python-support ... Errors were encountered while processing: nvidia-current python-pyopencl E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up nvidia-current (260.19.06-0ubuntu1) ... update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-2.6.35-30-generic Removing old nvidia-current-260.19.06 DKMS files... -------- Uninstall Beginning -------- Module: nvidia-current Version: 260.19.06 Kernel: 2.6.35-30-generic (i686) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko: - Uninstallation - Deleting from: /lib/modules/2.6.35-30-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod.... DKMS: uninstall Completed. ------------------------------ Deleting module version: 260.19.06 completely from the DKMS tree. ------------------------------ Done. Loading new nvidia-current-260.19.06 DKMS files... Building for 2.6.35-30-generic and 2.6.39-2.dmz.1-liquorix-686 Building for architecture i686 Building initial module for 2.6.35-30-generic Done. nvidia-current.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.35-30-generic/updates/dkms/ depmod.... DKMS: install Completed. Building initial module for 2.6.39-2.dmz.1-liquorix-686 Error! Bad return status for module build on kernel: 2.6.39-2.dmz.1-liquorix-686 (i686) Consult the make.log in the build directory /var/lib/dkms/nvidia-current/260.19.06/build/ for more information. Traceback (most recent call last): File "/usr/share/apport/package-hooks/dkms.py", line 57, in <module> report.write(open(apport.fileutils.make_report_path(report), 'w')) IOError: [Errno 2] No such file or directory: '/var/crash/nvidia-current.0.crash' dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 10 dpkg: dependency problems prevent configuration of python-pyopencl: python-pyopencl depends on nvidia-current; however: Package nvidia-current is not configured yet. dpkg: error processing python-pyopencl (--configure): dependency problems - leaving unconfigured Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.39-2.dmz.1-liquorix-686 Processing triggers for python-support ... Errors were encountered while processing: nvidia-current python-pyopencl keantoken@ubuntu:~$ Unfortunately the terminal is configured by default to just forget everything you've just gone through after a number of lines. Fixed that too late. I'm sorry if this is too long, but I don't know what to look for. I wouldn't have tried, but I searched and found pages saying "upgrading to Liquorix in Ubuntu is easy!". Back to top |
|||||
|
I've seen older dkms nvidia's fail to remove properly until you actually remove dkms itself. dkms has always been a really bad package in debian/ubuntu, because it doesn't follow the packaging rules at all, removing it doesn't remove its actions in many cases, removing an nvidia package from dkms does not turn off that nvidia package, an issue I've seen many times in the past, that's a total failure of the dkms package, and that package should be banned from debian in my opinion until it starts acting like a normal package that you install and uninstall reliably and cleanly. Why dkms cannot do this is I assume the result of some nasty dkms hacks.
Those are aptitude errors, also, do NOT do anything further with apt until you resolve the initial aptitude update errors you got. With apt, it's a bad habit to keep going with a new action when an old action remains unresolved. I don't like supporting dkms problems, it's crappy software in my opinion, and I don't like wasting my time on problems it has caused. The best thing to do is probably: apt-get purge dkms Not, note, aptitude. Then see how far you get. Also fix your apt-get update issues before you do other stuff, you are doing things wrong all over the place here, far too many things for me to actually help you. First do apt-get update fix any errors you encounter there. Do not proceed if you see something like failed to get a lock file, that means apt is active and running on a problem. I have been over the last year increasingly tempted to drop all ubuntu support, to be honest, but I do see ubuntu users who don't have these issues, so I assume it's something in how ubuntu does this process, but I don't run ubuntu except for rare testing / debugging sessions for sgfxi. And I've never really seen any issues with it, but I don't use it much. Back to top |
|||||
|
By the way, I really can see no reason for you running liquorix, for example, your vbox ose will NOT work with a newer kernel, you need vbox 4.x if I remember right.
The fact is, on a new ubuntu, not a LTR version that is older, Liquorix does install fine, but it's the other garbage in the system that causes you problems, all the dkms packages which MUST fail since they are for software versions too old for the bleeding edge liquorix kernel, which is the latest available. So you had started with a clean system, no extra junk installed, then installed the liquorix, then nvidia via sgfxi, then downloaded the most recent vbox deb directly from oracle/sun repos, not ubuntu's, you'd probably be fine. The main issue I have with ubuntu users in terms of support is there are just too many unknowns, and ubuntu users sadly don't tend to know the amount of things they are doing to make problems because ubuntu tries to hide these processes from the users without you the user actually understanding what happened when you clicked x or y in a gui, or what it means when apt has errors, or how to handle them. Back to top |
|||||
|
Doesn't sgfxi already try removing dkms and all packages with the string "nvidia" or "fglrx" in them? That would be really nice for cleaning up Ubuntu before installing drivers from the native installers.
Back to top |
|||||
|
it tries, certainly. But I've seen cases where removing the nvidia dkms package did NOT result in full removal, and dkms stubbornly tried to reinstall nvidia every boot.
Removing dkms itself solves this, but I can't have sgfxi remove dkms, much as I'd like to do that. There appears to be problems with older dkms modules, I see this now and then, but I believe the problem here is that ubuntu maverick has the wrong nvidia/vbox package for a new kernel, and then there's some other glitches. Certainly by far and away the easiest way to support users is to have them run sgfxi which will then try to do the cleanup, and whatever else might be required, like nouveau blocking, then we can go on from there at least having some idea of what the system is at that point. If dkms keeps trying to install the non existent nvidia, which I have seen, the only practical solution seems to be removing dkms itself. I'm sure there is some file, whose syntax I'm sure changes at random, that can be edited to remove the nvidia line, but one of the stupid joys of dkms is you cannot simply tell it to remove all nvidia modules and not try to install them again, you must know what the module number is, and give that to dkms. As I've noted, dkms is the worst piece of software I have seen since starting to use Linux full time, though nouveau is now giving it a very good run... Back to top |
|||||
|
Thanks for the help. I surprisingly didn't find any apt-get update errors, and I fixed that missing key error or whatever it was.
Sgfxi managed to install the nvidia driver for the generic kernel, but still fails for Liquorix, with a dkms error. I purged dkms and nvidia-current, and then used sgfxi. Then it didn't work, and I reinstalled nvidia-current/dkms, and then it still didn't work. Then I saw an error which said "api mismatch", I'm guessing that the Xorg.conf and installed drivers didn't match. So I restored xorg.conf from a backup, and did sgfxi again. Then it worked. I want to purge dkms/nvidia-current again and see if that allows me to install it for Liquorix. I started with Ubuntu because it seemed simple and well-managed like Windows... Can you suggest a different distribution that doesn't require advanced upkeep but is still flexible? I can learn Linux but until then I need to be able to DO something with it. Vbox isn't too important for me, I can upgrade. I had it because I intend to learn assembly language, but... Haha lol. I'll do that later. If I purge dkms, will that cause problems for other packages which include kernel modules? Thanks, - keantoken Back to top |
|||||
|
you have to purge dkms FIRST, period.
There's no point in posting until you do that, if you want to run Liquorix you cannot run an old ubuntu, didn't I say that already? Not until dkms and it's gunk is removed can we help you, sorry. Once that garbage is out of the system, and assuming you don't do more random things wrong as you've already done, then the nvidia driver should just install without issue with sgfxi with liquorix. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||