I like that last bit, and after this particular install (I tried it with an empty documents folder guy before the thread reached consensus that it was a problem, thus reboot loops*) I will be using the -f install for future SSU's. However, I was wondering why can't that be part of every SSU that nokia sends our way, IE why doesn't that run to begin with and report back if problems are encountered, or continue if they are not? Is there something crazy about that idea? if not, who would I recommend that too?


*I did revert my tablet to a more "stock" form before the SSU but alas...

Hi all;

I'm glad I checked before applying this latest Seamless update.

I'm beginning to wonderf if dual-boot really buys me anything. With dual-boot, I'm always installing everything twice; once to SD, once to flash. I'm always afraid to install SSUs before Fanoush updates his stuff.

I've not been on the forums much because my n810 is essential for my job. I use it daily to accomplish critical tasks - mostly via VPNC and VNC, sometimes via OpenSSH. I use Garnet VM every 10 minutes or so. I have all the apps I need and don't plan to add any more. I've pretty much given up on ever seeing signal strength in Kismet; that's the only thing I need that I don't already have.

I originally went to dual-boot to my 8GB SD card because I was afraid of running out of memory for apps, but because I always update my flash to match my SD app-for-app, I guess that means that my Flash can handle the apps I have installed.

Seriously considering reverting to flash-boot only, formatting the 8GB card for data, and just being a quiet, safe user while I wait for Chrome or Firefox or something that works better than the slow, inadequate microB.

Suggestions welcome,as always.

$teve

Given what happened with this SSU, I don't think that would be a bright idea.
You always want to be able to boot from mmc, because if something bad happens...but to do that you don't really need bootmenu (modified initfs)
Put the stock initfs and configure the tablet to boot from mmc ("flasher-3 --set-root-device mmc").
You can then:
Boot always from mmc, you can keep flash syncronized or not. If your system breaks or you want to boot from flash, turn off the tablet,extract the mmc card, and turn it on (it will boot from flash), and insert the mmc card later. Backups are very easy to do, keep and restore, just using tar.
Put a mmc without a linux system in it, and keep another mmc with a bootable system (a rootfs backup or debian) at hand, and keep flashable backups there. If your system breaks, you boot from that mmc card and restore the system.

I'd forgotten about my internal flash partition, kept it several versions behind, and was just using the normal one -- and I've spent days working on trying to my my tablet working in the wake of this "seamless" update. The internal flash backup is great. You can use your tablet when you really need it, and instead of reinstalling everything each time the seamless update wrecks your tablet:
http://www.internettablettalk.com/fo...8&postcount=31

You can use the partition installed to your internal SD to make a full backup of your flash-installed partition, and restore it. (fanoush is amazing.) You don't need a full 2gb or 8gb or whatever, either -- my sd install partition is only 1 gb, with the rest for data. If you use your n810 for a job, I'd *really* recommend keeping a backup partition -- even if you don't ever use it normally, you can get at your other data and use it in a pinch.

I reflashed my N810 with 770Flasher on my Mac and had no problems. Well, IIRC, Step 3 was incorrect: I still had to select the firmware image from the file selector, but that was easy to guess.

A success story for a change... ssu update wwent well for my n800, both on flash as on sd, even though I had removed the pdfs etc from my homedir, and off courrse had to reinstall bootmenu twicce.

The good: button hang seems fixed
The bad : videocenter does not seem to work, and less stable overall(full tablet crashes every 2 days, and desktop crash almost daily.

Overall, the best version of os2008 for my n800 yet (Chinook was terrible). Kudos to nokia for the shorter time to fix.

Since latest SSU, I've been experiencing problems when using microb. Sometimes the whole system crashes and reboots on its own. Other times it looks as if all browser windows have crashed and closed--no more world icon on the left indicating a browser window is open--and yet a browser window IS open, with "browserd" as its heading at the top.

Anyone experiencing anything similar?

Since my reflash I havent had the same crashing/freezing issues. however I did have one episode where the "browserd" showed up. I am wondering what that is, where it derives from. This is a freshly flashed machine, I have installed VGBA iNES, evince, fbreader, and GVM only. dunno if my user actions count as "wierd" or ill advised, but the crash sure was.

browserd is a daemon introduced in diablo to act as a kind of browser crash handler or something so that only the window relevant to the troublesome page crashes, not all browser windows...

but this is very much iirc...

Yes, but well before the update:

https://bugs.maemo.org/show_bug.cgi?id=3627