kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

artik, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Tags added: lucid needs-kernel-logs needs-upstream-testing

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

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

Title:
  Imac Radeon HD 4850 switch "Mini Display Port" output during install
  resulting black screen

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I tried to install Lucid on the new Apple Imac27" with ATI radeon HD
  4850 video card. After selected "install", the screen goes black. few
  investigations later, I discovered display output switch to the Mini
  Display Port. So, I tried to connect a second screen, and I was right
  : just after select "install lucid", the video output switch to the
  second screen, and the main screen turn black.

  I continue my installation using my 2nd screen (connected to the mini
  display port), and after it, I'm on the desktop. I activate Open
  radeon drivers, they works perfectly, but in the second screen (Vsync
  is perfect, and very smooth using compiz). Impossible to switch to the
  main screen. It's not recognized, and stay black.

  I tried proprietary ati drivers (10.6). With them, I can activate my
  main screen, but they are not better than the open ones : there is a
  big vsync bug. Actually, It's totally impossible for a normal user to
  use open ati drivers on the main screen with an Imac27 and ati radeon
  4850 graphic card.

  I think issue is in the kms driver, I tried to deactivate them. Main
  screen is recognized, but impossible to turn it on, it stay black, and
  Vsync issue re-appear on the second screen. Maybe the open radeon
  drivers also got a bug, cause after deactivate them, my main screen is
  now recognized on display manager, but impossible after activate it,
  it stay black => back to proprietary drivers, and the Vsync issue)

  i tried 2.6.32, 2.6.34, 2.6.35 rc1 released, bug is still here.

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