linux-restricted-modules for fglrx not installed

Bug #92854 reported by Stani
28
Affects Status Importance Assigned to Milestone
restricted-manager (Ubuntu)
Fix Released
Wishlist
Martin Pitt

Bug Description

Binary package hint: restricted-manager

I have an ati X1300. On a freshly installed Feisty I enabled the ati fglrx driver with restricted-manager. It enabled the driver, without being in use. I rebooted the computer and flgrxinfo was still pointing to mesa3d. I installed linux-restricted-modules and rebooted. Then my 3D acceleration worked. So my question is should restricted-modules not install also linux-restricted-modules, otherwise not experienced users might be lost?

Revision history for this message
Martin Pitt (pitti) wrote :

Indeed, but it's normally installed by default, so it's not a huge release blocker.

Changed in restricted-manager:
assignee: nobody → pitti
importance: Undecided → Medium
status: Unconfirmed → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

In fact, I wonder how this works at all. If linux-restricted-modules-... is not installed, then there are no restricted kernel modules that restricted-manager could probe and thus it should not display anything at all. Can you reproduce the situation and give me the output of

  dpkg -l 'linux*'

when it shows this erroneous behaviour? Thank you!

Changed in restricted-manager:
status: In Progress → Needs Info
Revision history for this message
Martin Pitt (pitti) wrote :

Ah, it displays them because of bug 93368, the entries in the manual module information lists are not checked for actual module existance.

So r-m should just give a warning if l-r-m is not installed and offer to install it.

Changed in restricted-manager:
importance: Medium → Wishlist
status: Needs Info → Confirmed
Revision history for this message
Stani (stani) wrote :

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-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.

Thanks for your help,

Stani

Revision history for this message
Stani (stani) wrote :

Just to clarify, what happens to an end-user. He will see that his driver is enabled, but can not be put in use. This might be confusing. It would be better if he tries to click in use, that a dialog pops up asking: "This feature needs the *** modules. Do you want to install them?" In the beginning I was clicking several times on the checkbox of "in use" and got a bit frustrated as it was not possible and there was no feedback.

Martin Pitt (pitti)
Changed in restricted-manager:
status: Confirmed → In Progress
Martin Pitt (pitti)
Changed in restricted-manager:
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

 restricted-manager (0.16) feisty; urgency=low
 .
   * restricted-manager: Add proper status text for 'not in use'. (LP: #97724)
   * restricted-manager: Do not show the confirm dialog when a driver cannot be
     changed anyway.
   * RestrictedManager/xorg_driver.py: Check if /etc/X11/xorg.conf exists, and
     if not, have can_change() return False. (LP: #97654)
   * restricted-manager: Check whether we have the correct l-r-m package
     installed and display an error dialog if not. (LP: #92854)
   * RestrictedManager/nvidia.py: Fix DefaultDepth to 24 when enabling the
     driver. (LP: #97735)

Changed in restricted-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.