Unable to boot

[Philippe Clérié]

I upgraded overnight from Wily to Xenial. The system will not boot. Only a blank screen after grub loads the kernel.

The recovery kernel loads fine and I was able to find the following messages:

[drm] VGACON disable radeon kernel modesetting
[drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

The recovery kernel command line had a nomodeset parameter that was not in the main kernel command line.

Note: For what it's worth I reported a similar issue against several Utopic kernels (bug #1407505). There was a back and forth with jsalisbury until a kernel finally worked. I have had no problems until today.

WORKAROUND: Adding the nomodeset parameter the main kernel command line finally booted the system.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1568211

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Philippe Clérié (pclerie)]

On 04/08/2016 09:30 PM, Brad Figg wrote:
> This bug is missing log files that will aid in diagnosing the problem.
>>From a terminal window please run:
>
> apport-collect 1568211
>
> and then change the status of the bug to 'Confirmed'.
>
> If, due to the nature of the issue you have encountered, you are unable
> to run this command, please add a comment stating that fact and change
> the bug status to 'Confirmed'.
>
> This change has been made by an automated script, maintained by the
> Ubuntu Kernel Team.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>

Installed and tried the apport-collect command:

philippe@aldebaran:~$ sudo apport-collect 1568211
ERROR: Could not import module, is a package upgrade in progress?
Error: No module named PyQt5.QtCore

I'll look at it tomorrow. (And no package upgrade in progress.)

On the other hand, the UMS error only showed up when I use the command
dmesg.

$ dmesg | grep drm

[ 2.654998] [drm] Initialized drm 1.1.0 20060810
[ 2.683811] [drm] VGACON disable radeon kernel modesetting.
[ 2.683831] [drm:radeon_init [radeon]] *ERROR* No UMS support in
radeon module!
[ 8.126683] [drm] VGACON disable radeon kernel modesetting.
[ 8.126706] [drm:radeon_init [radeon]] *ERROR* No UMS support in
radeon module!

Otherwise there are no other reference in the logs that I could find.
Not even /var/log/dmesg.

--
Philippe

------
The trouble with common sense it that it is so uncommon.
<Anonymous>

[Charlie McMackin (charliemac+bugs)]

I am also affected by this bug after upgrading to Xenial and trying to use radeon KMS. My system will only boot with `nomodeset` or `radeon.modeset=0`. Futhermore, attempting `sudo modprobe radeon modeset=1` after booting with `nomodeset` results in the same error state: screen goes blank, monitor's "No signal detected" message appears. Sometimes the machine reboots, but not always.

I have a Radeon HD5770 card. I will try to attach logs via apport

[Charlie McMackin (charliemac+bugs)]

apport-collect strongly suggested I file a new bug. I filed at (bug #1568429)

[Philippe Clérié (pclerie)]

Spooky.

This morning I booted normally.

I had a kernel upgrade to 4.4.0.18.34 early evening on 8 Apr which did have this problem. Since then there has been no updates. To the best of my knowledge I made no changes to the hardware.

But there I am with a working system. Very spooky.

I've attached the drm relevant messages from dmesg for information, just in case.

[Jaap Woldringh (jjhwoldringh)]

I have a computer with AMD A8-6600K APU processor with a module Radeon HD Graphics (HD 8570D)

Booting a new Ubuntu 16.04 from a LiveDVD the monitor receives no signal and apparently nothing happens, except the running of the DVD-player.

However, booting with the option Nomodeset is successful, only a message shows up that no UMS support is present in the Radeon module.

I am not sure this IS a bug, reading http://www.phoronix.com/scan.php?page=news_item&px=MTI2ODA
(if I am not expected to provide links, please excuse me)

[datanalytics.com (cgb-datanalytics)]

I am facing the same issue. I have upgraded from Xubuntu 14.04 to Xubuntu 16.04 and I was greeted with a black screen just after my first reboot.

I use a Radeon HD 5430 card with two monitors. Incidentally, I had to switch off one of them so that the Live USB from which I installed the upgrade would work. The problem, though, started with the reboot.

This is the output of my uname -a:

Linux tiramisu 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

There are three ways in which I can "start" my computer:

* Normal boot, which ends in a black screen.
* Recovery mode, which, after selecting "continue boot", generates errors such as "*ERROR* no UMS support in radeon module!" above, defaults to VESA module (and poor resolution), and cannot manage two screens. I enclose the Xorg.1.log file for this method.
* Recovery method and deleting the nomodesetting kernel option. After selecting "continue boot", I get a perfectly working environment: radeon module works, etc. I enclose the Xorg.0.log file for this method.

[datanalytics.com (cgb-datanalytics)]

I forgot to enclose the Xorg.1.log file for a failed boot. Here it goes.

[broadcast23 (kenn06401)]

I have an A8 3820 AMD cpu (HD 6550 graphics) I have the same problem. First I want to say that I have been booting a usb hdd since 16.04 alpha. when I booted kernal 4.4.0-10 no problem, but I then booted to 4.4.0-12 that's when the problem started. Then I waited for the release of 16.04, there was no change. I just booted the live dvd using nomodset option and the screen showed an error "no ums support on radeon module." I don't have any other driver installed except what's in the kernel.

[Roger Merritt (mcrogerm)]

I have an AMD A10-5800K (HD 7660D graphics) and have not been able to boot with 'nomodeset.' I get an error message, "ERROR: no UMS support in radeon module," and then in a few seconds the screen fades to black. I've had no problem booting from my USB with 14.04 LTS installed, or from the 15.10 LiveCD, but 16.04 seems to be hopeless. I can't even get a log of what's going on, because booting doesn't complete.

[penalvch (penalvch)]

Philippe Clérié, while utilizing the WORKAROUND, please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1568211

[Joe Helfrifch (joe-c)]

I'm having the same issue. The black screen problem showed up somewhere in the last week of January, as I documented having to use the nomodeset boot parameter in the course of investigating another bug (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1537308).

The nomodeset was a valid workaround for a while, but something in 16.04 has broken it. Adding it to the grub parameters allows me to boot, but the resolution is stuck at 800 X 600. It appears that adding nomodeset causes both the amdgpu code and the radeon code to give up and go home.

As near as I can tell from other reports I've found, this is occurring across distros.

[penalvch (penalvch)]

Joe Helfrifch, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[BeenD (doomd)]

Please check the output with deactivated "quiet splash". I've got the same problem since several weeks, but today I had time to analyze the problem. I've deactivated "quiet splash" and have seen that the computer freezes while loading the IDE/UDMA133 drivers, then I detached my IDE drives - finally ubuntu boots like charm.

[BeenD (doomd)]

Don't misunderstand - I had the same error as you guys and I've thought that the problem is my Radeon HD4250 onboard graphics card. For me it seems to be that the reason is the IDE driver. Please check and confirm - thank you.

[Tomdkat (tomdkat)]

I'm experiencing this issue on my mom's computer, a Gateway system with an AMD A6-5400K APU (Radeon HD 7540D graphics). The behavior Jaap Woldringh describes is exactly what I'm seeing. I boot an Ubuntu 16.04 liveDVD and I get the black screen. If I reboot from the liveDVD and specify "nomodeset", the system boots but in low resolution. When I look at the Xorg.0.log file, I see the "No UMS support in radeon module" message.

What's interesting is I booted the same liveDVD on another system, an HP with an AMD A8-5500k APU (Radeon HD 7560D graphics) and it booted just fine, no issues at all.

My mom's Gateway system is currently running Ubuntu 14.04.2 without any issues and at full resolution.

Of course, I would like to get this resolved before I attempt to upgrade her system to 16.04.1. :)

