From: Wes Janzen <superchkn@sbcglobal.net>
To: Thomas Molina <tmolina@cablespeed.com>
Cc: Norman Diamond <ndiamond@wta.att.ne.jp>,
dan@eglifamily.dnsalias.net, linux-kernel@vger.kernel.org
Subject: Re: Blank Screen in 2.6.0
Date: Tue, 30 Dec 2003 01:03:10 -0600 [thread overview]
Message-ID: <3FF1232E.3070401@sbcglobal.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0312292137100.6639@localhost.localdomain>
Thomas Molina wrote:
>On Tue, 30 Dec 2003, Norman Diamond wrote:
>
>
>
>> ...
>
>
>I've had problems at various times during 2.5 with a number of
>card-specific framebuffer drivers so I've backed off to only using the
>VESA framebuffer driver. Maybe the connection is which framebuffer driver
>is used.
>
>
I've had the same problem. I've tried using radeonfb and it's never
worked yet since 2.5.69. In 2.6.0, no matter what mode I select, I get
a horizontal frequency of 140kHz and a ~90Hz vertical sync. My monitor
blanks and pops up the on-screen menu with the horizontal frequency
high-lighted in red. My monitor supports up to 110kHz horizontal
according to my X log.
I compiled just the vesafb in as well, but it does the exact same
thing. It doesn't matter what values or modes I put in the vga/video
parameter. Only the text mode works now, and after only 2 days uptime
I've noticed I no longer have the full vertical screen. When I type,
random text or colored/flashing blocks appear in the bottom (roughly)
1/5th of the screen. Actually, anytime I run an ncurse app in my
console, it gets smaller. Now my console only occupies 1/2 the screen,
but it doesn't seem to get any smaller than that. I'm using the boot
parameter "vga=0x132".
My point is maybe your screen isn't blank, but rather the horizontal
frequency is out of your monitor's range?
Certainly, something has changed, because with 2.6.0-test11 I was
running "vga=0x31B video=vesafb:ywrap" and it worked great, whereas now
it doesn't work at all with any fb modes.
-Wes-
next prev parent reply other threads:[~2003-12-30 7:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 3:28 Blank Screen in 2.6.0 Norman Diamond
2003-12-29 22:44 ` Thomas Molina
2003-12-30 2:14 ` Norman Diamond
2003-12-30 2:46 ` Thomas Molina
2003-12-30 7:03 ` Wes Janzen [this message]
2004-01-05 23:46 ` James Simmons
2004-01-05 23:44 ` James Simmons
2003-12-30 21:03 ` Dan Egli
2004-01-05 23:34 ` James Simmons
2004-01-05 23:35 ` Dan Egli
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 14:49 Pacheco Jason NPRI
2003-12-28 18:14 dan
2003-12-28 19:40 ` Gabor MICSKO
2003-12-28 23:08 ` dan
2003-12-29 15:02 ` Ed Tomlinson
2003-12-29 7:45 ` Tomas Szepe
2003-12-29 6:22 ` Paul Misner
2003-12-29 15:13 ` Jesper Juhl
2004-01-06 23:02 ` James Simmons
2004-01-06 23:07 ` Jesper Juhl
2004-01-06 23:14 ` James Simmons
2004-01-07 0:39 ` Jesper Juhl
2004-01-07 17:44 ` James Simmons
2004-01-07 23:55 ` Jesper Juhl
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=3FF1232E.3070401@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=dan@eglifamily.dnsalias.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--cc=tmolina@cablespeed.com \
/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