Re: realtek bluetooth puzzle
On Jo, 16 dec 21, 23:30:37, Thomas Schmitt wrote: > Hi, > > Jude DaShiell wrote: > > [10200.545324] usb 3-1: Product: DISK > > [10200.545329] usb 3-1: Manufacturer: Realtek > > [10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected > > [10200.546006] scsi host6: usb-storage 3-1:1.0 > > [10201.560487] scsi 6:0:0:0: CD-ROMRealtek Driver Storage 1.00 > > PQ: 0 ANSI: 0 CCS > > [10201.566607] sr 6:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy > > [10201.588298] sr 6:0:0:0: Attached scsi CD-ROM sr1 > > Looks like the device is emulating a CD-ROM which offers driver files > to MS-Windows for automatic installation. The web says that this happens > when the device does not get the right answers from the operating system > which indicate that the drivers are already installed. Indeed it does look like it. > An Archlinux thread proposes to use a program named usb_modeswitch to get > the device out of this mode > https://bbs.archlinux.org/viewtopic.php?id=228195 > Debian has it in a package > https://tracker.debian.org/pkg/usb-modeswitch > > I find its home page somehow confusing > https://www.draisberghof.de/usb_modeswitch/ > But the web says that it is supposed to work automagically for known > devices. In most cases a simple 'eject' command is sufficient, so based on the above something like this might do it: eject /dev/sr1 The command `eject` is in the package with the same name. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: realtek bluetooth puzzle
Jude DaShiell wrote: > I have firmware-realtek installed for wireless devices and that's all > debian offers. but sometime if it is a new device on the market you may need either to wait for the firmware to go to the package or you can download from vendor or you can extract from the windows package Anyway - by price of BT USB dongles around 12,- it is perhaps worth to return and find a supported one Before doing this perhaps try on another linux if available -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: realtek bluetooth puzzle
Jude DaShiell wrote: > hcitool and rfkill list showed nothing, according to them the device isn't > there yet. I might be able to get this going with usb_modeswitch but need > a product identifier and another item to do that. based on the product name, find what is the chip inside and ask google -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: realtek bluetooth puzzle
I have firmware-realtek installed for wireless devices and that's all debian offers. On Fri, 17 Dec 2021, deloptes wrote: > Thomas Schmitt wrote: > > > I find its home page somehow confusing > > https://www.draisberghof.de/usb_modeswitch/ > > But the web says that it is supposed to work automagically for known > > devices. > > may be OP is needing the firmware and this mode is a fallout mode. It is > strange if it would need usb_modeswitch. > Also it is strange that it does not try anything else first. > >
Re: realtek bluetooth puzzle
hcitool and rfkill list showed nothing, according to them the device isn't there yet. I might be able to get this going with usb_modeswitch but need a product identifier and another item to do that. On Fri, 17 Dec 2021, deloptes wrote: > Jude DaShiell wrote: > > > Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth > > service being skipped. > > Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service > > 'org.bluez': timed out (service_start_timeout=25000ms) > > Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22 > > Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager > > initialized > > Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized > > Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized > > Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized > > it says it can not start bluetooth, but HCI device and connection manager > initialized, so what does hcitool said? > and why is pulseaudio involved - perhaps you need > pulseaudio-module-bluetooth and reboot to be sure it all setup properly > > also what said rfkill? > >
Re: realtek bluetooth puzzle
Jude DaShiell wrote: > Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth > service being skipped. > Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service > 'org.bluez': timed out (service_start_timeout=25000ms) > Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22 > Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager > initialized > Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized > Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized > Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized it says it can not start bluetooth, but HCI device and connection manager initialized, so what does hcitool said? and why is pulseaudio involved - perhaps you need pulseaudio-module-bluetooth and reboot to be sure it all setup properly also what said rfkill? -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: realtek bluetooth puzzle
Thomas Schmitt wrote: > I find its home page somehow confusing > https://www.draisberghof.de/usb_modeswitch/ > But the web says that it is supposed to work automagically for known > devices. may be OP is needing the firmware and this mode is a fallout mode. It is strange if it would need usb_modeswitch. Also it is strange that it does not try anything else first. -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: realtek bluetooth puzzle
firmware-realtek has been installed a while ago. I'm probably going to have to run usb-modeswitch against the device. On Thu, 16 Dec 2021, Jude DaShiell wrote: > > > On Thu, 16 Dec 2021, deloptes wrote: > > > Jude DaShiell wrote: > > > > > No Linux firmware came on the disk only windows files. To that extent I > > > checked. On debian does a way exist to check devices for missing > > > firmware? > > > > > > > in the log file journalctl or /var/log/syslog, after plugging in the usb (I > > am not sure if it is usb stick, because you mentioned card, but anywa) > > When bluetooth initializes you should see if it is looking for firmware and > > in your case not loading it. > > > > It could be that you have to install linux firmware packages free or not > > free (depends on the chip you have on the device) > > > > You could also check output of command rfkill list and see if hci0 device > > exists and is blocked > > > > The other thing use hcitool command (hcitool dev) and see if it shows hci > > device - I have seen some cases that hciattach needs to be run to enable > > the device. > Does any of this make sense? This is journalctl output: > 16:56:28 taf bluetoothd[1157]: Starting SDP server > Dec 16 16:56:28 taf bluetoothd[1157]: Bluetooth management interface 1.18 > initialized > Dec 16 16:56:40 taf bluetoothd[1157]: Terminating > Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0 > matched rules; type="error", sender=":1.9" (uid=1000 pid=817 > comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") > interface="(unset)" member="(unset)" error > name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" > destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ") > Dec 16 16:56:40 taf bluetoothd[1157]: Stopping SDP server > Dec 16 16:56:40 taf bluetoothd[1157]: Exit > Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0 > matched rules; type="error", sender=":1.9" (uid=1000 pid=817 > comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") > interface="(unset)" member="(unset)" error > name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" > destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ") > Dec 16 17:07:06 taf NetworkManager[1764]: [1639692426.3763] > Loaded device plugin: NMBluezManager > (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so) > Dec 16 17:09:50 taf NetworkManager[476]: [1639692590.3550] Loaded > device plugin: NMBluezManager > (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so) > Dec 16 17:10:08 taf dbus-daemon[475]: [system] Activating via systemd: > service name='org.bluez' unit='dbus-org.bluez.service' requested by > ':1.15' (uid=1000 pid=868 comm="/usr/bin/pulseaudio --daemonize=no > --log-target=jo") > Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth > service being skipped. > Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service > 'org.bluez': timed out (service_start_timeout=25000ms) > Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22 > Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager > initialized > Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized > Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized > Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized > > > > > >
Re: realtek bluetooth puzzle
On Thu, 16 Dec 2021, deloptes wrote: > Jude DaShiell wrote: > > > No Linux firmware came on the disk only windows files. To that extent I > > checked. On debian does a way exist to check devices for missing > > firmware? > > > > in the log file journalctl or /var/log/syslog, after plugging in the usb (I > am not sure if it is usb stick, because you mentioned card, but anywa) > When bluetooth initializes you should see if it is looking for firmware and > in your case not loading it. > > It could be that you have to install linux firmware packages free or not > free (depends on the chip you have on the device) > > You could also check output of command rfkill list and see if hci0 device > exists and is blocked > > The other thing use hcitool command (hcitool dev) and see if it shows hci > device - I have seen some cases that hciattach needs to be run to enable > the device. Does any of this make sense? This is journalctl output: 16:56:28 taf bluetoothd[1157]: Starting SDP server Dec 16 16:56:28 taf bluetoothd[1157]: Bluetooth management interface 1.18 initialized Dec 16 16:56:40 taf bluetoothd[1157]: Terminating Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.9" (uid=1000 pid=817 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ") Dec 16 16:56:40 taf bluetoothd[1157]: Stopping SDP server Dec 16 16:56:40 taf bluetoothd[1157]: Exit Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.9" (uid=1000 pid=817 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ") Dec 16 17:07:06 taf NetworkManager[1764]: [1639692426.3763] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so) Dec 16 17:09:50 taf NetworkManager[476]: [1639692590.3550] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so) Dec 16 17:10:08 taf dbus-daemon[475]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.15' (uid=1000 pid=868 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth service being skipped. Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22 Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager initialized Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized > >
Re: realtek bluetooth puzzle
Hi, Jude DaShiell wrote: > [10200.545324] usb 3-1: Product: DISK > [10200.545329] usb 3-1: Manufacturer: Realtek > [10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected > [10200.546006] scsi host6: usb-storage 3-1:1.0 > [10201.560487] scsi 6:0:0:0: CD-ROMRealtek Driver Storage 1.00 > PQ: 0 ANSI: 0 CCS > [10201.566607] sr 6:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy > [10201.588298] sr 6:0:0:0: Attached scsi CD-ROM sr1 Looks like the device is emulating a CD-ROM which offers driver files to MS-Windows for automatic installation. The web says that this happens when the device does not get the right answers from the operating system which indicate that the drivers are already installed. An Archlinux thread proposes to use a program named usb_modeswitch to get the device out of this mode https://bbs.archlinux.org/viewtopic.php?id=228195 Debian has it in a package https://tracker.debian.org/pkg/usb-modeswitch I find its home page somehow confusing https://www.draisberghof.de/usb_modeswitch/ But the web says that it is supposed to work automagically for known devices. Have a nice day :) Thomas
re: realtek bluetooth puzzle
Havbing removed the device I ran dmesg| wc -l. Inserting the device I ran dmesg| wc -l again and got a difference of 11 lines. So dmesg >dmesg.log and tail -11 dmesg.log got me this information. [10200.545324] usb 3-1: Product: DISK [10200.545329] usb 3-1: Manufacturer: Realtek [10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected [10200.546006] scsi host6: usb-storage 3-1:1.0 [10201.560487] scsi 6:0:0:0: CD-ROMRealtek Driver Storage 1.00 PQ: 0 ANSI: 0 CCS [10201.566607] sr 6:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy [10201.588298] sr 6:0:0:0: Attached scsi CD-ROM sr1 [10201.721911] usb 3-1: reset high-speed USB device number 6 using ehci-pci [10232.215266] usb 3-1: reset high-speed USB device number 6 using ehci-pci [10262.935626] usb 3-1: reset high-speed USB device number 6 using ehci-pci [10293.655994] usb 3-1: reset high-speed USB device number 6 using ehci-pci
Re: realtek bluetooth puzzle
Jude DaShiell wrote: > No Linux firmware came on the disk only windows files. To that extent I > checked. On debian does a way exist to check devices for missing > firmware? > in the log file journalctl or /var/log/syslog, after plugging in the usb (I am not sure if it is usb stick, because you mentioned card, but anywa) When bluetooth initializes you should see if it is looking for firmware and in your case not loading it. It could be that you have to install linux firmware packages free or not free (depends on the chip you have on the device) You could also check output of command rfkill list and see if hci0 device exists and is blocked The other thing use hcitool command (hcitool dev) and see if it shows hci device - I have seen some cases that hciattach needs to be run to enable the device. -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: realtek bluetooth puzzle
On 2021-12-16 21:45 UTC+0100, Jude DaShiell wrote: > No Linux firmware came on the disk only windows files. To that extent I > checked. On debian does a way exist to check devices for missing > firmware? > > > On Thu, 16 Dec 2021, deloptes wrote: > >> Jude DaShiell wrote: >> >>> So in reality this may actually not be a card >>> The disk that came with this claimed it was an realtek-0179 device if >>> memory serves. >> >> did you check firmware if required - do you have it installed? >> >> > You might have to install some non-free firmware from Debian repository. If it is not yet enabled, edit file /etc/apt/sources.list and edit the lines to look similar like "deb http://deb.debian.org/debian/ bullseye main non-free contrib" Then run "apt update". Then install the needed firmware package. Of course the difficulty is to find out which package you need. A search for realtek-0179 brings no usefull results on Google. It is strange that neither lsusb nor lspci bring up usefull information. If it is an USB device, unplug and plug it in again and watch the output of dmesg for messages. If it tells you firmware file "ExampleFileName" is missing then issue command "apt-file search ExampleFileName". It should tell you, which package to install. Regards, Christian
Re: realtek bluetooth puzzle
No Linux firmware came on the disk only windows files. To that extent I checked. On debian does a way exist to check devices for missing firmware? On Thu, 16 Dec 2021, deloptes wrote: > Jude DaShiell wrote: > > > So in reality this may actually not be a card > > The disk that came with this claimed it was an realtek-0179 device if > > memory serves. > > did you check firmware if required - do you have it installed? > >
Re: realtek bluetooth puzzle
Jude DaShiell wrote: > So in reality this may actually not be a card > The disk that came with this claimed it was an realtek-0179 device if > memory serves. did you check firmware if required - do you have it installed? -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: realtek bluetooth puzzle
On Thu, 16 Dec 2021, Christian Britz wrote: > > > On 2021-12-16 20:01 UTC+0100, Dan Ritter wrote: > > Jude DaShiell wrote: > >> bnep 20480 0 > >> bluetooth 483328 1 bnep > >> ecdh_generic 16384 1 bluetooth > >> ecc40960 1 ecdh_generic > >> > >> That's relevant output from lsmod. > >> If I run inxi -E > >> that returns no bluetooth data available. > >> This is supposed to be linux-compatible. > >> Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after > >> starting bluetooth adapters gets me nowhere. > >> Has anyone got one of these cards from WalMart going and can give me some > >> ideas for getting this up and working or find out if it can't work so I > >> can trash it and buy a different card from WalMart? > > > > Anything interesting in lsusb? > > > > -dsr- > > > > Or in the syslog? > (If it is really a "card", Jude should issue lspci.) > I ran lspci and no mention of bluetooth happened. dmesg.log output returned: [ 402.931062] Bluetooth: Core ver 2.22 [ 402.931086] NET: Registered PF_BLUETOOTH protocol family [ 402.931088] Bluetooth: HCI device and connection manager initialized [ 402.931092] Bluetooth: HCI socket layer initialized [ 402.931094] Bluetooth: L2CAP socket layer initialized [ 402.931098] Bluetooth: SCO socket layer initialized [ 402.942727] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 402.942733] Bluetooth: BNEP filters: protocol multicast [ 402.942741] Bluetooth: BNEP socket layer initialized So in reality this may actually not be a card The disk that came with this claimed it was an realtek-0179 device if memory serves. The Linux instructions were in an .mp4 file that was inaudible on my system. >
Re: realtek bluetooth puzzle
On Thu, 16 Dec 2021, Dan Ritter wrote: > Jude DaShiell wrote: > > bnep 20480 0 > > bluetooth 483328 1 bnep > > ecdh_generic 16384 1 bluetooth > > ecc40960 1 ecdh_generic > > > > That's relevant output from lsmod. > > If I run inxi -E > > that returns no bluetooth data available. > > This is supposed to be linux-compatible. > > Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after > > starting bluetooth adapters gets me nowhere. > > Has anyone got one of these cards from WalMart going and can give me some > > ideas for getting this up and working or find out if it can't work so I > > can trash it and buy a different card from WalMart? > > Anything interesting in lsusb? > > -dsr- > file: lsbusb.orig Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice5.14 iManufacturer 3 Linux 5.14.14 ehci_hcd iProduct2 EHCI Host Controller iSerial 1 :00:16.2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 4 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0100 power Port 2: .0100 power Port 3: .0100 power Port 4: .0100 power Device Status: 0x0001 Self Powered Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice5.14 iManufacturer 3 Linux 5.14.14 ohci_hcd iProduct2 OHCI PCI host controller iSerial 1 :00:16.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 4 wHubCharacteristic 0x0009 Per-port power switching Per-port overcurrent protection bPwrOn2PwrGood2 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0100 power Port 2: .0100 power Port 3: .0100 power Port 4: .0100 power Device Status:
Re: realtek bluetooth puzzle
On 2021-12-16 20:01 UTC+0100, Dan Ritter wrote: > Jude DaShiell wrote: >> bnep 20480 0 >> bluetooth 483328 1 bnep >> ecdh_generic 16384 1 bluetooth >> ecc40960 1 ecdh_generic >> >> That's relevant output from lsmod. >> If I run inxi -E >> that returns no bluetooth data available. >> This is supposed to be linux-compatible. >> Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after >> starting bluetooth adapters gets me nowhere. >> Has anyone got one of these cards from WalMart going and can give me some >> ideas for getting this up and working or find out if it can't work so I >> can trash it and buy a different card from WalMart? > > Anything interesting in lsusb? > > -dsr- > Or in the syslog? (If it is really a "card", Jude should issue lspci.)
Re: realtek bluetooth puzzle
Jude DaShiell wrote: > bnep 20480 0 > bluetooth 483328 1 bnep > ecdh_generic 16384 1 bluetooth > ecc40960 1 ecdh_generic > > That's relevant output from lsmod. > If I run inxi -E > that returns no bluetooth data available. > This is supposed to be linux-compatible. > Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after > starting bluetooth adapters gets me nowhere. > Has anyone got one of these cards from WalMart going and can give me some > ideas for getting this up and working or find out if it can't work so I > can trash it and buy a different card from WalMart? Anything interesting in lsusb? -dsr-
realtek bluetooth puzzle
bnep 20480 0 bluetooth 483328 1 bnep ecdh_generic 16384 1 bluetooth ecc40960 1 ecdh_generic That's relevant output from lsmod. If I run inxi -E that returns no bluetooth data available. This is supposed to be linux-compatible. Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after starting bluetooth adapters gets me nowhere. Has anyone got one of these cards from WalMart going and can give me some ideas for getting this up and working or find out if it can't work so I can trash it and buy a different card from WalMart?
