1002:9442 Monitor not detected via DisplayPort [Radeon HD 4850]

[DAP]

I have a PowerColor AX4850 512MD3-DHO video card, a BenQ XL2420TX monitor, and a Dell 3008WFP monitor.
I tried to connect the BenQ monitor with the DisplayPort connection.
This video driver did not recognize that there was anything plugged in.
Even if the BenQ was the only monitor connected, the OS driver found nothing.

WORKAROUND: The ATI binary BLOB did properly recognize this monitor plugged in to the DisplayPort, but that driver is unusable for other reasons.

I currently have this monitor connected via HDMI, but this connection precludes the use of 120 hz refresh and 3D video.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-radeon 1:6.14.99~git20111219.aacbd629-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,snap,expo,move,resize,scale,regex]
CompositorRunning: None
Date: Fri Aug 10 21:37:57 2012
DistUpgraded: 2012-04-28 14:29:07,399 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Device [1787:2266]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=c2921384-38b9-419e-b7ef-007bcc801561 ro nosplash debug --verbose
SourcePackage: xserver-xorg-video-ati
UpgradeStatus: Upgraded to precise on 2012-04-28 (104 days ago)
dmi.bios.date: 09/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2209
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2209:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2
---
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CasperVersion: 1.336
DistroRelease: Ubuntu 13.10
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130817)
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-2-generic N/A
 linux-backports-modules-3.11.0-2-generic N/A
 linux-firmware 1.113
RfKill:

Tags: saucy
Uname: Linux 3.11.0-2-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2209
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2209:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[madbiologist (me-again)]

Looks like a kernel bug.

Does this still occur on Ubuntu 12.10 "Quantal Quetzal" alpha 3?

[DAP (akadap)]

It will likely be a month before I can get the time to download and install an alpha version of the OS.
How does one go about getting a copy of that anyway?

[madbiologist (me-again)]

Development releases of Ubuntu are available at http://www.ubuntu.com/testing
Ubuntu 12.10 beta 1 will also be available at that location on 6th September 2012 - see https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc1-quantal/

[DAP (akadap)]

I downloaded a copy of 12.10 Alpha 3, made a boot disk and ran the live CD.
With just the DisplayPort connection, the monitor displayed the bios, then the low res screen with the keyboard icon at the bottom, then the screen went blank and the monitor turned off. I eventually heard the bongo drum sound where one chooses between the install and run the live CD, but the srceen never turned back on.

I tried again with my Dual Link DVI and HDMI connections, this worked, and I was able to set up the display properly.
I tried switching the HDMI monitor to DisplayPort, but the "Detect Monitors" button still refused to detect it.

[DAP (akadap)]

I installed the v3.6-rc1-quantal kernal & extras.
DisplayPort connected monitors behave the same as before.

[madbiologist (me-again)]

I don't see anything obvious in your dmesg. Are you able to ssh into the non-working configuration (while running 12.10) and get a dmesg from that?

[DAP (akadap)]

The dmesg was generated on a working configuration.
I haven't attempted to ssh into the DisplayPort only configureation, but I am sure the system is running, and SSH would work, because the proper sound effects happen, the screen is just blank.

[DAP (akadap)]

Just upgraded to 12.10. There has been no change to the behavior, still broken.

[DAP (akadap)]

Upgraded to 13.05. There has been no change to the behavior, stil broken.

[penalvch (penalvch)]

DAP, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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-rc4

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.

[DAP (akadap)]

On 08/11/2013 08:16 PM, Christopher M. Penalver wrote:
> DAP, could you please confirm this issue exists with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
> 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-rc4
>
> 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: latest-bios-2209 needs-upstream-testing regression-
> potential
>
> ** Tags added: quantal raring
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Summary changed:
>
> - Driver won't detect monitor on DisplayPort [Radeon HD 4850]
> + 1002:9442 Monitor not detected via DisplayPort [Radeon HD 4850]
>
This will have to wait until next weekend when I have time to figure out how to do all of those things.

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

