CalcProgrammer1

joined 4 years ago
MODERATOR OF
 

I've decided to move the official home of OpenRGB on Lemmy to a different instance. I started on lemmy.ml because it was hosted by the Lemmy developers, but this instance has a certain (rather negative) reputation across the greater Threadiverse. I also prefer the mlmym (old Reddit style) instance and lemmy.today has this (https://old.lemmy.today/c/OpenRGB).

I will be over there on my lemmy.today account. Please join this new community to continue our OpenRGB presence on Lemmy!

Edit: !OpenRGB@lemmy.today

[–] CalcProgrammer1@lemmy.ml 1 points 3 months ago

I just updated the Flatpak release to 1.0rc2 so new installs in Bazzite, SteamOS, etc. should be the same as downloading the AppImage from openrgb.org. Remember to set up udev rules in either case.

[–] CalcProgrammer1@lemmy.ml 1 points 3 months ago

Profiles are a bit of a mess in the current builds, but should work resuming from suspend. Hibernation may not work because the USB ports are likely powered off along with the entire system and thus the USB connection may not be reestablished properly. If this is the case, not much we can do until hidapi supports hotplugging (this has been something we wanted to support for a long time bit I don't want to depend on a fork of hidapi)

18
submitted 3 months ago* (last edited 3 months ago) by CalcProgrammer1@lemmy.ml to c/openrgb@lemmy.ml
 

I was hesitant to update the Flatpak build to a release candidate, but 1.0rc2 is the build we're recommending on openrgb.org and a bunch of distros have packaged it. To be fair, if there were more digits between 0.9 and 1.0 these rcs would've been proper releases. With a lot of users having success with 1.0rc2 on other platforms, 1.0 still being a ways out do to some backend reworks and cleanups, and 0.9 being ancient now, I've gone ahead and updated the Flatpak release to 1.0rc2. You will still have to setup udev rules outside of Flatpak, as that is a limitation of Flatpak itself.

[–] CalcProgrammer1@lemmy.ml 1 points 4 months ago

There are a handful of mostly-older games that had native Linux ports by third-party porting houses which broke save compatibility between the Windows and Linux versions of the game. However, these old Linux native ports are generally absolute garbage and you're better off running the Windows version via Proton, which does have compatibility with your Windows saves as it is running the same exact game version. It seems most games with native Linux versions released by the actual developer are fine, it's just when they offload the Linux version to a porting house that it can get messy. Those old third-party ported games were typically from the original SteamOS/Steam on Linux era (2012-2015 or so) before Proton became a thing though.

 

I've tagged the second Release Candidate build for OpenRGB 1.0. This build has quite a few user interface improvements over the previous 1.0rc1 release candidate build as well as some new device support and bug fixes. However, the main reason for this release candidate is that Microsoft has started flagging the WinRing0 driver we use for low-level IO (SMBus, Super-IO, etc) as vulnerable and Windows Defender is now tampering with OpenRGB installations, deleting this driver and breaking access to RAM and motherboard RGB controls. We have been working to replace WinRing0 with a new driver called PawnIO (https://pawnio.eu/) which is more secure as it keeps all of the SMBus controller accessing code kernel-side in signed Pawn modules. Now that we've resolved all of the bugs with PawnIO, I've decided to make a release candidate both to sunset the old WinRing0 support as well as introduce the new PawnIO support. For this reason there are two 1.0rc2 versions for Windows - 1.0rc2wr0 (with WinRing0) and 1.0rc2 (with PawnIO). PawnIO has two major caveats compared to WinRing0 which is why I wanted to publish a final WinRing0 build - it doesn't support 32-bit and it requires Administrator access all the time. If you have a use case where you need a 32-bit OpenRGB build that can access SMBus, you're stuck with WinRing0. Going forward, the OpenRGB Windows Installer gives you the option to install OpenRGB as a system service, which gets around the Administrator requirement by running the OpenRGB backend as a service. The GUI can then be used as a normal user, it just connects to the service using the SDK protocol instead of connecting directly to hardware. However, there are some UI inconveniences that running as a service still has (settings changes only affect the local copy, not the service, so configuring manually added devices, disabling devices, etc. requires manual config tweaking for the service's copy of the settings files).

I still want to do one major rework before 1.0 final. This will focus on some plugin API changes and SDK protocol changes to hopefully make using OpenRGB in client/server mode a better experience.

I have also tagged 1.0rc2 builds for the OpenRGB plugins. These rc2 builds of the plugins will work with OpenRGB 1.0rc1 and 1.0rc2.

