Nvidia driver - Debian way, custom (or not) kernel.

Share your own howto's etc. Not for support questions!
Post Reply
Message
Author
mindtrick
Posts: 10
Joined: 2006-08-29 22:31

#46 Post by mindtrick »

Anyway, upgrading to Sid.

User avatar
mzilikazi
Forum Ninja
Posts: 3321
Joined: 2004-09-16 02:14
Location: Colorado Springs, CO

#47 Post by mzilikazi »

mindtrick wrote:Anyway, upgrading to Sid.
You don't have to upgrade just pull the source from Sid and comment out the repo.
Debian Sid Laptops:
AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55 / 1.5G
Intel(R) Pentium(R) Dual CPU T2390 @ 1.86GHz / 3G

User avatar
neonl
Posts: 27
Joined: 2007-08-30 11:11

#48 Post by neonl »

Hi.

I'm a complete n00b at Debian (recently arrived form Ubuntu ;)) and I'm having a problem witch may be kind of stupid.

When I try to run the first line of the tutorial I get this:

Code: Select all

rui-debian:/home/rui# apt-get update && apt-get install nvidia-kernel-source module-assistant nvidia-settings nvidia-xconfig
Ign cdrom://[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21] etch Release.gpg
Ign cdrom://[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21] etch Release
Ign cdrom://[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21] etch/contrib Packages/DiffIndex
Ign cdrom://[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21] etch/main Packages/DiffIndex
Get:1 http://ftp.uevora.pt etch Release.gpg [378B]
Hit http://ftp.uevora.pt etch Release
Ign http://download.videolan.org sarge Release.gpg
Ign http://ftp.uevora.pt etch/main Packages/DiffIndex
Ign http://download.videolan.org sarge Release
Ign http://ftp.uevora.pt etch/main Sources/DiffIndex
Ign http://download.videolan.org sarge/main Packages/DiffIndex
Hit http://ftp.uevora.pt etch/main Packages
Ign http://download.videolan.org sarge/main Sources/DiffIndex
Hit http://ftp.uevora.pt etch/main Sources
Ign http://download.videolan.org sarge/main Packages
Ign http://download.videolan.org sarge/main Sources
Hit http://download.videolan.org sarge/main Packages
Get:2 http://security.debian.org etch/updates Release.gpg [189B]
Hit http://download.videolan.org sarge/main Sources
Hit http://security.debian.org etch/updates Release
Ign http://security.debian.org etch/updates/main Packages/DiffIndex
Ign http://security.debian.org etch/updates/contrib Packages/DiffIndex
Ign http://security.debian.org etch/updates/main Sources/DiffIndex
Ign http://security.debian.org etch/updates/contrib Sources/DiffIndex
Hit http://security.debian.org etch/updates/main Packages
Hit http://security.debian.org etch/updates/contrib Packages
Hit http://security.debian.org etch/updates/main Sources
Hit http://security.debian.org etch/updates/contrib Sources
Fetched 2B in 1s (1B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package nvidia-kernel-source
Do I need to update anything at /etc/apt/sources.list?

Thanks and sorry again if this is an Idiot question.

By the way, my graphic is a NVIDIA 8600 GT.
YOU! ARE! A! TOYYYYY! You're not the real Buzz Lightyear! You're - you are an action figure! - Toy Story

User avatar
mzilikazi
Forum Ninja
Posts: 3321
Joined: 2004-09-16 02:14
Location: Colorado Springs, CO

#49 Post by mzilikazi »

neonl wrote:Hi.Do I need to update anything at /etc/apt/sources.list?

Thanks and sorry again if this is an Idiot question.

By the way, my graphic is a NVIDIA 8600 GT.
Not an idiot question but yes - you need an Etch repo in sources.list. I have this one:

Code: Select all

deb http://ftp.us.debian.org/debian etch main contrib non-free
Debian Sid Laptops:
AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55 / 1.5G
Intel(R) Pentium(R) Dual CPU T2390 @ 1.86GHz / 3G

User avatar
neonl
Posts: 27
Joined: 2007-08-30 11:11

#50 Post by neonl »

Hi.

Problems again. Now when doing "apt-get install nvidia-glx" I get this

Code: Select all

neonland:/home/rui# apt-get install nvidia-glx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  nvidia-glx: Depends: nvidia-kernel-100.14.19 but it is not installable
The repos us.debian.org are enabled I done apt-get update...

The strangest thing is that I installed once already...
YOU! ARE! A! TOYYYYY! You're not the real Buzz Lightyear! You're - you are an action figure! - Toy Story

didi
Posts: 909
Joined: 2007-12-04 16:26
Location: the Netherlands

Re: Nvidia 100.14.19 - Debian way, custom (or not) kernel.

#51 Post by didi »

mzilikazi wrote: THERE IS NO NEED TO INSTALL FROM EXPERIMENTAL AT THIS TIME!
I do however leave the Experimental instructions for reference and it's likely that in the future we'll need the experimental repo again. (See bottom for Experimental instructions)
Thanks for that, it allowed me to install nvidia drivers the debian way (on Testing)
Standard method
You need some specific tools to build this:

Code: Select all

apt-get update && apt-get install nvidia-kernel-source module-assistant nvidia-settings nvidia-xconfig
In testing it couldn't/can't find nvidia-kernel-source, but it was available in sid. See below for more :lol:
I'd switch to a VT at this point and stop your DM

Code: Select all

CTRL+ALT+F1
/etc/init.d/gdm stop
or /etc/init.d/kdm stop if you're using kde, like you described at the experimental repos way ;)


EXPERIMENTAL NVIDIA DRIVER
THIS is for experienced users or at least those who do not mind fixing what they break. ;) If you do want the latest greatest bleeding edge Nvidia driver, here it is:

