Bug 1361525
| Summary: | The latest version of xorg-x11-drv-ati display driver is unable to drive "AMD FirePro W2100" and "AMD Radeon HD 3450" cards. | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | amit yadav <ayadav> | ||||||||||
| Component: | xorg-x11-drv-ati | Assignee: | Lyude <lyude> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 6.8 | CC: | airlied, ayadav, bgollahe, cww, jglisse, jkurik, lyude, rmarigny, tpelka | ||||||||||
| Target Milestone: | rc | Keywords: | OtherQA, Regression | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | xorg-x11-drv-ati-7.6.1-4.el6 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2018-06-19 05:19:38 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1374441, 1461138, 1506652 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
amit yadav
2016-07-29 10:03:21 UTC
radeon 0000:01:00.0: firmware: requesting radeon/oland_pfp.bin radeon 0000:01:00.0: firmware: requesting radeon/OLAND_pfp.bin si_cp: Failed to load firmware "radeon/OLAND_pfp.bin" [drm:si_init] *ERROR* Failed to load firmware! radeon 0000:01:00.0: Fatal error during GPU init [drm] radeon: finishing device. From the dmesg in the case report. Created attachment 1386598 [details]
Xorg.0.log
Created attachment 1386599 [details]
dmesg
Created attachment 1386703 [details]
xorg-x11-drv-ati-firmware test build
Created attachment 1387821 [details]
Xorg Log
Created attachment 1387822 [details]
Dmesg log
ok hold on something's not right on the customer's end. It took me a little bit to notice this, but your customer said this was regarding: (In reply to amit yadav from comment #0) > Description of problem: > HP Z230 with AMD FirePro W2100 graphics card, and some Dell system AMD > Radeon HD 3450 is not able to drive dual head configuration. Previously > these systems were running RHEL6.7 and dual head configuration was working > fine with xorg-x11-drv-ati driver available in RHEL6.7. As soon as the > system was updated to RHEL6.8, Xorg stopped loading ATI display driver. It > is falling back to generic display driver. Even if they fresh install > RHEL6.8 on those systems, it is using vesa driver only. > … > > Card-1 > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV370 [Radeon X300/X550/X1050 Series] > 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 > [Radeon X300/X550/X1050 Series] (Secondary) > > Card-2 > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV530 GL [FireGL V3400] > > Card-3 > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV370 [Radeon X300] Codenames RV370, RV530. The codename I see in comment 7 is oland, which is would be a R7 240. Then the dmesg you give on comment 1387822 says turks, which is another different card (it would be one of HD6450, HD6570, HD6670, HD6790 - HD6990, HD64xxM, HD67xxM, HD69xxM, HD7450 - HD7670). I'd recommend taking a look at https://www.x.org/wiki/RadeonFeature/ by the way, which has translations for all of these codenames. Except for the oland card, this doesn't sound like it's actually our bug. As a final note btw, Dave mentioned to me: 18:51 <airlied> Lyude: they need to rebuild the initrd after install the updated driver 18:51 <airlied> which I assume they haven't done so make sure your customer does that with the new builds as well, thanks! (In reply to Lyude from comment #29) > ok hold on something's not right on the customer's end. It took me a little > bit to notice this, but your customer said this was regarding: > > (In reply to amit yadav from comment #0) > > Description of problem: > > HP Z230 with AMD FirePro W2100 graphics card, and some Dell system AMD > > Radeon HD 3450 is not able to drive dual head configuration. Previously > > these systems were running RHEL6.7 and dual head configuration was working > > fine with xorg-x11-drv-ati driver available in RHEL6.7. As soon as the > > system was updated to RHEL6.8, Xorg stopped loading ATI display driver. It > > is falling back to generic display driver. Even if they fresh install > > RHEL6.8 on those systems, it is using vesa driver only. > > … > > > > Card-1 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV370 [Radeon X300/X550/X1050 Series] > > 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 > > [Radeon X300/X550/X1050 Series] (Secondary) > > > > Card-2 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV530 GL [FireGL V3400] > > > > Card-3 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV370 [Radeon X300] > > Codenames RV370, RV530. The codename I see in comment 7 is oland, which is > would be a R7 240. Then the dmesg you give on comment 1387822 says turks, > which is another different card (it would be one of HD6450, HD6570, HD6670, > HD6790 - HD6990, HD64xxM, HD67xxM, HD69xxM, HD7450 - HD7670). > > I'd recommend taking a look at https://www.x.org/wiki/RadeonFeature/ by the > way, which has translations for all of these codenames. > > Except for the oland card, this doesn't sound like it's actually our bug. > > As a final note btw, Dave mentioned to me: > > 18:51 <airlied> Lyude: they need to rebuild the initrd after install the > updated driver > 18:51 <airlied> which I assume they haven't done > > so make sure your customer does that with the new builds as well, thanks! Lyude, > Card-1 > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV370 [Radeon X300/X550/X1050 Series] > 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 > [Radeon X300/X550/X1050 Series] (Secondary) > > Card-2 > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV530 GL [FireGL V3400] > > Card-3 > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > RV370 [Radeon X300] Customer is not using above cards. These are available in our Pune office and I tried to replicate the issue using these cards. But I was not able to reproduce the issue with these cards. Customer is using following cards: AMD FirePro V3900 AMD FirePro W2100 AMD Radeon HD 3450 I will ask him to rebuild initrd and check status. (In reply to amit yadav from comment #30) > (In reply to Lyude from comment #29) > > ok hold on something's not right on the customer's end. It took me a little > > bit to notice this, but your customer said this was regarding: > > > > (In reply to amit yadav from comment #0) > > > Description of problem: > > > HP Z230 with AMD FirePro W2100 graphics card, and some Dell system AMD > > > Radeon HD 3450 is not able to drive dual head configuration. Previously > > > these systems were running RHEL6.7 and dual head configuration was working > > > fine with xorg-x11-drv-ati driver available in RHEL6.7. As soon as the > > > system was updated to RHEL6.8, Xorg stopped loading ATI display driver. It > > > is falling back to generic display driver. Even if they fresh install > > > RHEL6.8 on those systems, it is using vesa driver only. > > > … > > > > > > Card-1 > > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > > RV370 [Radeon X300/X550/X1050 Series] > > > 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 > > > [Radeon X300/X550/X1050 Series] (Secondary) > > > > > > Card-2 > > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > > RV530 GL [FireGL V3400] > > > > > > Card-3 > > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > > RV370 [Radeon X300] > > > > Codenames RV370, RV530. The codename I see in comment 7 is oland, which is > > would be a R7 240. Then the dmesg you give on comment 1387822 says turks, > > which is another different card (it would be one of HD6450, HD6570, HD6670, > > HD6790 - HD6990, HD64xxM, HD67xxM, HD69xxM, HD7450 - HD7670). > > > > I'd recommend taking a look at https://www.x.org/wiki/RadeonFeature/ by the > > way, which has translations for all of these codenames. > > > > Except for the oland card, this doesn't sound like it's actually our bug. > > > > As a final note btw, Dave mentioned to me: > > > > 18:51 <airlied> Lyude: they need to rebuild the initrd after install the > > updated driver > > 18:51 <airlied> which I assume they haven't done > > > > so make sure your customer does that with the new builds as well, thanks! > > Lyude, > > > > Card-1 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV370 [Radeon X300/X550/X1050 Series] > > 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 > > [Radeon X300/X550/X1050 Series] (Secondary) > > > > Card-2 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV530 GL [FireGL V3400] > > > > Card-3 > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > > RV370 [Radeon X300] > > Customer is not using above cards. These are available in our Pune office > and > I tried to replicate the issue using these cards. But I was not able to > reproduce > the issue with these cards. > > > Customer is using following cards: > > AMD FirePro V3900 > AMD FirePro W2100 > AMD Radeon HD 3450 > > I will ask him to rebuild initrd and check status. That worked! Customer is now able to get display on both monitors. Builds available at https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15220281 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1899 |