Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 12 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 13 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 5 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days, 2 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 9 hrs ago - more...
 |
|
2012-01-04
, 19:06
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#12
|
I'd be willing to be this is more due to the drop and over-use than overclocking. The one exception being, if you overclocked and ran it at high rates regularly (eg high CPU use via game emulators and such) then the heat from that may have caused some damage.
As for overclocking, the only issue I've ever seen with overclocking and fs corruption was pretty early on in the very first overclocking kernels. In that case, they were trying to under-volt too much, and sometimes the writes were failing because of the lack of voltage. The fs would corrupt because of bad data, but the block itself was fine. (So a reformat & copy over fixed it.)
It really does sound like your chip either took damage (a flaky solder joint is slowly coming lose?) or was just over-used and isn't aging well. The sudden clustering of failure though would point more toward chip damage.
Good luck!
As for overclocking, the only issue I've ever seen with overclocking and fs corruption was pretty early on in the very first overclocking kernels. In that case, they were trying to under-volt too much, and sometimes the writes were failing because of the lack of voltage. The fs would corrupt because of bad data, but the block itself was fine. (So a reformat & copy over fixed it.)
It really does sound like your chip either took damage (a flaky solder joint is slowly coming lose?) or was just over-used and isn't aging well. The sudden clustering of failure though would point more toward chip damage.
Good luck!
| The Following User Says Thank You to woody14619 For This Useful Post: | ||
|
|
2012-01-04
, 19:47
|
|
Posts: 64 |
Thanked: 109 times |
Joined on Mar 2010
|
#13
|
I had to reflash already 2 times, after I updated to KP49. First time complete and second time kernel only (due restart cycles). Never happened to me before KP49.
|
|
2012-01-04
, 22:13
|
|
Posts: 468 |
Thanked: 610 times |
Joined on Jun 2006
|
#14
|
Originally Posted by mauron85
depends on why you needed to flash the device.
I had to reflash already 2 times, after I updated to KP49. First time complete and second time kernel only (due restart cycles). Never happened to me before KP49.
|
|
2012-01-05
, 20:58
|
|
Posts: 64 |
Thanked: 109 times |
Joined on Mar 2010
|
#15
|
Originally Posted by Bernard
because n900 was not booting - restart cycles
depends on why you needed to flash the device.
 |
|
2012-01-06
, 01:04
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#16
|
Originally Posted by Bernard
- I would assume second option as most probable.
So a number of possibilities:
- wear because of age of the flash chip.
- damage to mounting of flash chip because of dropping the n900
- melting/short-circuit because of flashing/backupmenu
- damage because of overclocking/kernel-power
- Wear should not be the problem as the bad sectors should be marked and not used anymore. But here ends my linux/ext/SD knowledge, maybe backup/reformat/restore /opt once again from yor ubuntu PC (using backupmenuu, USB networking).
Pls.see
http://en.wikipedia.org/wiki/Flash_m...ng_and_erasing
http://en.wikipedia.org/wiki/Bad_sector
and
http://en.wikipedia.org/wiki/Badblocks
Code:
badblocks /dev/mmcblk0p2
- Third does not make sense and fourth I can not imagine.
http://talk.maemo.org/showthread.php?t=69081
So a number of possibilities:
- wear because of age of the flash chip.
- damage to mounting of flash chip because of dropping the n900
- melting/short-circuit because of flashing/backupmenu
- damage because of overclocking/kernel-power