Quote:
Originally Posted by knc1
You **MUST** install the kernel and the rootfs as a **matched pair**!
|
Thank you for the reply. I want my DXG to run perfectly and don't like those ERRORs either. I checked for the missing modules and found they were not being used at least during usbNetworking:
Code:
Module Size Used by
g_ether 28364 0
ppp_async 12484 0
crc_ccitt 1952 1 ppp_async
ppp_generic 25492 1 ppp_async
slhc 6624 1 ppp_generic
mxc_alsa_pmic 36480 1
snd_pcm 84421 1 mxc_alsa_pmic
snd_page_alloc 8520 1 snd_pcm
snd_timer 24740 1 snd_pcm
snd 49188 5 mxc_alsa_pmic,snd_pcm,snd_timer
mma7660F 28376 0
mxc_keyb 18968 1
uinput 10816 0
fuse 48404 2
arcotg_udc 48724 1 g_ether
charger 28992 1 arcotg_udc
mwan 8052 1 ppp_async
eink_fb_shim 126620 0
eink_fb_hal_broads 370172 0
eink_fb_hal 58884 6 eink_fb_shim,eink_fb_hal_broads
fiveway 20352 1
The expected modules must not be there even without usbnetworking when the update routine is shutting down the services and so causes the ERRORs.
The kernel from Yifan Lu and the OS 3.1 from Yifan Lu should be a matched set because I haven't flashed any different kernels or rootfs partitions since I first used my K3G to upgrade the DXG to 3.1 so I think that much is normal. I would be surprised if everybody didn't have those errors with the DXG. Of course, the 3.1 OS has some 2.5.8 features with the custom 2.5.8 kernel.
I now suspect the ERROR might be because there is no WIFI or the 3G WAN was turned off and the Lab126 didn't test for that before trying to remove the modules. Maybe they have something to do with the recovery kernel. Whatever is running the rmmod in preparation for the update still allows continuing into the update so I think there could be another reason. I tried to get more information with ;debugOn and then Update with the same result. I think this is the relavent part:
Code:
151102:162349 system: I S50updater:def:wand shutdown complete
151102:162350 system: I S50updater:def:read bundle line [/mnt/us/update-06-558700031-611680021.bin]
151102:162350 system: I S50updater:def:Applying update /mnt/us/update-06-558700031-611680021.bin
151102:162350 system: I S50updater:def:Size of update: 1926999 bytes
151102:162351 system: I S50updater:def:Version before update: 031-S1-055870
151102:162351 system: I _otaupexec:def:processing update /mnt/us/update-06-558700031-611680021.bin
151102:162351 system: I _otaupexec:def:version is "FC02"
151102:162353 system: I _otaupexec:def:update image checksum OK
151102:162357 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/update-06-558700031-611680021.bin"
151102:162357 init: Switching to runlevel: 5
That doesn't help at all. The update lasts for 7 seconds until the upgrade is unsuccessful and issues the U007 reason. I still suspect the jailbreaks and am now going to investigate. I remember reading about a leftover certificate that can cause the U007. Some say once the Kindle is jailbroken there is no reason to uninstall or reinstall the jailbreak and some say the jailbreak should be kept up-to-date. At least I have a backup now in case I spoil my current installation.
There is a possibility the U007 is caused by my history with the KDX and maybe with the K3G before the DXG upgrade. I have used various hacks like usbNetworking, launchpad, readabilitymod, updatesprovider, screensaver and readers like Duokan, Librerator, kpdfviewer and coolreader3. Those are now gone except for usbNetworking and launchpad. I have tweaked the DXG on my own only in the area of the logs where I turned off the logging until just decided to try the 3.4.2 upgrade. When changing the logging I might have modified a couple of files that Amazon checks for changes. I don't know. This is a confusing mystery.
Maybe I should read all of the Kindle Developers Corner again because I know others have had the U007 problem. I need to look into the jailbreaks. Thanks for the attempt knc1.