![]() |
2006-02-28
, 19:14
|
Posts: 23 |
Thanked: 0 times |
Joined on Feb 2006
@ Boston
|
#2
|
![]() |
2006-03-01
, 18:10
|
Posts: 23 |
Thanked: 1 time |
Joined on Jan 2006
@ Portland
|
#3
|
Just thought I'd mention that I was able to add new network connections after reflashing the device. I still don't know what might have cause the problem in the first place. It sort of feels like an out-of-space error, but I had 8Mb free, so that shouldn't be it — unless the number reported by df is inaccurate, or the filesystem the N770 uses requires a lot of space free in order to update a small file. So I'm still puzzled how to avoid this problem in the future.
![]() |
2006-03-01
, 18:39
|
Posts: 23 |
Thanked: 0 times |
Joined on Feb 2006
@ Boston
|
#4
|
By "reflashing", do you mean that you upgraded to the latest firmware image? (It is rev. 3.2005.51-13; you can find which version you are currently running under Control panel -> Device.)
The original firmware revision that the Nokias were shipped with were notorious for spontaneous reboots & other odd behavior. If you are still running the 2005.45 firmware Beowabbit, upgrade!
Yesterday evening it stopped associating with my access point at home. (I'm using WEP and not broadcasting the SSID, in case that makes any difference.) It saw the access point and reported two or three bars of signal strength, but when I tried to connect via that network, the little W on the connectivity (globe) icon in the titlebar just flashed. I tried several times, and went downstairs and tried again right next to the AP, with no luck. (By the way, my Mac and my housemate's laptop both use wireless connecting in the same way to the same AP.) Just as I was about to post here about it, it started working again, and I spent the rest of the evening listening to Internet radio.
This morning, though, it didn't work again. I tried re-entering the WEP key (although I hadn't touched it since originally setting it up yesterday), and when I tapped Next the Connection Manager crashed. When I brought it up again, there were no connections defined (including my Bluetooth phone connection). I tried to re-add my home wireless connection, and when I tapped Finish I didn't get any errors, but the connection wasn't saved -- I got the big dialogue box that's supposed to let me pick a connection, but it was blank between the titlebar and the buttons. A couple other attempts (rebooting in between, and pulling the battery to make sure the device was really reset) had the same result.
My first thought was that the root filesystem was out of space, but I checked, and I have 8Mb or so free. (I've installed osso-xterm, the Ogg Vorbis player, and Nethack. (At one point I had also installed Doom, but since I couldn't find a way to start it, I uninstalled it.) I did not enable root.
I'm guessing at this point that I'm going to need to reflash the device, but can anybody tell me what happened in the first place? And more importantly, how to avoid it? If this happens every other day, or even every month, the 770 is not going to be usable for me, and I'm going to need to give up on it and send it back.
Here are relevant-looking bits of dmesg:
<pre>
[...]
[ 8.000640] Inode #8086 was a directory with children - removing those too...
[ 8.000823] Inode #8088 was a directory with children - removing those too...
[ 8.003051] Inode #8497 was a directory with children - removing those too...
[ 8.003906] Inode #8514 was a directory with children - removing those too...
[ 8.004058] Inode #8516 was a directory with children - removing those too...
[ 8.004394] Inode #8526 was a directory with children - removing those too...
[ 10.945983] jffs2_get_inode_nodes(): Data CRC failed on node at 0x00183104: Read 0x94610a27, calculated 0xd369a246
[...]
</pre>
I see dmesg isn't preserved across reboots (makes sense), but from before I remember seeing stuff about successfully scanning 11 channels when I was trying to use wireless, and about "No power saving", and nothing else that seemed like it might be relevant. If there are logs other than the output of dmesg I haven't found them.