Really appreciate you answer... my beaglebone now boots 1:30 faster. Did 
you figure out the course in the initrd?

On Tuesday, October 17, 2017 at 4:59:34 PM UTC+2, RobertCNelson wrote:
>
> On Tue, Oct 17, 2017 at 9:45 AM, Robert Nelson <[email protected] 
> <javascript:>> wrote: 
> > On Tue, Oct 17, 2017 at 9:11 AM, Robert Nelson <[email protected] 
> <javascript:>> wrote: 
> >> Hi Alexander, 
> >> 
> >> On Tue, Oct 17, 2017 at 7:53 AM, Alexander Rössler 
> >> <[email protected] <javascript:>> wrote: 
> >>> I found a workaround for the problem. 
> >>> 
> >>> The problems seems to be related to the images I built with the 
> >>> setup_sdcard script. I used the Debian Stretch console image builder 
> 9.2 
> >>> with the following command: 
> >>> 
> >>>> ./setup_sdcard.sh --dtb beaglebone --enable-cape-universal 
> >>>> --enable-uboot-cape-overlays --boot_label SandyBox --enable-systemd 
> >>>> --hostname sandybox --img-4gb test.img 
> >>> 
> >>> 
> >>> With the prebuilt image, everything works as expected. For me this 
> >>> solution is okay. 
> >>> 
> >>> My best guess is that it has to do with the boot_label, but I have no 
> clue 
> >>> why it should only cause trouble with the RT kernels. 
> >> 
> >> It also could be the "--enable-systemd" that was only for the old 
> >> "wheezy", since jessie systemd has been the default and the flag my 
> >> change something else.. 
> >> 
> >> if [ "x${enable_systemd}" = "xenabled" ] ; then 
> >>        cmdline="${cmdline} init=/lib/systemd/systemd" 
> >> fi 
> > 
> > Nope, that didn't make a difference: 
> > 
> > debian@sandybox:~$ uname -r 
> > 4.9.56-bone-rt-r7 
> > 
> > debian@sandybox:~$ cat /proc/cmdline 
> > console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> > net.ifnames=0 quiet init=/lib/systemd/systemd cape_universal=enable 
> > 
> > 
> > [    4.573940] ALSA device list: 
> > [    4.573948]   #0: TI BeagleBone Black 
> > [    4.575942] Freeing unused kernel memory: 1024K 
> > [   37.414498] EXT4-fs (mmcblk0p1): mounted filesystem with ordered 
> > data mode. Opts: (null) 
> > [   37.991016] ip_tables: (C) 2000-2006 Netfilter Core Team 
> > 
> > debian@sandybox:~$ cat /proc/cmdline 
> > console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> > net.ifnames=0 quiet cape_universal=enable 
> > 
> > [    4.573685] ALSA device list: 
> > [    4.573870]   #0: TI BeagleBone Black 
> > [    4.575851] Freeing unused kernel memory: 1024K 
> > [   34.504317] EXT4-fs (mmcblk0p1): mounted filesystem with ordered 
> > data mode. Opts: (null) 
> > [   35.085202] ip_tables: (C) 2000-2006 Netfilter Core Team 
>
> Bingo, it's the initrd.img..  This is only really needed for 3.8.13, 
> "kernel overlays" (which are now, not recommended).. 
>
> [    4.133706] PM: Hibernation image not present or could not be loaded. 
> [    4.133987] ALSA device list: 
> [    4.133997]   #0: TI BeagleBone Black 
> [    4.147398] EXT4-fs (mmcblk0p1): mounted filesystem with ordered 
> data mode. Opts: (null) 
> [    4.147467] VFS: Mounted root (ext4 filesystem) readonly on device 
> 179:1. 
>
> So double check: 
>
> cat /proc/cmdline 
>
> that's using, root=/dev/mmcblk* 
>
> and that /etc/fstab 
>
> has "/dev/mmcblk*" 
>
> (aka no UUID) 
>
> Then your safe to do: 
>
> sudo rm /boot/initrd.img-4.* 
>
> I'll keep testing, as something in the initrd is blocking the RT kernel.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/88ecb2de-3c62-4a02-91ea-ae83b1f53088%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to