From: Mark Knecht <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: xorgconfig?
Date: Sun, 24 Jan 2010 12:12:38 -0800 [thread overview]
Message-ID: <5bdc1c8b1001241212u6298e39fqfc66556a780ba3e9@mail.gmail.com> (raw)
In-Reply-To: <hji82t$j2o$1@ger.gmane.org>
On Sun, Jan 24, 2010 at 11:46 AM, Nikos Chantziaras <realnc@arcor.de> wrote:
<SNIP>
>>
>> VIDEO_CARDS="intel vesa fbdev"
>> VIDEO_CARDS="intelvesa"
That was a mistake typing. Should have been "intel vesa" as the guy on
the intel-gfx list suggest I try vesa and right now I cannot seem to
get an i810 driver which is what just typing 'X' complains about.
>
> "intelvesa" doesn't exist. Basically, do a:
>
> equery uses xorg-drivers
>
> to see what values are acceptable for VIDEO_CARDS. The "video_cards_intel"
> USE flag for example means it's expanded from VIDEO_CARDS="intel"
>
>
>> In the first method when I boot if I have KMS_HELPERS enabled in the
>> kernel then the screen goes black at the udev step during boot and I
>> have to ssh in to reboot the machine. I can stop that by adding
>> i915.modeset=0 to the boot command line.
>
> When using KMS, make sure you have vesafb (or any other framebuffer driver)
> disabled.
>
> The next step is probably searching and asking for advice in the Intel
> section of Phoronix:
>
> http://www.phoronix.com/forums/forumdisplay.php?f=44
>
> Also, with new chipsets, it's pretty much a *must* to run the latest
> versions of X and kernel. At the moment that means xorg-server-1.7.4 and
> gentoo-sources-2.6.32-r2. If you're on Gentoo stable you will need a lot of
> unmasking :P
I have no problem I guess with ~amd64 if that's what I need to do but
the Intel guy said all I needed was xf86-intel-video 2.9 or higher and
I've got 2.9.1. He didn't suggest I needed xorg-server-1.7. I am
running gentoo-sources-2.6.32-r2.
Once I go ~amd64 I cannot go back right? Basically someday I could do
a reinstall but other than that I just have to stay ~amd64?
I'm not against doing it because desperately need the machine. If it
doesn't help it doesn't matter because right now what I have isn't
worth applying electricity to me.
The issue here is that Intel took a path of putting XP drivers out
there but there's no real support for how to make the machine run XP
which I need for TradeStation or I cannot trade futures. I've been
unable to trade for about 8 trading days now. If I cannot get XP on
the machine then the way I see it is run X and see if VMware can do
the job, or else spend $300 for some new version of Windows which I
HATE to think of doing, and I don't have it anyway. (Well, I do, but
money is REALLY tight.)
How do I go totally testing? Is that ARCH=~amd64 in my make.conf? Do I
really want that? Every leading edge version of every package on my
system? gcc? glibc? Isn't that risky when you need a machine to work
every day?
Thanks,
Mark
next prev parent reply other threads:[~2010-01-24 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 18:51 [gentoo-amd64] xorgconfig? Mark Knecht
2010-01-24 19:06 ` Drake Donahue
2010-01-24 19:15 ` Mark Knecht
2010-01-24 19:18 ` [gentoo-amd64] xorgconfig? Nikos Chantziaras
2010-01-24 19:34 ` Mark Knecht
2010-01-24 19:46 ` Nikos Chantziaras
2010-01-24 20:12 ` Mark Knecht [this message]
2010-01-24 20:19 ` Mark Knecht
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=5bdc1c8b1001241212u6298e39fqfc66556a780ba3e9@mail.gmail.com \
--to=markknecht@gmail.com \
--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