From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Cc: zdzichu@irc.pl
Subject: Re: Matroxfb in 2.6 still doesn't work in 2.6.7
Date: Sat, 19 Jun 2004 22:39:54 +0200 [thread overview]
Message-ID: <20040619203954.GC17053@vana.vc.cvut.cz> (raw)
In-Reply-To: <20040619193053.GA3644@irc.pl>
On Sat, Jun 19, 2004 at 09:30:53PM +0200, Tomasz Torcz wrote:
> On Sat, Jun 19, 2004 at 09:05:03PM +0200, Petr Vandrovec wrote:
> > after you start X? Picture you see happens with some (stupid) monitors
> > if there are missing sync pulses.
>
> Samsung SyncMaster 171s doesn't look stupid to me :-) And XFree86/Xorg
> somehow manages to work.
It should present you with some "hsync not supported" or something like that.
> > It works for me, with CRT analog monitor... What if you boot with
> > video=matroxfb:outputs:010,1280x1024-16@60 (if you plugged your LCD to analog
> > output)
>
> This is how my LCD is connected. Tried that - no change, still no picture.
> It doesn't work the same way as when no passing 'outputs:' to kernel, so
> I presume 'output:010' is default.
Default is '111', so you can plug your monitor to any of available outputs.
If you want exactly same videomode as you use under X, you should use
video=matroxfb:vesa:0x11A,right:48,hslen:112,left:248,hslen:112,lower:1,vslen:3,upper:48
maybe with ',sync:3' if +hsync/+vsync are mandatory for your monitor.
Petr Vandrovec
next prev parent reply other threads:[~2004-06-19 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 21:10 Tomasz Torcz
2004-06-19 19:05 ` Petr Vandrovec
2004-06-19 19:30 ` Tomasz Torcz
2004-06-19 20:39 ` Petr Vandrovec [this message]
2004-06-20 16:04 ` Tomasz Torcz
2004-06-20 17:01 ` Petr Vandrovec
2004-06-20 21:37 ` Tomasz Torcz
2004-06-21 1:31 ` Petr Vandrovec
2004-06-21 18:10 ` Tomasz Torcz
2004-06-22 0:51 ` Giuseppe Bilotta
2004-06-22 12:28 ` Tomasz Torcz
2004-06-20 21:57 Marek Szuba
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=20040619203954.GC17053@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
/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
all inboxes | Powered by JetHome®