Bluetoot doesn't turn on

[will_unicamp]

When I boot Windows and then restart and boot from Ubuntu, my bluetooth works fine. If I shutdown completely and boot from Ubuntu directly, it doesn't works anymore. I tried to use hciconfig to up bluetooth, reinstalled bluez, installed blueman, and nothing worked.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluetooth 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Tue May 1 10:41:48 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Sony Corporation VPCSB35FB
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae root=UUID=5ce83f5b-a5a7-4667-adf7-ffcde0342ba5 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R2085H4
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:svnSonyCorporation:pnVPCSB35FB:pvrC7006TUQ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCSB35FB
dmi.product.version: C7006TUQ
dmi.sys.vendor: Sony Corporation
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:0 acl:0 sco:0 events:0 errors:0
  TX bytes:9 acl:0 sco:0 commands:3 errors:0

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.