[Gta04-owner] Update of my GTA04 to latest production image and QtMoKo v56
Dr. H. Nikolaus Schaller
hns at goldelico.com
Wed Jul 17 19:00:34 CEST 2013
Am 17.07.2013 um 17:32 schrieb Sebastian Reinhardt:
> Am 17.07.2013 16:09, schrieb Dr. H. Nikolaus Schaller:
>> Hi,
>>
>> Am 17.07.2013 um 15:59 schrieb Sebastian Reinhardt:
>>
>>> Hello,
>>>
>>> I read about starting support of camera and fm-transceiver, so Yesterday, I updated my GTA04 to this version of boot files:
>>>
>>> http://download.goldelico.com/gta04/20130716-GTA04-Production-Universal/
>>>
>>> This, what I have done:
>>> 1. create a SD-card with "makesd" (taken from site above, replaced the /dev/sdx by correct /dev/sde)
>>> 2. I booted my Moko from this card, everthing was fine. I was able to scan the frequencies and test the cam.
>>> 3. ./flash_nand => I flashed the new file into NAND, but I got these messages:
>>> -----------------------------------
>>> root at gta04:~# ./flash-nand
>>> flashing Kernel
>>> flash_eraseall has been replaced by `flash_erase <mtddev> 0 0`; please use it
>>> Erasing 128 Kibyte @ 3e0000 -- 100 % complete
>>> Writing data to block 0 at offset 0x0
>>> ..
>>> [snip]
>>> ..
>>> Writing data to block 24 at offset 0x300000
>>> flashing Rootfs as UBIFS
>>> umount: ubi0:gta04-rootfs: not found
>>> ubiformat: mtd4 (nand), size 530055168 bytes (505.5 MiB), 4044 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
>>> libscan: scanning eraseblock 4043 -- 100 % complete
>>> ubiformat: 4032 eraseblocks have valid erase counter, mean value is 5
>>> ubiformat: 12 bad eraseblocks found, numbers: 807, 1125, 1203, 1373, 1689, 1955, 2475, 2503, 3383, 3425, 3681, 3727
>>> ubiformat: formatting eraseblock 889 -- 22 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 889 (mtd4)
>>> error 5 (Input/output error)
>>>
>>> ubiformat: error!: failed to erase eraseblock 889
>>> error 5 (Input/output error)
>>> ubiformat: marking block 889 bad
>>> ubiformat: formatting eraseblock 4043 -- 100 % complete
>>> UBI device number 0, total 4031 LEBs (520095744 bytes, 496.0 MiB), available 3958 LEBs (510676992 bytes, 487.0 MiB), LEB size 129024 bytes (126.0 KiB)
>>> Set volume size to 510676992
>>> Volume ID 0, size 3958 LEBs (510676992 bytes, 487.0 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "gta04-rootfs", alignment 1
>>> copying files (takes a while)
>>> tar: Read checkpoint 100
>>> ..
>>> [snip]
>>> ..
>>> tar: Read checkpoint 48000
>>> tar: ./dev/log: socket ignored
>>> tar: ./boot: implausibly old time stamp 1970-01-01 00:00:00
>>> tar: Read checkpoint 48100
>>> tar: ./dev/pts: implausibly old time stamp 1970-01-01 00:00:00
>>> tar: Read checkpoint 48200
>>> tar: ./run/sdp: socket ignored
>>> tar: ./run/dbus/system_bus_socket: socket ignored
>>> tar: ./run/udev/control: socket ignored
>>> tar: Read checkpoint 48300
>>> ..
>>> [snip]
>>> ..
>>> tar: Read checkpoint 65700
>>> copied
>>> patching and syncing
>>> synced
>>> Filesystem 1K-blocks Used Available Use% Mounted on
>>> rootfs 30612932 887856 28170004 4% /
>>> /dev/root 30612932 887856 28170004 4% /
>>> devtmpfs 244792 0 244792 0% /dev
>>> tmpfs 48980 352 48628 1% /run
>>> tmpfs 5120 0 5120 0% /run/lock
>>> tmpfs 97940 0 97940 0% /dev/shm
>>> tmpfs 244892 8 244884 1% /tmp
>>> tmpfs 244892 0 244892 0% /var/tmp
>>> /dev/mmcblk0p1 64448 4969 59479 8% /boot
>>> ubi0:gta04-rootfs 466452 418612 43000 91% /mnt/nand
>>> done.
>>> root at gta04:~#
>>> -----------------------------
>>> Can I ignore these error messages?
>> Yes. There is no serious message between.
> Great. I was a little bit concerned about the "input/output error"... :-)
>>
>>> 4. replaced these boot files on QtMoKo SD-Card by new ones:
>>> ------------------
>>> bootargs.scr
>>> boot.scr
>>> menu.rgb16z
>>> MLO
>>> splash.rgb16z
>>> u-boot.bin
>>> u-boot.flash
>>> uImage
>>> x-load.flash
>>> ------------------
>> Well, there may be something incompatible with QtMoko.
>>
>> First of all you only need to have these files on the SD card (since you don't want to flash U-Boot/NAND every time you boot with AUX button pressed):
>> * bootargs.scr
>> * uImage
> I have also the gta04-init- dir, to get the boot menu (QtMoko, NAND, 1st. shell, 2nd shell). But this ist not displayed any longer, *hmf*? Ok, I do not need it in normal operation....
>>
>>> 5. boot QtMoko
>>>
>>> Booting QtMoko works fine, but no RF- devices are available, no Modem, Bluetooh, WLAN and also no USB-Connection! What is wrong?
>>>
>>> I guess, I made any mistake, so what? Please help, because I do not like to flash the old version again....but I like to take calls, too.
>> Maybe it needs a reboot. And maybe the kernel module database (depmod -a) may be out of sync. I don't know if QtMoko uses the same kernel name to look for them.
> a depmod -a says:
> -----------------------------------------
> ERROR: could not open directory /lib/modules/3.7.0-offmode-gta04: No such file or directory
> FATAL: could not search modules: No such file or directory
> -----------------------------------------
> Ok, no problem. I made an link:
> ---------------
> cd /lib/modules/
> ls -l
> 3.7.0-gta04-qtmoko-v56
> 3.7.0-offmode-gta04 -> 3.7.0-gta04-qtmoko-v56
Ah, that may not do what you expect. AFAIK a symlink is not sufficient to make the
modules work with a different kernel.
I think you should install the correct kernel modules:
http://download.goldelico.com/gta04/20130716-GTA04-Production-Universal/modules.tgz
> ---------------
> Now "depmod -a" work without error messages => Reboot => but still no RF's/USB!
>
> One question: What ist an "offmode" Kernel?
Hm. I don't know... This was inherited from the neil-brown kernel and is the name of the kernel.
Maybe it is set somewhere in the default .config.
And Radek likely has changed it for "his" kernel to be 3.7.0-gta04-qtmoko-v56
>
> If I call "System Info" in QtMoKo I get suspicious output:
> Version: 55 (hä?, I called "apt-get upgrade", why is this v55?)
> Qt version: 4.8.3 (seems ok)
> .....
> Linux Kernel
> 3.7.0-offmode-gta04
> Compiled by: (hns at iMac.local)
>
> Then "no Modem", "No SIM is detected....", Network: GPRS/3G => nothing, WLAN => "unavailable"
>
> And now? I think the "offmode" is not ok, or is it?
In general it shows that it is still not easy to swap kernels without a matching rootfs (at least kernel modules).
BR,
Nikolaus
More information about the Gta04-owner
mailing list