[HP ProBook 4540s] Qualcomm Atheros bluetooth properly works with Ubuntu 16.04 LiveUSB but not on a fresh install

Bug #1653274 reported by Jordi Sayol on 2016-12-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

I've tested my notebook with Ubuntu 16.04/17.04 (64-bit) LiveUSB pen drive and the mini-pci Qualcomm Atheros QCWB335 [168c:0036] properly works, both wifi and bluetooth.

After a fresh install from the same LiveUSB pen drive, the bluetooth does not work.

$ bluetooth
bluetooth = none (no device)

Pressing the WiFi button turns off WiFi, and does not enable bluetooth. Pressing it again turns WiFi on, but bluetooth remains off.

WORKAROUND: Suspend, and unsuspend the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
 /dev/snd/controlC0: jordi 3434 F.... pulseaudio
CurrentDesktop: MATE
Date: Fri Dec 30 18:53:28 2016
HibernationDevice: RESUME=UUID=22fa6fdd-bc1b-48c0-a8e9-ba287e907d51
InstallationDate: Installed on 2016-12-27 (2 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP ProBook 4540s
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=429e043d-9fc2-4b1b-b017-10d3d2ea6bc2 ro quiet splash vt.handoff=7
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic N/A
 linux-firmware 1.157.2
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IRR Ver. F.62
dmi.board.name: 17F6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 58.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.62:bd09/29/2016:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4540s
dmi.product.version: A1019D1103
dmi.sys.vendor: Hewlett-Packard

Jordi Sayol (g-sayol) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
description: updated

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Jordi Sayol, thank you for reporting this and helping make Ubuntu better.

To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

tags: added: latest-bios-f.62
removed: apport-collected
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
summary: - Qualcomm Atheros bluetooth properly works with Ubuntu 16.04 LiveUSB but
- not on a fresh install
+ [HP ProBook 4540s] Qualcomm Atheros bluetooth properly works with Ubuntu
+ 16.04 LiveUSB but not on a fresh install
Jordi Sayol (g-sayol) wrote :
Download full text (3.3 KiB)

From my notebook running Ubuntu 16.04 (64-bit) LiveUSB pen drive:

$ bluetooth
bluetooth = on

# lspci -nnvvv
04:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
 DeviceName: WLAN
 Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network Adapter [11ad:0612]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at d0600000 (64-bit, non-prefetchable) [size=512K]
 Expansion ROM at d0680000 [disabled] [size=64K]
 Capabilities: [40] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
  Address: 0000000000000000 Data: 0000
  Masking: 00000000 Pending: 00000000
 Capabilities: [70] Express (v2) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
   ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
  LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
    EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
 Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
 Capabilities: [140 v1] Virtual Channel
  Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
  Arb: Fixed- WRR32- WRR64- WRR128-
  Ctrl: ArbSelect=Fixed
  Status: InProgress-
  VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
   Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
   Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
   Status: NegoPendi...


Jordi Sayol, to advise, you don't have to apport-collect to a report unless specifically requested to do so. Despite this, could you please advise to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653274/comments/17 ?

description: updated
Jordi Sayol (g-sayol) wrote :

Sorry for the "apport-collet". My mistake.

No changes on Ubuntu daily-live (December 31th 2016). Exactly the same behaviour, bluetooth properly works when run the LiveUSB pen drive but do not works after a fresh install using the same pen drive.

Note that I always used Ubuntu MATE on all the tests.

tags: added: zesty

Jordi Sayol, to clarify, if you click on your keyboard the WIreless Button once, does the bluetooth turn on, and the WiFi remain on?

Jordi Sayol (g-sayol) wrote :

No, if I press the wlan button, wifi turns off and bluetooth keeps missing. If pressed again, only wifi reactivate. Bluetooth alwais keep missing, like there is not a bluetooth device.

Another behaviour discovered. If I "Suspend" my notebook, when reactivate, the bluetooth works! and wifi remains working too.

Jordi Sayol, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

description: updated
Pilot6 (hanipouspilot) wrote :

Please add the output of

rfkill list

Jordi Sayol (g-sayol) wrote :

$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

$ bluetooth
bluetooth = none (no device)

Same behaviour with kernek 4.10 RC1. Bluetooth device is missing.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.10-rc1

Jordi Sayol, would anything change if you disconnected the below, restarted and then tried the WiFi keyboard combo:
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver

Jordi Sayol (g-sayol) on 2016-12-31
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Jordi Sayol (g-sayol) wrote :

Christopher M. Penalver, I don't understand you. I do not have any "wifi keyboard combo". I guess it was a thread mistake.

Jordi Sayol, as per the user manual downloaded from HP.com, it does have a WiFi keyboard button. Could you please read it and advise?

Jordi Sayol (g-sayol) wrote :

Christopher M. Penalver, Yes, there is a wlan button with a led. By default all devices are activated (led white). when pressed, led becomes orange indicating that all wireless devices (wifi and bluetooth) are deactivated. When the button is pressed again wifi reactivate, but bluetooth never. Bluetooth is only active (device present detected by Linux) after Suspend/reactivate the computer.

I have a question for you. If this is a Linux kernel problem, why this wireless device works like a charm when the computer is boot by the Ubuntu liveUSB pen drive?

Jordi Sayol, one way to help confirm if this is a regression in the linux kernel is to test the version that comes with the Live environment 4.4.0-21.37.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Jordi Sayol (g-sayol) wrote :

Christopher M. Penalver, sorry for the delay. I've booted liveUSB and installed the last three Ubuntu LTS (12.04.5, 14.04.5 and 16.04.1) and all of them have the exactly same behaviour. When booted from the LiveUSB, both WiFi and BLuetooth works like a charm, but when booted after a fresh install, Wifi works and bluetooth is not detected (no device installed), and in all the cases, after a system "Suspend", Bluetooth is detected again.

I don't know what's the source of this problem but I'm quite sure that this is not a simply regression on a kernel version.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers