From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Outputing 15.9kHz?
Date: Tue, 12 Sep 2006 18:21:44 -0700 [thread overview]
Message-ID: <49bf44f10609121821y6923c5d1l227868c291ef62ee@mail.gmail.com> (raw)
In-Reply-To: <20060906201215.35a27336.hilse@web.de>
> > The guy there says it won't work because a computer outputs a
> > non-interlaced signal and a standard TV uses interlaced. Basically,
> > exactly what you said. From your link, it looks like an interlaced
> > signal can be specifiec in xorg.conf which should solve that problem.
> > Is that right?
>
> There might be some vga cards that can't output an interlaced signal.
> But most should do pretty well. And I'm relatively sure you can't break
> anything by trying it out. Take the modelines from the link I've given
> and just try it out. And I did not talk about the different
> synchronization behaviour (mentioned in the site I've linked, too), but
> that's probably what your adapter does. So I would just give it a try.
> I would do a "hot" plugin and not wait too long if there's no picture
> appearing. No guarantees, though, but at that signal levels it
> shouldn't hurt. People did that before...
Ok I finally got this device today:
http://mythic.tv/product_info.php?products_id=30
I'm using the modeline from this link:
http://www.sput.nl/hardware/tv-x.html
and my xorg.conf looks like this:
Section "Monitor"
Identifier "monitor1"
Modeline "736x485i" 14.16 736 760 824 904 485 491 496 525
interlace -hsync -vsync
EndSection
Section "Device"
Identifier "device1"
Driver "i810"
VideoRam 4096
EndSection
Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
EndSection
Section "ServerLayout"
Identifier "layout1"
Screen "screen1"
InputDevice "mouse1" "CorePointer"
InputDevice "keyboard1" "CoreKeyboard"
EndSection
When I try to open an xfce4 desktop like this, the image is somewhat
scrambled and constantly rolls on the TV. It looks normal on a
monitor with the same settings.
/var/log/Xorg.0.log reports this:
(II) I810(0): monitor1: Using default hsync range of 28.00-33.00 kHz
(II) I810(0): monitor1: Using default vrefresh range of 43.00-72.00 Hz
(II) I810(0): Clock range: 9.50 to 163.00 MHz
(II) I810(0): Not using mode "736x485i" (unknown reason)
(II) I810(0): Not using default mode "640x350" (hsync out of range)
(II) I810(0): Not using default mode "320x175" (bad mode
clock/interlace/doublescan)
It continues through a long list of "Not using" resolutions, and then:
(--) I810(0): Virtual size is 640x480 (pitch 640)
(**) I810(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) I810(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492
525 -hsync -vsync
I've tried the 640x480i modeline from the above link with the same results.
What do you guys think?
- Grant
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-13 1:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 0:13 [gentoo-user] Outputing 15.9kHz? Grant
2006-09-06 13:18 ` Hans-Werner Hilse
2006-09-06 15:03 ` Grant
2006-09-06 18:12 ` Hans-Werner Hilse
2006-09-13 1:21 ` Grant [this message]
2006-09-13 10:46 ` Hans-Werner Hilse
2006-09-14 8:32 ` Grant
2006-09-15 14:14 ` Hans-Werner Hilse
2006-09-15 15:46 ` Grant
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=49bf44f10609121821y6923c5d1l227868c291ef62ee@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.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