apport information

[DAP (akadap)]

I ran the apport-collect command twice, I thought it had failed both times.
I got the error "dpkg-query: no packages found matching linux"

Behavior is exactly the same.
With only a Display Port monitor connected, I end up with the monitor shutting itself off after the screen with the blurry keyboard symbol at the bottom.
With both a dual link DVI monitor and a display port monitor connected, The system boots up and is usable, but the display port monitor still ends up being shut off.

[DAP (akadap)]

I installed a mainline kernel:

linux-image-3.11.0-031100rc5-generic_3.11.0-031100rc5.201308112135_amd64.deb

$ cat /proc/version
Linux version 3.11.0-031100rc5-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201308112135 SMP Mon Aug 12 01:35:49 UTC 2013

I get the same results. Display port monitor still shuts itself off.

[penalvch (penalvch)]

DAP, did this problem not occur in a release prior to Precise?

[DAP (akadap)]

Several years ago, before AMD abandoned the Radion driver for this card, I used displayport on a single monitor. I switched to dual link DVM when I added a KVM (was unable to find a KVM that supported displayport at the time, and I needed it to support HDMI). So I don't think I have ever seen the open source driver work with Display port, but for a time the closed sorce driver did.

[penalvch (penalvch)]

DAP, a cursory search revealed DisplayPort support landed in 2.6.33. Hence, for regression testing purposes, could you please test Maverick via http://old-releases.ubuntu.com/releases/maverick/ ?

[madbiologist (me-again)]

Can you please boot with both monitors connected, as described in comment #44, then run this command:

xrandr --prop

and attach the output to this bug report.

[DAP (akadap)]

I ran the Maverick bootable CD. Same results. Display port does not work.

[DAP (akadap)]

$ xrandr --prop
Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 8192 x 8192
HDMI-0 disconnected (normal left inverted right x axis y axis)
 underscan vborder: 0 (0x00000000) range: (0,128)
 underscan hborder: 0 (0x00000000) range: (0,128)
 underscan: off
  supported: off on auto
 coherent: 1 (0x00000001) range: (0,1)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
 underscan vborder: 0 (0x00000000) range: (0,128)
 underscan hborder: 0 (0x00000000) range: (0,128)
 underscan: off
  supported: off on auto
 coherent: 1 (0x00000001) range: (0,1)
DVI-0 connected 2560x1600+0+0 (normal left inverted right x axis y axis) 641mm x 400mm
 EDID:
  00ffffffffffff0010ac35404c544c33
  1c12010380412978ea8f95ad4f32b225
  0f5054a54b008180a940d100d140714f
  8100b3000101b06800a0a0402e603020
  360081902100001e000000ff00473530
  3148383741334c544c0a283c80a070b0
  23403020360081912100001c000000fd
  0031561d711c000a20202020202000dd
 load detection: 1 (0x00000001) range: (0,1)
 underscan vborder: 0 (0x00000000) range: (0,128)
 underscan hborder: 0 (0x00000000) range: (0,128)
 underscan: off
  supported: off on auto
 coherent: 1 (0x00000001) range: (0,1)
   2560x1600 59.9*+
   1920x1440 60.0
   1920x1200 60.0
   1600x1200 60.0
   1680x1050 59.9
   1280x1024 75.0 60.0
   1280x800 59.9
   1152x864 75.0
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
DIN disconnected (normal left inverted right x axis y axis)
 tv standard: pal
  supported: ntsc pal pal-m pal-60
             ntsc-j scart-pal pal-cn secam
 load detection: 1 (0x00000001) range: (0,1)

Hmm, it thinks it is disconnected. I wonder how the display showed the boot sequence & grub screens if it is disconnected.

[penalvch (penalvch)]

DAP, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

[DAP (akadap)]

