15/05/2011 11:23, Camaleón wrote: > On Sun, 15 May 2011 10:07:25 +0100, Brad Rogers wrote: > >> On Sun, 15 May 2011 08:37:43 +0000 (UTC) Camaleón <noela...@gmail.com> >> wrote: >> >> Hello Camaleón, > > (replying to your e-mail but also addressed to tv.debian's) > >>> Just a quick note on nvidia (or ati) proprietary drivers: they need the >>> corresponding kernel version package. >> >> Whilst what you say is true, a lot of the agony of installing nVidia >> drivers can be done away with by installing the nvidia-kernel-dkms >> package and associated dependencies. >> >> Doing that takes care of all the kernel dependant rebuilds of the >> driver, meaning that the sys-admin (me) doesn't have to remember to do >> it. > > :-) > > Don't ask me why -maybe due to inexperience-, but the first time I had to > deal with the closed nvidia driver in Debian I prefered¹ to not use > "dkms" and manually pulled the required packages which was the method I > was more used to. Hopefully, all went ok. > > And the same goes for my VirtuaBox client. Whenever I have to install or > update the "guest additions" I prefer to manually update the kernel > headers (which I hope they get automatically updated now that I've > installed the kernel meta-package). > > ¹I didn't know how this thingy worked, it is something I never used in > openSUSE, the distro I was using before coming to Debian. > > Greetings, >
I was a great fan of module-assistant, but since dkms entered Debian I don't miss m-a ! Give it a try, especially when using custom kernels it saves a lot of time for more interesting things than compiling modules. The only downside I see is philosophical, it makes using proprietary modules far too easy, there used to be some kind of redemption in the manual compilation suffering ;-) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dcfa39d.4030...@googlemail.com
