I dived into it deeper and my first bug report could have been made more accurate. The problem is that on my computer the linux-restricted-modules-common were installed, but not the linux-restricted-modules-2.6.20-11-generic, which correspond to "uname -r". Is this normal? The only other manipulation of my system was that I removed compiz, but that should not remove the generic modules. I never removed "linux-restricted-modules-2.6.20-11-generic" consciously myself.
If you want to reproduce this for yourself, it is very easy: just remove the package "linux-restricted-modules-2.6.20-11-generic" without removing "linux-restricted-modules-common".
I attach "dpkg -l 'linux*'" in a file.
I think that restricted-manager should check if "linux-restricted-modules-2.6.20-11-generic" (or corresponding) is really installed. There can always be a reason it is not installed or removed.
Hi Martin,
I dived into it deeper and my first bug report could have been made more accurate. The problem is that on my computer the linux-restricte d-modules- common were installed, but not the linux-restricte d-modules- 2.6.20- 11-generic, which correspond to "uname -r". Is this normal? The only other manipulation of my system was that I removed compiz, but that should not remove the generic modules. I never removed "linux- restricted- modules- 2.6.20- 11-generic" consciously myself.
If you want to reproduce this for yourself, it is very easy: just remove the package "linux- restricted- modules- 2.6.20- 11-generic" without removing "linux- restricted- modules- common" .
I attach "dpkg -l 'linux*'" in a file.
I think that restricted-manager should check if "linux- restricted- modules- 2.6.20- 11-generic" (or corresponding) is really installed. There can always be a reason it is not installed or removed.
Thanks for your help,
Stani