Opened 23 months ago

Closed 23 months ago

Last modified 23 months ago

#13693 closed bug (fixed)

radeon_hd: Enable for FirePro W4100

Reported by: moochris Owned by: kallisti5
Priority: normal Milestone: R1/beta1
Component: Drivers/Graphics/radeon_hd Version: R1/Development
Keywords: FirePro Cc: kallisti5
Blocked By: Blocking:
Has a Patch: yes Platform: x86-64

Description

I just got a FirePro W4100 to drive my 4K monitor, but VESA was used instead of radeon_hd.

I added the line with the missing PCI ID in radeon_hd/driver.cpp:293: {0x682c, 6, 0, RADEON_CAPEVERDE, CHIP_STD, "FirePro W4100"},

Build and ran - it does now load the driver for my card, but compared to the VESA driver, I get refresh problems - i.e. mouse jumping when moving and lots of tearing on moving windows. The refresh rate is 60Hz and this is over displayport, resolution 3840 x 2160.

I can investigate myself if I can get some pointers of bits of the driver to look at that might need tweaking for FirePro? (@kallisti5 - any ideas?)

Attachments (2)

syslog (512.0 KB) - added by moochris 23 months ago.
fireprow4100.patch (796 bytes) - added by moochris 23 months ago.

Download all attachments as: .zip

Change History (9)

Changed 23 months ago by moochris

Attachment: syslog added

Changed 23 months ago by moochris

Attachment: fireprow4100.patch added

comment:1 Changed 23 months ago by moochris

Has a Patch: set

comment:2 Changed 23 months ago by phoudoin

I guess our software-based screen painter is not able to keep pace with 4K needs. If you reduce resolution, does the same issues still show up? Not a solution, just to assert of not if it's resolution-bound issue or not.

Last edited 23 months ago by phoudoin (previous) (diff)

comment:3 in reply to:  2 Changed 23 months ago by moochris

Replying to phoudoin:

I guess our software-based screen painter is not able to keep pace with 4K needs. If you reduce resolution, does the same issues still show up? Not a solution, just to assert of not if it's resolution-bound issue or not.

I will try it and see (not near my machine at the moment), however a while ago I tried an RX 470 at the same resolution and it was perfectly smooth. It's also fine with VESA, so I think it's some issue with radeon_hd specifically with this card.

comment:4 Changed 23 months ago by moochris

Yes, so a lower resolution fixes the issue. I wonder why the VESA screen painter is fine at 3840x2160, but the radeon_hd driver is not?

I can just blacklist the radeon_hd driver for now, but I'm stuck at 16 bit depth with VESA, so it would be good to get radeon_hd working at that resolution.

Last edited 23 months ago by moochris (previous) (diff)

comment:5 Changed 23 months ago by kallisti5

Resolution: fixed
Status: newclosed

Looks like you're using DisplayPort.

While our radeon_hd driver supports DisplayPort, it is still extremely buggy. jessicah wants to work on multi-head support, and is doing it via a FirePro with a bunch of display port monitors... so hopefully we can figure out the major bugs :-)

Adding this PCI-ID soon in 807f4d4d. No hrev yet but likely ~hrev51403.

comment:6 in reply to:  5 Changed 23 months ago by moochris

Replying to kallisti5:

Looks like you're using DisplayPort.

Indeed.

While our radeon_hd driver supports DisplayPort, it is still extremely buggy. jessicah wants to work on multi-head support, and is doing it via a FirePro with a bunch of display port monitors... so hopefully we can figure out the major bugs :-)

That's great - I'll keep an eye on progress and I'm available for testing etc.

Adding this PCI-ID soon in 807f4d4d. No hrev yet but likely ~hrev51403.

Thanks - I see it's been committed for hrev51403

comment:7 Changed 23 months ago by jessicah

Had a small typo in that commit :P I've fixed in hrev51406.

Note: See TracTickets for help on using tickets.