Seamless Software Upgrade v4.2008.36-5 is out!

[lm2]

SSU hiding problem solved. General Antilles put his finger on it at the beginning of this thread, but I didn't put 2 and 2 together.

Seems my osso-software-version had been deleted. How, I know not. I certainly didn't do it directly. Anyway, for my n800 I did "apt-get install osso-software-version-rx34" and the OS2008 Feature Upgrade 36-5 finally showed up in app manager.

Use "apt-get install osso-software-version-rx44" for the n810.

Now here's hoping I don't get the reboot loop...

UPDATE: Everything installed OK, and I now have pre-ssu diablo on flash, and 4.2008.36-5 on SD (with "About product" showing proper versions in each case).

[BrentDC]

will this work for N810 internal memory boot;

1. update internal memory
2. update flash
3. install boot menu deb.

After this can i boot with updated os from internal memory?

If you're talking about penguinbait's bootmenu.deb, then unless he updated it already, I don't think so.

Installing bootmenu is simple enough, though. Especially if you previously had a working installation via penguinbait's stuff.

Download the newest init_flasher (link posted by fanoush earlier in the thread) to an ext2/3 partition (~/MyDocs/.documents/ will do), then untar it, cd to where you untarred it, then copy your existing bootmenu.conf file (I think it's in /root/install-tools/) to your current directory, then run ./init_flash

That worked for me.

Err, that was from yesterday's memory, so I may have botched some names/directories, but you get the point.

[Linear2202]

Facebook and Hotmail give me browser unsupported messages.

[tso]

facebook was doing that before the latest ssu iirc, try the user agent switch.

the basic problem is that microb is not id-ing itself as firefox, and facebook wants to make sure their ajax features work...

[jpt000]

I wasn't getting the update either so I did the "apt-get install osso-software-version-rx44" on the n810. I am now getting the infamous reboot loop (before the update...). I needed a fresh flash anyway...

[frethop]

Is there a way to force a Diablo update...? I'm still waiting for it to show up on my device.

[lm2]

Is there a way to force a Diablo update...? I'm still waiting for it to show up on my device.

If it doesn't show up when you go to app manager>check for updates and hit that circular icon on the bottom right corner, then you might have to do this (http://www.internettablettalk.com/forums/showpost.php?p=228881&postcount=251).

[BrentDC]

Penguinbait updated bootmenu installer! See http://www.internettablettalk.com/forums/showpost.php?p=228900&postcount=24

[briand]

Y'know... I read through some 200-odd messages here yesterday, mostly preaching doom and gloom regarding this update... I was almost trepidatious when I arrived within my WiFi zone last night...

. I had development stuff on the tablet
. I had SVN versions of software on the tablet
. I had the "browser fix" .deb installed on the tablet
. I had bora, chinook, and diablo apps installed on the tablet
. I had no problem with Modest not notifying me about mail (IMAP/Gmail), but didn't want one, either.
. Regardless, I chose to "install"
. Immediately got a message about the "browser fix", so I removed that via the Application Manager, and chose to 'install' the upgrade.
. I have had no problems whatsoever!

okay, okay... The "contacts" applet was on my screen... and the Tableteer applet was on the screen, but c'mon... that's easily solved. Yeah, a bunch of PDF documentation was re-installed in my documents directory, but I cleaned it out without trouble... and, yeah, my extras repository was disabled, so I re-enabled it.

No rebooting loops, no removing batteries, no reflashing the tablet, and no real issues... reading here, one might think that I was the exception to the norm -- but I'm willing to bet I'm just being more vocal about my experience than the rest of the 'silent majority'.

[frethop]

If it doesn't show up when you go to app manager>check for updates and hit that circular icon on the bottom right corner, then you might have to do this (http://www.internettablettalk.com/forums/showpost.php?p=228881&postcount=251).

Very cool. That did it. Thanks,.

[Benson]

. I had development stuff on the tablet
. I had SVN versions of software on the tablet
. I had the "browser fix" .deb installed on the tablet
... I had some -dev packages from the SDK forcing me to keep the corresponding binary packages back a version.
. I had bora, chinook, and diablo apps installed on the tablet
. I had no problem with Modest not notifying me about mail (IMAP/Gmail), but didn't want one, either.
. Regardless, I chose to "install"
. Immediately got a message about the "browser fix", so I removed that via the Application Manager, and chose to 'install' the upgrade.
... Got a message about the ~4 packages I'd held back for the SDK, did apt-get install on them, and went back to App Mgr.
. I have had no problems whatsoever!

okay, okay... The "contacts" applet was on my screen... and the Tableteer applet was on the screen, but c'mon... that's easily solved. Yeah, a bunch of PDF documentation was re-installed in my documents directory, but I cleaned it out without trouble... and, yeah, my extras repository was disabled, so I re-enabled it.

No rebooting loops, no removing batteries, no reflashing the tablet, and no real issues... reading here, one might think that I was the exception to the norm -- but I'm willing to bet I'm just being more vocal about my experience than the rest of the 'silent majority'
+1 to that, except for the expected fooling around to get the update across two images of my (nominal) penta-boot, a rescue SD, and of course restore my boot-menu. And the SDK stuff, I knew I was on thin ice, but I'd made pretty sure of what I'd have to do back when I installed it... :D

[BrentDC]

+1 to that, except for the expected fooling around to get the update across two images of my (nominal) penta-boot, a rescue SD, and of course restore my boot-menu. And the SDK stuff, I knew I was on thin ice, but I'd made pretty sure of what I'd have to do back when I installed it... :D

Public Service Announcement:

If you have a virgin, straight out-of-box, brand new device, please do not install this update.

If you use kernel patches, have rotation enabled, frequently use the SDK repo, hacked system files, dual boot, use powerlaunch: you are good to go.

:D

[ioan]

On my n800, I enabled the soft poweroff in systemui.xml... but every time when I put the tablet in soft power off, the d-pad led is blinking. In control panel->display->led all the check boxes are unchecked. Does anyone else have this problem?

I don't have new emails (I don't use the email app on the tablet), I don't use any kind of alarm on the tablet. I reflashed yesterday and installed the two OS updates, so this is a clean tablet.

Any ideas?

[skatebiker]

I installed SSU from the notofication without problems.
Everything browser, youtube, SIP calling, MSN via Pidgin works.

It also restarted automatically.

[GeneralAntilles]

It would be interesting to have a site poll under this subject regarding the success or failure rate of this (or any) software update.

No it wouldn't. It would be just as useful as the responses to this thread. A self-selecting sample that doesn't represent the actual experience for most tablet users.

[nhanquy]

I had my N810 updated when it was running on mmc2 late last night. The tablet kept rebooting a couple times then booted from flash. The boot menu was gone. I shut it off.

This morning I plugged it to the AC adapter. It kept rebooting itself at least 5 times and then booted from flash. I lost the boot menu. I re-run the initfs_flasher; funny thing was it did not ask for dropbear and such but it configured the tablet the way it was.

I rebooted the tablet. It went to boot from mmc2 and said "software updated".

I haven't tested any software on the tablet yet.

[thaldyron]

I've updated when booted from the internal card. The installation phase succeeded but the configuration failed so I used dpkg --configure. After rebooting it shows the correct version but the bootmenu and everything works without me flashing the initfs.
How's that possible?

[deluxe]

Let me add a sad little "me too" to this. Constant reboot loop, going to have to re-flash. All my data is safe on the card, but it's going to be a pain to have to reinstall all my apps.

I had an initial issue with the update not flashing due to the Flash Version I had installed a few weeks ago, so I removed that and it installed OK. Then, when it rebooted it got stuck in a reboot loop. I had the power adapter plugged in, so I unplugged it and it booted fine next time. Seems to be all OK now(have been using it off and on for 3 hrs). This is a simple fix that might work, and sure beats rebuilding the whole OS and Apps.

[deluxe]

No problems so far!
The browser is really fast!

Was Flash in fullscreen (youtube) possible before? I can't remember.

It was for me, full screen.

[deluxe]

You may be right. But one amazing feature I think is RSS feeds get updated even if my RSS feed reader is not kept launched, only thing I need to do is keep my internet tablet switched on and connected to internet. but the same happen with gpodder or other rss parsers.

That seems to happen for me too, providing I have the W-Lan connection running, and thet the refresh setting is enabled within the RSS reader App.

[Texrat]

reading here, one might think that I was the exception to the norm -- but I'm willing to bet I'm just being more vocal about my experience than the rest of the 'silent majority'.

Probability is on your side. People tend to express problems, but not satisfaction...

[st5150]

SSU hiding problem solved. General Antilles put his finger on it at the beginning of this thread, but I didn't put 2 and 2 together.

Seems my osso-software-version had been deleted. How, I know not. I certainly didn't do it directly. Anyway, for my n800 I did "apt-get install osso-software-version-rx34" and the OS2008 Feature Upgrade 36-5 finally showed up in app manager.

Use "apt-get install osso-software-version-rx44" for the n810.

Now here's hoping I don't get the reboot loop...

UPDATE: Everything installed OK, and I now have pre-ssu diablo on flash, and 4.2008.36-5 on SD (with "About product" showing proper versions in each case).

Thanks, what's wrong with my setup though?


apt-get install osso-software-version-rx44
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package osso-software-version-rx44 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
osso-software-version-unlocked
E: Package osso-software-version-rx44 has no installation candidate

[Scythe]

It worked like a charm for me. Faster browser (seems to scroll a lot better). I also didn't notice it before, but there's an ability to set a cache max value in the settings. I'm sure it's been there for awhile, I just never realized it.

[benny1967]

Probability is on your side. People tend to express problems, but not satisfaction...

Me satisfied.

Even found one very annoying bug (https://bugs.maemo.org/show_bug.cgi?id=3304) fixed.

I want Nokia to release updates more frequently, so: It felt great! Do it again!

[lm2]

Thanks, what's wrong with my setup though?

This is beyond my abilities to answer. I assume it's not as simple as noting that the osso version you're trying to install is for n810 not n800??

[deluxe]

I skeptically updated last night, and voila, i am now running 2008.36-5 on my N800. Update went without any issue. My only annoyance so far is that the RSS feed applet still doesn't update as it did under Chinook. Browser speed increase? Not sure I see what others, including Texrat have reported - my GMail still loads the AJAX site in about 30 seconds - no different than before.

Wow, I just ran a quick test load of Gmail. With the browser already open to another site, it takes my n810 exactly 5 seconds to load and fully display my Gmail inbox. This is quite a bit faster than pre-update, but I am not sure exactly how much, as I never run that test before.

[Peet]

No it wouldn't. It would be just as useful as the responses to this thread. A self-selecting sample that doesn't represent the actual experience for most tablet users.

For a community rep you can sometimes be quite... uncompromising with your approach to suggestions.

In the following part of my message (which you omitted) I pondered whether such a "community poll" (with followup query) could help pinpoint system setups that are more prone to "SSU" failure than others.

But hey, I got the message that the idea wasn't interesting to you. There's of course the danger that some silly person might indeed take the result of such a poll as being representative of the whole tablet userbase and who knows what undesirable shenanigans might follow from that!

It certainly wouldn't be interesting to the self-selecting sample which frequents ITT (and possibly tends to install more 3rd party apps than the average Joe) as a quick reference of what to pay attention to wrt. potential breakage.

Anyway, thanks for the Maemo Community Chair opinion.

(Is that as in a Nokia-paid rep to the community, or community's rep to Maemo/Nokia?)

[st5150]

This is beyond my abilities to answer. I assume it's not as simple as noting that the osso version you're trying to install is for n810 not n800??

It's a n 810. Anyone know why I can't upgrade? Nothing showed up in app manager, but I ran a apt-get upgrade and everything seemed to install, except nothing was flashed and it's still showing as 2008.30-2 even though I believe I the new browser and everything else installed. Anyone want to take a stab at my problem?

[Linear2202]

I have used the user agent switch app, and it works ok. It's just disappointing that it needs to be used in the first place.

Otherwise, the update has worked great for me, very appreciative of the work being done.

[gochito]

I got the reboot loop , had to reflash my tablet for the first time since Diablo.

Looks good, lost all the programs, but I think that I'll take this opportunity to clean up my repositories list :-)

[GeneralAntilles]

For a community rep you can sometimes be quite... uncompromising with your approach to suggestions.


It's part of my charm. ;)


In the following part of my message (which you omitted) I pondered whether such a "community poll" (with followup query) could help pinpoint system setups that are more prone to "SSU" failure than others.


I did skim more than I intended, and assumed you intended some sort of poll to "prove" how "broken" the process was. I'm sorry.

I'm not particularly hopeful about people's abilities to diagnose their own symptoms here, and don't think a poll is going to be the most useful of approaches. I'd rather just try to figure it out person-to-person (as I've been doing elsewhere), than shotgun a list a guessed causes and get people to tick boxes.


Anyway, thanks for the Maemo Community Chair opinion.


Anytime.


(Is that as in a Nokia-paid rep to the community, or community's rep to Maemo/Nokia?)

:rolleyes:

[la3875]

Spoke too soon... Got the update notification again today and watching traffic here I found that reflashing actually took me backward. Took the chance again and got into the reboot loop again. Only thing I can think may be contributing to this is leaving the mini SD card in place during update?

[Texrat]

Leaving the mini SD card in should not, in and of itself, interfere with SSU.

[debudebu]

Nope, mine still randomly silently crashes and I have to reboot the device to open the program and check my mail. I just LOVE that! The main reason I bought this unit is to keep tabs on my e-mail. It worked pre-diablo flawlessly, and now, even after two useless updates later doesn't. Oh yea, I keep forgetting, we're talking about software developers (oops, EXCUSE ME, "engineers") here. Perhaps by Christmas, 2010

this happens with mine too. gmail pop3

[st5150]

Help! What have I done? I'm afraid to reboot!


~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
w busybox dnsmasq hildon-application-framework-rx34-rx44 libconbtui0 libicd-network-dun maemo-pan netbase omweather
osso-applet-device osso-bluez-compat osso-connectivity osso-connectivity-ui osso-connectivity-ui-btsettings
osso-connectivity-ui-conndlgs osso-connectivity-ui-connmgr osso-connectivity-ui-gwsettings osso-connectivity-ui-gwwizard
osso-connectivity-ui-iapsettings osso-connectivity-ui-statusbar osso-core osso-core-busybox osso-filemanager ppp
The following NEW packages will be installed:
bash bsdutils coreutils debianutils e2fslibs e2fsprogs grep gzip host libacl1 libattr1 libavahi-core5 libblkid1 libcomerr2
libss2 libuuid1 mktemp mount ncurses-bin sed slang1a-utf8 tar util-linux
The following packages have been kept back:
canola2
The following packages will be upgraded:
avahi-daemon
1 upgraded, 23 newly installed, 24 to remove and 1 not upgraded.
Need to get 6625kB of archives.
After unpacking 10.6MB of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
bash bsdutils libattr1 libacl1 coreutils mktemp debianutils e2fslibs libblkid1 libcomerr2 libss2 libuuid1 e2fsprogs grep gzip
mount ncurses-bin sed tar slang1a-utf8 util-linux libavahi-core5 host avahi-daemon
Install these packages without verification [y/N]? y
Get:1 http://debfarm.free.fr chinook/user e2fslibs 1.40.3-1 [113kB]
Get:2 http://repository.maemo.org diablo/sdk/free bash 2.05b-26osso4 [637kB]
Get:3 http://debfarm.free.fr chinook/user libblkid1 1.40.3-1 [46.3kB]
Get:4 http://repository.maemo.org diablo/sdk/free bsdutils 1:2.12p-4sarge1.osso4 [66.5kB]
Get:5 http://repository.maemo.org diablo/free libattr1 1:2.4.43-1 [10.3kB]
Get:6 http://debfarm.free.fr chinook/user libss2 1.40.3-1 [38.2kB]
Get:7 http://repository.maemo.org diablo/free libacl1 2.2.47-2 [16.8kB]
Get:8 http://repository.maemo.org diablo/sdk/free coreutils 5.2.1-2osso2 [2710kB]
Get:9 http://debfarm.free.fr chinook/user libuuid1 1.40.3-1 [39.0kB]
Get:10 http://debfarm.free.fr chinook/user e2fsprogs 1.40.3-1 [580kB]
Get:11 http://repository.maemo.org diablo/sdk/free mktemp 1.5-2 [10.3kB]
Get:12 http://repository.maemo.org diablo/sdk/free debianutils 2.17 [50.3kB]
Get:13 http://repository.maemo.org diablo/free libcomerr2 1.37-2sarge1 [26.5kB]
Get:14 http://repository.maemo.org diablo/sdk/free grep 2.5.1.ds1-4 [174kB]
Get:15 http://repository.maemo.org diablo/sdk/free gzip 1.3.5-10sarge1 [79.0kB]
Get:16 http://repository.maemo.org diablo/free mount 2.12p-4sarge1.maemo1 [135kB]
Get:17 http://repository.maemo.org diablo/free ncurses-bin 5.4-3.osso1 [199kB]
Get:18 http://repository.maemo.org diablo/sdk/free sed 4.1.2-8 [203kB]
Get:19 http://repository.maemo.org diablo/sdk/free tar 1.14-2.1osso [508kB]
Get:20 http://repository.maemo.org diablo/sdk/free slang1a-utf8 1.4.9dbs-8 [299kB]
Get:21 http://repository.maemo.org diablo/sdk/free util-linux 2.12p-4sarge1.osso4 [413kB]
Get:22 http://repository.maemo.org diablo/free libavahi-core5 0.6.23-2maemo3 [109kB]
Get:23 http://repository.maemo.org diablo/free host 20000331-9 [75.0kB]
Get:24 http://repository.maemo.org diablo/free avahi-daemon 0.6.23-2maemo3 [86.6kB]
Fetched 6625kB in 40s (162kB/s)
(Reading database ... 27674 files and directories currently installed.)
Removing osso-connectivity ...
Removing libicd-network-dun ...
Removing osso-connectivity-ui ...
Removing osso-connectivity-ui-statusbar ...
Removing osso-connectivity-ui-btsettings ...
Removing osso-connectivity-ui-connmgr ...
Removing osso-connectivity-ui-iapsettings ...
Removing osso-connectivity-ui-gwsettings ...
Removing osso-connectivity-ui-conndlgs ...
Removing osso-connectivity-ui-gwwizard ...
Removing libconbtui0 ...
Removing osso-filemanager ...
Removing hildon-application-framework-rx34-rx44 ...
Removing osso-applet-device ...
Removing osso-bluez-compat ...
Removing maemo-pan ...
Removing bluez-utils ...
Stopping bluez-utils: hcid.
Removing osso-core ...
Removing osso-core-busybox ...
Removing omweather ...
Removing ppp ...
Stopping all PPP connections...done.
Removing dnsmasq ...
Stopping DNS forwarder and DHCP server: dnsmasq.
Removing netbase ...
dpkg: busybox: dependency problems, but removing anyway as you request:
sysvinit depends on busybox | coreutils; however:
Package busybox is to be removed.
Package coreutils is not installed.
Package busybox which provides coreutils is to be removed.
osso-core-config depends on busybox | coreutils; however:
Package busybox is to be removed.
Package coreutils is not installed.
Package busybox which provides coreutils is to be removed.
lsb-base depends on sed; however:
Package sed is not installed.
Package busybox which provides sed is to be removed.
sysvinit depends on busybox | coreutils; however:
Package busybox is to be removed.
Package coreutils is not installed.
Package busybox which provides coreutils is to be removed.
osso-core-config depends on busybox | coreutils; however:
Package busybox is to be removed.
Package coreutils is not installed.
Package busybox which provides coreutils is to be removed.
Removing busybox ...
dpkg-deb (subprocess): failed to exec tar: No such file or directory
dpkg-deb: subprocess tar returned error exit status 2
dpkg: error processing /var/cache/apt/archives/bash_2.05b-26osso4_armel.deb (--unpack):
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
/var/cache/apt/archives/bash_2.05b-26osso4_armel.deb
E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/sbin/docpurge ]; then /usr/sbin/docpurge; else exit 0; fi'
E: Sub-process returned an error code
E: Sub-process /usr/bin/dpkg returned an error code (1)



Virtually nothing is working now! I have one active SSH session that is kind of working.......

Is there a way to install what was removed using apt-get and the debs I have left in /var/cache/apt/archives ?

[doubledee]

went online for the first time in a week or so, update icon showed up quickly, update went totally smoothly, no probs!

browser does seem a bit quicker

all good!

[mwiktowy]

Y'know... I read through some 200-odd messages here yesterday, mostly preaching doom and gloom regarding this update... I was almost trepidatious when I arrived within my WiFi zone last night...

...

No rebooting loops, no removing batteries, no reflashing the tablet, and no real issues... reading here, one might think that I was the exception to the norm -- but I'm willing to bet I'm just being more vocal about my experience than the rest of the 'silent majority'.

So that (and GA and several other "power-users" reporting no big issues) kind of blows away the theory that it is only power-users have this reboot-loop issue.

So let's try to find the common thread that is definitely causing some issues with many people that are not using their tablets in exotic ways.

The only things that I had on my tablet that could possibly be considered non-standard are:
1) rtcomm beta
2) chinook base and extras repos in order to install some old apps that hadn't been moved over.

Are either of these two commonalities anong other people having issues that don't fit into the "5 stages of self-doomed hackerdom" as outlined by Jaffa?

PS ... just to add that it is an N810 that I have that I had SSU issues with.

[tso]

rtcomm was installed here, but i removed it partially to make sure i had enough free space (libpurple wanted pidgin-data, and takes up about 20MB).

chinook base and extras disabled here...

[Andyjenk]

Received the update message about an hour ago. Had to clear some space for it otherwise nothing unusual. AFAIK I don't have rtomm beta but may have chinook base and extra repos, tho I don't think I have Chinook installed. I'm getting the "won't shut down - pulled battery - start loop". I've got 2X 4Gb SDHC cards anyone ideas as to what else could be common?

[Jaffa]

Are either of these two commonalities anong other people having issues that don't fit into the "5 stages of self-doomed hackerdom" as outlined by Jaffa?

...which, of course, was supposed to be an example list; not definitive (if I knew, I could fix the problems ;-))

rtcomm-beta's an interesting idea. qole had that installed at the summit, might prove to be a data point.

[Benson]

Help! What have I done? I'm afraid to reboot!Excellent! Rebooting now would make things quite hard to recover indeed.



Virtually nothing is working now! I have one active SSH session that is kind of working.......

Is there a way to install what was removed using apt-get and the debs I have left in /var/cache/apt/archives ?
Looks like you've attempted to upgrade with the SDK repo enabled, causing conflicts with busybox.

I'm not familiar enough with Debian packaging to be sure what you should do from here, but I think none of that would work anymore. As I understand it, you are currently stuck with no tar, and probably no shell, so installing packages may not work...

First order of business, then, would be to get busybox back on, and all relevant links reinstated. You've got a busybox in /mnt/initfs, but it's linked against a different libc, so you can't just drop it in here...

All I'm thinking is to rip busybox out of another system (on an SD, if you have one).

[Andyjenk]

A quick look thru this thread shows we're talking N800s and N810s. It's not simply a case of OK for N810, not OK for N800, is it?
Sorry, I havent had time to read all 30 pages...

[Benson]

There have been a couple of observations that N800s are fine and N810s break, but it's not that simple. While more trouble is reported with N810s, some N810s went fine, and some N800s failed; I don't think there's a significant correlation.

[briand]

as a data point, then...

My unit is an N800, not an N810

I don't have rtcomm-beta installed.


...but, I do have Pidgin (and, thus, libpurple) installed from the Chinook extras repository.

[st5150]

Thanks! So you said:

Excellent! Rebooting now would make things quite hard to recover indeed.




Looks like you've attempted to upgrade with the SDK repo enabled, causing conflicts with busybox.

I'm not familiar enough with Debian packaging to be sure what you should do from here, but I think none of that would work anymore. As I understand it, you are currently stuck with no tar, and probably no shell, so installing packages may not work...

First order of business, then, would be to get busybox back on, and all relevant links reinstated. You've got a busybox in /mnt/initfs, but it's linked against a different libc, so you can't just drop it in here...

All I'm thinking is to rip busybox out of another system (on an SD, if you have one).


I have gtar and I have a SSH shell, but no ls, cp, etc. I manageed to gtar up my archives and /home directories. How do I use apt-get to install a local .deb in my archives directory? Yes I have busybox in /mnt/initfs/bin but I can't seem to execute anything there. I'm also running this OS off of SD, so I suppose I *could* reboot to the flash OS, mount the SD OS and ah, I'm freaking out, can you or anyone give me a roadmap or have I fubar?

[twaelti]

N810, failed :-(
(After the update, hardware buttons didn't work anymore, so I was unable to reboot. Had to remove the battery. Now stuck in endless rebooting loop)

[SVC]

Are there other ways to re-flash on Windows than through the Nokia software program? I've got the booting problem for one of my tablets (n810), but the update wizard doesn't recognize it (pushing the upper one on the tablet's front).

Have others had success on flashing with the wizard? Most of the posts in the thread seem to concentrate on other platforms.

[Bundyo]

@st5150: Any dpkg? :)

[st5150]

@st5150: Any dpkg? :)


yes!



:/etc# dpkg
dpkg: need an action option

Type dpkg --help for help about installing and deinstalling packages ;
Use `dselect' or `aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;
Type dpkg --license for copyright license and lack of warranty (GNU GPL) .

Options marked produce a lot of output - pipe it through `less' or `more' !


I've never used dpkg though... help?

ps- want to "talk" in my other thread to keep this one from being further cluttered? http://www.internettablettalk.com/forums/showthread.php?t=23986

[danramos]

Probability is on your side. People tend to express problems, but not satisfaction...

Also, disagreements. I disagree. :)

But hey, I got the message that the idea wasn't interesting to you. There's of course the danger that some silly person might indeed take the result of such a poll as being representative of the whole tablet userbase and who knows what undesirable shenanigans might follow from that!

If I see the word 'shenanigans', one more time... :P

It's part of my charm. ;)

HEY! I think I might have charm too! :D

There have been a couple of observations that N800s are fine and N810s break, but it's not that simple. While more trouble is reported with N810s, some N810s went fine, and some N800s failed; I don't think there's a significant correlation.

...and finally, for my one serious answer in this reply...

I have an N800 and it failed for me the first time. I had to flash back to the original Diablo release and then let it update until it was finally up-to-date.

[danramos]

I've never used dpkg though... help?

Quickie answer here: dpkg -i packagename.deb

[mwiktowy]

...which, of course, was supposed to be an example list; not definitive (if I knew, I could fix the problems ;-))

Ya ... I realize that. I was just being sarcastic since people seemed to be using that as the canonical list of reasons why they should entirely dismiss people having issues.

rtcomm-beta's an interesting idea. qole had that installed at the summit, might prove to be a data point.

It is pretty intrusively replacing core bits but I found it really stable.

I am pretty sure that I had rtcomm-beta install before the last SSU and it went fine. There may have been an update to rtcomm-beta since then though. So if that is the culprit, that would narrow down the list of causes. Maybe I will reflash back to the old firmware again and try to cause it just by installing that one package.

Is it possible to cleanly "uninstall" the SSU package and revert back the the pre-installed state or is it the case where the SSU package is just a meta package that drags all the required updates in and is non-reversible?

[alephito]

I did not have rtcomm-beta nor pidgin installed in my N810 and suffered the death loop. I had Gizmo, though.

[maacruz]

I have gone through 4 update installations to be finally able to know what fails and gather that information (1->reboot cycle-teeth gnashing, 2->white screen of death-head banging, 3->success, 4->document and check fixes)

I put this here in the hope it can help those of you who haven't still updated to avoid failure.
The first issue is the big update size. Make sure you have plenty of space before trying.
Second, you better make a backup of your system if you haven't done so (see this post http://www.internettablettalk.com/forums/showpost.php?p=33348&postcount=31) and want to avoid a full reflash. Once you have a rootfs backup save the file in your PC to be able to reflash it with flasher, if things go wrong. If you have a bootable system in mmc, just do a tgz backup.

Now, lets start with all the issues I have found:

- The update can't be installed if sliderotate is installed. Simply uninstall sliderotate. Same with certain flash patch, it is documented in this thread (I do not have that patch)

- The update contains 32 deb archives. That in itself is not an issue, but, given how the package manager/apt works, means that if only one of such packages doesn't install, all packages will remain unconfigured leaving the system broken unless fixed by hand. So, for this very reason, use apt-get to install the update, and do not reboot if the update fails unless you have no other option.

- apt and the nokia repositories are updated too, if the update fails, the nokia repositories are borked and you won't be able to fix the system unless you already have all packages. Pre-download all packages first with "apt-get -d install osso-software-version-rx44"

- The update contains a documentation package. This package causes a lot of trouble, because it fails if the user has moved, removed or linked the documentation files:
It fails if there is no files in "/usr/share/pre-installed/MyDocs/.documents/". Create that directory and touch or put a file there if you have that deleted.
It fails if the "/home/user/MyDocs/.documents/osso_software_copyright.pdf" file is a symlink
It fails if the "/home/user/MyDocs/.documents/~sfil_li_folder_user_guides/" directory is a symlink or is empty. Make sure you have an actual directory with any file there.

- The init.d handling scripts are prone to fail, and because dpkg is not robust and/or post-install scripts have poor error recovery, causes the "dangling symlink /etc/rc2.d" problem. This problem doesn't affect everyone, and only happens on some packages. I think it is relate to how the post-install script passes arguments to the "invoke-rc.d" script, but I have to investigate further. In this update, the packages tablet-browser-daemon, mce, ke-recv and icd2 are affected by this problem and their installation will fail.
The best way to get rid of this problem once and forever is to edit the "/usr/sbin/invoke-rc.d" script and make sure it never fails the symlink check. There is already a thread about this in ITT. I have attached the fixed script here, so just copy it to /usr/sbin
A worse way to fix this is to delete the /etc/rc2.d related files (S99tablet-browser-daemon, S21mce, S30ke-recv, S59icd2) when the installation fails, then after successfully installing those packages (using "dpkg -i" because apt-get won't work) you'll have to create by hand those symlinks or otherwise the following things will not work right: usb, screen keyboard, network, power-off button. Those packages are tricky to get installed because they need other packages configured before installing, so you need to run "apt-get -y -f install" before "dpkg -i"

- Do not work through a ssh shell and don't let the tablet enter power-save mode. One of the packages is the network daemon (icd2) and will be shut down when installing, cutting off your shell. Since also mce is being reinstalled and has been shut down too, if you tablet enters power save mode you won't be able to regain control of it or even properly turn it off, leaving no other option than to remove the battery.

- It is possible to reboot with the update not configured if the only packages not installed are tablet-browser-daemon, mce, ke-recv, icd2 and the documentation, and then finish the installation by hand. Failure before that probably means endless reboot cycle.

- If the update has failed but you have been able to complete installation by hand, you have to "flash-and-reboot" to install the new kernel and initfs

[lm2]

The update can't be installed if sliderotate is installed.

While I had my problems with this update, having sliderotate installed wasn't one of them...unless sliderotate was responsible for removing osso-software-version, and uninstalling would have put it back. Even if it was responsible for that, reinstalling osso-software did the trick. Once the system updated, I just reinstalled sliderotate kernel from within sliderotate settings, and I was good to go.

[maacruz]

While I had my problems with this update, having sliderotate installed wasn't one of them...unless sliderotate was responsible for removing osso-software-version, and uninstalling would have put it back. Even if it was responsible for that, reinstalling osso-software did the trick. Once the system updated, I just reinstalled sliderotate kernel from within sliderotate settings, and I was good to go.
It gave me a conflict with xserver-xomap, and didn't go away until I uninstalled sliderotate.

[Benson]

Recent versions of sliderotate do not conflict with osso-software-version-rx?4-unlocked; in any event uninstalling sliderotate would not restore that... Some early rotation packages did force removing an osso-software-version, but I think since the first SSU they've been largely ok.

Removing osso-software-version-rx?4-unlocked is an additional cause, however it happens, and can (AFAIK) only really be fixed ahead of time by installing it again.

[callanish]

I almost feel guilty in saying that my update went off without a hitch, but it did and thank the Gods for that because based on my topsy turvy life, I just need stress free gadgets right now and after a weekend of restoring a windows xp pc from scratch, the last thing I needed would have been a infinite boot loop issue on my N810. Just sort of stunned that so many users are having so many issues with this upgrade.

[Texrat]

Also, disagreements. I disagree. :)

Key word was tend (I even emphasized it in the original post).

And if ya like, I can prove my premise with stats. I didn't get hired as a data analyst for my good looks. :D

[canoehead]

So that (and GA and several other "power-users" reporting no big issues) kind of blows away the theory that it is only power-users have this reboot-loop issue.

So let's try to find the common thread that is definitely causing some issues with many people that are not using their tablets in exotic ways.

The only things that I had on my tablet that could possibly be considered non-standard are:
1) rtcomm beta
2) chinook base and extras repos in order to install some old apps that hadn't been moved over.

Are either of these two commonalities anong other people having issues that don't fit into the "5 stages of self-doomed hackerdom" as outlined by Jaffa?

PS ... just to add that it is an N810 that I have that I had SSU issues with.

I updated two N800's today, and both went fine. I did notice that when the devices were being halted at the end of the update, there was a period of time where the screen went dark, but the device wasn't fully shut down. The screen actually faded twice -- once from the hildon UI down to a powered dark screen (a very odd fade away), then later the LCD powered down completely. It looked down for a while, but wasn't quite.

Once shut down, I could start the devices again with no issues. Pressing the power button let the LED light up, device booted etc.

Are people being patient enough during the halt? Are files being corrupted if the battery is being yanked during the final writes out to flash memory?

Just one observation.

[Benson]

And if ya like, I can prove my premise with stats. I didn't get hired as a data analyst for my good looks. :D

Yep, everyone knows data analysts are hired for creativity, not looks. :p

[danramos]

Key word was tend (I even emphasized it in the original post).

And if ya like, I can prove my premise with stats. I didn't get hired as a data analyst for my good looks. :D

Don't muddy this all up with facts. I go with the truthiness from my gut. You can't trust facts! Heck.. even my spell-checker is nagging at me that 'truthiness' isn't a word--but I know in my gut that it IS a word... and that's a fact. ;)

BTW: HUuuuuuuge thanks to maacruz for gathering all that info and for the constructive suggestions! ...even if they're not a good exercise in truthiness (http://en.wikipedia.org/wiki/Truthiness). ;)

[Texrat]

(OT) LOL... I laughed my *** off at Stewart and Colbert last night. Colbert had Paul Begala in stitches, too. Those guys are enjoying the US political craziness too much. Almost as much as some of you are enjoying the SSU (see how I brought that back on topic?)

[thepenguinonthetelly]

OK, I don't know what the problem was before because the update installed fine today. Weird. Browser is a little faster (especially on this forum), but I'll have to check elsewhere to see if there's a major difference. Anyone know if the battery charge problem still exists (giving false readings, etc)?

[speculatrix]

one thing that now works for me that never did before is that the file manager now lists windows and SMB servers on the lan, which has been a bonus.

also, file manager shows bluetooth devices like my phone, again, it never showed that before.

it does seem slower connecting to wifi.

I've not exercised it enough to comment on speed of the browser.

EDIT: yes, its definitely a bit "snappier". was browser Auntie Beeb's news this morning and pages rendered faster with zoom and full screen switching being very quick - it nearly completed the zooming before the pop-up appeared saying "zoom to 120%". Thanks, Nokia.

[tso]

ok, maacruz's post makes me wonder if the people that did the ssu system at nokia actually understands how .deb and apt-get works...

[sjgadsby]

The only things that I had on my tablet that could possibly be considered non-standard are:
1) rtcomm beta

I have RTCOMM Beta installed on my N810, and I've had no problems with either SSU.

[geneven]

Well, I'm really happy with the fact that all this stuff is in this one thread, so if I have a problem all I have to do is make an in-depth study of 32 pages!!

I just reflashed the old-fashioned way and didn't even restore a backup. Everything is working fine.

[rlauzon]

one thing that now works for me that never did before is that the file manager now lists windows and SMB servers on the lan, which has been a bonus.

Strange. I have the update, but I can't get file manager to see the SMB shares on my network.

I can't seem to find anyway to adjust the settings (like the workgroup name) anyplace. Is there something extra I need to install?

[Benson]

Well, I'm really happy with the fact that all this stuff is in this one thread, so if I have a problem all I have to do is make an in-depth study of 32 pages!!

I just reflashed the old-fashioned way and didn't even restore a backup. Everything is working fine.

OK, welcome to Diablo original completely-non-updated, then... :confused:

There's no FIASCO images for anything since 2008.23-14 that I can find. (On http://tablets-dev.nokia.com/nokia_N800.php, that is.) So while reflashing the old-fashioned way works, it doesn't really help. (Unless you know of an updated image somewhere else? I try to keep the latest image on hand, since last time I trashed my initfs and Nokia's servers were down... So by all means, let us know if you swiped found an image of 36-5!)

[tso]

heh, time for slipstream for maemo? ;)

[tubby17]

Well, with penguinbait's and Benson's assistance, I finally took the plunge and updated my dual-boot (flash/internal mmc) n810. The steps that worked for me are here (http://www.internettablettalk.com/forums/showthread.php?p=229088#post229088). Haven't noticed any substantive changes yet, though I haven't done a lot of testing. I'm just glad that my "should I update/shouldn't I update" internal struggle has been resolved.

Though, OT, I sped up the speed of the browser a LOT a few days ago by uninstalling adblock and installing flashblock.

[Laughing Man]

Did you remove osso-software-version? . . .

Not that I know of. I got the last SSU update and the only thing I did since then was update some programs already installed on there.

[dfinch]

Bought 3 DX cables, only two work.

Interesting! I took my DX cable to work and tried to flash there. Guess what? It worked! So I am now in process of reinstalling everything - this is going to take days (of evenings).

Funny thing about the DX cable is that it does work to connect my N810 at home just for seeing it as an external disk. But it won't flash!!!

Well at least I have a way to update in the future if we get the same disaster. I know many are saying the reboot loop is the exception but if you happen to be a 'victim' it's a disaster.:(

[nilchak]

The update worked fine on my N810 - I was a little afraid what with all the reports of screw ups post update - but nothing happened.

But now on the Backlight applet I dont see the options for the rotation. Cant use the rotation now at all. Where di the rotation menus go from that applet ?

[mwiktowy]

- The update contains a documentation package. This package causes a lot of trouble, because it fails if the user has moved, removed or linked the documentation files:
It fails if there is no files in "/usr/share/pre-installed/MyDocs/.documents/". Create that directory and touch or put a file there if you have that deleted.
It fails if the "/home/user/MyDocs/.documents/osso_software_copyright.pdf" file is a symlink
It fails if the "/home/user/MyDocs/.documents/~sfil_li_folder_user_guides/" directory is a symlink or is empty. Make sure you have an actual directory with any file there.


This covers my scenario. I get rid of all the documentation after every reflash to save the 13 MB and just move the English user manual somewhere else.

Hard to believe that document package script is so brittle.

Thanks for the analysis.

[Texrat]

I usually clear out the unneeded docs, too... glad I forgot this time!

Has that been bugged yet?

[GeneralAntilles]

Has that been bugged yet?

Bug #3602 (https://bugs.maemo.org/show_bug.cgi?id=3602) and bug #3750 (https://bugs.maemo.org/show_bug.cgi?id=3750).

[sachin007]

ya i updated my internal memory first and then flash. installed boot menu and control panel shows both as 36-5.

But app manager shows red exclamation mark and says borked in details in my internal memory partition.

So did it update or no?

[Texrat]

Thanks man. Voted and commented on 3602, voted on 3750.

[Mara]

That might be it: I did remove some preinstalled document files prior to this SSU update.

One suggestion (?) I propose is to have some sort of simulated SSU install option. With this in place it could be seen beforehand if the process is going to fail, without actually updating the system. This should be complemented with a full log file that would pinpoint where the problem is.

[Bundyo]

I had some preinstalled docs trouble too, had to create a folder and an empy document, since the deb setup failed if they're not present.

+1 for deb install simulation (not only for SSU, probably will be best if all debs can be tested).

[Pertti]

Original problem:

I seem to have a major issue with this upgrade on my N800:

Despite the fact that I have ~1GB space left on both internal and external memory cards, I keep on getting an error during the update that there is not enough space left for installing the update. The update was said to be ~36MB in the update dialog.

All prior updates have been successful without any problems.

Anybody else having similar issue?


Update: I found a solution

The error was about "not enough memory in target location" and thus really did not seem to be about device memory (RAM). I solved the problem by deleting a number of applications was not using too much and after that the update succeeded without any problems.

Pertti

[callanish]

I seem to have a major issue with this upgrade on my N800:

Despite the fact that I have ~1GB space left on both internal and external memory cards, I keep on getting an error during the update that there is not enough space left for installing the update. The update was said to be ~36MB in the update dialog.

All prior updates have been successful without any problems.

Anybody else having similar issue?

Pertti

How much do you have left in device memory? That's probably where your mixing up internal/external memory with device memory.

[aya]

I seem to have a major issue with this upgrade on my N800:

Despite the fact that I have ~1GB space left on both internal and external memory cards, I keep on getting an error during the update that there is not enough space left for installing the update. The update was said to be ~36MB in the update dialog.

All prior updates have been successful without any problems.

Anybody else having similar issue?

Pertti

If you are using redpill mode, switch it back to blue pill and in your application manager, check the download destination to make sure it will be MMC.

[fpp]

I have gone through 4 update installations to be finally able to know what fails and gather that information (1->reboot cycle-teeth gnashing, 2->white screen of death-head banging, 3->success, 4->document and check fixes)
I put this here in the hope it can help those of you who haven't still updated to avoid failure.


One word : WOW :-)

- The update contains a documentation package. This package causes a lot of trouble, because it fails if the user has moved, removed or linked the documentation files:


(shound of other shoe falling...)

I have a hunch this is the #1 killer bee for most "normal users" who don't have any fancy mods installed (kernel, bootmenu, etc.).

This is something I do routinely, like many others I guess, to regain space after flashing (along with music, images and video). It was pure chance that last time I retained the French versions of both documents and did not delete any directories. Pfew...

That install script is *definitely* too brittle...

[GeneralAntilles]

That install script is *definitely* too brittle...

I always delete the folder with all the bundled manuals, and I've never had trouble. So it's not quite that brittle.

[Texrat]

I always delete the folder with all the bundled manuals, and I've never had trouble. So it's not quite that brittle.

Then how to account for those who had problems for that reason?

[GeneralAntilles]

Then how to account for those who had problems for that reason?

Symlinking? Deleting a level up at .documents?

[Khertan]

I delete this folder too ... maybe something else ...

[EIPI]

Then how to account for those who had problems for that reason?

if uid = councilchair then {install fine} else {execute wonky install randomly}

:)

Is anyone else still having problems with the RSS reader applet not updating? I have had this problem since Diablo came out, and it still doesn't appear fixed.

[Bundyo]

Interestingly enough, i didn't delete any documents. Media yes, but no documents. And i had the preinstalled documents problem anyway.

[Texrat]

lol EIPI. :D

As to your question, rss reader working fine on 2 versions of Diablo here.

[briand]

Code:
if uid = councilchair then {install fine} else {execute wonky install randomly}


should probably check the uid.type subclass, as the above will fail unless he changes his user id... ;)

[codeMonkey]

I always delete the folder with all the bundled manuals, and I've never had trouble. So it's not quite that brittle.

Ditto on two n800s.

[EIPI]

lol EIPI. :D

As to your question, rss reader working fine on 2 versions of Diablo here.

Hmmm - appears that bug 3335 (https://bugs.maemo.org/show_bug.cgi?id=3335) is not fixed then.

[vinc17]

- The update contains a documentation package. This package causes a lot of trouble, because it fails if the user has moved, removed or linked the documentation files:
It fails if there is no files in "/usr/share/pre-installed/MyDocs/.documents/". Create that directory and touch or put a file there if you have that deleted.
It fails if the "/home/user/MyDocs/.documents/osso_software_copyright.pdf" file is a symlink
It fails if the "/home/user/MyDocs/.documents/~sfil_li_folder_user_guides/" directory is a symlink or is empty. Make sure you have an actual directory with any file there.
My reboot loop could be due to that: to make some disk space, I either removed this directory or removed every file from it (thus letting it empty). After all, these files belong to the user, not root, and the user does nothing wrong by removing such files.

- Do not work through a ssh shell
I sometimes do upgrades via ssh, but this wasn't the case here (and in general, I avoid upgrades of important packages via ssh).

[Texrat]

Hmmm - appears that bug 3335 (https://bugs.maemo.org/show_bug.cgi?id=3335) is not fixed then.

That would be odd to me, since I successfully restored backup on one of my recent fresh Diablo installs, and rss works fine...

[la3875]

Well reflashing this time around update was successful. I was grasping at straws regarding the SD card. Restored all files and apps and we're back to stable again for the moment. Thanks all!

[Rohan]

Hi All,

I'm really at a bit of a loss here. I've searched around and can't seem to find the solution to my problem. I installed the update (v4.2008.36-5) yesterday and have now reflashed twice and I cannot get on the internet! My wifi connects, but no pages will load and I am unable to install anything from the application manager. As such I am unable to restore as the list of applications I previously had installed are all greyed out. Also, I know my wifi is fine as numerous other devices are able to connect and browse.

This is driving me absolutely nuts as my tablet was working fine until last night!

Please help!

Thanks in advance.

[Oberon85]

Another positive experience....
Couldn't see the update on my dual boot when booting from SD, so;

apt-get clean
apt-get upgrade
reboot
no change in version numbers, sort of expected that.
reboot to flash
update via app manager
reboot
run penguinbaits install-tools
(forget that I didn't uninstall last time, uninstall install-tools, reinstall install tools.. 8-)
reboot
choose SD
version numbers updated...
all stable, and microb is noticeably faster on gmail, youtube, ....
thanks to all who have taken the time to post their results here... watching and learning from all of your examples and help

extra thanks to penguinbait and fanoush you guys rock.

[Laughing Man]

I still don't understand how updating flash (internal build in memory) would update a boot from SD partition. Maybe the kernel yes. But individual packages should have to be updated on both the flash and SD correct?

[BrentDC]

I always delete the folder with all the bundled manuals, and I've never had trouble. So it's not quite that brittle.

I also deleted the Manuals, Video, and Music on both OS partitions and they both updated fine. I kept the ~/MyDocs/.* folders, though.

I don't think there is a hard-and-fast rule governing the success of this update...

[Rohan]

With regards to my previous post. After playing around with my N810 and router (N1 Vision), my N810 will only connect and actually work with WPA2 enabled, not WPA. It worked fine before.

Any ideas?

[albright]

Couldn't see the update on my dual boot when booting from SD

I *can* see the update when I boot from sd card on my n810.
Does that mean it is safe to upgrade the sd and leave the
flash version as is?

(Actually, I tried once to run the update from the sd booted
version and got a "corrupt installation file" error after the
download. What's with that??)

[lm2]

run penguinbaits install-tools
(forget that I didn't uninstall last time, uninstall install-tools, reinstall install tools.. 8-)
reboot
choose SD
version numbers updated...


Think again. I too updated flash first and saw that version numbers were updated. But the cool kids around here insisted that, even so, updating flash without updating SD while booting from SD does not do the trick. I suggest that you boot from SD and follow the steps set out here (http://www.internettablettalk.com/forums/showthread.php?p=228881#post228881).

[lm2]

I *can* see the update when I boot from sd card on my n810.
Does that mean it is safe to upgrade the sd and leave the
flash version as is?

(Actually, I tried once to run the update from the sd booted
version and got a "corrupt installation file" error after the
download. What's with that??)

Not sure about the last part, but yes, it is safe to install from SD first. (You will not have to update flash, if you don't want to--or so Benson says...)

In fact, if you look at my post immediately above, you'll see that you *should not* update flash first. Your system may be tricked into thinking that the SD has thereby been already updated.

[Oberon85]

i think you missed the first part of my post:
"apt-get clean
apt-get upgrade
reboot
no change in version numbers, sort of expected that.
reboot to flash"
the apt-get upgrade par t of this is where my SD was updated... watched it download 33mb of stuff including microb, etc, install, setup, the works. All I meant to say was that even though I could not see the SSU in app manager, I was able to upgrade from the cli, and that after doing the upgrade to my SD, the version numbers had not changed in control panel, about product screen. I have verifired that the upgraded software version in SD and flash match by comparing the upgrade output log I made in SD to the app manager log from flash.

all still working well...

[daperl]

FYI. 3 (not 4) different flash partitions are being updated (I think):

the linux kernel
the bootstrap OS referred to as initfs
and the runtime OS referred to as rootfs

If the boot loader partition needed to be updated this would have been a reflash.

For mulit-booters, rootfs is the only thing that is on your SD. All runtime OS's share the kernel and the initfs and that is why you're seeing version numbers change before you update your SD OS's. You need to update and then re-fanoush for all of your runtime OS partitions.

It wouldn't be a bad idea to have an mtd diagram considering the sophistication of this community. Go to the OpenWRT.org project for some more embedded linux info. Ignorance has turned out not to be bliss.

[sachin007]

i think you missed the first part of my post:
"apt-get clean
apt-get upgrade
reboot
no change in version numbers, sort of expected that.
reboot to flash"
the apt-get upgrade par t of this is where my SD was updated... watched it download 33mb of stuff including microb, etc, install, setup, the works. All I meant to say was that even though I could not see the SSU in app manager, I was able to upgrade from the cli, and that after doing the upgrade to my SD, the version numbers had not changed in control panel, about product screen. I have verifired that the upgraded software version in SD and flash match by comparing the upgrade output log I made in SD to the app manager log from flash.

all still working well...

Can you go to your app manager and check if the os 2008 upgrade has a red exclamation mark with borked in the details?

thanks

[allnameswereout]

I had some preinstalled docs trouble too, had to create a folder and an empy document, since the deb setup failed if they're not present.

+1 for deb install simulation (not only for SSU, probably will be best if all debs can be tested).

# apt-get -s dist-upgrade

:confused:

I sometimes do upgrades via ssh, but this wasn't the case here (and in general, I avoid upgrades of important packages via ssh).

Just use screen.

[Bundyo]

I meant in the App Manager, most users don't use apt-get.

[albright]

Well ... I booted into flash, performed update (n810 would
not update from sd). Ran the new initfs_flash to reinstall
bootloader. All seemed to go well.

But now I can boot into flash normally, and I have the
multiboot menu, but if I try to boot to SD, the blue bar
gets half way and the device reboots ...

I guess I must re-clone the system to SD ??

What a PIA

[GeneralAntilles]

I still don't understand how updating flash (internal build in memory) would update a boot from SD partition. Maybe the kernel yes. But individual packages should have to be updated on both the flash and SD correct?

Read the thread. I explained it earlier. :)

It's really quite simple, nothing at all is being touched on the other partition when you're updating one or the other. The version info is contained on the config partition which is common to all other partitions.

[thaldyron]

Does this update contain a new kernel?
After updating uname still shows:
Linux Nokia-N810-23-14 2.6.21-omap1 #2 Wed Jul 16 12:29:11 EEST 2008 armv6l unknown

[Benson]

Does this update contain a new kernel?
After updating uname still shows:
Linux Nokia-N810-23-14 2.6.21-omap1 #2 Wed Jul 16 12:29:11 EEST 2008 armv6l unknown

Yes, it has a new kernel.
$ uname -a
Linux Nokia-N800-23-14 2.6.21-omap1 #2 Tue Sep 30 03:24:41 CEST 2008 armv6l unknown

[allnameswereout]

Yes, it has a new kernel.
$ uname -a
Linux Nokia-N800-23-14 2.6.21-omap1 #2 Tue Sep 30 03:24:41 CEST 2008 armv6l unknown

Are you sure? Both are #2, but the one thaldyron is running is compiled on 16 july 2008.

Linux Nokia-N810-23-14 2.6.21-omap1 #2 Wed Jul 16 12:29:11 EEST 2008 armv6l unknown

Linux Nokia-N800-23-14 2.6.21-omap1 #2 Tue Sep 30 03:24:41 CEST 2008 armv6l unknown

Your time zone is also CEST, not EEST.

Here is my N810 uname -v output, on updated SSU/Diablo, no custom kernel.

#2 Tue Sep 2 10:13:14 EEST 2008

Anyway, it doesn't matter much. Only thing added is WiMAX support. Right?

[Benson]

Well, mine is on an N800, so it's unsurprising that it's N800, and that it was built at a different time on a different machine (evidently in a different timezone); but the fact that Thaldyron's is from July rather than something close to September 30th makes it look like his kernel did not get updated...

(Oh, I just realized I have got an updated kernel for rotation -- still, something Septemberish should be correct on either platform, I'd think...)

[Laughing Man]

Read the thread. I explained it earlier. :)

It's really quite simple, nothing at all is being touched on the other partition when you're updating one or the other. The version info is contained on the config partition which is common to all other partitions.

So I would be correct in that when you update in flash, your not actually updating the packages specifically dealing with the browser, modest, or whatever in SD. Only in flash. And vice versa (if updating the SD, then you would not be updating those components in flash).

[allnameswereout]

Well, mine is on an N800, so it's unsurprising that it's N800, and that it was built at a different time on a different machine (evidently in a different timezone); but the fact that Thaldyron's is from July rather than something close to September 30th makes it look like his kernel did not get updated...

(Oh, I just realized I have got an updated kernel for rotation -- still, something Septemberish should be correct on either platform, I'd think...)

True, my point exactly. On the other hand they're all #2. Somebody did something wrong; that version should have been incremented to (at least) #3.

PS: Its just me or not, but when checking out the version I had to boot my tablet and geez... my tablet boots fast.

[febb]

I don't know if this is related to the SSU v4.2008.36-5 but the story is as follows:

After the update and lock-up on infinite reboots (because, I suspect, I had installed the screen rotation feature); I updated it again to the original Diablo firmware.

I made the regular updates, including the first Diablo SSU and then the current (second) SSU. Everything seemed to be working fine, I even installed maemo mapper, gnumeric and some other regular stuff from the regular repos.

Today, having little battery left "less than an hour" and the N810 working perfectly on a WiFi network, I soft powered off the device and as soon as I got home I turned on the N810 and then turned it OFF to be plugged in to recharge the battery: as every other day. (I like to see the "chargning" and "battery full" labels on screen, thats is why I turned it off)

When I plugged in the battery charger, the white NOKIA logo screen came up and the device didn't boot. I couldn't even turn it off. I had to take the battery out. I put the battery in again and the same thing happened: NOKIA logo screen and locked device; no boot and not being able to turn it off.

FInally, after several attempts doing this, I plugged the USB cable (which was recognized, by the usb link symbol on the top right corner on the NOKIA logo screen) and finally was able to reflash the original Diablo firmware (again, for third time).

This has never happened before on my N810.

Questions are:

1) Any of you has experienced this lockup of your N810 with the same or similar conditions as described ?
2) Could it be related to the latest SSU ...?

Your comments are welcome. Thanks in advance.

Kind regards.

[st5150]

Can someone please upload their unmodified /etc/mce/mce.ini from this latest diablo update ? (this means you've never installed sliderotate )

[kp4djt]

I just did the latest update and now there are two objects on my screen one is a large square that has the following in it (no contacts) not sure what it is supposed to be but I have contacts on the machine and they do not show up there. The other is a changing window of adverts, I have tried to figure out how to get rid of them, but seems a horrible way to inflict stuff on users. The one window appears to be attempting to offer downloads from the Maemo site. Anyone else seen this over the past few days with the latest update??

[Benson]

Well, I actually don't recall seeing it (surprisingly), but maybe I just put my selections back in without even thinking. At the home screen, choose the drop-down menu, pick Select applets..., and deselect any you don't like.

[vinc17]

# apt-get -s dist-upgrade
This isn't sufficient for a simulation: it won't detect a failure in the install scripts. I doubt a simulation is possible anyway.

[maacruz]

This isn't sufficient for a simulation: it won't detect a failure in the install scripts. I doubt a simulation is possible anyway.
It could be done more or less easily using aufs/unionfs.

[zzzy]

I have gone through 4 update in... [snip] ...stall the new kernel and initfs

Would an admin please link maacruz's posting to the Troubleshooting message board and make it sticky... I wish I had found it last night before having spent 4 hours stabbing in the dark at software that seems to have been designed at Micro$oft (i.e.: "Update has failed", period: no log files, no technical details, no *&^$#%*& recovery option whatsoever).

I was lucky enough that my .36-5 update chocked while attempting to chmod the .documents directory tree (which used to reside on my mmc2 device) while still leaving the entire system in a stable state.

But after having (re)discovered teh trick with creating bogus *.pdf files under /usr/share/pre-installed/MyDocs/.documents/ and moving ~/MyDocs/.* back to internal storage, I also had to deal with version conflicts for libdb4.2 (= 4.2.52-18osso) and libglade2-0 (= 1:2.4.0-1osso2). I had to manually edit the Package: osso-software-version-rx34 entry in /var/lib/dpkg/status and replace the = sign with > in the Depends: line for the two dependencies above.

Oh, and also for those who choose to fix this from within the Application Manager application, changing the option clean-after-install to 0 in ~/.osso/hildon-application-manager helps shorten the trial-and-error cycles.

[possessedskier]

Another positive experience....
Couldn't see the update on my dual boot when booting from SD, so;

apt-get clean
apt-get upgrade
reboot
no change in version numbers, sort of expected that.
reboot to flash
update via app manager
reboot
run penguinbaits install-tools
(forget that I didn't uninstall last time, uninstall install-tools, reinstall install tools.. 8-)
reboot
choose SD
version numbers updated...


That's exactly what I had to do. See my post here (http://www.internettablettalk.com/forums/showpost.php?p=228840&postcount=237). The version number on the SD didn't change until I updated the flash also. I did uninstall sliderotate first and reinstalled it today with no problems. Thanks to all who continue to post solutions on this forum. The ITT and Ubuntu forums rock!

[zzzy]

Can someone please upload their unmodified /etc/mce/mce.ini from this latest diablo update ? (this means you've never installed sliderotate )

[2|user@Nokia-N800-23-14|~]cat /etc/mce/mce.ini | grep -v ^# | grep -v ^$
[Modules]
ModulePath=/usr/lib/mce/modules
Modules=homekey;battery;filter-brightness-als;inactivity;camera;alarm
[HomeKey]
HomeKeyLongDelay=800
HomeKeyShortAction=shortsignal
HomeKeyLongAction=longsignal
[PowerKey]
PowerKeyMediumDelay=1000
PowerKeyLongDelay=1500
PowerKeyDoubleDelay=1000
PowerKeyShortAction=menu
PowerKeyLongAction=poweroff
PowerKeyDoubleAction=disabled
[SoftPowerOff]
ConnectivityPolicyCharger=retain
ConnectivityPolicyBattery=forceoffline
ConnectivityPolicyPowerOn=offline
[DevLock]
DevLockDelay0=0
DevLockDelay1=1
DevLockDelay2=1
DevLockDelay3=5
DevLockShutdownTimeout=30000
[TKLock]
BlankImmediately=0
DimImmediately=0
DimDelay=3000
DisableTSImmediately=1
DisableKPImmediately=0
CameraPopoutUnlock=1
[KeyPad]
BacklightTimeout=10
BacklightFadeTime=100
[LED]
LEDPatterns=PatternError;PatternDeviceOn;PatternPo werOn;PatternPowerOff;PatternCommunicationCall;Pat ternCommunicationChat;PatternCommunicationEmail;Pa tternCommonNotification;PatternWebcamActive;Patter nBatteryCharging;PatternBatteryFull;PatternPsyched elia;PatternDeviceSoftOff
[LEDPatternMonoRX34]
PatternError=0;1;0;250;500;15
PatternDeviceOn=254;0;0;75;5000;10
PatternDeviceSoftOff=253;0;0;100;10000;5
PatternPowerOn=10;3;0;2000;1000;15
PatternPowerOff=9;3;0;2000;1000;15
PatternCommunicationCall=30;1;0;250;2000;15
PatternCommunicationChat=30;1;0;250;2000;15
PatternCommunicationEmail=30;1;0;250;2000;15
PatternCommonNotification=30;1;0;250;2000;15
PatternWebcamActive=255;0;0;0;0;0
PatternBatteryCharging=50;4;0;500;7500;10
PatternBatteryFull=40;4;0;1500;0;10
PatternExample=42;1;30;500;1500;10
[LEDPatternNJoyRX44]
PatternError=0;1;0;40002000200040ff200020000000;00 00;0000
PatternDeviceOn=254;0;0;4000205f20df7f007f007f007f 000000;4000205f20df7f007f007f007f000000;4000205f20 df7f007f007f007f000000
PatternDeviceSoftOff=253;0;0;4000203f20bf7f007f007 f007f007f000000;4000203f20bf7f007f007f007f007f0000 00;0000
PatternPowerOn=10;3;0;4000207f207f01ff01ffc000;400 0207f207f01ff01ffc000;4000207f207f01ff01ffc000
PatternPowerOff=9;3;0;4000017f017f36ff36ff7f00c000 ;4000017f017f36ff36ff7f00c000;4000017f017f36ff36ff 7f00c000
PatternCommunicationCall=30;1;0;0000;0000;40007f00 017f017f050001ff01ff0000
PatternCommunicationChat=30;1;0;0000;0000;40007f00 017f017f050001ff01ff0000
PatternCommunicationEmail=30;1;0;0000;0000;40007f0 0017f017f050001ff01ff0000
PatternCommonNotification=30;1;0;0000;0000;40007f0 0017f017f050001ff01ff0000
PatternWebcamActive=20;1;0;4000027f027fc000;0000;0 000
PatternBatteryCharging=50;4;0;0000;4000257f06ff7f0 041000000;0000
PatternBatteryFull=40;4;0;0000;407f0000;0000
PatternPsychedelia=250;1;0;4000167f167f17ff17ff000 0;40001300197f197f15ff15ff0000;4000237f237f130022f f22ff13000000
PatternExample=42;1;30;4000167f167f17ff17ff0000;40 00167f167f17ff17ff0000;0000
[LEDPatternNJoyRX48]
PatternError=0;1;0;40002000200040ff200020000000;00 00;0000
PatternDeviceOn=254;0;0;e10040101d701d70e0041d001d f01df0e00440007f007f007f007f000000;e00240024d0de08 016004d8de08040007f007f007f007f000000;0000
PatternDeviceSoftOff=253;0;0;4000204f20cf7f007f007 f007f007f000000;4000204f20cf7f007f007f007f007f0000 00;0000
PatternPowerOn=10;3;0;40101d701d700106e00401ff01ff c000;40024d0ee08001ff01ffc000;0000
PatternPowerOff=9;3;0;40f07f007f007f007f007f001d00 1df01df0e0044000c000;40107f007f007f007f007f0016004 d004d8ee0804000c000;0000
PatternCommunicationCall=30;1;0;0000;0000;40007f00 017f017f050001ff01ff0000
PatternCommunicationChat=30;1;0;0000;0000;40007f00 017f017f050001ff01ff0000
PatternCommunicationEmail=30;1;0;0000;0000;40007f0 0017f017f050001ff01ff0000
PatternCommonNotification=30;1;0;0000;0000;40007f0 0017f017f050001ff01ff0000
PatternWebcamActive=20;1;0;4000027f027fc000;0000;0 000
PatternBatteryCharging=50;4;0;0000;4000257f06ff7f0 041000000;0000
PatternBatteryFull=40;4;0;0000;407f0000;0000
PatternPsychedelia=250;1;0;4000167f167f17ff17ff000 0;40001300197f197f15ff15ff0000;4000237f237f130022f f22ff13000000
PatternExample=42;1;30;4000167f167f17ff17ff0000;40 00167f167f17ff17ff0000;0000

[possessedskier]

I just did the latest update and now there are two objects on my screen one is a large square that has the following in it (no contacts) not sure what it is supposed to be but I have contacts on the machine and they do not show up there. The other is a changing window of adverts, I have tried to figure out how to get rid of them, but seems a horrible way to inflict stuff on users. The one window appears to be attempting to offer downloads from the Maemo site. Anyone else seen this over the past few days with the latest update??

These are the Speed Contacts and Tableteer Info home screen applets. Click the home menu near the top left of the main screen then "Select applets" and uncheck them.

[Amarantus]

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

[maxinflixion]

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?

[Neon Samurai]

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.)

[GeneralAntilles]

(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? :\

[Neon Samurai]

update didn't go as planned for me. Broke boot from sd (which was expected), but the backup I did just before updating doesn't seem to work. The only thing I get back when restoring is bookmarks. Applications(list) is gone, so I have to reinstall from scratch...
Anyone else experiencing this? (and yes, I did remember to back everything up)

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.

[gemniii42]

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.<snip>

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

[Neon Samurai]

Mine (#3542 (https://bugs.maemo.org/show_bug.cgi?id=3542)) is now working - but was just before the update (workaround for my issue on the bug list)

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.

[Neon Samurai]

No problems so far!
The browser is really fast!

Was Flash in fullscreen (youtube) possible before? I can't remember.

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

[GeneralAntilles]

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.


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. . . .

[Neon Samurai]

Can you say more? I always boot from SD, and last SSU worked fine for me, but I can't remember if I had to install SSU in both flash and when booting from SD. So:

1. Will I need to install SSU from both flash and while booting from SD?
2. Will I need to do the same with fanoush's flasher?

Thanks!

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.

[Neon Samurai]

Right, the tablet typically has to be online for 24 hours straight for auto alerts to work.

I get update notifcations regularily. I don't reboot often except when getting the wifi nic back out of permiscuous mode so I can connect to wireless again. I regularily use offline mode when not near trusted wireless also. I figured the update notifier was simply using a date stamp from the last check to try again every day or week.

You can also just open the package manager and hit the update button though.

[lm2]

I'm going to try updating the internal flash install, fanoush's initfs then the SD in that order first though.

If at any time you find that SD is not showing any ssu update, do this (http://www.internettablettalk.com/forums/showthread.php?p=228881#post228881), then check app manager again.

[Neon Samurai]

Sorry if this has been answered before but is there a reason Nokia can not turn Maemo into a true rolling distro rather than instead of a mostly rolling distro with kernel and init flashing? Is that a hardware design issue that could go way with the next tablet platform?

I must admit, I've been spoiled by "apt-get dist-upgrade" on larger little iron's

[GeneralAntilles]

Sorry if this has been answered before but is there a reason Nokia can not turn Maemo into a true rolling distro rather than instead of a mostly rolling distro with kernel and init flashing? Is that a hardware design issue that could go way with the next tablet platform?


The whole boot process is changing in Fremantle.

[Texrat]

I get update notifcations regularily. I don't reboot often except when getting the wifi nic back out of permiscuous mode so I can connect to wireless again. I regularily use offline mode when not near trusted wireless also. I figured the update notifier was simply using a date stamp from the last check to try again every day or week.

You can also just open the package manager and hit the update button though.

There was further discussion after that post, so that's the wrong one to respond to.

[tso]

The whole boot process is changing in Fremantle.

its starting to look as if fremantle is more "toss the whole thing and start over from scratch" then "fix what appears to be broken"...

could be a good thing, could be bad (and im no optimist when it comes to tech companies, or just about any large organization in general).

[Benson]

The way I see it, it's more "toss all the things that are Nokia's own concoction and have not been adopted more widely"; AFAICT, we're still keeping Matchbox (not Nokia's invention) and Hildon (Nokia's invention, but is adopted). Not strictly true, of course; we're still dumping kdrive, which is not Nokia's; but you get the idea. Maybe it's just the idealist/optimist in me, but it looks like they are trying to fix the non-(supposedly)-"value adding" uniquenesses, which is a good thing.

Of course, the cynical might just say they're trying to have more of their stuff taken care of by upstream projects, so they have more man-hours to put into breaking stuff from upstream...

[Neon Samurai]

The whole boot process is changing in Fremantle.

Cheers, I can live with it until then. Now I have to go read over Ari's keynote.

Now that I have my N800 back, I'll be using that as a test platform before changing my N810 which will make this sort of thing smoother. First test will be updating internal, boot menu, SD, boot menu and see if that does it. My particular illness enjoys rebuilding an OS from scratch each major version but it would be nice to avoid it a little easier on my PDA. The issue seems like it will take care of itself in v5 so one more recloning won't hurt me.

Now, if the Ruby folk would hurry up and get Gems working with the new version. I could use the update all or apt-get upgrade blindly then. Until then, I think configuring apt to not upgrade the ruby package through the applicable config file will fix that.

[Neon Samurai]

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

The short answer may be a PICNIC issue; problem in chare not in computer.

This last update, I broke the wifi under the SD boot by taking a few update packages indavidually instead of finishing the job all at once. Since rebooting.. no wifi connectivity.

The previous update seemed to update ok but then consistantly hung on boot with the process bar about half way across so that was a recloning fix too.

I basically have to update the internal flash install and the SD install and have not yet had luck with the kernel and initfs update packages. As it seems to work for others, I think the issue is my aproach more than anything else. It would also be easier if I wasn't stubburn about how I did my cloning rather than just using the clone package or scripts available (I like my mounts under /mnt instead of two temporary root folders).

I often learn these things the hard way but, like security, if I don't break it then how am I to know how to fix/harden it? ;)

[Neon Samurai]

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

I could be mistaken but I thought the internal flash block the factory default setup sits on was 512 meg because 256 seems a bit small. I tried to confirm on mine here just now but it's booted of the SD and it's been a long while since I've booted the internal flash.

Now, the internal SD non removable and limited to 2 gig.. if that is really the N800's removable SD slot under the plastic shell, me and a rotary tool may be getting an internal SD upgrade. I haven't had the guts to look into that beyond theory yet though. The only thing I missed between the N800 and N810 was the two removable allowing the device to max out around 8*2 = 16 gig of SD storage.

[Neon Samurai]

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. . . .

yeah, I can fully admit this being my own limited understanding. As mentioned, this time I borked it all myself by chewing the wifi support prematurely. The last time was a hung boot. I can see how initfs and kernel should simply need the boot loader menu reimaged so now it's a matter of seeing it happen on my own device.

(edit because I'm slow today and closed before I was finished): offhand, is there documentation on how the initfs integrates? I know the general process is initial byte code -> RAM -> bios -> initfs -> kernel (or kernel -> initfs). Is there some subtle difference with maemo or am I just not thinking it through?

[Benson]

I could be mistaken but I thought the internal flash block the factory default setup sits on was 512 meg because 256 seems a bit small. I tried to confirm on mine here just now but it's booted of the SD and it's been a long while since I've booted the internal flash.
It's 256MB, but it's using jffs2, a filesystem that compresses data (both to fit more on, and especially to avoid wearing out the flash), so you get around 512MB of data on it (depending on the data, of course).

Now, the internal SD non removable and limited to 2 gig.. if that is really the N800's removable SD slot under the plastic shell, me and a rotary tool may be getting an internal SD upgrade. I haven't had the guts to look into that beyond theory yet though. The only thing I missed between the N800 and N810 was the two removable allowing the device to max out around 8*2 = 16 gig of SD storage.No, there's no SD slot under there -- the SD interface is used for an SD-compatible SMT chip. You'd have to desolder that, then solder on some fine wires running to an SD socket or soldered directly onto an SD. Doable, but only with appropriate skills+equipment. Nobody with said skills and equipment has seen fit to do it yet, though.

And that 8GB is invalid -- there are 16 and 32 GB SDs, and 16GB microSDs available now. I hope you've looked at craves1's adapter thread? He's manufacturing (and soon selling) full-size SD adapters that convert the external miniSD into an internal SD; two versions are available, and possibly a third for people who are good friends with a rotary tool. (The latter will permit the standard battery door; the former are for a custom bulged battery door w/standard battery, and for adding to the door that comes with a Mugen 3.6Ah battery.) If 16GB would make you happy, one of those should do the trick.

[gemniii42]

I could be mistaken but I thought the internal flash block the factory default setup sits on was 512 meg because 256 seems a bit small. I tried to confirm on mine here just now but it's booted of the SD and it's been a long while since I've booted the internal flash.

Now, the internal SD non removable and limited to 2 gig.. if that is really the N800's removable SD slot under the plastic shell, me and a rotary tool may be getting an internal SD upgrade. I haven't had the guts to look into that beyond theory yet though. The only thing I missed between the N800 and N810 was the two removable allowing the device to max out around 8*2 = 16 gig of SD storage.
the flash is 256, the 2Gb has been discussed heavily and noone has figured out a way to upgrade it without major brain surgery.
/edit
and there is a thread to use a 32GB card going, plus 16Gb micro cards are out (but pricey)

[Neon Samurai]

the flash is 256, the 2Gb has been discussed heavily and noone has figured out a way to upgrade it without major brain surgery.
/edit
and there is a thread to use a 32GB card going, plus 16Gb micro cards are out (but pricey)

hm.. drat, so it's not just the plastic casing over a removable SD slot that I can swap and clone? That saves me hacking up the chassis under the back panel at least.

[Neon Samurai]

And that 8GB is invalid -- there are 16 and 32 GB SDs, and 16GB microSDs available now. I hope you've looked at craves1's adapter thread? He's manufacturing (and soon selling) full-size SD adapters that convert the external miniSD into an internal SD; two versions are available, and possibly a third for people who are good friends with a rotary tool. (The latter will permit the standard battery door; the former are for a custom bulged battery door w/standard battery, and for adding to the door that comes with a Mugen 3.6Ah battery.) If 16GB would make you happy, one of those should do the trick.

I'll have to let you know if more than 16 gig will make me happy once I fill my 8 gig though by then a mini larger that 8 gig will probably do just fine. I think it's more the percieved feeling of a hardware downgrade by giving up the internal SD slot.

I did the same thing with my Palm before the N800. "upgrading" from T5 to LifeDrive seemed like a hardware downgrade. It was the newer unit but platter drives, slower cpu and some there functions left out that the T5 had. In the end, the N800 was the first device that was actually an upgrade from the T5.. so I upgraded. Now, the T5 is only used for bluetooth stuff I can't yet replace under maemo.

Good to know about the internal slot before I go hacking up mine though.

[Laughing Man]

uh oh.. i got this trying to install osso.

Some packages could not be installed. This may mea n that you have
requested an impossible situation or if you are us ing the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug re port against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
osso-software-version-rx34: Depends: kernel-diab lo-flasher (= 2.6.21-200835maemo1) but 2.6.21-2008 35maemo1rotation is to be installed
Depends: libsdl-mixe r1.2 (= 1.2.6-4) but 1.2.8-1 is to be installed
Depends: xserver-xom ap (= 1:1.3.99.0~git20070321-0osso20083101) but 1: 1.3.99.0~git20070321-0osso20083101rotation is to b e installed
E: Broken packages
~ $

[sjgadsby]

...so it's not just the plastic casing over a removable SD slot that I can swap and clone?

No, it's MoviNAND (http://www.samsung.com/global/business/semiconductor/products/fusionmemory/Products_MoviNAND.html). Most likely it's a KMBDG0000A, though it could be a KMAKG0000M. Either way, someone with the right tools and knowledge of how to use them should be able to double their N810's internal storage. And if the N810s use KMAKG0000Ms, then an upgrade to 8GB is possible.

[Prestwick]

Updated before I headed into work and gave it a thorough work over.

On 3 UK 3G but MicroB is responsive and faster than it used to be in parts. Youtube is much better to use than before and the video controls are responsive to the touch rather than waiting a year and a day just to pause video.

Boot times are noticeably quicker too I think. Modest (as usual) is a massive disappointment and only serves to slow down the tablet and cause me immense amounts of stress, grief and pain as it struggles to process gmail IMAP with the speed and understanding of a ninety year old Victorian trying to learn C++.

Usually, when I'm on Wifi and the device suddenly crawls to a halt, you know that Modest is trying to comprehend the concept of web e-mail accounts and IMAP. I've deleted my g-mail account details from the tablet to solve the problem ;)

[Viqsi]

- The update contains a documentation package. This package causes a lot of trouble, because it fails if the user has moved, removed or linked the documentation files:
It fails if there is no files in "/usr/share/pre-installed/MyDocs/.documents/". Create that directory and touch or put a file there if you have that deleted.
It fails if the "/home/user/MyDocs/.documents/osso_software_copyright.pdf" file is a symlink
It fails if the "/home/user/MyDocs/.documents/~sfil_li_folder_user_guides/" directory is a symlink or is empty. Make sure you have an actual directory with any file there.

Oh, now *that* REALLY pisses me off.

I have the internal card reformatted as ext2 so that I could use it as a default user space. And the way I normally did this was to symlink /home/user/MyDocs to that. So, kaboom.

What in the almighty hell is a .deb doing even glancing sideways at the /home directory? That's the user's playground. You DO-NOT-TOUCH the user's playground. Ever.

GRARGH.

[Thesandlord]

OK, sorry if this has been answered before. Sliderotate seems to have been updated for 36-5, but I am unable to properly install it.

If I go through xTerm, I can install it, BUT it uninstalls osso-software-version-rx44, which would disable the future software SSU. It says there is a problem with xserver-xomap when i try to install osso.

Is there a way to get sliderotate and osso-software-version together?

[Rider]

I have the internal card reformatted as ext2 so that I could use it as a default user space. And the way I normally did this was to symlink /home/user/MyDocs to that. So, kaboom.


That's what I'm doing too and the update was smooth without a problem.

[Aisu]

Why the *hell* do we have to have an "OS Feature Update" package?? Why can't we update like EVERY OTHER Debian system?? Package by package whenever they're *ready*.

Damnit, this update did not install correctly, it busted my apt, and it reflashed my initfs even though it did not install.

Now I go to reflash.

[tso]

its to "help" those non-linux users "grasp" app manager...

thats also why there is a red pill mode, even tho i wish sometimes there was a "power user" mode that showed some of the info that red pill does...

[GeneralAntilles]

thats also why there is a red pill mode, even tho i wish sometimes there was a "power user" mode that showed some of the info that red pill does...

Well, if you want to patch Application manager up a bit to better allow the use-case (with an toggleable option, preferably), then I'm pretty sure we can work something out for the community distribution (http://maemo.org/community/council/view/1222953254.html).

[Wzrd]

No problem with this update for me except for deleting my bootmenu options.

However, my tablet seemed to slow down quite a bit with the last upgrade after I cloned the OS to SD. With this update on top of the other one, it seems even slower now.

It seemed faster before I did the cloning. The internal OS seems alot slower now overall. I may have to reflash and just forget the clone to OS. Or, strictly use the cloned os primarily. Although, the only difference I see is a very slight speed in booting and app loading on the cloned OS vs. internal OS. Otherwise, no substantial big improvement.

[johnpad]

Hi,

Unfortunately I do not have the time to read through the last 42 pages of this thread so if possible could somebody please help with a summary.

What I have learned so far is:

1 If you are booting off an external card you will need to redo the boot menu
2 If you have screen rotation the install may fail (leads to reboot loop)
3 If you have a problem with the install you will need to re-flash
4 You need to make sure you have enough space (on the internal drive) before you start

Does this sound about right?
Is there anything else to go on this list?

If we get a definitive answer I will create a new thread just to save people searching too far and I will correct this post.

Cheers -John

[JaseP]

If you can clearly identify such problems - ideally including why your tablet got into the state it did - then Bugzilla (http://bugs.maemo.org/) is the place to log them.


Well,... I for one feel the need to defend this guy... Identify the specific causes?!?!?! How on Earth is anyone supposed to do that when the darn thing keeps rebooting in an endless cycle??? Please read on for more well intentioned chastising...


A 20-page thread of wailing, gnashing of teeth and cries of "G4h, N0ki4 ate my baybeeees" isn't going to help anyone much. At best, it discourages others who've made potentially dangerous modifications from installing the update. At worst, it leaves an impression of poor quality on this release. Given it works for the silent majority, that would be unfortunate.


Well, I certainly hope that it leaves an impression of poor quality... I too have experienced the endless reboot errors on my N800, not only after one upgrade, but after re-flashing and re-upgrading... Shame on Nokia for fostering an Alpha test on us... Potentially dangerous modifications?!?!? This is LINUX we are talking about!!! Modifications are the very life-blood of Open Source!!! We deserve better QA, especially since we purchased a consumer product that is little better to Nokia than a test-bed for their VOIP-phone of the future...


Now, there are some specific things we can identify with this release which are (to be charitable) poor QA. Others which are anti-social:


Again, understatement. IMHO you owe this guy an apology...

[vinc17]

Well,... I for one feel the need to defend this guy... Identify the specific causes?!?!?! How on Earth is anyone supposed to do that when the darn thing keeps rebooting in an endless cycle???
Yes, one doesn't know why it keeps rebooting: no log, not a single error message. Ditto for the Application manager: one doesn't know what's going on when packages are installed (one doesn't even know what packages are installed), one doesn't know when something fails. While problems can often be solved after seeing logs / error messages under Unix, this is not possible here.

[Benson]

Yes, one doesn't know why it keeps rebooting: no log, not a single error message. Ditto for the Application manager: one doesn't know what's going on when packages are installed (one doesn't even know what packages are installed), one doesn't know when something fails. While problems can often be solved after seeing logs / error messages under Unix, this is not possible here.

Wrong. It's possible, but only if you've anticipated the potential for trouble and cloned to an SD. When you have a non-booting system with a HDD, you can pull it, put it in another system, mount it read-only, and go look at logfiles, etc. Or you can boot off removable media, and examine it. The same is possible with the tablet if you either were running off SD (you can look at the SD in another system) or if you were running flash and have a bootable SD.

There's also some tools that may be ionstalled in the initfs to give you a USB networking (with telnet/ssh) or USB serial connection. This gets you a shell before it loops and you can diagnose/repair things from there.

While there are some issues with this update, they mainly boil down to packaging and package-deployment issues. There is no real inability to diagnose failures, and anyone who can't clone to SD probably couldn't diagnose the failure in any case.

[qwerty12]

its to "help" those non-linux users "grasp" app manager...

thats also why there is a red pill mode, even tho i wish sometimes there was a "power user" mode that showed some of the info that red pill does...

It would help if you were more specific ;P

[lazuli]

as johnpad mentioned, the update may fail and lead to an endless reboot if rotation is installed. if so, does uninstalling the rotation ensure a "seamless" update? i think many users like me just want to be reassured about this before going for the update..

[Benson]

I'm not aware of any evidence to support that. AFAIK, all existing rotation packages prevent the update from starting in the first place. The main culprit for reboot loops seems to be the preinstalled documentation and media.

[vinc17]

Wrong. It's possible, but only if you've anticipated the potential for trouble and cloned to an SD.
But the point is that most users don't anticipate and don't clone to SD (users don't always have a SD or have space on the SD anyway).

When you have a non-booting system with a HDD, you can pull it, put it in another system, mount it read-only, and go look at logfiles, etc.
With other systems (e.g. Debian), this isn't needed: boot messages are output to the screen, so that one can see what's going on and possible errors. This is not always convenient, but still much better than having nothing at all like on the tablet. Moreover, one can enter single-user mode from the firmware, so that one can try to fix things.

There's also some tools that may be installed in the initfs to give you a USB networking (with telnet/ssh) or USB serial connection. This gets you a shell before it loops and you can diagnose/repair things from there.
Sounds really interesting. Any more information, please?

While there are some issues with this update, they mainly boil down to packaging and package-deployment issues. There is no real inability to diagnose failures, and anyone who can't clone to SD probably couldn't diagnose the failure in any case.
No, this needs to anticipate. One should really be able to diagnose the failure without anticipating and without having a spare SD. This isn't much a problem for this failure as it occurs for many users, so that some of them can diagnose it. But some other uncommon failures could really be hard to diagnose.

[GeneralAntilles]

Sounds really interesting. Any more information, please?


http://wiki.maemo.org/Booting_from_a_flash_card#Install_bootmenu

[tso]

It would help if you were more specific ;P

dependencies tab, being able to see what lib versions are installed (libpurple0, im looking at you)...

[Jaffa]

Well,... I for one feel the need to defend this guy... Identify the specific causes?!?!?! How on Earth is anyone supposed to do that when the darn thing keeps rebooting in an endless cycle???

Something is different on the tablet of every user for whom it's failed. No-one's going to be able to pin down what's common if what's been done to them isn't clear.

"Specific causes" meant - if it's failed for you - what, exactly have you done to the tablet since you last reflashed it? Saying "nothing, it's the same" and then later it turns out "well, I installed sliderotate" (not mentioning any particular user, here) means something was done.

Software doesn't fail randomly, unless there's a hardware failure. Something is different which is causing reboot loops etc.

[sattlert]

Then, because I'd deleted stuff out of MyDocs, and put links there to the internal mmc card, the document package didn't work, I had to remove the links and re-create the dirs and put some dummy files in. Finally, the packages installed and dpkg-reconfigure worked, and I was upgraded.

I had the same problem. I had .documents linked to a folder on the internal mmc card, and the update process kept failing. The log read: mv: cannot rename '/usr/share/pre-installed/MyDocs/.documents/*': No such file or directory

After creating a new folder .documents under /usr/share/pre-installed/MyDocs with some dummy file in it, I could finally install the update successfully.

[vinc17]

http://wiki.maemo.org/Booting_from_a_flash_card#Install_bootmenu
Some users said that the SSU broke their bootmenu, so how would this solve anything concerning the endless reboot loop?

Moreover this wiki page doesn't mention the tools to get USB networking before the reboot (http://wiki.maemo.org/USB_networking is silent on this point too).

[vinc17]

Software doesn't fail randomly, unless there's a hardware failure. Something is different which is causing reboot loops etc.
Unfortunately not everyone remembers everything what they did since the last reflash, including things not done as root (as the SSU behavior also depends on user space, as it was shown).

[mikkov]

I cannot understand why SSU installs anything to user's home directory at all. Home directory is for user to do anything he wants and trying to make a deb which works there 100% is not a easy task.

[Neon Samurai]

Yes, one doesn't know why it keeps rebooting: no log, not a single error message. Ditto for the Application manager: one doesn't know what's going on when packages are installed (one doesn't even know what packages are installed), one doesn't know when something fails. While problems can often be solved after seeing logs / error messages under Unix, this is not possible here.

- there is a config file which includes the list of isntalled packages. I believe this is the source document for the GUI package manager. If you can't see the list of installed packages in your GUI app, you can instead get it from the text file directly. When upgrading between versions, I've copied this to reference when needing to know what nifty package I previously had installed. I'd give the location and name but I'm at work and can't confirm currently. Other's here will know where it is though (thought it was /etc/dpkg/ or /etc/apt/.. maybe a var. believe the file was packages.installed or similar)

- in terms of logging, I've considered adding syslogd to my install but I want to minimize what writes to the flash memory ratehr than hit the chips write limit any faster than I have too. I've had to many usb flashdrives hit there limit to rush my N810 into retirnment. You can install syslogd though if prefered.

[Neon Samurai]

Software doesn't fail randomly, unless there's a hardware failure.

You haven't worked with Windows much. :D

(sorry, I know it's completely off topic but I couldn't resist after giggling at that line a few times. Well written software will give an indication of why it has failed though; even if us humble end users don't know how to read that indication.)

[GeneralAntilles]

Some users said that the SSU broke their bootmenu, so how would this solve anything concerning the endless reboot loop?


Simple, take the jffs2 image the initfs_flasher generates and store it on your computer.


Moreover this wiki page doesn't mention the tools to get USB networking before the reboot (http://wiki.maemo.org/USB_networking is silent on this point too).

The USBNet article is a slightly different subject. The README for the initfs flasher contains all the relevant information.

In summary, hold down the menu key and plug in a USB cable.

Unfortunately not everyone remembers everything what they did since the last reflash, including things not done as root (as the SSU behavior also depends on user space, as it was shown).

Yes, well, they surely remember if they did something, and not report having done nothing when it's clearly not the case. Black periods are a symptom of a possibly severe neurological disorder. :rolleyes:

[Neon Samurai]

Update:

I had some time this morning so I figured I'd leave my internal OS install to update. It hit a non-responsive update server and failed leaving me with a partial update; the majority of packages seem to be hanging at the GUI's "downloading" status bar. I grabbed any package related too networking that didn't hang on download but figured the wireless networking would be chewed the same way I managed to break my SD install's connectivity. Now that I've had a chance to reboot and check, my internal install is detecting wireless networks as it should so I can continue the updates when the servers stop hanging my downloads later.

This also means that I can grab those same .deb and bring them to the SD to install from local storage. This will fix the networking issue of not detecting any wifi signals to connect too. Now, provided the updated OS does not go into looped rebooting or a hung partial boot, I'll be able to try the update and boot menu reflash rather than fixing issues beyond my comprehension by recloning.

[vinc17]

- there is a config file which includes the list of isntalled packages.
I regularly retrieve the output of "dpkg -l", but this gives too little information about the status of the tablet.

- in terms of logging, I've considered adding syslogd to my install but I want to minimize what writes to the flash memory ratehr than hit the chips write limit any faster than I have too.
Perhaps it could be disabled at the end of the boot.

[Texrat]

Unfortunately not everyone remembers everything what they did since the last reflash, including things not done as root (as the SSU behavior also depends on user space, as it was shown).

Hang on a second.

It's unfortunate that some have performed actions on their tablets that interfered with SSU, and they don't recall offhand what those actions were, but doing so in the first place was a risk they chose to take.

I have said this numerous times but I guess it is still not resonating with everyone: Nokia cannot possibly test for every single possible configuration out there. And the community has done some really far out things! (that's not meant in a bad way-- I think it's cool).

The above is not an excuse for "alpha products or poor QA" as one poster mistakenly alleged. It's just reality. And comparing Maemo to long-established linux builds (as some have) is a bit naive.

None of the problems with SSU are wilfull maliciousness on Nokia's part as some seem to believe. They are the result of something irregular. And while statements like Jaffa's about doing a little investigation may seem trite, doing so and reporting back through bugzilla is the only way that the Maemo team can acquire the information necessary to prevent future problems.

[bafio]

Hang on a second.

It's unfortunate that some have performed actions on their tablets that interfered with SSU, and they don't recall offhand what those actions were, but doing so in the first place was a risk they chose to take.

I have said this numerous times but I guess it is still not resonating with everyone: Nokia cannot possibly test for every single possible configuration out there. And the community has done some really far out things! (that's not meant in a bad way-- I think it's cool).


Fine with me, as long as they alert users that the supplied documentation is an integral part of the operating system. Such a feature is uncommon on mainstream OS so many users may be surprised that deleting such documentation may cause the update to fail. If this is not poor quality insurance on a software release, they would better provide warnings when deleting such files!
Otherwise, in a more constructive way, they could try to provide some fixes and learn from their mistakes.

[Texrat]

Fine with me, as long as they alert users that the supplied documentation is an integral part of the operating system. Such a feature is uncommon on mainstream OS so many users may be surprised that deleting such documentation may cause the update to fail. If this is not poor quality insurance on a software release, they would better provide warnings when deleting such files!
Otherwise, in a more constructive way, they could try to provide some fixes and learn from their mistakes.

I feel like I must be speaking some alien language.

Isn't the last part of your post what I just said?

The documentation issue has been bugged and I am confident it will be addressed. Reporting it, voting on it and discussing it are all parts of the feedback and correction process. Have you voted on that bug yet?

[dxitt]

Hi,

I updated my n810 last night and found out that WLAN "selection connection" is NOT working properly. It keeps "searching", but no wifi network shows up! Though it still connects to my home wireless router as it was saved in the profile. The WLAN taskbar icon is grayed out... :(

Anyone else is having similar problems? How do I fix this.

Any help will be very much appreciated.

-DX

[sjgadsby]

Anyone else is having similar problems?

Yes. Please see bug # 3749 (https://bugs.maemo.org/show_bug.cgi?id=3749).

[cyberhomi]

After the so called seamless software upgrade my N810 went into looping reboots. I didn't know what to do until I read about it in this forum. Can't thank you enough. The manual reflash took several tries.

[chrisak]

I'm gonna throw this in here, but afraid it'll will get lost. My upgrade seems to have thankfully gone very well, altugh I've found that my browser has lost some of the menu options regularly available when 'right clicking' a link. I no longer have the option to open link in new window... instead are 2 "play....." entries, one trying to open link in kmplayer, and the other in default media player. Other menu items are copy link location, and some zoom and general page navigation options.

Right click menu on other areas of a web page seems to produce corrrect menu.... its only wen right clicking links. Anyone else experiencing this?

[qwerty12]

dependencies tab

For that, something as simple as this applied to the application manager source would work:
http://pastebin.com/d6cae4caa

I don't have a tablet available atm so I can't test it out. Although I can try it out in the scratchbox...

Oops, read the code wrongly. Removing those two lines would work better.

Fixed patch:
http://pastebin.com/m35af5bd1

This one actually works to show dependencies in blue pill.

[Laughing Man]

Does anyone know how to resolve my problem?

http://www.internettablettalk.com/forums/showpost.php?p=229872&postcount=406

[amigokin]

After the so called seamless software upgrade my N810 went into looping reboots. I didn't know what to do until I read about it in this forum. Can't thank you enough. The manual reflash took several tries.

This is why the Internet Tablet ecosystem sucks. This kind of things does not happens with an iPhone update.

[vinc17]

It's unfortunate that some have performed actions on their tablets that interfered with SSU, and they don't recall offhand what those actions were, but doing so in the first place was a risk they chose to take.

What??? Here SSU failed just because I removed user files. I would have never thought this would be a problem.

I have said this numerous times but I guess it is still not resonating with everyone: Nokia cannot possibly test for every single possible configuration out there.

If SSU fails just because the user has removed user files, this is entirely Nokia's fault.

[tso]

This is why the Internet Tablet ecosystem sucks. This kind of things does not happens with an iPhone update.

sarcasm?

(fullfilling minimum character requirements...)

[maacruz]

I'm not aware of any evidence to support that. AFAIK, all existing rotation packages prevent the update from starting in the first place. The main culprit for reboot loops seems to be the preinstalled documentation and media.
That's right, the rotation package doesn't break anything, it just may prevent you from installing the SSU because dependencies not met (something to do with xserver-xomap)
I think, from my experience, that there are three main causes for the reboot loops: the preinstalled documentation (why on earth a .deb touchs /home?), the rc.d handling scripts (they are not very... how to say it... mmm... they are very far from being what chkconfig in other systems is), and the package manager which dares to simply say that the SSU coudn't be installed and leave the system completely broken.

[briand]

If SSU fails just because the user has removed user files, this is entirely Nokia's fault.


Was it that the user files were removed, or that the .documents directory was moved or removed?

[daperl]

This is why the Internet Tablet ecosystem sucks. This kind of things does not happens with an iPhone update.

No Thanks!

or

-1 Troll/Flamebait

or

The humor went over my head.

Probably #3.

[Benson]

In my understanding, there's several ways it can fail, including if you've removed all the PDFs and left the empty directory.

I haven't gotten the package and looked at the scripts, but it sounds like a piece of work, alright.

[GeneralAntilles]

If SSU fails just because the user has removed user files, this is entirely Nokia's fault.

I always remove the bundled PDFs, and have never had an issue with the documentation package. So, clearly, this isn't the whole story.

[Mara]

I always remove the bundled PDFs, and have never had an issue with the documentation package. So, clearly, this isn't the whole story.

Maybe the keyword is "some files"? I did delete all but English user guide... and did end with the endless reboot loop. I never moved or symlinked the .documents directory.

[Texrat]

Yes. Please see bug # 3749 (https://bugs.maemo.org/show_bug.cgi?id=3749).

Comments from 4 different people, but only one vote.

...

[Texrat]

What??? Here SSU failed just because I removed user files. I would have never thought this would be a problem.

That response has nothing to do with the quote you responded to.

If SSU fails just because the user has removed user files, this is entirely Nokia's fault.

I didn't say Nokia had no responsibility.

Please read and respond more carefully, thanks.

[Laughing Man]

This is why the Internet Tablet ecosystem sucks. This kind of things does not happens with an iPhone update.

err. actually it does. Maybe not as often though since iphones are locked down so there's not much u can modify without jailbreaking it.

[vinc17]

Was it that the user files were removed, or that the .documents directory was moved or removed?
I didn't remove the .documents directory: some of my own document files (e.g. note.note.html from Notes) were in this directory, and I didn't want them to be removed. I just removed PDF files, and perhaps ~sfil_li_folder_user_guides since this directory became empty (but I don't remember). BTW, I thought that these PDF files were just files installed by default, with no relation with the package system (in Debian, documentation is in /usr/share/doc, never in the user's home directory).

[sjgadsby]

err. actually it does. Maybe not as often though since iphones are locked down so there's not much u can modify without jailbreaking it.

Indeed. A bug in iTunes 7.71 broke some iPhones.

[vinc17]

That response has nothing to do with the quote you responded to.
Then you shouldn't have responded to my post: you said that users chose to take a risk by doing some actions. I did not. So, why are you talking about risks?

I didn't say Nokia had no responsibility.
But in some posts, the user is blamed just because SSU failed for no special reasons:
Yes, well, they surely remember if they did something, and not report having done nothing when it's clearly not the case. Black periods are a symptom of a possibly severe neurological disorder. :rolleyes:
(Really, in my case, this is nothing... except standard use of the tablet of course.)

[vinc17]

I always remove the bundled PDFs, and have never had an issue with the documentation package. So, clearly, this isn't the whole story.
I looked at the /var/lib/dpkg/info/pre-installed-documentation-rx44.postinst script, and that's true that it should not fail just because the ~sfil_li_folder_user_guides directory is empty (unless this is due to a bug in busybox). I hope maacruz can give more information about:
It fails if the "/home/user/MyDocs/.documents/~sfil_li_folder_user_guides/" directory is a symlink or is empty. Make sure you have an actual directory with any file there.

Note 1: I'm not sure about the real cause of the SSU failure in my case. As the SSU didn't give any error message, it is really difficult to know. But if SSU really fails if ~sfil_li_folder_user_guides is empty, then this is the most probable cause of failure in my case.

Note 2: in case this is important, the MyDocs/.sounds directory was empty when I did the upgrade (but I don't see why this could be a cause of failure).

[Texrat]

Then you shouldn't have responded to my post: you said that users chose to take a risk by doing some actions. I did not. So, why are you talking about risks?

I'm confused. First you say you deleted doc files, then you say you did nothing.

Which is it?

And before you make this a circular argument by stating again that removing docs should not affect SSU, please note that I am in agreement and have asked that you join us in voting on and discussing the relevant bugs.

But in some posts, the user is blamed just because SSU failed for no special reasons.

I haven't seen a single post that does so, including what you quoted (and definitely not mine). No one is blaming users if SSU fails for no special reasons.

[vinc17]

I'm confused. First you say you deleted doc files, then you say you did nothing.

Which is it?
I did nothing except normal use of the tablet (I've deleted user doc files, but this isn't an action more particular than any other one concerning the files under /home/user).

[Texrat]

I did nothing except normal use of the tablet (I've deleted user doc files, but this isn't an action more particular than any other one concerning the files under /home/user).

I see you chose to ignore my plea for keeping this from going circular.

I'm out. Enjoy.

[vinc17]

I see you chose to ignore my plea for keeping this from going circular.
I already voted for bug 3750 (https://bugs.maemo.org/show_bug.cgi?id=3750) a few days ago. I don't think I can do anything else.

[Neon Samurai]

This is why the Internet Tablet ecosystem sucks. This kind of things does not happens with an iPhone update.

Is Apple allowing third party developers to freely release software without having to crack there phone with the jailbreak patch? Tell me again how fantastic the iPhone is when you manage to change the battery yourself and get it tripple booting between three OS.

[maacruz]

If you updated your system in mmc don't forget to modify again /usr/sbin/osso-mmc-umount.sh and /usr/sbin/osso-usb-mass-storage-enable.sh, they were overwritten by the SSU.

[tso]

two modest observations:

1. so far it has not randomly deleted any mails (knock on wood)

2. i just spotted it going to the next mail after i deleted the mail i was reading. as in, it didnt drop me back to the inbox first. im sure that got to be new behavior...

[Neon Samurai]

all good here.
- internal flash updated clean
- boot menu flashed clean
- external sd updated clean
- boot menu flashed clean again

none of the listed issues baked my install in the process. NIC on the sd even worked though hildon didn't show it. Now to see if the battery level shows correctly and Map will save favourits.

[ldrn]

Yick! So *this* was what was causing the problems. I'd find out my tablet wouldn't reboot, reflash and restore from backup, try the seamless update, have it fail -- then ignore it. A day to a few weeks later, I'd reboot my tablet for some reason, and blam... and clueless to why, I'd start redoing things again. :(

I am getting royally pissed off with the tablet set up process by the end of this. Can't Nokia save my time zone information and language and etc in the backup file?

Although in the end, I ignored my backup file. Based on what people have said here, I probably had deleted the user guides. I had to configure a lot of things manually each time anyway... man, this was the most painful update ever. Can't Nokia go back to non-seamless updates?:(

[benny1967]

This is why the Internet Tablet ecosystem sucks. This kind of things does not happens with an iPhone update.

Does the iPhone have OTA-updates at all? I thought Apple handled it all via iTunes? (I really don't know, just a question...)

[Makurosu]

Well, that didn't go so good. Here's my report. I ran the update and it locked my N800 so hard I had to take the battery out of it to get it to restart. Then it went into a reboot loop. So, I had to flash the device. Very nice. I'm not going to read 47 pages of this thread, but I'm guessing people aren't sitting around holding hands and singing cumbaya on this one.

It's up and running again now though, so I guess all's well that end's well. Sorta.

[eliagp]

same here, got into a reboot loop. Heck, at least I was expecting it. If it had work, it would have been great, but hey, I knew what I was getting into.

[Bundyo]

I have one rule when installing SSUs: I always start an xterm after that and run an "apt-get -f install" just to be sure. If app manager can't simulate the install, at least it can check if everything went ok before we restart...

[Peet]

It's been almost a week since the Seamless SU v4.2008.36-5 was unleashed and although there has been no word from its developers at Nokia, perhaps the unofficial Maemo gurus could help by compiling a Howto list of ways of minimizing possible pain when something goes wrong and posting the guide to the ITT front page (constantly updated when new valid information surfaces)?

Simply expecting the visitors to wade through 500 messages containing the odd tidbit of wisdom (and how do they know which advice is correct?) is a lot to ask IMO.

Also, it would appear that some of the update failures are caused by the latest SSU's install script so couldn't the script be made more error-proof and reissued?

[GeneralAntilles]

It's been almost a week since the Seamless SU v4.2008.36-5 was unleashed and although there has been no word from its developers at Nokia

There's been plenty of word, you just can't expect every one of them to waste their time replying here. ;) Watch (http://lists.maemo.org/pipermail//maemo-developers/) the right (http://lists.maemo.org/pipermail/maemo-users/) places (http://bugs.maemo.org/).

Personally, I'm investing my time this direction (http://maemo.org/community/council/view/1222953254.html).

[Peet]

It's good that there is debate going on among the developers, but ideally some of the fruits of that debate would trickle to the userspace.

Of course one problem is that the furball that is SSU is inviting the Diablo user to simply install it (it now being seamless and all) before hitting the forums...

[luca]

It fails if there is no files in "/usr/share/pre-installed/MyDocs/.documents/". Create that directory and touch or put a file there if you have that deleted.

I've not updated my n800 yet (I'm waiting for a replacement lcd), but I'm checking these prerequisites and I don't have that directory.
I don't remember deleting it (I just deleted the promotional video and the user guides in the languages I don't need, but even those in the user directory).
Could it be that it was removed in the postinstall script of pre-installed-documentation-rx34?

[urzatio]

Maybe I haven't seen the response to the constant reboot, yet... anyway, did the reboot, the internal memory had enough space (to my knowledge,at least), tried to re-flash using the 770flasher (yes I'm on a mac) but the flasher just says, Suitable USB device not found, waiting.... , now I have a nokia brick... lovely. :(

[maacruz]

Maybe I haven't seen the response to the constant reboot, yet... anyway, did the reboot, the internal memory had enough space (to my knowledge,at least), tried to re-flash using the 770flasher (yes I'm on a mac) but the flasher just says, Suitable USB device not found, waiting.... , now I have a nokia brick... lovely. :(
First try using a PC, use a liveCD if it doesn't have linux installed and it's not yours. You may carry flasher-3 on a usb memory

[GeneralAntilles]

First try using a PC, use a liveCD if it doesn't have linux installed and it's not yours. You may carry flasher-3 on a usb memory

Why? The OS X flashers work fine.

The logical first step is to make sure you're following the flashing procedure (http://wiki.maemo.org/Updating_the_tablet_firmware) correctly, then to rule out the hardware (make sure the USB cable is OK, try a different USB cable, make sure you're not connecting through a hub, etc.).

[windzilla]

I have one rule when installing SSUs: I always start an xterm after that and run an "apt-get -f install" just to be sure. If app manager can't simulate the install, at least it can check if everything went ok before we restart...


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...

[stevecrye]

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

[maacruz]

Hi all;
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.
$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.

[ldrn]

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/forums/showpost.php?p=33348&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.

[vinc17]

tried to re-flash using the 770flasher (yes I'm on a mac) but the flasher just says, Suitable USB device not found, waiting.... , now I have a nokia brick... lovely. :(
I reflashed my N810 with 770Flasher on my Mac and had no problems. Well, IIRC, Step 3 (http://wiki.maemo.org/Updating_the_tablet_firmware#GUI_with_770Flasher) was incorrect: I still had to select the firmware image from the file selector, but that was easy to guess. :)

[rittf800]

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.

[lm2]

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?

[windzilla]

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.

[tso]

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...

[luca]

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?

Yes, but well before the update:

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

[pkuhar]

My wireless stopped working failed NOT SO seamless software update. So I can'f fix my installation And my PC is not detection n800 via USB, so no reflash possible.
Any ideas? I was thinking of downloading whole repository to SD cards and try to update with that?

[Benson]

Reflash is possible, I'm sure; you're probably not doing the procedure quite right. But that's not the best solution anyway.

As for the network problem, that's been discussed some, but I haven't tracked it as mine wasn't affected. There's probably some info out there that'll help you figure out what packages, etc. are at issue.

[luca]

I've not updated my n800 yet (I'm waiting for a replacement lcd), but I'm checking these prerequisites and I don't have that directory.
I don't remember deleting it (I just deleted the promotional video and the user guides in the languages I don't need, but even those in the user directory).
Could it be that it was removed in the postinstall script of pre-installed-documentation-rx34?

Definitely is the post install scripts that removes /usr/share/pre-installed/MyDocs/.documents/ (I know because it made fail the second dpkg --configure pre-installed-documentation-rx34).
The first (and third ;)) one failed because I had symlinks in /home/user/MyDocs/.documents.
After removing the symlinks, recreating the directory /usr/share/pre-installed/MyDocs/.documents/ with a dummy file, a dpkg --configure pre-installed-documentation-rx34, a apt-get install and a flash-and-reboot I completed the update.
Thanks to maacruz message and this thread I avoided the reboot loop and having to reflash.
I hope next time the pre installed documentation won't cause these problems.

[cybic]

After the Update i have more power drain - cpu is always jumping between 10-50 percent :(

[Andre Klapper]

After the Update i have more power drain - cpu is always jumping between 10-50 percent :(

That's vague, tell us which exact process to blame...

[manooe]

just updated this and tested with GPS, I thought that fist-time-to fix GPS signal is less than 5 minutes which is much more faster then the previous Upgrade. It works as if A-GPS is included.

[cybic]

That's vague, tell us which exact process to blame...

Sure - Hildon Desktop always needs about 23% of CPU Time - eats Battery badely...

Also - maybe i'm wrong, but it seems to happen after i lock the device!

N810

[Xtremegene]

Finally braved this SSU as well - deleted the user guide PDFs, but also had many other random documents I've made. Update went through successfully and yeah, the web browser is even more snappier. Hopefully it'll be stable in the long term though. Onwards to cloning the OS to a 8GB SDHC card... and playing with Debian!

[zigzago]

I recently acquired a used N810. For what it's worth, I updated the firmware to 36-5 yesterday and have experienced no problems.

[bunanson]

I recently acquired a used N810. For what it's worth, I updated the firmware to 36-5 yesterday and have experienced no problems.

More info please, a step by step guide would be very appreciated. How do you do it? did you backup? You have rotation installed? Upgrade from OS?

TIA,

bun