![]() |
Bluetooth not working, "FW error" found in dmesg
I use bluetooth sparingly, maybe once or twice a month, so I am not 100% certain about when it stopped working.
Anyway, I had overclocked the cpu to 900 mhz using kernel-power in extras-testing and was fine-tuning voltages, reading the overclocking thread, I decided to check in terminal "dmesg | grep error" to find any cpu related errors and the output was "[ 124.260314] hci_h4p hci_h4p: FW error", 3 minutes and some googling later, I found it to be related to bluetooth. So I decided to activate it to pair the N900 with some bluetooth headphones and it just didn't work, no icon, no nothing. Right now, I've reflashed the device and the error is presistent. No bluetooth for me. output from "dmesg | grep hci_h4p": Code:
[ 5.895874] hci_h4p hci_h4p: Registering HCI H4P device Code:
[ 15.793151] Bluetooth: L2CAP ver 2.13 |
Re: Bluetooth not working, "FW error" found in dmesg
fw =firmware error?
|
Re: Bluetooth not working, "FW error" found in dmesg
Quote:
|
Re: Bluetooth not working, "FW error" found in dmesg
Quote:
|
Re: Bluetooth not working, "FW error" found in dmesg
What was the outcome of your bluetooth chip? have you solved the problem or it was an hardware fault? I have the exact same problem and I am still investigating if it is or not an harware fault (but the more time I spend investigating, the more I think so...)
|
Re: Bluetooth not working, "FW error" found in dmesg
Quote:
|
Re: Bluetooth not working, "FW error" found in dmesg
Quote:
|
Re: Bluetooth not working, "FW error" found in dmesg
Quote:
|
Re: Bluetooth not working, "FW error" found in dmesg
Yes i had to do the same. I ran some tests with xterm after lots of googling. It seems though that the hardware is there but there is no firm/software in the blutooth folder. But i guess i will send it in as i dnt think I will get a fix for this.
Thanks Bud |
Re: Bluetooth not working, "FW error" found in dmesg
if you guys really fried your bluetooth chip with overclocking you shold post this in the overclocking thread.
maybe you are one of the first who fried your phones |
All times are GMT. The time now is 20:17. |
vBulletin® Version 3.8.8