From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: f5ibh <f5ibh@db0bm.ampr.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: display problem with matroxfb
Date: Tue, 23 Jan 2001 22:54:06 MET-1 [thread overview]
Message-ID: <136DEFAC3E11@vcnet.vc.cvut.cz> (raw)
On 23 Jan 01 at 21:34, f5ibh wrote:
>
> After booting and having the display shifted to the middle of the screen, I've
Stop. Do you see right portion of screen in left, left portion in right,
with black column in between, or is picture only shifted, without
wraparound? I thought that you see wrapped display...
> 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
Are you sure that it is source of problem? Default matroxfb settings
for 640x480 is 'timmings 39721 48 16 33 10 96 2' - As horizontal position
is in multiple of 8, I cannot understand, how moving picture one column
(8 pixels) right(!) (and even worse - there is no rounding in code,
so you only changed right screen margin from 16 to 8 - this should
move picture even more to right side of screen) and one scanline up could
make so drastical change...
> 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...
After boot look at /proc/cmdline. If it is cutted at column 64 (or 79),
you have to upgrade your LILO. RedHat6.2 uses LILO with this dumb limitation.
Also, you do not have to specify vesa,pixclock,hslen and vslen, as you leave
them on defaults. So 'video=matrox:left:50,right:10,upper:32,lower:11'
should work... But I think that only 'right:' really matters.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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 21:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 22:54 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 0:57 display problem with matroxfb 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 20:34 f5ibh
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=136DEFAC3E11@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=f5ibh@db0bm.ampr.org \
--cc=linux-kernel@vger.kernel.org \
/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