[–] CalcProgrammer1@lemmy.ml 1 points 6 months ago (1 children)

Might be because I added a systemd service recently, so OpenRGB may run as a background service. However, the device configuration in the GUI is for the local instance, not the remote one (as the service runs OpenRGB as root so it uses root's configuration). You can disable the service with systemctl disable openrgb and reboot and see if that fixes it. As part of the API/SDK rework I'm doing before 1.0 I want to add a settings interface so the GUI can change some settings on the server to fix this issue.

[–] CalcProgrammer1@lemmy.ml 4 points 1 year ago

I think the defaults are extreme and also use LW as a no telemetry/ads FF replacement, but I understand the vision. I'm fine with LW having the defaults it has, they can be easily turned off and I'd rather start with extreme privacy and just change what I need than the other way around where I could be leaving privacy options on the table.

 

OpenRGB 1.0rc1 is the first release candidate build before the upcoming official 1.0 release. This build should be considered stable, but we're looking to track down any major last-minute bugs before release. The plugin API has been updated, so if you're upgrading from 0.9 you will need to upgrade your plugins to the latest pipeline versions.

Builds for 1.0rc1 have been posted on https://openrgb.org/ as well.

 

AMDGPU driver maintainer Alex Deucher posted patches for enabling the OEM I2C interface on AMD GPUs on Linux. This interface is necessary for OpenRGB to be able to communicate with and control RGB devices on the graphics card PCB and to this point has only been available to Windows users of OpenRGB. No changes should be necessary to OpenRGB itself, once you install an updated kernel with these changes then your supported AMD GPU should be detected! I have tested Alex's development branch and was able to control my ASUS TUF RX7800XT and Sapphire Nitro+ RX580 lighting.

[–] CalcProgrammer1@lemmy.ml 134 points 1 year ago (16 children)

Honestly, not even mad. Sucks for the victims, but we need hackers poking holes in kernel anticheats. Show the game companies that kernel anticheat is a waste of effort and maybe this horrific plague of gaming will die off.

[–] CalcProgrammer1@lemmy.ml -5 points 1 year ago (4 children)

Hell of a lot better than "overthrowing the US regime" would that's for damn sure, especially if Harris wins. Just remember the Jan 6th people wanted to do the same thing, if for different reasons. Look at how well that's going for them. Play stupid games, win stupid prizes.

[–] CalcProgrammer1@lemmy.ml 3 points 1 year ago

If Bungie is behind it I have zero interest without even knowing what it is. Destiny 2 was an OK game, but its god awful anticheat bans Linux users. That is a sure-fire way to make me pretend your game doesn't exist. Client side anticheat is a plague. Do it properly on the server side.

[–] CalcProgrammer1@lemmy.ml 86 points 1 year ago (10 children)

Until any competing store releases a Linux client, I can't really argue against Steam. They are a gatekeeper and almost a monopoly, but they're also the most benevolent and pro-consumer gatekeeper that we have in the PC gaming distribution space. As long as all the competition continue to be Windows-only and, in some cases, actively work against Linux users, I don't want Valve's digital fiefdom to fall.

[–] CalcProgrammer1@lemmy.ml -5 points 1 year ago (15 children)

Ok, what is your strategy then? I don't disagree that some prominent Democrats aren't as liberal as we like, but Nancy Pelosi isn't a government official anymore. As the old guard gets replaced, the hope is that we bring in more and more liberal people over time. Voting third party is ineffective no matter how you look at it, at least not in the Presidential election. If third parties want any hope of taking over they need to start small and win local and state positions rather than just trying to start at the top. Another comment here said the Green Party has 200 elected positions of like 50000+. That's nowhere near enough influence on the ground to win a Presidential race.

Voting third party - waste your vote. Your vote means nothing. There is no chance that a third party wins a Presidential election and to think otherwise is naive. If you're a young voter, voting for the first time, you may think this is a good option. I sure did, and if you vote third party I can't stop you, but in a few election cycles I hope you'll come to the same realization that it's a waste of time. Hopefully your wasted vote doesn't let something as evil as Trump's Presidency happen.

Vote Republican - we definitely, actively, vocally, and happily continue to endorse Israel and genocide and probably stop supporting Ukraine at all and possibly even support Russia directly. We know what side Trump is on. Voting Trump doesn't help the genocide situation at all. Things in the US will go to shit, that's almost a given. Fascism gets worse on the global stage.

Vote Democrat - we know that there is at least conflict among Dems regarding Israel and Palestine. We know that they strongly support Ukraine and oppose Russia. They probably won't stop supplying Israel, but at least there's a chance that something will change. There's also still the subject of control of the Senate, House, and Supreme Court - the President alone can't do everything. It's not a perfect situation, but few things in life are. We do know that things in the US will be much better under Dems.

Unfortunately, it's going to be very very difficult to break the two-party paradigm without ranked choice voting here in the US. Do you see a serious path forward for the US that doesn't involve supporting Israel? I don't. At least not right now. Be serious. The US has too many interests (militarily and economically) in Israel. I'm open to suggestions as long as they are realistic.

[–] CalcProgrammer1@lemmy.ml 0 points 1 year ago (21 children)

Agreed 100%. I reached voting age in 2008 and I was one of those "both sides suck" idealistic young voters who voted third party. I did again in 2012 and again in 2016 thinking "Hillary's already got this one, I can protest vote". Nope, we ended up with Trump. Ever since that I will only vote blue no matter who, at least as long as the Democrats are the only viable party with some sense of normalcy. Third parties are completely unviable in the US election system. We need ranked choice for a third party vote to not be a throwaway vote. Until that happens, we can't afford to pick "the best choice", we have to pick "the best choice that actually has a chance". Even if it's not really the best choice. Very happy to have gone out and voted early last week. We need the blue wave. Once the Republican party is thoroughly stomped into the ground and made completely unviable can we focus on a truly liberal third party, but honestly we probably have a better chance of slowly moving the Dems left than we do a third party taking over. It may not happen in my lifespan but I'd rather see progress than regression.

 

I did a video tutorial and demonstration showing the Steam, FEX Emulator, and Distrobox setup I documented on the postmarketOS wiki here:

https://wiki.postmarketos.org/wiki/Steam

I go through the setup process for the Ubuntu container, FEX emulator, Steam, and then install and test two games - Half Life 2: Lost Coast and Tomb Raider (2013) to demonstrate gaming performance on an ARM device (in this case a Xiaomi Pad 5 Pro with Qualcomm Snapdragon 870 chip).

 

I managed to get Steam installed on my OnePlus 6T and Xiaomi Pad 5 Pro, both running postmarketOS, using Distrobox to create an Ubuntu 24.04 container and then installing FEX-Emu inside of it. I wrote up a guide on the postmarketOS wiki on how to do it, some issues I ran into, some tips on how to get around those issues, and a list of games I've tested. Feel free to expand upon this list if you try it out. Older games such as Half Life 2 are quite playable, especially if your device supports keyboard and mouse input. I have not yet tested using a controller.

 

I have added support for system-wide plugin installations in Linux for the upcoming 1.0 release. The plugin files can be installed system-wide to the /usr/lib/openrgb/plugins path, which allows them to be provided by distribution packages rather than manually downloading them.

I have created AUR packages for the following plugins and they have been picked up by the Chaotic AUR repository if you want binary builds.

  • openrgb-plugin-e131-receiver-git
  • openrgb-plugin-effects-git
  • openrgb-plugin-hardware-sync-git
  • openrgb-plugin-visual-map-git

I plan to update the rest of the plugins on https://gitlab.com/OpenRGBDevelopers and get them into the AUR as well before 1.0 releases. Until that happens, you will need to use the openrgb-git AUR package to utilize these new plugin packages. The current 0.9 release in the main repository does not support system-wide plugin installation.

 

I made a 3D printed, Arduino-powered desk fan based around a 120mm Corsair QL120 ARGB fan after seeing Noctua's desk fan. I wanted something similar but with RGB. It is based around CorsairLightingProtocol so it syncs with OpenRGB but also has a knob to adjust fan speed and LED brightness directly. I made a video showing it off but if you prefer to read about it, I have project documentation and files (code, assembly instructions, and 3D models) on GitLab here:

https://gitlab.com/CalcProgrammer1/OpenRGBDeskFan

The 3D models are also on Thingiverse:

https://www.thingiverse.com/thing:6655697

 

I did an interview with Linux YouTuber and podcaster Brodie Robertson on his podcast Tech Over Tea! We talked about the origins of OpenRGB, the challenges we face with reverse engineering, and discuss the OpenPleb initiative. We also talked about some other miscellaneous Linux things.

24
submitted 2 years ago* (last edited 2 years ago) by CalcProgrammer1@lemmy.ml to c/openrgb@lemmy.ml
 

#OpenRGB 0.9 has been released! Check it out at https://openrgb.org/! The full release notes are available on GitLab here:

https://gitlab.com/CalcProgrammer1/OpenRGB/-/releases/release_0.9

view more: next ›