From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 3698] New: vesafb doesn't work anymore
Date: Thu, 4 Nov 2004 10:34:47 -0800 [thread overview]
Message-ID: <20041104103447.526c0587.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Thu, 4 Nov 2004 05:55:57 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3698] New: vesafb doesn't work anymore
http://bugme.osdl.org/show_bug.cgi?id=3698
Summary: vesafb doesn't work anymore
Kernel Version: 2.6.9
Status: NEW
Severity: normal
Owner: jsimmons@infradead.org
Submitter: dilorenzo@kmfms.com
Distribution:
Debian Sarge
Hardware Environment:
Dell Inspiron 8600 notebook / nvidia geforce graphic
Problem Description:
I used vesafb with mode 0x314 (in lilo vga=788) until kernel 2.6.7.
Now I decided to upgrade to 2.6.9, I did it as always:
make oldconfig and so on...
But when I restart, the screen blanks, I tried it with vga=ask, but
it didn't work with the 3xx modes, the normal modes work, but
as I work a lot with the console I need a 'nice' one, like mode 314.
I compared the bootlogs in /var/log/kern.log and found that with the
2.6.7 kernel there were some lines with 'vesafb: ...' and after that
there was a line :
'Console: switching to colour frame buffer device 100x37'.
But with the 2.6.9 kernel these lines don't appear.
------- 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:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
reply other threads:[~2004-11-04 18:34 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=20041104103447.526c0587.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).