Hi all, im running out of ideas about getting mini2440 work with debian. I flashed uboot on NAND. I have a SD card with 2 partition (vfat for boot, and ext3 for rootfs) I downloaded lots of kernels: -The one from FriendlyARM: http://www.friendlyarm.net/dl.php?file=linux-2.6.32.2-mini2440_20100609.tgz -This one: git://repo.or.cz/openembedded/mini2440.git -And the one from kernel.org and patching it with arm patch. I use this for crosscompile: http://code.google.com/p/mini6410-debian/downloads/detail?name=arm-linux...= I use debootstrap for making the grip: sudo debootstrap --arch=armel --foreign lenny grip/ http://www.emdebian.org/grip/ I configure uboot this way: setenv bootcmd mmcinit \; fatload mmc 0:1 0x31000000 uImage \; bootm 0x31000000 setenv bootargs console=ttySAC0,115200 mini2440=1tb rootfstype=ext3 root=/dev/mmcblk0p2 rw rootwait After about 30-40 kernel recompiles, i dont find a solution (the problem at end of post). Dont matter if i compile with mini2440_defconfig , or if i use one of config_mini2440_* (a70,l80,n35,t35,vga..), o just use menuconfig and do my selection. I do make clean, make, make modules, make modules_install, make uImage .... in that order, and also tried ones i saw in a forum: make -j4 , make -j4 modules. All of those options using cross compiler specifiyng arm arch. When i run in NAND, it works fine until mounting rootfs. Its not a failure of sd partitions, or bad make (no errors), uImage loads OK. The problem is when it mounts rootfs, here is a sample of the log: ....... ....... ## Booting kernel from Legacy Image at 31000000 ... Image Name: Linux-2.6.32-rc8 Created: 2011-02-25 11:23:11 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2034804 Bytes = 1.9 MB Load Address: 30008000 Entry Point: 30008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux............................................................. .............................................. ......... ........ mmc0: new SD card at address 1234 mmcblk0: mmc0:1234 SA02G 1.83 GiB mmcblk0: p1 p2 kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on mmcblk0p2, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with writeback data mode. VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 128K Unable to handle kernel paging request at virtual address 00100104 pgd = c39c0000 [00100104] *pgd=3397f031, *pte=00000000, *ppte=00000000 Internal error: Oops: 817 [#1] last sysfs file: Modules linked in: CPU: 0 Not tainted (2.6.32-rc8 #1) PC is at __rmqueue+0x80/0x310 LR is at get_page_from_freelist+0x128/0x45c pc : [<c0069b0c>] lr : [<c0069ec4>] psr: 20000093 sp : c3823b50 ip : c04222d8 fp : 000201da r10: 00100100 r9 : 00000000 r8 : 00200200 r7 : c03e8b94 r6 : 00000010 r5 : 00000002 r4 : c04222c0 r3 : c03e8bf8 r2 : c03e8bc0 r1 : 00000001 r0 : 00000010 Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user Control: c000717f Table: 339c0000 DAC: 00000015 Process init (pid: 1, stack limit = 0xc3822270) Stack: (0xc3823b50 to 0xc3824000) 3b40: c03e8b94 00000000 00000002 c03e8b94 3b60: 00000003 c03e8bc4 00000000 00000000 c3822000 c03e8bc4 000201da c0069ec4 3b80: 00000041 c3979880 00000000 ............ ............ (ALL LOG ATTACHED) I tried all options, using vfat for boot, or using ext2. I tried lots of kernel configurations, but i dont get where is the problem... any help would be apreciated!!!!! thanks in advance
Mini2440 debian rootfs failure
http://mini2440.netyxia.net/viewtopic.php?f=9&t=13 give this toolchain a try, it worked for me, using friendlyarm kernel and emdebian grip rootfs I'm using ext4 for rootfs and ext2 for kernel partition.
Hi Cristian, can you provide me the .config file you used to compile the kernel? maybe mini2440_defconfig? thanks!
Hi all, i finally solved it using another toolchain (not yours cristian, however you put me on the way ;) ). I did it with this one: http://billforums.station51.net/viewtopic.php?f=4&t=9 Now, i having a problem with network (makes mini2440 board reset). But i created a new Post with updated subject, for keeping ordered info in the forum. Thanks all!