Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: razerd Segmentation faults in Maverick

  1. #1
    Join Date
    Jun 2006
    Location
    USA
    Beans
    151
    Distro
    Kubuntu 12.04 Precise Pangolin

    Unhappy razerd Segmentation faults in Maverick

    Greetings,

    I have am using Maverick Meerkat 10.10

    Kernel version:

    2.6.35-22-generic

    I have a Razer DeathAdder gaming mouse. I am trying to compile/run this tool:

    Razer config tool

    I have jumped through several hoops:

    http://ubuntuforums.org/showthread.php?p=9876151

    This install was for 10.04.

    This link helped with taming the mouse a little:

    http://ubuntuforums.org/showthread.p...ighlight=razer

    Code:
    xinput --set-prop "Razer Razer DeathAdder" "Device Accel Constant Deceleration" 5
    Code:
    xinput --set-prop "Razer Razer DeathAdder" "Device Accel Velocity Scaling" 1

    I get the program to compile (after some problems the usb.h file not being where the system said it was) and I install it following these instructions in the README file that I have attached.

    I get a segmentation fault error when the razer daemon razerd tries to start:

    Code:
    44.202331] input: Razer Razer DeathAdder as /devices/pci0000:00/0000:00:02.1/usb1/1-4/1-4.3/1-4.3:1.0/input/input8
    [   44.202408] generic-usb 0003:1532:0016.0008: input,hidraw1: USB HID v1.11 Mouse [Razer Razer DeathAdder] on usb-0000:00:02.1-4.3/input0
    [   44.202433] razerd[2514]: segfault at 10 ip 00007fcf976a87aa sp 00007fff28b2cc80 error 4 in libc-2.12.1.so[7fcf9765f000+17a000]
    It goes w/o saying that I cannot run razercfg or qrazercfg.

    If your got this far I hope you have some suggestions for me. Please take time to follow the links I have provided before replying. They provide incite to current situation.

    Thanks

    Skaramanger
    Last edited by skaramanger; November 24th, 2010 at 12:13 AM. Reason: mistyped html code
    M2N-SLI with AMD Phenom II X4 940 8GB of 400Mhz 128bit DDR2 RAM, an Evga GTX560ti Video card Phoenix Bios Rev. 5001

    Kubuntu 12.10 (do-release-upgrade)

  2. #2
    Join Date
    Jun 2006
    Location
    USA
    Beans
    151
    Distro
    Kubuntu 12.04 Precise Pangolin

    Re: razerd Segmentation faults in Maverick

    I've also looked at this link:

    https://wiki.archlinux.org/index.php/Razer
    M2N-SLI with AMD Phenom II X4 940 8GB of 400Mhz 128bit DDR2 RAM, an Evga GTX560ti Video card Phoenix Bios Rev. 5001

    Kubuntu 12.10 (do-release-upgrade)

  3. #3
    Join Date
    Jan 2007
    Beans
    Hidden!
    Distro
    Kubuntu 11.04 Natty Narwhal

    Re: razerd Segmentation faults in Maverick

    "..(after some problems the usb.h file not being where the system said it was).."

    ...guess you edited CMakeLists.txt (line 23),to find usb.h.,
    maybe you got a wrong path there ?If so:

    ..suggest to change line 23 to:

    check_lib(usb /usr/src/linux-headers-2.6.35-22-generic/include/config/usb.h)

    and recompile the stuff,do not forget this.

    Back in a few hours....
    Last edited by realzippy; November 24th, 2010 at 02:02 PM.

  4. #4
    Join Date
    Jun 2006
    Location
    USA
    Beans
    151
    Distro
    Kubuntu 12.04 Precise Pangolin

    Re: razerd Segmentation faults in Maverick

    zippy:

    Quote Originally Posted by realzippy View Post
    "..(after some problems the usb.h file not being where the system said it was).."

    ...guess you edited CMakeLists.txt (line 23),to find usb.h.,
    maybe you got a wrong path there ?

    Exactly, but... see below

    If so:

    ..suggest to change line 23 to:

    check_lib(usb /usr/src/linux-headers-2.6.35-22-generic/include/config/usb.h)

    I attempted that and discovered that that was not where usb.h was located. Though the system thought is was at where you posted it to be. I installed libusb.dev from the repositories and it installed it here: /usr/include/usb.h So I changed line 23 to that and got it to compile with some warnings



    and recompile the stuff,do not forget this.

    Yeah I have that all setup and double checked.

    Back in a few hours....
    Here are my compile messages:

    Code:
    [~/razer]$ cmake .
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /home/xxxxx/razer
     [xxxxx~/razer]$ make
    [  0%] Generate udev rules
    Generating udev rules
    srcdir=/home/xxxxx/razer  bindir=/home/xxxxx/razer  instdir=/usr/local
    [ 11%] Built target razer_udev_rules
    [ 22%] Building C object librazer/CMakeFiles/razer.dir/librazer.o
    [ 33%] Building C object librazer/CMakeFiles/razer.dir/cypress_bootloader.o
    /home/xxxxx/razer/librazer/cypress_bootloader.c: In function ‘cypress_print_one_status’:
    /home/xxxxx/razer/librazer/cypress_bootloader.c:57: warning: format not a string literal and no format arguments
    /home/xxxxx/razer/librazer/cypress_bootloader.c: At top level:
    /home/xxxxx/razer/librazer/cypress_bootloader.c:168: warning: ‘cypress_cmd_verifyfl’ defined but not used
    [ 44%] Building C object librazer/CMakeFiles/razer.dir/hw_copperhead.o
    /home/xxxxx/razer/librazer/hw_copperhead.c: In function ‘copperhead_commit’:
    /home/xxxxx/razer/librazer/hw_copperhead.c:264: warning: unused variable ‘value’
    /home/xxxxx/razer/librazer/hw_copperhead.c: In function ‘copperhead_read_fw_ver’:
    /home/xxxxx/razer/librazer/hw_copperhead.c:250: warning: ‘err’ is used uninitialized in this function
    [ 55%] Building C object librazer/CMakeFiles/razer.dir/hw_deathadder.o
    [ 66%] Building C object librazer/CMakeFiles/razer.dir/hw_krait.o
    [ 77%] Building C object librazer/CMakeFiles/razer.dir/hw_lachesis.o
    [ 88%] Building C object librazer/CMakeFiles/razer.dir/hw_naga.o
    Linking C shared library librazer.so
    [ 88%] Built target razer
    [100%] Building C object razerd/CMakeFiles/razerd.dir/razerd.o
    Linking C executable razerd
    [100%] Built target razerd
     [~/razer]$
    Thanks for your help

    Skaramanger
    Last edited by skaramanger; November 25th, 2010 at 03:36 AM. Reason: remove misc.
    M2N-SLI with AMD Phenom II X4 940 8GB of 400Mhz 128bit DDR2 RAM, an Evga GTX560ti Video card Phoenix Bios Rev. 5001

    Kubuntu 12.10 (do-release-upgrade)

  5. #5
    Join Date
    Jan 2007
    Beans
    Hidden!
    Distro
    Kubuntu 11.04 Natty Narwhal

    Re: razerd Segmentation faults in Maverick

    That looks fine,where is the problem?(sorry,blind and tired in the moment-late here in europe-)

    sorry for stupid question:

    Have you run

    Code:
    sudo make install
    after "make" (which looks fine?)

  6. #6
    Join Date
    Jun 2006
    Location
    USA
    Beans
    151
    Distro
    Kubuntu 12.04 Precise Pangolin

    Re: razerd Segmentation faults in Maverick

    zippy,

    Yeah I ran that and no error messages came back. Only when I attempt to starte the daemon or reboot the computer I get the posted error message and a udev error that admittedly I havn't investigated yet. It scrolled by in the boot messages.

    Thanks again,

    Sleep tight,

    Skaramanger

    Quote Originally Posted by realzippy View Post
    That looks fine,where is the problem?(sorry,blind and tired in the moment-late here in europe-)

    sorry for stupid question:

    Have you run

    Code:
    sudo make install
    after "make" (which looks fine?)
    M2N-SLI with AMD Phenom II X4 940 8GB of 400Mhz 128bit DDR2 RAM, an Evga GTX560ti Video card Phoenix Bios Rev. 5001

    Kubuntu 12.10 (do-release-upgrade)

  7. #7
    Join Date
    Jan 2007
    Beans
    Hidden!
    Distro
    Kubuntu 11.04 Natty Narwhal

    Re: razerd Segmentation faults in Maverick

    That is strange.Compiled it here,exactly same "make" output,same kernel,aso,
    and "qrazercfg" starts the GUI tool (no mouse to configure,do not have a razer),screenshot attached.

    ..have you noticed (readme) the X11 chapter (..because on configuration events razerd has to temporarly unregister the mouse from the
    system
    )?And have you configured your xorg.conf that way?Note that you will only have a xorg.conf when running ATI/NVIDIA proprietary driver.Otherwise you might have to create one...



    Edit:

    "Yeah I ran that and no error messages came back.....and a udev error."
    Can you post your "make install" output?BTW,here is "mine":

    Code:
    XXXXX@xxxxx:~/razer$ sudo make install
    [sudo] password for XXXXX: 
    [  0%] Generate udev rules
    Generating udev rules
    srcdir=/home/xxxxx/razer  bindir=/home/xxxxx/razer  instdir=/usr/local
    [ 11%] Built target razer_udev_rules
    [ 88%] Built target razer
    [100%] Built target razerd
    Install the project...
    -- Install configuration: ""
    -- Installing: /usr/local/lib/librazer.so
    -- Installing: /etc/udev/rules.d/01-razer-udev.rules
    -- Installing: /usr/local/sbin/razerd
    -- Removed runtime path from "/usr/local/sbin/razerd"
    -- Installing: /usr/local/bin/pyrazer.py
    -- Installing: /usr/local/bin/razercfg
    -- Installing: /usr/local/bin/qrazercfg
    Attached Images Attached Images
    Last edited by realzippy; November 25th, 2010 at 11:13 AM.

  8. #8
    Join Date
    Mar 2007
    Beans
    1

    Re: razerd Segmentation faults in Maverick

    I also have troubles with DeathAdder in Maverick.
    Code:
    mxx@ubuntupc:~(0:57)% sudo razerd                    
    Razer device service daemon
    razer_usb_claim: first claim failed -25
    razer-deathadder: USB read 0x01 0x05 failed: -25
    hw_deathadder: Failed to get firmware version
    zsh: segmentation fault  sudo razerd
    What does it mean?

  9. #9
    Join Date
    Jun 2006
    Location
    USA
    Beans
    151
    Distro
    Kubuntu 12.04 Precise Pangolin

    Re: razerd Segmentation faults in Maverick

    Zippy,

    Whack!

    Make install:

    Code:
    [xxxxx ~/razer]$ sudo make install
    [sudo] password for xxxxx: 
    [  0%] Generate udev rules
    Generating udev rules
    srcdir=/home/xxxxxx/razer  bindir=/home/xxxxxx/razer  instdir=/usr/local
    [ 11%] Built target razer_udev_rules
    [ 22%] Building C object librazer/CMakeFiles/razer.dir/librazer.o
    [ 33%] Building C object librazer/CMakeFiles/razer.dir/cypress_bootloader.o
    /home/terryg/razer/librazer/cypress_bootloader.c: In function ‘cypress_print_one_status’:
    /home/terryg/razer/librazer/cypress_bootloader.c:57: warning: format not a string literal and no format arguments
    /home/terryg/razer/librazer/cypress_bootloader.c: At top level:
    /home/terryg/razer/librazer/cypress_bootloader.c:168: warning: ‘cypress_cmd_verifyfl’ defined but not used
    [ 44%] Building C object librazer/CMakeFiles/razer.dir/hw_copperhead.o
    /home/terryg/razer/librazer/hw_copperhead.c: In function ‘copperhead_commit’:
    /home/terryg/razer/librazer/hw_copperhead.c:264: warning: unused variable ‘value’
    /home/terryg/razer/librazer/hw_copperhead.c: In function ‘copperhead_read_fw_ver’:
    /home/terryg/razer/librazer/hw_copperhead.c:250: warning: ‘err’ is used uninitialized in this function
    [ 55%] Building C object librazer/CMakeFiles/razer.dir/hw_deathadder.o
    [ 66%] Building C object librazer/CMakeFiles/razer.dir/hw_krait.o
    [ 77%] Building C object librazer/CMakeFiles/razer.dir/hw_lachesis.o
    [ 88%] Building C object librazer/CMakeFiles/razer.dir/hw_naga.o
    Linking C shared library librazer.so
    [ 88%] Built target razer
    [100%] Building C object razerd/CMakeFiles/razerd.dir/razerd.o
    Linking C executable razerd
    [100%] Built target razerd
    Install the project...
    -- Install configuration: ""
    -- Installing: /usr/local/lib/librazer.so
    -- Installing: /etc/udev/rules.d/01-razer-udev.rules
    -- Installing: /usr/local/sbin/razerd
    -- Removed runtime path from "/usr/local/sbin/razerd"
    -- Up-to-date: /usr/local/bin/pyrazer.py
    -- Up-to-date: /usr/local/bin/razercfg
    -- Up-to-date: /usr/local/bin/qrazercfg
    Code:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig:  version 1.0  (buildmeister@builder58)  Thu Apr 22 20:35:23 PDT 2010
    
    
    Section "ServerLayout"
        Identifier     "Layout0"
        Screen      0  "Screen0" 0 0
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #    InputDevice    "Keyboard0" "CoreKeyboard"
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #    InputDevice    "Mouse0" "CorePointer"
    EndSection
    
    Section "Files"
    EndSection
    
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    Section "InputDevice"
    
        # generated from default
        Identifier     "Mouse"
        Driver         "mouse"
        Option	   "Device" "/dev/input/mice"
    
    EndSection
    
    # commented out by update-manager, HAL is now used and auto-detects devices
    # Keyboard settings are now read from /etc/default/console-setup
    #Section "InputDevice"
    #
    #    # generated from default
    #    Identifier     "Keyboard0"
    #    Driver         "kbd"
    #EndSection
    
    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "Unknown"
        HorizSync       28.0 - 33.0
        VertRefresh     43.0 - 72.0
        Option         "DPMS"
    EndSection
    
    Section "Device"
        Identifier     "Device0"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
    EndSection
    
    Section "Screen"
        Identifier     "Screen0"
        Device         "Device0"
        Monitor        "Monitor0"
        DefaultDepth    24
        SubSection     "Display"
            Depth       24
        EndSubSection
    EndSection
    Still looking through my logs trying to find the message referring to UDEV. Sorry didn't post last night holiday here in the states and I was involved in food consumption/digestion


    Found 'em

    Code:
    Nov 26 10:22:31 tz-desktop udevd[423]: SYSFS{}= will be removed in a future udev
     version, please use ATTR{}= to match the event device, or ATTRS{}= to match a 
    parent device, in /etc/udev/rules.d/01-razer-udev.rules:6

    Code:
    # UDEV rules for razer devices
    #
    # We just send a rescan command to razerd.
    # It will pick up new devices and forward information to the applications.
    
    ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="1532", RUN+="/usr/local/bin/razercfg --scan"
    ACTION=="remove", SUBSYSTEM=="usb_device", RUN+="/usr/local/bin/razercfg --scan"
    
    /etc/udev/rules.d/01-razer-udev.rules (END)


    Thanks again,

    Skaramanger
    Last edited by skaramanger; November 26th, 2010 at 05:07 PM. Reason: found udev message in syslog
    M2N-SLI with AMD Phenom II X4 940 8GB of 400Mhz 128bit DDR2 RAM, an Evga GTX560ti Video card Phoenix Bios Rev. 5001

    Kubuntu 12.10 (do-release-upgrade)

  10. #10
    Join Date
    Jun 2006
    Location
    USA
    Beans
    151
    Distro
    Kubuntu 12.04 Precise Pangolin

    Re: razerd Segmentation faults in Maverick

    mxx,

    Can you post an error message from your messages log file (>use dmesg | grep error from the commmand prompt)?

    Quote Originally Posted by mxx View Post
    I also have troubles with DeathAdder in Maverick.
    Code:
    mxx@ubuntupc:~(0:57)% sudo razerd                    
    Razer device service daemon
    razer_usb_claim: first claim failed -25
    razer-deathadder: USB read 0x01 0x05 failed: -25
    hw_deathadder: Failed to get firmware version
    zsh: segmentation fault  sudo razerd
    What does it mean?


    skaramanger
    M2N-SLI with AMD Phenom II X4 940 8GB of 400Mhz 128bit DDR2 RAM, an Evga GTX560ti Video card Phoenix Bios Rev. 5001

    Kubuntu 12.10 (do-release-upgrade)

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •