[Asus N550JV] Bluetooth not working initially

[alperyilmaz]

Initially bluetooth doesn't work. "rfkill list" either shows bluetooth is soft blocked, or unblocked. If it boots unblocked, it does not work.

WORKAROUND: Only if it is soft blocked "sudo rfkill unblock bluetooth" and I was able to pair a bluetooth mouse and the connection was persistent (not sporadic). I even tried this; I paired a tablet and streamed audio from tablet to my laptop.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-7-generic 3.13.0-7.25
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 2609 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 2609 F.... pulseaudio
CasperVersion: 1.337
CurrentDesktop: Unity
Date: Fri Feb 7 16:12:13 2014
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140205)
MachineType: ASUSTeK COMPUTER INC. N550JV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-7-generic N/A
 linux-backports-modules-3.13.0-7-generic N/A
 linux-firmware 1.123
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/17/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N550JV.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N550JV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.207:bd09/17/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N550JV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

This bug was opened against Trusty, which is the current development release. If this bug is already fixed, then it should be marked as "Fix Released".

[alperyilmaz (alperyilmaz)]

Hi Christopher,

I did reboot to live USB couple times and I cannot confirm that bluetooth
was "soft blocked each time".
Two times, it was soft blocked and after unblocking it, everything worked
fine. But two times, it was -not- blocked, however I was not able to make
bluetooth work no matter what I tried.
So, if it's soft blocked, it works after unblocking.. But, if it's
unblocked initially, it does not work (maybe it does not recognize the
device or adapter, and that's why it's not blocked)..

I hope my information helps. If there are more tests or debugging you want
me to do, I'll be more than happy to contribute.

Thanks,
alper

On Fri, Feb 14, 2014 at 8:19 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> alperyilmaz, just to clarify your Bug Description, upon every fresh boot
> the bluetooth is always soft blocked as per rfkill list?
>
> ** Description changed:
>
> - This test was requested by developers as a followup to
> - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260825
> -
> - The bug was filed by fuujuhi and the user did the upstream kernel test
> -
> - The latest development release test was remaining. I ran Ubuntu Daily
> build as live USB. And tested the bluetooth problem.
> - Initially bluetooth didn't work. When I ran "rfkill list" I noticed that
> bluetooth was soft blocked. Then I ran the command "sudo rfkill unblock
> bluetooth" and everything worked fine. I was able to pair a bluetooth mouse
> and the connection was persistent (not sporadic). I even tried this; I
> paired a tablet and streamed audio from tablet to my laptop.
> - So, this bug is fixed in development release of Ubuntu.
> -
> -
> - $ uname -a
> - Linux ubuntu 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014
> x86_64 x86_64 x86_64 GNU/Linux
> -
> - $ cat /proc/version_signature
> - Ubuntu 3.13.0-7.25-generic 3.13.1
> -
> - $ lsb_release -rd
> - Description: Ubuntu Trusty Tahr (development branch)
> - Release: 14.04
> + Initially bluetooth didn't work. When I ran "rfkill list" I noticed that
> + bluetooth was soft blocked. Then I ran the command "sudo rfkill unblock
> + bluetooth" and everything worked fine. I was able to pair a bluetooth
> + mouse and the connection was persistent (not sporadic). I even tried
> + this; I paired a tablet and streamed audio from tablet to my laptop. So,
> + this bug is fixed in development release of Ubuntu.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-image-3.13.0-7-generic 3.13.0-7.25
> ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
> Uname: Linux 3.13.0-7-generic x86_64
> ApportVersion: 2.13.2-0ubuntu2
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC1: ubuntu 2609 F.... pulseaudio
> - /dev/snd/controlC0: ubuntu 2609 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC1: ubuntu 2609 F.... pulseaudio
> + /dev/snd/controlC0: ubuntu 2609 F.... pulseaudio
> CasperVersion: 1.337
> CurrentDesktop: Unity
> Date: Fri Feb 7 16:12:13 2014
> LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140205)
> MachineType: A...

[alperyilmaz (alperyilmaz)]

Hi Christopher,

I am very sorry, I thought I upgraded to the latest BIOS. But it looks like I upgraded to previous version.

I upgraded the BIOS to version 208 after your message, and the terminal code shows this:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
N550JV.208
11/19/2013

After that I booted to live USB 10 times. Here's the summary:
1. and 2. trials, adapter was not recognized ("hcitool dev" was empty) and there was NO soft block. No matter what I tried bluetooth didn't work.

3. trial, Adapter was not recognized initially and there was soft block. After unblocking adapter was recognized and then bluetooth worked

4 thru 10. trials: Adapter was recognized ("hcitool dev" gave an ID) and there was NO soft block, bluetooth worked without any workarounds/tweaks.

If you find these tests inconclusive I can do much more tests.

Thanks for your time and help.

[penalvch (penalvch)]

alperyilmaz, thanks for updating your BIOS. It would appear based on your testing that some improvement was had due to this, but an updated driver would need to take it the rest of the way.

Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.14-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Simone Fabris (simone-fabris)]

I have the same problem on Asus N550JV, latest BIOS, Ubuntu 14.04

[penalvch (penalvch)]

Simone Fabris, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Max Schwarz (xqms)]

I also work with an ASUS n550jv.

It's possible that this problem is caused by /etc/init/rfkill-restore.conf. I noticed that ath3k was complaining about a failed firmware download right after that script is run.

This is my theory on what is happening: ath3k starts the firmware download. rfkill-restore decides to (for some reason) block/unblock the asus-bluetooth rfkill. This disrupts the firmware download, and the device is in an unrecoverable state.

Since disabling the rfkill-restore.conf via
echo "manual" | sudo tee /etc/init/rfkill-restore.override
the problem has not occured for over 10 reboots. I had one issue (fw download failed with a different message) after a forced shutdown (holding the power button), but one reboot later everything was okay.

That's no guarantee, but maybe this helps.

[Max Schwarz (xqms)]

By the way, I'm using kernel 3.15.3, so it's probably not fixed upstream. If my theory turns out to be true, then there is a kernel bug (allowing rfkill to interrupt the fw transfer), but also an easy userspace fix (delay rfkill-restore until hci0 is up).

[penalvch (penalvch)]

Max Schwarz, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Fuujuhi (fuujuhi)]

Why expired / incomplete ? This bug should be at least "confirmed". BIOS was upgraded back to 208 as per comment #7

[penalvch (penalvch)]

Fuujuhi, please do not adjust the Status of this report as you are not the original reporter. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]