Actually, you can press and hold the boot button too, to load the bootloaders from the sdcard. You can try that short term but long term you'll want to deal with it how I explained above.
On Mon, Jun 13, 2016 at 7:48 PM, William Hermans <[email protected]> wrote: > When I've tried to use the 4.4.X bone kernels it actually just won't boot >> into Linux at all, the LEDs don't even turn on... No idea what's up with >> that. >> > > It depends. How old is the Linux on the eMMC ? Older bootloaders will > cause the board to lock up in u-boot. In order to get around this you need > to either install a newer image on the eMMC, or backup MLO + u-boot.img to > some place safe, then completely remove them from the eMMC. > > On Mon, Jun 13, 2016 at 6:44 PM, <[email protected]> wrote: > >> When I've tried to use the 4.4.X bone kernels it actually just won't boot >> into Linux at all, the LEDs don't even turn on... No idea what's up with >> that. >> >> I can stick with Wheezy and 3.8.X but I'd really love to know what is >> causing this and how I can fix it. Never like being in the dark about >> hardware I rely on. >> >> On Monday, June 13, 2016 at 6:38:18 PM UTC-7, William Hermans wrote: >>> >>> Forgot to add . . . >>>> >>>> $ uname -r >>>> 4.4.9-bone-rt-r10 >>>> >>> >>> D'oh ! That's not very useful . . . >>> >>> $ sudo lsb_release -a >>> No LSB modules are available. >>> Distributor ID: Debian >>> Description: Debian GNU/Linux 8.4 (jessie) >>> Release: 8.4 >>> Codename: *jessie* >>> >>> >>> On Mon, Jun 13, 2016 at 6:33 PM, William Hermans <[email protected]> >>> wrote: >>> >>>> Forgot to add . . . >>>> >>>> $ uname -r >>>> 4.4.9-bone-rt-r10 >>>> >>>> Also keep in mind if you retrograde kernels, you'll have to install the >>>> proper device tree compiler, and recompile all your device tree overlays >>>> against the proper version for 3.8.x >>>> >>>> >>>> On Mon, Jun 13, 2016 at 6:31 PM, William Hermans <[email protected]> >>>> wrote: >>>> >>>>> No capemgr isn't the problem. It's either a missing kernel config >>>>> option( by comparison ), or the configs are different. However . . . >>>>> >>>>> $ apt-cache search linux-image |grep 3.8 >>>>> linux-image-3.8.13-bone65 - Linux kernel, version 3.8.13-bone65 >>>>> linux-image-3.8.13-bone66 - Linux kernel, version 3.8.13-bone66 >>>>> linux-image-3.8.13-bone67 - Linux kernel, version 3.8.13-bone67 >>>>> linux-image-3.8.13-bone68 - Linux kernel, version 3.8.13-bone68 >>>>> linux-image-3.8.13-bone69 - Linux kernel, version 3.8.13-bone69 >>>>> linux-image-3.8.13-bone70 - Linux kernel, version 3.8.13-bone70 >>>>> linux-image-3.8.13-bone71 - Linux kernel, version 3.8.13-bone71 >>>>> linux-image-3.8.13-bone72 - Linux kernel, version 3.8.13-bone72 >>>>> linux-image-3.8.13-bone73 - Linux kernel, version 3.8.13-bone73 >>>>> linux-image-3.8.13-bone74 - Linux kernel, version 3.8.13-bone74 >>>>> linux-image-3.8.13-bone76 - Linux kernel, version 3.8.13-bone76 >>>>> linux-image-3.8.13-bone77 - Linux kernel, version 3.8.13-bone77 >>>>> linux-image-3.8.13-bone78 - Linux kernel, version 3.8.13-bone78 >>>>> linux-image-3.8.13-bone79 - Linux kernel, version 3.8.13-bone79 >>>>> linux-image-3.8.13-xenomai-r67 - Linux kernel, version >>>>> 3.8.13-xenomai-r67 >>>>> linux-image-3.8.13-xenomai-r69 - Linux kernel, version >>>>> 3.8.13-xenomai-r69 >>>>> linux-image-3.8.13-xenomai-r70 - Linux kernel, version >>>>> 3.8.13-xenomai-r70 >>>>> linux-image-3.8.13-xenomai-r71 - Linux kernel, version >>>>> 3.8.13-xenomai-r71 >>>>> linux-image-3.8.13-xenomai-r72 - Linux kernel, version >>>>> 3.8.13-xenomai-r72 >>>>> linux-image-3.8.13-xenomai-r76 - Linux kernel, version >>>>> 3.8.13-xenomai-r76 >>>>> linux-image-3.8.13-xenomai-r78 - Linux kernel, version >>>>> 3.8.13-xenomai-r78 >>>>> >>>>> >>>>> On Mon, Jun 13, 2016 at 4:56 PM, <[email protected]> wrote: >>>>> >>>>>> Loaded up my Wheezy image and installed the 4.1.26-ti-rt-r63 kernel. >>>>>> Broken just like the Jessie install. Great data point, Jessie isn't the >>>>>> problem. Also tried the 4.1.18-bone-rt-r20 kernel. Same thing. >>>>>> >>>>>> I'm starting to wonder if there's not something going on with the way >>>>>> the new cape manager works? In order to get the UART up I have to pull >>>>>> and >>>>>> install the new overlays with git. Perhaps the new overlay doesn't jump >>>>>> in >>>>>> quite as fast as the old? >>>>>> >>>>>> -- >>>>>> 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/bb30a4a8-333f-4077-b5c3-2e2b0e661fd9%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/beagleboard/bb30a4a8-333f-4077-b5c3-2e2b0e661fd9%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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/166c5e67-f96f-49d3-b761-60d002e02bf3%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/166c5e67-f96f-49d3-b761-60d002e02bf3%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORp%3DNS855ShxoOcVpyOP96%3DV_QivaGhsDN7cishooQ4j3g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
