Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #243184 > unrolled thread

realtek bluetooth puzzle

Back to article view | Back to linux.debian.user

Contents

  realtek bluetooth puzzle Jude DaShiell <jdashiel@panix.com> - 2021-12-16 20:10 +0100
    Re: realtek bluetooth puzzle Dan Ritter <dsr@randomstring.org> - 2021-12-16 20:20 +0100
      Re: realtek bluetooth puzzle Christian Britz <cbritz@t-online.de> - 2021-12-16 20:40 +0100
        Re: realtek bluetooth puzzle Jude DaShiell <jdashiel@panix.com> - 2021-12-16 21:20 +0100
          Re: realtek bluetooth puzzle deloptes <emanoil.kotsev@deloptes.org> - 2021-12-16 21:30 +0100
            Re: realtek bluetooth puzzle Jude DaShiell <jdashiel@panix.com> - 2021-12-16 21:50 +0100
              Re: realtek bluetooth puzzle Christian Britz <cbritz@t-online.de> - 2021-12-16 22:20 +0100
              Re: realtek bluetooth puzzle deloptes <emanoil.kotsev@deloptes.org> - 2021-12-16 22:40 +0100
                Re: realtek bluetooth puzzle Jude DaShiell <jdashiel@panix.com> - 2021-12-16 23:40 +0100
                  Re: realtek bluetooth puzzle Jude DaShiell <jdashiel@panix.com> - 2021-12-17 00:20 +0100
                  Re: realtek bluetooth puzzle deloptes <emanoil.kotsev@deloptes.org> - 2021-12-17 00:40 +0100
                    Re: realtek bluetooth puzzle Jude DaShiell <jdashiel@panix.com> - 2021-12-17 01:00 +0100
                      Re: realtek bluetooth puzzle deloptes <emanoil.kotsev@deloptes.org> - 2021-12-17 01:20 +0100

#243184 — realtek bluetooth puzzle

bnep                   20480  0
bluetooth             483328  1 bnep
ecdh_generic           16384  1 bluetooth
ecc                    40960  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?

[toc] | [next] | [standalone]

#243185

Jude DaShiell wrote: 
> bnep                   20480  0
> bluetooth             483328  1 bnep
> ecdh_generic           16384  1 bluetooth
> ecc                    40960  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-

[toc] | [prev] | [next] | [standalone]

#243187

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
>> ecc                    40960  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.)

[toc] | [prev] | [next] | [standalone]

#243190

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
> >> ecc                    40960  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.
>

[toc] | [prev] | [next] | [standalone]

#243191

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

[toc] | [prev] | [next] | [standalone]

#243194

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?
>
>

[toc] | [prev] | [next] | [standalone]

#243196

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

[toc] | [prev] | [next] | [standalone]

#243197

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

[toc] | [prev] | [next] | [standalone]

#243201

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]: <info>  [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]: <info>  [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

> >

[toc] | [prev] | [next] | [standalone]

#243205

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]: <info>  [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]: <info>  [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
>
> > >
>
>

[toc] | [prev] | [next] | [standalone]

#243207

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

[toc] | [prev] | [next] | [standalone]

#243208

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?
>
>

[toc] | [prev] | [next] | [standalone]

#243212

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web