On Thu, Apr 11, 2019 at 4:13 PM Martin Michlmayr <t...@cyrius.com> wrote:
> * Lieven Baes <y...@waime.eu> [2019-04-11 15:05]: > > What can I do instead of a whole reinstall ? > > Is there a trick to boot the 'old' system? > > This should work: > setenv bootargs $(bootargs_console) > usb start > ext2load usb 1:1 0x00800000 /uImage.bak > ext2load usb 1:1 0x01100000 /uInitrd.bak > bootm 0x00800000 0x01100000 > > But before you do that, can you try: > setenv bootargs $(bootargs_console) earlyprintk=serial,ttyS0,115200 > usb start > ext2load usb 1:1 0x00800000 /uImage > ext2load usb 1:1 0x01100000 /uInitrd > bootm 0x00800000 0x01100000 > > or maybe: > setenv bootargs $(bootargs_console) earlyprintk > usb start > ext2load usb 1:1 0x00800000 /uImage > ext2load usb 1:1 0x01100000 /uInitrd > bootm 0x00800000 0x01100000 > > to see if you can get more debug info. > Thx, now there is a bit more debug-output: => setenv bootargs $(bootargs_console) earlyprintk=serial,ttyS0,115200 => usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... Device NOT ready Request Sense returned 02 3A 00 2 Storage Device(s) found => ext2load usb 1:1 0x00800000 /uImage 2066746 bytes read in 450 ms (4.4 MiB/s) => ext2load usb 1:1 0x01100000 /uInitrd 12288774 bytes read in 1777 ms (6.6 MiB/s) => bootm 0x00800000 0x01100000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: kernel 4.9.0-8-marvell Created: 2019-02-26 16:56:20 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2066682 Bytes = 2 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: ramdisk 4.9.0-8-marvell Created: 2019-02-26 16:56:21 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 12288710 Bytes = 11.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.0-8-marvell (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 Debian 4.9.130-2 (2018-10-27) [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] OF: fdt:Machine model: Globalscale Technologies Guruplug Server Plus [ 0.000000] bootconsole [earlycon0] enabled [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: $(bootargs_console) earlyprintk=serial,ttyS0,115200 [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 501664K/524288K available (3789K kernel code, 396K rwdata, 1132K rodata, 296K init, 249K bss, 22624K reserved, 0K cma-reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff800000 ( 496 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc03bb868 (3791 kB) [ 0.000000] .init : 0xc04f8000 - 0xc0542000 ( 296 kB) [ 0.000000] .data : 0xc0542000 - 0xc05a53f8 ( 397 kB) [ 0.000000] .bss : 0xc05a53f8 - 0xc05e39fc ( 250 kB) [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 95563 02233 ns [ 0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.008443] Console: colour dummy device 80x30 [ 0.013038] console [tty0] enabled [ 0.016581] bootconsole [earlycon0] disabled Than it stops. I did all your options, and implement it in my u-boot-variables, giving all the same result. thx Lieven Baes aka yanu