I read through this thread trying to get help for an issue which I have currently with my efika mx smartbook.
I recently updated the kernel on a working system to the latest version available at:
kernel: linux-image-22.214.171.124.12-efikasb_10.08.00_armel.deb (2010-12-05, 8 MB, Debian package)
After doing so (dpkg --install linux-image...), my smartbook no longer boots. It appears to start booting, then hangs at the message:
[ ms ] Waiting for root device /dev/sda2...
In an attempt to rescue my system, I prepared an SD card from the maverick-installer.img taken from http://www.powerdeveloper.org/asset/by-id/113
Mouting the SD card on another Linux based system, the card appears to be ok:
/dev/sdb2 on /media/installer type ext4 (rw,noexec,nosuid,nodev)
/dev/sdb1 on /media/disk type ext2 (rw,noexec,nosuid,nodev)
[root@localhost ~]# parted /dev/sdb
GNU Parted 1.8.1
Welcome to GNU Parted! Type 'help' to view a list of commands.
Model: ChipsBnk Multi-Reader (scsi)
Disk /dev/sdb: 7959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 128MB 127MB primary ext2
2 128MB 1700MB 1572MB primary ext3
[root@localhost disk]# cd /media/disk
[root@localhost disk]# ls -la
drwxr-xr-x 3 root root 1024 Dec 7 19:57 .
drwxr-xr-x 4 root root 4096 Dec 29 19:03 ..
-rwxr-xr-x 1 root root 1704 Dec 2 20:25 boot.scr
-rw-r--r-- 1 root root 474 Dec 2 15:48 boot.scr-efikamx
-rw-r--r-- 1 root root 474 Dec 2 15:48 boot.scr-efikasb
-rwxr-xr-x 1 root root 1632 Dec 2 20:23 boot-script-installer
-rwxr-xr-x 1 root root 1646 Dec 2 20:23 boot-script-installer-debug
-rw-r--r-- 1 root root 65473 Dec 2 15:48 config-126.96.36.199.12-efikamx
-rw-r--r-- 1 root root 65601 Dec 2 15:48 config-188.8.131.52.12-efikasb
-rw-r--r-- 1 root root 6253539 Dec 2 16:12 initrd.img-184.108.40.206.12-efikamx
-rw-r--r-- 1 root root 6245283 Dec 2 20:24 initrd.img-220.127.116.11.12-efikasb
-rwxr-xr-x 1 root root 281 Dec 1 01:02 kernel-prep
drwx------ 2 root root 12288 Dec 7 19:43 lost+found
-rwxr-xr-x 1 root root 76 Dec 1 01:02 script-prep
-rw-r--r-- 1 root root 856891 Dec 2 15:48 System.map-18.104.22.168.12-efikamx
-rw-r--r-- 1 root root 864308 Dec 2 15:48 System.map-22.214.171.124.12-efikasb
-rwxr-xr-x 1 root root 149496 Dec 2 18:51 u-boot-2009.01-2.0.6-efikamx
-rwxr-xr-x 1 root root 165060 Dec 2 18:51 u-boot-2009.01-2.0.6-efikasb
-rw-r--r-- 1 root root 1926372 Dec 7 18:51 uImage-126.96.36.199.12-efikamx
-rw-r--r-- 1 root root 1934572 Dec 7 18:51 uImage-188.8.131.52.12-efikasb
-rw-r--r-- 1 root root 6253603 Dec 7 18:51 uInitrd-184.108.40.206.12-efikamx
-rw-r--r-- 1 root root 6245347 Dec 7 18:51 uInitrd-220.127.116.11.12-efikasb
-rw-r--r-- 1 root root 1926308 Dec 2 15:48 vmlinuz-18.104.22.168.12-efikamx
-rw-r--r-- 1 root root 1934508 Dec 2 15:48 vmlinuz-22.214.171.124.12-efikasb
However, with the SD card inserted, it appears to still boot from the internal *disk* (hangs with same error).
I have also unsuccessfully tried to boot the system from an SD card which was prepared with sb_rescue_2GB.dd.lzma. In this case, the system remains with a blank screen when powered up (I let it sit for 5 minutes or so).
Any pointers would be greatly appreciated.
It seems at first it didn't update to the new U-Boot. Second of all please do not use Peter's rescue image (just edit the etc/rc.local on the Maverick SD to remove the /home/oem/install line)
When you're booting with the new kernel from an old system, since we modularized PATA and MMC subsystems to match the rest of Ubuntu, you MAY (if it didn't autodetect the need for it, sometimes it doesn't) need to add
And then run
update-initramfs -c -k 126.96.36.199.12-efikamx
Before it is useful (or, add those lines and then remove and reinstall the kernel package).
flash-kernel should run automatically from update-initramfs but somehow it doesn't. It's always safer to run it manually if you update yourself. The packaging system will run it automatically though since we added the support for this in the new Maverick image.
Pretty much everything can be solved with an update to the new image. The number of changes we made aren't huge and they're all fiddly little config updates.
We'll be providing a new image very shortly which will allow updating to a system with the accelerated graphics and hopefully we will have solved some of these.
Apologies for how "quirky" it is, but without decent mainline support in Ubuntu this is how we have to live with the machine operaton. Some of the things we
"fixed" don't seem to fail for any good reason in the first place, and others that stay broken are because the defaults in Ubuntu are very hard to change when gconf is concerned..
First though let's make sure you're at the latest U-Boot..
Matt Sealey, Genesi USA Inc.
Product Development Analyst