From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70861] New: Radeon KMS Not Triggering On Boot
Date: Wed, 19 Feb 2014 17:11:16 +0000 [thread overview]
Message-ID: <bug-70861-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=70861
Bug ID: 70861
Summary: Radeon KMS Not Triggering On Boot
Product: Drivers
Version: 2.5
Kernel Version: 3.13.3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: segaloco@gmail.com
Regression: No
I recently bumped from 3.13.2 to 3.13.3, and upon bootup, the 'radeon' driver
didn't seem to kick-in like usual. I've tried rebooting a couple of times but
to no avail. When I booted up the 3.13.2 kernel once again, everything worked
fine.
I'm not sure what all information you'll need to diagnose what this problem
will be, but I'm happy to provide whatever is needed. For starters, my video
line in grub.conf (Legacy GRUB) is:
video=radeon:mtrr:3,ywrap,1366x768-32@60
What I want to stress is that this behavior started with kernel 3.13.3, as
everything worked as intended in 3.13.2.
My system is loosely based on Gentoo although it is almost entirely upstream
packages built by hand now, so there wouldn't be any distro modifications
present between kernel versions. All I did for the new kernel is copy .config
over from 3.13.2 and ran and exited menuconfig to freshen the file. Please let
me know any other information that will help diagnose this problem! Thank you!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-02-19 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 17:11 bugzilla-daemon [this message]
2014-02-19 17:18 ` [Bug 70861] Radeon KMS Not Triggering On Boot bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-70861-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.