-
Notifications
You must be signed in to change notification settings - Fork 0
Description
I'm not quite sure how to approach this problem, and I don't think it's a problem with your package. My system is relatively new, only about 30 days old, and was initially installed with Debian 6.0 and later upgraded to Debian 7.0. I haven't built the kernel myself and no major changes have occurred.
In /lib/modules before installing dkms and this package, I had the directories:
2.6.32-5-amd64/ 3.2.0-4-amd64/
Now I have the directories:
2.6.32-5-amd64/ 3.2.0-4-686-pae/ 3.2.0-4-amd64/
Output from uname -a:
Linux home02 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
Output from package install (not first install; first install was done in Synaptic package manager and I lost that output.) :
root@home02:/home/ivan/softs# dpkg --install rts5229-dkms_1.0.7-1_all.deb
(Reading database ... 246507 files and directories currently installed.)
Preparing to replace rts5229-dkms 1.0.7-1 (using rts5229-dkms_1.0.7-1_all.deb) ...
Deleting module version: 1.0.7
completely from the DKMS tree.
Done.
Unpacking replacement rts5229-dkms ...
Setting up rts5229-dkms (1.0.7-1) ...
Loading new rts5229-1.0.7 DKMS files...
Building only for 3.2.0-4-amd64
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.