From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 6229] New: modprobe atyfb before fbcon -> black screen
Date: Tue, 14 Mar 2006 16:23:47 -0800 [thread overview]
Message-ID: <20060314162347.6bb72b1f.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Tue, 14 Mar 2006 16:14:32 -0800
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 6229] New: modprobe atyfb before fbcon -> black screen
http://bugzilla.kernel.org/show_bug.cgi?id=6229
Summary: modprobe atyfb before fbcon -> black screen
Kernel Version: 2.6.15
Status: NEW
Severity: normal
Owner: jsimmons@infradead.org
Submitter: samuel.thibault@ens-lyon.org
Most recent kernel where this bug did not occur: Never tested it before
Distribution: debian
Hardware Environment: 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) and 0000:01:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
Hi,
When trying to use framebuffer, I first inserted atyfb (before inserting fbcon) and got a black screen. As soon as fbcon is inserted, the console shows up right, but in the middle the screen is just black.
Steps to reproduce:
- get sure fbcon is compiled as module and not inserted
- modprobe atyfb
Regards,
Samuel
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
reply other threads:[~2006-03-15 0:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060314162347.6bb72b1f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).