Bug 13464 - Do not may turn from fglrx to radeon driver on AMD trinity graphic
Summary: Do not may turn from fglrx to radeon driver on AMD trinity graphic
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: Mageia 4
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-31 13:25 CEST by Dušan Pavlík
Modified: 2015-10-27 06:58 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Dušan Pavlík 2014-05-31 13:25:23 CEST
Description of problem: I want using FOOS driver on my desktop.
When I changing graphic driver boot is ending with black screen. Same is with drakconf or with xorg.conf

test with draconf is ending with -
"Vyskytla sa chyba:
(EE) 
Fatal server error:

Skúste zmeniÅ¥ niektoré parametre"



Same problem is with installation from DVD. Working only Vesa driver or proprietary driver. Booting (with radeon driver configuration) after instalation is ending with black screen.


my configuration:

inxi -F
System:    Host: localhost.localdomain Kernel: 3.12.20-desktop-1.mga4 x86_64 (64 bit) 
           Desktop: KDE 4.11.4 Distro: Mageia 4 thornicroft
Machine:   Mobo: ASUSTeK model: F2A85-V PRO version: Rev X.0x Bios: American Megatrends version: 5206 date: 01/18/2013
CPU:       Quad core AMD A10-5800K APU with Radeon HD Graphics (-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) 
           Clock Speeds: 1: 1900.00 MHz 2: 1900.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7660D] 
           X.Org: 1.14.5 drivers: fglrx,v4l Resolution: 1600x1200@59.8hz 
           GLX Renderer: AMD Radeon HD 7660D GLX Version: 4.3.12618 - CPC 13.251
Audio:     Card-1: Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel 
           Card-2: Advanced Micro Devices [AMD/ATI] Trinity HDMI Audio Controller driver: snd_hda_intel 
           Sound: Advanced Linux Sound Architecture ver: k3.12.20-desktop-1.mga4
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 
           IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: 50:46:5d:8d:e5:1c
Drives:    HDD Total Size: 3032.6GB (89.9% used) 1: id: /dev/sda model: SSDSA2SH032G1GN size: 32.0GB 
           2: id: /dev/sdb model: WDC_WD30EZRX size: 3000.6GB 
Partition: ID: / size: 30G used: 21G (74%) fs: ext4 ID: /home size: 93G used: 72G (83%) fs: ext4 
           ID: swap-1 size: 11.98GB used: 0.00GB (0%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 29.0C mobo: 26.0C gpu: 4294962.00C 
           Fan Speeds (in rpm): cpu: N/A fan-1: 895 fan-2: 524 fan-3: 0 fan-4: 0 fan-5: 691 
Info:      Processes: 211 Uptime: 20:23 Memory: 2732.3/7363.7MB Client: Shell (bash) inxi: 1.9.17




Version-Release number of selected component (if applicable):
x11-server-xorg        1.14.5-2.mga4
x11-driver-video-ati    7.2.0-9.mga4
kernel-desktop-       3.12.20-1.mga4

How reproducible:
Every time when I want change graphic driver.

Steps to Reproduce:
1.Start drakconf
2.Start Turn graphic server 
3.Change graphic cart to radeon
4.Test graphic 

or change

driver from fglrx to radeon in /etc/X11/xorg.conf


Reproducible: 

Steps to Reproduce:
Dušan Pavlík 2014-05-31 13:26:39 CEST

Target Milestone: --- => Mageia 4

Comment 1 Christian Lohmaier 2015-01-07 18:12:27 CET
radeon driver might need glamoregl module for proper acceleration - unfortunatley, there's bug in mageia4 that prevents loading this extension. (see bug#13209 for details) - failing to load that module results in the symtoms of having graphical output during booting, but when it comes to starting displaymanager you get black screen.

Although the error message in /var/log/Xorg.0.log or in gdm (or whatever display manager is used) should then state appropriate message).

Using a different AccelMethod in the Driver section should allow you to boot.

Please provide error messages in english if possible (LC_MESSAGES=C name-of-program should work most of the time for that)

CC: (none) => lohmaier+mageia

Comment 2 Samuel Verschelde 2015-09-21 13:22:00 CEST
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/
Comment 3 Marja Van Waes 2015-10-27 06:58:52 CET
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


Note You need to log in before you can comment on or make changes to this bug.