From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89731] New: System doesn't boot on muxed IntelHD + HD5650
Date: Sun, 14 Dec 2014 14:03:33 +0000 [thread overview]
Message-ID: <bug-89731-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=89731
Bug ID: 89731
Summary: System doesn't boot on muxed IntelHD + HD5650
Product: Drivers
Version: 2.5
Kernel Version: 3.17.4-301.fc21.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: and.bernabei@gmail.com
Regression: No
Created attachment 160521
--> https://bugzilla.kernel.org/attachment.cgi?id=160521&action=edit
journal log
I installed Fedora21 (also tried updating the packages) but my system doesn't
boot at all when in "Switchable" mode in BIOS.
The only way to have a successful boot is to use the VESA driver (nomodeset),
or using the "Discrete" BIOS vga mode.
You can find the journal log attached, in contains useful call traces.
I am available to help with the debugging of this issue ;)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-14 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 14:03 bugzilla-daemon [this message]
2014-12-14 14:05 ` [Bug 89731] System doesn't boot on muxed IntelHD + HD5650 bugzilla-daemon
2014-12-15 15:02 ` bugzilla-daemon
2015-02-03 21:06 ` bugzilla-daemon
2015-04-07 14:59 ` bugzilla-daemon
2015-04-25 14:29 ` bugzilla-daemon
2015-04-25 19:07 ` bugzilla-daemon
2015-05-01 21:27 ` 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-89731-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox