mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: J Brook <jbk@postmark.net>
To: Andrew Ferguson <andrew@owsla.cjb.net>
Cc: raffo@neuronet.pitt.edu, papadako@csd.uoc.gr,
	alan@clueserver.org, vandrove@vc.cvut.cz,
	linux-kernel@vger.kernel.org
Subject: Re: Matrox G400 Dualhead
Date: Sat, 31 Mar 2001 17:46:38 +0000	[thread overview]
Message-ID: <20010331174638.16806.qmail@venus.postmark.net> (raw)

> I have a similar problem with my G450, booting into the framebuffer,
> then loading xdm and working in X, and then switching back to the 
> console. I may have another detail to add in that when I switch back
> to the console from X, my monitor blanks and displays the warning 
> that the frequencies are out of range.

 I think I have a work around. Boot up 2.4.3 with the framebuffer
enabled as normal. Log in as root and use the fbset program to change
the settings for all the framebuffers.
eg.

fbset -a 1024x768-70

or whatever works for you. fbset has its own man page.

This makes everything hunky-dory for me, in that after running fbset
I
can go in and out of X without ever losing the video signal.

 Petr, I had a look at the drivers/video/matrox subdir and there's no
difference between 2.4.2 and 2.4.3, however there are differences in
the drivers/video dir to do with framebuffers. The files that have
been changed in drivers/video/ are:
  creatorfb.c
  fbmem.c
  fonts.c
  modedb.c
  sbus.c

 I know nothing about the nature of the changes that have been made
though!

 It does seem to be a kernel problem rather than a X4.0.3 problem
seeing as how 4.0.3 works fine under 2.4.2, and that using fbset on
the framebuffer console in 2.4.3 solves the problem.

     John
----------------
jbk@postmark.net

             reply	other threads:[~2001-03-31 17:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31 17:46 J Brook [this message]
2001-04-01  8:55 ` [lkml]Re: " thunder7
  -- strict thread matches above, loose matches on Subject: below --
2001-05-27 22:48 mythos
2001-05-28  3:13 ` Rafael Herrera
2001-05-28  8:43   ` mythos
2001-05-28 16:16     ` Rafael Herrera
2001-04-02 22:55 Trevor Hemsley
2001-04-01 20:22 mythos
2001-04-02 17:36 ` Petr Vandrovec
2001-03-31 11:01 Trevor Hemsley
2001-04-02 17:39 ` Petr Vandrovec
2001-03-31  0:12 J Brook
2001-03-31  1:59 ` Petr Vandrovec
2001-03-31  7:09 ` Rafael E. Herrera
2001-03-30 20:13 mythos
2001-03-30 20:45 ` Alan Olsen
2001-03-30 21:10   ` mythos

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=20010331174638.16806.qmail@venus.postmark.net \
    --to=jbk@postmark.net \
    --cc=alan@clueserver.org \
    --cc=andrew@owsla.cjb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=papadako@csd.uoc.gr \
    --cc=raffo@neuronet.pitt.edu \
    --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

all inboxes | Powered by JetHome®