public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: Matroxfb in 2.6 still doesn't work in 2.6.7
Date: Sat, 19 Jun 2004 21:30:53 +0200	[thread overview]
Message-ID: <20040619193053.GA3644@irc.pl> (raw)
In-Reply-To: <20040619190503.GB17053@vana.vc.cvut.cz>

On Sat, Jun 19, 2004 at 09:05:03PM +0200, Petr Vandrovec wrote:
> > My LCD monitor turns black and slowly change into all white.
> > There is some very bright white area in lower right corner of monitor.
> 
> When monitor goes into this mode? Immediately after kernel starts, or
 
 During kernel boot, before even mounting root and running init.

> 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.

> Are you sure that you do not have any
> fbset or stty commands in your startup scripts?

 There was single 'stty onlcr'. After commenting it out nothing changed.

> What if you boot with init=/bin/bash?

 No change. Screen melts to white before bash is execed.  
 
> > % dmesg | grep -i matrox
> > matroxfb_crtc2: secondary head of fb0 was registered as fb1
> 
> 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.  

> or video=matroxfb:outputs:100,1280x1024-16@60 (if you plugged your LCD to
> digital output with digital-analog connector convertor) ?

 With LCD still connected to analog output and outputs:100, LCD turns 
itself off during kernel boot.
 
> You can also try patching your kernel with 
> http://platan.vc.cvut.cz/ftp/pub/linux/matrox-latest/matrox-2.6.7-rc2-c1818.gz. It
> should help you if videomode is destroyed by your initscripts.

 My initscripts don't mess with videomode, but I will check this patch.

-- 
Tomasz Torcz               "Never underestimate the bandwidth of a station 
zdzichu@irc.-nie.spam-.pl    wagon filled with backup tapes." -- Jim Gray 


  reply	other threads:[~2004-06-19 19:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 21:10 Matroxfb in 2.6 still doesn't work in 2.6.7 Tomasz Torcz
2004-06-19 19:05 ` Petr Vandrovec
2004-06-19 19:30   ` Tomasz Torcz [this message]
2004-06-19 20:39     ` Petr Vandrovec
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
  -- strict thread matches above, loose matches on Subject: below --
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=20040619193053.GA3644@irc.pl \
    --to=zdzichu@irc.pl \
    --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