I snapped up a 770 from Expansys (dodgy customer service, cheap prices) last week who despite claiming to have 282 in stock were actually telling slight porkies. It came in the post yesterday only a few days late (too bad I paid for next day delivery).

Anyway. I've used linux/unix as a hobbiest and commercially for about 11 years so the 770 really appealled to me when it came out, but even more so when it became mega cheap. I plan to use the device for its intended purpose too, but as I've a much faster GPS/PDA/phone and laptops it's not so important if i break it slightly, provided it doesn't get too bricked.

Searching this forum and various other places I've figured a fair amount out so far; I've got dropbear running and can ssh in from other computers. I've gotten various things installed on it including UKMP.

The first time I switched it on the screen was a bit messed up, which has happened a few times since. The main cause for concern is that it reboots itself far more than I'd like. Earlier on today it'd boot up and be useable for about 2 minutes before rebooting again. I've no idea why and I'd love to know. Sometimes it reboots after just loading up and enabling wireless. Sometimes it locks up first for a few seconds, other times it just goes straight away.

I installed syslogd (apt-get install sysklogd) and enabled in syslog.conf the kernel and daemon level logs to try and shine some light on it. I'm now getting files in /var/log which is nice and it seems to be automatically turning them over into gzips which is great. I was hoping I'd see something really obvious in there, but sadly not. I'm getting various memory errors in kern.log, but I'm not sure whether these are normal or not. Here's an example:

Aug 8 17:56:53 Nokia770-49 kernel: [ 117.151794] JFFS2 notice: (331) read_dnode: header CRC failed on node at 0x6148fe8: read 0xffffffff, calculated 0x17230b97
Aug 8 17:56:53 Nokia770-49 kernel: [ 117.341217] JFFS2 notice: (331) check_node_data: wrong data CRC in data node at 0x06c11000: read 0x1b179df2, calculated 0xc97f09c0.
Aug 8 17:56:53 Nokia770-49 kernel: [ 117.606781] JFFS2 notice: (331) check_node_data: wrong data CRC in data node at 0x06d12000: read 0x94c1c44e, calculated 0x7b072e65.

I've enabled swap on the memory card, with it freshly booted, streaming net radio and running dropbear I get in top:

Mem: 60516K used, 1708K free, 0K shrd, 56K buff, 20416K cached

According to control panel the device is:

OS 2006
Version: 3.2006.49-2

According to /proc/cpuinfo:

Processor : ARM926EJ-Sid(wb) rev 3 (v5l)
Hardware : Nokia 770
Revision : 17100016

According to /proc/version:

Linux version 2.6.16.27-omap1 (bifh1@doree) (gcc version 3.4.2 (release) (CodeSourcery ARM Q3D 2004)) #1 PREEMPT Wed Nov 29 16:29:50 EET 2006

I've no idea whether its a battery issue or not. Unless I'm missing something there doesn't seem to be any reporting on battery status? It shows in the UI if it's plugged in, but not the state. In syslog I've noticed lines of:

daemon.log:Aug 8 14:23:44 Nokia770-49 bme-dbus-proxy[696]: battery_state_changed (val=4) sent!
daemon.log:Aug 8 14:24:00 Nokia770-49 bme-dbus-proxy[696]: battery_full sent!

Any ideas? Does it sound normal or did I get a duff one? (I don't fancy my luck getting a replacement from expansys) Is there anything I should be looking for in syslog?

Thanks

I'm not expert, but that looks bad. Have you tried flashing it with the latest image? Even if it's the _same_ image, it would overwrite anything that might have gone wacko. I'm guessing since JFFS2 is reporting it rather than FAT, that it's not a memory card, but is the built-in memory itself.

I haven't flashed it yet, I'm away at the moment so waiting till I'm back home with linux boxes to do it from.

For added info, after a reboot I copied the contents of /proc/bootreason and those in /var/lib/dsme/stats to a directory on the mmc. They are:

Nokia770-49:/media/mmc1/crashlog# cat bootreason
32wd_to
Nokia770-49:/media/mmc1/crashlog# cat 32wd_to
230
Nokia770-49:/media/mmc1/crashlog# cat lifeguard_resets
/usr/bin/maemo_af_desktop : 1 *
Nokia770-49:/media/mmc1/crashlog# cat lifeguard_restarts
/usr/bin/osso-media-server : 6
/usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z : 3 *
Nokia770-49:/media/mmc1/crashlog# cat sw_rst
1

I've got something similar and I've found:
http://lists.laptop.org/pipermail/bu...ne/078204.html

for me it's:
[ 89.520050] JFFS2 error: (337) read_direntry: illegal nsize in node at 0x71640f8: nsize 0x56, totlen 0x37e
[ 99.002563] JFFS2 notice: (337) check_node_data: wrong data CRC in data node at 0x0592e800: read 0x6d3b97ba, calculated 0x1ec4b25a.

Reflash didn't change a thing - I'll have to get used to this probably.

Edit: my n770 got kind of worse after next flash - it powers itself down with no startup after that. I have to remove battery for a while to be able to switch it on.