Failed to grab - device or resource busy

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
User avatar
Stretch
Level 2
Level 2
Posts: 76
Joined: Sun Sep 09, 2007 6:19 pm

Failed to grab - device or resource busy

Post by Stretch »

I recently upgraded to Felicia and 2.6.27-7-generic kernel. I use a Belkin Nostromo N52 Gamepad for online gaming and it has been working fine up till recently. I am now seeing the error below "failed to grab - device or resource busy".

Jan 22 17:13:23 jupiter kernel: [ 5438.340025] usb 4-2: new low speed USB device using uhci_hcd and address 9
Jan 22 17:13:23 jupiter kernel: [ 5438.516141] usb 4-2: configuration #1 chosen from 1 choice
Jan 22 17:13:23 jupiter kernel: [ 5438.535217] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb4/4-2/4-2:1.0/input/input16
Jan 22 17:13:23 jupiter kernel: [ 5438.567472] input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-2
Jan 22 17:13:46 jupiter kernel: [ 5461.120014] usb 4-1: new low speed USB device using uhci_hcd and address 10
Jan 22 17:13:46 jupiter kernel: [ 5461.297508] usb 4-1: configuration #1 chosen from 1 choice
Jan 22 17:13:46 jupiter kernel: [ 5461.315341] input: Honey Bee Nostromo SpeedPad2 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1:1.0/input/input17
Jan 22 17:13:46 jupiter kernel: [ 5461.340273] input,hidraw1: USB HID v1.10 Keyboard [Honey Bee Nostromo SpeedPad2 ] on usb-0000:00:1d.0-1
Jan 22 17:13:46 jupiter kernel: [ 5461.366376] input: Honey Bee Nostromo SpeedPad2 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1:1.1/input/input18
Jan 22 17:13:46 jupiter kernel: [ 5461.392624] input,hidraw2: USB HID v1.10 Mouse [Honey Bee Nostromo SpeedPad2 ] on usb-0000:00:1d.0-1
Jan 22 17:13:51 jupiter nostromo_daemon[7750]: Removing stale pidfile.
Jan 22 17:13:51 jupiter nostromo_daemon[7750]: Nostromo device not found.
Jan 22 17:13:51 jupiter nostromo_daemon[7750]: Couldn't find any supported devices.
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Removing stale pidfile.
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Found 050d:0815 at dev 3
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Failed to grab: Device or resource busy
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Starting reader_thread with fd=10
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Found 050d:0815 at dev 4
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Failed to grab: Device or resource busy
Jan 22 17:13:59 jupiter nostromo_daemon[7769]: Starting reader_thread with fd=11

I contacted the guy who wrote the driver software and he said:
One of the early things I had to do was add a 'grab' to the code to keep any other drivers from seeing the output from the device. It sounds like that may be failing.

Check the syslog (/var/log/messages or similar), that's where it's going to dump its logging, and if it yells about an error that's where it will be.
Thing is, I don't know where to go from here. Anyone got any ideas?

PS the keys on the keypad work ok but they can't be re-mapped as the software allows. They always show the default keymap / profile.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Husse

Re: Failed to grab - device or resource busy

Post by Husse »

This is not the same but close
http://www.linuxmint.com/forum/viewtopi ... se#p124852
Maybe you find something there
User avatar
Stretch
Level 2
Level 2
Posts: 76
Joined: Sun Sep 09, 2007 6:19 pm

Re: Failed to grab - device or resource busy

Post by Stretch »

No joy I'm afraid Husse.

The strange thing is, this worked fine for years but started failing after the recent upgrade to Mint :?

Well not just Mint, also Mandriva, so it may be a kernel / HAL issue.
Husse

Re: Failed to grab - device or resource busy

Post by Husse »

Or a HAL issue
From Intrepid/Felicia configuring of mouse etc is done in HAL although you still can use xorg.conf
Here's some info about it
https://wiki.ubuntu.com/X/Config/Input
Locked

Return to “Hardware Support”