Basilisk v3 Settings Not Sticking On Shutdown

[0pLuS0]

Details about the problem

I have a Blackwidow v3 Tenkeyless and a Basilisk v3, I only made three changes in Polychromatic. I changed the 1st mouse dpi to 400, and I set both of the peripherals for the Effect on Static, which then showed the default Razer Green as the color.

When I shut down my computer and then turn it back on, the mouse reverts back to cycling through the colors and won't stop until I open Polychromatic and click on Static, even though it's shown hightlighted.

If I reboot my computer the Static setting is sticking, so I don't understand why it won't stick on shutdown.

I have set in /etc/rc.d/rc.modules.local; /sbin/razerkbd to have openrazer loaded on start.

Operating System / Desktop Environment / Version(s)

Slackware 15.0 x86_64
Openbox 3.6.1
nvidia-driver-510.60.02
MSI Optix G27CQ4
xorg-server-1.20.14
qt5-5.15.3
gtk+3-3.24.31
openrazer 3.3.0
polychromatic-0.7.3

Here's a screen shot of the settings for the mouse.

THANKS

P.S. After posting this issue, I see what the problem is. I'm Dual Boot, Slackware 15.0 & Windows 10. When I shut down from Windows, this is when I'm seeing the problem. Hopefully there's a way to fix this, if end-users are Dual Boot, using Razer in Windows.

[lah7]

OpenRazer's daemon has a software persistence feature which is supposed to restore settings at log on. Please check this is enabled:

~/.config/openrazer/razer.conf

[Startup]
restore_persistence = True

The options to re-apply are stored in ~/.config/openrazer/persistence.conf.

If that doesn't work, the other options are:

• Run a polychromatic-cli command at log on using your desktop environment's equivalent "Start-up Applications" feature. (For example, in Cinnamon)
• Write a Python script and interface with OpenRazer's Python library directly and run that at log on.
• Hang tight for the future, as I am wanting to add a feature here to conveniently set this up via GUI. Duplicate of #333.

[0pLuS0]

Interesting, the Blackwidow v3 Tenkeyless settings stuck, but the mouse wouldn't with it on restore_persistence = False

I set it to True and it works.

Why would the keyboard work and the mouse wouldn't and the restore_persistence had to be changed? I would of assumed it would of needed to be set to True for both devices?

THANKS

[lah7]

It varies by hardware. OpenRazer is setting hardware effects, so the firmware (especially for older models) usually remembers settings between power cycles. Razer Synapse and some of the newer Razer devices handle everything in software, so they default to spectrum on power on and expect something on the computer to do all the work.

OpenRazer introduced this persistence feature to cater to those "software only" hardware. It's also possible that when support was added, it was unknown for that model. It can be turned on via Polychromatic (Controller app) too under Tools → OpenRazer → Configure.

Since that resolves the problem, I'll close this issue and track the enhancement in #333, so users can set up how they like it without needing to enable that OpenRazer feature.

[0pLuS0]

Using Polychromatic, I'm not sure, when the settings are suppose to be applying, I assumed right when you reboot the system and openrazer is loaded.

The problem isn't Linux and this is not the solution to the problem I'm seeing, it's because I'm Dual Boot with Windows, that the issues I'm seeing only happen when I shut the computer down inside Windows, and then start the computer back and boot into Linux, then I see this problem.

If I shut down the computer in Linux, and then start the computer, and boot into Linux, there isn't any issue, the mouse options stick as soon as I start up Slackware, half way through the boot up, when Openrazer loads, the mouse goes solid green.

Also, if I shut down in Windows, then start the computer, and boot into Linux, the mouse Static lighting doesn't stick until I log into X.

Sorry for troubling you, I should of reported this to Openrazer, unless Polychromatic plays some part here in this too?

THANKS

[lah7]

It's likely because Razer Synapse handles everything in software, so when that takes over, the hardware is back to a default spectrum upon next power cycle. The hardware effect becomes "software" rather then "static". Some firmware might be smart enough to use the last hardware effect.

The trouble is, even when Windows applies the static effect, it's actually sending a different command, like "draw a frame with all LEDs green" (software) rather then "activate the static effect hardware that's green" (hardware). If you're just wanting the same settings on both, the solution might be to uninstall Razer Synapse on Windows (and I mean, make sure it's fully removed), then use OpenRazer to set the hardware effect.

Since OpenRazer daemon is a user process, it's only running as soon as you log on (on most distros). Unlike Razer Synapse which I think is a Windows driver. If you do use Razer Synapse, you could use the OpenRazer driver sysfs directly by echoing a file (as root or plugdev) during system boot up.

Equally, OpenRazer doesn't technically know what the hardware is actually doing, which is where the persistence comes in. Until Razer Synapse is removed from the equation, that particular device will reset to spectrum on next power up.

I see an issue was raised over on OpenRazer, let's continue the discussion over there: openrazer/openrazer#1807