From: Mark <whitetr6@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Nvidia problem
Date: Wed, 27 Jul 2005 07:54:12 -0400 [thread overview]
Message-ID: <1f81f7e005072704542bf2b69e@mail.gmail.com> (raw)
In-Reply-To: <pan.2005.07.27.09.59.06.354248@cox.net>
Well, now it works :-)
I don't know what fixed it, but my guess is, as Duncan suggested, I
didn't reboot after recompiling the kernel, and before emerging
nvidia. After that sequence, the module loads fine.
Thank you all very much for the tips and taking the time to help. Best regards
On 7/27/05, Duncan <1i5t5.duncan@cox.net> wrote:
> Michal Zeravik posted <42E7328A.9030002@olomouc.com>, excerpted below,
> on Wed, 27 Jul 2005 09:06:50 +0200:
>
> > Anyone got work X transparency (composite) with xcompmgr working with
> > 2.6.12 and nvidia drivers? For me it is not working even with generic nv
> > driver.
>
> I don't do unfreedomware, and have an issue with NVidia not providing
> even programming interface information to the community, so I refuse to
> buy NVidia video.
>
> However, I got it working with an ATI Radeon 9200 SE and the xorg native
> drivers the other day. It's /nice/ in KDE. That was running the
> xorg-x11-6.8.99.15 6.9/7.0 snapshot build, with unified framebuffer on a
> dual 2048x1736 monitor layout.
>
> Composite crashes with Xinerama enabled and dual framebuffers instead of
> the single unified framebuffer, thru 6.8.99.13. The .14 and .15
> snapshots won't xinerama correctly even without composite, and I decided I
> liked the separate framebuffers with xinerama (I like being able to
> switch the resolution on one monitor without having to worry about the
> other one as well), so I switched back to .13, without composite, of
> course, since it crashes in xinerama mode.
>
> Still, I was able to play with it enough to get a feel for why everybody
> is going so crazy over composite, and what it can do. Once it goes fully
> stable, it'll definitely support some really nice eye candy. It's really
> cool when it works.
>
> --
> Duncan - List replies preferred. No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." Richard Stallman in
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
>
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>
--
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-27 11:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 2:28 [gentoo-amd64] Nvidia problem Mark
2005-07-27 2:45 ` [gentoo-amd64] " Sebastian Zaffarano
2005-07-27 2:52 ` Mark
2005-07-27 3:38 ` Sebastian Zaffarano
2005-07-27 3:49 ` Mark
2005-07-27 4:25 ` [gentoo-amd64] " Duncan
2005-07-27 4:28 ` Duncan
2005-07-27 5:00 ` Ian McCulloch
2005-07-27 6:33 ` [gentoo-amd64] " Dulmandakh Sukhbaatar
2005-07-27 21:40 ` Luke-Jr
2005-07-27 5:48 ` [gentoo-amd64] " Joerg Gollnick
2005-07-27 7:06 ` Michal Žeravík
2005-07-27 7:20 ` Michael Edwards
2005-07-27 9:59 ` [gentoo-amd64] " Duncan
2005-07-27 11:54 ` Mark [this message]
2005-07-27 15:06 ` Michal Žeravík
2005-07-27 16:23 ` [gentoo-amd64] " Duncan
2005-07-27 17:52 ` [gentoo-amd64] " Sami Samhuri
2005-07-27 19:21 ` [gentoo-amd64] " Duncan
2005-07-27 21:42 ` [gentoo-amd64] " Luke-Jr
2005-07-28 1:50 ` Sami Samhuri
2005-07-28 11:11 ` [gentoo-amd64] " Duncan
2005-07-28 18:18 ` Sami Samhuri
2005-07-27 7:12 ` [gentoo-amd64] " Jeremy Huddleston
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=1f81f7e005072704542bf2b69e@mail.gmail.com \
--to=whitetr6@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