BELOW are instructions for getting your nvidia driver from the experimental branch. As of 4.23.07 this is not necesary. I leave it here for completeness.
Add an experimental repo to /etc/apt/sources.list

Code: Select all

deb http://ftp.de.debian.org/debian experimental main contrib non-free
deb-src http://ftp.de.debian.org/debian experimental main contrib non-free
Get updated, install the necesary packages

Code: Select all

apt-get update && apt-get install nvidia-kernel-source/experimental module-assistant nvidia-settings
Well, I'm not an experienced user, but got it working through this way afterall.
Since the nvidia-kernel-source package wasn't available in the testing repos, I added those two lines to my sources.list and then tried apt-get install nvidia-kernel-source/experimental, which gave me errors (couldn't find it or sth like that).
But when I changed it to apt-get install nvidia-kernel-source (without the "/experimental") it did install. After that I commented out the sid repos, since I didn't want any (more) updates from that.
Followed the rest of your directions and got it working 8)

User avatar
bluesdog
Posts: 2082
Joined: 2006-02-01 09:02
Location: Similkameen, British Columbia, Canada

#52 Post by bluesdog »

neonl wrote:Hi.

Problems again. Now when doing "apt-get install nvidia-glx" I get this

Code: Select all

neonland:/home/rui# apt-get install nvidia-glx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  nvidia-glx: Depends: nvidia-kernel-100.14.19 but it is not installable
The repos us.debian.org are enabled I done apt-get update...

The strangest thing is that I installed once already...
Check your repositories include, temporarily, sid/unstable

Example:
deb http://ftp.us.debian.org/debian sid main contrib non-free
nvidia-kernel-source 100.14.19-1 from sid/unstable, is required by nvidia-glx 100.14.19

Temporarily add sid repository,

Code: Select all

apt-get update
apt-get install nvidia-kernel-source
do your module build using nvidia-kernel-source 100.14.19-1, then

Code: Select all

apt-get update
apt-get install nvidia-glx
Tips & Tricks

Something more to read while waiting

If you obviously have not read THIS, don't expect too much...




*winter bluesdog....*

User avatar
roadnottaken
Posts: 163
Joined: 2007-08-20 17:54

#53 Post by roadnottaken »

I just took a look at the nvidia drivers (both the debian packages and the upstream drivers) and discovered a very wide spread of versions. The Etch version is 1.0.x, the Sid version is 100.x, and the drivers from nVidia are version 169.x (and there is no Lenny version due to release-critical bugs). Why is there such a huge spread in the version numbers?

I also noticed that the version in Etch does not seem to support any of the gforce chips. Is this correct? Finally, why does nvidia-glx from Sid have a broken dependency (nvidia-kernel-100.14.19)?

