I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.
First of, Debian has the following versions of nvidia-kernel-dkms packages:
squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1
The version in squeeze fail on anything above
I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.
First of, Debian has the following versions of nvidia-kernel-dkms packages:
squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1
The version in squeeze fail on anything above
MRH writes:
>On 23/01/11 04:53, Cameron Hutchison wrote:
>> and I had to revert two commits to fix it:
>>
>> 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
>> regenerate kernel.release file when make kernelrelease)
>>
>> 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make ke
On 23/01/11 04:53, Cameron Hutchison wrote:
"tv.deb...@googlemail.com" writes:
The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with "kernel-package:
2.6.37" in the archives. But since it seems to affect only proprietary
soft
On 22/01/11 23:03, tv.deb...@googlemail.com wrote:
[...]
I have the same setup, I build my kernel (2.6.37 currently) with
kernel-package and both nvidia and VirtualBox 4 work fine (they build
automatically with dkms). I don't use extraversion, only
--append-to-version and --revision.
The problem
"tv.deb...@googlemail.com" writes:
>The problem with extraversion and 2.6.37 is known, it's been reported
>here if I remember, look for a message starting with "kernel-package:
>2.6.37" in the archives. But since it seems to affect only proprietary
>software I guess they'll have to adapt.
Since
On Saturday 22 January 2011 13:24:08 MRH wrote:
> Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
> that moment it stopped working, saying that the kernel driver (vboxdrv)
> is not loaded and suggesting to run /etc/init.d/vboxdrv setup
>
> This fails:
> --
> Stopping V
>On the 22/01/2011 23:20, MRH wrote:
>> On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
>> In<4d3b20c8.3080...@o2.pl>, MRH wrote:
>>>CC [M]
>>> /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
>>> In file included from
>>> /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox
On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
In<4d3b20c8.3080...@o2.pl>, MRH wrote:
CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
from
/var/lib/dkms/vboxho
In <4d3b20c8.3080...@o2.pl>, MRH wrote:
> CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
>In file included from
>/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
> from
>/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal
Hi,
You're not gonna get much help using non-free software on a tarnished
kernel. That said, when i have problems with VBox i just purge
everything, dkms included, make sure the drivers are actually deleted,
then reinstall, with dkms. Usually does the trick.
HTH,
Nuno
--
Mars 2 Stay!
http://xkc
Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
that moment it stopped working, saying that the kernel driver (vboxdrv)
is not loaded and suggesting to run /etc/init.d/vboxdrv setup
This fails:
--
Stopping VirtualBox kernel modules:done..
Uninstalling old VirtualBo
12 matches
Mail list logo
