No bluetooth adapters detected

Recently I got a new network card for my netbook (Acer Aspire One AOA150/ZG5) as this one supported bluetooth (the network card previously in my netbook didn't). I got an Intel Centrino Wireless-N 1030 (as that one supports bluetooth), and when I use lspci it is listed. I'm also able to connect to wifi with it just fine, but for some reason it's not appearing in my bluetooth adapters (I have installed the bluez package along with bluedevil for KDE and started the bluetooth daemon). I'm not sure what the issue is, and I've been looking around on Google trying to find an answer (with no luck so far).

Re: No bluetooth adapters detected

Okay, then it must be a that the driver is not loaded. I guess it 'could' be a BIOS thing, but the fact that lspci dose show the bluetooth chipset makes me thing that it is not.

I looked at the kernel config and all the Bluetooth driver are compiled with the default kernel. They are compiled as Modules though, so there is a chance that maybe your driver is just not auto-loading like it should. In any case I'd start googleing and trying to find out which driver your card uses.

Also, after installing this new network card I've noticed issues with my BIOS (after about 4 seconds it will freeze, and then a few seconds later continue, and then do that again (it doesn't seem to effect the OS except when booting, as the bootloader will freeze with 2 seconds left and then a few seconds later start booting)). I'm not sure if I can fix that or if I should just put my old card in (I've yet to really Google this however, so I'll be doing that before I replace the card or anything, I just felt it was worth mentioning).

Re: No bluetooth adapters detected

Please use [code ][/code ] tags (w/o) the spaces. It makes stuff much easier to read.

Anyway, it is definitely not the issue I get as rfkill doesn't see bluetooth at all.

What errors are you getting when you try to start the bluetooth service manually?

By manually do you mean running

systemctl enable bluetooth.service

and

systemctl start bluetooth.service

(sorry, not really sure :v) When I run those I get no errors or anything (basically it just runs and nothing comes up). However, lately I've noticed that when in tty1 an error constantly appears (even when I'm not doing anything it just shows up in the terminal; wont show up in the terminal running in KDE however, only when I'm not in the GUI). The error is:

[ 501.646833] hub 5-0:1.0: unable to enumerate USB device on port 1

The numbers inside the square brackets change each time the message displays (the message displays once every 15 or so seconds). I'm not sure if this is related to the bluetooth issue however, as my bluetooth device is connected via mini PCI-e, but the issue only started after installing the new card.

Re: No bluetooth adapters detected

Zukaro wrote:

Also, after installing this new network card I've noticed issues with my BIOS (after about 4 seconds it will freeze, and then a few seconds later continue, and then do that again (it doesn't seem to effect the OS except when booting, as the bootloader will freeze with 2 seconds left and then a few seconds later start booting)). I'm not sure if I can fix that or if I should just put my old card in (I've yet to really Google this however, so I'll be doing that before I replace the card or anything, I just felt it was worth mentioning).

Awe shoot ya, it sounds like your BIOS is having trouble identifying/activating the bluetooth device. I kind of thought it was a long shot that it was a driver problem 1) it is Intel and Intel loves Linux, 2) The Arch Kernel is built with all the bluetooth drivers available.

Three things you could try,

First, see if there is an option in BIOS to do a like "Full Boot" or Not a "Fast Boot"/"Quick Boot"

Second, see if there is a new BIOS available for your laptop.

Three, take out the card, and put it back in. "Maybe" it didn't seat properly.

If you can get all your money back.... Maybe you should, and get a flushmount USB bluetooth adapter instead.

Re: No bluetooth adapters detected

hunterthomson wrote:

Zukaro wrote:

Also, after installing this new network card I've noticed issues with my BIOS (after about 4 seconds it will freeze, and then a few seconds later continue, and then do that again (it doesn't seem to effect the OS except when booting, as the bootloader will freeze with 2 seconds left and then a few seconds later start booting)). I'm not sure if I can fix that or if I should just put my old card in (I've yet to really Google this however, so I'll be doing that before I replace the card or anything, I just felt it was worth mentioning).

Awe shoot ya, it sounds like your BIOS is having trouble identifying/activating the bluetooth device. I kind of thought it was a long shot that it was a driver problem 1) it is Intel and Intel loves Linux, 2) The Arch Kernel is built with all the bluetooth drivers available.

Three things you could try,

First, see if there is an option in BIOS to do a like "Full Boot" or Not a "Fast Boot"/"Quick Boot"

Second, see if there is a new BIOS available for your laptop.

Three, take out the card, and put it back in. "Maybe" it didn't seat properly.

If you can get all your money back.... Maybe you should, and get a flushmount USB bluetooth adapter instead.

I think I'm going to do that (sending the card back), as I have a USB bluetooth adapter which does work with Arch (I tested it a minute ago). I've never actually updated the BIOS so I'm not sure how (but that's just a Google search away, so I might try that, as this netbook was never made with bluetooth support in mind so that could be the reason it's not working). I did try disabling quick boot but that didn't make a difference. I have a feeling if the card wasn't connected properly wireless wouldn't work at all either.

Anyways, thanks for the help. Before I send the card back I'm going to look into updating the BIOS so I can see if that's the issue.

rfkill is a small tool to query the state of the rfkill switches, buttons and subsystem interfaces.

Yes, I know. I assume that's why it shows up in mine. *But* the hardware switch does not unblock bluetooth on my machine even though it should. It did used to work for wifi though I'm not sure it does any more. I don't know if this is because the switch is a fn+Fn combination but so it is. The only way to unblock bluetooth for me is to reset the bios to defaults.

I just thought it was worth checking that wasn't the problem for the OP since I also get claims about there being no device etc. when it is hardblocked. But if rfkill doesn't show it at all, it cannot be the same problem. That's all.