From: "Félix Ortega" <guile@mac.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: VGA out on ibook2
Date: 14 Oct 2001 18:18:11 +0200 [thread overview]
Message-ID: <1003076294.11870.1.camel@milleniumfalcon> (raw)
En sáb, 2001-10-13 a 13:05, Michel Dänzer escribio:
[...]
> Do you use Option "UseFBDev" in X?
Yes. I'm using Ati driver 16bit depth with the option UseFBDev,
PanelWidth 1024 and PanelHeigth 768.
The behaviour of the vga out it's a little strange. If I boot without
the external monitor conected, when I turn on external monitor with
m3mirror, I have the "wavy" image I described in the other message. But
if I boot with the external monitor connected, from OpenFirmware I have
external monitor and when I boot I have a cuasi-perfect text console and
an X console like if it's on another depth. If I put the X Server at 8
bit depth, I can see almost perfect picture (the colors are wrong). If I
put 16 or 24 bit, I have a "dual" screen, the screen divided in planes
so if I move the cursor across the middle of the screen, the cursor in
the external monitor exits right and enter left. If I switch back to the
text console, everything is ok.
I have tried with Ati Xfree and with FrameBuffer X, with the same
results.
I have dumped the struct aty128_crtc with printk's in the function
aty128_set_crt_enable, and it has allways the same values.
I'm a little confused because is the first time I try to tweak a driver,
anyone can help me?
Sorry my poor english, please....
--
Félix Ortega Hortiguela <guile@mac.com>
Avoid the gates of hell -- Use Linux!
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-14 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 16:18 Félix Ortega [this message]
2001-10-18 1:02 ` VGA out on ibook2 Michel Dänzer
[not found] <200110120459.XAA10187@lists.linuxppc.org>
2001-10-12 7:36 ` Paulo Abreu
2001-10-13 11:05 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 2:25 EliuG
2001-10-12 7:17 ` Michael Schmitz
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=1003076294.11870.1.camel@milleniumfalcon \
--to=guile@mac.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.