1814:3290 Ralink corp. RT3290 Bluetooth not toggling on

[Geoff Kelsall]

When I try to toggle my Novatech nfinity laptop bluetooth via Fn+F11 nothing happens.

geoff@geoff-laptop:~$ lspci|grep Bluetooth
01:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
geoff@geoff-laptop:~$ ps aux| grep bluetooth
geoff 2090 0.0 0.1 490248 6648 ? Sl 09:02 0:00 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
root 3328 0.0 0.0 19240 1752 ? Ss 09:41 0:00 /usr/sbin/bluetoothd
geoff 3371 0.0 0.0 14984 1004 pts/3 R+ 09:52 0:00 grep --color=auto bluetooth

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic]
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: geoff 1957 F.... pulseaudio
Date: Thu Oct 3 09:58:04 2013
HibernationDevice: RESUME=UUID=75bcd0bb-68ec-4ee2-a80d-e6cd4aa1d39d
InstallationDate: Installed on 2013-10-03 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=286ca2cc-f79e-446b-9746-3865b1bfc022 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ChiefRiver
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc3-saucy/

[Geoff Kelsall (q5sc)]

geoff@geoff-laptop:~$ cd Downloads/
geoff@geoff-laptop:~/Downloads$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-3.12.0-031200rc3-generic.
(Reading database ... 155625 files and directories currently installed.)
Unpacking linux-headers-3.12.0-031200rc3-generic (from linux-headers-3.12.0-031200rc3-generic_3.12.0-031200rc3.201309291835_amd64.deb) ...
Selecting previously unselected package linux-image-3.12.0-031200rc3-generic.
Unpacking linux-image-3.12.0-031200rc3-generic (from linux-image-3.12.0-031200rc3-generic_3.12.0-031200rc3.201309291835_amd64.deb) ...
Done.
dpkg: dependency problems prevent configuration of linux-headers-3.12.0-031200rc3-generic:
 linux-headers-3.12.0-031200rc3-generic depends on linux-headers-3.12.0-031200rc3; however:
  Package linux-headers-3.12.0-031200rc3 is not installed.

dpkg: error processing linux-headers-3.12.0-031200rc3-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-3.12.0-031200rc3-generic (3.12.0-031200rc3.201309291835) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.12.0-031200rc3-generic /boot/vmlinuz-3.12.0-031200rc3-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.12.0-031200rc3-generic /boot/vmlinuz-3.12.0-031200rc3-generic
update-initramfs: Generating /boot/initrd.img-3.12.0-031200rc3-generic
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.12.0-031200rc3-generic /boot/vmlinuz-3.12.0-031200rc3-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.12.0-031200rc3-generic /boot/vmlinuz-3.12.0-031200rc3-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.12.0-031200rc3-generic /boot/vmlinuz-3.12.0-031200rc3-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.12.0-031200rc3-generic
Found initrd image: /boot/initrd.img-3.12.0-031200rc3-generic
Found linux image: /boot/vmlinuz-3.8.0-19-generic
Found initrd image: /boot/initrd.img-3.8.0-19-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 12.04.2 LTS (12.04) on /dev/sda1
done
Errors were encountered while processing:
 linux-headers-3.12.0-031200rc3-generic
geoff@geoff-laptop:~/Downloads$

[Geoff Kelsall (q5sc)]

I just tested on 13.10 and cannot get it to work there either. However on 13.10 wireless fails after a short time and lspci shows no bluetooth - not sure whether that info is relevant.

[Geoff Kelsall (q5sc)]

Yes - in 12.04 LTS.

I don't know about other people but for me, although I am running 12.04 LTS now, I do not need Bluetooth enough to be worth putting effort into that.

However it would be nice if it could work when I eventually go to 14.04 LTS.

So shall I test on that?

[Geoff Kelsall (q5sc)]

I mean yes the problem did occur in 12.04 (perhaps there is a difference between my British English and your US English!) and in all releases I have tested so far.

[penalvch (penalvch)]

Geoff Kelsall, did this problem not occur in a release prior to Precise?

[Launchpad Janitor (janitor)]

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

[Geoff Kelsall (q5sc)]

I have not tested any old releases. It does not work on any release that I have tested.

[penalvch (penalvch)]

Geoff Kelsall, thank you for providing the requested information. Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

[Geoff Kelsall (q5sc)]

OK I have made a note in my calendar to try that when I get my laptop back in a few weeks time. And I will test the suggestion at http://forum.novatech.co.uk/showthread.php?26038-Is-there-a-BIOS-update-for-the-nfinity-i5-please&p=333753 that the problem may be to do with UEFI. I do not know much about UEFI so if you have opinions on that I will be interested to hear.

[Sapiencialinux (albertosapiens)]

Maybe duplicate from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189721

[Sapiencialinux (albertosapiens)]

Not fixed on 3.13-r6

[penalvch (penalvch)]

Sapiencialinux, thank you for your comment. at this point, this is not considered a duplicate of another report, or vice versa. 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 a Ubuntu repository 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

[Geoff Kelsall (q5sc)]

I ran the daily buid from a usb stick (non-UEFI) and when I tried the Bluetooth app it said that no Bluetooth adapters were found. Not sure whether any of the below is useful.

ubuntu@ubuntu:~$ sudo service bluetooth status
bluetooth start/running, process 2265
ubuntu@ubuntu:~$ hciconfig
ubuntu@ubuntu:~$ hcitool dev
Devices:
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.13.0-5-generic #20-Ubuntu SMP Mon Jan 20 19:56:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ lspci|grep Bluetooth
01:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
ubuntu@ubuntu:~$ ps aux| grep bluetooth
root 2265 0.0 0.0 19276 1712 ? Ss 10:56 0:00 /usr/sbin/bluetoothd
ubuntu 14458 0.0 0.0 263596 3096 ? Sl 10:59 0:00 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
ubuntu 15178 0.0 0.0 15944 920 pts/0 S+ 11:10 0:00 grep --color=auto bluetooth
ubuntu@ubuntu:~$ /usr/sbin/bluetoothd
ubuntu@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
Codename: trusty
ubuntu@ubuntu:~$

