On Fri, Apr 12, 2019 at 7:36 AM Rob J. Epping <epp...@renf.us> wrote:
> On April 11, 2019 3:06:20 PM UTC, Lieven Baes <y...@waime.eu> wrote: > >On Thu, Apr 11, 2019 at 4:13 PM Martin Michlmayr <t...@cyrius.com> > >wrote: > [snip] > >[ 0.008443] Console: colour dummy device 80x30 > >[ 0.013038] console [tty0] enabled > console is opened on dummy "screen" device > >[ 0.016581] bootconsole [earlycon0] disabled > and serial console is stopped. > >Than it stops. > > try the following : > setenv bootargs $(bootargs_console) earlyprintk=serial,ttyS0,115200 > console=ttyS0,115200 > usb start > ext2load usb 1:1 0x00800000 /uImage > ext2load usb 1:1 0x01100000 /uInitrd > bootm 0x00800000 0x01100000 > That was 'the trick' to continue booting the kernel. Also this worked well, without 'earlyprintk': setenv bootargs $(bootargs_console) console=ttyS0,115200 But why do I have to place this 'console=ttyS0,115200' an extra time when it was already set in: setenv bootargs_console 'console=ttyS0,115200 root=/dev/sda2 rootdelay=10' setenv bootcmd_mmc 'usb start; ext2load usb 1:1 0x00800000 /uImage; ext2load usb 1:1 0x01100000 /uInitrd' setenv bootcmd 'setenv bootargs $(bootargs_console) console=ttyS0,115200; run bootcmd_mmc; bootm 0x00800000 0x01100000' Big thanks to all you guys for doing this great work, every day. This guruplug is serving me for almost 10 years, that's nice. Martin, do you need to change this on your guruplugs-webpage by adding that console-argument? https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ <https://www.cyrius.com/debian/kirkwood/sheevaplug/install/> thx Lieven Baes aka yanu
