Yeah, we dropped using uuid in v4.4.x+ as it broke and we fixed the mmc
kernel names.
3.8.13 needs it, see the uuid var in /boot/uENv.txt
Regards,
On Aug 3, 2017 5:19 PM, "Doreen Yen" <d...@sentons.com> wrote:
Dear Robert C. Nelson,
Thanks for the /boot/uEvn.txt comment out enable_uboot_overlays=1
advice which has gotten further, but there is still a problem as you see
below:
I re-flashed from microSD, edited the /boot/uEvn.txt then
sudo apt update
sudo apt-get install linux-image-3.8.13-bone86
sudo reboot
Truly I had ejected the microSD before S3 power button, because
running from eMMC so ALERT! /dev/mmcblk1p1 makes sense.
Why is it stuck in initramfs ? It should not look for filesystem on
microSD ?
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fb82000, end 8ffff697 ... OK
Loading Device Tree to 8fb78000, end 8fb81605 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.475233] omap2_mbox_probe: platform not supported
[ 0.632876] tps65217-bl tps65217-bl: failed to find backlight node
[ 0.632889] tps65217-bl tps65217-bl: DT parse failed.
[ 0.700804] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.737910] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.775018] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.812127] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.827442] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN
conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.837102] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 0.843877] bone-capemgr bone_capemgr.9: loader: failed to load slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.860236] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
failed
[ 0.921758] pinctrl-single 44e10800.pinmux: pin 44e10854 already
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 0.933508] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
-22
[ 0.940822] pinctrl-single 44e10800.pinmux: could not request pin 21 on
device pinctrl-single
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk1p1 does not exist. Dropping to a shell!
B▒t-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
On Thu, Aug 3, 2017 at 2:46 PM, Robert Nelson <robertcnel...@gmail.com>
wrote:
> Well to run 3.8.13, you need to disable u-boot overlays in /boot/uEvn.txt
> (master enable)
>
> Regards,
>
>
> On Aug 3, 2017 3:20 PM, <d...@sentons.com> wrote:
>
> * My second and brand new Beaglebone Black was flashed to eMMC and worked
> fine with *
> BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-07-14-2gb.img
> *following the excellent instructions of*
>
> http://derekmolloy.ie/write-a-new-image-to-the-beaglebone-bl
> ack/#prettyPhoto
>
> *Next installed:* sudo apt install linux-headers-3.8.13-bone86
>
> *because we have a driver that needs those 3.8.13 headers.*
>
> *We have a script that calls* update_kernel.sh --bone-kernel --stable
>
> *Afterwards the reboot will not start the kernel. My first board used
> 3.8.13-bone84 alright but is running from microSD not eMMC.*
>
> *What is causing kernel start failure and how to fix it? Should I just
> replace the `uname -r` in the driver Makefile with explicit 3.8.13-bone86
> ???*
>
> *Console output for second Beaglebone Black has:*
>
>
> Running uname_boot ...
>
> loading /boot/vmlinuz-3.8.13-bone86 ...
>
> 5594568 bytes read in 373 ms (14.3 MiB/s)
>
> uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
>
> loading /boot/dtbs/3.8.13-bone86/am335x-boneblack.dtb ...
>
> 26118 bytes read in 31 ms (822.3 KiB/s)
>
> uboot_overlays: [fdt_buffer=0x60000] ...
>
> uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo ...
>
> 378 bytes read in 340 ms (1000 Bytes/s)
>
> fdt_overlay_apply(): FDT_ERR_NOTFOUND
>
> uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
>
> 1105 bytes read in 238 ms (3.9 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
>
> 4169 bytes read in 134 ms (30.3 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
>
> 695 bytes read in 350 ms (1000 Bytes/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
> ...
>
> 2402 bytes read in 130 ms (17.6 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> uboot_overlays: loading /lib/firmware/univ-bbb-EVA-00A0.dtbo ...
>
> 54858 bytes read in 209 ms (255.9 KiB/s)
>
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>
> fdt_overlay_apply(): FDT_ERR_BADMAGIC
>
> loading /boot/initrd.img-3.8.13-bone86 ...
>
> 4705709 bytes read in 320 ms (14 MiB/s)
>
> debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M
> net.ifnames=0 quiet cape_universal=enable] ...
>
> debug: [bootz 0x82000000 0x88080000:47cdad 88000000] ...
>
> ERROR: Did not find a cmdline Flattened Device Tree
>
> Could not find a valid device tree
>
>
> and finally is stuck at boot prompt,
>
>
> Config file not found
>
> starting USB...
>
> USB0: Port not available.
>
> link up on port 0, speed 100, full duplex
>
> BOOTP broadcast 1
>
> DHCP client bound to address 10.150.100.52 (37 ms)
>
> Using cpsw device
>
> TFTP from server 0.0.0.0; our IP address is 10.150.100.52; sending through
> gateway 10.150.100.1
>
> Filename 'boot.scr.uimg'.
>
> Load address: 0x80000000
>
> Loading: T T T T T T T T T T T T T T T T T T T T
>
> Retry count exceeded; starting again
>
> link up on port 0, speed 100, full duplex
>
> BOOTP broadcast 1
>
> DHCP client bound to address 10.150.100.52 (40 ms)
>
> Using cpsw device
>
> TFTP from server 0.0.0.0; our IP address is 10.150.100.52; sending through
> gateway 10.150.100.1
>
> Filename 'boot.scr.uimg'.
>
> Load address: 0x82000000
>
> Loading: T T T T T T T T T T T T T T T T T T T T
>
> Retry count exceeded; starting again
>
> =>
>
> *Would really enjoy running from eMMC rather than microSD. While waiting
> for reply, I will try changing the driver Makefile to explicitly plug in
> 3.8.13-bone86, which means I have to reflash since otherwise I am stuck at
> boot prompt.*
>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/beagleboard/153ddcdd-47eb-4b99-a47a-97d846652a08%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/153ddcdd-47eb-4b99-a47a-97d846652a08%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhwn%2Bs2z4VrhZhvd%2BD6P8NjCDwM1S7X-46Dpp4s5Su4bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
