Menu

ROCCAT Savu under Gentoo 3.12.13

Help
Max
2014-04-14
2014-04-21
1 2 > >> (Page 1 of 2)
  • Max

    Max - 2014-04-14

    Hello,

    I've been trying to get my ROCCAT Savu mouse running under Gentoo with Linux kernel 3.12.13. I really don't want to crosspost this, so I'll just link to the thread, which I've created in the Gentoo forums, where I explain my problem:
    http://forums.gentoo.org/viewtopic-t-987988.html

    As no one there seems to have a solution, I would like to know if anyone here experienced something like this?

    Thanks for any idea :)

     
  • Stefan Achatz

    Stefan Achatz - 2014-04-15

    The line

    [   13.798332] savu 0003:1E7D:2D5A.0007: timeout initializing reports
    

    is normal for the Savu and does not limit it's functionality.

    Imo no need to frickle around with X if the kernel spits out busy errors.

    If you say "The "Razer" keyboard leads the the same error, but works... ":
    Do you refer to the errors in the Xorg log or dmesg?

    You compiled your kernel multiple times. Have you tried completely without internal roccat modules, without external modules and roccat-tools uninstalled? In this case the default hid driver should catch the device. Does the Savu show the same errors in dmesg and refuses to work?

    You saying "I am far away from being an Linux expert" and using Gentoo is imo not the best combination.

     
  • Max

    Max - 2014-04-15

    I refered to the lines:

    [    2.024321] input: Razer Razer BlackWidow Ultimate 2013 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.1/input/input9
    [    2.040997] input: failed to attach handler kbd to device input9, error: -16
    [    2.045996] sysrq: Failed to open input device, error -16
    [    2.050995] input: failed to attach handler sysrq to device input9, error: -16
    

    the difference I see, is that the Razer keyboard at some point gets catched (earlier in the dmesg output...)

    I tried it without the Roccat module compiled at all. The errors stay exactly the same. And the mouse shows no sign of life anyway :(

    You saying "I am far away from being an Linux expert" and using Gentoo is imo not the best combination.

    Yes, you are right. But it is learning by doing, right? And as I wrote, I tried it several years ago (when even less experienced with Linux) and then didn't used it for a while. And I usually get along (this is the first time I was ever stuck with something so I had to ask). I mean, different distributions have (of course) different approaches and I want to try something completely different (to say Debian and Ubuntu). And if you are willing to invest some time reading documentation and know how a Linux system in general works, I didn't find it too complicated to get a for my wishes fully working Gentoo environment (apart from my favored mouse)

     
  • Stefan Achatz

    Stefan Achatz - 2014-04-15

    Now I would say it's either kernel (not my modules) and/or hardware(usb controller, not the devices) related.

    Does Gentoo have a failsave configuration for the kernel that you can use? Or is there a newer kernel available?

    Are these USB3.0 ports you stick your hid devices in? Have you tried different controllers on your board? Use lsusb to find out about your root hubs and where your devices are connected.

    The most important question to rule out the hardware: Have you used this exact hardware configuration successfully with another Linux distribution? Or Windows? If not maybe try a live-cd.

     
  • Dominique Michel

    In my make.conf file, I have the following line:

    INPUT_DEVICES="evdev roccat_koneplus synaptics"

    I think you must have something like roccat_savu, or whatever is the correct xorg input module for the Savu.

    In /etc/modprobe.d/, I have nothing for that mouse.
    Nothing either into /etc/X11/
    .*
    And CONFIG_HID_ROCCAT=m into the kernel.

     
  • Max

    Max - 2014-04-18

    Sry for the delayed response, I was busy the last two days...

    Now I would say it's either kernel (not my modules) and/or hardware(usb controller, not the devices) related.

    Yes I came to the same conclusion. Might the firmware of the Savu itself affect anything? It's updated to the newest release in this case.

    Does Gentoo have a failsave configuration for the kernel that you can use? Or is there a newer kernel available?

    Failsave boot doesn't change anything. And no, there is no newer kernel available

    Are these USB3.0 ports you stick your hid devices in? Have you tried different controllers on your board?

    No and yes. I currently use the mouse in a "power" USB 2.0 Port (these red ones, which offer a higher current afaik). But I tried nearly every single port that is available on this machine including USB 3.0 Ports. But none works.

    Have you used this exact hardware configuration successfully with another Linux distribution? Or Windows? If not maybe try a live-cd.

    I previously used exactly this hardware configuration (even port combination) successfully under Ubuntu (serveral versions), Mint and I think Debian, as well as Windows 7 and 8.1 (currently installed beside Gentoo). Everywhere the Savu works like a charm. And for good measure I tried it with a Ubuntu Live CD which I had laying around... works.

    I think you must have something like roccat_savu, or whatever is the correct xorg input module for the Savu.

    I tried, what you suggested, but also no change here :(

     
  • Stefan Achatz

    Stefan Achatz - 2014-04-18

    Then your solution would be to go back to a previous kernel version until a newer, working one is available.

     
  • Stefan Achatz

    Stefan Achatz - 2014-04-18

    Another idea: step down on compiler optimizations.

     
  • Max

    Max - 2014-04-18

    Another idea: step down on compiler optimizations.

    Tried it with -O1 and -O0, but no difference

    Then your solution would be to go back to a previous kernel version until a newer, working one is available.

    Seems like I won't stick with Gentoo. If I ever find a solution, I will post it here, but much thanks for your help :)

     
  • Dominique Michel

    It work with other Linux distributions. That imply it must work with gentoo. Distributions kernels compile most thing as modules, did you check the difference of lsmod output with gentoo and a working distribution?

    From my exprience, it is 2 things that can confuse a kernel with a working hardware, 1) some hardware work better with modules than when built-in, 2) distribution kernels can load the wrong module for a given hardware sometime.
    1) need to re-compile with modules, 2) the wrongly loaded module can be black-listed in /etc/modules.d.

     
  • Max

    Max - 2014-04-19

    It work with other Linux distributions. That imply it must work with gentoo.

    I totally agree, but I'm not sure whether I might be proven wrong.

    1) some hardware work better with modules than when built-in, 2) distribution kernels can load the wrong module for a given hardware sometime.

    I booted from a current Kubuntu Live CD and copied the loaded modules. Then I recreated it under Gentoo by configuring the kernel. Althought I seem to miss some sound related modules, everything like HID and so on is identically now (regarding lsmod).

    And again:

    [   14.880008] input: ROCCAT ROCCAT Savu as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input10
    [   14.889777] input: failed to attach handler kbd to device input10, error: -16
    [   14.894775] sysrq: Failed to open input device, error -16
    [   14.899775] input: failed to attach handler sysrq to device input10, error: -16
    [   14.899817] savu 0003:1E7D:2D5A.0007: input,hidraw6: USB HID v1.10 Keyboard [ROCCAT ROCCAT Savu] on usb-0000:00:1d.0-1.8/input1
    

    But which module would produce that output?

     
  • Max

    Max - 2014-04-19

    Oh and there is one additional thing: While Kubuntu loads nouveau I load nvidia proprietary. But I don't think this should change anything.

     
  • Stefan Achatz

    Stefan Achatz - 2014-04-19

    With optimizations I also meant support for spezial instruction stets. You could try some generic settings.

     
  • Dominique Michel

    I think it is a kernel config issue. You must double check it, especially the usb config. Can you make 2 past-it, one with your kernel config, the other with full dmesg output until the error.

     
  • Dominique Michel

    Sorry, they are linked in your gentoo post. According to dmesg, you have 3 different mouses at the same time, the kernel recognize the mouse part of the Roccat, nit not its keyboard part.

     
  • Max

    Max - 2014-04-19

    With optimizations I also meant support for spezial instruction stets. You could try some generic settings.

    Do you mean something like -mtune=generic ? I don't know very much about these gcc optimization arguments, since i've never used them. Also might the GCC version affect something (using 4.7.3 currently)?

    Can you make 2 past-it, one with your kernel config, the other with full dmesg output until the error.

    I will make another one here. I suppose this one is a bit different, since i compile much more parts as a module now:

    kernel config:
    http://bpaste.net/show/JTsOsYVFIUtDChXJ90pu/

    dmesg:
    http://bpaste.net/show/xVBSxrmBZZLYJ0wZrqXL/

     
    • Dominique Michel

      Do you mean something like -mtune=generic ?

      No don't do that. Use the flags recommended by the handbook, they are the same than the one used by the gentoo devs and are very well tested. Any other combination of flags need to do profiling on a per package basic and I know no one that have the time to do that.

      I can also put the links on your new kernel config and dmesg output on the gentoo forum. Maybe someone here will have an idea.

       
      • Dominique Michel

        Also, the kernel have its own flag optimization. And like with portage CFLAGS, just use the default if you don't know what you do.

         
        • Max

          Max - 2014-04-20

          And like with portage CFLAGS, just use the default if you don't know what you do.

          Sounds reasonable :)

          I can also put the links on your new kernel config and dmesg output on the gentoo forum. Maybe someone here will have an idea.

          We maybe should. But till now I am not really sure where the problem actual occurs, or even what the problem actually is.

           
  • Max

    Max - 2014-04-19

    According to dmesg, you have 3 different mouses at the same time, the kernel recognize the mouse part of the Roccat, nit not its keyboard part.

    I am not sure what you mean, but I read it, as if no part of the mouse is recognized correctly. And of course no device has a working handler attached, the event devices are always "busy" or produce no output...

     
    • Dominique Michel

      You get several things for the roccat.

      [ 2.052100] hub 2-1:1.0: port 8, status 0101, change 0000, 12 Mb/s
      [ 2.062973] hub 2-1:1.0: port 8 not reset yet, waiting 10ms
      [ 2.124966] usb 2-1.8: new full-speed USB device number 6 using ehci-pci
      [ 2.135962] hub 2-1:1.0: port 8 not reset yet, waiting 10ms
      [ 2.211449] usb 2-1.8: skipped 1 descriptor after interface
      [ 2.211451] usb 2-1.8: skipped 1 descriptor after interface
      [ 2.211573] usb 2-1.8: default language 0x0409
      [ 2.211823] usb 2-1.8: udev 6, busnum 2, minor = 133
      [ 2.211825] usb 2-1.8: New USB device found, idVendor=1e7d, idProduct=2d5a
      [ 2.212440] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
      [ 2.213052] usb 2-1.8: Product: ROCCAT Savu
      [ 2.213653] usb 2-1.8: Manufacturer: ROCCAT
      [ 2.214304] usb 2-1.8: usb_probe_device
      [ 2.214306] usb 2-1.8: configuration #1 chosen from 1 choice
      [ 2.214451] usb 2-1.8: adding 2-1.8:1.0 (config #1, interface 0)
      [ 2.214479] usb 2-1.8: adding 2-1.8:1.1 (config #1, interface 1)

      Later:

      [ 5.377553] input: ROCCAT ROCCAT Savu as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/input/input7
      [ 5.776302] input: failed to attach handler kbd to device input6, error: -16
      [ 5.781297] sysrq: Failed to open input device, error -16
      [ 5.786297] input: failed to attach handler sysrq to device input6, error: -16

      And:

      [ 5.799352] mousedev: PS/2 mouse device common for all mice
      [ 5.799371] savu 0003:1E7D:2D5A.0005: input,hiddev0,hidraw3: USB HID v1.10 Mouse [ROCCAT ROCCAT Savu] on usb-0000:00:1d.0-1.8/input0

      and:

      [ 15.797981] savu 0003:1E7D:2D5A.0006: timeout initializing reports
      [ 15.798018] input: ROCCAT ROCCAT Savu as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input9
      [ 15.808726] input: failed to attach handler kbd to device input9, error: -16
      [ 15.813725] sysrq: Failed to open input device, error -16
      [ 15.818725] input: failed to attach handler sysrq to device input9, error: -16
      [ 15.818766] savu 0003:1E7D:2D5A.0006: input,hidraw5: USB HID v1.10 Keyboard [ROCCAT ROCCAT Savu] on usb-0000:00:1d.0-1.8/input1

      It look like you get the mouse event on usb-0000:00:1d.0-1.8/input0 and the keyboard event on usb-0000:00:1d.0-1.8/input1

      But it is error at the pci level. I don't know what that mean. It is also a time out. Maybe you have too much debuging stuff.

       
  • Max

    Max - 2014-04-20

    Just to compare I'll post an output of Kubuntu Live-CD dmesg where the mouse works:

    http://bpaste.net/show/cuI3BMaDdPuQJCFpLTNN/

    As you can see it also prints:

    [    4.517524] usb 2-1.8: new full-speed USB device number 6 using ehci-pci
    [    4.611337] usb 2-1.8: New USB device found, idVendor=1e7d, idProduct=2d5a
    [    4.611340] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    4.611342] usb 2-1.8: Product: ROCCAT Savu
    [    4.611343] usb 2-1.8: Manufacturer: ROCCAT
    

    And later:

    [   68.291527] input: ROCCAT ROCCAT Savu as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/input/input19
    [   68.291665] savu 0003:1E7D:2D5A.0005: input,hiddev0,hidraw4: USB HID v1.10 Mouse [ROCCAT ROCCAT Savu] on usb-0000:00:1d.0-1.8/input0
    [   68.979950] usbcore: registered new interface driver snd-usb-audio
    [   78.290300] savu 0003:1E7D:2D5A.0006: timeout initializing reports
    [   78.290352] input: ROCCAT ROCCAT Savu as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input20
    [   78.290526] savu 0003:1E7D:2D5A.0006: input,hidraw5: USB HID v1.10 Keyboard [ROCCAT ROCCAT Savu] on usb-0000:00:1d.0-1.8/input1
    

    The timeout thing is not the problem. It occurs here too and as written above:

    The line
    [ 13.798332] savu 0003:1E7D:2D5A.0007: timeout initializing reports
    is normal for the Savu and does not limit it's functionality.

    Then...

    It look like you get the mouse event on usb-0000:00:1d.0-1.8/input0 and the keyboard event on usb-0000:00:1d.0-1.8/input1

    If I look at the other lines it just looks ok. But the thing is (and I think that is what the "Failed to open..." line says) that the event devices are always "busy" not only to me if I want to "cat" them, but also to the input driver/kbd handler.

    But it is error at the pci level.

    PCI drivers missing maybe?

    Maybe you have too much debuging stuff.

    Do you have a certain module in mind? I dind't activate all these Kernel hacking and debugging things, cause I don't see me debugging kernel modules :D

     
  • Dominique Michel

    One thing you can try is to made a new kernel starting with the kubuntu config (if it is like Debian, you can find it with the kernel sources or in /proc somewhere from the running kernel). For the first one, you just change the microprocessor and the graphic card to suit your need in gentoo. If the Savu work with it, you can continue by scaling it down further and removing the non need stuffs. It is how I done my first kernel it was a very long time ago.

     
  • Max

    Max - 2014-04-20

    One thing you can try is to made a new kernel starting with the kubuntu config

    I think I'll try that.

     
  • Max

    Max - 2014-04-20

    Ok thank you very much for that hint. I finally got a working Savu mouse (responding event device and no more dmesg error as far as I've tested to that point) :) Ok... to be honest nothing else works anymore, but thats just a matter of time I hope.

    In this case I started with the config of the Gentoo minimal installation CD and will now partially add support for whatever I need. The only thing is that I now have to use an initramfs to load the ext4 module which I didn't had to do before. But maybe there is another module which takes care of that, which I just don't compile for now.

    Might take a week or so since I don't have much time over the next days.

     
1 2 > >> (Page 1 of 2)

Anonymous
Anonymous

Add attachments
Cancel