Most OSs from the DVD2/images fail to run

RazZziel
Hi, I've just purchased a Tiny6410SDK with N43. I've built a 4GB SDK with
the provided SD Flasher and the "images" directory on the SD2, with no
problems.

However, most OSs fail to run or install.

If I try installing the OSs on the NAND Flash, WindowsCE6 works (althrough
it's in Chinese, and I don't know how to put it in English), but all
Android, Linux and Ubuntu fail. They install correctly, but fail to run. On
my serial terminal, I see all kinds of kernel panics, etc, on all of them
(I can provide logs if necesary).

If I try running the OSs from the SD card, WindowsCE6 runs, and this time
Linux runs as well. Ubuntu still fails, and Android fails, but this time at
least, instead of kernel panicking, it shows the boot logo, but halts
there, and shows some errors, like:


--------------------
mount: mounting /sdcard on /r/sdcard failed: No such file or directory
init: cannot open '/initlogo.rle'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj
instea
d.
enabling adb
adb_open
/ # Compat-wireless backport release: compat-wireless-2011-06-28-2-FA
Backport based on linux-next.git next-20110707
cfg80211: Calling CRDA to update world regulatory domain
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
usbcore: registered new interface driver ath9k_htc
usbcore: registered new interface driver rt73usb
usbcore: registered new interface driver rt2800usb

rtw driver version=v3.0.1590.20110511
usbcore: registered new interface driver rtl8192cu
usbcore: registered new interface driver zd1211rw
warning: `zygote' uses 32-bit capabilities (legacy support in use)
s3c-rtc s3c64xx-rtc: rtc only supports 100 years
alarm_set_rtc: Failed to set RTC, time will be lost on reboot
request_suspend_state: wakeup (3->0) at 45771647024 (1970-01-02
00:00:11.0877378
50 UTC)
init: untracked pid 1133 exited
init: untracked pid 1126 exited
------------[ cut here ]------------
WARNING: at kernel/mutex-debug.c:78 debug_mutex_unlock+0xac/0x118()
Modules linked in: zd1211rw rtl8192cu rt2800usb rt2800lib rt73usb rt2x00usb
rt2x
00lib ath9k_htc ath9k_common mac80211 ath9k_hw ath libertas_sdio libertas
cfg802
11 compat
[<c016a9a4>] (unwind_backtrace+0x0/0xe4) from [<c017f51c>]
(warn_slowpath_common
+0x4c/0x64)
[<c017f51c>] (warn_slowpath_common+0x4c/0x64) from [<c017f54c>]
(warn_slowpath_n
ull+0x18/0x1c)
[<c017f54c>] (warn_slowpath_null+0x18/0x1c) from [<c01a596c>]
(debug_mutex_unloc
k+0xac/0x118)
[<c01a596c>] (debug_mutex_unlock+0xac/0x118) from [<c050c530>]
(__mutex_unlock_s
lowpath+0xb4/0x110)
[<c050c530>] (__mutex_unlock_slowpath+0xb4/0x110) from [<c0422af0>]
(s3c_g3d_ioc
tl+0x158/0x270)
[<c0422af0>] (s3c_g3d_ioctl+0x158/0x270) from [<c0422c58>]
(s3c_g3d_release+0x50
/0x64)
[<c0422c58>] (s3c_g3d_release+0x50/0x64) from [<c01e796c>]
(fput+0x114/0x210)
[<c01e796c>] (fput+0x114/0x210) from [<c01e4b2c>] (filp_close+0x58/0x64)
[<c01e4b2c>] (filp_close+0x58/0x64) from [<c018262c>]
(put_files_struct+0xb8/0x1
60)
[<c018262c>] (put_files_struct+0xb8/0x160) from [<c0182910>]
(do_exit+0x194/0x66
4)
[<c0182910>] (do_exit+0x194/0x664) from [<c018310c>]
(do_group_exit+0xb0/0xe4)
[<c018310c>] (do_group_exit+0xb0/0xe4) from [<c018dd20>]
(get_signal_to_deliver+
0x3c4/0x420)
[<c018dd20>] (get_signal_to_deliver+0x3c4/0x420) from [<c01684ec>]
(do_signal+0x
68/0x65c)
[<c01684ec>] (do_signal+0x68/0x65c) from [<c01690bc>]
(do_notify_resume+0x18/0x4
8)
[<c01690bc>] (do_notify_resume+0x18/0x48) from [<c0165eb8>]
(work_pending+0x24/0
x28)
---[ end trace 7433969f0698b415 ]---
request_suspend_state: wakeup (0->0) at 67152794365 (1970-01-02
00:00:32.4688848
60 UTC)
init: untracked pid 1264 exited
init: untracked pid 1263 exited
request_suspend_state: wakeup (0->0) at 88737002587 (1970-01-02
00:00:54.0530935
63 UTC)
init: untracked pid 1311 exited
init: untracked pid 1312 exited

/ #
--------------------


I've tried several bootloaders, like superboot-20110727.bin and
u-boot_nand-ram256.bin.

I'm not posting separate errors, because as most of the OSs fail, with
default parameters, I assume I must be doing something wrong in general.
Does anyone have an idea of what it could be?


This is my FriendlyARM.ini

--------------------
#This line cannot be removed. by FriendlyARM(www.arm9.net)

LCD-Mode = Yes
LCD-Type = N43

CheckOneButton=No
Action=run
OS=Android

VerifyNandWrite=Yes

StatusType = Beeper| LED

#################### Linux #####################
Linux-BootLoader = Linux/superboot-20110727.bin
Linux-Kernel = Linux/zImage_n43
Linux-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs
init=/linuxrc console=ttySAC0,115200
Linux-RootFs-InstallImage = Linux/rootfs_qtopia_qt4-slc.ubi
Linux-RootFs-RunImage = Linux/rootfs_qtopia_qt4.ext3

################### Android ####################
#Android-BootLoader = Android/superboot-20110727.bin
#Android-BootLoader = Linux/u-boot_nand-ram256.bin
Android-BootLoader = Linux/u-boot_sd-ram128.bin
Android-Kernel = Android/azImage_n43
Android-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs
 init=/linuxrc console=ttySAC0,115200 androidboot.console=s3c2410_serial0
Android-RootFs-InstallImage = Android/rootfs_android-slc.ubi
Android-RootFs-RunImage = Android/rootfs_android.ext3

################### WindowsCE6 #################
WindowsCE6-Bootloader= superboot-20110727.bin
#WindowsCE6-Bootloader= WindowsCE6\NBOOT_N43-RAM256.nb0
WindowsCE6-BootLogo = WindowsCE6\bootlogo.bmp
WindowsCE6-InstallImage = WindowsCE6\NK_n43-i.bin
WindowsCE6-RunImage = WindowsCE6\NK_n43-i.bin

#################### Ubuntu #####################
#Ubuntu-BootLoader = superboot-20110727.bin
#Ubuntu-BootLoader = Ubuntu/u-boot_nand-ram128.bin
Ubuntu-BootLoader = Ubuntu/u-boot_sd-ram128.bin
Ubuntu-Kernel = Ubuntu/uzImage_n43
Ubuntu-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs 
init=/linuxrc console=ttySAC0,115200
Ubuntu-RootFs-InstallImage = Ubuntu/rootfs_ubuntu-slc.ubi
Ubuntu-RootFs-RunImage = Ubuntu/rootfs_ubuntu.ext3

############### UserBin #################
#UserBin-Image=WindowsCE6/NK_N43-i.nb0
#UserBin-Image=BasicOS/demo.bin
UserBin-Image=Games/SuperMarioWar/zImage_n43
#UserBin-Image=Games/SuperMarioWar/u-boot_nand-ram256.bin
UserBin-StartAddress=50100000
--------------------

hitsch
Hi 
I also got a Tiny6410 with a 7" display and have the same problem as you. I
also downloaded the Tiny6410B20111022.iso from the friendlyarm ftp server->
same thing: installation well but running failed.
I still have no solution...

TheRegnirps
Is the supervivi in the images directory the same as in your script file?
According to your listing above, it must be superboot-20110727.bin

When you run SD-Flasher, do you "Fuse" version superboot-20110727.bin ?

TheRegnirps
Do you have 2G NAND? It is MLC and you must use the images that have MLC
not SLC suffix. Make sure they are on the Sd card and edit the .ini file.

hitsch
Hi 
I succeed now with booting from the 2GB Nand MLC2, which is on the latest
Tiny6410 board.

I put the superboot 20110722 on the SD card to start the download menu
(option CheckOneButton=yes) and than I manually download the files via USB
on a Windows XP and the DNW tool. The file which worked was the
u-boot_nand-ram256.bin (which I created myself), superboot-xy.bin didn't
work (versions tested 20110722, 20110826, 20111102).
Now I can run linux from the Nand and can go on further...