desktop-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Jockey/fglrx are not supposed to hardcode the driver in xorg.conf any
more, as X.org auto-detects this these days, and prefers fglrx over ati
if available.

How can the jockey handler detect that case of a "MUX-less" system where
it should not offer the fglrx driver?

** Project changed: jockey => jockey (Ubuntu)

** Changed in: jockey (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/850220

Title:
  Running on an Intel/AMD hybrid system, fglrx installs, but is not
  properly enabled

Status in “jockey” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Natty system
  Jockey version 0.9.2-0ubuntu5

  Using Jockey on an Intel CPU, Intel UMA, AMD discrete (MUX-less)
  graphics system, Jockey offers the fglrx driver, will install it, but
  does not properly enable it.  The xorg.conf created is attached -
  which doesn't mention fglrx.  Systems with the same AMD device in a
  simple discrete config there is no issue.  I expect Jockey is getting
  confused by the presence of the Intel graphics device.

  Note it is a good thing it fails!  This is a MUX-less system, for
  which the AMD graphics device won't work.  If it succeeded, the
  graphics would fail on reboot.  So there appropriate way forward may
  /not/ be to 'fix' the xorg.conf generation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/850220/+subscriptions