Bug 13808

I'll confirm the bug on my mga4 64 bit installs for my Cedar [Radeon HD 5450 Series], AMD Radeon R7 200 Series, and Seymour [Radeon HD 6400M  Series]  PCI cards and using the fglrx driver.

CC: (none) => junknospam

still valid with recent updates ?

CC: sysadmin-bugs => anssi.hannula, thierry.vignaud, tmb
Component: Release (media or process) => RPM Packages

20141101
> Comment #2 from Manuel Hiebel <manuel.mageia@hiebel.eu> ---
> still valid with recent updates ?
>

    Sadly yes.  Just tried it from MMC and hitting the Test button produced
a black screen.
    Is it possible that for some reason this is shutting off the back lighting?

    This is on an HP notebook with AMD 4 cores(A10-5745M APU)
and the video card information is below:
  Identification
Vendor: âAdvanced Micro Devices, Inc. [AMD/ATI]
Description: âRichland [Radeon HD 8610G]
Media class: âVGA compatible controller
Connection
Bus: âPCI Express
PCI domain: â0
Bus PCI #: â0
PCI device #: â1
PCI function #: â0
Vendor ID: â0x1002
Device ID: â0x990f
Sub vendor ID: â0x103c
Sub device ID: â0x216b
Misc: Module: âCard:ATI Radeon HD 6400 and later (radeon/fglrx)

    Thanks for your effort.
    Bobbie Sellers

(In reply to Manuel Hiebel from comment #2)
> still valid with recent updates ?

Yup. just now finished a clean install with updates using vesa video driver.
My install scripts use urpmi to install fglrx/ati packages.
set fglrx video and reboot, log in, startx, no video.
reset vesa video driver, reboot, delete fglrx/ati packages, select video setup for fglrx, install packages, reboot video now works.

Test still gives black screen. This is a desktop pc.
$ lspci | grep -i radeon
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

(In reply to Bit Twister from comment #4)

> $ lspci | grep -i radeon
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Cedar [Radeon HD 5000/6000/7350/8350 Series]

Oops, was on wrong machine.
lspci | grep -i radeon
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240]

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD

I just tested this on my hardware running Mageia 5 and it is worse than ever requiring (alt)+(ctrl)+(backspace) to escape the useless blank and pied screen.


Before it required only a wait for the screen to clear back to the 
MMC/Hardware/Graphic setup screen.

I originally thought that the problem was that the backlight for
the LCD was being turned off but the new problem looks much 
worse with lines of distorted character compressed nearly
flat showing up on the screen.

The test done today ended up with log-out and log-in to get
back to the workspaces.

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Hi Bobbie and Bit Twister,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

No reply, so closing as OLD since Mageia 5 is no longer maintained.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Resolution: (none) => OLD
Status: REOPENED => RESOLVED