The instructions want me to send my report to the correct mantainer. I have no faith I can pick the correct mantaner from that 9000 line file. My best guess is the mantaner for "RADEON FRAMEBUFFER DISPLAY DRIVER", Is this correct? If not please let me know the correct project I should be sending this to.

[DAP (akadap)]

It seems this bug has already been reported: https://bugzilla.kernel.org/show_bug.cgi?id=60231
I assume this means I should not report it again.

[DAP (akadap)]

It has been reported more than once: https://bugzilla.kernel.org/show_bug.cgi?id=60639

[penalvch (penalvch)]

DAP, that bugzilla is mostly ignored by maintainers and developers. You would want to follow the instructions previously provided and send an e-mail to the appropriate maintainer mailing list.

[madbiologist (me-again)]

No, not the "RADEON FRAMEBUFFER DISPLAY DRIVER". That maintainer list seems to be incomplete. The closest one would be "DRM DRIVERS (David Airlie)" however he pretty much just takes what the AMD developers send him. For DisplayPort issues your best bet is to email Alex Deucher and attach copies of the output of "lspci -vvnn" and "xrandr --prop". It's also probably pointing him to https://bugzilla.kernel.org/show_bug.cgi?id=60231 with it's dmesg that has been expanded by use of the debug parameter. To avoid spam in launchpad I'll say that you can find his email address at https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8a53fa23fd3e7c22d93f28e6aaae8358c53326ba

I'm going to look through the dmesg at https://bugzilla.kernel.org/show_bug.cgi?id=60231 now.

[DAP (akadap)]

e-mail has been sent to Alex Deucher.

[penalvch (penalvch)]

DAP, you should also e-mail the maintainer mailing list (linux-x11) in case Alex doesn't notice/respond.

[DAP (akadap)]

This is the response I got from alex:
I'd suggest cc'ing youself to the kernel bugs and trying the patches on 60639 as well as providing a copy of your dmesg log and xorg log with the patch applied.

Alex

If I am going to do this, I will need some instructions. I assume this means he wants me to recompile the kernel with patches applied.

[penalvch (penalvch)]

DAP, assuming the patches are in a git repository one may follow https://wiki.ubuntu.com/KernelTeam/GitKernelBuild .

[DAP (akadap)]

Following those instructions I was able to download the kernel source and am currently compiling it (it is taking forever).

I'm still not clear on the "kernel bugs" I'm supposed to CC myself to (I hope he is not refering to the kernel mailing list that gets 1000 messages/day), or where to get the 60639 patch, or how to apply said patch.

[DAP (akadap)]

I think he is referring to this: https://bugzilla.kernel.org/attachment.cgi?id=107040

But I still need to know how to apply this patch. Pointing me at a howto would be fine. Thanks.

[DAP (akadap)]

I found that the patch had already been applied to the kernel source I downloaded, but the patch did not fix the problem.

In the process of compiling the kernel, it created the folowing packages that I installed:
linux-firmware-image_3.11.0-rc6-custom-1_amd64.deb
linux-headers-3.11.0-rc6-custom_3.11.0-rc6-custom-1_amd64.deb
linux-image-3.11.0-rc6-custom_3.11.0-rc6-custom-1_amd64.deb
linux-libc-dev_3.11.0-rc6-custom-1_amd64.deb

The instructions I used do not contain instructions on how to revert back to the old kernel and uninstall this stuff.
If I try and remove linux-libc-dev_3.11.0... with synaptic package manager, it wants to uninstall a buch of other stuff.

So how do I revert back to the old kernel?

[Joseph Salisbury (jsalisbury)]

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[penalvch (penalvch)]

DAP, 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 just make a comment to this.

If reproducible, could you also please test the latest upstream kernel available via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/ and advise to the results?

[DAP (akadap)]

Sorry, I gave up on this card ever working properly on linux and bought an NVIDEA card to replace it. I no longer have a setup to test the card in.

[penalvch (penalvch)]

DAP, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035556/comments/67 regarding you no longer have the original hardware setup. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.