Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 3247

usb key not recognized on pogo E02 (2 replies)

$
0
0
Hi all,

I've run debian on my pogo E02 successfully sereval years. Now, my USB key died. I thus prepared a new and bigger key with the newest rootfs I found. Problem is, the pogo E02 does not like the usb key. Here is the output of the netconsole:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700)
Pogo E02
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=3", size 91 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 727, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 704, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Error reading superblock on volume 'rootfs' errno=-22!
ubifsmount - mount UBIFS volume


Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
1 bytes read in 253 ms (0 Bytes/s)
Found bootable drive on usb 0:1
3832036 bytes read in 410 ms (8.9 MiB/s)
EHCI timed out on TD - token=0x4e008d80
EHCI timed out on TD - token=0x4e008d80
EHCI timed out on TD - token=0x4e008d80
 ** ext4fs_devread read error - block
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2019-03-10   9:13:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3831972 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK


Starting kernel ...

Your help is highly appreciated.

Best,
Andreas

Viewing all articles
Browse latest Browse all 3247

Trending Articles