razer-laptop-control
razer-laptop-control copied to clipboard
[BUG] Socket doesn't exit. Is daemon running?
Describe the bug I reinstalled package and reboot system but it's not working
> razer-cli read
Error. Socket doesn't exit. Is daemon running?
To Reproduce
- install razer-laptop-control-dkms-git 1.3.0.r14.g1d2f26e-1
- install razer-laptop-control-git 1.3.0.r14.g1d2f26e-1
- run razer-cli read or razer-cli --help
Expected behavior The command works without errors.
System information Model of my laptop: Razer Blade Stealth 13 RZ09-03272E12-R3U1
> sudo dmidecode | grep -A3 '^System Information'
System Information
Manufacturer: Razer
Product Name: Blade Stealth 13 (Late 2020) - RZ09-0327
Version: 0.04
> uname -a
Linux alexandr-pc 5.13.8-1-MANJARO #1 SMP PREEMPT Thu Aug 5 09:47:52 UTC 2021 x86_64 GNU/Linux
> cat /etc/os-release
AME="Manjaro Linux"
ID=manjaro
ID_LIKE=arch
BUILD_ID=rolling
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="32;1;24;144;200"
HOME_URL="https://manjaro.org/"
DOCUMENTATION_URL="https://wiki.manjaro.org/"
SUPPORT_URL="https://manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
LOGO=manjarolinux
> lsusb | grep Razer
Bus 003 Device 003: ID 1532:0259 Razer USA, Ltd Razer Blade
> lsmod | grep razer
> sudo dmesg | grep razer
[ 1.094793] systemd[1]: Configuration file /etc/systemd/system/razerdaemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.
[ 31.714816] audit: type=1131 audit(1629095642.929:82): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=razerdaemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 412.698048] audit: type=1130 audit(1629096044.810:90): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=razerdaemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 442.706446] audit: type=1131 audit(1629096074.820:91): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=razerdaemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 481.617436] audit: type=1131 audit(1629096113.730:119): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=razerdaemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 663.568833] audit: type=1130 audit(1629096295.678:148): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=razerdaemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 693.576355] audit: type=1131 audit(1629096325.685:149): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=razerdaemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
> sudo systemctl status razerdaemon.service
razerdaemon.service - Razer laptop control daemon
Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2021-08-16 11:45:25 +05; 57min ago
Process: 3289 ExecStart=/usr/share/razercontrol/daemon (code=exited, status=1/FAILURE)
Main PID: 3289 (code=exited, status=1/FAILURE)
CPU: 3ms
Aug 16 11:45:18 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:19 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:20 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:21 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:22 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:23 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:24 alexandr-pc daemon[3289]: Waiting for sysfs to be ready
Aug 16 11:45:25 alexandr-pc daemon[3289]: Timed out waiting for sysfs after a minute!
Aug 16 11:45:25 alexandr-pc systemd[1]: razerdaemon.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 11:45:25 alexandr-pc systemd[1]: razerdaemon.service: Failed with result 'exit-code'.
Hi, did you solve the issue? I assume it caused by inappropriate instalation
Hi, did you solve the issue? I assume it caused by inappropriate instalation
Hi. No
@SalyczeQ Do you known as I can my problem?
Have you checked if dkms driver is builded?
You need to make sure the daemon is running. You can try starting it with sudo systemctl start razerdaemon
or by directly running /usr/share/razercontrol/daemon
Getting the same issue. razerdaemon
service will start but after 30 seconds or so will crash:
sudo systemctl status razerdaemon ✔ 2.7.5
× razerdaemon.service - Razer laptop control daemon
Loaded: loaded (/etc/systemd/system/razerdaemon.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2022-02-20 20:38:59 EST; 29s ago
Process: 3430 ExecStart=/usr/share/razercontrol/daemon (code=exited, status=1/FAILURE)
Main PID: 3430 (code=exited, status=1/FAILURE)
CPU: 4ms
Feb 20 20:38:52 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:53 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:54 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:55 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:56 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:57 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:58 sam-blade daemon[3430]: Waiting for sysfs to be ready
Feb 20 20:38:59 sam-blade daemon[3430]: Timed out waiting for sysfs after a minute!
Feb 20 20:38:59 sam-blade systemd[1]: razerdaemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 20 20:38:59 sam-blade systemd[1]: razerdaemon.service: Failed with result 'exit-code'.
journalctl
gives the following as the full log output of the service before it crashes. Happy to provide any other logs if you tell me where to look:
sudo journalctl -u razerdaemon.service 3 ✘ 2.7.5
Feb 20 20:17:56 sam-blade systemd[1]: Started Razer laptop control daemon.
Feb 20 20:17:56 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:17:57 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:17:58 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:17:59 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:00 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:01 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:02 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:03 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:04 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:05 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:06 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:07 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:08 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:09 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:10 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:11 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:12 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:13 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:14 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:15 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:16 sam-blade daemon[28205]: Waiting for sysfs to be ready
Feb 20 20:18:17 sam-blade daemon[28205]: Waiting for sysfs to be ready
This is on a Razer Blade Stealth 2021 edition running Manjaro
I fixed it by uninstalling it, and then compiling it myself (See issue #56 for a guide, it really isn't complicated, but you need to replace sudo update-initramfs -u
with sudo mkinitcpio
if you are running Arch (or maybe on other Distros as well, but I only know that you need to replace it in arch since I am using Arch)
EDIT: I had the problem where it waits for sysfs