Firmware Update
U-Boot 2.0.6 includes support for booting both systems under the same autoscripting system that other ARM boards (Marvell Dove, Beagleboard) utilize - on boot, the firmware will scan SD card and PATA for the first partition of format VFAT (MSDOS) or ext2/3 (Linux) and try and load a file called "boot.scr". This is all U-Boot does in the latest version. This is a departure from the system used on shipping TO2 and TO3 Efika MX Smarttop systems which would simply scan SD then PATA for "uImage" and blindly load it with built-in kernel boot arguments. The net benefit is that you gain support for
- Setting boot arguments for the kernel in an editable file on disk (SD or PATA)
- Using Initrd ramdisks (essential for current Ubuntu installations, enabling more modular kernel images)
- Doing any pre-boot scripting you need to perform before the kernel loads
Kernel Update (2.6.31.14.12 - efikasb-10.08.00 branch)
- Operates on ALL Efika MX models (TO2, TO3, Smartbook)
Includes updates to GPU kernel module, many fixes to platform support for TO2 boards, Smartbook improvements such as USB suspend issue being fixed, and also the "vertical offset" display bug fixed. The packages include a modular kernel without MMC, PATA or USB support compiled in - these are modules and it is expected by the behavior of Ubuntu that these are loaded from the initial ramdisk generated upon installation.
NOTE: If you install this kernel on an older Maverick system PLEASE add the modules "pata_fsl", "ehci_hcd", "mx_sdhci", "mmc_block" to the /etc/initramfs-tools/modules file in order for them to be forcibly added to the initial ramdisk on installation.
Maverick System Update
- Operates on ALL Efika MX models (TO2, TO3, Smartbook)
The desktop image has been updated to GNOME rather than Xfce since it is more stable and user friendly. The installed system image is not substantially bigger on disk, and includes OpenOffice. All updates to the end of November have been applied so there should be very little in terms of packages that are out of date. All systems (Smarttop TO2, TO3 and Smartbook) will boot into the installer, copy in the image to the PATA disk, reboot and ask for Language, Timezone, Keyboard settings, Username, Password, Machine Name and suchlike. This will replace the old "oem" user with one of your choice.
You may need to add yourself to the "Audio" and "Video" groups to enable sound and webcam access. You can do this as you log in to the system for the first time through the Users and Groups control panel item.
NOTE: please do not select "Encrypt my Home folder" - something is not operating correctly in the setup of ecryptfs, and the result is that it will give you a basically broken system. We realise the importance of a secure environment especially for workplaces where access to VPNs or corporate networks is only authorized with encryption enabled, and we are working on a solution.
Okay, I got the maverick-installer.img.xz file, how do I install it to my system?
Simply extract the archive (WinZip, 7-Zip, or command line at your option) and use your favorite utility here to copy it to a 2GB SD card. The utilities recommended are "dd" (or dcfldd), "flashnul" on Windows, or on an existing Ubuntu installation the Ubuntu USB Image Writer (you can find a list of imaging utilities here).
As an example with "dd", you can do the following:
xz -dc maverick-installer.img.xz | dd of=/dev/mmcblk0
Once you have this image on an SD card simply power off your system and insert the SD card. Power it back on and the system will install automatically and when complete, shut down automatically. You may then remove the SD card and boot into the installed system. It really is that simple.
If you have problems seeing the Progress of the installation (HDMI or DVI monitor not working correctly), we would much appreciate the details of your monitor. We have tested on several (upwards of 10) HDMI and DVI monitors and HDTV units with successful results, however there are reports of other monitors not working ideally. This is under investigation. If you had any problems with your monitor in the past, you may want to check on IRC or on the forums before installing a Smarttop and potentially getting no display..
Thanks Matt for all your efforts!
ReplyDeleteOn my T03 Smartbook I have decided to follow the suggested option, restart from scratch from the new installation that I have put on my 2GB SD CARD with the command: xz -dc maverick-installer.img.xz | dd of=/dev/mmcblk0
After that I have switch off the Smartbook and then I have put on the SD slot my SD card with the maverick installation , take from http://www.powerdeveloper.org/platforms/efikamx/linux
I have switch on the SB and the power on light and the lock light blink for a while and then I can see the backlight on the LCD without any image in the screen. Waiting if something happen after 5-10 minutes the backlight switch off and nothing happen.
If i press power button the backlight appear again.
After that I have power off the SB, eject the SD card and switch on again my SB but the SB is not anymore usable, I can see the blink of power light and lock light , the backligth appear but nothing happen.
Apologies. For some reason the SD card image is getting corrupted. I cannot tell if it is in the imaging of the card (compression on my side) or on user side (if you image the card and GNOME mounts the FAT partition, it tends to trash it).
ReplyDeleteI am making a fresh new image to upload that will have been tested yet again through the whole testing plan on a batch of TO2 and TO2 systems and Smartbooks (5 of each, using 3 SD cards rotating them through the batches to see if the cards are getting corrupted in use).
In the meantime there IS a possibility that a) it has not downloaded correctly and b) that your OS is automounting the card as it is copying the image to it. I can hint as to how to turn it off in GNOME (~2.30) but in KDE or older GNOME it is a mystery to me how you'd stop it doing it. They keep moving the configuration around with udev/hal/dbus changes.
Thank you for working on the encrypted home directories! That helps me to recommend the smartbook not only as a developers machine but also for work for my colleagues!
ReplyDeleteSame thing here :-(
ReplyDeleteApparently, booting on that image not only failed to boot and/or to display anything on script (but did turn on the backlight), it also bricked the device even when I subsequently remove the disk. :( :( :( :(
Device here is a TO3.
Same here, smartbook, backlight nothing happens, mine isn't bricked through
ReplyDeleteNot sure if this is related, but the new kernel doesn't fix the lid (usb reawakening) problems. I'm trying to build one, but getting errors. If you want me to test, let me know...
ReplyDeleteSame here, including the fact that the sb doesn't seem to boot off of the PATA when no SD card is present.
ReplyDeleteA couple of times, I've tried booting off of the SD with the power cable disconnected and seen single-line diagnostic messages on the sb console.
I don't have a serial cable connected, and wonder if that's relevant.
Matt, instead of a disk image, which is not all that portable due to the partition table, can you make filesystem images?
ReplyDeleteOr does some utility somewhere want things to be at a fixed sector number on disk?
By filesystem images, I mean, tarballs, one for the FAT filesystem, one for the ext4 filesystem. That plus simple instructions on using fdisk, mkdosfs and mke2fs.
ReplyDeleteHopefully, the thing is not completely bricked, just in a bad state (but how can we tell?).
You can't tell. I am making a new image right now it will be up within the hour (i.e. about midnight in Europe, 7th December).
ReplyDeleteThe reason we don't ship filesystem tarballs is because it is cruel and unusal for people who do not have another Linux box and the instructions to use fdisk, msdosfs and mke2fs do not work on Macs, they change per Linux version, and it is generally really quite annoying.
By shipping a disk image we can quantify the problems people have and it can be extracted and imaged to an SD card on any platform you are capable of using an SD card with.
That, and we'd be doubling the work to ship the filesystem images AND an image for an SD card. In the end, the image Should Just Work(tm) but we're fighting a U-boot bug.
OK, I found a recipe to mount subpartitions of a disk image with a combination of fdisk -l -u -C 512 foo.img and mount -o loop,offset=$(($start_sector * 512)) foo.img /mnt
ReplyDeleteas explained by
http://wiki.edseek.com/guide:mount_loopback
found by google.
Then I see that the uImage file in the "TO* updater" image is the same that was in the previous maverick image.
Have you updated the maverick image itself yet? The page doesn't hint at an update...
I can confirm that now with last image of maverick installation WORK PERFECTLY!!!
ReplyDeleteNow my Efika Mx SB is up again!
The new image of maverick boots into the ubuntu name and logo with five "progress" dots that change color, but nothing else seems to happen for many minutes - much longer than a usual ubuntu installation. Using Ctrl-Alt-Fn, I can switch virtual terminals, but there's no shell in sight to try to diagnose the issue.
ReplyDeleteAt least the machine is not bricked, but it's still unusable.
Pressing ESC repeatedly at the beginning gives me console output, the shells I was wanting, and makes it work faster than I had to wait in the dark the first time around. Go figure!
ReplyDeleteThanks for this working update.
The documentation is a bit confusing... should I follow the pdf:
ReplyDeletehttp://www.powerdeveloper.org/asset/by-id/117
Where it's stated that one should update to Uboot 2.6 first ?
Or follow this post where you mention:
"
It is therefore shipped as part of the Maverick installer. We recommend everyone simply update to Maverick.
"
If the latter is true, why not remove the Uboot image and PDF section altogether to avoid confusion ?
In other words, step-wise should I:
ReplyDeleteA:
1) Use SD card with maverick-installer.img.xz directly.
-or-
B:
1) Use SD card with efikamx-updater.img.xz.
2) Power off.
3) Use SD card with maverick-installer.img.xz.
Thanks in advance !
but I have understood that with the Smartbook is not needed efikamx-updater, so I had only make the step 3)
ReplyDeleteOk, having an Efika MX (not the smarttop), I guess I should go for full "B" procedure then... is that right, Matt/robyinno ?
ReplyDeleteThanks ppl!
Updated the updater
ReplyDeleteThen updated to Maverick... *but*:
"An error occurred while mounting /var/run"
Press S to skip mounting or M for manual recovery
Too bad that the USB keyboard is not recognized and cannot press any key :_/
Sorry my delay to check the comments...
ReplyDeleteI have made only A option. 1) Use SD card with maverick-installer.img.xz directly.
Have you retried to make only A) ?
If the problem persist I think only Matt can answer you.
I don't understand the problem, guys :)
ReplyDeleteCan you file a bug report at http://launchpad.net/efikamx ?
Ack, reported:
ReplyDeletehttps://bugs.launchpad.net/efikamx/+bug/693762