From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 31676] New: garbled text after loading nouveau module on EFI boot; X driver thinks there are no connected outputs
Date: Wed, 17 Nov 2010 02:49:08 -0800 (PST) [thread overview]
Message-ID: <bug-31676-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31676
Summary: garbled text after loading nouveau module on EFI boot;
X driver thinks there are no connected outputs
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: bjt23-HmMyXyqgL2CVc3sceRu5cw@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=40329)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40329)
dmesg output as I modprobe nouveau
Hopefully this isn't too similar or the same as #29171. I have one of he new
11" MacBook Air machines (MacBookAir3,1) with the 320M chipset (PCI id 0x08a2,
NVAF I believe).
I'm booting in EFI mode using grub2, as this machine appears to have issues
setting up the SATA controller in BIOS emulation mode. I've booted in BIOS
mode and done a dump of the video BIOS and int10 vector, which I'm loading via
grub2's "loadbios" command.
I'm running 2.6.37-rc2 with a bunch of hw-specific patches applied (as well as
a patch to boot in EFI physical rather than virtual mode, which unbreaks PCI),
the 16 Nov nouveau-drm snapshot from pq's webdir on people.fd.o, and
xf86-video-nouveau git rev 1143e7a.
First I modprobe nouveau. Screen flashes, and it looks kinda garbled and
messed up. I can vaguely see the cursor flashing, and I can ssh in. I'll
attach dmesg output. From that it looks like it's not finding connected
outputs, and it's using a fallback 1024x768 res (the LCD panel's native res is
1366x768).
From there I try to start X, and it looks like it has the same problem, unable
to find a connected output, and then the server segfaults.
Also possibly of note: I'm unable to get the nvidia proprietary driver to work
either (it just claims it can't initialize the card at all and bails).
Please let me know if there's any more information I can provide.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-11-17 10:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 10:49 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-31676-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-11-17 10:49 ` [Bug 31676] garbled text after loading nouveau module on EFI boot; X driver thinks there are no connected outputs bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 11:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 16:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-17 21:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-25 11:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-25 12:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-05 21:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-14 15:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-16 14:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-16 16:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-17 7:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-03 21:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-23 10:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-23 12:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <20110323125339.90BD713004F-4GnqB8vgsbnwRzGw0Gvu8Q/tdpCO6/zZ@public.gmane.org>
2011-03-23 18:04 ` Emil Velikov
2011-03-27 9:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-11 22:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-12 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-15 22:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-15 22:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-15 22:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-31676-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.