User avatar
llivv
Posts: 5484
Joined: 2007-02-14 18:10
Location: cold storage

#54 Post by llivv »

Those are all $10000 questions. Let me see how close I can come to answering them correctly.
roadnottaken wrote: Why is there such a huge spread in the version numbers?
Both Debian and upstream devels have a "standard?" way of numbering versions. Since packages usually have more than one file in them, when certain files in the package change the version number changes to reflect the changlog for the updated files. When other files in the package are updated both the changlog and the version number are different to reflect what has been updated in the package. ( at least this is how I understand it so far)
roadnottaken wrote:I also noticed that the version in Etch does not seem to support any of the gforce chips. Is this correct?
sorry but I always seem to get confused by what is the gForce GPU and what is the gForce chipset. nForce too shessh!
roadnottaken wrote:Finally, why does nvidia-glx from Sid have a broken dependency (nvidia-kernel-100.14.19)?
It probably depends on who you ask, as to what kind of answer you'll get to this kind of question. Let me refer you to someone elses take on it instead of me making a fool of myself by typing in something I know zilch about.
nvidia_is_bad_at_coding.png and if you don't get it, join the crowd :wink:

Oh and by the way, the new version of metacity is hopefully going into experimental soon. You can get it at the maintainers site now. And it has composition enabled by default.
metacity maintainer wrote:hey guys,

here in italy are 3.02 a.m and i'm still drunk (as my friend XX said:"i have a problem with alcol.. i like it") , but i made a good thing for all the crazy guys who run experimental, i've build latest metacity (the GNOME window manager).

The cool thing of version 2.21.5 (experimetal) is that it is build with the composition manager enabled by default.

all my changes are in the debian pkg-gnome svn, but i'm not sure if i should upload it right now, so feel free to take it on my home on people .
I like a good double of scotch (or two or three ....) every once in a while too, Riccardo ... :wink: and thank you very much.

User avatar
bluesdog
Posts: 2082
Joined: 2006-02-01 09:02
Location: Similkameen, British Columbia, Canada

#55 Post by bluesdog »

...why does nvidia-glx from Sid have a broken dependency (nvidia-kernel-100.14.19)?
The pre-built nvidia-kernel packages in Debian unstable repositories always seem to lag behind the available nvidia-glx driver.
Perhaps the assumption is those who use unstable stuff also build their own modules :wink:

To satisfy the dependency, just build the kernel module package from nvidia-kernel-source, as outlined above.

The list of supported chipsets is available in /usr/share/doc/nvidia-glx/README.txt.gz


... solstice cheers and best wishes to one and all <hic>
Tips & Tricks

Something more to read while waiting

If you obviously have not read THIS, don't expect too much...




*winter bluesdog....*

Kingghost
Posts: 11
Joined: 2006-05-16 08:47

#56 Post by Kingghost »

I'm having issues installing the drivers. I'm currently running SID, with kernal 2.6.23-1-486. ANywho when Installing the drivers I get a couple errors.

Code: Select all




 ┌─────────Building nvidia-kernel-source, step 2, please wait...───────────┐
 │ Done! Run                                                               │
 │ m-a install nvidia-kernel-source                                        │
 │ to install.                                                             │
 │                                                                         │
 │                                                                         │
 │                                                                         │
 │                                                                         │
 │                                                                         │
 │                                                                         │
 │                                                                         │
 │  ┌───────────────────────────────────────────────────────────────────┐  │
 │  │                               100%                                │  │
 │  └───────────────────────────────────────────────────────────────────┘  │
 └─────────────────────────────────────────────────────────────────────────┘




Done with /usr/src/nvidia-kernel-2.6.23-1-486_100.14.19-1+2.6.23-2_i386.deb .
dpkg -Ei /usr/src/nvidia-kernel-2.6.23-1-486_100.14.19-1+2.6.23-2_i386.deb
Selecting previously deselected package nvidia-kernel-2.6.23-1-486.
(Reading database ... 128072 files and directories currently installed.)
Unpacking nvidia-kernel-2.6.23-1-486 (from .../nvidia-kernel-2.6.23-1-486_100.14                                                                                                                               .19-1+2.6.23-2_i386.deb) ...
dpkg: dependency problems prevent configuration of nvidia-kernel-2.6.23-1-486:
 nvidia-kernel-2.6.23-1-486 depends on nvidia-kernel-common (>= 20051028+1-0.1);                                                                                                                                however:
  Package nvidia-kernel-common is not installed.
