How to update Kindle 2/DX/DXG with YifanLu's firmware from 3.2.1 to 3.4.2

[knc1]

So lets back-port 5.6.5 to it and tell Amazon its a large screen Kindle Voyage and we want the newest of new book formats sent to it.

[thatworkshop]

Originally Posted by knc1

So lets back-port 5.6.5 to it and tell Amazon its a large screen Kindle Voyage and we want the newest of new book formats sent to it.

@newman, @knc1: Let's take it to PM. (not prime minister, private msg)

[knc1]

Originally Posted by idoit

@newman, @knc1: Let's take it to PM. (not prime minister, private msg)

I don't think the result would be worth the effort.

The "2-series" devices don't have enough memory or processor resources.

Plus, we probably would not get far trying to run ARMv7 code on an ARMv6 core.

[rockiecxh]

I failed with U007 error when trying to upgrade from 3.2.1 to 3.3. Everything seems fine, even the md5 value is same as demoed in the instructions. No luck.

[knc1]

Originally Posted by rockiecxh

I failed with U007 error when trying to upgrade from 3.2.1 to 3.3. Everything seems fine, even the md5 value is same as demoed in the instructions. No luck.

There are a lot of details in that section which you did not mention what happened in your case.

Let's work backward from the 3.3 -> 3.4 header -

Copy that file to Kindle's USB root and run it from Kindle's interface. YifanLu adds: "You might get an error and it's OK because some of the modem files may be different, but your Kindle will be updated regardless." I did not get any error, so I can't verify that.

After restart your Kindle should be upgraded to "3.3 (611680021)", verify that in Settings.

What have you done and what where the results relating to those two paragraphs?

[NiLuJe]

U007 means you most likely have a borked jailbreak, or did something stupid with the public keys at one point.

[thatworkshop]

Originally Posted by NiLuJe

U007 means you most likely have a borked jailbreak, or did something stupid with the public keys at one point.

Oh yea, pretty much...

Sorry if I sounded like South Park Eric Cartman. Just finished an episode.

[newman]

Just an update on using swap file on Kindle (a way to get rid of the low virtual memory problem while using bspatch in upgrade of webkit libs, or as a permanent option to enlarge Kindle's virtual memory): It corrupts /mnt/base-us/ filesystem frequently! I usually noticed that when plugged Kindle via USB to PC and Calibre told me that mounted FS is probably read-only. Even when I fixed those corruptions with fsck they were happening again and again... When I removed the swapfile (it was on /mnt/base-us/) the corruptions are gone. I guess it may have something to do with remount of /mnt/base-us/ filesystem when Kindle is attached to PC via USB.

[knc1]

Originally Posted by newman

- - - - -
When I removed the swapfile (it was on /mnt/base-us/) the corruptions are gone.

I guess it may have something to do with remount of /mnt/base-us/ filesystem when Kindle is attached to PC via USB.

Does the same happen when the swapfile is on /mnt/us ?
I don't recall which of those FUSE layered file systems twobob used.

I do recall that twobob did his work via ssh over wifi.
(ssh, sftps, scp, vlc, etc)
The USB cable was just used for external power.

So it is possible that in his use-case he never had the opportunity to discover any inter-action with the exchanging of kernel driver modules and the swap storage.

But I do know that he ran native compiles on his K5 that where long running (libwebkit-gtk takes days) without troubles.

Some of the other people using swap - - -

Some created a file in USB storage, converted it to a device (with losetup) and then used the swap partition driver on that device.

Geekmaster used (or at least tested) doing swap over an NBD over WiFi connection to his pc.
I don't recall if he ever used (or even tested) NBD over the USB cable network.

One note on the NBD + network driver combination -
There is (or at least there was) a rather rare kernel deadlock path in that combination.
But it is (or was) rare and did not corrupt anything, just required a hard (power button) re-boot.

[thatworkshop]

wuh?!!! I use swapon /mnt/us/ all the time (size 256mb).
No issues insofar.

[knc1]

Originally Posted by idoit

wuh?!!! I use swapon /mnt/us/ all the time (size 256mb).
No issues insofar.

That may be the key, to use /mnt/us/ rather than /mnt/base-us.

I might have even written: 'use /mnt/base-us/' somewhere, I honestly don't recall if I did or not.
I am sorry for any trouble I caused if it was my doing.

[NiLuJe]

I'd honestly have said use base-us too, to avoid the fuse layer of interaction (I wouldn't even have expected swap to work on top of a fuse proxy), so, yeah .

[knc1]

Originally Posted by NiLuJe

I'd honestly have said use base-us too, to avoid the fuse layer of interaction (I wouldn't even have expected swap to work on top of a fuse proxy), so, yeah .

I would have expected it to deadlock almost immediately.

At least if it allocates memory.
Anything that allocates memory in the path of servicing swap (which gets accessed by shortage of memory) would seem to be a no-no.

Hey, but if it works . . . .

[thatworkshop]

Originally Posted by knc1

That may be the key, to use /mnt/us/ rather than /mnt/base-us.

I might have even written: 'use /mnt/base-us/' somewhere, I honestly don't recall if I did or not.
I am sorry for any trouble I caused if it was my doing.

On my side, everything looks good, M. Thanks.

By the way, I wish Kindles were System on SD card too, just like some models of Kobo are. It would have been phenomenal!

[newman]

I mean this:

dd if=/dev/zero of=/mnt/base-us/swapfile bs=1M count=64
chmod +x /mnt/base-us/busybox
/mnt/us/busybox mkswap /mnt/base-us/swapfile
/mnt/us/busybox swapon /mnt/base-us/swapfile

It's the only combination of /mnt/us × /mnt/base-us which worked for me. It does not work for me with /mnt/us/ (not sure which step exactly).