From: Anuradha Ratnaweera <ARatnaweera@virtusa.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Where are the matroxfb updates?
Date: Wed, 29 Jan 2003 15:16:08 +0600 [thread overview]
Message-ID: <20030129091608.GA549@aratnaweera.virtusa.com> (raw)
In-Reply-To: <20030129083752.GD4950@vana.vc.cvut.cz>
On Wed, Jan 29, 2003 at 12:37:52AM -0800, Petr Vandrovec wrote:
>
> On Wed, Jan 29, 2003 at 02:22:26PM +0600, Anuradha Ratnaweera wrote:
>
> > both monitors display the same screen. /dev/fb1 gets registered, and
> > ttys get moved to it with con2fb, but not to any of the monitors. Both
> > monitors still seem to act as /dev/fb0. The moved tty no longer exist.
>
> What about using matroxset to set things up?
Config.in patch applied.
# ./matroxset -m 00001111
# ioctl failed: Device or resource busy
Have tried other variations, too.
# ls /proc/drivers/mga/
fb0
# cat /proc/drivers/mga/fb0/bios
BIOS: 1.2.21
Output: 0x00
TVOut: no
PINS: found
Info: c02a0a8c
Howerver, fb1 gets registered (yes as the secondary head of fb0).
# dmesg | grep matrox
Kernel command line: BOOT_IMAGE=linux ro root=306 video=matrox:vesa:0x192,font:SUN12x22,nopan
matroxfb: Matrox G450 detected
matroxfb: MTRR's turned on
matroxfb: 1152x864x16bpp (virtual: 1152x864)
matroxfb: framebuffer at 0x42000000, mapped to 0xe0805000, size 33554432
matroxfb_crtc2: secondary head of fb0 was registered as fb1
Anuradha
--
Debian GNU/Linux (kernel 2.4.21-pre4)
Adore, v.:
To venerate expectantly.
-- Ambrose Bierce, "The Devil's Dictionary"
next prev parent reply other threads:[~2003-01-29 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 2:06 Anuradha Ratnaweera
2003-01-29 5:31 ` Petr Vandrovec
2003-01-29 7:36 ` Anuradha Ratnaweera
2003-01-29 8:04 ` Petr Vandrovec
2003-01-29 8:22 ` Anuradha Ratnaweera
2003-01-29 8:37 ` Petr Vandrovec
2003-01-29 9:16 ` Anuradha Ratnaweera [this message]
2003-01-29 10:35 ` Anuradha Ratnaweera
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=20030129091608.GA549@aratnaweera.virtusa.com \
--to=aratnaweera@virtusa.com \
--cc=linux-kernel@vger.kernel.org \
--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®