dpkg: error processing nvidia-kernel-2.6.23-1-486 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-kernel-2.6.23-1-486

I: Direct installation failed, trying to post-install the dependencies

apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  nvidia-kernel-common
The following NEW packages will be installed:
  nvidia-kernel-common
0 upgraded, 1 newly installed, 0 to remove and 58 not upgraded.
1 not fully installed or removed.
Need to get 4526B of archives.
After unpacking 115kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://debian.yorku.ca sid/contrib nvidia-kernel-common 20051028+1-0.1 [45                                                                                                                               26B]
Fetched 4526B in 2s (1871B/s)
Selecting previously deselected package nvidia-kernel-common.
(Reading database ... 128079 files and directories currently installed.)
Unpacking nvidia-kernel-common (from .../nvidia-kernel-common_20051028+1-0.1_all                                                                                                                               .deb) ...
Setting up nvidia-kernel-common (20051028+1-0.1) ...

************************************************************************
*
* The update-modules command is deprecated and should not be used!
*
************************************************************************

Setting up nvidia-kernel-2.6.23-1-486 (100.14.19-1+2.6.23-2) ...
slutb0x:/htpc# rmmod nvidia
slutb0x:/htpc# /etc/init.d/gdm restart /proc/modules
Stopping GNOME Display Manager: gdm.
Starting GNOME Display Manager: gdm.nf


When GDM starts it displays an error

Kingghost
Posts: 11
Joined: 2006-05-16 08:47

#57 Post by Kingghost »

I got around this by doing..

update-pciids && apt-get install module-assistant nvidia-kernel-source && m-a prepare && m-a a-i nvidia && apt-get install nvidia-glx && depmod -a && modprobe nvidia && dpkg-reconfigure xserver-xorg

Eck
Posts: 740
Joined: 2007-06-27 16:13

#58 Post by Eck »

Maybe those couple of additions would have helped, but the normal ways didn't work for me today with my previously install nvidia drivers from Sid on my Lenny system. I kept getting the 100.14.19 kernel modules built and that making it impossible to upgrade nvidia-glx.

I purged my Sid sources, nvidia-kernel-100.14.19, nvidia-glx, nvidia-glx-dev, nvidia-settings, nvidia-xconfig, nvidia-kernel-source, nvidia-kernel-common, xserver-xorg-core and its friends and reinstalled the deskop, gnome-desktop, kde-desktop tasks, gnome-desktop-environment, xorg-dev, removed nvidia from /etc/modules.conf, dpkg-reconfigured nv back in, booted into it, and installed the downloaded NVidia driver from upstream.

No more Sid sources to be concerned about or problems with NVidia driver changes when upgraded. I had used the Debian way for the first time this time, and it had been fine but this upgrade would have left me with nv as I couldn't get module-assistant to do the upgrade and nvidia-glx was impossible to install with the 100.14.19 that module-assistant always left me with. It just wouldn't build 169.07 kernel even though that's the source I had upgraded to. It would take that source and install 100.14.19 somehow.

Interestingly, compiz (compiz-manager really) reports what --no-libgl-fallback is an unknown switch (I added it as the new driver requires that, or has required it since the beta). But it starts Compiz Fusion fine anyway and all is working. Strange.
Lenovo z560 Laptop Nvidia GeForce 310m Hitachi 500GB HD Intel HD Audio 4GB RAM

User avatar
roadnottaken
Posts: 163
Joined: 2007-08-20 17:54

#59 Post by roadnottaken »

You shouldn't use nv as your fall-back driver. I've found that the generic "vesa" driver usually works better with my nVidia card (a GeForce 8400). Specifically, I noticed that, using the nv driver, switching between the GUI and a terminal was a lot slower as was anything else involving graphics, and cpu usage was much higher (compared with the vesa driver).

Eck
Posts: 740
Joined: 2007-06-27 16:13

#60 Post by Eck »

No problem. I usually don't have nv running long enough to notice its peculiarities.

I just removed my additional --no-libgl-fallback compiz option and compiz started up fine without it using the 169.07 NVidia script driver. I'm surprised actually. I had thought that was needed, but for some nice reason this official Debian Lenny Compiz Fusion set works fine without bothering to add that. Maybe it does it in some mysterious way that doesn't include that command.