Thanks!

[penalvch (penalvch)]

Tomdkat, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Tomdkat (tomdkat)]

ok, will do. Should I boot from the 16.04 liveDVD, with "nomodeset" specified, and run the "ubuntu-bug linux" command?

Thanks!

[[e-mail] (mirko-guarnier)]

Same issue here with Radeon HD 7560D. Blank screen or resolution stuck at 600x800. Unusable. Sorry I cannot apport right now.
But I noticed one thing: booting ubuntu as UEFI has the issue. Booting the same partition from a separate Arch partition without UEFI, loaded ubuntu full resolution (keeping nomodeset though). Not sure how/if this is relevant

[Joe Helfrifch (joe-c)]

I saw one report that said that disabling a PCI controller solved the issue
as well, but I don't know what in my laptop could be running on that,
unless it's the memory card adapter.

Do we know that anyone is working on this upstream, or are we just
installing builds hoping something will work magically? I bought this
laptop ten months ago to be a dedicated development box, and I've gotten
about two workdays out of it. I could just fall back to 14.04 at this
point with the keyboard fix and at least get stuff done.

On Wed, Jul 20, 2016 at 4:44 PM, <email address hidden> <
<email address hidden>> wrote:

> Same issue here with Radeon HD 7560D. Blank screen or resolution stuck at
> 600x800. Unusable. Sorry I cannot apport right now.
> But I noticed one thing: booting ubuntu as UEFI has the issue. Booting the
> same partition from a separate Arch partition without UEFI, loaded ubuntu
> full resolution (keeping nomodeset though). Not sure how/if this is relevant
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1568211
>
> Title:
> Unable to boot
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> I upgraded overnight from Wily to Xenial. The system will not boot.
> Only a blank screen after grub loads the kernel.
>
> The recovery kernel loads fine and I was able to find the following
> messages:
>
> [drm] VGACON disable radeon kernel modesetting
> [drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!
>
> The recovery kernel command line had a nomodeset parameter that was
> not in the main kernel command line.
>
> Note: For what it's worth I reported a similar issue against several
> Utopic kernels (bug #1407505). There was a back and forth with
> jsalisbury until a kernel finally worked. I have had no problems until
> today.
>
> WORKAROUND: Adding the nomodeset parameter the main kernel command
> line finally booted the system.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568211/+subscriptions
>

--
Get your facts out, get your fiction out, get your story out. There are no
excuses anymore. --John Rogers
http://joe.helfrich.us

[Charlie McMackin (charliemac+bugs)]

Is there a big difference between bug #1568429 and this one? If not, I've attached all the apport data I know how to on that bug and am willing to run commands / help debug if devs with more know-how can point me in right direction...

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[rade (radisha)]

Radeon 3650 HD same problem here. No UMS Support

[elhoir (jfarroyo82)]

AMD RX 470 here now, im getting the
[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting

message

let me attach my data

[penalvch (penalvch)]

elhoir (jfarroyo82), it is most helpful if you file a new report. If the nomodeset WORKAROUND lets you boot, please file a new report via a terminal:
ubuntu-bug linux

Else, use:
https://bugs.launchpad.net/ubuntu/+source/linux/+filebug

Please feel free to subscribe me to it.

[elhoir (jfarroyo82)]

Hello Christopher,

I already did, but as i was unsure about the affected package, i set it to xserver-xorg-video-amdgpu instead of Linux....

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1818580

[elhoir (jfarroyo82)]

And yes, the "NOMODESET" parameter lets me boot, but performance is really awful :(

[shadowvzs (shadowvzs)]

i also got black screen, indiferent ubuntu/linux mint/manjaro, kernel 4.15 or 5.0...
only with nomodeset work with awfull resolution :( amd radeon rx vega 11

[penalvch (penalvch)]

shadowvzs, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.