[Bug 341526] Re: [Feature Request] Add support for Dell Driver Injection Disk

Bug Watch Updater 341526 at bugs.launchpad.net
Fri Oct 27 17:28:40 UTC 2017


Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=489314.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2009-03-09T13:13:02+00:00 Matt wrote:

+++ This bug was initially created as a clone of Bug #316481 +++

Description of problem and the rationale.

Anaconda needs to automatically (without passing command line options at boot)
look for kernel modules and load them. The drivers will be packaged in the new
redhat driver disk format.
Dell suggests that this could be done in the loader, just after loading the
driver disks in the usual method (linux dd).

Code in RHEL 5.3 anaconda which searches for drivers on discovered media
having a file system label OEMDRV needs to be forward-ported to Fedora
rawhide.

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/0

------------------------------------------------------------------------
On 2009-03-09T19:03:22+00:00 Jeremy wrote:

The problem is that this ends up making it so that the user gets put
into a situation where they're using unsupported (by the OS vendor)
drivers when installing the OS.  OS installation is tricky enough --
letting random vendors throw their own random bits and pieces to happen
at various times just makes that worse, not better.  Which is why it's
far better that the user at least *opt into* it and know that they're
going down the path as opposed to just having it happen behind their
backs.

I was against this initially and am still against it (and with more
reasons the longer I think about it :-)

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/1

------------------------------------------------------------------------
On 2009-03-09T19:48:53+00:00 Matt wrote:

Mechanism vs policy my friend.  I'm not opposed to policy being "only
drivers produced and tagged by Red Hat will be supported by Red Hat".
And I don't think having an anaconda / kernel command line option to
enable the mechanism would be all that bad.  (I prefer these things to
"just work" without additional sysadmin knowledge of documented but
never read options, but I can see the point of having such a command
line option.)

the fundamental problem I'm trying to solve is that customers, for
better or worse, want to stick with an existing set of OS bits (e.g.
their install image used on lots of machines, or a kickstart file which
anaconda uses), while having sufficient device drivers for all hardware,
both existing and future.  Dell does a good job of getting drivers for
new hardware into the upstream kernel as quickly as possible.  But we
can't always get such drivers into the kernel 6 months to 1 year ahead
of time, which is the customer's deployment lifecycle for a given OS
release.  Hence there will always be a need for a "driver update
process" (mechanism) of some sort, with policy for how/when it's used.

Objections noted, the feature is now in RHEL 5.3.  I expect it to still
be there in RHEL 6.  I believe this means it needs to be in F11
anaconda, where it can be exposed to a wide range of policy
considerations, and appropriate mechanisms, if any, can be developed to
implement the determined policies.

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/2

------------------------------------------------------------------------
On 2009-03-11T09:22:09+00:00 Martin wrote:

The patch is ready, it is just waiting for anaconda to stabilize due to
our work on storage rewrite, which is changing the codebase a lot.

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/3

------------------------------------------------------------------------
On 2009-03-11T09:49:49+00:00 Martin wrote:

*** Bug 436951 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/4

------------------------------------------------------------------------
On 2009-03-24T13:34:44+00:00 Martin wrote:

Should be present in anaconda 11.5.0.37

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/11

------------------------------------------------------------------------
On 2009-06-01T11:26:47+00:00 Paniraj wrote:

Martin

I checked at anaconda rawhide code (anaconda-11.5.0.57-1

I dont see any code related to auto pick up drivers from usb storage. 
Can you please point me to the code?
Can you please let me know how to check if this feature is implemented.


If this is not yet in tree, then please update the patches for auto pick up drivers from usb storage. Dell needs this feature to be there in Fedora-11 so that we can validate this before it is pushed to RHEL 6.

Sandeep said it was designed to work with a boot option "ddlabel=<lable
of partition containing drivers." I dont see this also being
implemented.

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/12

------------------------------------------------------------------------
On 2009-06-01T11:57:33+00:00 Martin wrote:

Due to storage rewrite, this feature will be missing from F-11 and
(re-)included into F-12. Sorry for the inconvenience.

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/13

------------------------------------------------------------------------
On 2009-06-09T12:02:30+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/14

------------------------------------------------------------------------
On 2010-04-06T08:34:48+00:00 Martin wrote:

This feature is now present in F13. Closing this bug as a part of my
personal cleanup.

Reply at: https://bugs.launchpad.net/ubuntu/+source/hw-
detect/+bug/341526/comments/23


** Changed in: fedora
       Status: In Progress => Fix Released

** Changed in: fedora
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountmedia in Ubuntu.
https://bugs.launchpad.net/bugs/341526

Title:
  [Feature Request] Add support for Dell Driver Injection Disk

Status in hw-detect package in Ubuntu:
  Fix Released
Status in mountmedia package in Ubuntu:
  Fix Released
Status in hw-detect source package in Hardy:
  Won't Fix
Status in mountmedia source package in Hardy:
  Won't Fix
Status in hw-detect source package in Karmic:
  Fix Released
Status in mountmedia source package in Karmic:
  Fix Released
Status in Fedora:
  Fix Released
Status in Suse:
  Unknown

Bug description:
  Upcoming Dell servers will be supporting a new technology called
  "Driver Injection Disks".  These are essentially read only flash
  drives that are connected internally on the USB bus containing drivers
  preloaded from the factory.

  They are intended to be used during OS installation for an OS release
  that doesn't yet include support for the drivers in a server natively.
  RHEL and SLES have both adopted it already into their installers.

  Here are the key points about it:
  1) It will show up as a VFAT disk with the label OEMDRV
  2) Drivers from many OSes may be contained on the VFAT disk at any given time.  This means that if a server is certified against Ubuntu 8.04, RHEL 5.3, Windows Server 2008, and Ubuntu 10.04, that drivers will be on for each of these OSes.  Because of this, it's important to account for possible collisions.  For Ubuntu releases, this is solved by shipping Ubuntu drivers in:
  $mnt/ubuntu/$(lsb_release -r -s).  Drivers for Ubuntu 8.04 will not be offered with Ubuntu 10.04 installs then.
  3) This VFAT disk will always be exposed as read only to the user during installation.  Using Dell supported tools however, it can be injected with updated drivers if the customer would like.
  4) This option should be preseedable, so in the event that Dell was to ship an Ubuntu server with Ubuntu preloaded, the drivers should be able to be installed from the Driver Injection Disk in the factory.
  5) When not preseeded, the customer should be offered the option to use the drivers on the Driver Injection Disk, with the default choice being No.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/341526/+subscriptions



More information about the foundations-bugs mailing list