Menu
▾
▴
#9 No Savu found
I don't know what else to try... Here is the relevant content of my /proc/bus/input/devices :
I: Bus=0003 Vendor=1e7d Product=2d5a Version=0110
N: Name="ROCCAT ROCCAT Savu"
P: Phys=usb-0000:00:04.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb4/4-2/4-2:1.0/input/input1
U: Uniq=
H: Handlers=kbd mouse0 event1
B: PROP=0
B: EV=1f
B: KEY=4837fff072ff32d bf54444600000000 1f0001 20c100b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=1c3
B: ABS=100000000
B: MSC=10
I: Bus=0003 Vendor=1e7d Product=2d5a Version=0110
N: Name="ROCCAT ROCCAT Savu"
P: Phys=usb-0000:00:04.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb4/4-2/4-2:1.1/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=e080ffdf01cfffff fffffffffffffffe
B: MSC=10
B: LED=1f
Here is my /etc/X11/xorg.conf:
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Savu" "CorePointer"
EndSection
[snip]
Section "InputDevice"
Identifier "Savu"
Driver "evdev"
Option "Phys" "usb-0000:00:04.0-2/input0"
Option "HWHEELRelativeAxisButtons" "7 6"
EndSection
And here is what I get when I run savucontrol:
$ savucontrol
** (savucontrol:8180): CRITICAL **: No Savu found.
I tried installing the binary package from : http://debian.orson.at/ first and got this result (I run Debian sid).
I then came here and downloaded sources for roccat-tools and kmod-roccat, compiled and installed kmod-roccat using dkms. modprobe roccat does not throw errors.
I then compiled and installed roccat-tools using:
cmake -DCMAKE_INSTALL_PREFIX="/usr" -DDEVICES="savu" -DLIBDIR=$PREFIX/lib/x86_64-linux-gnu/
And no matter what I do, I still keep getting that error, but the line number keeps increasing (8180). I even tried updating the firmware, but savuupdate throws the same error.
What am I doing wrong?
Discussion
Anonymous
I've found this sitting in my dmesg:
So I added blacklist-roccat.conf to /etc/modprobe.d, ran depmod -a, rebooted, but no joy. Those messages are still sitting there.
Installing blacklist-roccat.conf is definitely needed, so the kernels own and external modules don't get mixed up.
As you did this already, try to modprobe roccat and savu. Is module roccat found and loaded without errors? (That's the module where the allegedly missing symbols are defined)
Would you please give your kernel version?
I reinstalled kmod-roccat, for the hell of it. It also provides a log of everything going on.
Notice my kernel version right there? I wonder if the "Kernel preparation" bit is normal? Or the bad exit status?
So it apparently installed.
Some checks:
I'll do a reboot now and post the results.
So after a reboot:
Does modprobe roccat and modprobe savu produce any output normally?
dmesg content (inserting all references to the mouse):
So you haven't told me about the bad exit status when dkms tries to compile the modules.
Please do the following:
Enter the folder 2.6.39_and_up in the kmod-roccat sources and execute "make"
Then you will see why compilation fails and we can work on that error.
I found this in the dump by modprobe -c:
Here is the result of make:
Looks legit to me... Maybe dkms fails internally for some reason... Things like permissions or ownership might mess it up. I'm looking into it.
/usr/src has all of the appropriate permissions and the right ownership.
I checked that the bad exit status of dkms only has to do with cleaning the build area.
Could you please execute the following commands:
find /lib/modules/3.2.0-4-amd64 -name "roccat"
lsmod | grep roccat
modprobe -c | grep roccat
Since find /lib/modules/3.2.0-4-amd64 -name "roccat" didn't yield any results, I decided to do something a bit more complete:
I seem to have a few roccat things, and a module in /sys.
That seems right to me.
I expected the blacklisted items, and the alias symbol items. I notice that there is no alis hid for savu. Why is that?
Sorry, I meant (forgot the asterisks):
find /lib/modules/3.2.0-4-amd64 -name "roccat"
And please do also:
find /lib/modules/3.2.0-4-amd64 -name "savu"
You can see no alias for kernel internal hid_roccat_savu because it's not in 3.2, but you should see one for the external compiled savu:
modprobe -c | grep savu
Both find commands yield nothing. FYI, the "" takes what's between, translates it into text and pipes it to the shell prior to command parsing. That means that
find /lib/modules/3.2.0-4-amd64 -name "roccat"
will be interpreted as
find /lib/modules/3.2.0-4-amd64 -name roccat
by the shell. The double quotes become relevant when there are some characters such as spaces, | & ! $ and the like. I mention this because I also notice you do not use the double quotes with grep (it could be used: grep "savu" the same way as find /lib/modules/3.2.0-4-amd64 -name "savu")
If you're already very familiar with shell scripting, you may disregard the previous part of the post. If you learnt something new, ask me about the difference between double quotes ("") and single quotes ('') in shell scripting.
The problem is not my understanding of quotes. The problem is sourceforges text formatting thingy that keeps deleting my asterisks. So again: I meant these commands (this time formatted so that sourceforge is happy, and you can see that I had a reason to use quotes in the first place)
Ah, much better, I see. You are right, quotes are quite needed. Here is my result:
Those kernel/drivers/hid/* things are the pre-installed kernel drivers, right? The ones being blacklisted?
Here we have a problem: You have 2 different versions of the external modules installed.
The ones in the subfolder updates/dkms are from your dkms install.
The ones in the extra subfolder come from somewhere else. Maybe you installed a package containing these?
Any better?
This is getting weirder... I went and deleted the modules in the extra folder. When I tried to rmmod roccat/savu modules, it failed saying the modules were not loaded.
Then I did this:
I then replugged my mouse, and it stopped responding: it still had power, but I could not move the cursor. Figured I might need to configure it:
So the mouse isn't detected even when both modules are loaded? To make sure, I tried removing the modules, as a second way of checking if they were loaded.
I then replugged my mouse, and I can use it once more.
Here is my dmesg starting from when I disconnected the mouse when the modules were not loaded.
The dmesg output shows that it partially worked once.
At last resort could you please do the following:
This is a bit more informative as "modprobe -c" as it has the paths in it.
If this leads to nothing I'll try to shovel free some space to install your exact distribution and try to reproduce this.
One more Idea:
You could check if and which roccat modules are in the initial ramdisk:
Create a folder, cd into it and execute the following:
What's your distribution anywhay?
I don't have time to check my initial ramdisk today, but I probably will tomorrow.
My distribution is Debian Sid (I mentionned it in my first post, I think), on an amd64.
Closed for inactivity