> > *f the "clone" didn't work on either Ubuntu or Windows I would have > assumed the initial boot was "self-modifying", and tried to figure out the > dpkg dselect stuff to create a "master list" to apt-get install all my > bits and pieces instead of setting up a master system and cloning it. But > I actually thought I was clever and done until I tried the BBB on Windows > 7.* >
What you did probably was clever. As mentioned above, the problem is Windows ability to deal with similar, but different drivers. We both know the hardware is the same, but Windows does not because they hardware is presented differently though software. To be clearer on how you have to deal with this situation. First, you may, or may not have to boot into safe mode in order to remove the existing driver. Passed that, if the Beaglebone is not plugged in, you will have to force hardware manager to show hidden( inactive ) devices, and then remove it. Once fully removed, you may even be required to install the drivers from beagleboard.org, and *THEN* also visit MS updates, and install their "special sauce" before the driver will work. Whatever happens, the whole process is very inconsistent, and largely Microsoft's fault, that could possibly be mitigated by keeping the drivers as consistent as well. So, this is why I say it is just easier to deal with this hardware from Linux. Because . . it really is. And yes, I do realize that some people can be really stubborn and refuse to use anything other than x.y.z. Be it OSX, Windows, or some flavor of Unix. On Sat, Dec 26, 2015 at 8:54 PM, Robert Nelson <[email protected]> wrote: > > On Dec 26, 2015 9:32 PM, "Wally Bkg" <[email protected]> wrote: > > > > > > Thanks for the reply, you are always concise and helpful. > > > > No I've never flashed the A5A 2GB eMMC, keeping the original Angstrom > as a "fallback", but I did do a lot of opkg stuff in an attempt to actually > use it, but kept getting tripped up by differences between Angstrom and > Ubuntu/Debian and the dearth up to date Angstrom docs and information -- if > an Adafruit tutorial didn't address it, I was pretty much stuck. I was > quick to try the BBB Debian images. > > > > So are you suggesting I download the latest 2GB Debian "flasher" image, > flash it, and then boot my SD card? > > > > Easy enough to do but, how does this explain the working on Ubuntu 15.10 > but not Windows 7 aspect of it? > > > > I'm thinking the old u-boot leaves the USB bus in a bad state, and we > don't properly re-init it from that state. > > Side note, I haven't tested the old angstrom u-boot with our now default > Debian image in probably 2 years.. > > Regards, > > -- > 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.
