I upgraded my N800 it works fine , of course have to reflash for boot from SD

I updated last night (n800) and got stcuk in the "unable to power off/no wifi" then endless boot loop.

So... I reflashed using the Nokia utility and all is well. And I didn't even mind havign to reinstall stuff since I just recently jumped back in to the NIT world and had installed way too much crap over the last week as it is.

Has anyone figured why this updated borks selected tablets yet?

Fanoush, thank you sir.

your boot loader menu is what makes the 512meg-non-removable-intarnal-flash tablet trully increadable instead of pretty good. It's been the foundation of my system installs since I first hit that crippling limitation with the N800.

Now, it tripple boots internal, os2007 and os2008 though my n810 remains a dual boot (may try os2007 against it just for fun).

I don't believe even half the possabilities of the hardware have yet been explored and what is possible already is enabled now only by your initfs loader.

(now, if I could only figure out an elegant way to avoid needing to reclone and reinstall my SD partition after initfs-flasher and diablo-kernel updates chew it each major release. But, that's a completely seporate issue for me to figure out.)

Er? Why in the world would you need to reclone to the SD card after updating the initfs? :\

I have to reclone after initfs-flash and diablo-kernel updates though the semi-rolling distro aproach is much better than the complete image flash previous aproach.

One thing that may help you though as I haven't used the backup function when updating. I use the following:

internal flash hosts a clean OS install as cloning base and "rescue boot"

internal SD holds the default n810 data it ships with plus the memory swap file.

external SD holds partitions
- fat32 storage partition 4.5 gigs for media, documents, package archives and anything else I can fit
- ext2 storage parition 1.5 gigs for my cloned OS with breathing room for my system build.

When I do a initfs and kernel update (in this case, a major version OS update) I copy /home/user to /home/userback.

Once booted from the internal flash, I let update all get all the packages including initfs and kernel then unpack the latest boot menu from Fanoush. I don't use the auto cloning scripts though they are a handy reference to pluck specific lines from.
- mount the internal flash block as read only to /mnt/tmp.
- mount the ext2 partition from the SD as /mnt/floppy.
- under /mnt/floppy, remove all directories except /mnt/floppy/home
- under /mnt/floppy/home, remove /mnt/floppy/home/user if you like but don't remove that ./userback directory tree
- clone /mnt/tmp (internal flash) too /mnt/floppy (SD ext2 partition)
- do your initfs_flasher steps from Fanoush's tarball, the script that only rebuilds an flashes the initfs
- reboot from SD and make sure the clean clone works
- copy any config files and directories from /home/userback to /home/user. I usually copy the directories or MyDoc at least then the .files as needed after I reinstall each prefered application.

I've done this since os2007 with a nice smooth transition of config and saved data each time. With my data primarily stored on the SD's fat32 parition, it is mostly just copying config files back into place.

How did you get 512meg-non-removable-intarnal-flash?
Is that an upgrade I missed?

Your actually better off without a functioning auto-check for your email. There is some security risk in having apps anounce you out over the wifi automatically when connected. Especially if your not using spop/smtps. Making involuntary noise when connected sucks but trumpetting your uname/passwd every five minutes would be much worse. I find it as easy to hit the update button when I'm ready to check for new email. My email clients on the workstations at home don't even auto-check.

Try the MyTube if it keeps giving you grief. I've had good luck using MyTube exclusively for youtube video viewing.

Um, yeah, I don't think you understand what the initfs and kernel flashing procedure does. It doesn't touch your rootfs on either the internal NAND nor any partitions on the card.

There is no need to reclone, all of your information is still there, you just have to reflash the initfs so you can boot from the card. . . .

I'm trying to figure out an elegant way to do the same. using rsync to duplicate only the changed files to the SD clone was one thought I had. I'm going to try updating the internal flash install, fanoush's initfs then the SD in that order first though. the internal update means the newer initfs can be rebuilt with the boot menu then the SD can be updated from the repositories to keep it in sync. It may mean a second initfs flash for the boot menu after though.

A tip; don't do half an update on the SD isntall then reboot. I updated a few of the NIC related packages from the top of the list then hit some packages asking for dependencies. I figured I'd finish the surgical update later and rebooted. My wireless radio has stopped functioning after the reboot now though so it must have had some other dependencies or modules in the kernel that are not package dependencies. I expect updating the clean internal flash install will be a non issue with the "update all" button or an apt-get update && apt-get upgrade since the wifi issue should only be effecting my SD install. If not, I'll do a complete reflash and build it all up from the bottom again.

Thought it was worth mentioning so other's can avoid chewing there wireless connectivity unexpectedly.