dukla2000
Posts: 190
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: Bluetooth not working after update - information needed!

Wed Jun 22, 2016 12:42 am

hoplite wrote:Ugh. I've got bluetooth issues that don't quite match those described here, but I'll comment here anyway, in case anyone else has the same issue or can point me in the right direction.
If you are using the Pi3 onboard WiFi then get yourself a BT dongle, see my thread here.
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

hoplite
Posts: 3
Joined: Tue Jun 21, 2016 4:43 pm

Re: Bluetooth not working after update - information needed!

Wed Jun 22, 2016 9:12 pm

dukla2000 wrote:If you are using the Pi3 onboard WiFi then get yourself a BT dongle, see my thread here.
Thanks, that worked. I continued to use the onboard bluetooth but disabled the wifi and hardwired with ethernet. That stopped the bluetooth disconnections.

AlbertoDominguez
Posts: 1
Joined: Sat Jul 09, 2016 2:21 pm

Re: Bluetooth not working after update - information needed!

Sat Jul 09, 2016 2:33 pm

Hello,

I'm just got a new Raspberry Pi 3 Model B and I cannot make BT work.
  1. Clean installation (over BerryBoot). Bluetooth Activated within OpenELEC addon but Bluetooth section always display "no Bluetooth adapter found".
  2. I also installed Raspbian to check (on the same SD through BerryBoot). Bluetooth works just fine (Raspberry and Device works just fine).
  3. No messages after running bluetoothcl. Running 'list' command does not return anything. Running 'show' returns "No default controller available". Also running 'lsusb' command in terminal does not show any Bluetooth device.
  4. Not an update.
  5. Not sure how to remove Bluetooth.

User avatar
cresfang
Posts: 37
Joined: Fri Apr 29, 2016 3:03 am
Location: Garden of Time
Contact: Website

Re: Bluetooth not working after update - information needed!

Wed Jul 13, 2016 8:24 am

For me its bcoz of the ps3controller driver from RetroPie.

I noticed the bluetooth in Raspbian Jessie stopped working after I installed RetroPie with ps3controller driver.
After I removed that driver, all worked OK again.
Raspberry Pi 3

User avatar
MarkHaysHarris777
Posts: 1820
Joined: Mon Mar 23, 2015 7:39 am
Location: Rochester, MN
Contact: Website

Re: Bluetooth not working after update - information needed!

Fri Jul 15, 2016 9:09 am

Greetings:
I used the dtoverlay = pi3-disable-bt

Some time later I commented out the overlay in /boot/config.txt and rebooted. When the machine came back up the hcitool would not find the device. Also, the bluetoothctl commands (power on, scan on, &c) returned an error about the default controller not being found !

sudo hciconfig -a showed nothing.

systemctl status bluetooth showed loaded and available, but inactive dead.

pi-bluetooth showed at the latest level.

I finally tried :
sudo apt-get --reinstall install pi-bluetooth

Now, bluetoothctl works fine... all commands (power on, scan on, scan off &c)

So, I'm confused. A lot of folks are running into this... for some reason something is honking with the pi-bluetooth and killing it. Re-installing it seems to get things running, but what a pain. One minute its working, and the next its not working for any rhyme nor reason; cornfused here...

regards,
marcus
marcus
:ugeek:

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1616
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth not working after update - information needed!

Fri Jul 15, 2016 9:40 am

Interesting. I just tried including pi3-disable-bt overlay for one boot, then removing it and rebooting, and I noticed that Bluetooth didn't work after the reboot. However, a second reboot brought it back. Similarly, after the add/reboot/remove process a full shutdown followed by a hard reset won't wake Bluetooth, but a power cycle will.

It sounds like the changes made by the overlay interfere with (or tickle faults in) warm-reset in some way.

recklessfb
Posts: 37
Joined: Wed Jul 06, 2016 12:26 am

Re: Bluetooth not working after update - information needed!

Sat Aug 13, 2016 3:58 pm

I updated to the latest kernel version yesterday. Update via the rpi-update command. I have the PI 3 using the inbuild bluetooth adapter.
I'm still having issues with the bt. I successful connected and played some music to my bt speaker earlier and then I switched off the speaker and turned off bluetooth on the raspberry pi 3. Now, the bluetooth on the the rpi refuses to turn on.
My attemps to renable the bt via terminal below:
http://www.pastebin.com/PaQqNC3Y

