Linux Journal A blog about Ubuntu, Linux, Android and IT
  • Jul
    28

    Bugfix: Enable Bluetooth on Fedora 15

    Filed under: Interesting;

    I currently play a bit around with Fedora 15, but unfortunately there are a couple of show stoppers for me to spoil the fun of the new Fedora release something. One of them is that Bluetooth does not work properly. In panel one sees the Bluetooth icon and supposedly is also Bluetooth enabled, but the Bluetooth manager steadfastly claimed that Bluetooth is disabled.The problem probably lies in these two bugs and betrift probably many users, but fortunately the little problems with some manual work can be eliminated from the world.

    Display

    For me Bluetooth is very important, because otherwise I do not work with my Magic Mouse can. My Belkin Bluetooth stick is indeed found in Fedora 15 as a USB device, but hcitool reports that BT no receiver is available …

    The commands lsusb and hcitool comes to the problem quite well on the ropes. If lsusb reports that a BT adapter was found and no device hcitool prints, then you will probably be affected by this problem …

    $ Lsusb | grep BlueBus 007 Device 002: ID 0a5c: 4500 Broadcom Corp.. BCM2046B1 USB 2.0 HubBus 007 Device 005: ID 050D: 0017 Belkin Components B8T017 Bluetooth + EDR 2.1$ Hcitool devDevices:

    The solution is to enable the Bluetooth service. Over the following two commands send you activate the service and start it by hand. After that, the BT service in the future be loaded at boot.

    $ Sudo systemctl enable bluetooth.service$ Sudo systemctl start bluetooth.service

    Then you can connect your BT device again with your Fedora system. According to the above bug, this issue affects only users who have upgraded from an older version, but my system is freshly installed here with the final release of Fedora 15 has been.

    Otherwise

    Fedora 15 makes a great visual impression. GNOME 3 and the artwork of Fedora to make her much, but you have to get used to the user even much much more at the new GNOME Shell in Ubuntu than Unity. Technically available for my system, unfortunately, next to the Bluetooth bug also another show stopper.

    This made it easy to start the live CD install on my system, but when booting the installed system I get only messages I only have one black screen with messages in the style of “CPU # 0 stuck, CPU # 1 stuck, etc. “on the screen. Try it with a little bit I get my computer with the kernel option “noapic” to run. But it's funny when the Live CD boots without problems, but hang on boot the installed system remains.

    .

    No Comments

Leave a reply