<zmatt>
jrmu: all beaglebones except the AI use the same SoC, and the same u-boot (which uses the eeprom to autodetect which board it is and load the appropriate DT to pass to the kernel)
<jrmu>
ok thanks zmatt
<zmatt>
some are more similar than others, in particular the blue is a bit more different than the others
<zmatt>
the green is just pretty much the black minus hdmi
<zmatt>
I don't know anything about openbsd, sorry
<zmatt>
install onto sd card? but aren't you booting from sd card?
<zmatt>
how would it install onto itself?
<zmatt>
anyway, there used to be someone here who's familiar with openbsd on beaglebones, but I haven't seen him in a long time
<jrmu>
yeah it can install onto itself
<jrmu>
afterbooting
<zmatt>
ok
<jrmu>
it worked on one device
<jrmu>
but for some reason this second beaglebone black won't work
<jrmu>
is there any command for me to boot from the microSD card? that's all I would need
<zmatt>
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
<zmatt>
to bypass the bootloader on eMMC in favor of the one on SD card
<jrmu>
ok let me try it again
<zmatt>
in general, if not installing to eMMC I'd generally recommend wiping eMMC (or at least wiping the bootloader from eMMC)
<zmatt>
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
vagrantc has quit [Quit: leaving]
<jrmu>
ok, I will research
<jrmu>
I tried to wipe out the eMMC (and in fact tried to install there)
<jrmu>
but ended with write errors, let me try again and show you
<zmatt>
yeah no idea what's going, clearly something is going horribly wrong
<zmatt>
*what's going on
<jrmu>
I'll ask on #openbsd as well
<jrmu>
this happened also on the other device
Shadyman has joined #beagle
<zmatt>
and you were getting this on both eMMC and SD card right?
<zmatt>
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
<Konsgn>
I blame the chip shortages
set_ has joined #beagle
<jrmu>
zmatt: this only occurs on the eMMC
<jrmu>
on the SD it seems to work ok
<jrmu>
it affects both eMMCs
<jrmu>
on both boards
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
Konsgn has quit [Quit: Leaving]
_outrageous has joined #beagle
outrageous has quit [Ping timeout: 256 seconds]
set_ has quit [Read error: Connection reset by peer]
set_ has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
lucascastro has quit [Remote host closed the connection]
lucascastro has joined #beagle
vd33 has quit [Ping timeout: 256 seconds]
<zmatt>
jrmu: well then it's probably not due to the eMMC chips themselves :P
<jrmu>
zmatt: I got it working with another microSD card
Shadyman has quit [Quit: Leaving.]
<jrmu>
as for eMMC, still not working, so i suspect maybe a software issue
rob_w has joined #beagle
Morshing has joined #beagle
set_ has quit [Ping timeout: 268 seconds]
Morshing has quit [Read error: Connection reset by peer]
set_ has joined #beagle
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
Morshing has joined #beagle
set_ has quit [Ping timeout: 268 seconds]
dinuxbg has quit [Ping timeout: 268 seconds]
Morshing has quit [Ping timeout: 252 seconds]
set_ has joined #beagle
dinuxbg has joined #beagle
Morshing has joined #beagle
ikarso has joined #beagle
set_ has quit [Ping timeout: 256 seconds]
nmingotti has joined #beagle
<nmingotti>
Hi, where is it written which dtb files are loaded from /boot/dtbs/4.19.94-ti-r42 ?
<zmatt>
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
<nmingotti>
i see
<nmingotti>
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 ?
<zmatt>
you can find the name of the base dtb in /proc/device-tree/chosen/base_dtb
<zmatt>
and the names of the files in /proc/device-tree/chosen/overlays/ (except "name") are the names of the overlays (without ".dtbo" suffix)
<nmingotti>
thank you zmatt I will look well in those directories, last question
dinuxbg has quit [Ping timeout: 268 seconds]
Morshing has quit [Remote host closed the connection]
set_ has joined #beagle
dinuxbg has joined #beagle
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
set_ has quit [Read error: Connection reset by peer]
set_ has joined #beagle
Morshing has joined #beagle
set_ has quit [Ping timeout: 268 seconds]
<zmatt>
nmingotti: last question?
<nmingotti>
yes, zmatt, sorry i was trying to collect idea to say it well
<nmingotti>
so, I suppose to try to modify things i need to write another overlay, better than touching existing working ones
<nmingotti>
if i write my little overlay and compile to a dtbo file, say it is called test-1.dtbo
<nmingotti>
do i put in in uEnv : uboot_overlay_addr4=/lib/firmware/test-1.dtbo ?
<nmingotti>
making so, i am i sure that "test-1" will be loaded after all the other default overlays ?
ikarso has quit [Quit: Connection closed for inactivity]
CoffeeBreakfast has joined #beagle
xet7 has quit [Quit: Leaving]
xet7 has joined #beagle
rob_w has quit [Quit: Leaving]
mattb0ne has joined #beagle
mattb0ne has quit [Ping timeout: 256 seconds]
mattb0ne has joined #beagle
<mattb0ne>
to share internet over ethernet in windows you just need to share the host computers connection to the internet?
mattb0ne has quit [Remote host closed the connection]
Morshing has quit [Remote host closed the connection]
set_ has joined #beagle
nmingotti has quit [Quit: Client closed]
mattb0ne has joined #beagle
mattb0ne has quit [Remote host closed the connection]
buzzmarshall has joined #beagle
zjason has quit [Read error: Connection reset by peer]
zjason has joined #beagle
Morshing has joined #beagle
set_ has quit [Ping timeout: 256 seconds]
set_ has joined #beagle
Morshing has quit [Ping timeout: 240 seconds]
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
mattb0ne has joined #beagle
vagrantc has joined #beagle
vagrantc has quit [Ping timeout: 240 seconds]
vagrantc has joined #beagle
nmingotti has joined #beagle
<nmingotti>
are there on sale 46 pin headers with numbers printed ?
<nmingotti>
Also, how do you make a stable connection to beaglebon headers ? hot glue ? other ?
_outrageous is now known as outrageous
outrageous has quit [Remote host closed the connection]