2012/3/13 Chris Whittenburg <whittenb...@gmail.com>: > I'm booting an Overo using a 3.0.23 kernel built with a recipe very > similar to the linux_3.0.bb recipe for beagleboard. > I'm using the console-base-image for the fs.
Hi Chris, do you use openembedded-core and meta-gumstix [1], or another configuration? > It hangs right after "Freeing init memory: 212K". > Then after about 30 seconds, I get "NET: Registered protocol family 10". > Then after another 7 minutes, I get "udevd[75]: starting version 181". > Then, nothing else-- but I haven't waited hours. The overo kernel I currently use works fine (3.0.17 from meta-gumstix). But for the first boot of a fresh rootfs the machine takes a long time (to create gtk-icon-cache or whatnot). To be honest if I boot any xserver image the boot process will go on for 30 minutes without any message. > The heartbeat LED is still blinking, so it's not totally dead. The blue led should indicate if there is any device activity. > Is this related to recent discussions about init scripts not getting run? My guess: It is because of postinstall scripts that need to be run on the machine at the first boot, can't tell if the init .rc files get "converted" at the first start too. > I did a similar experiment a couple weeks ago, I think with the 3.0.17 > kernel, building on another host machine and it worked fine. > > Thanks for any pointers. Or is there more debugging I can turn on? > > Regards, > Chris > > _______________________________________________ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel [1 meta-gumstix] http://gitorious.org/schnitzeltony-oe-meta/meta-gumstix?page=1 -- Regards Samuel _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
