From: Helge Deller <deller@gmx.de>
To: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: fbset not working with tridentfb on 2.6.x kernels
Date: Tue, 20 Apr 2004 01:00:47 +0200 [thread overview]
Message-ID: <200404200100.47906.deller@gmx.de> (raw)
Hi,
I've tried the tridentfb a few times with the last 2.6 kernel series (e.g. 2.6.6-rc1, 2.6.5, 2.6.4, 2.6.3) and with none of those kernels switching resolution with fbset worked. Everytime just screen was just scrambled with weired random graphics pixel stuff.
modprobe tridentfb on 2.6.6-rc1 gives:
tridentfb: Trident framebuffer 0.7.8-NEWAPI initializing
tridentfb: framebuffer size = 8192 Kb
tridentfb: 0000:01:00.0 board found
tridentfb: 1024x768 flat panel found
tridentfb: fb0: Trident frame buffer device 640x480-8bpp
My system is a IBM R30 laptop with the following lspci output:
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 5d) (prog-if 00 [VGA])
Subsystem: IBM ThinkPad T30
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at 80800000 (32-bit, non-prefetchable)
Memory at 80500000 (32-bit, non-prefetchable)
Memory at 81000000 (32-bit, non-prefetchable)
Capabilities: [80] AGP version 1.0
Capabilities: [90] Power Management version 1
I'm willing to test any patches to get this think working correctly....
Helge
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-19 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 23:00 Helge Deller [this message]
2004-04-23 16:52 ` fbset not working with tridentfb on 2.6.x kern James Simmons
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=200404200100.47906.deller@gmx.de \
--to=deller@gmx.de \
--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).