Latest posts of: superpat

Show Posts
Pages: 1 ... 3 4 [5] 6 7 ... 10

61	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 12, 2010, 05:32:36 AM
@mgillespie Hi, I changed the line back in uboot-nand-custom.txt to orion_nand Then I ran the runme again, The plug new kernel took an exception. I tried the complete install twice. Again I have attached the putty.log as a file as it is long!

62	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 12, 2010, 04:33:24 AM
@mgillespie I thought I should give it a try. Unfortunately it finishes up with a Bad Magic Number Here is my Installer x86 m/c output Quote debsilch:/home/patrick/sheevaplug-installer-v1.01# php runme.php nand ** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f) Preparing environment variables file ... reading uboot/uboot-env/uboot-dflt.txt uboot/uboot-env/fw_setenv baudrate 115200 CRC read error on uboot-env.bin: Success uboot/uboot-env/fw_setenv loads_echo 0 uboot/uboot-env/fw_setenv ipaddr 10.4.50.165 uboot/uboot-env/fw_setenv serverip 10.4.50.5 uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/ uboot/uboot-env/fw_setenv netmask 255.255.255.0 uboot/uboot-env/fw_setenv stdin serial uboot/uboot-env/fw_setenv stdout serial uboot/uboot-env/fw_setenv stderr serial uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\) uboot/uboot-env/fw_setenv mainlineLinux no uboot/uboot-env/fw_setenv CASset min uboot/uboot-env/fw_setenv enaMonExt no uboot/uboot-env/fw_setenv enaCpuStream no uboot/uboot-env/fw_setenv enaWrAllo no uboot/uboot-env/fw_setenv pexMode RC uboot/uboot-env/fw_setenv disL2Cache no uboot/uboot-env/fw_setenv setL2CacheWT yes uboot/uboot-env/fw_setenv disL2Prefetch yes uboot/uboot-env/fw_setenv enaICPref yes uboot/uboot-env/fw_setenv enaDCPref yes uboot/uboot-env/fw_setenv sata_dma_mode yes uboot/uboot-env/fw_setenv MALLOC_len 1 uboot/uboot-env/fw_setenv ethprime egiga0 uboot/uboot-env/fw_setenv netbsd_en no uboot/uboot-env/fw_setenv vxworks_en no uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none uboot/uboot-env/fw_setenv image_name uImage uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\; bootm 0x2000000\; uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\; uboot/uboot-env/fw_setenv bootdelay 3 uboot/uboot-env/fw_setenv disaMvPnp no uboot/uboot-env/fw_setenv ethaddr 00:50:43:4e:2a:14 uboot/uboot-env/fw_setenv ethmtu 1500 uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500 uboot/uboot-env/fw_setenv usb0Mode host uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81 uboot/uboot-env/fw_setenv nandEcc 1bit uboot/uboot-env/fw_setenv netretry no uboot/uboot-env/fw_setenv rcvrip 169.254.100.100 uboot/uboot-env/fw_setenv loadaddr 0x02000000 uboot/uboot-env/fw_setenv autoload no uboot/uboot-env/fw_setenv enaAutoRecovery yes uboot/uboot-env/fw_setenv ethact egiga0 reading uboot/uboot-env/uboot-nand-custom.txt uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs rootdelay=5 uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_mtd:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\) uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:c1:e6 uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000 uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200 uboot/uboot-env/fw_setenv bootcmd run recover1 uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000 uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000 uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd Burning uboot and environment variables ... This will take few minutes ... Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release $URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS 2000 kHz jtag_nsrst_delay: 200 jtag_ntrst_delay: 200 dcc downloads are enabled Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2) Info : JTAG Tap/device matched target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled 0 0 1 0: 00052078 NAND flash device 'NAND 512MiB 3,3V 8-bit' found successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit' wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 18.110443s target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled 0 0 1 0: 00052078 NAND flash device 'NAND 512MiB 3,3V 8-bit' found successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit' wrote file uboot.bin to NAND flash 0 up to offset 0x00074000 in 66.042610s ** U-boot should be up and running now. Open your console ... I have attached the putty.log as a file (its a bit long to insert in line!) A small quibble, I seem to have a hybrid Sheevaplug. It is a V1.3, but it still has the V1.0 ftdi addresses, so I did not have to edit the config as in the readme. I tried it 3 times and got the same result each time. cheers Patrick

63	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 12, 2010, 03:47:04 AM
Hi, I have downloaded it, but I want to sort out my problem with using a Rfxcom receiver, (see post re only one ttyusb), before I blow my "standard" set-up away Thank you for your efforts in creating the new installer. cheers Patrick

64	General Category / General Discussion / Re: Only one USB serial is showing up!	on: January 11, 2010, 08:27:41 AM
@myself Just found this:- Quote Re: USB to Serial Cable -- no data from ttyUSB0 Quote: Originally Posted by ramjet_1953 View Post I don't know why, but the Ubuntu developers see fit to install brltty as a default. This is a package that allows blind people to use a Braille reader. Unfortunately, it interferes with serial communications for other uses. Go into Synaptic package manager and ensure that these 3 packages are NOT installed: 1. brltty 2. brltty-flite 3. brltty-x11 Hopefully, after they are removed your USB to Serial will come to life. Regards, Roger Thanks!! This fixed my problem with my serial connection also!! Just going to see if this is the problem cheers P EDIT No No britty or derivatives installed! onward!

65	General Category / General Discussion / Re: Only one USB serial is showing up!	on: January 11, 2010, 04:38:21 AM
Hi, I too am puzzled about serial USB enumeration. I have just got around to trying a RFXCOM 433Mhz receiver for X10 and various sensors. When I plugged it into the Sheevaplug USB type A socket, the kernel ( bog standard from Installer v1.0 V 2.6.30.2 ) showed this:- Quote usb 1-1: new full speed USB device using orion-ehci and address 3 usb 1-1: configuration #1 chosen from 1 choice ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected usb 1-1: Detected FT232RL usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 root@ubuntu:/var/log# Now the funny thing is that I am already using /dev/ttyUSB0 to connect to the Sheevaplug with PUTTY, looking at /dev Quote root@ubuntu:/var/log# dir /dev block null ram4 tty24 tty53 ttype bus port ram5 tty25 tty54 ttypf char ppp ram6 tty26 tty55 ubi0 console psaux ram7 tty27 tty56 ubi0_0 core ptmx ram8 tty28 tty57 ubi_ctrl cpu_dma_latency pts ram9 tty29 tty58 urandom fd ptyp0 random tty3 tty59 usbdev1.1 full ptyp1 rtc0 tty30 tty6 usbdev1.1_ep00 initctl ptyp2 serial tty31 tty60 usbdev1.1_ep81 input ptyp3 shm tty32 tty61 usbdev1.3 kmem ptyp4 sndstat tty33 tty62 usbdev1.3_ep00 kmsg ptyp5 stderr tty34 tty63 usbdev1.3_ep02 log ptyp6 stdin tty35 tty7 usbdev1.3_ep81 loop0 ptyp7 stdout tty36 tty8 vcs loop1 ptyp8 tty tty37 tty9 vcs2 loop2 ptyp9 tty0 tty38 ttyS0 vcs3 loop3 ptypa tty1 tty39 ttyS1 vcs4 loop4 ptypb tty10 tty4 ttyUSB0 vcs5 loop5 ptypc tty11 tty40 ttyp0 vcs6 loop6 ptypd tty12 tty41 ttyp1 vcsa loop7 ptype tty13 tty42 ttyp2 vcsa2 mapper ptypf tty14 tty43 ttyp3 vcsa3 mem ram0 tty15 tty44 ttyp4 vcsa4 mtd0 ram1 tty16 tty45 ttyp5 vcsa5 mtd0ro ram10 tty17 tty46 ttyp6 vcsa6 mtd1 ram11 tty18 tty47 ttyp7 xconsole mtd1ro ram12 tty19 tty48 ttyp8 zero mtdblock0 ram13 tty2 tty49 ttyp9 mtdblock1 ram14 tty20 tty5 ttypa net ram15 tty21 tty50 ttypb network_latency ram2 tty22 tty51 ttypc network_throughput ram3 tty23 tty52 ttypd root@ubuntu:/var/log# You can see that there is only one ttyUSB. So my question is how do I set up udev rules ( I suppose ) to enumerate a ttyUSB for the RFXCOM receiver. I tried another experiment, I disconnected my min usb cable and the PUTTY terminal, and used SSH to look at what was going on when I plugged my RFXCOM receiver in to the type A port. What happened was that the kernel "found " the ftdi device, and connected it to ttyUSB0 again!. However although the receiver was supposed to be pumping out loads of ascii text, there was nothing from /dev/ttyUSB0. When I reconnected the PUTTY cable to the min slot and used ttyUSB0, it picked up where it left off, connected as a Linux console! So I assume that the data structure for ttyUSB0 originally set up on first connection of the PUTTY cable to the "jtag" port has persisted through the disconnection Advice gratefully received cheers Patrick

66	General Category / General Discussion / Re: Competition to the plug?	on: January 07, 2010, 03:07:50 AM
@mgillespie Not a computer contender but one of the biggest example of marketing winning over specifications Two words for you:- BETAMAX VHS cheers Patrick

67	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: January 06, 2010, 09:25:53 AM
@pingtoo No Problemo! I mounted the card on /mnt/plug Therefore I take a directory of boot NOT /boot (that would be my x86 system disk!) Quote debsilch:/mnt/plug# debsilch:/mnt/plug# dir bin etc lost+found opt root selinux tmp var boot home media PackageList.txt rootfs.tar.gz srv uImage dev lib mnt proc sbin sys usr debsilch:/mnt/plug# debsilch:/mnt/plug# debsilch:/mnt/plug# stat boot File: `boot' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 801h/2049d Inode: 393217 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-06 12:38:20.000000000 +0000 Modify: 2010-01-01 15:51:20.000000000 +0000 Change: 2010-01-01 15:51:20.000000000 +0000 debsilch:/mnt/plug# debsilch:/mnt/plug# debsilch:/mnt/plug# debsilch:/mnt/plug# cd boot debsilch:/mnt/plug/boot# stat . File: `.' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 801h/2049d Inode: 393217 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-06 12:38:20.000000000 +0000 Modify: 2010-01-01 15:51:20.000000000 +0000 Change: 2010-01-01 15:51:20.000000000 +0000 debsilch:/mnt/plug/boot# and again with ls -i Quote debsilch:/mnt/plug# ls -i 163841 bin 11 lost+found 49153 root 466945 tmp 393217 boot 311297 media 12 rootfs.tar.gz 14 uImage 172033 dev 16385 mnt 32769 sbin 155649 usr 409601 etc 131073 opt 98305 selinux 319489 var 344065 home 13 PackageList.txt 335873 srv 294913 lib 81921 proc 303105 sys debsilch:/mnt/plug# cd boot debsilch:/mnt/plug/boot# ls -i 393218 uImage debsilch:/mnt/plug/boot# cheers P

68	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: January 06, 2010, 03:32:29 AM
@pingtoo YOU ARE CORRECT! I copied the file uImage into /opt, renaming it uImageb for clarity. I then installed the card in the plug, loaded up your debug u-boot and did a ext2ls of /opt Quote Marvell>> ext2ls mmc 0:1 /opt <2, 0, 204> revision_level = 0x1, inode_size = 0x100 ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> Iterate dir opt ext2fs_read_block 000003e3 <7960, 0, 8> ext2fs_read_block 000003e3 <7960, 8, 1> iterate >.< ext2fs_read_block 000003e3 <7960, 12, 8> ext2fs_read_block 000003e3 <7960, 20, 2> iterate >..< ext2fs_read_block 000003e3 <7960, 24, 8> ext2fs_read_block 000003e3 <7960, 32, 10> iterate >lost+found< ext2fs_read_block 000003e3 <7960, 44, 8> ext2fs_read_block 000003e3 <7960, 52, 13> iterate >rootfs.tar.gz< ext2fs_read_block 000003e3 <7960, 68, 8> ext2fs_read_block 000003e3 <7960, 76, 15> iterate >PackageList.txt< ext2fs_read_block 000003e3 <7960, 92, 8> ext2fs_read_block 000003e3 <7960, 100, 3> iterate >bin< ext2fs_read_block 000003e3 <7960, 104, 8> ext2fs_read_block 000003e3 <7960, 112, 4> iterate >boot< ext2fs_read_block 000003e3 <7960, 116, 8> ext2fs_read_block 000003e3 <7960, 124, 3> iterate >dev< ext2fs_read_block 000003e3 <7960, 128, 8> ext2fs_read_block 000003e3 <7960, 136, 3> iterate >etc< ext2fs_read_block 000003e3 <7960, 140, 8> ext2fs_read_block 000003e3 <7960, 148, 4> iterate >home< ext2fs_read_block 000003e3 <7960, 152, 8> ext2fs_read_block 000003e3 <7960, 160, 3> iterate >lib< ext2fs_read_block 000003e3 <7960, 164, 8> ext2fs_read_block 000003e3 <7960, 172, 5> iterate >media< ext2fs_read_block 000003e3 <7960, 180, 8> ext2fs_read_block 000003e3 <7960, 188, 3> iterate >mnt< ext2fs_read_block 000003e3 <7960, 192, 8> ext2fs_read_block 000003e3 <7960, 200, 3> iterate >opt< ext2fs read inode 131072 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 0 <4194320, 0, 128> ext2fs_read_block 00081000 <4227072, 0, 8> ext2fs_read_block 00081000 <4227072, 8, 1> iterate >.< ext2fs read inode 131072 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 0 <4194320, 0, 128> <DIR> 4096 . ext2fs_read_block 00081000 <4227072, 12, 8> ext2fs_read_block 00081000 <4227072, 20, 2> iterate >..< ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> <DIR> 4096 .. ext2fs_read_block 00081000 <4227072, 24, 8> ext2fs_read_block 00081000 <4227072, 32, 7> iterate >uImageb< ext2fs read inode 131073 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 1 <4194320, 256, 128> 2309636 uImageb I then did a ext2ls mmc 0:1 /boot Quote Marvell>> ext2ls mmc 0:1 /boot <2, 0, 204> revision_level = 0x1, inode_size = 0x100 ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> Iterate dir boot ext2fs_read_block 000003e3 <7960, 0, 8> ext2fs_read_block 000003e3 <7960, 8, 1> iterate >.< ext2fs_read_block 000003e3 <7960, 12, 8> ext2fs_read_block 000003e3 <7960, 20, 2> iterate >..< ext2fs_read_block 000003e3 <7960, 24, 8> ext2fs_read_block 000003e3 <7960, 32, 10> iterate >lost+found< ext2fs_read_block 000003e3 <7960, 44, 8> ext2fs_read_block 000003e3 <7960, 52, 13> iterate >rootfs.tar.gz< ext2fs_read_block 000003e3 <7960, 68, 8> ext2fs_read_block 000003e3 <7960, 76, 15> iterate >PackageList.txt< ext2fs_read_block 000003e3 <7960, 92, 8> ext2fs_read_block 000003e3 <7960, 100, 3> iterate >bin< ext2fs_read_block 000003e3 <7960, 104, 8> ext2fs_read_block 000003e3 <7960, 112, 4> iterate >boot< ext2fs read inode 393216 ext2fs read blockgroup <11, 0, 32> ext2fs read inode blkno 0 blkoff 0 <12582928, 0, 128> ext2fs_read_block 00081000 <4227072, 0, 8> ext2fs_read_block 00081000 <4227072, 8, 1> iterate >.< ext2fs read inode 131072 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 0 <4194320, 0, 128> <DIR> 4096 . ext2fs_read_block 00081000 <4227072, 12, 8> ext2fs_read_block 00081000 <4227072, 20, 2> iterate >..< ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> <DIR> 4096 .. ext2fs_read_block 00081000 <4227072, 24, 8> ext2fs_read_block 00081000 <4227072, 32, 7> iterate >uImageb< ext2fs read inode 131073 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 1 <4194320, 256, 128> 2309636 uImageb Marvell>> THIS ALSO RETURNS THE FILE UIMAGEB which is ONLY in /opt !!! Somehow the u-boot.bin is obtaining the contents of /opt when asking for /boot. My brain hurts trying to follow the inode links! BTW trying the card on the x86 box, show NO problems i.e. uImage in /boot and uImageb in /opt. cheers Patrick EDIT>>>>> Googling around, there is a lot of chatter about u-boot having problems with inode length of 256 instead of 128 bytes. I ran tune2fs on my card and got this result:- Quote debsilch:/home/patrick# tune2fs -l /dev/sda1 tune2fs 1.41.3 (12-Oct-2008) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 43c2340e-e052-486d-8aeb-fd67117f89f8 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: ext_attr resize_inode dir_index filetype sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 491520 Block count: 1964757 Reserved block count: 98237 Free blocks: 1879310 Free inodes: 484080 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 479 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Fri Jan 1 15:23:57 2010 Last mount time: Wed Jan 6 12:37:58 2010 Last write time: Wed Jan 6 12:38:27 2010 Mount count: 4 Maximum mount count: 32 Last checked: Wed Jan 6 10:08:12 2010 Check interval: 15552000 (6 months) Next check after: Mon Jul 5 11:08:12 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Default directory hash: half_md4 Directory Hash Seed: 9baf17bb-ab2c-4569-ac5a-06abfad052b4 debsilch:/home/patrick# as you can see inode size is 256 bytes.. I don't see the same sort of error in the many other problems posted on the web about u-boot and inode size, but it is worth keeping in mind Patrick

69	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: January 06, 2010, 02:47:28 AM
@pingtoo Hi, Some interesting stuff! I did some reading about inodes, ls and stat, trying to remember what I learnt many years ago on my DEC Ultrix system manglers course! I took my 8GB Kingston card out of the Sheevaplug and mounted it in one of my x86 Linux boxes (Debian distrib) I then did ls -i and stat of the directories in dispute Here are the results:- Quote debsilch:/mnt/plug# debsilch:/mnt/plug# ls -i 163841 bin 11 lost+found 49153 root 466945 tmp 393217 boot 311297 media 12 rootfs.tar.gz 14 uImage 172033 dev 16385 mnt 32769 sbin 155649 usr 409601 etc 131073 opt 98305 selinux 319489 var 344065 home 13 PackageList.txt 335873 srv 294913 lib 81921 proc 303105 sys debsilch:/mnt/plug# ls -i boot 393218 uImage debsilch:/mnt/plug# debsilch:/mnt/plug# ls -i opt debsilch:/mnt/plug# debsilch:/mnt/plug# ls -i opt debsilch:/mnt/plug# debsilch:/mnt/plug# debsilch:/mnt/plug# debsilch:/mnt/plug# stat boot File: `boot' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 801h/2049d Inode: 393217 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-06 08:54:58.000000000 +0000 Modify: 2010-01-01 15:51:20.000000000 +0000 Change: 2010-01-01 15:51:20.000000000 +0000 debsilch:/mnt/plug# stat boot/uImage File: `boot/uImage' Size: 2309636 Blocks: 4520 IO Block: 4096 regular file Device: 801h/2049d Inode: 393218 Links: 1 Access: (0777/-rwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-01 16:32:44.000000000 +0000 Modify: 2010-01-01 15:51:20.000000000 +0000 Change: 2010-01-01 16:07:59.000000000 +0000 debsilch:/mnt/plug# stat opt File: `opt' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 801h/2049d Inode: 131073 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-06 08:55:59.000000000 +0000 Modify: 2009-12-03 12:33:56.000000000 +0000 Change: 2010-01-01 15:26:27.000000000 +0000 debsilch:/mnt/plug# You will see that the inode for the boot directory is given by stat on an x86 m/c is boot = 393217 boot/uImage = 393298 Also ls -i is exactly the same/ For the empty opt directory opt=131073 Now looking at the results given by your debug u-boot, the inode for the boot directory is given as boot = 393216 and for the opt directory opt=131072 These are showing as ONE less in each case, than the value obtained on the x86 system. I suppose it depends on whether the count starts at zero or one on each system! However, what appears to be written on my Kingston card is that a good file system, with NO cross linked or dual inodes. You can see that (on a x86 system) the inodes are as they should be. I would suggest my RFS on the sdhc card is not corrupt, (at least not in an obvious way). I am a bit unclear of the methodology of the next test you wish me to do. Please advise steps you wish me to try. YOU WERE CORRECT! SEE NEXT REPLY FOR MORE TEST RESULTS. thanks again regards Patrick

70	Hardware and U-Boot firmware / U-Boot stuff / TESTING using pingtoo debug enabled uboot	on: January 05, 2010, 03:19:36 AM
Hi pingtoo. Thanks for all your work on this problem. Here are the results of testing using your debug enabled u-boot. I have annotated the putty printout with notes of points of interest! Looking at the preview, I see the notes have wrapped and are below the line where I put them, but you should be able to work out what I was trying to point out! Firstly for comparison reference here is a directory of my SDHC card root file system taken on my Linux box You will see there is a uImage in /boot. ( There is a second copy in / , (this enables me to load uImage) Quote debsilch:/media/disk# ls -la total 49196 drwxr-xr-x 21 root root 4096 2010-01-01 16:32 . drwxr-xr-x 4 root root 4096 2010-01-05 09:47 .. drwxr-xr-x 2 root root 4096 2009-12-03 12:37 bin drwxr-xr-x 2 root root 4096 2010-01-01 15:51 boot drwxr-xr-x 4 root root 4096 2010-01-01 16:36 dev drwxr-xr-x 42 root root 4096 2010-01-01 16:36 etc drwxr-xr-x 2 root root 4096 2009-08-31 04:45 home drwxr-xr-x 11 root root 4096 2009-12-03 12:37 lib drwx------ 2 root root 16384 2010-01-01 15:24 lost+found drwxr-xr-x 2 root root 4096 2009-12-03 12:33 media drwxr-xr-x 2 root root 4096 2009-08-31 04:45 mnt drwxr-xr-x 2 root root 4096 2009-12-03 12:33 opt -rw-r--r-- 1 root root 13840 2009-12-03 12:37 PackageList.txt drwxr-xr-x 2 root root 4096 2009-08-31 04:45 proc drwxr-xr-x 2 root root 4096 2009-12-03 12:33 root -rw-r--r-- 1 root root 47891458 2010-01-01 15:26 rootfs.tar.gz drwxr-xr-x 2 root root 4096 2009-12-03 12:37 sbin drwxr-xr-x 2 root root 4096 2008-09-16 08:48 selinux drwxr-xr-x 2 root root 4096 2009-12-03 12:33 srv drwxr-xr-x 2 root root 4096 2008-08-12 15:26 sys drwxrwxrwt 4 root root 4096 2010-01-01 16:36 tmp -rwxr-xr-x 1 root root 2309636 2010-01-01 16:32 uImage drwxr-xr-x 11 root root 4096 2009-12-03 12:36 usr drwxr-xr-x 13 root root 4096 2009-12-03 12:33 var debsilch:/media/disk# cd boot debsilch:/media/disk/boot# ls -la total 2268 drwxr-xr-x 2 root root 4096 2010-01-01 15:51 . drwxr-xr-x 21 root root 4096 2010-01-01 16:32 .. -rwxrwxrwx 1 root root 2309636 2010-01-01 15:51 uImage debsilch:/media/disk/boot# Here is the output from putty for your debug U-boot. Quote Hit any key to stop autoboot: 3 0 Marvell>> usb start] (Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Marvell>> fatload usb 0:1 0x1600000 /ext2-debug-u-boot.bin reading /ext2-debug-u-boot.bin .............................................. 474076 bytes read Marvell>> go 0x1600000 ## Starting application at 0x01600000 ... __ __ _ _ \| \/ \| __ _ _ ____ _____\| \| \| \| \|\/\| \|/ _` \| '__\ \ / / _ \ \| \| \| \| \| \| (_\| \| \| \ V / __/ \| \| \|_\| \|_\|\__,_\|_\| \_/ \___\|_\|_\| _ _ ____ _ \| \| \| \| \| __ ) ___ ___ \| \|_ \| \| \| \|___\| _ \ / _ \ / _ \\| __\| \| \|_\| \|___\| \|_) \| (_) \| (_) \| \|_ \___/ \|____/ \___/ \___/ \__\| MARVELL BOARD: SHEEVA PLUG LE U-Boot 1.1.4 (Jan 4 2010 - 21:45:00) Marvell version: 3.4.27 U-Boot code: 01600000 -> 0167FFF0 BSS: -> 016CFEE0 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM CS[1] base 0x10000000 size 256MB DRAM Total size 512MB 16bit width Addresses 24M - 0M are saved for the U-Boot usage. Mem malloc Initialization (24M - 23M): Done NAND:512 MB Flash: 0 kB CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME] Hit any key to stop autoboot: 3 0 Marvell>> version U-Boot 1.1.4 (Jan 4 2010 - 21:45:00) Marvell version: 3.4.27 - pingtoo ext2 testing.01 << YOUR DEBUG VERSION Marvell>> mmcinit SDHC found. Card desciption is: Manufacturer: 0x27, OEM "PH" Product name: "SD8GB", revision 2.0 << KINGSTON 8GB TYPE 6 SDHC CARD Serial number: 2953847158 Manufacturing date: 8/2009 CRC: 0x00, b0 = 0 Marvell>> ext2ls mmc 0 <<< SAME COMMAND A YOU USED IN YOUR EXAMPLE <2, 0, 204> revision_level = 0x1, inode_size = 0x100 ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> ext2fs_read_block 000003e3 <7960, 0, 8> ext2fs_read_block 000003e3 <7960, 8, 1> iterate >.< ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> <DIR> 4096 . ext2fs_read_block 000003e3 <7960, 12, 8> ext2fs_read_block 000003e3 <7960, 20, 2> iterate >..< ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> <DIR> 4096 .. ext2fs_read_block 000003e3 <7960, 24, 8> ext2fs_read_block 000003e3 <7960, 32, 10> iterate >lost+found< ext2fs read inode 10 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 10 <3869, 0, 128> <DIR> 16384 lost+found ext2fs_read_block 000003e3 <7960, 44, 8> ext2fs_read_block 000003e3 <7960, 52, 13> iterate >rootfs.tar.gz< ext2fs read inode 11 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 11 <3869, 256, 128> 47891458 rootfs.tar.gz ext2fs_read_block 000003e3 <7960, 68, 8> ext2fs_read_block 000003e3 <7960, 76, 15> iterate >PackageList.txt< ext2fs read inode 12 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 12 <3870, 0, 128> 13840 PackageList.txt ext2fs_read_block 000003e3 <7960, 92, 8> ext2fs_read_block 000003e3 <7960, 100, 3> iterate >bin< ext2fs read inode 163840 ext2fs read blockgroup <9, 128, 32> ext2fs read inode blkno 0 blkoff 0 <5242896, 0, 128> <DIR> 4096 bin ext2fs_read_block 000003e3 <7960, 104, 8> ext2fs_read_block 000003e3 <7960, 112, 4> iterate >boot< ext2fs read inode 393216 ext2fs read blockgroup <11, 0, 32> ext2fs read inode blkno 0 blkoff 0 <12582928, 0, 128> <DIR> 4096 boot ext2fs_read_block 000003e3 <7960, 116, 8> ext2fs_read_block 000003e3 <7960, 124, 3> iterate >dev< ext2fs read inode 172032 ext2fs read blockgroup <9, 160, 32> ext2fs read inode blkno 0 blkoff 0 <5505040, 0, 128> <DIR> 4096 dev ext2fs_read_block 000003e3 <7960, 128, 8> ext2fs_read_block 000003e3 <7960, 136, 3> iterate >etc< ext2fs read inode 409600 ext2fs read blockgroup <11, 64, 32> ext2fs read inode blkno 0 blkoff 0 <13107216, 0, 128> <DIR> 0 etc ext2fs_read_block 000003e3 <7960, 140, 8> ext2fs_read_block 000003e3 <7960, 148, 4> iterate >home< ext2fs read inode 344064 ext2fs read blockgroup <10, 320, 32> ext2fs read inode blkno 0 blkoff 0 <11010064, 0, 128> <DIR> 4096 home ext2fs_read_block 000003e3 <7960, 152, 8> ext2fs_read_block 000003e3 <7960, 160, 3> iterate >lib< ext2fs read inode 294912 ext2fs read blockgroup <10, 128, 32> ext2fs read inode blkno 0 blkoff 0 <9437200, 0, 128> <DIR> 4096 lib ext2fs_read_block 000003e3 <7960, 164, 8> ext2fs_read_block 000003e3 <7960, 172, 5> iterate >media< ext2fs read inode 311296 ext2fs read blockgroup <10, 192, 32> ext2fs read inode blkno 0 blkoff 0 <9961488, 0, 128> <DIR> 4096 media ext2fs_read_block 000003e3 <7960, 180, 8> ext2fs_read_block 000003e3 <7960, 188, 3> iterate >mnt< ext2fs read inode 16384 ext2fs read blockgroup <8, 64, 32> ext2fs read inode blkno 0 blkoff 0 <524304, 0, 128> <DIR> 4096 mnt ext2fs_read_block 000003e3 <7960, 192, 8> ext2fs_read_block 000003e3 <7960, 200, 3> iterate >opt< ext2fs read inode 131072 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 0 <4194320, 0, 128> <DIR> 4096 opt ext2fs_read_block 000003e3 <7960, 204, 8> ext2fs_read_block 000003e3 <7960, 212, 4> iterate >proc< ext2fs read inode 81920 ext2fs read blockgroup <8, 320, 32> ext2fs read inode blkno 0 blkoff 0 <2621456, 0, 128> <DIR> 4096 proc ext2fs_read_block 000003e3 <7960, 216, 8> ext2fs_read_block 000003e3 <7960, 224, 4> iterate >root< ext2fs read inode 49152 ext2fs read blockgroup <8, 192, 32> ext2fs read inode blkno 0 blkoff 0 <1572880, 0, 128> <DIR> 4096 root ext2fs_read_block 000003e3 <7960, 228, 8> ext2fs_read_block 000003e3 <7960, 236, 4> iterate >sbin< ext2fs read inode 32768 ext2fs read blockgroup <8, 128, 32> ext2fs read inode blkno 0 blkoff 0 <1048592, 0, 128> <DIR> 4096 sbin ext2fs_read_block 000003e3 <7960, 240, 8> ext2fs_read_block 000003e3 <7960, 248, 7> iterate >selinux< ext2fs read inode 98304 ext2fs read blockgroup <8, 384, 32> ext2fs read inode blkno 0 blkoff 0 <3145744, 0, 128> <DIR> 4096 selinux ext2fs_read_block 000003e3 <7960, 256, 8> ext2fs_read_block 000003e3 <7960, 264, 3> iterate >srv< ext2fs read inode 335872 ext2fs read blockgroup <10, 288, 32> ext2fs read inode blkno 0 blkoff 0 <10747920, 0, 128> <DIR> 0 srv ext2fs_read_block 000003e3 <7960, 268, 8> ext2fs_read_block 000003e3 <7960, 276, 3> iterate >sys< ext2fs read inode 303104 ext2fs read blockgroup <10, 160, 32> ext2fs read inode blkno 0 blkoff 0 <9699344, 0, 128> <DIR> 0 sys ext2fs_read_block 000003e3 <7960, 280, 8> ext2fs_read_block 000003e3 <7960, 288, 3> iterate >tmp< ext2fs read inode 466944 ext2fs read blockgroup <11, 288, 32> ext2fs read inode blkno 0 blkoff 0 <14942224, 0, 128> <DIR> 0 tmp ext2fs_read_block 000003e3 <7960, 292, 8> ext2fs_read_block 000003e3 <7960, 300, 3> iterate >usr< ext2fs read inode 155648 ext2fs read blockgroup <9, 96, 32> ext2fs read inode blkno 0 blkoff 0 <4980752, 0, 128> <DIR> 4096 usr ext2fs_read_block 000003e3 <7960, 304, 8> ext2fs_read_block 000003e3 <7960, 312, 3> iterate >var< ext2fs read inode 319488 ext2fs read blockgroup <10, 224, 32> ext2fs read inode blkno 0 blkoff 0 <10223632, 0, 128> <DIR> 0 var ext2fs_read_block 000003e3 <7960, 316, 8> ext2fs_read_block 000003e3 <7960, 324, 6> iterate >uImage< ext2fs read inode 13 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 13 <3870, 256, 128> 2309636 uImage Marvell>> ext2ls mmc 0:1 /boot << ATTEMPTING TO LIST THE CONTENTS OF /boot <2, 0, 204> revision_level = 0x1, inode_size = 0x100 ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> Iterate dir boot ext2fs_read_block 000003e3 <7960, 0, 8> ext2fs_read_block 000003e3 <7960, 8, 1> iterate >.< ext2fs_read_block 000003e3 <7960, 12, 8> ext2fs_read_block 000003e3 <7960, 20, 2> iterate >..< ext2fs_read_block 000003e3 <7960, 24, 8> ext2fs_read_block 000003e3 <7960, 32, 10> iterate >lost+found< ext2fs_read_block 000003e3 <7960, 44, 8> ext2fs_read_block 000003e3 <7960, 52, 13> iterate >rootfs.tar.gz< ext2fs_read_block 000003e3 <7960, 68, 8> ext2fs_read_block 000003e3 <7960, 76, 15> iterate >PackageList.txt< ext2fs_read_block 000003e3 <7960, 92, 8> ext2fs_read_block 000003e3 <7960, 100, 3> iterate >bin< ext2fs_read_block 000003e3 <7960, 104, 8> ext2fs_read_block 000003e3 <7960, 112, 4> iterate >boot< ext2fs read inode 393216 ext2fs read blockgroup <11, 0, 32> ext2fs read inode blkno 0 blkoff 0 <12582928, 0, 128> ext2fs_read_block 00081000 <4227072, 0, 8> ext2fs_read_block 00081000 <4227072, 8, 1> iterate >.< ext2fs read inode 131072 ext2fs read blockgroup <9, 0, 32> ext2fs read inode blkno 0 blkoff 0 <4194320, 0, 128> <DIR> 4096 . ext2fs_read_block 00081000 <4227072, 12, 8> ext2fs_read_block 00081000 <4227072, 20, 2> iterate >..< ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> <DIR> 4096 .. << FAILURE NO LISTING OF /boot/uImage Marvell>> <INTERRUPT> Marvell>> ext2load mmc 0 0x800000 /boot/uImage <<ATTEMPTING TO LOAD uImage FROM /boot <2, 0, 204> revision_level = 0x1, inode_size = 0x100 ext2fs read inode 1 ext2fs read blockgroup <8, 0, 32> ext2fs read inode blkno 0 blkoff 1 <3864, 256, 128> Iterate dir boot ext2fs_read_block 000003e3 <7960, 0, 8> ext2fs_read_block 000003e3 <7960, 8, 1> iterate >.< ext2fs_read_block 000003e3 <7960, 12, 8> ext2fs_read_block 000003e3 <7960, 20, 2> iterate >..< ext2fs_read_block 000003e3 <7960, 24, 8> ext2fs_read_block 000003e3 <7960, 32, 10> iterate >lost+found< ext2fs_read_block 000003e3 <7960, 44, 8> ext2fs_read_block 000003e3 <7960, 52, 13> iterate >rootfs.tar.gz< ext2fs_read_block 000003e3 <7960, 68, 8> ext2fs_read_block 000003e3 <7960, 76, 15> iterate >PackageList.txt< ext2fs_read_block 000003e3 <7960, 92, 8> ext2fs_read_block 000003e3 <7960, 100, 3> iterate >bin< ext2fs_read_block 000003e3 <7960, 104, 8> ext2fs_read_block 000003e3 <7960, 112, 4> iterate >boot< Iterate dir uImage ext2fs read inode 393216 ext2fs read blockgroup <11, 0, 32> ext2fs read inode blkno 0 blkoff 0 <12582928, 0, 128> ext2fs_read_block 00081000 <4227072, 0, 8> ext2fs_read_block 00081000 <4227072, 8, 1> iterate >.< ext2fs_read_block 00081000 <4227072, 12, 8> ext2fs_read_block 00081000 <4227072, 20, 2> iterate >..< Unable to read "/boot/uImage" from mmc 0:1 ** << FAIURE CANNOT LOAD uIimage FROM /boot/ Marvell>> This indicates exactly the "standard" way this card / u-boot fails. I hope this ouput is of use to you. What would you like me to try next? cheers Patrick

71	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: January 04, 2010, 04:09:23 PM
Hi pingtoo, I will be very happy to test any debug versions or experiments you want me to try. Just say what you want me to do, cheers Patrick

72	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: January 04, 2010, 04:04:17 AM
@pingtoo, I am sorry for the delay in replying, I have had to visit relatives for the weekend. I apologise that I was not clear in my English to you, I will try to keep it more straightforward in future. Regarding your request for error printouts, unforunately there are not any of much use. U-Boot ether works OK or returns no output when it fails. Trying a ext2ls, if it fails, just returns to the uboot prompt when trying to execute:- set bootargs 'console=ttyS0,115200 ro root=/dev/mmcblk0p1 rootdelay=1' mmcinit ext2load mmc 0 0x800000 /boot/uImage uboot reports 0 bytes read and returns to uboot prompt The post from "restamp" just above in this thread, sums it up very well! Thanks again to everyone who are working to make u-boot more solid! regards Patrick

73	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: January 01, 2010, 04:10:13 PM
hi pingtoo, No you mis-understand me. Please re read my previous reply, and this reply, to clarify. ALL my problems are with u-boot and the rfs. I have no problems reading /boot/uImage with the sdhc card mounted using a card reader on my linux m/c. The directories /boot, /etc, and /dev have exactly the same owners. Using ext2ls from u-boot, /boot/ and /etc appear empty, but /dev returns a list of files The only diff in owner and permissions is that the first digit of the permissions, (d,p,b,c etc) is null in the failing directories file contents and are used in all the files and directories in /dev. OF COURSE THE FILE SYSTEM IS EXT2!!!!! I am using a single 8gb ext2 partition on my sdhc card. If I move uImage from inside /boot and put it in the root (/uImage) then i can boot it using ext2load and run my deb system OK, from the sdhc card, including a fsck of the ext2fs on bootup! All files list ok using linux pc. (see included listings in previous post). Read the same problem from the other poster, I included a pointer. cheers Patrick

74	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot patched 3.4.27 - STILL PROBLEMS	on: January 01, 2010, 10:11:33 AM
Hi pingtoo and rooster. I have been doing so more testing with the patched version of uboot 3.4.27 and my 8GB Kingston class 6 card. I cleared the card completely... and reformatted with ext2fs. I untarred a Debian root file system from M Gilespie (sp?) on it. I cross compiled a new uImage, and installed it in /boot on the card. When I tried to ext2load /boot/uImage or ext2ls mmc 0:1 /boot uboot returned an empty directory !!! HOWEVER ext2ls mmc 0:1 /dev returned a list of the contents ? Looking through this forum I found this entry, (actually to rooster!):- http://plugcomputer.org/plugforum/index.php?topic=307.msg3117#msg3117 Which describes my problem exactly. So I moved uImage from /boot to / on the card and booted manually thus:- Quote set bootargs 'console=ttyS0,115200 ro root=/dev/mmcblk0p1 rootdelay=3' mmcinit ext2load mmc 0 0x800000 /uImage bootm 0x800000 This worked OK and loaded and booted my new kernel which runs OK. The number of manual mmcinits I give do not make any difference. Now the problem is that the only difference between ext2load working and not working is a new ext2fs using the same command, untarring the same root file system, but installing a new kernel, which will be slightly different in size on the SAME SDHC card. Now a further interesting observation. I tried an ext2ls on /boot failed /dev returned contents OK /etc failed When I put the card in a reader on my Linux box, and did a ls -la on /boot , /dev, and /etc, I found that there was a difference, /boot and /etc contents had NO alpha bit set and failed to list, all the files and directories in /dev had the ALPHA character of the permision set thus:- Quote debsilch:/mnt/plug# ls -la dev total 16 drwxr-xr-x 4 root root 4096 2010-01-01 16:36 . drwxr-xr-x 21 root root 4096 2010-01-01 16:32 .. crw-rw---- 1 root video 10, 175 2009-12-03 12:35 agpgart crw-rw---- 1 root audio 14, 4 2009-12-03 12:35 audio crw-rw---- 1 root audio 14, 20 2009-12-03 12:35 audio1 crw-rw---- 1 root audio 14, 36 2009-12-03 12:35 audio2 crw-rw---- 1 root audio 14, 52 2009-12-03 12:35 audio3 crw-rw---- 1 root audio 14, 7 2009-12-03 12:35 audioctl crw------- 1 root tty 5, 1 2009-12-03 12:34 console lrwxrwxrwx 1 root root 11 2010-01-01 15:27 core -> /proc/kcore crw-rw---- 1 root audio 14, 3 2009-12-03 12:35 dsp crw-rw---- 1 root audio 14, 19 2009-12-03 12:35 dsp1 crw-rw---- 1 root audio 14, 35 2009-12-03 12:35 dsp2 crw-rw---- 1 root audio 14, 51 2009-12-03 12:35 dsp3 lrwxrwxrwx 1 root root 13 2010-01-01 15:27 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 2009-12-03 12:34 full prw------- 1 root root 0 2009-12-03 12:35 initctl crw-r----- 1 root kmem 1, 2 2009-12-03 12:34 kmem srw-rw-rw- 1 root root 0 2010-01-01 16:36 log brw-rw---- 1 root disk 7, 0 2009-12-03 12:34 loop0 brw-rw---- 1 root disk 7, 1 2009-12-03 12:34 loop1 brw-rw---- 1 root disk 7, 2 2009-12-03 12:34 loop2 brw-rw---- 1 root disk 7, 3 2009-12-03 12:34 loop3 brw-rw---- 1 root disk 7, 4 2009-12-03 12:34 loop4 brw-rw---- 1 root disk 7, 5 2009-12-03 12:34 loop5 brw-rw---- 1 root disk 7, 6 2009-12-03 12:34 loop6 brw-rw---- 1 root disk 7, 7 2009-12-03 12:34 loop7 crw-r----- 1 root kmem 1, 1 2009-12-03 12:34 mem crw-rw---- 1 root audio 35, 0 2009-12-03 12:35 midi0 crw-rw---- 1 root audio 14, 2 2009-12-03 12:35 midi00 crw-rw---- 1 root audio 14, 18 2009-12-03 12:35 midi01 crw-rw---- 1 root audio 14, 34 2009-12-03 12:35 midi02 crw-rw---- 1 root audio 14, 50 2009-12-03 12:35 midi03 crw-rw---- 1 root audio 35, 1 2009-12-03 12:35 midi1 crw-rw---- 1 root audio 35, 2 2009-12-03 12:35 midi2 crw-rw---- 1 root audio 35, 3 2009-12-03 12:35 midi3 crw-rw---- 1 root audio 14, 0 2009-12-03 12:35 mixer crw-rw---- 1 root audio 14, 16 2009-12-03 12:35 mixer1 crw-rw---- 1 root audio 14, 32 2009-12-03 12:35 mixer2 crw-rw---- 1 root audio 14, 48 2009-12-03 12:35 mixer3 crw-rw---- 1 root audio 31, 0 2009-12-03 12:35 mpu401data crw-rw---- 1 root audio 31, 1 2009-12-03 12:35 mpu401stat crw-rw-rw- 1 root root 1, 3 2009-12-03 12:34 null crw-r----- 1 root kmem 1, 4 2009-12-03 12:34 port crw-rw-rw- 1 root tty 5, 2 2009-10-04 21:23 ptmx drwxr-xr-x 2 root root 4096 2009-12-03 12:35 pts lrwxrwxrwx 1 root root 4 2010-01-01 15:26 ram -> ram1 brw-rw---- 1 root disk 1, 0 2009-12-03 12:34 ram0 brw-rw---- 1 root disk 1, 1 2009-12-03 12:34 ram1 brw-rw---- 1 root disk 1, 10 2009-12-03 12:34 ram10 brw-rw---- 1 root disk 1, 11 2009-12-03 12:34 ram11 brw-rw---- 1 root disk 1, 12 2009-12-03 12:34 ram12 brw-rw---- 1 root disk 1, 13 2009-12-03 12:34 ram13 brw-rw---- 1 root disk 1, 14 2009-12-03 12:34 ram14 brw-rw---- 1 root disk 1, 15 2009-12-03 12:34 ram15 brw-rw---- 1 root disk 1, 16 2009-12-03 12:34 ram16 brw-rw---- 1 root disk 1, 2 2009-12-03 12:34 ram2 brw-rw---- 1 root disk 1, 3 2009-12-03 12:34 ram3 brw-rw---- 1 root disk 1, 4 2009-12-03 12:34 ram4 brw-rw---- 1 root disk 1, 5 2009-12-03 12:34 ram5 brw-rw---- 1 root disk 1, 6 2009-12-03 12:34 ram6 brw-rw---- 1 root disk 1, 7 2009-12-03 12:34 ram7 brw-rw---- 1 root disk 1, 8 2009-12-03 12:34 ram8 brw-rw---- 1 root disk 1, 9 2009-12-03 12:34 ram9 crw-rw-rw- 1 root root 1, 8 2009-12-03 12:34 random crw-rw---- 1 root audio 35, 64 2009-12-03 12:35 rmidi0 crw-rw---- 1 root audio 35, 65 2009-12-03 12:35 rmidi1 crw-rw---- 1 root audio 35, 66 2009-12-03 12:35 rmidi2 crw-rw---- 1 root audio 35, 67 2009-12-03 12:35 rmidi3 crw-rw---- 1 root audio 14, 1 2009-12-03 12:35 sequencer drwxr-xr-x 3 root root 4096 2009-12-03 12:36 shm crw-rw---- 1 root audio 35, 128 2009-12-03 12:35 smpte0 crw-rw---- 1 root audio 35, 129 2009-12-03 12:35 smpte1 crw-rw---- 1 root audio 35, 130 2009-12-03 12:35 smpte2 crw-rw---- 1 root audio 35, 131 2009-12-03 12:35 smpte3 crw-rw---- 1 root audio 14, 6 2009-12-03 12:35 sndstat lrwxrwxrwx 1 root root 4 2010-01-01 15:26 stderr -> fd/2 lrwxrwxrwx 1 root root 4 2010-01-01 15:26 stdin -> fd/0 lrwxrwxrwx 1 root root 4 2010-01-01 15:26 stdout -> fd/1 crw-rw-rw- 1 root tty 5, 0 2009-12-03 12:34 tty crw------- 1 root tty 4, 0 2009-12-03 12:34 tty0 crw------- 1 root tty 4, 1 2009-12-03 12:34 tty1 crw------- 1 root tty 4, 2 2009-12-03 12:34 tty2 crw------- 1 root tty 4, 3 2009-12-03 12:34 tty3 crw------- 1 root tty 4, 4 2009-12-03 12:34 tty4 crw------- 1 root tty 4, 5 2009-12-03 12:34 tty5 crw------- 1 root tty 4, 6 2009-12-03 12:34 tty6 crw------- 1 root tty 4, 7 2009-12-03 12:35 tty7 crw------- 1 root tty 4, 8 2009-12-03 12:35 tty8 crw------- 1 root tty 4, 9 2009-12-03 12:35 tty9 crw-rw-rw- 1 root root 1, 9 2009-12-03 12:34 urandom prw-r----- 1 root adm 0 2010-01-01 16:57 xconsole crw-rw-rw- 1 root root 1, 5 2009-12-03 12:34 zero Whereas the failing directory /etc looks like:- Quote debsilch:/mnt/plug# ls -la etc total 428 drwxr-xr-x 42 root root 4096 2010-01-01 16:36 . drwxr-xr-x 21 root root 4096 2010-01-01 16:32 .. -rw-r--r-- 1 root root 2986 2009-12-03 12:35 adduser.conf -rw-r--r-- 1 root root 44 2009-12-03 12:33 adjtime drwxr-xr-x 2 root root 4096 2009-12-03 12:37 alternatives drwxr-xr-x 4 root root 4096 2009-12-03 12:36 apt -rw-r--r-- 1 root root 1453 2008-05-13 16:49 bash.bashrc drwxr-xr-x 2 root root 4096 2009-12-03 12:37 bash_completion.d -rw-r--r-- 1 root root 332 2009-01-04 16:12 bindresvport.blacklist drwxr-xr-x 2 root root 4096 2009-12-03 12:35 calendar drwxr-xr-x 2 root root 4096 2009-12-03 12:35 cron.d drwxr-xr-x 2 root root 4096 2009-12-03 12:36 cron.daily drwxr-xr-x 2 root root 4096 2009-12-03 12:35 cron.hourly drwxr-xr-x 2 root root 4096 2009-12-03 12:35 cron.monthly -rw-r--r-- 1 root root 724 2008-09-28 12:07 crontab drwxr-xr-x 2 root root 4096 2009-12-03 12:36 cron.weekly -rw-r--r-- 1 root root 54 2009-12-03 12:37 crypttab -rw-r--r-- 1 root root 2969 2008-10-12 18:07 debconf.conf -rw-r--r-- 1 root root 6 2009-08-30 21:01 debian_version drwxr-xr-x 2 root root 4096 2009-12-03 12:37 default -rw-r--r-- 1 root root 600 2008-08-10 22:35 deluser.conf drwxr-xr-x 4 root root 4096 2009-12-03 12:36 dhcp3 drwxr-xr-x 3 root root 4096 2009-12-03 12:35 dpkg -rw-r--r-- 1 root root 0 2009-12-03 12:35 environment -rw-r--r-- 1 root root 37 2009-12-03 12:33 fstab -rw-r--r-- 1 root root 2689 2009-01-04 16:15 gai.conf drwxr-xr-x 2 root root 4096 2009-12-03 12:35 groff -rw-r--r-- 1 root root 487 2009-12-03 12:37 group -rw------- 1 root root 476 2009-12-03 12:35 group- -rw-r----- 1 root shadow 406 2009-12-03 12:37 gshadow -rw------- 1 root root 398 2009-12-03 12:35 gshadow- -rw-r--r-- 1 root root 9 2006-08-07 18:14 host.conf -rw-r--r-- 1 root root 7 2009-12-03 12:36 hostname -rw-r--r-- 1 root root 37 2009-12-03 12:36 hosts -rw-r--r-- 1 root root 579 2009-12-03 12:36 hosts.allow -rw-r--r-- 1 root root 878 2009-12-03 12:36 hosts.deny drwxr-xr-x 2 root root 4096 2009-12-03 12:37 init.d -rw-r--r-- 1 root root 1307 2009-12-03 12:36 inittab -rw-r--r-- 1 root root 1723 2009-01-14 11:19 inputrc drwxr-xr-x 2 root root 4096 2009-12-03 12:35 iproute2 -rw-r--r-- 1 root root 28 2009-08-31 04:45 issue -rw-r--r-- 1 root root 21 2009-08-31 04:45 issue.net drwxr-xr-x 2 root root 4096 2009-12-03 12:37 keys -rw-r--r-- 1 root root 7335 2009-12-03 12:37 ld.so.cache -rw-r--r-- 1 root root 34 2009-12-03 12:34 ld.so.conf drwxr-xr-x 2 root root 4096 2009-12-03 12:34 ld.so.conf.d -rw-r--r-- 1 root root 118 2009-12-03 12:35 localtime -rw-r--r-- 1 root root 10879 2008-11-22 20:16 login.defs -rw-r--r-- 1 root root 599 2008-10-08 16:53 logrotate.conf drwxr-xr-x 2 root root 4096 2009-12-03 12:36 logrotate.d drwxr-xr-x 2 root root 4096 2008-08-18 22:34 lsb-base -rw-r--r-- 1 root root 4630 2009-01-25 03:27 manpath.config -rw-r--r-- 1 root root 803 2008-10-13 06:06 mke2fs.conf drwxr-xr-x 3 root root 4096 2009-12-03 12:35 modprobe.d -rw-r--r-- 1 root root 248 2009-12-03 12:35 modules lrwxrwxrwx 1 root root 13 2010-01-01 15:27 motd -> /var/run/motd -rw-r--r-- 1 root root 286 2009-12-03 12:35 motd.tail -rw-r--r-- 1 root root 297 2010-01-01 16:36 mtab -rw-r--r-- 1 root root 7672 2008-08-26 17:31 nanorc drwxr-xr-x 6 root root 4096 2009-12-03 12:36 network -rw-r--r-- 1 root root 60 2009-12-03 12:35 networks lrwxrwxrwx 1 root root 28 2010-01-01 15:27 nologin -> /var/lib/initscripts/nologin -rw-r--r-- 1 root root 475 2006-08-28 17:33 nsswitch.conf drwxr-xr-x 2 root root 4096 2009-12-03 12:33 opt -rw-r--r-- 1 root root 552 2009-03-17 23:58 pam.conf drwxr-xr-x 2 root root 4096 2009-12-03 12:37 pam.d -rw-r--r-- 1 root root 811 2009-12-03 12:37 passwd -rw------- 1 root root 811 2009-12-03 12:37 passwd- -rw-r--r-- 1 root root 475 2006-10-28 14:42 profile -rw-r--r-- 1 root root 2626 2008-08-28 03:00 protocols -rw------- 1 root root 0 2009-12-03 12:35 .pwd.lock drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc0.d drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc1.d drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc2.d drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc3.d drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc4.d drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc5.d drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rc6.d -rwxr-xr-x 1 root root 306 2009-12-03 12:35 rc.local drwxr-xr-x 2 root root 4096 2009-12-03 12:37 rcS.d -rw-r--r-- 1 root root 55 2010-01-01 16:36 resolv.conf -rwxr-xr-x 1 root root 268 2008-04-17 14:22 rmt -rw-r--r-- 1 root root 887 2008-08-28 03:00 rpc -rw-r--r-- 1 root root 2565 2009-02-08 04:00 rsyslog.conf drwxr-xr-x 2 root root 4096 2009-02-08 04:13 rsyslog.d -rw-r--r-- 1 root root 1287 2008-11-22 20:16 securetty drwxr-xr-x 2 root root 4096 2009-12-03 12:35 security -rw-r--r-- 1 root root 18480 2008-08-28 03:00 services -rw-r----- 1 root shadow 563 2009-12-03 12:37 shadow -rw------- 1 root root 563 2009-12-03 12:37 shadow- -rw-r--r-- 1 root root 155 2009-12-03 12:35 shells drwxr-xr-x 2 root root 4096 2009-12-03 12:35 skel drwxr-xr-x 2 root root 4096 2009-12-03 12:37 ssh -rw-r--r-- 1 root root 2275 2009-01-11 22:11 sysctl.conf drwxr-xr-x 2 root root 4096 2009-01-11 22:11 sysctl.d drwxr-xr-x 2 root root 4096 2009-12-03 12:35 terminfo -rw-r--r-- 1 root root 8 2009-12-03 12:35 timezone drwxr-xr-x 3 root root 4096 2008-04-29 05:39 udev drwxr-xr-x 2 root root 4096 2009-12-03 12:35 vim -rw-r--r-- 1 root root 4221 2008-09-08 06:03 wgetrc drwxr-xr-x 4 root root 4096 2009-12-03 12:37 X11 I cannot think of any reason why the alpha character ( which stands for b block c charc d directory etc etc), should have any effect on making the ext2ls work correctly! I can only conclude that there is STILL something very flakey with U-boot, even the much improved patched version 3.4.27 regards Patrick

75	Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25	on: December 28, 2009, 06:02:16 AM
@pingtoo Result of quick test (only one off, we have visitors and my wife is giving me stick to turn this lot off now!!!!) WONDERFUL!!!!!!!!!! I dl'd your patched uboot and burnt it to nand. Using the 8GB Kingston SDHC card and exactly the same RFS and uImage as before, and the same bootargs and ext2load command as before, uImage loads correctly and boots OK. I need to set the mainline stuff in the env, but thats not what we were testing! I will do more exhaustive testing once our visitors have gone Thanks for your work (AND everybody else who has grafted on this!!!!! Wish you all a Happy and Prosperous New Year regards Patrick

Pages: 1 ... 3 4 [5] 6 7 ... 10