We'd need to know exactly what steps you did in order to get an idea of what is going wrong. I've followed those same exact steps personally( many many times ), and have never had a problem other than doing something wrong on my end.
As for the long boot times, if and when it actually boots correctly. This is possibly related to the onboard ethernet. I believe you either need a connection manager( I do not use one myself - but I've seen Robert recommend this ), or set the oneboard ethernet to a static IP. Something about the kernel taking up to 2 minutes to find a dhcp lease, or something of that nature. *shrug* On Thu, Jan 8, 2015 at 5:54 AM, Robert Kuhn <rob...@ku.hn> wrote: > Hi, > > boot takes much longer with 69 kernel: > > [ 0.767408] pinctrl-single 44e10800.pinmux: pin 44e10854 already > requested by 44e10800.pinmux; cannot claim for gpio-leds.8 > [ 0.779110] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status > -22 > [ 0.786380] pinctrl-single 44e10800.pinmux: could not request pin 21 on > device pinctrl-single > Loading, please wait... > systemd-fsck[206]: BEAGLEBONE: clean, 35288/236176 files, 147950/943872 > blocks > [ 64.384719] libphy: PHY 4a101000.mdio:01 not found > [ 64.389761] net eth0: phy 4a101000.mdio:01 not found on slave 1 > > > What happens here? Also I get a kernel oops when shutting down: > > Detaching DM devices. > [ 111.285531] (NULL device *): gadget not registered. > [ 111.291442] Power down. > [ 111.296139] Kernel panic - not syncing: Attempted to kill init! > exitcode=0x00000000 > [ 111.296139] > [ 111.305707] [<c001125d>] (unwind_backtrace+0x1/0x98) from [<c049bfd3>] > (panic+0x5b/0x160) > > All would be much simpler for me if > CONFIG_DRM_LOAD_EDID_FIRMWARE=y > would be enabled in kernel. So if any developer is reading this - please > enable this in the next kernel please. It helps a lot to deal with some DVI > monitors. > > Thanks! > > > Am Donnerstag, 8. Januar 2015 11:55:45 UTC+1 schrieb Robert Kuhn: > >> >> Hi, >> >> thanks: >> Linux beaglebone 3.8.13-bone69 #1 SMP Thu Jan 8 09:16:29 CET 2015 armv7l >> GNU/Linux >> >> Just to be sure: I untar'd 3.8.13-bone69-modules.tar.gz and >> copied 3.8.13-bone69.zImage to /boot/uboot/zImage. Is this enough? Whats >> about 3.8.13-bone69-firmware.tar.gz and 3.8.13-bone69-dtbs.tar.gz? Do I >> need them? >> >> Thanks! >> >> >> Am Mittwoch, 7. Januar 2015 16:56:05 UTC+1 schrieb William Hermans: >>> >>> https://eewiki.net/display/linuxonarm/BeagleBone+Black >>> >>> On Wed, Jan 7, 2015 at 7:28 AM, Robert Kuhn <rob...@ku.hn> wrote: >>> >>>> Hi, >>>> >>>> I use the Bone Black with the current Debian firmware (2014-05-14). I >>>> need to recompile the kernel to activate a specific feature. Whats the best >>>> way to do this? Is there a description for this? >>>> >>>> Thanks! >>>> >>>> -- >>>> 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...@googlegroups.com. >>>> 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. > 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. For more options, visit https://groups.google.com/d/optout.
