Bug 19058

Ubuntu 16.04 LIVE works on all machines mentioned above..

bug related to GNOME-edition of Mageia STA1 (others not tested)

Working distros:
Ubuntu 16.04
Manjaro 16.06

not working distros:
Fedora 24 (but low graphics o.K.)
Korora

What's the PCI ids of your card?
You can just redo the mga installation.
Once reaching the summary stage, just:
- attach an USB key to the machine
- go to tty2 (alt+ctrl+F2)
- type the "run" command
- attach (not paste) the report.bug file you'll found on the USB key to this bug report

Another question, what driver is sued by FC24 low graphics mode?
I'm pretty sure it's "vesa"

Once we've all the data, we can add a special entry for that broken card so that it defaults to a working non accelerated driver.

CC: (none) => thierry.vignaud
Source RPM: (none) => ldetect-lst, x11-driver-video-ati

(In reply to Thierry Vignaud from comment #3)
 
Two machines with graphics card:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ATI AMD Radeon R7 200 Series
	Manufacturer	ATI
	Model	AMD Radeon R7 200 Series
	Device ID	1002-6610
	Subvendor	ATI AIB (1787)
	Current Performance Level	Level 0
	Voltage	0.800 V
	GPU Clock	1100,0 MHz
	Temperature	30 °C
	Core Voltage	0.800 V
	Driver version	16.200.1035.1001
	BIOS Version	113-C5760100_100
	Memory Type	HyperMemory
	Memory	1024 MB
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
AMD A8 6500T Quad Core Processor (APU onboard graphics)
On  this machine Mageia 6 would/should be installed...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Booting "Mageia-6-sta1-LiveDVD-GNOME-x86_64-DVD.iso"
on the uefi-machine crashes the machine after the third line
displayed after starting on of the two menueentries
(hard reset).
---------------------------------------------------------
The "Mageia-6-sta1-x86_64-DVD.iso" is o.K.,
I can install Mageia gnome, the random crashes
on booting are related to "GRUB-Customizer", resulting
"start of the ubuntu kernel instead of the mageia
(ubuntu and mageia on the same machine)".
 (solution: -> chainloading works).

So, no report.bug file possible...

> Another question, what driver is sued by FC24 low graphics mode?

(Fedora-Workstation-Live-x86_64-24-1.2.iso)
The resolution is 640x480 only(unknown display),
the driver used on
"AMD A8-6500T APU with Radeon HD Graphics x4" is:
"Gallium 0.4 on llvmpipe (LLVM3.8, 128bits)
--------------------------------------------------------------
Manjaro 16.04 uses the free radeon-driver by default
(Gallium 0.4 ARUBA (DRM 2.43.0, LLVM 3.8.0))
and works perfectly; but the menueentry "proprietary Driver"
crashes my machine (stopps booting, str-alt-entf doesnot work).
(Manjaro Live Mode works with full resolution, FD24 crashes).
--------------------------------------------------------------
btw: installation from usb-key

If you read my previous comment, I give you the instructions to do while installing, so no need to reboot and thus it's not the problem if the installed OS doesn't reboot...

Keywords: (none) => NEEDINFO

Problem:
not time for this at time....
Next:
> Once reaching the "summary stage", just:
whats that in german please, for favore?
I dont understanst "summary stage"
What does the command "run" do?
(i only know run "script")

I use an usb-key for installing, do i need
a second usb-key for the report.bug file?

(In reply to Hartmut Schulze from comment #6)
> > Once reaching the "summary stage", just:
> whats that in german please, for favore?
> I dont understanst "summary stage"

It means, once the installer has finished installed the packages, you're presented with a summary screen ("Zusammenfassung" according tohttp://gitweb.mageia.org/software/drakx/tree/perl-install/install/share/po/de.po#n1133) which let review the bootloader, network, firewall, ... configuration.

> What does the command "run" do?

Just type "bug" then <enter> and the "bug" command will be run

> (i only know run "script")
> 
> I use an usb-key for installing, do i need
> a second usb-key for the report.bug file?

Honestly, I'm not sure.
It will tell you if needed, I think.

Created attachment 8297 [details]
Bug REport

Well, now i have redone the mageia 6 installation
using the "Mageia-6-sta1-x86_64-DVD.iso"
from an usb-key.
Installation was o.K.
The installation crashes while booting...

Then I installed Manjaro 16.06
and the installer complained, that on the
/boot/efi/ partition there is no "esp-flag".
Manjaro installed well, boots o.K.
Magei 6 from the bootmenu crashes.

I attach (not paste) the report.bug file  ;-)

First, the thing is you're testing an old ISO (DrakX v17.46 whereas we're now at 17.53).
There's been quite a lot of fixes since 17.46

