On Friday, October 4, 2013 7:24:10 PM UTC-4, [email protected] wrote: > > Im glad to see you explanation, now is solved... a doubt is left: How > could the Sys Builder make image that boot always in eth0? might they use > eth0 or wifi... IMHO >
I'm afraid my knowledge pretty much ends at knowing WHAT the issue is and a generalized way to solve it - but not the specifics for your case. I only remember all of this because I ran across the same "issue" with running Ubuntu on virtual systems via Amazon EC2. I'd try to "clone" a working system to turn it into an EC2 image and when I booted a new copy[which received a new virtual ethernet card with a new MAC address] it would not work. I eventually figured out the specific steps to follow when creating an EC2 image to purge this information so they would work - but I honestly don't know what exactly the "process" should be when dealing with the BBB. At the moment I only have one BBB so it doesn't affect me. Sorry I couldn't be more help. :-( I just figured I'd try to explain it in some extra detail because it was quite frustrating/difficult to understand when I first encountered it[especially since this "feature" had not been in the previous version of Ubuntu I used at the time, so it initially felt like the new version of Ubuntu "broke" EC2]. -- 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/groups/opt_out.
