Reply
Thread Tools
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#11
Originally Posted by fanoush
Milhouse, are you using wi-fi for the ssh connection? Did you try also other combinations like on battery with xterm or ssh on mains? Looks like you always wrote ssh+battery xterm+mains. Would be interesting if it is caused by network connection or poor battery.

I never had such symptoms but I don't use wi-fi regulary for ssh into the device, I prefer bluetooth (better response time, lower power requirements, no random disconnects). Maybe wi-fi driver is buggy and reboots the device? There are many variables in wi-fi network (access point brand and settings) so there can be combinations which are not stable. So the battery may be ok, just wi-fi may be the problem.
I'll try the above combinations and let you know!

Originally Posted by fanoush
As for unmet dependencies you mentioned only tableteer and sardine, did you try upgrading also with regular maemo2.0 repository added? I think sardine needs it.
This is the sources.list I used to upgrade to Sardine:

Code:
/opt/etc/apt # more sources.list
#maemo:essential
deb http://catalogue.tableteer.nokia.com/certified/     mistral user
deb http://catalogue.tableteer.nokia.com/non-certified/ mistral user

deb http://repository.maemo.org sardine main
deb http://repository.maemo.org maemo2.0 free non-free
What other repositories should I add? I read some documentation on the Sardine Wiki that suggested the above repositories were all that I required.

Originally Posted by fanoush
As for the dmesg output it looks like you rootfs had very interesting time in the past It can still be OK but it may be also corrupted. All these messages are just warnings or infos but it definitely looks like there were random reboots with jffs2 filesystem in the middle of work. In theory it should still work but if there are some strange issues I'd try reflash (rootfs only, otherwise you loose the bootmenu). You can still backup old rootfs to mmc before reflash in case you need to boot it or want some data from it later.
And there's me thinking I've taken good care of my 770! I've only flashed the standard firmware (all OS2005 releases, then enabled r&d mode, then flashed OS2006 beta and final). Yesterday I replaced initfs, that's the full extent of my device flashing! Day to day usage is pretty stable - I have the occasional unexplained reboots (quite rare really) but I thought everyone had these!

I'm guessing if I restore rootfs I'll lose all installed applications etc. so will keep that as a last resort. If I've missed any Sardine repositories I'll add them and try upgrading to Sardine again, and if that still fails I'll consider reflashing my rootfs. However if I've got all the correct repositories that implies the Sardine upgrade may not be usable right now in which case I'll wait some more until it is!

Any idea where Sardine progress can be tracked/monitored (more from a device point of view than x86 desktop env)?

Many thanks for all your help!
 
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#12
Originally Posted by Milhouse
What other repositories should I add? I read some documentation on the Sardine Wiki that suggested the above repositories were all that I required.
The list is OK. I thought you mentioned only sardine and tableteer repository but you have maemo2.0 too. This should be enough.

Originally Posted by Milhouse
I have the occasional unexplained reboots (quite rare really) but I thought everyone had these!
Yes, one such reboot is enough to produce such warnings in the log (Empty flash at ... - jffs2 is a bit counfused that it found free flash not already marked as free, it is OK but not expected. Wrong data CRC in data node at ... - this is probably OK too but I don't understand why, just have read somewher these are OK, it is only jffs2 notice, not error)

Originally Posted by Milhouse
I'm guessing if I restore rootfs I'll lose all installed applications etc. so will keep that as a last resort. If I've missed any Sardine repositories I'll add them and try upgrading to Sardine again, and if that still fails I'll consider reflashing my rootfs. However if I've got all the correct repositories that implies the Sardine upgrade may not be usable right now in which case I'll wait some more until it is!
It seems you did nothing wrong. I smell rotten sardine

Originally Posted by Milhouse
Any idea where Sardine progress can be tracked/monitored (more from a device point of view than x86 desktop env)?
No idea, I haven't tried it yet. I'm waiting for bigger MMC card for sardine partition.
Originally Posted by Milhouse

Many thanks for all your help!
I think I did not help at all :-)
Please let us know if you upgrade to Sardine successfully in future.
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#13
Further news... battery+xterm would result in a reboot just reformatting the second partition... when it did succeed, rsync would cause a reboot. Didn't get as far as testing with ssh+mains - there's obviously something very wrong.

Have now reflashed again. It would appear that the following messages:
Code:
[  545.320098] Empty flash at 0x00007ffc ends at 0x00008000
[  545.320312] Empty flash at 0x0000fffc ends at 0x00010000
[  545.320495] Empty flash at 0x00017ffc ends at 0x00018000
are caused by flashing with the reduced sized initfs (needed to install the boot menu).

With the fresh image, reduced size initfs, boot menu, xterm, sshd, rsync and e2fsprogs I'm now trying again...
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#14
So far so good - mk.ext2fs and rsync'ing OS2006 to mmc worked without a hitch (over ssh+battery)... now to upgrade to Sardine!!
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#15
Bah! Looks like the on-device upgrade for Sardine is still broken, there are still tons of dependency problems resulting in a failure to boot

Oh well, at least my device seems a bit more stable!
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 15:55.