Additional information I unintentionally left out, and be VERY CAREFUL with using he -rf flags with rm. Make sure you're removing the correct directory. This can completely hose your Linux rootfs if you're not absolutely sure what you're doing. This is also partly why I traverse into a new mount when working with system files. So I don't accidentally modify anything on the live system . . .
root@beaglebone:~/a# cd .. root@beaglebone:~# umount /root/a root@beaglebone:~# rm -rf a/ On Tue, Feb 14, 2017 at 8:03 PM, William Hermans <[email protected]> wrote: > By the way, DR. Molloy seems to be a good guy, and has a lot of useful > information. But much of that information is dated, and wont work with > current images. > What this boils down to is that if you're not an expert, or at least > proficient with Linux. You're very likely to run into many problems. It may > be best just to pose your questions here on the groups. Robert knows all > the details of the images, and often times I can at least help pick up his > slack. As well as I probably have a lot of hands on experience with most of > the peripheral modules, on current Linux image. > > On Tue, Feb 14, 2017 at 7:58 PM, William Hermans <[email protected]> > wrote: > >> >> >> On Tue, Feb 14, 2017 at 7:02 PM, mzimmers <[email protected]> wrote: >> >>> >>> William: I do in fact own a debug cable. I'll try plugging it in and see >>> if I can see anything. I've never worked with boot arguments; can you tell >>> me where they're kept? >>> >>> mz >>> >> >> root@beaglebone:~# lsblk >> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >> mmcblk1boot0 179:16 0 2M 1 disk >> mmcblk1boot1 179:24 0 2M 1 disk >> mmcblk0 179:0 0 14.7G 0 disk >> `-mmcblk0p1 179:1 0 1.7G 0 part / >> mmcblk1 179:8 0 3.6G 0 disk >> `-mmcblk1p1 179:9 0 3.6G 0 part >> >> root@beaglebone:~# mkdir a >> >> root@beaglebone:~# mount /dev/mmcblk1p1 /root/a/ >> >> root@beaglebone:~# cd a/ >> >> root@beaglebone:~/a# nano boot/uEnv.txt >> >> You're looking for( Whichever line has this and is not commented out) -> >> cmdline=coherent_pool=1M >> quiet >> >> Remove the "quiet" off the end, then save / exit the file then reboot - >> From the emmc of course. Observe the serial debug output. Also, at least >> one person I can remember reported issues with booting without the quiet >> option. So perhaps you may want to put it back after you're done getting >> your verbose information ? Up to you. >> >> >> >> >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORp58WZHoTqW%2BJy2v_HQEvGGam9b3RKqDqhQV1Fd-A%2BQnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
