On Apr 30, 2014 8:21 AM, "Doug" <[email protected]> wrote: > > Robert, > > I don't think you get my point or maybe I am not understanding the BBB evolution. We have a large number of individuals who have already purchased rev B boards. They will not have any updated eMMC code. What is there is there. On the other hand some will be purchasing the Rev C which will be available in a few weeks. > > If there is a fix we can do in Arch Linux that will universally fix our boot issue for any circumstance of eMMC state, Rev B, C without touching eMMC then I am all for it. If not then getting eMMC out of the way is the best choice.
Once you get a serial adapter on the board, shoot us a printenv pastebin > > BTW we would be using Debian but it clearly does not work for our application. Besides periodic crashes we had problems with USB audio. Runnng Archlinux solved all those problems. Laughs not a problem, Arch is using my kernel patchset anyways that I use as beta for Ubuntu and debian, just with a custom config > > > -- > 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]. > 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]. For more options, visit https://groups.google.com/d/optout.