I'm actually happy that I'm not mixing distributions anymore. I did apt-show-versions | grep unstable and I have nothing left over from before. Nice. All Lenny now. Guess I'll get rid of that /etc/apt/apt.conf file.

Of course, the caveat is I will now need to do nvidia-installer --uninstall and reinstall the driver after any xorg or kernel upgrades, but I was always used to doing that so it's really no big deal.
Lenovo z560 Laptop Nvidia GeForce 310m Hitachi 500GB HD Intel HD Audio 4GB RAM

Eck
Posts: 740
Joined: 2007-06-27 16:13

#61 Post by Eck »

Bug #459848 shows that I wasn't crazy (but I know better).

Module Assistant can't build the nvidia-kernel-source because the package has been renamed and m-a can't find it to unpack once it is installed.

A work around regarding renaming the installed package and doing one other change (at least for the 64 bit, maybe just the rename is needed for i386) then allows m-a to build the source.

That's also a good reason why nvidia-glx couldn't install. It depends upon that nvidia-kernel-169.07 installed and aptitude wouldn't install it without that. And I'm glad I didn't get insistent and force it since it wouldn't have worked on the 100.14.19 Kernel that m-a kept installing with auto-install nvidia. If I did the individual steps and had it use the already upgraded source, it would fail to install, but if I did it fresh with auto-install it would install the older source. So either way (no kernel or 100.14.19) I wasn't going to get nvidia-glx to install or work.

The bug reporter requests a different package that will work with m-a, but I think the nvidia-kernel packages are renamed for a reason. They're getting ready for the 2.6.23 Kernels and a newer module-assistant and kernel module packages that WILL work the way he has named them.

That's my read anyway. So ideally for now it is probably best to install it without the use of module-assistant. That way they will have the newer name installed and the new m-a will later on seamlessly be able to see and work with the packages as the upgrades will also have the new style naming.

For me, yeah I could probably learn how to do it without m-a but I really couldn't be bothered. A simple ctrl-alt-F1, /etc/init.d/kdm stop, export CC=gcc-4.1, sh NVIDIA-Linux (tab).run and dpkg-reconfigure xerver-xorg and nvidia-xconfig --composite, and I'm done.

No need to run a mixed Lenny/Sid system or deal with a buggy xserver-1.4. When all this gets to Lenny and actually works properly perhaps I'll go back to the Debian way.

If you're wondering about the export CC=gcc-4.1, that's because the Debian kernels are built with the older 4.1 and the system runs with the newer version so the Nvidia installer warns about mismatched gcc versions. Since Debian does still keep 4.1 installed, and export just before installing the driver will show the 4.1 stuff so NVidia can use it to make a matching kernel module that is built with the same gcc that the Debian Kernel was built with.

The official Debian NVidia stuff includes a script that just has it ignore the mixmatch which is like a user telling the NVidia script to proceed anyway. Actually, having the installer use the same gcc version as was used to build the Kernel is the better way to go. So the NVidia downloaded driver from the NVidia website is actually a better all around method of installation, in my opinion.

Not for the package management system and placement of gl files so xorg, kernel, and mesa upgrades. The Debian way is better in that sense. It was nice having a system that had everything in more logical Debian specific places, similar to how specific Fedora, SUSE packages do it, but NVidia uses symlinks that work just fine. Just needs reinstalling whenever those other things are upgraded as they break the symlinks.

I'm just glad that the NVidia official script is available for times like this when the standard install method, module-assistant, gets buggy and doesn't work. Although it's really just a transition problem right now. But they should get that fixed somehow since lots of folks are going to be trying to get the update installed and will run into this mess. Think everyone's going to find their way to the bug reports on the package? I don't. Most will see the only way to fix this is to uninstall NVidia and use vesa or nv if they insist on not running the official NVidia installer.
Lenovo z560 Laptop Nvidia GeForce 310m Hitachi 500GB HD Intel HD Audio 4GB RAM

Eck
Posts: 740
Joined: 2007-06-27 16:13

#62 Post by Eck »

And now bug 454348 regarding the virtualbox-ose modules describes the same problem going on with module assistant not being able to build a module as it doesn't see any with the new naming scheme.