RafaelSimionato
Posts: 3
Joined: Fri Sep 02, 2016 10:12 pm

Re: Bluetooth not working after update - information needed!

Mon Sep 05, 2016 6:47 pm

aoakley wrote:Hit this problem when updating a headless image based off Jessie Lite on a Pi3.

What worked for me to resolve it, was installing raspberrypi-sys-mods as indicated in earlier post (thanks):

> systemctl status hciuart.service
Shows failed. Also if you reboot, you see a hciuart error message during the boot-up messages.

To fix this:
> sudo apt-get install raspberrypi-sys-mods
When prompted to overwrite the config, type Y

> sudo apt-get install --reinstall pi-bluetooth
Still shows an error, let's reboot to pick up the new UART config

> sudo shutdown -r now
Note that we no longer get an hciuart error message during boot

Once rebooted, do:
> systemctl status hciuart.service
Now shows Bluetooth loaded and active (running)
In my case I got problems when installing pi-bluetooth. I needed to remove it from previous installation due other problems and got the following error when installing it again :

-------------------------------------------------------------------------------
pi@raspberrypi02:~/$ sudo apt-get install pi-bluetooth
Reading package lists... Done
...
Setting up pi-bluetooth (0.1.1) ...
Job for hciuart.service failed. See 'systemctl status hciuart.service' and 'journalctl -xn' for details.
-------------------------------------------------------------------------------


I tried it and worked! I've just added --reinstall in the first instruction as raspberrypi-sys-mods was already installed in my system :

sudo apt-get install --reinstall raspberrypi-sys-mods

And applied other steps listed by aoakley.

Tinderbox (UK)
Posts: 53
Joined: Sat Oct 08, 2016 8:56 pm
Location: England, United Kingdom

Re: Bluetooth not working after update - information needed!

Mon Oct 10, 2016 7:09 pm

I got my Pi 3 B today, downloaded and Installed the latest Noobs and selected Raspbian, the wifi and bluetooth worked straight away, But when i turn off the Bluetooth and reboot the Bluetooth enables again, this cannot be a good for security to have it running all the time.

In comparison the wifi remembers if i have enabled or disabled it without a problem.

Thanks

John.
Raspberry Pi 3 Model B

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1616
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth not working after update - information needed!

Mon Oct 10, 2016 7:30 pm

We've noticed this already, found a solution, and a fix is being packaged ready for release.

mexxle
Posts: 4
Joined: Mon Oct 17, 2016 5:09 pm

Re: Bluetooth not working after update - information needed!

Tue Oct 18, 2016 5:53 pm

Hi,
I just installed my new RPi3, everything was fine until a reboot. After the reboot the Bluetooth icon is greyed out with "no bluetooth adapter found".
I didn't update anything, it's an out of the box installation of the latest jessie image.

Whats wrong here?

scottmconnolly
Posts: 1
Joined: Thu Nov 03, 2016 7:03 pm

Re: Bluetooth not working after update - information needed!

Thu Nov 03, 2016 7:24 pm

Bluetooth works after Pixel Update. Devices are discoverable, but can not connect without using audio controls. Configuration menu gives a sound system option, PCM, but no further controls.

adityaagarwal
Posts: 2
Joined: Sun Nov 13, 2016 1:23 pm

Re: Bluetooth not working after update - information needed!

Sun Nov 13, 2016 1:34 pm

I am having some problems in creating an RFCOMM server for serial communication using Bluetooth. I am able to scan and pair with devices. But the bluetooth daemon fails to load any profiles including the serial communication profile. The output of "systemctl status -l bluetooth" is shown below. "sdptool browse local" also returns "no such file or directory found". Have tried many fixes recommended on the internet after which I was able to get the bluetoothd running but can't get it to load any profiles.

● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Sun 2016-11-13 13:20:23 UTC; 4min 59s ago
Docs: man:bluetoothd(8)
Main PID: 3792 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─3792 /usr/lib/bluetooth/bluetoothd --experimental --noplugin=sap --compat