You should test a net install instead:
eg: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/images/Mageia-Cauldron-netinstall-nonfree-x86_64.iso

Then, what you though is an ESP really isn't as it's really not tagged as such in the GPT, as shown by fdisk:

* fdisk before:
/dev/sda1       2048    821247    819200  400M Microsoft basic data

Same after partitioning.
An ESP must use a special GUID, see https://en.wikipedia.org/wiki/EFI_system_partition & https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs

You cannot just create a FAT partition and mount it over there.
If you do it manually, you must select "EFI" in the type pull down menu, not FAT.

Anyway could you retry with current cauldron?

Hi,

> You should test a net install instead:

doesnot work, because the installer opens on a 640x480 screen,
so the Installer is partly outside my monitor.....

Next?

------------
O.T.:

installing Mageia 5 and upgrading to Cauldron works,
but this is not the way it should ;-))

If you got https://wiki.mageia.org/en/File:Boot-iso2b.png, that's OK
I should have told you to read https://wiki.mageia.org/en/Mageia_Netinstall_Iso_(Boot.iso)

(In reply to Thierry Vignaud from comment #12)
> If you got https://wiki.mageia.org/en/File:Boot-iso2b.png, that's OK
> I should have told you to read
> https://wiki.mageia.org/en/Mageia_Netinstall_Iso_(Boot.iso)

Igot that all be myself,
but the screen "partitioning" is half way outside of my monitor
so i cannot reach the buttons.

And the Manjaro-Installation on the PC is working,
so I would not do automatic installation, sorry

Care to provide a screenshot?
Just press the F2 key when you're seeing that then you can attach a USB key and copy /tmp/DrakX-screenshots on the USB key after mounting it.

(In reply to Thierry Vignaud from comment #14)
> Care to provide a screenshot?
> Just press the F2 key when you're seeing that then you can attach a USB key
> and copy /tmp/DrakX-screenshots on the USB key after mounting it.

Dont like experiments - wont help will not do anything further

The Mageia 5 installer on the network-install.medium is ok,
the Mageia 6 installer on the network-install.medium is to big
for the screen, only half of the installer fits on the screen
no moving possible, the left side is on the screen,
the right side is invisible.

sorry

We won't be able to fix something that look specific to your hardware w/o help, such as a screenshot, logs, ...

ccing kernel guy in case 640x480 resolution could be a kernel regression

CC: (none) => tmb

Created attachment 8303 [details]
SCREENSHOTS

Hi,

some screenshots,
as I am real lazy, I used a camera...

The pictures Mageia 0 to 4 are
from the "Mageia-Cauldron-netinstall-nonfree-x86_64.iso".

The Manjaro_001 shows what Grub-Customizer thinks
about Mageia 6 (multiple entries, every one crashes).

BTW: the Manjaro-People are good in "booting",
the 16.06 boots fast as hell compared with mageia 5,
which boots really very very slow.

Why not get help fom the manjaro-team?

 Because: "Not Invented Here" ????????????????
    (we are on LINUX, you know?)

So Manjaro is stable like a rock, but ugly,
Mageia is better in hardware and system-config.

So integrate manjaro booting into mageia 6 is too difficult?
(btw. "Mageia-5-x86_64-DVD.iso" works perfectly)

(start satire/ warning: some parts may be offensive! /end satire)

Created attachment 8306 [details]
more screenshots...

(In reply to Hartmut Schulze from comment #19)
> Created attachment 8306 [details]
> more screenshots...

Hi monsieurs,

the attached zip-file contains some
screenshots maybe helpfull.

The Mageia 6 installation will not a time boot
by its own GRUB-menu, so I made a new in the
Manjaro-GRUB-menu (screenshot of contents).
(derivated from the manjaro-boot-menu entry).

Then mageia 6 boots o.k sometimes, sometimes crashes
(3 times crashes, 3 times o.k).
Look at name of the pictures taken.

Would it be helpfull to try
another kernel in mageia 6 ?


Regards

(In reply to Thierry Vignaud from comment #17)
> ccing kernel guy in case 640x480 resolution could be a kernel regression

Hi

in the meantime even Mageia 5 doesnot work anymore
on my "OS-Trial-PC" 

(https://de.msi.com/Motherboard/support/A88XM-E45.html  with an A8 6500T APU).

There is one SSD:

/efi/boot on sda1
Manjaro /root on sda2
Ubuntu /root on sda3 (as a placeholder for experiments)

And on a HDD
/swap         on /sdb1
Manjaro /home on /sdb2
Ubuntu  /home on /sdb3

Everything is working at time.
Ubuntu is chainloaded by Manjaro-bootloader   ;- ))

Forteen days before Mageia 5 residet on /sda3 and /sdb3.
Then I thought its time for Cauldron, and the waste of liftime begun...

I installed Mageia 6 STA1 (without updates) in Place of Ubuntu, after
formatting /sda3.
(Installation was only possible with the Mageia-6-sta1-x86_64-DVD.iso).

Today Mageia would not boot any longer after updating the distro...
O.K. then I installed Mageia 5 as it was before on the machine.
Without update: boots as usual.
Then I updated, and NO booting possible (Mageia 5 chainloaded by Manjaro!!!!)
Only the Kernel 3.19.8  >BUT in rescue-mode only<  worked!!!!!!!!!!!
Then I tried upgrading to Caulron as discribed in the wiki.
This time NO booting was possible, even with the 3.19.8 kernel in rescue mode.

Whats wrong with the Magicans?????????????????????????????

LOOK:   https://distrowatch.com/dwres.php?resource=popularity

After that i put ubuntu 16.04 in place of mageia, adjusted the chainloader,
and manjaro with ubuntu worked flawlessly!!

(40_custom (looking for other OS disabled!!!))

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry "Ubuntu Bootloader starten" {
search --fs-uuid --no-floppy --set=root 5DCB-E345
chainloader (${root})/EFI/ubuntu/grubx64.efi
}


What now (in german: wat nu?)

Hi!

Problem solved by courtesy of the last "SABAYON Live DVD"!!!!!!!!!!!!

                 -- Long live KISS --

The reason for the failure is not the AMD A8 APU 6500T
but the MSI board A88XM-E45 (with AMI BIOS).

The mentioned SABAYON Live DVD I could only start
when I access the "noacpi acpi = off" choose in the boot menu.
Then the installation ran flawlessly in full video resolution.

SABAYON even puts kernel parameters correctly what Mageia 6 does not do!

Until recently, the mentioned kernel parameters for Mageia 5
were not necessary. Software modifications?

For me, no hardware modifications, must be software problem ...

Finaly Cauldron is up and running on my PC
(chainloaded by ugly Manjaro).

Someone should test whether these kernel-paramters
would help on systems with AMD-graphics generally.

And for the Magicans: an automatic detection
to prevent a crash at booting....

Regards - for me Problem = SOLVED

(Kernel parameters added: noacpi acpi=off)

No such parameters are very motherboard specific.
They were needed more often in the old days but they're quite a lot less needed since the kernel asks for windows compatibility acpi tables.

That must be a kernel regression on your motherboard type

(In reply to Thierry Vignaud from comment #23)
> No such parameters are very motherboard specific.
> They were needed more often in the old days but they're quite a lot less
> needed since the kernel asks for windows compatibility acpi tables.
> 
> That must be a kernel regression on your motherboard type

Seems so. Even Sabayon needs this paramters,
stops booting, does not crash without.
(acpi=off alone shows only one boiling-bubble in plymouth,
additional noacpi all five bubbles)
Manjaro 16.06 is the only distro patching this flaw,
EXOR may be because of kernel 4.6.4?

Thank you in advance

Created attachment 8331 [details]
Screenshots of Grub2-Cfg Manjaro Mageia

Hi,

Attached the current GRUB2 data:

A time of 16.06 Manjaro with kernel 4.6.5-1
And Mageia Cauldron with kernel 4.7.0 / 4.6.3

As I said, Mageia crashes without "noacpi acpi = off"

Manjaro thinks not even think to crash but will boot rapidly.

Oddly, one Mageia Cauldron 
the computer will not turn off at time...

The screen output is:

[327.169526] reboot: System haltet
_


Would be nice someone explain that to a 65 years old silly pensioner...

Since most distros have switched to systemd, poweroff != halt/shutdown.
Both halts the system but only the former does an electric halt

(In reply to Thierry Vignaud from comment #26)
> Since most distros have switched to systemd, poweroff != halt/shutdown.
> Both halts the system but only the former does an electric halt

Thank you Thierry.
To make Your reply helpfull:
"How To" change poweroff from halt to shutdown instead please.
(DAU question I know /(DAU = Dumb Amiga User) (I own a CMB A2000 since 1988)

Regards

I'm not sure what's your question but:
If you use "poweroff" instead of "halt", then your machine will stop at the electrical/power level too.

(In reply to Thierry Vignaud from comment #28)
> I'm not sure what's your question but:
> If you use "poweroff" instead of "halt", then your machine will stop at the
> electrical/power level too.

Sorry, I do not know the path to the file to change halt to poweroff..

(In reply to Hartmut Schulze from comment #29)
> (In reply to Thierry Vignaud from comment #28)
> > I'm not sure what's your question but:
> > If you use "poweroff" instead of "halt", then your machine will stop at the
> > electrical/power level too.
> 
> Sorry, I do not know the path to the file to change halt to poweroff..

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
looks like a new BUG:

the command systemctl --force poweroff 
halts the (real existing) PC - if given in Mageia Cauldron,
(machine haltet)

whereas in Manjaro "> then your machine will stop at the
> electrical/power level too." poweroff works 100%

> Sorry, I do not know the path to the file to change halt to poweroff..
means: where is the damn configuration-file    ;- >>

oh no!!!!!

the reason why the machine halts instead of shutdown is really simple:

-------------- the kernel-parameters "noacpi acpi=off" ------------------

Tested with manjaro on the same machine:
adding "noacpi acpi=off" to the GRUB2
resalts in halting the machine, not poweroff.

I remembered this because in AROS (Icaros) this once upon a time
was the reason for exactly the same behavior....

(In reply to Hartmut Schulze from comment #18)
> Created attachment 8303 [details]
> SCREENSHOTS
> 

Thx, part of the custom partitioning screen is indeed cut off on the right side.
I intend to open a separate bug report for that later (if no one beats me to it, and if it doesn't already exist)

Keeping this report for needing to add "noacpi acpi=off" to be able to boot a Live in Live mode.

( I wasn't aware that kernel parameter prevents a poweroff, btw. Maybe, after the machine halted, powering off with "Alt+SysRq+o" works?)

CC: (none) => mageia, pterjan
Assignee: tmb => pkg-bugs

Hi Marja,

powering off with "Alt+SysRq+o" does not work in this case.
machine stops, hardware is running, vents too, screen is on; RESET-Button works.
Power button works (3 seconds delay).

A Manjaro-Installation on the same (real) machine
does not need "acpi=off" and runs o.K.

seems to be a kernel issue

(In reply to Hartmut Schulze from comment #33)
> Hi Marja,
> 
> powering off with "Alt+SysRq+o" does not work in this case.
> machine stops, hardware is running, vents too, screen is on; RESET-Button
> works.



i should have tried first whether that works here after halting a machine :-/

  *****  SUMMARY  *******

Three real PC:
#1.  Nvidia card and BIOS
#2.  AMD card and BIOS
#3.  AMD-APU and UEFI-BIOS
--------------------------------------------------------
PC #1.
Ubuntu 16.04: all working, w.o. add. kernel parameters
ICAROS 2.1: all working, w.o. add. kernelparameters
Mageia cauldron sta1 Live DVD: all working, w.o. add. kernelparameters
Mageia cauldron sta1 install: all working, w.o. add. kernelparameters
-----------------------------------------------------------------------
PC#2.
(Windows 7, all "working"- o.K.)
open Suse 42.1: all working, without additional kernel parameters
Mageia cauldron sta1 Live DVD: reset on booting
Mageia cauldron sta1 install: all working, w.o. add. kernelparameters
but not installed because Work PC.
------------------------------------------------------------------------
PC#3.
Manjaro 16.06: all working, w.o. add. kernel parameters. radeon driver.
Working system, will not be changed. Chainloader for experimental dispos
(reFind is installed, only used if necessary).
sda1: /boot/efi, sda2: root (manjaro) sda3 root (experimental distros)
sdb1: swap,  sdb2: /home (manjaro) sdb3 /home (exp)
Experimental Department, root on SSD, home on HDD
Ubuntu 16.04: all working, w.o. add. kernel parameters
Sabayon 16.07: working only with "noapic Apic=off"
Fedora 24: working with "nomodeset", but resolution 640x480 only...
Mageia 5 install DVD: all working, w.o. add. kernel parameters
installation o.K. for some month (w.o. add. kernel parameters)...

Mageia 5 Live DVD: crashes instantly
Mageia Cauldron Live DVD: crashes instantly
Mageia Cauldron Install DVD: all working, w.o. add. kernel parameters
but the Installation does not boot- "Apic=off" needed
Because of this:  no cpufreq, no shutdown (electrically), halt instead ...
(reboot is o.K.)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  -->so: AMD card - AND - kernel issue?!

Created attachment 8349 [details]
Fames Last Words Video...

Record of my Videocam:

[3.610679] Found TLB entry in CRAT table (not processing)
[3.611260] Creating topology SYSFS entries
[3.611863] Finished initializing topology ret=0
[3.612950] kfd: initialized module
[3.613547] fb: switching to radeondrmfb from EFI VGA
_

(follows: blank screen, reboot)

NEXT Solution: 

> [3.613547] fb: switching to radeondrmfb from EFI VGA
> _
> 
> (follows: blank screen, reboot)
so, Thierry , before you declare, that is all meaningless ;-))

look at:
      https://bbs.archlinux.org/viewtopic.php?id=178307

So I used the kernelparameter "radeon.dpm=0" instead of "acpi=off"
and the Cauldron boots up and SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

(you may use "radeon.modeset=0", but that doesnot work really,
results in a very very long boot-time)

Thread (hopefully) to be marked as     = SOLVED =

   (In reply to Hartmut Schulze from comment #38)

> 
> So I used the kernelparameter "radeon.dpm=0" instead of "acpi=off"
> and the Cauldron boots up and SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> 

And did you leave or did you remove "noacpi"? 

Did I correctly change the Summary at the top of this bug report, or should that have been left unchanged, and "radeon.dpm=0" only added for installed systems?

Does powering your system off work well, too, now?

Summary: AMD-Graphics card: LIVE-boot not possible without "noacpi acpi=off" => AMD-Graphics card: LIVE-boot not possible without "radeon.dpm=0"

Sorry for my mistakes  :-/

I removed "acpi=off"  
(noacpi alone doesnot work, maybe on my machine only)

Your new Summary is o.K. thank you.

powering off my system works well now.

Reason: someone may ask AMD, powerswitching of the CPU AND the APU
(CPU: AMD A8 6500T.
___________________________

One additional hint: 

on my machine with an AMD "R7 200" card
I needed "radeon.modeset=0" after upgrading
from openSuse 42.1 to 42.2 alpha.
But only for ca. 3 times, then my "unbreakable openSuse installation"
worked without this parameter (puuuh). --> Self repair ???

reassigning, now that we have a kernel packagers group

Assignee: pkg-bugs => kernel

(In reply to Marja van Waes from comment #41)
> reassigning, now that we have a kernel packagers group

Yes that´s a kernel problem:

i switched back to Mageia 5,

booting the colonel 3.19.8-desktop-3.mga5 works

booting the  kernel 4.4.30-desktop-2.mga5 crashes,

   needs radeon.dmp=0 as kernel parameter.

btw i have Manjaro 16.10 testing on the same machine

NO NEED for "radeon.dpm=0"
        with kernel 4.4 and even using the 4.9 kernel.....

Now:
Kernel 4.9 needs 2radeon.dpm=0
because:
reboot instead of shutdown.

(only on systems with amd apu! (A8 6500T for example))

(In reply to Hartmut Schulze from comment #43)
> Now:
> Kernel 4.9 needs "radeon.dpm=0"
> because:
> reboot instead of shutdown.
> 
> (only on systems with amd apu! (A8 6500T for example))
........................................................
Nun ja, ist leider immer noch aktuell  :- ((

(In reply to Hartmut Schulze from comment #44)
> (In reply to Hartmut Schulze from comment #43)
> > Now:
> > Kernel 4.9 needs "radeon.dpm=0"
> > because:
> > reboot instead of shutdown.
> > 
> > (only on systems with amd apu! (A8 6500T for example))
> ........................................................
> Nun ja, ist leider immer noch aktuell  :- ((

Und bloss, weil die APU im AMD K8 6500T
gar kein Stromsparen kann.
Muss ein Fehler in der Linux Firmware Datei sein,
denn eine AMD A8 6500T ist
 >keineswegs<
eine Radeon HD 8550

Fixt das mal jemand? Bitte?

(In reply to Hartmut Schulze from comment #45)
> (In reply to Hartmut Schulze from comment #44)
> > (In reply to Hartmut Schulze from comment #43)
> > > Now:
> > > Kernel 4.9 needs "radeon.dpm=0"
> > > because:
> > > reboot instead of shutdown.
> > > 
> > > (only on systems with amd apu! (A8 6500T for example))
> > ........................................................
> > Nun ja, ist leider immer noch aktuell  :- ((
> 
> Und bloss, weil die APU im AMD K8 6500T
> gar kein Stromsparen kann.
> Muss ein Fehler in der Linux Firmware Datei sein,
> denn eine AMD A8 6500T ist
>  >keineswegs<
> eine Radeon HD 8550
> 
> Fixt das mal jemand? Bitte?

Reminder: This is an international bug tracker, please write in English.

Hallo reminder:

in doubt, ask aunt google

so: somewone cares, noone repairs...

(In reply to Rémi Verschelde from comment #46)
> (In reply to Hartmut Schulze from comment #45)
> > (In reply to Hartmut Schulze from comment #44)
> > > (In reply to Hartmut Schulze from comment #43)
> > > > Now:
> > > > Kernel 4.9 needs "radeon.dpm=0"
> > > > because:
> > > > reboot instead of shutdown.
> > > > 
> > > > (only on systems with amd apu! (A8 6500T for example))
> > > ........................................................
> > > Nun ja, ist leider immer noch aktuell  :- ((
> > 
> > Und bloss, weil die APU im AMD K8 6500T
> > gar kein Stromsparen kann.
> > Muss ein Fehler in der Linux Firmware Datei sein,
> > denn eine AMD A8 6500T ist
> >  >keineswegs<
> > eine Radeon HD 8550
> > 
> > Fixt das mal jemand? Bitte?
> 
> Reminder: This is an international bug tracker, please write in English.

Please, if this is an international bug tracker,
why not reply in an international language but a local?
(international means https://en.wikipedia.org/wiki/International

You may be annoyed that your bug is still not fixed, but that does not give you the right to start trolling.

We do what we can, pro bono, if it's not enough for you, we are sorry for the inconvenience but bugs don't solve themselves magically.

(In reply to Rémi Verschelde from comment #49)
> You may be annoyed that your bug is still not fixed, but that does not give
> you the right to start trolling.
> 
> We do what we can, pro bono, if it's not enough for you, we are sorry for
> the inconvenience but bugs don't solve themselves magically.

Excuse me, this was a test weather someone cares about bugs.
So Mageia seems NOT to be a dead borne child. (end of satire.

But honestly, o.K. - there are Bugs lasting for 17 Years before solved.
Why do I complain  ;- ))

This special problem has a workaround, I can live with that.
The Solution is to my opinion not a kernel-problem,
but in the Linux-firmware-file: a mixup with on-chip-graphics "HD 8550"
and grapics Card "HD8550". Whereas the onchip-graphic needs radeon.dpm=0,
the grapics card works with radeon.dpm=1 I found some time ago
in an  different forum.
As the Kernel team cannot find the bug,
we should consider to ask the firmware-team??

 so sorry for my ironic german part.

qote:
but bugs don't solve themselves magically.
end quote
I do not pray for magic, as I am not Prof. Zamorra...

(In reply to Hartmut Schulze from comment #50)
> (In reply to Rémi Verschelde from comment #49)
> > You may be annoyed that your bug is still not fixed, but that does not give
> > you the right to start trolling.
> > 
> > We do what we can, pro bono, if it's not enough for you, we are sorry for
> > the inconvenience but bugs don't solve themselves magically.
> 
> Excuse me, this was a test weather someone cares about bugs.
> So Mageia seems NOT to be a dead borne child. (end of satire.
> 
> But honestly, o.K. - there are Bugs lasting for 17 Years before solved.
> Why do I complain  ;- ))
> 
> This special problem has a workaround, I can live with that.
> The Solution is to my opinion not a kernel-problem,
> but in the Linux-firmware-file: a mixup with on-chip-graphics "HD 8550"
> and grapics Card "HD8550". Whereas the onchip-graphic needs radeon.dpm=0,
> the grapics card works with radeon.dpm=1 I found some time ago
> in an  different forum.
> As the Kernel team cannot find the bug,
> we should consider to ask the firmware-team??
> 
>  so sorry for my ironic german part.
> 
> qote:
> but bugs don't solve themselves magically.
> end quote
> I do not pray for magic, as I am not Prof. Zamorra...
AMD A8 6500T "Why radeon.dpm=0"

http://products.amd.com/de-de/search/APU/AMD-A-Series-Processors/AMD-A8-Series-APU-for-Desktops/A8-6500-with-Radeon%E2%84%A2-HD-8570D/59

(In reply to Hartmut Schulze from comment #27)
> (In reply to Thierry Vignaud from comment #26)
> > Since most distros have switched to systemd, poweroff != halt/shutdown.
> > Both halts the system but only the former does an electric halt
> 
> Thank you Thierry.
> To make Your reply helpfull:
> "How To" change poweroff from halt to shutdown instead please.
> (DAU question I know /(DAU = Dumb Amiga User) (I own a CMB A2000 since 1988)
> 
> Regards

DAU?.. LOL

I am still an Amiga User... and worked on the spanish translation for AmigaOS 3.5 and 3.9.. Regards

CC: (none) => ezequiel_partida