From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Monitor goes off on boot
Date: Wed, 08 Mar 2006 14:04:00 +0100 [thread overview]
Message-ID: <440ED640.2010503@planet.nl> (raw)
In-Reply-To: <342e1090603080431j3cd9c844mc5900bcc81b5a086@mail.gmail.com>
Daniel da Veiga schreef:
>
> The livecd uses the VESA drivers, that should support most if not all
> cards
Yes, I'm sure that's true-- but what I'm wondering is, does the LiveCD
use the VESA drivers *no matter what* is returned by autodectection of
the video hardware?
My question here is because I have installed a lot of distros, and the
thing is that as soon as autodetection got an ATI product ID back from
the video hardware, I automatically got the radeon drivers. And for me,
the radeon drivers are bad news. So I would always have to manually
specify vesa anyway (after X broke).
I would actually suspect that the same thing happens to nVidia users
under most circumstances (they load the nv driver rather than vesa), but
of course the nVidia open-source drivers actually work properly, so this
is likely not a problem for them.
So I'm originally asking if the card might be subject to this condition
(since I have experienced signal loss errors due to misconfiguration of
an ATI card, which misconfiguration is in some cases due to hardware
autodetection mishandling the card when found).
> so, what you are getting is probably a VSync problem, Xorg tries to
> probe the monitor for supported resolutions and H/VSyncs, what
> happened must be that it is using a Vsync not supported by your
> monitor.
>
That certainly would explain things, but how broken would autodetection
then be (or the monitor's EDID?? support) if it couldn't even
detect/report its own Vsync range?
Not that you might not be right, but that's really scary-- scarier than
my theory of autodetect working properly, but mishandling what it detects.
Holly
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-08 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 6:18 [gentoo-user] Monitor goes off on boot A.R.S. KA9QLQ Alvin Koffman
2006-03-08 7:46 ` Iain Buchanan
2006-03-08 8:00 ` A.R.S. KA9QLQ Alvin Koffman
2006-03-08 8:17 ` Rumen Yotov
2006-03-08 8:18 ` Ghaith Hachem
2006-03-08 10:44 ` Holly Bostick
2006-03-08 10:55 ` Ghaith Hachem
2006-03-08 11:30 ` Holly Bostick
2006-03-08 12:04 ` Ghaith Hachem
2006-03-08 12:31 ` Daniel da Veiga
2006-03-08 13:04 ` Holly Bostick [this message]
2006-03-08 14:39 ` Daniel da Veiga
2006-03-08 17:41 ` A.R.S. KA9QLQ Alvin Koffman
2006-03-08 18:07 ` Daniel da Veiga
2006-03-08 22:11 ` Alan E. Davis
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=440ED640.2010503@planet.nl \
--to=motub@planet.nl \
--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