Nov 13 13:20:23 raspberrypi bluetoothd[3792]: l2cap_bind: Address already in use (98)
Nov 13 13:20:23 raspberrypi bluetoothd[3792]: network-nap: Invalid argument (22)
Nov 13 13:20:23 raspberrypi bluetoothd[3792]: l2cap_bind: Address already in use (98)
Nov 13 13:20:23 raspberrypi bluetoothd[3792]: avrcp-controller: Protocol not supported (93)
Nov 13 13:20:23 raspberrypi bluetoothd[3792]: l2cap_bind: Address already in use (98)
Nov 13 13:20:23 raspberrypi bluetoothd[3792]: audio-avrcp-target: Protocol not supported (93)
Nov 13 13:21:19 raspberrypi bluetoothd[3792]: Endpoint registered: sender=:1.11 path=/MediaEndpoint/A2DPSource
Nov 13 13:21:19 raspberrypi bluetoothd[3792]: Endpoint registered: sender=:1.11 path=/MediaEndpoint/A2DPSink
Nov 13 13:21:19 raspberrypi bluetoothd[3792]: Endpoint unregistered: sender=:1.11 path=/MediaEndpoint/A2DPSource
Nov 13 13:21:19 raspberrypi bluetoothd[3792]: Endpoint unregistered: sender=:1.11 path=/MediaEndpoint/A2DPSink


adityaagarwal
Posts: 2
Joined: Sun Nov 13, 2016 1:23 pm

Re: Bluetooth not working after update - information needed!

Mon Nov 14, 2016 11:04 am

ExecStart=/usr/lib/bluetooth/bluetoothd -C
ExecStartPost=/usr/bin/sdptool add SP

I have tried adding the above without success. Even after adding the -C option it is not working

User avatar
Douglas6
Posts: 4306
Joined: Sat Mar 16, 2013 5:34 am
Location: Chicago, IL

Re: Bluetooth not working after update - information needed!

Mon Nov 14, 2016 3:22 pm

What happens when you

Code: Select all

sudo sdptool browse local
What are the results of

Code: Select all

systemctl status bluetooth

Steven Boelens
Posts: 53
Joined: Sat Sep 08, 2012 12:16 pm

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 5:30 pm

I have the same symptoms as mentioned by baoshi in may.

I had Wifi working some time ago. I updated and upgraded my RPi3 today to start with a new Bluetooth project and couldn't get bluetooth to work. The Wifi is also gone after the update (although I didn't test if Wifi worked directly before the update/upgrade).

I initially did this with apt-get update / upgrade / dist-upgrade but later also tried a fresh install of the Jessie image of september 2016. Both gave the same results.

In dmesg I see the error message

Code: Select all

mmc1: error -110 whilst initialising SDIO card
four times. These are the only lines mentioning mmc1 or SDIO.

bluetoothctl cannot find any devices when I try the show command, it reports "No default controller available".

I tried all the solutions that were presented here (reinstalled raspberrypi-sys-mods as well as pi-bluetooth) but with no difference. My RPi3 has the /dev/serial1 device but not the /dev/serial0 device.
Reinstalling the pi-bluetooth also gave me the error message listed in this thread before: "Job for hciuart.service failed. See 'systemctl status hciuart.service' and 'journalctl -xn' for details."

I have not modified /boot/config.txt the only line which has no comment-# is the last line in the file:

Code: Select all

dtparam=audio=on
Running the command sudo sdptool browse local:

Code: Select all

Failed to connect to SDP server on FF:FF:FF:00:00:00: No such file or directory
I looked in the raspi-config tool for the option to enable loading of the device tree but that option wasn't there. Updating the tool (from within the tool itself) gave me other options in the advanced section but no option to enable loading of the device tree in this version as well.

I have the RPi3 powered through a USB hub in my monitor, this always worked before. Just to make sure that it isn't power-related I also tried with the power supply from the RPi foundation which is listed for 2.5A. Switching to the separate power supply didn't change anything.

I think I tried all the suggestions in this thread and also in viewtopic.php?f=28&t=138629. At the end of that thread someone mentioned that his RPi3 was tested and found to be broken. I know that hardware errors are rare and this setup worked before so I think a hardware error is not likely. But I am out of suggestions for this problem.

I hope that someone has some other suggestions for fixing this problem.

Thanks in advance.
Steven.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1616
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 6:46 pm

