User talk:Vados

From ArchWiki
Latest comment: 13 April 2021 by Vados in topic System76 Oryx Pro

System76 Oryx Pro

Hey Vados! I came across your article while investigating lm-sensors on the oryp7 (basically identical to the oryp6 you probably have). I haven't had any more luck than you; but I wanted to stop by and mention that the Oryx Pro article has come a long way since you contributed in December. Might be worth a revisit!  :) -- Sweyn78 (talk) 02:44, 7 April 2021 (UTC)Reply[reply]

Hey Sweyn78,
I've never messaged anyone on with wiki before so I hope this is how you do it, I can't tell if I'm replying to your message or not...
Thanks for the pointer! I've been happily using my Oryx Pro this whole time and haven't had any problems :).
One thing I did notice was that `system76.service` is actually failing on my machine now, and because of python dependencies:
   Mar 30 18:43:17 mroryxman system76-daemon[3042416]: Traceback (most recent call last):
   Mar 30 18:43:17 mroryxman system76-daemon[3042416]:   File "/usr/lib/system76-driver/system76-daemon", line 34, in <module>
   Mar 30 18:43:17 mroryxman system76-daemon[3042416]:     import system76driver
   Mar 30 18:43:17 mroryxman system76-daemon[3042416]: ModuleNotFoundError: No module named 'system76driver'
   Mar 30 18:43:17 mroryxman systemd[1]: system76.service: Main process exited, code=exited, status=1/FAILURE
This may be due to some pyenv settings getting picked up by the system or something but I sure wish this bit of their kit was also written in rust, I'll take a look and see if anything has changed.
-- Preceding unsigned comment by Vados (talk) 2021-04-06T22:52:18‎
Best practices for wiki messaging are to always include a signature -- just add four tildes (~~~~), and your signature will be inserted on save. I've gone ahead and signed your message for you this time.
Also: You should create a new section (== Section title ==) when starting a talk-page conversation. In this case, though, since you are replying to an existing conversation, the best thing to do would have been to reply at your own talk page, and use the {{Ping}} template. Unfortunately, the Arch Wiki lacks that for some reason; so perhaps the best workaround is to just mirror the conversation on both of our talk pages, lol. And by that: I mean Ctrl+A, Ctrl+C, Ctrl+V. :p
Oh, and another thing: It's best to indent your reply. You can do this by putting any number of colons (: Lorem ipsum dolor sit amet) before each line of your message. I've gone ahead and added these to yours, as well.
Also: My apologies for editing said colons into your reply! Anything other than adding a signature is considered bad etiquette; but I figured it'd be fine in this case, since you're new to talk pages.
Anyways! Onto the important stuff, lol.
Glad yours has been working well! I had no audio with mine out of the box -- quite annoying! I haven't seen your error, though. I would hope user pyenv settings wouldn't impact something run as root by systemd.
-- Sweyn78 (talk) 03:07, 7 April 2021 (UTC)Reply[reply]
Wow, that's fascinating, haven't done much wiki-talking before, I had no idea about any of this. Honestly it feels really painful that no one built a normal messaging system and just... had saving to a page(rather than some DB) be an implementation detail. Thanks for letting me know, hopefully this one is a bit better.
Oof, no audio out of the box is certainly unfortunate, I can imagine myself being confused for days wondering what was wrong, spending tons of time with jack or alsa wondering how you'd misconfigured something despite not even doing anything on the box yet! yeah as far as my error goes I actually had that happen to another package -- that's true, I had the issue happen before but I think it was a --user unit instead.
-- Vados (talk) 03:33, 7 April 2021 (UTC)Reply[reply]
I know! Wiki talk pages are terrible. It's stayed pretty much unchanged since the early 2000s...
New headers should just be for entirely new topics/conversations. New replies can just go under existing headers.  :)
Yeah, that about sums up my first few days, lol. Turns out I had to enable a systemd service for system76-firmware-daemonAUR, and create a file in /etc/modprobe.d.
Ah, okay. That would make sense for a user unit. The system76 service isn't user, though, I don't think.
I'm working right now on getting games running with the dGPU using system76-powerAUR. Seems a bit temperamental so far.
-- Sweyn78 (talk) 04:01, 7 April 2021 (UTC)Reply[reply]
I just wonder if this is what everyone on Wikipedia and other Wikis are doing?
Thanks for teh clarification -- hopefully this one indents properly as a response!
Games have actually worked pretty well for me -- though I only play CS:GO and Among Us. Every update was a crapshoot though, some blog posts to be had on broken NVIDIA drivers making it into my system and I got to learn more than I wanted to about rolling back kernel module updates. What issues are you having with games?
I actually keep my laptop screen shut and only run on the dGPU (two monitors), which is the whole reason I went with the Oryx Pro to start with.
Vados (talk) 04:29, 7 April 2021 (UTC)Reply[reply]
Yep, it sure is. Although, at Wikipedia, the talk pages are a million times more toxic. All I'll say is there's a good reason why its editor count has been declining for so long. 😅
Oh boy lol. I've already had one of those situations, myself. Probably plenty more to come as I figure out this switchable graphics thing.
Oh lol. I work and game on a couch. On a touchpad. I'm mildly insane, clearly. But it works well-enough, and sure beats sitting at a desk all the time. :D
I'm pretty much always plugged-in, so I would be fine just having the dGPU render everything. But I'd rather get hybrid working, for temperature and fan-noise reasons.
Speaking of which: I sure hope I can figure out how to get pwmconfig and fancontrol to behave, soon. I'm wondering if maybe I can do sensors-detect on Pop!_OS and just copy the resulting configs over.
-- Sweyn78 (talk) 04:36, 7 April 2021 (UTC)Reply[reply]
I've figured out how to control the fans! Unfortunately, it requires editing and recompiling the firmware. I've created a feature request on GitHub to get system76-acpi-dkmsAUR to expose the PWM settings in sysfs; once implemented, pwmconfig should be able to work. -- Sweyn78 (talk) 18:52, 12 April 2021 (UTC)Reply[reply]
Wow that's huge -- well done! Editing and recompiling the firmware is a bit of work to make this possible. I think I actually missed your previous message, my apologies (if you'd prefer please email me @
Originally for switching graphics I used optimus-manager but then it stopped working, but at that point the system76 CLI tools already had support for changing the driver. It's all foggy now but I *think* at the beginning the CLI didn't have support for changing the driver on the fly? I can't remember. Now my starting script is basically just CLI commands to switch into the GPU then startx (my laptop acts more like a desktop).
Hahahah working and gaming on a couch definitely is insane (ly comfortable sounding), laptops are not for laps!
Glad you finally have control of your fans though -- now make sure not to set them too low! :)
Vados (talk) 01:03, 13 April 2021 (UTC)Reply[reply]