From: f5ibh <f5ibh@db0bm.ampr.org>
To: vandrove@vc.cvut.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: display problem with matroxfb
Date: Tue, 23 Jan 2001 21:34:51 +0100 [thread overview]
Message-ID: <200101232034.VAA06711@db0bm.ampr.org> (raw)
Hi Petr,
I've tested the parameters you gave to me, with no success : all is right with
vesafb and wrong with matroxfb. vesa:0x105 does not work, the monitor is out of
sync (I've tried 0x305 too).
Here are parts of the syslog at system boot for matroxfb and vesafb :
matroxfb: Matrox Mystique (PCI) detected
matroxfb: MTRR's turned on
matroxfb: 640x480x8bpp (virtual: 640x13075)
matroxfb: framebuffer at 0xE7000000, mapped to 0xc8805000, size 8388608
Console: switching to colour frame buffer device 80x30
fb0: MATROX VGA frame buffer device
vesafb: framebuffer at 0xe7000000, mapped to 0xc8000000, size 8192k
vesafb: mode is 640x480x8, linelength=640, pages=11
vesafb: protected mode interface info at c000:7820
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
fb0: VESA VGA frame buffer device
After booting and having the display shifted to the middle of the screen, I've
played a bit with fbset and the -left, -right, -move, -match options. After a
while I got an 'acceptable' picture (some pixels missing on the left). At this
point, fbset -s give me the following :
mode "640x480-60"
# D: 25.176 MHz, H: 31.628 kHz, V: 60.243 Hz
geometry 640 480 640 480 8
timings 39721 50 10 32 11 96 2
accel true
rgba 8/0,8/0,8/0,0/0
endmode
I've replaced these values in /etc/fb.modes instead of the original values and
after login in the system, entering 'fbset -match -a' set the virtual consoles
correctly.
How can I pass the parameters at boot time ?
I've tried :
video=matrox:vesa:0x301,pixclock:39721,left:50,right:10,upper:32,lower:11,hslen:96,vslen:2
... without any success...
--
Regards
Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-23 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 20:34 f5ibh [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 0:57 Trevor Hemsley
[not found] <20010129011553.A1085@ppc.vc.cvut.cz>
2001-01-29 0:28 ` Petr Vandrovec
2001-01-24 23:14 Trevor Hemsley
2001-01-24 22:17 f5ibh
2001-01-24 22:59 ` Rafael E. Herrera
2001-01-24 19:42 Petr Vandrovec
2001-01-24 9:32 f5ibh
2001-01-24 1:17 Petr Vandrovec
2001-01-23 23:19 f5ibh
2001-01-23 22:54 Petr Vandrovec
2001-01-22 22:16 Petr Vandrovec
2001-01-22 21:11 f5ibh
2001-01-21 14:48 f5ibh
2001-01-22 0:18 ` Petr Vandrovec
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=200101232034.VAA06711@db0bm.ampr.org \
--to=f5ibh@db0bm.ampr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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
Powered by JetHome