That SDIO error suggests that WiFi/Bluetooth combo chip is failing to start, which (since you are the only(?) person complaining after the update) makes me think your power supply is inadequate.

How are you powering your Pi, and what else is attached to it?

Steven Boelens
Posts: 53
Joined: Sat Sep 08, 2012 12:16 pm

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 7:15 pm

I tried two different scenarios for the power supply. I tried with the Raspberry Pi power supply which I ordered together with the display (which isn't attached). This power supply is 2.5A. I also tried powering the RPi 3 from a USB hub in my monitor. Powering through the monitor USB hub always worked flawlessly before. But just to make absolutely sure this isn't the problem I will try another 2A power supply as well.

The only extra attachment to the Pi is a Tmp102 temperature sensor. The Pi is headless so no mouse/keyboard, only the tmp102 sensor, the ethernet cable and the power supply are connected to the Pi.

I did find a few articles that mentioned the error in the dmesg output "mmc1: error -110 whilst initialising SDIO card" but none gave a solution for my problem. The articles I found are mostly older articles from earlier this year (like when this thread started). The articles I looked at are all the articles listed at https://www.google.nl/webhp?sourceid=ch ... +raspberry.

rfkill was also mentioned as a possible cause. This rfkill is listed in the list that is displayed by lsmod. But if I ask which modules it knows about it doesn't display anything. The "rfkill list" and "rfkill list all" both show no output.

Steven Boelens
Posts: 53
Joined: Sat Sep 08, 2012 12:16 pm

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 7:22 pm

I tried a another 2A power supply with the same results.
Still the same error message "mmc1: error -110 whilst initialising SDIO card" during startup.

Code: Select all

pi@raspberrypi:~ $ dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.21-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #911 SMP Thu Sep 15 14:22:38 BST 2016
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x3a800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 241664
[    0.000000] free_area_init_node: node 0, pgdat 808c2f40, node_mem_map b9fa6000
[    0.000000]   Normal zone: 2124 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 241664 pages, LIFO batch:31
[    0.000000] [bcm2709_smp_init_cpus] enter (9520->f3003010)
[    0.000000] [bcm2709_smp_init_cpus] ncores=4
[    0.000000] PERCPU: Embedded 13 pages/cpu @b9f62000 s22592 r8192 d22464 u53248
[    0.000000] pcpu-alloc: s22592 r8192 d22464 u53248 alloc=13*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 239540
[    0.000000] Kernel command line: 8250.nr_uarts=0 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa02082 bcm2709.serial=0x8a5e49
22 smsc95xx.macaddr=B8:27:EB:5E:49:22 bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 consol
e=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 939072K/966656K available (6348K kernel code, 432K rwdata, 1716K rodata, 476K init, 764K bss, 19392K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
    lowmem  : 0x80000000 - 0xbb000000   ( 944 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x807e854c   (8066 kB)
      .init : 0x807e9000 - 0x80860000   ( 476 kB)
      .data : 0x80860000 - 0x808cc250   ( 433 kB)
       .bss : 0x808cf000 - 0x8098e1ec   ( 765 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] Architected cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000009] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000025] Switching to timer-based delay loop, resolution 52ns
[    0.000285] Console: colour dummy device 80x30
[    0.000484] console [tty1] enabled
[    0.000509] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000530] pid_max: default: 32768 minimum: 301
[    0.000839] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000853] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001784] Disabling cpuset control group subsystem
[    0.001815] Initializing cgroup subsys io
[    0.001843] Initializing cgroup subsys memory
[    0.001888] Initializing cgroup subsys devices
[    0.001908] Initializing cgroup subsys freezer
[    0.001927] Initializing cgroup subsys net_cls
[    0.001974] CPU: Testing write buffer coherency: ok
[    0.002037] ftrace: allocating 21220 entries in 63 pages
[    0.051047] CPU0: update cpu_capacity 1024
[    0.051079] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.051092] [bcm2709_smp_prepare_cpus] enter
[    0.051228] Setting up static identity map for 0x8240 - 0x8274
[    0.052844] [bcm2709_boot_secondary] cpu:1 started (0) 17
[    0.053060] [bcm2709_secondary_init] enter cpu:1
[    0.053103] CPU1: update cpu_capacity 1024
[    0.053109] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.053481] [bcm2709_boot_secondary] cpu:2 started (0) 17
[    0.053645] [bcm2709_secondary_init] enter cpu:2
[    0.053666] CPU2: update cpu_capacity 1024
[    0.053672] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.054027] [bcm2709_boot_secondary] cpu:3 started (0) 16
[    0.054158] [bcm2709_secondary_init] enter cpu:3
[    0.054178] CPU3: update cpu_capacity 1024
[    0.054184] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.054243] Brought up 4 CPUs
[    0.054267] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.054275] CPU: All CPU(s) started in HYP mode.
[    0.054282] CPU: Virtualization extensions available.
[    0.054888] devtmpfs: initialized
[    0.066015] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.066345] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.067071] pinctrl core: initialized pinctrl subsystem
[    0.067582] NET: Registered protocol family 16
[    0.072838] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[    0.079796] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.079807] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.079959] Serial: AMBA PL011 UART driver
[    0.080092] uart-pl011 3f201000.uart: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.080250] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.143156] bcm2835-dma 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0x1
[    0.143713] SCSI subsystem initialized
[    0.143901] usbcore: registered new interface driver usbfs
[    0.143991] usbcore: registered new interface driver hub
[    0.144088] usbcore: registered new device driver usb
[    0.150610] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-09-21 13:13
[    0.177817] clocksource: Switched to clocksource arch_sys_counter
[    0.222404] FS-Cache: Loaded
[    0.222671] CacheFiles: Loaded
[    0.234830] NET: Registered protocol family 2
[    0.235681] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.235795] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.235984] TCP: Hash tables configured (established 8192 bind 8192)
[    0.236076] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.236123] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.236350] NET: Registered protocol family 1
[    0.236667] RPC: Registered named UNIX socket transport module.
[    0.236677] RPC: Registered udp transport module.
[    0.236685] RPC: Registered tcp transport module.
[    0.236693] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.237782] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.239170] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.252378] VFS: Disk quotas dquot_6.6.0
[    0.252688] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.254917] FS-Cache: Netfs 'nfs' registered for caching
[    0.255817] NFS: Registering the id_resolver key type
[    0.255869] Key type id_resolver registered
[    0.255878] Key type id_legacy registered
[    0.258205] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.258358] io scheduler noop registered
[    0.258380] io scheduler deadline registered (default)
[    0.258446] io scheduler cfq registered
[    0.260998] BCM2708FB: allocated DMA memory fac00000
[    0.261024] BCM2708FB: allocated DMA channel 0 @ f3007000
[    0.269752] Console: switching to colour frame buffer device 82x26
[    1.028482] bcm2835-rng 3f104000.rng: hwrng registered
[    1.028635] vc-cma: Videocore CMA driver
[    1.028646] vc-cma: vc_cma_base      = 0x00000000
[    1.028655] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    1.028664] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    1.028884] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    1.043537] brd: module loaded
[    1.052089] loop: module loaded
[    1.052992] vchiq: vchiq_init_state: slot_zero = 0xbac80000, is_master = 0
[    1.054398] Loading iSCSI transport class v2.0-870.
[    1.055042] usbcore: registered new interface driver smsc95xx
[    1.055093] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.255363] Core Release: 2.80a
[    1.255376] Setting default values for core params
[    1.255410] Finished setting default values for core params
[    1.455773] Using Buffer DMA mode
[    1.455784] Periodic Transfer Interrupt Enhancement - disabled
[    1.455792] Multiprocessor Interrupt Enhancement - disabled
[    1.455801] OTG VER PARAM: 0, OTG VER FLAG: 0
[    1.455816] Dedicated Tx FIFOs mode
[    1.456129] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbac14000 dma = 0xfac14000 len=9024
[    1.456158] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[    1.456181] dwc_otg: Microframe scheduler enabled
[    1.456224] WARN::hcd_init_fiq:413: FIQ on core 1 at 0x80447364
[    1.456238] WARN::hcd_init_fiq:414: FIQ ASM at 0x804476d4 length 36
[    1.456251] WARN::hcd_init_fiq:439: MPHI regs_base at 0xbb9a8000
[    1.456311] dwc_otg 3f980000.usb: DWC OTG Controller
[    1.456348] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    1.456382] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    1.456432] Init: Port Power? op_state=1
[    1.456440] Init: Power Port (0)
[    1.456636] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.456651] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.456663] usb usb1: Product: DWC OTG Controller
[    1.456675] usb usb1: Manufacturer: Linux 4.4.21-v7+ dwc_otg_hcd
[    1.456687] usb usb1: SerialNumber: 3f980000.usb
[    1.457460] hub 1-0:1.0: USB hub found
[    1.457505] hub 1-0:1.0: 1 port detected
[    1.458140] dwc_otg: FIQ enabled
[    1.458149] dwc_otg: NAK holdoff enabled
[    1.458157] dwc_otg: FIQ split-transaction FSM enabled
[    1.458189] Module dwc_common_port init
[    1.458468] usbcore: registered new interface driver usb-storage
[    1.458729] mousedev: PS/2 mouse device common for all mice
[    1.459444] bcm2835-cpufreq: min=600000 max=1200000
[    1.459731] sdhci: Secure Digital Host Controller Interface driver
[    1.459740] sdhci: Copyright(c) Pierre Ossman
[    1.460062] sdhost: log_buf @ bac13000 (fac13000)
[    1.517843] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.520112] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.520125] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    1.575149] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.577410] mmc0: new high speed SDHC card at address 1234
[    1.577927] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.577978] mmcblk0: mmc0:1234 SA08G 7.42 GiB
[    1.578398] ledtrig-cpu: registered to indicate activity on CPUs
[    1.578520] hidraw: raw HID events driver (C) Jiri Kosina
[    1.578748] usbcore: registered new interface driver usbhid
[    1.578756] usbhid: USB HID core driver
[    1.579288] Initializing XFRM netlink socket
[    1.579320] NET: Registered protocol family 17
[    1.579452] Key type dns_resolver registered
[    1.579528]  mmcblk0: p1 p2
[    1.580110] Registering SWP/SWPB emulation handler
[    1.580891] registered taskstats version 1
[    1.581071] vc-sm: Videocore shared memory driver
[    1.581085] [vc_sm_connected_init]: start
[    1.582640] [vc_sm_connected_init]: end - returning 0
[    1.584951] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    1.585345] of_cfs_init
[    1.585422] of_cfs_init: OK
[    1.590765] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    1.590778] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    1.647927] Indeed it is in host mode hprt0 = 00021501
[    1.827857] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.827994] Indeed it is in host mode hprt0 = 00001101
[    2.028096] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    2.028112] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.028874] hub 1-1:1.0: USB hub found
[    2.028966] hub 1-1:1.0: 5 ports detected
[    2.307843] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.408096] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.408111] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.410824] smsc95xx v1.0.4
[    2.471137] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:5e:49:22
[    3.587840] mmc1: error -110 whilst initialising SDIO card
[    5.637836] mmc1: error -110 whilst initialising SDIO card
[    7.697837] mmc1: error -110 whilst initialising SDIO card
[    8.266792] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[    8.267085] EXT4-fs (mmcblk0p2): 1 orphan inode deleted
[    8.267096] EXT4-fs (mmcblk0p2): recovery complete
[    9.144593] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    9.144649] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    9.152781] devtmpfs: mounted
[    9.153522] Freeing unused kernel memory: 476K (807e9000 - 80860000)
[    9.434527] random: systemd: uninitialized urandom read (16 bytes read, 75 bits of entropy available)
[    9.438218] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    9.438560] systemd[1]: Detected architecture 'arm'.
[    9.552819] NET: Registered protocol family 10
[    9.554279] systemd[1]: Inserted module 'ipv6'
[    9.555996] systemd[1]: Set hostname to <raspberrypi>.
[    9.695356] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 77 bits of entropy available)
[    9.757894] mmc1: error -110 whilst initialising SDIO card
[    9.805980] random: systemd: uninitialized urandom read (16 bytes read, 78 bits of entropy available)
[    9.807244] random: systemd: uninitialized urandom read (16 bytes read, 78 bits of entropy available)
[    9.808817] random: systemd: uninitialized urandom read (16 bytes read, 78 bits of entropy available)
[    9.824106] random: systemd: uninitialized urandom read (16 bytes read, 78 bits of entropy available)
[    9.824842] random: systemd: uninitialized urandom read (16 bytes read, 78 bits of entropy available)
[    9.825011] random: systemd: uninitialized urandom read (16 bytes read, 78 bits of entropy available)
[    9.858092] random: systemd: uninitialized urandom read (16 bytes read, 79 bits of entropy available)
[    9.860864] random: systemd: uninitialized urandom read (16 bytes read, 79 bits of entropy available)
[    9.980664] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    9.981068] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    9.981146] systemd[1]: Starting Remote File Systems (Pre).
[    9.981297] systemd[1]: Reached target Remote File Systems (Pre).
[    9.981440] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    9.981908] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    9.981989] systemd[1]: Starting Encrypted Volumes.
[    9.982058] systemd[1]: Reached target Encrypted Volumes.
[    9.982141] systemd[1]: Starting Swap.
[    9.982215] systemd[1]: Reached target Swap.
[    9.982287] systemd[1]: Expecting device dev-mmcblk0p1.device...
[    9.982358] systemd[1]: Starting Root Slice.
[    9.982498] systemd[1]: Created slice Root Slice.
[    9.982567] systemd[1]: Starting User and Session Slice.
[    9.982786] systemd[1]: Created slice User and Session Slice.
[    9.982858] systemd[1]: Starting Delayed Shutdown Socket.
[    9.983019] systemd[1]: Listening on Delayed Shutdown Socket.
[    9.983088] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    9.983267] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    9.983337] systemd[1]: Starting Journal Socket (/dev/log).
[    9.983515] systemd[1]: Listening on Journal Socket (/dev/log).
[    9.983605] systemd[1]: Starting udev Control Socket.
[    9.983754] systemd[1]: Listening on udev Control Socket.
[    9.983838] systemd[1]: Starting udev Kernel Socket.
[    9.983959] systemd[1]: Listening on udev Kernel Socket.
[    9.984050] systemd[1]: Starting Journal Socket.
[    9.984261] systemd[1]: Listening on Journal Socket.
[    9.984384] systemd[1]: Starting System Slice.
[    9.984596] systemd[1]: Created slice System Slice.
[    9.984708] systemd[1]: Starting File System Check on Root Device...
[   10.018438] systemd[1]: Starting system-systemd\x2dfsck.slice.
[   10.018823] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[   10.018945] systemd[1]: Starting system-autologin.slice.
[   10.019239] systemd[1]: Created slice system-autologin.slice.
[   10.019431] systemd[1]: Starting Increase datagram queue length...
[   10.022021] systemd[1]: Starting Restore / save the current clock...
[   10.026230] systemd[1]: Mounted Huge Pages File System.
[   10.027659] systemd[1]: Starting udev Coldplug all Devices...
[   10.031006] systemd[1]: Mounting Debug File System...
[   10.055313] systemd[1]: Started Set Up Additional Binary Formats.
[   10.055754] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[   10.058901] systemd[1]: Mounting POSIX Message Queue File System...
[   10.106866] systemd[1]: Starting Load Kernel Modules...
[   10.109787] systemd[1]: Starting Slices.
[   10.109883] systemd[1]: Reached target Slices.
[   10.132764] systemd[1]: Started Create list of required static device nodes for the current kernel.
[   10.152494] systemd[1]: Starting Create Static Device Nodes in /dev...
[   10.191334] systemd[1]: Mounted POSIX Message Queue File System.
[   10.191742] systemd[1]: Mounted Debug File System.
[   10.196569] fuse init (API version 7.23)
[   10.196601] systemd[1]: Started Increase datagram queue length.
[   10.212267] systemd[1]: Started udev Coldplug all Devices.
[   10.247299] i2c /dev entries driver
[   10.256573] systemd[1]: Started Load Kernel Modules.
[   10.271859] systemd[1]: Started Restore / save the current clock.
[   10.281753] systemd[1]: Time has been changed
[   10.306671] systemd[1]: Started Create Static Device Nodes in /dev.
[   10.345310] systemd[1]: Starting udev Kernel Device Manager...
[   10.388866] systemd[1]: Mounting FUSE Control File System...
[   10.391767] systemd[1]: Mounting Configuration File System...
[   10.394380] systemd[1]: Starting Apply Kernel Variables...
[   10.397443] systemd[1]: Starting Syslog Socket.
[   10.397762] systemd[1]: Listening on Syslog Socket.
[   10.397995] systemd[1]: Starting Journal Service...
[   10.401508] systemd[1]: Started Journal Service.
[   10.416653] systemd-udevd[129]: starting version 215
[   10.878981] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[   10.931298] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[   11.135825] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   11.836758] systemd-journald[133]: Received request to flush runtime journal from PID 1
[   13.783105] uart-pl011 3f201000.uart: no DMA platform data
[   14.177057] Adding 102396k swap on /var/swap.  Priority:-1 extents:4 across:192508k SSFS
[   14.297948] cfg80211: World regulatory domain updated:
[   14.297973] cfg80211:  DFS Master region: unset
[   14.297983] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   14.297998] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   14.298010] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   14.298022] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   14.298037] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   14.298051] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   14.298067] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   14.298081] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   14.298093] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   14.870116] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   14.870322] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.361540] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   16.363015] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   18.092414] random: nonblocking pool is initialized
[   43.936194] Bluetooth: Core ver 2.21
[   43.937591] NET: Registered protocol family 31
[   43.937615] Bluetooth: HCI device and connection manager initialized
[   43.937643] Bluetooth: HCI socket layer initialized
[   43.937666] Bluetooth: L2CAP socket layer initialized
[   43.937730] Bluetooth: SCO socket layer initialized
[   43.962620] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   43.962639] Bluetooth: BNEP filters: protocol multicast
[   43.962661] Bluetooth: BNEP socket layer initialized
pi@raspberrypi:~ $ 

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1616
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 7:30 pm

