Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Static not working for Razer Blade 15 Advanced (Early 2022) #1992

Closed
lah7 opened this issue Dec 28, 2022 · 20 comments
Closed

Static not working for Razer Blade 15 Advanced (Early 2022) #1992

lah7 opened this issue Dec 28, 2022 · 20 comments
Labels

Comments

@lah7
Copy link
Member

lah7 commented Dec 28, 2022

Multiple users have reported the hardware static effect does not work for Razer Blade 15 Advanced (Early 2022).

Likely the wrong command is being sent for this particular device model as the LEDs don't change.

@z3ntu
Copy link
Member

z3ntu commented Jan 9, 2023

@brian-mcnamara Do you also see this on your device?

@brian-mcnamara
Copy link
Contributor

Ill take a look.

@brian-mcnamara
Copy link
Contributor

I'm unable to replicate, was able to select static and select multiple colors.

@joemckie @Weuxel
can you send more info about the device you are on and what openrazer is reporting under "Device Info"?

@z3ntu
Copy link
Member

z3ntu commented Jan 10, 2023

Can you both send your firmware version? Should be part of polychromatic device Info I think

@Weuxel
Copy link

Weuxel commented Jan 11, 2023

Sure.

Device_Info

@brian-mcnamara
Copy link
Contributor

Thanks, looks like I only have firmware version 1.0 which appears to be the only difference. I wonder if they changed something between firmware versions. I'm also not too sure how I can get the latest firmware. Will have to look around

@z3ntu
Copy link
Member

z3ntu commented Jan 11, 2023

I'd guess for the Blades also Synapse will have the updater built-in? I think I saw someone even upgrading it with USB passthrough to a Windows VM but I can't recommend this since I tried with a Firefly mousepad and that semi-bricked it and I needed a real Windows machine to restore it.

@brian-mcnamara
Copy link
Contributor

Not that I can tell. I have my blade in a dual boot and synapse says I'm all up to date. Does not look like there is a bios update available too which is my only other idea...

@camholl
Copy link
Contributor

camholl commented Jan 30, 2023

Hi, I'm having this issue on a 2022 blade 15 base. Switching to another effect and back again works, but switching from static to a different colour does not.
No usb signals are sent to the keyboard during in the latter case, and dbus logs show the following suspicious output:

method return time=1675081797.008148 sender=:1.91 -> destination=:1.169 serial=719 reply_serial=18 signal time=1675081797.014443 sender=org.freedesktop.DBus -> destination=:1.169 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.169" signal time=1675081797.014467 sender=org.freedesktop.DBus -> destination=(null destination) serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.169" string ":1.169" string ""

Strangely, a similar output appears when switching from "breathing" to static, although in this case it seems to work:

method return time=1675081482.814051 sender=:1.91 -> destination=:1.163 serial=656 reply_serial=19 signal time=1675081482.820733 sender=org.freedesktop.DBus -> destination=:1.163 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.163" signal time=1675081482.820758 sender=org.freedesktop.DBus -> destination=(null destination) serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.163" string ":1.163" string ""

This might not be very helpful, but it's just something that I noticed.
I don't really have the knowledge to know where to begin with this one, but I'll have a look into it. In the meantime, hopefully someone with more knowledge than me can make some sense of this :)

@z3ntu
Copy link
Member

z3ntu commented Jan 30, 2023

Try systemctl --user stop openrazer-daemon.service and then run openrazer-daemon -Fv

Then try again what you've done

@brian-mcnamara
Copy link
Contributor

I just saw Razer published new firmware and bios. Interestingly enough, this now puts me on firmware version 1.2 so I completely skipped 1.1. Curious if 1.1 had issues, as I am unable to repo this after upgrading.
@Weuxel curious is updating the firmware/bios will solve the issues for you.

@Weuxel
Copy link

Weuxel commented Mar 3, 2023

@brian-mcnamara It indeed does! Thank you.

@Weuxel
Copy link

Weuxel commented Mar 3, 2023

As a little side question: Is it normal, that secure boot is enabled again after a bios update? Does Razer reset the bios settings after an update? I had virtualization turned on... that seemes to have survived.

@brian-mcnamara
Copy link
Contributor

brian-mcnamara commented Mar 3, 2023

As a little side question: Is it normal, that secure boot is enabled again after a bios update? Does Razer reset the bios settings after an update? I had virtualization turned on... that seemes to have survived.

Yes, I too experienced this. I had to disable secure boot after upgrading the bios. Glad it seems to have fixed the issue tho!

@z3ntu Seems we can close this issue with the resolution being to upgrade FW/bios.

@phealy
Copy link

phealy commented Mar 8, 2023

FYI, I think the firmware update has been pulled. Not only did it turn Secure Boot back on for me, it turned off Intel VMD (which I had configured to put my two drives in a RAID0 so I didn't have to manage the capacity separately)... and then seemingly wrote something to the EFI partition while the RAID was not configured, corrupting my RAID set.

See my reddit post for some details.

@brian-mcnamara
Copy link
Contributor

Yikes, that's not good! Glad you had a backup. I was debating going with hardware raid, but ended up wanting to play around with zfs some more. Curious if the disabling secure boot had something to do with the need to update the EFI partition, but also curious what it changed since I would assume the non-raid layout of the disk would look nothing like a EFI partition.

@phealy
Copy link

phealy commented Mar 8, 2023

Unfortunately it does look like a regular disk at first - the RAID was just doing 256kb chunks, so one of the drives had chunk 0, which contained the GPT and the partition header for EFI right at the beginning.

Interestingly that firmware update left me on 1.1 and the static display doesn't work - I worked around this for now by creating a custom scheme and just setting it static all one color :)

@phealy
Copy link

phealy commented Apr 10, 2023

Just a note that they've re-published the updates and applying them did fix this problem for me. Static now works as expected.

@z3ntu
Copy link
Member

z3ntu commented Apr 22, 2023

Can we close this issue then?

@brian-mcnamara
Copy link
Contributor

Can we close this issue then?

Yea, this issue is resolved with firmware upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

6 participants