From: Antonio Malcolm <antonio...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Decent Starting Point For Rolling A Desktop Environment?
Date: Mon, 9 Feb 2015 10:56:30 -0800 (PST) [thread overview]
Message-ID: <268a4943-fd02-4499-8dbf-58f04e8d14d8@googlegroups.com> (raw)
In-Reply-To: <98b01b42-2db1-49e2-9ef2-27689f4e6b65@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1242 bytes --]
Yeah, my biggest gripe, setting up Nvidia, now, is that Nvidia's OpenGL
drivers overwrite Intel's OpenGL drivers, meaning if you have dual GPU's,
you get no OpenGL acceleration on the integrated (Intel) GPU.
Currently, I'm tinkering with using Nvidia's installer to install their
drivers to another directory, and point to them in an xorg conf file
specific to Optimus settings. Using their kernel module seems to break
xorg's server in Void, though (which makes it unusable- the screen flashes,
and there's no way to get to the CLI), so my next attempt is to use their
drivers with Void's nvidia-dkms package. Other wise, between xorg conf
files specific to each GPU, and lightdm's conf, I'm able to switch between
an Optimus setup and an Intel standalone setup. I should be able to get
this working, it's just going to take some trial and error. This is on an
Aorus X3+.
And getting either AMD or Nvidia, with dual graphics, on the MacBook Pro,
is ALWAYS a pain in the arse, but that has nothing to do with either AMD or
Nvidia, and everything to do with Apple. In any case, GPU setup in Linux is
typically work, and more work than getting other things configured (save
for, maybe, trackpads, sometimes).
[-- Attachment #1.2: Type: text/html, Size: 1241 bytes --]
next prev parent reply other threads:[~2015-02-09 18:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 14:58 Antonio Malcolm
2015-01-22 15:07 ` Christian Neukirchen
2015-01-22 15:09 ` Enno Boland
2015-01-22 18:35 ` Antonio Malcolm
2015-01-22 21:02 ` Logen Kain
2015-01-23 3:04 ` Antonio Malcolm
2015-01-23 3:19 ` Logen Kain
2015-01-23 16:08 ` Antonio Malcolm
2015-01-24 8:27 ` Antonio Malcolm
2015-01-27 1:43 ` Logen Kain
2015-01-27 1:52 ` Logen Kain
2015-01-27 1:57 ` Logen Kain
2015-01-27 8:55 ` Juan RP
2015-01-29 0:55 ` Antonio Malcolm
2015-02-02 21:35 ` Antonio Malcolm
2015-02-03 9:46 ` Logen Kain
2015-02-03 9:58 ` Stefan Mühlinghaus
2015-02-04 0:38 ` Antonio Malcolm
2015-02-05 10:39 ` Logen Kain
2015-02-09 18:56 ` Antonio Malcolm [this message]
2015-02-11 9:06 ` Logen Kain
2015-02-11 20:36 ` Antonio Malcolm
2015-02-04 7:47 ` Stefan Mühlinghaus
2015-02-04 18:34 ` Antonio Malcolm
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=268a4943-fd02-4499-8dbf-58f04e8d14d8@googlegroups.com \
--to="antonio..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).