And, the developer responds that the user shouldn't be building the modules with module assistant so this is a no fix bug.

Great. Someone know how to build modules the old, manual way that wants to make guides for NVidia and Virtualbox?

I said in the latest reply that this is supposed to be the new, improved way? No thanks. Let's go back to the semi-automatic module assistant please?

What? Is aptitude supposed to do this automatically now? If it is supposed to, it isn't working as I have the module listed in /etc/modules.conf and unless I use module-assistant (works with virtualbox because an older module is available, but not with NVidia because there isn't an older one). nothing loads and virtualbox cannot start a virtual machine.

A won't fix bug. I don't get it. It's a feature! Debian is turning into Microsoft if making something break so a user can't use it is a won't fix bug.
Lenovo z560 Laptop Nvidia GeForce 310m Hitachi 500GB HD Intel HD Audio 4GB RAM

hkoster1
Posts: 1269
Joined: 2006-12-18 10:10

#63 Post by hkoster1 »

@Eck... why am I getting so tired reading all your stuff? Too many letters, too many words, too many sentences, if you ask me.

OK, let me just summarize the current (10 January 2008) situation:

1. There's a new version of nvidia-glx, etc, in Sid: 169.07-1, that won't install because the corresponding nvidia-kernel module isn't available.

2. Module-assistant won't unpack the nvidia-kernel source archive, so this must be done by hand in /usr/src (as root)

Code: Select all

tar xvjf nvidia-kernel.tar.bz2
Edit: it's a bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459862

3. Now (still as root)

Code: Select all

m-a a-i nvidia-kernel
compiles/installs the new nvidia-kernel-2.6.23-1-amd64_169.07-1+2.6.23-2_amd64.deb package OK, and likely for other kernels too.

4. Still as root,

Code: Select all

aptitude update && aptitude full-upgrade
to install the matching 169.07-1 nvidia-glx, etc package.

5. Clean up (get rid of old 100.14.19 stuff), restart X and enjoy!

@Mzilikazi -- change the title of this thread?
Last edited by hkoster1 on 2008-01-14 09:29, edited 2 times in total.
Real Debian users don't do chat...

Eck
Posts: 740
Joined: 2007-06-27 16:13

#64 Post by Eck »

That's all I had to do? Unpack the thing?

Well...

That was easy. Maybe. I'll go try it with Virtualbox, probably sticking with the NVidia official binary since it's installed and working. No Sid needed.

Gosh yes, I do get wordy. But I have so much to say! :)

Edit -

Nope, module assistant will still substitute the older module and warn that it is replacing the newer virtualbox-ose module while it is doing the auto-install. Then Aptitude will offer to upgrade it again, breaking Virtualbox by removing the kernel module.

The Debian Wiki article on Virtualbox saved the day and allowed me to use the newer source and module.

I used its instructions for Etch, which doesn't have pre-built modules for Virtualbox. I extracted the tarball that Aptitude had deposited in /usr/src like you said, but this time cd to the /usr/src/modules/virtualbox-ose.

Instead of running module assistant I did make and make install in that folder. I did modprobe vboxdrv and, magically, it was there to run and lsmod | grep vbox showed me a number. I'll have to remember to make uninstall before this stuff gets upgraded again.

So I've got Virtualbox-ose 2.5.2 running with the latest virtualbox kernel for it. Most won't figure this out, I wouldn't think.

See, this is broken. So sorry everyones so sick of my posts but this is a critical bug. Of course it will be fixed automatically when 2.6.23 and the modules get redone and into Lenny, but until then there is no using module assistant for this stuff unless we use the older packages.

The deb for the older virtualbox-ose module is in /usr/src, and that is what module assistant unpacks even if the newer tarball is extracted. It simply replaces the updated files with the older ones from the deb file it extracts, ignoring the tarball.

Maybe it works for nvidia, but I won't be going through all that, thank you.
Lenovo z560 Laptop Nvidia GeForce 310m Hitachi 500GB HD Intel HD Audio 4GB RAM

lubor
Posts: 3
Joined: 2008-01-13 17:02

#65 Post by lubor »

Code: Select all

m-a a-i nvidia
Last edited by lubor on 2009-12-23 23:18, edited 1 time in total.

Post Reply