Closed ShaolinWarrior closed 6 years ago
Was looking through the comments on some other posts an ran along these steps which I had not presently done before:
git clone https://aur.archlinux.org/razer-drivers-git.git
cd razer-drivers-git
curl https://gist.githubusercontent.com/z3ntu/28cb958ce9a778de0975e54c54b77318/raw/0afe285366c35799924717b3286f460425e69bd6/PKGBUILD.nagachroma -o PKGBUILD
makepkg -sr
^^This last one wasn't working at all initially, was outputting an error: install file (razer-driver-dkms-git.install) does not exist or is not a regular file.
Ended up finding this step:
git reset --hard origin/master
Which fixed that above issue. I then ran:
sudo pacman -U python-razer-git-*.tar* razer-daemon-git-*.tar* razer-driver-dkms-git-*.tar*
Which is presently giving me the following feedback:
λ ~/razer-drivers-git/ master* sudo pacman -U python-razer-git-*.tar* razer-daemon-git-*.tar* razer-driver-dkms-git-*.tar*
zsh: no matches found: python-razer-git-*.tar*
Also, I performed the following:
λ ~/ sudo dkms remove razer_chroma_driver/1.0.0 --all
I edited the dkms.conf file at /usr/src/razer_chroma_driver-1.0.0/dkms.conf, changed this line
MAKE="KERNELDIR=/lib/modules/${kernelver}/build make driver"
to
MAKE="KERNELDIR=/lib/modules/${kernelver}/build make driver_verbose"
Then I ran
sudo dkms install razer_chroma_driver/1.0.0
Here is the output:
λ ~/ sudo dkms install razer_chroma_driver/1.0.0
Creating symlink /var/lib/dkms/razer_chroma_driver/1.0.0/source ->
/usr/src/razer_chroma_driver-1.0.0
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
KERNELDIR=/lib/modules/4.9.60-1-MANJARO/build make driver_verbose...(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.9.60-1-MANJARO (x86_64)
Consult /var/lib/dkms/razer_chroma_driver/1.0.0/build/make.log for more information.
Her is the contents of said log file:
DKMS make.log for razer_chroma_driver-1.0.0 for kernel 4.9.60-1-MANJARO (x86_64)
Wed Nov 8 10:02:47 EST 2017
make: *** No rule to make target 'driver_verbose'. Stop.
I tried runnig RazerCommander once more, but same issue as previously mentioned.
Below is a screenshot of Polychromatic working on my system, and recognizing my device.
Octopi was telling me I had some updates available so I ran
pacaur -S
After the installation of the AUR updates, it gave me a little advice and reccomended I run the following:
systemctl --user enable --now openrazer-daemon.service
Seeing as it had to do with the Razer daemon service, I figured that was wise advice and ran it.
I then ran into an error saying that a DKMS module wasn't installed, specifically -
4.9.47-1-rt37-MANJARO
(yes module, not headers)
So I installed with
sudo dkms autoinstall -k 4.9.47-1-rt37-MANJARO
Which installed without issue and without any further tips or advice from the system.
Now when I run
λ ~/ dkms status
I get the following output:
razer_chroma_driver, 1.0.0, 4.9.47-1-rt37-MANJARO, x86_64: installed
razer_chroma_driver, 1.0.0, 4.9.Tried running it verbose to see if that would give a hint to the problem, here's the output:60-1-MANJARO, x86_64: installed
So I'm thinking sweet, maybe that was the one thing I was missing, so I tried running RazerCommander, and - No luck.
So I tried running it again from the terminal with the -v argument to see a verbose log, here's the output:
λ ~/ razercommander -v
Traceback (most recent call last):
File "/usr/bin/razercommander", line 52, in <module>
from razercommander import __main__
File "/usr/lib/python3.6/site-packages/razercommander/__main__.py", line 250
print('Skipping device: %s', % device.name)
I don't understand the output myself at this moment in time, but I will keep digging into it.
try again later with the latest commit
this is probably a duplicate of #43 closing, if it's not a duplicate, please reopen it.
Still new to all of this, so please forgive me if I'm in the wrong spot, or if I'm posting the wrong information. I tried to do as much troubleshooting on my own, and, it may be that I have done everything right, but that the issue is elsewhere unrelated to this project. I'll let you be the judge of that, and hopefully we can get my issue resolved together.
Issue: Installed (what feels like everything), however I can't open the RazerCommander program to modify the side buttons on my Razer Naga Chroma. According to OpenRazer and RazerCommander, after I have installed everything, I should be able to configure my mouse - right? Maybe? Polychromatic and Razergenie both seem to be recognizing my device without issue. When I say it 'won't open, I mean exactly that. I click the icon, and it acts like it's going to open for just a moment, then it goes away. Below is my system details, installs regarding this, and logs gathered up from other people's questions - hopefully they help.
My setup:
Manjaro 17.0.6 Gellivara x86_64 Linux 4.9.60-1-MANJARO KDE 5.39.0 / Plasma 5.11.2 Razer Naga Chroma
Installed headers using:
pacman -S linux49-headers
plugdev:
sudo gpasswd -a meihua plugdev
Rebooted
Installed: Polychromatic Razercommander-git Razergenie-git
rebooted
Output of: sudo dkms install razer_chroma_driver/1.0.0
Module razer_chroma_driver/1.0.0 already installed on kernel 4.9.60-1-MANJARO/x86_64
Output of: python3 -c "from razer.client import DeviceManager; a = DeviceManager(); print(a.devices)"
Output of: sudo modprobe razermouse && lsmod | grep razer
Output of: sudo udevadm test /sys/bus/hid/devices/0:1532:0053.
Output of: openrazer-daemon -Fv
Output of: dmesg
Output of: sudo journalctl -b | grep -i razer_mount
Output of: sudo ~/.local/share/openrazer/logs/razer.log
sudo: /home/meihua/.local/share/openrazer/logs/razer.log: command not found