From: "Petr Vandrovec Ing. VTEI" <VANDROVE@vc.cvut.cz>
To: "dhiltgen@toocool.calpoly.edu" <dhiltgen@toocool.itslab.calpoly.edu>
Cc: O.Waller@ee.qub.ac.uk, mlan@cpu.lu,
linuxppc-dev@lists.linuxppc.org,
Geert.Uytterhoeven@cs.kuleluven.ac.be
Subject: Re: matroxfb, anybody? (More details...)
Date: Tue, 2 Feb 1999 12:53:20 MET-1 [thread overview]
Message-ID: <205EF7C55EE@vcnet.vc.cvut.cz> (raw)
On 2 Feb 99 at 2:37, dhiltgen@toocool.calpoly.edu wrote:
> Using con2fb makes the console switching much happier... I associated
> tty2 to matrox and left the rest on control. The tty2 console didn't
> move immediately; I had to run fbset -i -fb /dev/fb1 on tty2 (still
You have some problem somewhere. If I do (atyfb + matroxfb or vga16fb +
matroxfb):
<switch to tty2>
con2fb /dev/fb1 /dev/tty2
then immediately at this point contents of screen on atyfb/vga16fb is
frozen and output on matroxfb is activated. Without any intervening
fbset, of course. I hope, that resolution on controlfb is compatible
with matroxfb capabilities (i.e. 8-32 bpp, 4bpp only on Millennium I/II).
> The cursor tends to get messed up on matrox... a second "large"
> multi-color funky cursor square (about 4x larger) exists after an fbset.
Could it be forgotten fbcon software cursor (flashing box 1x1 character)?
It could be also 32x32 pixels uninitialized hardware cursor, but I do not
know why driver should forget to initialize it.
> Scrolling is still messed up. When the matrox scrolls off the end,
> control gets the scroll action. Again, if I switch consoles things get
> reset as they should be. ^L will also clean it up temporarily.
? Isn't it control problem? vgacon + matroxfb, vga16fb + matroxfb,
atyfb + matroxfb and matroxfb + matroxfb hapilly coexist here...
BTW, updates on non-fg framebuffer are suspended until you switch
to that framebuffer.
> I can get two X servers started, and I tried to use "X :0 tty1" for one
> of them and "X :1 tty2" for the other, but I can't get them to co-exist.
> happily. The first one always takes tty7. I even tried "-keeptty" as
> it sounded like it might force the X server to stick to the initial tty
> instead of 7. Bottom line: I can switch from either one to console,
> but I can only get back to the first one that I started through
> tty7. (Either matrox or control but never both)
It could be on tty8. And I think that you want to run `X vt2 :1'
(I hope that it is not fbdev specific option).
> Also, only the active X server is "alive." The second one just freezes
> as if it thinks it lost the console to a VC switch.... not the desired
> result. So is this an X server issue, (Should ignore the VC switch) or a
> kernel issue? Sounds like a kernel issue, as the kernel should realize
It is kernel issue. At least, it send signals about getting/loosing fg
terminal on every console switch.
> 1) How can I get the two X servers to use different VCs so that I can
> switch between them. Alternatively...
I did "XF86_Mach64 & ; XF86_SVGA :1 &" just now and I got
Mach64 server running (on top of vga16fb) on /dev/tty24 and Matrox
running on /dev/tty25... /dev/tty24 is available here as right-alt-ctrl-F12,
/dev/tty25 as left-alt-ctrl-F1 + alt-left_arrow... Both hapilly working.
You can switch between them, but, of course, only one updates screen in
one moment. Because of I have dual-input EIZO, it does not cause problems
to me :-)
> 2) Is there any way to get the mouse to "fall off" one side and end
> up on the other X server (Like Sun's with multiple heads.) XFree86 4.0
> maybe? Is it even close to usable yet if I signed up to be a developer,
> or is it really messy right now?
I do not think that it is possible at this moment.
Petr Vandrovec
vandrove@vc.cvut.cz
> Note: All of this was without passing any kernel parameters. I'm now
> running with "video=matrox:vesa:0x11a,nopan,fv:80" and only using the
Why nopan? It must be slow as hell...
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-02 12:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-02 12:53 Petr Vandrovec Ing. VTEI [this message]
1999-02-04 5:49 ` matroxfb, anybody? (More details...) dhiltgen@toocool.calpoly.edu
1999-02-04 22:52 ` Takashi Oe
-- strict thread matches above, loose matches on Subject: below --
1999-02-01 18:32 Petr Vandrovec Ing. VTEI
1999-02-01 17:38 Petr Vandrovec Ing. VTEI
1999-02-01 17:15 ` Geert Uytterhoeven
1999-02-01 20:32 ` Owen Waller
1999-02-01 15:55 Benjamin Herrenschmidt
1999-02-01 16:25 ` Geert Uytterhoeven
1999-02-02 15:10 ` Owen Waller
1999-02-02 20:03 ` Geert Uytterhoeven
1999-02-01 12:51 Petr Vandrovec Ing. VTEI
1999-02-01 12:08 ` Geert Uytterhoeven
1999-02-01 16:30 ` Owen Waller
1999-02-01 16:18 ` Geert Uytterhoeven
1999-02-01 19:14 ` Benjamin Herrenschmidt
1999-02-01 20:30 ` Owen Waller
1999-02-02 15:04 ` Owen Waller
1999-02-01 10:34 Petr Vandrovec Ing. VTEI
1999-02-01 10:04 ` Geert Uytterhoeven
1999-02-01 12:35 ` Owen Waller
1999-02-02 10:37 ` dhiltgen@toocool.calpoly.edu
1999-01-30 10:00 matroxfb, anybody? dhiltgen@toocool.calpoly.edu
1999-01-30 15:32 ` Owen Waller
1999-01-30 23:34 ` matroxfb, anybody? (More details...) dhiltgen@toocool.calpoly.edu
1999-01-31 9:38 ` Gerd Knorr
1999-01-31 14:24 ` Geert Uytterhoeven
1999-02-06 15:22 ` Gerd Knorr
1999-01-31 14:36 ` Geert Uytterhoeven
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=205EF7C55EE@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=Geert.Uytterhoeven@cs.kuleluven.ac.be \
--cc=O.Waller@ee.qub.ac.uk \
--cc=dhiltgen@toocool.itslab.calpoly.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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;
as well as URLs for NNTP newsgroup(s).