Thread: Mini Is there a reason why we currently cannot run Android on the Kobo Mini?
View Single Post
Old 05-08-2015, 10:19 AM   #5
MarekGibek
Zealot
MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.MarekGibek is out to avenge the death of his or her father, Domingo Montoya.
 
MarekGibek's Avatar
 
Posts: 129
Karma: 34471
Join Date: Aug 2013
Location: Cracow, Poland
Device: Kobo Touch N905C
Quote:
Originally Posted by bluearcus View Post
Hi Marek,

I've been looking into this... it looks like a kernel issue.

Taking your latest Kobo Touch image, and applying the Kobo Mini Uboot, HWConfig and the required (one byte) change to the uboot strings to force /dev/mmcblk0p2 gives me the same result as dancol90 was getting, namely a hang on the rootfs availability.

Which reminded me of similar hangs on desktop installations after careless kernel changes.

So I took the original kobo mini kernel and pasted that into the image....

At which point everything goes swimmingly -

Code:
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SDHC card at address 0002
mmcblk0: mmc0:0002 N/A   7.50 GiB 
 mmcblk0: p1 p2 p3
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
Freeing init memory: 112K
Kernel panic - not syncing: No init found.
So it looks like the mmc hang is because we are missing something kobo-mini specific on the MMC HW side in the kernel build :-(

Regards,

Mike
Hi Mike!

That's cool. You were able to boot kernel. But it cannot be original kobo kernel. Android kernel needs to have applied Android patches. For example it doesn't use Linux's init boot schema (Android kernel starts different app on the start), so that's why you can see this error. What error messages do you have if you use Android kernel from here?
https://github.com/marek-g/kobo-kernel-2.6.35.3-android

/Marek
MarekGibek is offline   Reply With Quote