public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Monitor goes off on boot
Date: Wed, 8 Mar 2006 15:07:14 -0300	[thread overview]
Message-ID: <342e1090603081007w76690407l8997e1b79f80f4f6@mail.gmail.com> (raw)
In-Reply-To: <20060308174113.44269.qmail@web34706.mail.mud.yahoo.com>

On 3/8/06, A.R.S. KA9QLQ Alvin Koffman <alvin_ka9qlq@yahoo.com> wrote:
> --- Daniel da Veiga <danieldaveiga@gmail.com> wrote:
>
>
> > Well, it would be the safest way. But now that you mentioned it, I
> > only tested in my machine (ATI, old one) and another server (NVidia,
> > FX5200), both loaded without Direct Rendering and using VESA (but that
> > could be result of failed autodetection). I think I'll ask at the devs
> > list.
> >
>  The fx 5200 is what I have but live cd kills the display.

Well, NVidia opensource drivers are know for reliability, that
excludes a weird driver/device configuration, VESA or NV, both drivers
should work OK.

Holly's theory,

"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?"

Its my best bet by now. I would try another monitor and see what
happens. May be a hardware problem after all...

> Alvin
>
> For the best jerky you've ever had go to
> http://alk.jerkydirect.com/
> My home page
> http://ka9qlq.tripod.com
> This PC is windows free with Mepis Linux 3.4-3
> http://www.mepis.org/
> 1(747)632-4973 SIP
> Get Gizmo 1 cent per minuet calling
> http://www.gizmoproject.com/
> --
> gentoo-user@gentoo.org mailing list
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-03-08 18:13 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
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 [this message]
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=342e1090603081007w76690407l8997e1b79f80f4f6@mail.gmail.com \
    --to=danieldaveiga@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