**** BEGIN LOGGING AT Sun Dec 19 02:59:56 2021 Dec 19 03:00:35 if you aren't already doing so, try powering on with the S2 button held down (the button closest to the SD card slot), you can let go of the button once any leds turn on Dec 19 03:00:55 to bypass the bootloader on eMMC in favor of the one on SD card Dec 19 03:00:57 ok let me try it again Dec 19 03:01:25 in general, if not installing to eMMC I'd generally recommend wiping eMMC (or at least wiping the bootloader from eMMC) Dec 19 03:02:08 since the bbb will prefer to load u-boot from eMMC over loading it from SD card, which can cause problems if trying to boot a system from SD card that's wildly different from the one on eMMC Dec 19 03:06:10 ok, I will research Dec 19 03:09:15 I tried to wipe out the eMMC (and in fact tried to install there) Dec 19 03:09:21 but ended with write errors, let me try again and show you Dec 19 03:15:12 zmatt: this is what I see when trying to wipe out the eMMC https://paste.ircnow.org/4pmj0labct6nw1mv05yf Dec 19 03:16:01 yeah no idea what's going, clearly something is going horribly wrong Dec 19 03:16:08 *what's going on Dec 19 03:16:30 I'll ask on #openbsd as well Dec 19 03:16:34 this happened also on the other device Dec 19 03:17:13 and you were getting this on both eMMC and SD card right? Dec 19 03:18:08 if it ony happened to one of them I'd suspect the storage medium is broken due to wear-out, but if the problems affects both I have no idea Dec 19 03:50:08 I blame the chip shortages Dec 19 04:05:47 zmatt: this only occurs on the eMMC Dec 19 04:05:51 on the SD it seems to work ok Dec 19 04:05:59 it affects both eMMCs Dec 19 04:06:02 on both boards Dec 19 09:23:03 jrmu: well then it's probably not due to the eMMC chips themselves :P Dec 19 09:46:33 zmatt: I got it working with another microSD card Dec 19 09:47:33 as for eMMC, still not working, so i suspect maybe a software issue Dec 19 14:09:17 Hi, where is it written which dtb files are loaded from /boot/dtbs/4.19.94-ti-r42 ? Dec 19 14:10:02 nmingotti: u-boot decides which base dtb and which overlays to load based on the board identification eeprom and the settings in /boot/uEnv.txt Dec 19 14:12:29 i see Dec 19 14:15:02 is there a way i can see this list of files, or, in some way to dump the current configuration. In my note about FreeBSD i see I was using the 'ofwdump' command. Is there something similar in Debian ? Dec 19 14:16:14 you can find the name of the base dtb in /proc/device-tree/chosen/base_dtb Dec 19 14:16:39 and the names of the files in /proc/device-tree/chosen/overlays/ (except "name") are the names of the overlays (without ".dtbo" suffix) Dec 19 14:19:41 thank you zmatt I will look well in those directories, last question Dec 19 15:27:24 nmingotti: last question? Dec 19 15:32:52 yes, zmatt,  sorry i was trying to collect idea to say it well Dec 19 15:33:59 so, I suppose to try to modify things i need to write another overlay, better than touching existing working ones Dec 19 15:34:51 if i write my little overlay and compile to a dtbo file, say it is called test-1.dtbo Dec 19 15:36:20 do i put in in uEnv : uboot_overlay_addr4=/lib/firmware/test-1.dtbo ? Dec 19 15:37:08 making so, i am i sure that "test-1" will be loaded after all the other default overlays ? Dec 19 17:10:20 to share internet over ethernet in windows you just need to share the host computers connection to the internet? Dec 19 22:55:00 are there on sale 46 pin headers with numbers printed ? Dec 19 22:55:54 Also, how do you make a stable connection to beaglebon headers ? hot glue ? other ? **** ENDING LOGGING AT Mon Dec 20 02:59:56 2021