public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Donahue <donahue95@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] video driver / system state question
Date: Mon, 25 Jan 2010 19:23:54 -0500	[thread overview]
Message-ID: <1264465434.14075.3.camel@oddman.donahues.us.> (raw)
In-Reply-To: <20100126000912.GA806500@sgi.com>

On Mon, 2010-01-25 at 16:09 -0800, Bob Sanders wrote:
> Mark Knecht, mused, then expounded:
> > far no luck but I'm learning so it's interesting.
> > 
> >    My quick question goes like this - if I boot with no drivers I get
> > a VGA console. If I modprobe a frame buffer driver at boot time then I
> > get a nice looking but slow frame buffer console. All good so far.
> > However my graphics adapter is supposed to use the i915 driver and
> > when I modprobe that - either in auto-load or at the command like
> > after logging in - my screen goes 'black'. I'm wondering what I do -
> > other than look at what's in dmesg - to figure out what state the
> > machine is in. Is the screen turned off? Is the driver running and
> > putting out 'black'?
> >
> 
> The "black" is the monitor being driven beyond it's spec in either
> vertical or horitizontal or both.
> 
> For it to work, you'll need a proper mode line that can be stolen from
> some other Linux system  via a google search or by downloading puppy
> linux and using that to work out what X is doing.
> 
> With X and gfx, /var/log/Xorg.0.log is your friend.  Especially when
> used with a google search on the error message.
> 
> Bob 
> -  
> 
> 
have you emerged a window manager/desktop? twm and xterm are no longer
provided with the server.




  reply	other threads:[~2010-01-26  2:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 23:20 [gentoo-amd64] video driver / system state question Mark Knecht
2010-01-26  0:09 ` Bob Sanders
2010-01-26  0:23   ` Drake Donahue [this message]
2010-01-26  3:09     ` Mark Knecht
2010-01-26  5:05       ` Drake Donahue
2010-01-26 15:16         ` Richard Freeman
2010-01-26 15:19         ` Richard Freeman
2010-01-26  0:10 ` [gentoo-amd64] " Nikos Chantziaras
2010-01-26  1:03   ` Mark Knecht
2010-01-26  1:04   ` Duncan
2010-01-26  1:13   ` Mark Knecht
2010-01-26 10:59     ` Peter Humphrey
2010-01-26 17:30       ` Mark Knecht
2010-01-26 18:37         ` Nikos Chantziaras
2010-01-26 21:04           ` Mark Knecht
2010-01-26 19:37         ` Drake Donahue

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=1264465434.14075.3.camel@oddman.donahues.us. \
    --to=donahue95@comcast.net \
    --cc=gentoo-amd64@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