From: Alan Ianson <agianson@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gaming on gentoo
Date: Sat, 17 Dec 2022 02:12:52 -0800 [thread overview]
Message-ID: <20221217021252.693f5543060e60ff71d04571@gmail.com> (raw)
In-Reply-To: <CA+ihco8VcFAe57n-XZf2gLLyDj2Cz=LkH1dfySMDEiTb1BeF=Q@mail.gmail.com>
On Sat, 17 Dec 2022 11:03:42 +0200
Artur Tamm <artur.tamm.85@gmail.com> wrote:
> I try to have a systemd and pulseaudio free setup ("religious" reasons).
I also prefer OpenRC myself but I like pulseaudio. It doesn't replace alsa, it compliments it.
> When I need pulse I use apulse and otherwise everything else is compiled
> with alsa flag.
I normally have both alsa and pulseaudio once I have a desktop profile selected. It's worked well for me.
> I wonder if the issue is related to graphics drivers/libraries instead.
I don't think so but it might be. It really doesn't make sense does it? There is some detail in the works here. It is odd since I have never had a problem with quakespasm or darkplaces. I have always built them from source and they always run without any issues.
I also have issues with ioquake3. I can run a binary I built on slackware and it runs fine (here, on gentoo). When I try to build on gentoo the build fails. I haven't had a good look at that though, I'll leave that on the back burner and look at that another time.
> D remember having segfaults with some other
> linux ports whirh were caused by a missing library which did not show up (I
> do not remember the name but something with ?t3c?) but I think it is now in
> mesa. .If you figure out what opengl features are being used we could
> compare glxinfo outputs.
I am going to build a quakespasm with debugging support and run it through gdb. I am no expert with any of this though, so I have to read up on how to do that. I hope that will provide an answer I can understand and work out.
I'll reply with anything I find and hopefully at some point I can move beyond this.
> So, I tested quakespasm on an ryzen 7 apu (2700u) with vega gpu (thinkpad
> e485). I am using mesa drivers and a linux 6.0.8 kernel.
I was sporting a 6.1 kernel a couple days ago without any issues. :) I am running 5.15.80 now and am happy to stick with the defaults that the gentoo devs choose to go with most times.
next prev parent reply other threads:[~2022-12-17 10:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 5:17 [gentoo-user] Gaming on gentoo Alan Ianson
2022-12-13 8:37 ` Alan Ianson
2022-12-13 12:12 ` Artur Tamm
2022-12-13 12:24 ` Alan Ianson
2022-12-13 12:28 ` Artur Tamm
2022-12-13 12:47 ` Alan Ianson
2022-12-13 13:25 ` Alan Ianson
2022-12-13 13:32 ` Artur Tamm
2022-12-13 13:45 ` Alan Ianson
2022-12-13 13:49 ` Artur Tamm
2022-12-13 14:24 ` Alan Ianson
2022-12-14 21:12 ` Artur Tamm
2022-12-15 6:06 ` Alan Ianson
2022-12-15 19:06 ` Laurence Perkins
2022-12-17 1:17 ` Alan Ianson
2022-12-17 1:20 ` David Rosenbaum
2022-12-17 2:20 ` Alan Ianson
2022-12-17 9:03 ` Artur Tamm
2022-12-17 10:12 ` Alan Ianson [this message]
2022-12-17 16:54 ` David Rosenbaum
2022-12-17 18:46 ` Artur Tamm
2022-12-17 19:53 ` Alan Ianson
2022-12-20 0:07 ` Frank Steinmetzger
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=20221217021252.693f5543060e60ff71d04571@gmail.com \
--to=agianson@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