What's the best way to disable suggesting some drivers?

Asked by Sergey "Shnatsel" Davidoff

I need to prevent Jockey from suggesting installing fglrx in my distro because it has known issues with the WM in use. What's the best way to do it? By "best" I mean clean and not requiring a lot of tweaking/maintenance.

Is deleting the .py of the handler sufficient, or there's some config file with handler list or something?

Question information

Language:
English Edit question
Status:
Solved
For:
Jockey Edit question
Assignee:
No assignee Edit question
Solved by:
Sergey "Shnatsel" Davidoff
Solved:
Last query:
Last reply:
Revision history for this message
Martin Pitt (pitti) said :
#1

Any of the following options will work, depending on what you want to achieve:

 - Delete the handler in /usr/share/jockey/handlers
 - Adjust the handler's "available()" method with some custom code if you only want to disable it in particular circumstances
 - Update the fglrx package to drop modaliases (i. e. models) which are known to not work; this could/should even happen in Ubuntu itself

Unfortunately you can't override it in /usr/share/jockey/modaliases (see https://bugs.launchpad.net/jockey/+bug/850223).

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#2

Thanks Martin Pitt, that solved my question.

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#3

I want to disable fglrx because it doesn't play well with Mutter (and vsynced Clutter in general) and has dreadful issues with dual-screen under Mutter. Since open-source AMD drivers are supported by AMD and work much better, we'd prefer to stick to them by default, but still allow power users to install fglrx if they know what they are doing. So I guess I'll simply delete the Jockey handler.

I'm also leaning towards blacklisting vboxdrv - it also has a lot of known issues and been dubbed "tainted crap" on LKML (see http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw). In addition, the guest additions version from Ubuntu repos is usually outdated (as of my experience anyway). I hear a redesign of Jockey is upcoming, so you might want to drop it in Ubuntu too.

As for Nvidia, we'll probably investigate installing the proprietary driver on boot to avoid the hit-or-miss reverse-engineered Nouveau. Jolicloud already did that, see https://github.com/jolicloud/jolicloud-hardware

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#4

Oh, there's no more handler for vboxdrv. Sorry, my bad.

Thanks a lot for your help!

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#5

Hmm, Jockey still suggests installing fglrx even though I've deleted /usr/share/jockey/handlers/fglrx.py
What else shall I tweak to prevent Jockey from suggesting installing it?

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#6

Jockey even claims to successfully install the driver despite the fact that /usr/share/jockey/handlers/fglrx.py is missing.

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#7

I've found a "disable-jockey-fglrx" package at http://dell.archive.canonical.com/updates/pool/public/d/disable-jockey-fglrx/
Looks like it's exactly what I'm looking for.

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) said :
#8

For the record, removing the helper didn't help and the above package is complex enough to be useless in our case.

The simplet way to do this for fglrx is to hijack the function available(self) in /data/handlers/fglrx.py and make it always return false.