Active Topics
-
[Announce] genwall a simple iptables firewall (90)
to Applications by paoletto - 1 day, 4 hrs ago -
N9 as WiFi repeater/extender? (1)
to Nokia N9 / N950 by paoletto - 1 day, 5 hrs ago -
Sailfish OS flashing files (89)
to SailfishOS by monkeyisland - 2 days, 5 hrs ago - more...
 |
|
2007-10-05
, 14:16
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#72
|
Originally Posted by onion_cfe
Are Quim and Eero's comments in Bugzilla not detailed enough?
Nokia and others - Clarification very much required on the fix before I flash it and buy a new large card!
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
 |
|
2007-10-05
, 15:11
|
|
Posts: 1,310 |
Thanked: 820 times |
Joined on Mar 2006
@ Irving, TX
|
#73
|
Originally Posted by Texrat
Well... they are rather detailed, but may bark the wrong tree...
Are Quim and Eero's comments in Bugzilla not detailed enough?
In my case, when my memory card corruptions happened, I did not have WiFi connection active, nor did I have tablet hooked up to PC via USB. The only thing that my the tablet was doing was in sleep (display off), while simultaneously running MaemoMapper in moving car, and connected to Bluetooth GPS receiver. MaemoMapper application constantly listened coordinates data from the GPS receiver and updated its (non-visible, due to display dimmed) display with correct map tiles. What it actually did, it READ (note, READ, not WRITE) map tiles from the memory card. I had all the necessary map tiles loaded in the memory card so MaemoMapper did not have a need to retrieve and save any of them to the card. (Earlier I did not have data plan on my phone, thus this would have been technically impossible, and the corruptions still happened.)
So, in my case the corruption clearly occurred in different circumstances than what was described to be the root causes. However, the fix was explained with good detail. It is my current belief that this fix should work in my use case as well. Also, since I never experienced the corruption when the MaemoMapper was in full screen mode (which forces it to keep the display always on), should further prove the problem being in the power save mode and in its implementation affecting memory cards.
So far, the new kernel has worked fine for me. (But I haven't tried this MaemoMapper test on the go yet...)
 |
|
2007-10-05
, 15:25
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
@ Halifax, Nova Scotia, Canada
|
#74
|
Originally Posted by Texrat
Haha.. hope you still think so when ThoughtFix has his poll for his spare RX-44. :P
You're a good man.
|
|
2007-10-05
, 15:48
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#75
|
Originally Posted by Mara
I'm confused. I just read Eero's latest remarks and the focus was on the kernel, voltages and timing-- not wifi. So I don't get the continued emphasis on wlan and wifi by posters.
Well... they are rather detailed, but may bark the wrong tree...
In my case, when my memory card corruptions happened, I did not have WiFi connection active, nor did I have tablet hooked up to PC via USB. The only thing that my the tablet was doing was in sleep (display off), while simultaneously running MaemoMapper in moving car, and connected to Bluetooth GPS receiver. MaemoMapper application constantly listened coordinates data from the GPS receiver and updated its (non-visible, due to display dimmed) display with correct map tiles. What it actually did, it READ (note, READ, not WRITE) map tiles from the memory card. I had all the necessary map tiles loaded in the memory card so MaemoMapper did not have a need to retrieve and save any of them to the card. (Earlier I did not have data plan on my phone, thus this would have been technically impossible, and the corruptions still happened.)
So, in my case the corruption clearly occurred in different circumstances than what was described to be the root causes. However, the fix was explained with good detail. It is my current belief that this fix should work in my use case as well. Also, since I never experienced the corruption when the MaemoMapper was in full screen mode (which forces it to keep the display always on), should further prove the problem being in the power save mode and in its implementation affecting memory cards.
So far, the new kernel has worked fine for me. (But I haven't tried this MaemoMapper test on the go yet...)
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
|
|
2007-10-05
, 16:58
|
|
Posts: 1,310 |
Thanked: 820 times |
Joined on Mar 2006
@ Irving, TX
|
#76
|
Originally Posted by Texrat
OK, maybe it was little bit different in Eero's comment, but I was reading this.
I'm confused. I just read Eero's latest remarks and the focus was on the kernel, voltages and timing-- not wifi. So I don't get the continued emphasis on wlan and wifi by posters.
EDIT: In fact the details are in the link inside that link to the bug fix details... where they reference to the large downloads to the memory card over the air (wireless). So, technically it could be via bluetooth also?
However, I was not doing any download or writes to memory card when my card s corrupted.
Last edited by Mara; 2007-10-05 at 17:04.
|
|
2007-10-05
, 17:10
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Aug 2007
|
#77
|
Ok, lets try to move this along because it feels like we're at cross-purposes here.
When I read this explanation:
...I feel I am understanding what it means, and to me it implies that the issue could just as easily occur away from WLAN and inter-card transfers, and certainly USB, which tells me that this will fix my problem, However, the text released alongside the update specifically only mentions "over-the-air" and inter-card transfers. I am emphasising WLAN because the release did..
I have my USB related card corruption problem, I have the patch and what it is said to fix, and I have a technical post which explains the cause of the fixed problem. I would like somebody more knowledgeable than myself to join the dots between these three things.
The question "is my problem fixed?" stands, and the fact that i've had two responses wondering why i'm asking and zero responses saying "yes" leads me to believe that i'm justified in continuing to ask. Please refrain from discouraging anybody that might be williing to provide an answer.
When I read this explanation:
What happened:
- Once the card has acknowledged that it had received the data,
the kernel driver switched the MMC clock off
- If the device doesn't have any active clocks (display off, no USB
connected, no RD-mode, no network activity for a while, MMC clocks
off etc), the kernel power management switched the device into sleep mode
- In sleep mode MMC ports get less power
However, the card could still be doing something internally which would
draw power from the MMC port. With some cards, this seems to have damaged
them.
This new release provides a software fix for a bug which may have appeared while copying large amount of data over-the-air or from external SDHC memory card to internal memory or vice versa
The question "is my problem fixed?" stands, and the fact that i've had two responses wondering why i'm asking and zero responses saying "yes" leads me to believe that i'm justified in continuing to ask. Please refrain from discouraging anybody that might be williing to provide an answer.
|
|
2007-10-05
, 17:29
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#78
|
You're leaping to an invalid conclusion about my motive, onion. My point is we are best served by stripping away inconsequential aspects of the dialog and focussing on what's truly relevant. I have made no motion whatsoever to discourage dialog of any sort, and resent such accusations.
There's a profound difference between root cause (as explained by Eero) and circumstances of occurrence (the "over-the-air" comment). I think the latter was unnecessarily specific and caused confusion... probably why I subconsciously ascribed it much lower significance than the probable root cause remarks.
So hopefully we can all disabuse ourselves of the essentially-moot wifi aspect and focus on probable root cause. In that respect, I believe your question HAS been answered, but I'll reiterate: it appears that the problem has been fixed. However, this is one of those issues that only real-world testing can confirm or deny. Nokia developers seem satisfied that such testing proves the bug fixed. Your mileage *may* vary. That's the best anyone can offer at this point.
There's a profound difference between root cause (as explained by Eero) and circumstances of occurrence (the "over-the-air" comment). I think the latter was unnecessarily specific and caused confusion... probably why I subconsciously ascribed it much lower significance than the probable root cause remarks.
So hopefully we can all disabuse ourselves of the essentially-moot wifi aspect and focus on probable root cause. In that respect, I believe your question HAS been answered, but I'll reiterate: it appears that the problem has been fixed. However, this is one of those issues that only real-world testing can confirm or deny. Nokia developers seem satisfied that such testing proves the bug fixed. Your mileage *may* vary. That's the best anyone can offer at this point.
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
|
|
2007-10-05
, 18:41
|
|
Posts: 39 |
Thanked: 0 times |
Joined on Aug 2007
|
#79
|
Fair points, and I apologise for misreading your motive. I'm perhaps a little sparse on this forum to be writing stuff like that in the direction of better established members.
I just wish I felt more confident about buying some new 8GB cards. In line with other's comments, I don't want to be the self-funded test platform for this one - not a second time. I think what that really amounts to is me now having to wait and see if the problem completely disappears.
I certainly haven't seen anybody report a newly corrupted card in the last 3 days, so that's a good sign. There could be nothing but good news here, and I really hope that's the case.
I just wish I felt more confident about buying some new 8GB cards. In line with other's comments, I don't want to be the self-funded test platform for this one - not a second time. I think what that really amounts to is me now having to wait and see if the problem completely disappears.
I certainly haven't seen anybody report a newly corrupted card in the last 3 days, so that's a good sign. There could be nothing but good news here, and I really hope that's the case.
|
|
2007-10-05
, 18:44
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#80
|
No problem. I can't prove the problem is completely resolved of course but I have a high degree of confidence that it is. So high in fact that at the nearest opportunity I will break down and purchase an SDHC card and install it on an N800 I use solely for testing. Believe me, I run that poor sucker through the mill. 
Last edited by Texrat; 2007-10-05 at 18:46.
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Last edited by Texrat; 2007-10-05 at 18:46.
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net