> > *Hey William,* > > *Yes, that's all very clear in hindsight. I do wish that I had looked up > how to turn it off properly before I made the mistake. * > > *Thank you for the clarification on the kernel. It's hard to find > up-to-date info.* > > *-Nate* >
Ok, so now that we have that clear ;) hehe. You have to treat this like you would any other computer. Except perhaps the beaglebone is more fragile. Due to hardware costs, and the fact that the software, that is specific to the beaglebone is written by various members of the community. Who by the way do not get paid to do that. But you would shut down the BBB the same way you would shutdown your laptop from the command line. $ sudo shutdown now -h *or* $ sudo halt There is also a button closest to the ethernet jack which triggers an NMI through the PMIC, which should signal the processor to cleaning shut down linux. The button furthest from the ethernet jack on the same side ( left ) if I remember correctly is the reset button. So make sure not to press that while the OS is running either. The effect would be similar to pulling the power. On Wed, Apr 20, 2016 at 9:38 PM, Nathan Wheeler <wheelersou...@gmail.com> wrote: > Hey William, > > Yes, that's all very clear in hindsight. I do wish that I had looked up > how to turn it off properly before I made the mistake. > > Thank you for the clarification on the kernel. It's hard to find > up-to-date info. > > -Nate > > On Wednesday, April 20, 2016 at 9:15:44 PM UTC-7, William Hermans wrote: >> >> So, question. If you removed the battery from your laptop, and then ran >> your laptop with no battery, an just yanked the power cord out of the wall >> to shut it down. What do you think would happen ? It's the same difference, >> except it would possibly take many more attempts at corrupting you laptop, >> before it did actually corrupt the file system. >> >> Also, it's running Debian wheezy with a 3.8.x kernel, not Angstrom. Just >> so you know. RevC's all came with a *bone-47* 3.8 kernel. >> >> On Wed, Apr 20, 2016 at 9:04 PM, Nathan Wheeler <wheele...@gmail.com> >> wrote: >> >>> Hey all, >>> >>> I did a search - maybe someone is better at it than I am and could help >>> connect me to an explanation/solution? Anyway, here's what has happened: >>> >>> I got my board in the mail yesterday and connected it to my new MacBook >>> Pro Retina (running OSX 10.11.3). I was able to ssh over USB after >>> installing the included drivers and write/run code on the board. I didn't >>> write anything special, just practiced loading a python example to the >>> board. >>> >>> I didn't know that pulling the USB cable without turning the board off >>> via the Power button could corrupt the eMMC onboard. I understand I should >>> have read the manual, but I think this information needs to be included on >>> any "quick start" info provided to beginners. (If they tell you how to turn >>> it on, shouldn't they tell you how to safely turn it off?) I have a lot of >>> experience with Arduino and mistakenly thought that I could unplug the >>> BeagleBone from power without any other shutdown steps. >>> >>> So now, the board powers on and the user LEDs flash, and the board shows >>> up as an external storage device on my laptop. But the IP address has >>> changed to 198.168.7.1, and any attempts to ssh either result in a timeout >>> or require password authentication. And the default passwords provided on >>> Adafruit and other places are not working. >>> >>> So, my questions are: >>> • How do I know if I've corrupted the data in the eMMC? Will the board >>> act normally but not connect? >>> • If I can't ssh via USB, will I be able to do so via ethernet, or >>> should I just start over/do a restore of Angstrom? >>> • Is Angstrom stiil the default distro, or are the boards shipping with >>> Debian now? >>> • Is this possibly an El Capitan issue? I read a little about that, but >>> I downloaded and installed a HoRNDIS version that was supposed to fix the >>> issue. >>> >>> Thanks for your help - I'm really looking forward to learning how to use >>> this board and become part of the community. I build interactive interfaces >>> for musical performance and am excited about the possibilities offered >>> here. >>> >>> - Nate >>> >>> -- >>> 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...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/bcdcae01-ee98-4900-b795-f5b372ded41f%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/bcdcae01-ee98-4900-b795-f5b372ded41f%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/7b283842-bf9c-4ef9-9793-c9639d13810f%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/7b283842-bf9c-4ef9-9793-c9639d13810f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrLNzJHdR3ah02jOPv0u5RH%3DtsXsjwXoqW_nHOcg2TKEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