[penalvch (penalvch)]

Geoff Kelsall, thank you for testing Trusty. Could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/ and advise if this is reproducible?

[Geoff Kelsall (q5sc)]

geoff@geoff-laptop:~$ uname -a
Linux geoff-laptop 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:46:44 UTC 2014 i686 i686 i386 GNU/Linux
geoff@geoff-laptop:~$

Bluetooth still says "No Bluetooth adaptors available"

[penalvch (penalvch)]

Geoff Kelsall, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Geoff Kelsall (q5sc)]

Sorry I have never fıled such a report before and I do not understand what information I am supposed to provide from the documentation link mentioned below:

"As well, it is imperative that you include any further debugging information from http://www.kernel.org/doc/Documentation/ using the newest upstream mainline kernel available. Failure to provide the information from the documentation mentioned for the driver or subsystem your reporting a bug in, may likely result in negative unintended consequences. In addition, please be 100% certain you have included all relevant comment information not included in the Bug Description and a kernel developer should review. They are some of the busiest people in the Linux space. They do not need to dive through downstream bug reports to find something that should have been provided when the bug was first filed. If you are unsure about anything asked for, or intend on not following this format, please do not file a report. Instead, continue to ask questions in Launchpad, and of the Ubuntu community, until all issues are cleared up. "

Can you explain in simple terms?

[penalvch (penalvch)]

Geoff Kelsall, if it's outside your immediate ability to provide any further information, it would be fine to skip this one step.

[Geoff Kelsall (q5sc)]

Mailed <email address hidden> with requested info.
Cannot see any url yet at http://www.spinics.net/lists/linux-bluetooth/ for my email.

[Geoff Kelsall (q5sc)]

http://www.spinics.net/lists/linux-bluetooth/msg43371.html

Also same problem in live 14.04

[Geoff Kelsall (q5sc)]

I do not understand why this bug is not a duplicate of bug 1189721. Surely the cause of it not toggling on is that there is no driver? Please could you explain.

[Geoff Kelsall (q5sc)]

When you remove it as duplicate I think it would be polite to explain why you have done so, as I have explained above why I thought it was a duplicate. You probably have greater knowledge of this than me so may well be right but if you do not explain how can we know.

[penalvch (penalvch)]

Geoff Kelsall, as this bug is marked Triaged, not the one you keep unnecessarily marking this a duplicate it of, if you want a lower priority on your bug, keep marking it a duplicate.

[Robin (robingape)]

For the avoidance of anyone's doubt, this bug is functionally a duplicate of bug #1189721. The reason for the problem as reported on bug 1234541 is that there is *no* driver to enable the bluetooth functionality of the RT3290 combined Wi-Fi & Bluetooth device. The focus—and bug reports—should transfer to the 1189721 bug, whose resolution should also deal with 1234541.

Cheers

[Høst (helvete)]

In Ubuntu 13.10 the rtbth driver bluetooth worked (I was able to pair with devices, and with "bluez-simple-agent" I was able to transfer files).
Here's the driver that works with ubuntu 13.10, 3.11 kernel:
https://launchpad.net/~barracuda72/+archive/ralink/+files/rtbth-dkms_3.9.3-0ubuntu1~ppa3.tar.gz
With Ubuntu 14.04 and the 3.13 kernel it will not longer work. I've patched the driver according to this page:
http://wirama.web.id/rt3290-bluetooth-rtbth-driver-with-kernel-3-13/
And it can be installed, but the only problem is that pairing isn't possible. Also, I've tested installing Ubuntu 13.10 from scratch and then updating it to 14.04 with the rtbth module installed, or downgrading to 3.11 kernel in Ubuntu 14.04.
Also I've installed the 3.16rc5 kernel, with not luck (I upgraded everything when I had the 3.13 kernel with "sudo apt-get dist-upgrade). The problem persists with every kernel: can't pair with devices. It's the only problem
Here are some info:
hoest@hoest:~$ uname -a
Linux hoest 3.16.0-031600rc5-generic #201407131735 SMP Sun Jul 13 21:36:15 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ lspci -nnk
02:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298]
 Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter [103c:18ec]
 Kernel driver in use: rtbt

How can I send an email to the kernel team, or anything so this can be fixed? It's anonying to have a non working bluetooth.

[penalvch (penalvch)]

Robin, please stop marking linux (Ubuntu) bugs duplicates of others unless you are going to submit a patch that will imminently fix the issue. linux (Ubuntu) bug triaging is completely different then upstream, or userspace, and has nothing to do with how related one bug seems to another one.

Høst, 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

[Geoff Kelsall (q5sc)]

The Linux bug reporting process is probably obvious for those who use it often but it is confusing for someone like me who uses it rarely.

I do not understand why you say "linux (Ubuntu) bug triaging is completely different then upstream, or userspace, and has nothing to do with how related one bug seems to another one."

As far as I can see no action (such as triaging) has been taken on
http://www.spinics.net/lists/linux-bluetooth/msg43371.html
so I wonder if I have just wasted my time by raising it. If there was a comment on it to say something like "this is low priority - sorry no one is likely to look at it soon" I would accept that.

I understand Ubuntu is very popular but I cannot see non-technical people taking the time to raise bugs in this way to help improve Ubuntu - they will just buy an iphone or ipad from Apple for simplicity and forget about Linux.