The Following User Says Thank You to azstunt For This Useful Post: | ||
|
2010-04-17
, 06:03
|
Posts: 3,664 |
Thanked: 1,530 times |
Joined on Sep 2009
@ Hamilton, New Zealand
|
#2
|
|
2010-04-17
, 06:04
|
Posts: 43 |
Thanked: 32 times |
Joined on Jan 2010
|
#3
|
|
2010-04-17
, 06:25
|
Posts: 3,664 |
Thanked: 1,530 times |
Joined on Sep 2009
@ Hamilton, New Zealand
|
#4
|
|
2010-06-02
, 21:52
|
Posts: 20 |
Thanked: 4 times |
Joined on Nov 2009
|
#5
|
|
2010-06-03
, 00:07
|
Posts: 43 |
Thanked: 32 times |
Joined on Jan 2010
|
#6
|
|
2010-09-18
, 07:15
|
Posts: 9 |
Thanked: 4 times |
Joined on Aug 2010
|
#7
|
|
2010-09-18
, 18:29
|
Posts: 43 |
Thanked: 32 times |
Joined on Jan 2010
|
#8
|
|
2010-09-19
, 08:56
|
Posts: 9 |
Thanked: 4 times |
Joined on Aug 2010
|
#9
|
|
2010-09-19
, 10:02
|
|
Posts: 1,210 |
Thanked: 597 times |
Joined on Apr 2010
@ hamburg,germany
|
#10
|
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":