can't install using makefile in manjaro kde #37
Comments
|
Haven't tried compiling it on |
|
Thanks! It's the kde edition of manjaro |
|
Hi, same to me. I can't install it on Manjaro (xfce). Thanks for your kind help mate! |
|
I have the same problem on Fedora 23. gcc -L../lib -rdynamic razer_daemon.do razer_daemon_dbus.do razer_daemon_effects.do razer_daemon_libraries.do razer_daemon_parameters.do razer_daemon_render_nodes.do razer_daemon_types.do -lrazer_chroma_debug -lm -ldl -o razer_bcd_debug_shared /usr/bin/ld: cannot find -lrazer_chroma_debug |
|
There is a issue with the command in the lib/Makefile (and the others that use LIBDBUS) which doesn't set the LIBDBUS flag. Ensure you have dbus headers installed. Also you'll also need the kernel-headers installed for the kernel your running (aka output of I have a pull request which fixes the command which should then work for arch. This commit openrazer/openrazer@32f607a contains the differences you need to get the Makefiles to work. Also I'm not expecting |
|
BenoitMartin2. Dont post massive errors in pull requests, its just annoying. What files are in the lib folder after you typed make |
|
Next time I'll use a paste, sry. |
|
Thanks. cd into the daemon_controller and run |
|
Same :/ |
|
Hi folks, I did the changes to the makefiles but I still get the same problem: http://pastebin.com/nq61YKj5 I am not sure if it'd help if I create that directory before doing make? @terrycain Can you give a small introduction how to start the driver and how to echo stuff to it (if it finishes compiling one day :-)). And again, if there is anyhting to help, just let me know. I really appreciate all the hard work! @BenoitMartin2 Thanks! Edit: As far as I can understand the problem is that the makefile tries to create a deamon with use of SysV but Arch based ditros only have systemd available. So the init script must be adjusted. Have a look here: |
|
@BenoitMartin2 make sure you have all the libraries installed as @Fennic said. Otherwise im not sure whats wrong. @flennic make install wont work on arch, its designed for debian. There is a daemon start script in |
|
Just do be curious: I executed ./activate_driver.sh and what I got is this: Which looks good in my eyes. If the deamon is running now, is there a way to to send commands to it like make all keys illuminated in blue or smth. like this? |
|
Unless my script is giving you false hope looks like the kernel driver is loaded. Whats the output of Best make sure the driver is actually binded before trying other things |
|
Output is: How to check if the driver is actually binded? Hell I feel like a 4 years old kid asking all those questions but I have no idea how drivers work or how close/far I am from getting it to run. I also found a folder systemd with a razer_bcd.service file. Is it possilbe if I copy all needed files manually to the correct location that it could work? |
|
Run That's fine it takes a while to tame the linux kernel and its many drivers. The daemon still needs a lot of work but you can manually operate the driver (once again ill make a wiki page to say what data the device driver files accept). |
The Wiki idea sounds really good. I really appreciate all of your hard work, sadly I can't help you that much. If I get more into this after the Wiki is up, maybe I can do some work. We will see. Just letting you know that I am really thankful. Another question is: The deamon that already exists, does it work the same way in ubuntu and arch or are there differences? Because you said it still needs a lot of work? I guess just one color-backlight would be awesome too :-) Take your time to do this and if there is paperwork to do (Wiki or somethink where your could need help), just let me know! |
|
As sudo run this "should" set the keyboard into wave mode. The wiki should be good once I've done it. The daemon works well its just not very flexible at the moment. The only issue is the differences in the layout of the filesystems between ubuntu and arch, if everything is where the daemon expect it to be it should run. |
No idea why that is. Can't really change the 0 to 1 with vim either, says sync error and that the file has been modified since opening it. One last question: I can see the ubuntu location for all of the files in the makefile. Do you have any idea where the files for systemd go? Like /etc/init.d/racer_bcd where I have to put that? Becasue as far as I can read the makefile is works well until the point where it's trying to create /etc/init.d/ files and symlinks. If we get to the point where everything is working as intended (yeah I know :D), is it hard to make a pacman package for the AUR, do you have any idea how much work that is? But anyways, that's not on the list right now. But if I am bored, I am willing to try it. Could help a lot of people. |
|
Run it as root Once I get the wiki up and running ill document everything, then feel free to make an AUR package and update the documentation to getting it working on arch |
Works now, but nothing's happening :/ |
|
What about |
Same behaviour. Works but nothing happens. FYI: https://github.com/pollonamid/razer_blackwidow_chroma_driver_arch Edit: Makes the keys glow reall really low in white. Edit2: Makes the keybord glow! 👍 Edit3: This does not work, so no colors for the moment. Edit4: Worked, my keyboard looks like a rainbow now. Other modes seem to work too. The "-n" fixed things for me. Still I can't turn of some modes (e.g. my keyboard now slowly changes colors but I can't stop it. Tried echo -n "0" to all valid files, doesn't stop). But that is better than nothing working. So for now it looks like the core driver is working. So basically the daemon needs to be at the right place for systemd and the makefile should be adjusted for arch linux systems. It should also try to install missing dependencies with pacman. I'll try around more, maybe I can find the right places and put them into a makefile so that you can have a look at that. Cheers! |
|
Yeh the mode_static takes hexadecimal. \xFF\xFF\x0 should be yellow. I'm going to write a page about the driver files. Then about what goes where on the filesystem and then about the daemon. It "migh" just work if you run The wiki is getting there. Using driver page |
|
Hey there, hexadecimal works. But therefore I have another strange thing: When I start my computer and booting into arch, the keyboard mode is set so spectrum. So somehow the driver is started instantly, even before decrypting my harddrive. How can the keybord be illuminated even before the OS booted? I thought there is no daemon running? :-) Thanks for the "Using driver page!" |
|
The keyboard illumination is at a hardware level, it'll turn on the
|
|
Okay, seems like I do not fully understand how this works. After my PC starts, which part sends the data to the keyboard? You say it's on hardware level, so which hardware is doing that? As far as I know the keyboard itself is stupid (unlike Logitech's keyboards) and is not able to save any information itself. Or is it possible it's still powered via USB and can keep the data that way? |
|
No the keyboard is not stupid. There are a few effects that the keyboard can perform itself, the driver only allows us to tell the keyboard "do this effect". The keyboard knows how to do spectrum,wave,reactive,static,none and breathing effects |
|
I'm not real sure if the keyboard can save what backlighting mode to run,
|
|
Thanks for all the information. I configured the keyboard on Mac OS X before and when I plugged it into my Linux machine it didn't show any light effects. Therefore I thought the wrong way. If you plan to develop an opensource driver, how do you know how to communicate with the keyboard? It's not like Razer is telling us how. But anyways, thats not part of this issue. |
Yes I guess so. My keyboard is illuminated blue all the time. Any way to test if the driver is binded?
What exactly do you mean with another prompt until killed? Sorry for my disability :( |
|
Returning a prompt, meaning the second |
|
Ah okay now I get the point. I didn't use Ctrl+C. It gave me the prompt back without any interaction of mine. So it means, it is NOT working as intended, right? Edit: Will retest with binded driver. One second. Edit2: Eh, I binded the driver and run the command again. Got the same behaviour except the fact that my keyboard is going to rage mode, complete random colors, weird waves and so on. Looks like my keyboard got a lsd pill. |
|
Correct. If the driver is binded then paste the output of |
|
Edit: How to turn of those colors, driving me mad o.O Edit2: Shouldn't it be just one? Edit3: Rebooted. Now static colors again, but mixed colors. |
|
in the repo, inside the daemon folder is there a file called |
Keep in mind I just restarted. So I guess the driver is unbinded. Shall I bind it again for this test? Edit: After rebinding: Keyboard went black. Edit2: |
|
Yes. Driver must be binded for this to work |
|
See edit last post. |
|
Ok I know what's happening. I'm a bit busy at the moment, I'll reply tonight/tomorrow but all hope is not lost ;). |
|
Allright :-) Take your time and thanks for all your efforts! Good night! |
|
Try rerunning If that doesn't work then run And of course post output |
Gives me back my lsd keyboard. Stops instantly -> gives me the command prompt back. Second try from the root directory looks fine. |
|
OK I am am assuming razer_bcd is installed in /usr/sbin, whats the output of What I think is the issue is that the main razer_bcd is looking for files which don't exist then just dies. One big issue which I might tackle at some point is that the daemon has no logging which isn't very helpful when your trying to troubleshoot things. |
|
|
Most strange. Make sure librazer_chroma.so is up-to-date. I would remove |
|
Hi, good new :) I installed Windows so as to play a bit AND to test my keyboard. The loaded profile on Windows remains activated switching to Linux. I use a KVM switch. |
|
I can confirm that saved profile remains across reboots, PC switches,
|
|
Nice then! I'll go set my game profiles etc. |
|
hi, I can't install on ubuntu 14.04 LTS, getting this error: razer_chroma.o: In function |
|
Path to the current directory? Command used to make |
|
I don't understand. can you help me install this driver personally? can you contact me? |
|
What is the filepath to where you checked out the repository? And what command did you run to get that output above. |
|
I'm going to post it here, because I'm betting it's related, but I can't compile on openSUSE 42.1 Leap. `\n::\033[32m COMPILING razer_bcd controller [SHARED]\033[0mgcc -L../lib -rdynamic razer_daemon_controller.o -lrazer_chroma -lrazer_chroma_controller -lm -ldl Also, I have a Blackwidow, a Firefly, an Orbweaver, a Deathstalker and a Kraken 7.1, so if you need any possible debugging info from any of those, I'll be happy to contribute. |
|
Ugh this problem appears every now and again. What's the contents of the Oooh lots of devices, yes once this works we'll get to work supporting all of them ;) |
|
Also full output of |
|
Unable to install on Fedora 24 getting the following: make -C /lib/modules/4.5.5-300.fc24.x86_64/build SUBDIRS=/home/jasonk/pez2001-razer_chroma_drivers-88eaeed/driver modules > /dev/null 2>&1 |
|
Can you please recreate the ticket on here. |
|
In the new repo that terrycain just posted there are PKGBUILDs for Arch based distros. They should work no problem in manjaro, too |
here is the output of the comand:
The text was updated successfully, but these errors were encountered: