Well, you may not like the term "crappy", but I agree with Karel that the app manager is highly perfectible, both in its ergonomics and functionality.

Indeed, repositories being sometimes unavailable are not the app manager's fault (but should we need so many ?...). OTOH, it could and should be much easier to enable/disable them as needed without painstakingly editing them one by one through that tiny list window that looks like it was designed by Torquemada...

Also, you'd think that instead of the three lone, useless and disabled buttons making up the tool bar on the app's main screen, there could be shortcuts for useful functions available only from submenus : install package from file, refresh package list, show installer log, manage repos...

Apart from these ergonomics 101 basics, the app manager *does* have an unfortunate tendency to end up in a sort of limbo where it doesn't really work anymore as far as installing and uninstalling are concerned. I suspect many users just shrug it off and take advantage of the next firmware update to flash the problem away ; others use black-magic commands in xterm to straighten it up, using one after another gleaned in the forums until one works.

In either case it's not the fault of the repos, and not the user's (happens even without tinkering with Red pill mode or command line dpkg or whatever). It's just that the app is not as robust and reliable as we usually expect a package manager to be : and that is, huh... looking for the appropriate word here... well, yes, crappy.

In this sense I understand Karel's misgivings about relying on this tool to manage entire OS life cycles from Chinook onwards, like we do on desktops and servers, without the recurrent "clean sheet" firmware flashing we've had till now (no matter how much we hate 'em), and without assurance that it's been (being ?) *seriously* upgraded...

Here you go, just the kernel image for 4.2007.38-2....

http://nmacleod.com/nokia/n800/zImage-4.2007.38-2 (1,317,632 bytes)

You may better also flash initfs (and wait a bit for updated bootmenu). Whole initfs is recompiled. Maybe from same source but I guess at least wlan driver modules are new and may contain some (or even most?) fixes.

My understanding is the only thing that changed was the kernel, is this not the case??

Initfs has changed as well, how much we'll only know once fanoush has a chance to take a look. When I tried his initfs_flash utility, with a fresh new install, it exited and warned that there was a new initfs version being used.

Kernel modules in initfs are also part of kernel. I guess fix for corruption when downloading via wlan may be in wlan driver. Modules in initfs are recompiled so this may be the reason why.

BTW, I have updated initfs_flasher.tgz with changes for this FW. It is untested but I hope it will work. There are no changes in linuxrc script which is the only thing that matters for bootmenu.sh script. USB recovery mode is also included but you may always answer no if you don't want it.

My initial guess, was the ext2/3 modules, not wlan. But was just a guess...

I just stuck the new kernel on, and it seems OK so far - booted fine, got WiFi etc.

Annoying to see that Nokia still don't output the card speed to dmesg - that's a really useful feature present in the "community" SDHC kernel... guess I'll need to submit an enhancement request for a flaming obvious feature that Nokia leave out.

Excellent! Worked for me, thanks fanoush! Now I can get back to work.

(and hope and wait for Philip to make another kernel with 48MHz support...)

Yes, but you may still not get the fix. On the other hand kernel modules are changed but size is still the same so maybe it is just rebuild from same source. We may know more when someone from Nokia answers bug #1204