• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 280 281 282 283 284 ... 1175 Next »

Bluetooth passthrough with Arch Linux?
View New Posts | View Today's Posts

Pages (2): 1 2 Next »
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Bluetooth passthrough with Arch Linux?
08-11-2017, 10:26 PM
#1
Youngsie97 Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Aug 2017
Hi there, just curious to see if anybody has had any success getting Bluetooth pass through working on Arch Linux?

I've done a bit of googling but came up empty so decided to post here instead.

So first up i'm using the Kinvio BTD 400 adapter I've had it working on Ubuntu and Windows but i'm not having any luck with arch .

I'm using 4.12.4-1-ARCH linux

I've set both the udev rule and dolphin.ini as follows.

Udev
SUBSYSTEM=="usb", ATTRS{idVendor}=="0A5C", ATTRS{idProduct}=="21E8", TAG+="uaccess" (I've also tried with decimal values)

Dolphin.ini
[BluetoothPassthrough]
Enabled = True
VID = 2652
PID = 8680

lsusb -v output:
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x21e8 BCM20702A0 Bluetooth 4.0
bcdDevice 1.12
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 218
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
Device Firmware Upgrade Interface Descriptor:
bLength 9
bDescriptorType 33
bmAttributes 5
Will Not Detach
Manifestation Tolerant
Upload Unsupported
Download Supported
wDetachTimeout 5000 milliseconds
wTransferSize 64 bytes
bcdDFUVersion 1.10


Input of any kind would be much appreciated thanks for your time Big Grin
Find
Reply
08-11-2017, 10:49 PM
#2
leolam Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 1,478
Threads: 5
Joined: Sep 2015
What's the error Dolphin gives you? ERROR_ACCESS? If so, that means the udev rule is not actually getting loaded so Dolphin can't access the adapter. Have you checked the Arch wiki for the proper location?
Website Find
Reply
08-11-2017, 11:01 PM
#3
Youngsie97 Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Aug 2017
(08-11-2017, 10:49 PM)leolam Wrote: What's the error Dolphin gives you? ERROR_ACCESS? If so, that means the udev rule is not actually getting loaded so Dolphin can't access the adapter. Have you checked the Arch wiki for the proper location?

I haven't actually but putting the gamecube udev rule in /etc/udev/rules.d seems to work, i'm wondering if i perhaps have the file named wrong? i went for 52-bluetooth.rules?
Find
Reply
08-11-2017, 11:03 PM
#4
leolam Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 1,478
Threads: 5
Joined: Sep 2015
That should be fine.
Website Find
Reply
08-11-2017, 11:04 PM
#5
Youngsie97 Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Aug 2017
(08-11-2017, 11:01 PM)Youngsie97 Wrote: I haven't actually but putting the gamecube udev rule in /etc/udev/rules.d seems to work, i'm wondering if i perhaps have the file named wrong? i went for 52-bluetooth.rules?

scratch this, it seems even without the rule file the gc adapter works now, so it is possible that the rules aren't being loaded. 
Find
Reply
08-11-2017, 11:07 PM
#6
Youngsie97 Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Aug 2017
(08-11-2017, 11:04 PM)Youngsie97 Wrote: scratch this, it seems even without the rule file the gc adapter works now, so it is possible that the rules aren't being loaded. 

I've checked the wiki and /etc/udev/rules.d is indeed the place the files should reside, so now i'm really stumped as to why it isn't working. I've tried udev reload udev trigger and even rebooting the system to no Avail. Thanks for the suggestion  anyhow
Find
Reply
08-11-2017, 11:56 PM
#7
leolam Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 1,478
Threads: 5
Joined: Sep 2015
Rebooting the system should be unnecessary (after all this isn't Windows Tongue), just make sure to unplug/replug after changing rules.

Anyway, have you made sure the issue is actually related to permissions? What error does Dolphin show?
Website Find
Reply
08-12-2017, 12:03 AM
#8
Youngsie97 Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Aug 2017
(08-11-2017, 11:56 PM)leolam Wrote: Rebooting the system should be unnecessary (after all this isn't Windows Tongue), just make sure to unplug/replug after changing rules.

Anyway, have you made sure the issue is actually related to permissions? What error does Dolphin show?

Failed to open Bluetooth device: LIBUSB_ERROR_ACCESS(related to udev) then no Bluetooth device found. Running dolphin as sudo removes the first error as it can obviously access stuff but then it can't find my Bluetooth adaptor as i have to force it in Dolphin.ini and i have no idea where Dolphin would store it's configs when run as sudo .

So it almost certainly looks like permission issues but i'm new enough to Linux that i don't know where in the chain i need to fix it.  
Find
Reply
08-12-2017, 02:29 AM
#9
Youngsie97 Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Aug 2017
Not the best way by far and i would love to fix the issue properly but for the mean time i've found a work around is to run sudo dolphin-emu -u folder then just edit the ini in that folder bluetooth passthrough is now working flawlessly,

for now i've got an alias Dolphin for sudo dolphin-emu -u dolphinconfig

this is obviously not the best way as it is the inpropper way to do things but allows me to play Kirby epic yarn
Find
Reply
09-14-2017, 04:05 PM
#10
CuriousTommy Offline
Junior Member
**
Posts: 27
Threads: 6
Joined: Apr 2014
(08-12-2017, 02:29 AM)Youngsie97 Wrote: Not the best way by far and i would love to fix the issue properly but for the mean time i've found a work around is to run sudo dolphin-emu -u folder then just edit the ini in that folder bluetooth passthrough is now working flawlessly,

for now i've got an alias Dolphin for sudo dolphin-emu -u dolphinconfig

this is obviously not the best way as it is the inpropper way to do things but allows me to play Kirby epic yarn

If anyone else is running into this problem, I figured out how to get it to work. I put the udev rule in /usr/lib/udev/rules.d/51-usb-device.rules and I was able to use the USB passthrough feature!
Find
Reply
« Next Oldest | Next Newest »
Pages (2): 1 2 Next »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode