|
|
 |
« on: April 30, 2009, 12:17:10 PM » |
|
So, I killed the installation on my plug and am trying to reinstall with the help of the USB recover document. I am following it, put an ext2 (tried ext3 with same results) fs on it and the following files:
-rw-r--r-- 1 root root 72011776 2009-04-30 14:53 flashware.img -rw-r--r-- 1 root root 470808 2009-04-30 14:53 u-boot-rd88f6281Sheevaplug_400db_nand.bin -rw-r--r-- 1 root root 142475264 2009-04-30 14:53 ubuntu-9.0.5.Release.jffs2 -rw-r--r-- 1 root root 2070316 2009-04-30 14:54 uImage.sheeva.040309
I do the initial configuration (I did NOT install a new U-boot image via tftp first, is this required?), reset and sent the rcvr command, it starts fetching stuff from the USB drive, ending in the following error:
" .................. ....... ......................... ......................... ......................... ......................... ......................... ** ext2fs doesn't support tripple indirect blocks. **
** Unable to read "/flashware.img" from usb 0:1 ** Couldn't load recovery image from USB flash drive, Trying network interface "
Has anyone else seen this before?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #1 on: April 30, 2009, 12:37:57 PM » |
|
My USB drive was formatted for DOS (FAT16 I believe). I placed the files on it and uboot had no problem reading them during recovery.
I don't believe that the uboot has a proven ext2 loader. I just read that most have vfat(msdos) formatted drives used in the USB recovery process.
|
|
|
|
« Last Edit: April 30, 2009, 12:41:35 PM by bfmorgan »
|
Logged
|
|
|
|
|
|
|
 |
« Reply #2 on: April 30, 2009, 12:43:11 PM » |
|
My USB drive was formatted for DOS (FAT16 I believe). I placed the files on it and uboot had no problem reading them during recovery.
Which U-boot do you have? The document says ext2/ext3. I did an e2fsck -c on my usb drive as well, just in case. Is it at all possible to put a new U-boot on from usb or mmc? Would make things easier than having to set up the required network services first. /MD
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #3 on: April 30, 2009, 01:21:34 PM » |
|
The USB recovery uses bubt with needs a tftp server. I don't know of any other way to get it to load from any other type of device.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #4 on: April 30, 2009, 01:26:32 PM » |
|
I put the files on a vfat filesystem instead, and I noticed that I had consistently set the mtd1Size wrong (an extra 0)
It boots much farther, but ends in a Kernel Panic:
" RAMDISK: Couldn't find valid RAM disk image starting at 0. List of all partitions: 1f00 1024 mtdblock0 (driver?) 1f01 2048 mtdblock1 (driver?) 1f02 521216 mtdblock2 (driver?) No filesystem could mount root, tried: squashfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) "
I remember having seen this on the forums, so will look around, anyone with a definite recipe, let me know?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #5 on: May 04, 2009, 01:58:25 AM » |
|
same here! any good advice?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #6 on: May 04, 2009, 05:35:13 PM » |
|
Can you provide the U-Boot environment dump right from u-boot startup?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #7 on: May 14, 2009, 05:26:41 AM » |
|
Can you provide the U-Boot environment dump right from u-boot startup?
here is (please suggest) : ===== QUOTE ===== Marvell>> printenv baudrate=115200 loads_echo=0 ipaddr=10.4.50.165 serverip=10.4.50.5 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; ethaddr=00:50:43:6f:2f:33 ethmtu=1500 mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host yuk_ethaddr=00:00:00:EE:51:81 nandEcc=1bit netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no ethact=egiga0 run_diag=no bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.e bootcmd_usb=usb start; ext2load usb 0:1 0x0800000 /boot/uInitrd; ext2load usb 0:1 0x400000 /boot/uImage arcNumber=2097 bootargs_root=root=/dev/mtdblock2 ro bootcmd=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 stdin=serial stdout=serial stderr=serial mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=3 disaMvPnp=no enaAutoRecovery=yes Environment size: 1455/131068 bytes Marvell>> ===== UNQUOTE =====
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #8 on: May 17, 2009, 11:40:37 AM » |
|
I can confirm that with u-boot-rd88f6281Sheevaplug_400db_nand.bin I was unable to use any of my USB thumb drives 256MB, 1GB, 4GB in either ext2/ext3 or fat32 and successfully boot the flashware.img.
However as soon as i formatted one of them to fat16 (even though the filenames were truncated in the mount), uBoot loaded the image fine.
So I now have recovered my SheevaPlug after being hit with the "unable to login" issue.
Jae
|
|
|
|
|
Logged
|
|
|
|
|
bezaur
Newbie
Karma: 0
Posts: 2
|
 |
« Reply #9 on: June 25, 2009, 09:53:04 AM » |
|
I'm also having a problem using the usb recovery. I formatted a usb stick as fat16, I've copied over the files from the USB recovery: 06/24/2009 07:25 PM 72,011,776 flashware.img 06/24/2009 07:25 PM 470,808 u-boot-rd88f6281Sheevaplug_400db_nand.bin 06/24/2009 07:25 PM 2,070,316 uImage.sheeva.040309 03/19/2009 02:53 PM 142,475,264 ubuntu-9.0.5.Release.jffs2
md5sums: b8ce660ddd8bb764f28d6395261e7b52 *flashware.img 35365bf593a36419f38725d8c66ad791 *u-boot-rd88f6281Sheevaplug_400db_nand.bin fc341724950a3fcd9e2c28a5fe70f895 *uImage.sheeva.040309 9d98e66b8718e2083e9d82e7dc72b62a *ubuntu-9.0.5.Release.jffs2
and followed the recovery directions (including updating the uboot and modifying the env variables). When I reset and run the rcvr command I get something that looks very similar to the doc's boot except for the end where it can't find the squashfs (snippets of boot below). I can post the full printenv and boot sequence if people are interested, but wondering if anyone has any pointers as to where to start looking to track this down. Is this likely a problem with the env? the flashware.img? Other? -- charles Marvell>> rcvr USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Trying to load image from USB flash drive using FAT FS reading /flashware.img
...
72011776 bytes read Update bootcmd
bootcmd: setenv bootargs $(console) root=/dev/ram0 rootfstype=squashfs initrd=0x2400000,0x40ad000 ramdisk_size=66228 recovery=usb serverip=0.0.0.0; bootm 0x2000000; Booting the image (@ 0x2000000)... ## Booting image at 02000000 ... Image Name: Linux-2.6.22.18 Created: 2009-03-30 15:30:26 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2148292 Bytes = 2 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel. Linux version 2.6.22.18 (root@localhost.localdomain) (gcc version 4.2.1) #2 Mon Mar 30 08:30:12 PDT 2009 CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177 Machine: Feroceon-KW Using UBoot passing parameters structure Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists. Total pages: 130048 Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)rw root=/dev/ram0 rootfstype=squashfs initrd=0x2400000,0x40ad000 ramdisk_size=66228 recovery=usb serverip=0.0.0.0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB 0MB 0MB = 512MB total Memory: 449024KB available (3920K code, 260K data, 124K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16
CPU Interface ------------- SDRAM_CS0 ....base 00000000, size 256MB SDRAM_CS1 ....base 10000000, size 256MB SDRAM_CS2 ....disable SDRAM_CS3 ....disable PEX0_MEM ....base e8000000, size 128MB PEX0_IO ....base f2000000, size 1MB INTER_REGS ....base f1000000, size 1MB NFLASH_CS ....base fa000000, size 2MB SPI_CS ....base f4000000, size 16MB BOOT_ROM_CS ....no such DEV_BOOTCS ....no such CRYPT_ENG ....base f0000000, size 2MB
Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG Soc: 88F6281 A0 LE
Detected Tclk 200000000 and SysClk 400000000 MV Buttons Device Load
...
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com dm_crypt using the OCF package. sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mvsdmmc: irq =28 start f1090000 mvsdmmc: no IRQ detect usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). mvCLAudioCodecRegGet: Error while reading register! mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID! Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list: #0: Marvell mv88fx_snd ALSA driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Couldn't find valid RAM disk image starting at 0. List of all partitions: 1f00 1024 mtdblock0 (driver?) 1f01 4096 mtdblock1 (driver?) 1f02 519168 mtdblock2 (driver?) No filesystem could mount root, tried: squashfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
|
|
|
|
|
Logged
|
|
|
|
|
bezaur
Newbie
Karma: 0
Posts: 2
|
 |
« Reply #10 on: June 25, 2009, 07:28:28 PM » |
|
As a followup, I'm adding my version, printenv and full output of the rcvr boot attempt below: Marvell>> version
U-Boot 1.1.4 (Apr 9 2009 - 12:23:12) Marvell version: 3.4.16 Marvell>> printenv baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/mtdblock2 ro ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 cesvcid=ULULULULULULPPULULULULULDA bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 yuk_ethaddr=00:00:00:EE:51:81 netretry=no autoload=no ethaddr=00:50:43:01:CA:1E run_diag=no bootcmd=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 ipaddr=172.18.126.190 serverip=172.18.126.189 rcvrip=172.18.126.189 loadaddr=0x2000000 mtd1Size=0x400000 filesize=0x44ad000 bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)rw root=/dev/mtdblock2 stdin=serial stdout=serial stderr=serial console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)rw mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=3 disaMvPnp=no enaAutoRecovery=yes
Environment size: 1392/131068 bytes Marvell>> rcvr USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Trying to load image from USB flash drive using FAT FS reading /flashware.img . ... ...
72011776 bytes read Update bootcmd
bootcmd: setenv bootargs $(console) root=/dev/ram0 rootfstype=squashfs initrd=0x2400000,0x40ad000 ramdisk_size=66228 recovery=usb serverip=0.0.0.0; bootm 0x2000000; Booting the image (@ 0x2000000)... ## Booting image at 02000000 ... Image Name: Linux-2.6.22.18 Created: 2009-03-30 15:30:26 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2148292 Bytes = 2 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel. Linux version 2.6.22.18 (root@localhost.localdomain) (gcc version 4.2.1) #2 Mon Mar 30 08:30:12 PDT 2009 CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177 Machine: Feroceon-KW Using UBoot passing parameters structure Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists. Total pages: 130048 Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)rw root=/dev/ram0 rootfstype=squashfs initrd=0x2400000,0x40ad000 ramdisk_size=66228 recovery=usb serverip=0.0.0.0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB 0MB 0MB = 512MB total Memory: 449024KB available (3920K code, 260K data, 124K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16
CPU Interface ------------- SDRAM_CS0 ....base 00000000, size 256MB SDRAM_CS1 ....base 10000000, size 256MB SDRAM_CS2 ....disable SDRAM_CS3 ....disable PEX0_MEM ....base e8000000, size 128MB PEX0_IO ....base f2000000, size 1MB INTER_REGS ....base f1000000, size 1MB NFLASH_CS ....base fa000000, size 2MB SPI_CS ....base f4000000, size 16MB BOOT_ROM_CS ....no such DEV_BOOTCS ....no such CRYPT_ENG ....base f0000000, size 2MB
Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG Soc: 88F6281 A0 LE
Detected Tclk 200000000 and SysClk 400000000 MV Buttons Device Load Marvell USB EHCI Host controller #0: c08ab600 PEX0 interface detected no Link. PCI: bus0: Fast back to back transfers enabled SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 Time: kw_clocksource clocksource has been installed. IP route cache hash table entries: 16384 (order: 4, 65536 bytes) TCP established hash table entries: 65536 (order: 7, 524288 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 65536 bind 65536) TCP reno registered checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 66228K RTC registered Use the XOR engines (acceleration) for enhancing the following functions: o RAID 5 Xor calculation o kernel memcpy o kenrel memzero Number of XOR engines to use: 4 cesadev_init(c0011674) mvCesaInit: sessions=640, queue=64, pSram=f0000000 Warning: TS unit is powered off. MV Buttons Driver Load squashfs: version 3.3 (2007/10/31) Phillip Lougher squashfs: LZMA suppport for slax.org by jro NTFS driver 2.1.28 [Flags: R/O]. JFFS2 version 2.2. (NAND) é 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler anticipatory registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A RAMDISK driver initialized: 20 RAM disks of 66228K size 4096 blocksize loop: module loaded Loading Marvell Ethernet Driver: o Cached descriptors in DRAM o DRAM SW cache-coherency o Single RX Queue support - ETH_DEF_RXQ=0 o Single TX Queue support - ETH_DEF_TXQ=0 o TCP segmentation offload enabled o Receive checksum offload enabled o Transmit checksum offload enabled o Network Fast Processing (Routing) supported o Driver ERROR statistics enabled o Driver INFO statistics enabled o Proc tool API enabled o Rx descripors: q0=128 o Tx descripors: q0=532 o Loading network interface(s): o eth0, ifindex = 1, GbE port = 0 o eth1, ifindex = 2, GbE port = 1
mvFpRuleDb (c5cb0000): 16384 entries, 65536 bytes Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI Copyright (c) 1999-2006 Intel Corporation. e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI e100: Copyright(c) 1999-2006 Intel Corporation
Warning Sata is Powered Off NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 288 at 0x02400000 Bad eraseblock 971 at 0x07960000 Bad eraseblock 2060 at 0x10180000 mtd: bad character after partition (r) 3 cmdlinepart partitions found on MTD device nand_mtd Using command line partition definition Creating 3 MTD partitions on "nand_mtd": 0x00000000-0x00100000 : "uboot" 0x00100000-0x00500000 : "uImage" 0x00500000-0x20000000 : "rootfs" ehci_marvell ehci_marvell.70059: Marvell Orion EHCI ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1 ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100 ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected USB Universal Host Controller Interface driver v3.0 usb 1-1: new high speed USB device using ehci_marvell and address 2 usb 1-1: configuration #1 chosen from 1 choice usbcore: registered new interface driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice i2c /dev entries driver Linux telephony interface: v1.00 Marvell Telephony Driver: mvBoardVoiceAssembleModeGet: TDM not supported(boardId=0x9) assembly=-1,irq=-1 mp_check_config: Error, invalid voice assembley mode md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 raid6: int32x1 97 MB/s raid6: int32x2 114 MB/s raid6: int32x4 122 MB/s raid6: int32x8 111 MB/s raid6: using algorithm int32x4 (122 MB/s) md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 raid5: measuring checksumming speed arm4regs : 1084.000 MB/sec 8regs : 754.800 MB/sec 32regs : 899.600 MB/sec raid5: using function: arm4regs (1084.000 MB/sec) device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com dm_crypt using the OCF package. sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mvsdmmc: irq =28 start f1090000 mvsdmmc: no IRQ detect usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). mvCLAudioCodecRegGet: Error while reading register! mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID! Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list: #0: Marvell mv88fx_snd ALSA driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Couldn't find valid RAM disk image starting at 0. List of all partitions: 1f00 1024 mtdblock0 (driver?) 1f01 4096 mtdblock1 (driver?) 1f02 519168 mtdblock2 (driver?) No filesystem could mount root, tried: squashfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #11 on: June 26, 2009, 06:17:49 AM » |
|
Guys, when formatting the USB to EXT2 you must use the mksf.ext2 -I 128 option to use inode size of 128byte, otherwise uboot will not mount the partition.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #12 on: July 03, 2009, 03:33:18 AM » |
|
im having the same issues (kernel panic)
FAT16 formatted, copied the 4 files over, rcvr, seems to be plodding along nicely and then BOOM, kernel panic, same point as everyone else...
have you guys got solutions yet?
thanks Duke
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #13 on: August 06, 2009, 02:42:04 AM » |
|
I am also unable to boot the recovery image: RAMDISK: Couldn't find valid RAM disk image starting at 0. List of all partitions: 1f00 1024 mtdblock0 (driver?) 1f01 2048 mtdblock1 (driver?) 1f02 521216 mtdblock2 (driver?) No filesystem could mount root, tried: squashfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Same as bezaur above. --setimike
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #14 on: August 06, 2009, 04:27:01 AM » |
|
Ok, I did finally follow the instructions, set up a tftp server to run bubt and that allowed me to run recovery image.
|
|
|
|
|
Logged
|
|
|
|
|
|