← Back to team overview

kernel-packages team mailing list archive

[Bug 1568211] [NEW] no UMS support in radeon module

 

Public bug reported:

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.

Adding the nomodeset parameter the main kernel command line finally
booted the system. It's kind of ugly but it seems to work.

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.

Hope that helps.

** Affects: linux-meta (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1568211

Title:
  no UMS support in radeon module

Status in linux-meta package in Ubuntu:
  New

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.

  Adding the nomodeset parameter the main kernel command line finally
  booted the system. It's kind of ugly but it seems to work.

  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.

  Hope that helps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1568211/+subscriptions


Follow ups