Summary

Integrate Jockey into Ubiquity so that users have an obvious way of obtaining missing drivers as part of the Ubuntu installation process.

Release Note

The desktop CD installer now integrates the functionality of the Hardware Drivers tool (jockey) to provide users with a quick means of installing additionally needed drivers.

Rationale

Users are trying to set up a netbook but only have wireless connectivity. If they don't install bcmwl prior to running Ubiquity, they aren't able to after install due to the apt-cache not including the CD or USB key they installed from and Jockey thus not offering the tool.

User stories

Assumptions

BulletProofX should be expected to work as a fallback in cases where a different graphics driver (nvidia, for example) is installed by jockey and does not function.

Design

A new page will be added to the installer workflow for additional driver selection. This page will only be presented if there are possible additional drivers to install, much like migration-assistant is only visible if there are users on other operating systems to import data from.

This page will be constructed using the existing jockey UI code by instantiating jockey.ui. The UI to remove drivers will be removed as it's not relevant here.

Implementation

Jockey upstream

Preseeding

As OEMs will likely use this functionality, a means to automate this step via preseeding is necessary. This will be handled with a multiselect debconf question that uses the jockey keys (kmod:b43) as possible values. This question should accept the value "recommended", which will use recommended drivers automatically. The "recommended" option can be used in combination with any number of additional options to install all of the recommended drivers, plus the additional drivers specified (if available).

Preseeding needs to be respected above filtering. That is, if a driver is preseeded, but not shown in ubiquity, it should still be installed if available.

Translation

As ubiquity is translated into more languages than are currently installed on the live CD, if we use any of jockey's translations, we'll need to import them into the debconf templates for ubiquity. This is already done for common GTK labels, and should serve as a suitable starting point.

Test/Demo Plan

Automated testing will be accomplished using the existing daily installer testing (http://people.canonical.com/~scott/daily-installer/), or a modification thereof.

A test case will be added to the CD tracker for hardware driver installation in ubiquity.

BoF agenda and discussion

Problem

Users are trying to set up a netbook but only have wireless connectivity. If they don't install bcmwl prior to running Ubiquity, they aren't able to after install due to the apt-cache not including the CD or USB key they installed from and Jockey thus not offering the tool.


CategorySpec

FoundationsTeam/Specs/LucidJockeyUbiquityIntegration (last edited 2009-12-01 15:20:55 by ev)