Using your best supply (or all of them), can you run "vcgencmd get_throttled" shortly after booting and report the results.

Also, I notice in the log that the file system came up read-only and needing a check - is this common for you?

Steven Boelens
Posts: 53
Joined: Sat Sep 08, 2012 12:16 pm

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 7:40 pm

Code: Select all

pi@raspberrypi:~ $ vcgencmd get_throttled
throttled=0x50000
pi@raspberrypi:~ $ 
I haven't knowingly made the filesystem readonly and needing a check. I checked another RPi3 which does have working Wifi and Bluetooth and on that Pi the filesystem is also listed as "VFS: Mounted root (ext4 filesystem) readonly on device 179:2.".

The Pi with the working Wifi and Bluetooth mentions throttled=0x0.

Steven Boelens
Posts: 53
Joined: Sat Sep 08, 2012 12:16 pm

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 7:50 pm

I also tried with the 2.5A power supply:

Code: Select all

pi@raspberrypi:~ $ vcgencmd get_throttled
throttled=0x0
pi@raspberrypi:~ $ 
But also with the throttle at 0x0 the message in the dmesg still appears.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1616
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 8:07 pm

That value (0x50000) means that the Pi has been throttled (bit 16) due to undervoltage (bit 18), but that it isn't throttled now (bit 0), with no undervoltage now (bit 2). Power demands at boot time are large because systemd tries to do as much at once as possible.

