On Wed, Jan 15, 2014 at 11:22 AM, Louis McCarthy <compeo...@gmail.com> wrote: > I am awaiting approval in the bug tracker, but I saw your comment related to > Wicd/Connman. If I remember correctly, there were issues with multiple > connections (wired and wireless) and DHCP (only assigned an IP to the first > adapter) with connman. Not sure if those were resolved.
Sorry about that, Louis. You should be active in the bug tracker now. > > Louis > > On Wednesday, January 15, 2014 9:23:59 AM UTC-6, RobertCNelson wrote: >> >> On Wed, Jan 15, 2014 at 9:05 AM, Louis McCarthy <comp...@gmail.com> wrote: >> > Thanks for all of your hard work Robert! >> > >> > Not sure if this is really a "bug" or more of a optimization. >> > >> > I downloaded and installed (via Win32 Disk Imager) the eMMC Flasher to a >> > 4 >> > Gb Kingston card. When I booted the new card on a BBB A5A, it loaded all >> > the >> > way into the GUI, performed the rsync, and then the lights went solid. >> > >> > My question is, is it necessary to boot the flasher all the way into the >> > GUI? It may shave a couple minutes off of the "flash" time by limiting >> > the >> > run level. >> >> Well, I guess we could get a little more creative with the image. >> I've kept to really simple... Right now the only difference between >> the dd/microSD image with the dd/flasher is one file in the boot >> partition.. >> >> /boot/uboot/flash-eMMC.txt >> >> >> https://github.com/beagleboard/image-builder/blob/master/scripts_device/boot/am335x_evm.sh#L56 >> >> Otherwise the biggest cpu hog was actually the screensaver. (xorg/lxde >> wasn't too resource intensive..) >> >> Which i've now disabled by default: >> >> >> https://github.com/beagleboard/image-builder/commit/6fe60d9a2f28d8f9f28747fd05f3cb0c96ef61ed >> >> So when i push out new image this week, it should shave a few more >> minutes.. (even without that change it's still not the 45 minutes it >> took Angstrom.. ;) ) >> >> > Another interesting note, is that once the rsync is done and the lights >> > all >> > go solid, the GUI is still responsive and usable. I guess I was assuming >> > that it would go to a halt state. Once again, not a problem, just a >> > comment. >> >> Do we want it to "halt" ? I wish we could "eject" the microSD, as if >> we halt, the user is just probably going to hit the power button and >> the flash starts all over.. >> >> Regards, >> >> -- >> Robert Nelson >> http://www.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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
