Bug 56561

I'm not sure how to provide debugging info for this problem, the boot just stalls at the point of starting KMS, a blinking cursor is active but nothing loads beyond this point, there are no errors printed to screen and there are no logs saved from the failed session.

Created attachment 69269 [details]
dmesg - successful boot kernel 3.4.7

Created attachment 69270 [details]
Xorg.0.log - successful boot kernel 3.4.7

Created attachment 69271 [details]
dmesg - failing kernel 3.6.3 running with 'nomodeset'

Created attachment 69272 [details]
Xorg.0.log - failing kernel 3.6.3 running with 'nomodeset'

Do newer kernels work without radeon driver options on the kernel command line, in particular without radeon.msi=0?

If not, can you bisect which kernel change introduced the problem?

Make sure you have the radeon firmware installed and available in your initrd if you are using one.

(In reply to comment #6)
> Do newer kernels work without radeon driver options on the kernel command
> line, in particular without radeon.msi=0?
> 
> If not, can you bisect which kernel change introduced the problem?

The kernel command line options do not effect the later kernels.

I will need some spare time to bisect, although this bug report looks to be relevant,
--
 https://bugzilla.redhat.com/show_bug.cgi?id=845745
--
user 'Richard Gration' is running the exact same laptop setup as here and experiencing identical issues.

(In reply to comment #7)
> Make sure you have the radeon firmware installed and available in your
> initrd if you are using one.


The firmware should be loading (I am using stock arch linux kernels), when 3.4.7 or 3.6.3-nomodeset boots I see '[drm] Loading R500 Microcode' in the logs. (Sorry I wrote r300 in the bug title which should be r500).

(In reply to comment #9)
> The firmware should be loading (I am using stock arch linux kernels), when
> 3.4.7 or 3.6.3-nomodeset boots I see '[drm] Loading R500 Microcode' in the
> logs. (Sorry I wrote r300 in the bug title which should be r500).

The ums driver loads later (when the filesystem is available).  If there is no firmware in your initrd, the kernel firmware loader will wait several minutes to timeout before continuing.  Can you boot into a non-X runlevel with nomodeset and then try and modprobe radeon manually from the console?

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/309.