If you can swap Pis, keeping everything else the same, and the failure follows the Pi, that suggests that the failing Pi is either marginal or outright faulty. High current draw could be a symptom rather than a cause of the issue.

The only other thing you could do is revert to an older image and see if the problem remains. Even if nothing relevant has changed between releases, sometimes a difference in code placement can tickle issues in a particularly slow or fast part.

You could also try core_freq=250 and arm_freq=900 to slow the cores down.

Steven Boelens
Posts: 53
Joined: Sat Sep 08, 2012 12:16 pm

Re: Bluetooth not working after update - information needed!

Sat Nov 19, 2016 8:18 pm

I did some experiments with different power supplies. The power supply which I thought was good (2A) repeatedly showed 0x50000 and sometimes 0x50005 values. So this powersupply isn't as good as I thought it was.

The 2.5A power supply which came with the RPi display (2.5A) repeatedly only shows 0x0 for the throttled value. So I will be using this power supply in the future.
With this power supply the dmesg still mentions the error -110 for the SDIO.

The RPi which has working Wifi and Bluetooth isn't easily available for swapping things out and testing various configurations.

The download page at raspberrypi.org only lists the latest Jessie image. Are older images not available anymore?

Return to “Troubleshooting”

Who is online

Users browsing this forum: Skelot, wildfire and 24 guests