From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FGyRK-0003YN-DU for garchives@archives.gentoo.org; Wed, 08 Mar 2006 13:10:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k28D9oTF018030; Wed, 8 Mar 2006 13:09:50 GMT Received: from smtp17.wxs.nl (smtp17.wxs.nl [195.121.247.8]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k28D46di024492 for ; Wed, 8 Mar 2006 13:04:06 GMT Received: from [10.0.0.150] (ip3e83ab52.speed.planet.nl [62.131.171.82]) by smtp17.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IVT00KBQ8ATIW@smtp17.wxs.nl> for gentoo-user@lists.gentoo.org; Wed, 08 Mar 2006 14:04:06 +0100 (CET) Date: Wed, 08 Mar 2006 14:04:00 +0100 From: Holly Bostick Subject: Re: [gentoo-user] Monitor goes off on boot In-reply-to: <342e1090603080431j3cd9c844mc5900bcc81b5a086@mail.gmail.com> To: gentoo-user@lists.gentoo.org Message-id: <440ED640.2010503@planet.nl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5 (X11/20060206) X-Enigmail-Version: 0.94.0.0 References: <20060308061805.56816.qmail@web34712.mail.mud.yahoo.com> <440EB580.3030009@planet.nl> <4bf052bf0603080255s2be03911p161a61959af35235@mail.gmail.com> <342e1090603080431j3cd9c844mc5900bcc81b5a086@mail.gmail.com> X-Archives-Salt: c339b18b-7187-4e49-b6be-29d06fc74135 X-Archives-Hash: 8a2958ea5c5a42e7c0f5c4d64a9035e0 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