<zmatt>
oh you're talking about the kernel, I wasn't. there's no (visible) crash here, but it seems the watchdog gets enabled and eventually expires, causing a system reset
<zmatt>
I was talking about the crash log in your paste when using the u-boot from SD card (with S2 button)
<argonautx>
at data abort, I pushed the S2 button, while reconnecting the device with the power source (usb-plug)
<zmatt>
you mean the data abort was the first message after reconnecting power?
<argonautx>
so I pushed the S2 button only one time
<argonautx>
yes
<zmatt>
how bizarre... does that happen every time?
m-atoms has quit [Quit: Leaving]
<argonautx>
I just reproduced it, it seems so, after releasing the button there's a much faster reset loop
<zmatt>
??
<zmatt>
the S2 button should have no relevance once power is applied
<zmatt>
it's sampled at the moment of power-on (20ms after the power led turns on) and shouldn't have any impact otherwise
<zmatt>
(it decides whether the bootloader on eMMC is bypassed and this decision will apply until the next time the device is powered off and on again)
<zmatt>
can you share a paste of what you're seeing?
<zmatt>
okay so your earlier paste was in fact interrupted by pressing a key, u-boot seems to be working fine
<zmatt>
well
<zmatt>
sort of
<zmatt>
at least it seems to be going through the steps of booting a kernel
<zmatt>
but that crash log looks like one produced by u-boot, not one produced by the kernel (despite being after printing "Starting kernel ...")
<zmatt>
so I'm not sure what's going on, but this looks to me like both your u-boot and your kernel are broken, possibly misbuilt
<argonautx>
I attached a TFT as well, and there is neighter anything to see,
<zmatt>
no, nor would there be any expectation of that
<argonautx>
so the kernel crashes relendlessly, without any trace
<zmatt>
when using the u-boot on eMMC it seems to start the kernel but crash afterwards (evidently before it can initialize the serial console), while the u-boot you put on SD card seems to crash in the process of transferring control to the kernel
<zmatt>
so yeah, your yocto system is broken quite badly
<argonautx>
okay, thank you so far, then this it's the yocto depatement I have to address
<zmatt>
indeed. there's probably a #yocto channel you can try for help
<argonautx>
Im on it ;-)
<argonautx>
thank you
argonautx has quit [Ping timeout: 265 seconds]
thinkfat_ has joined #beagle
thinkfat has quit [Ping timeout: 245 seconds]
<set_>
If I wanted to run a .sh script that seems to need to be altered via ' sudo ', what method would I use to change it to debian instead of root? For instance, chown or another tool?
<set_>
chgrp?
vagrantc has quit [Quit: leaving]
<set_>
Anyway...I tried. Let us see!
<set_>
I guess this log file is all I have now. Boo!
<set_>
I need flight! Flying Blues as far as the eye can see...
<flatwhatson>
set_: you need to learn a little about unix permissions. when you "ls -l /path/to/script.sh" it will list owner & group names, and the read/write/execute (rwx) permission for owner/group/others in that order
<set_>
Right!
<set_>
ls -l !
<set_>
I remember...
<set_>
I should check first to figure out what is what and then proceed. Thank you.
<flatwhatson>
no worries. basically with this your objective to give yourself write permission, either as owner/group/other. you could change the ownership (chown), group (chgrp) and/or permissions (chmod)
<set_>
Gotcha. Okay. Thank you.
<set_>
chown, chgrp, and chmod. Got it.
<set_>
I used chown user:user file.sh to change ownership.
<set_>
Now...off to look up ls -l on the file.
<set_>
The first 'user' was my debian user and then the second 'user' was the group.
<set_>
Thank you.
<set_>
Pray for rain!
vd44 has quit [Ping timeout: 256 seconds]
akaWolf has quit [Ping timeout: 246 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
flatwhatson has quit [Read error: Connection reset by peer]
flatwhatson has joined #beagle
akaWolf has joined #beagle
ikarso has joined #beagle
rob_w has joined #beagle
giort has joined #beagle
giort has quit [Quit: giort]
Shadyman has quit [Quit: Leaving.]
otisolsen70 has joined #beagle
agentnocent has joined #beagle
agentnocent has quit [Client Quit]
argonautx has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
florian has joined #beagle
rob_w has quit [Quit: Leaving]
lucascastro has joined #beagle
Posterdati has joined #beagle
alan_o has quit [Ping timeout: 245 seconds]
alan_o has joined #beagle
vd has joined #beagle
florian has quit [Quit: Ex-Chat]
Guest15 has joined #beagle
set_ has quit [Ping timeout: 252 seconds]
sicelo has quit [Quit: Bye!]
<Guest15>
zmatt: still trying to debug my Qt problem and going over some old notes. "kmscube -a" should try all displays, but on my system (1.17.xxx sgx) it fails with "drmModeGetResources failed: Invalid argument". However, if I specify the card it works. Any useful clues there?
sicelo has joined #beagle
sicelo has joined #beagle
sicelo has quit [Changing host]
robert___ has joined #beagle
akaWolf1 has joined #beagle
GenTooMan has quit [*.net *.split]
akaWolf has quit [*.net *.split]
tbr has quit [*.net *.split]
CrazyEddy has quit [*.net *.split]
Daulity has quit [*.net *.split]
buckket has quit [*.net *.split]
akaWolf1 is now known as akaWolf
tbr has joined #beagle
CrazyEddy has joined #beagle
buckket has joined #beagle
GenTooMan has joined #beagle
lucascastro has quit [Read error: Connection reset by peer]
lucascastro has joined #beagle
troth has quit [Ping timeout: 265 seconds]
troth has joined #beagle
bldr_ has joined #beagle
linkliu62 has joined #beagle
v3r3mitz has joined #beagle
djinni has quit [Ping timeout: 265 seconds]
charlie5 has quit [Ping timeout: 265 seconds]
linkliu61 has quit [Ping timeout: 265 seconds]
bldr has quit [Ping timeout: 265 seconds]
Posterdati has quit [Ping timeout: 265 seconds]
xet7 has quit [Ping timeout: 265 seconds]
kveremitz has quit [Read error: Connection reset by peer]
akaWolf has quit [Ping timeout: 265 seconds]
v3r3mitz is now known as kveremitz
akaWolf has joined #beagle
xet7 has joined #beagle
Posterdati has joined #beagle
djinni has joined #beagle
giort has joined #beagle
giort has quit [Quit: giort]
vagrantc has joined #beagle
GenTooMan has quit [Quit: Leaving]
GenTooMan has joined #beagle
russ has quit [Ping timeout: 252 seconds]
russ has joined #beagle
buzzmarshall has joined #beagle
russ has quit [Ping timeout: 252 seconds]
<Guest15>
zmatt: scratch that. On debian 9 it must be that the gpu is on card 0. However, I did get Qt to work eventually.
russ has joined #beagle
kveremitz has quit [Ping timeout: 252 seconds]
vd has quit [Ping timeout: 256 seconds]
vd has joined #beagle
kveremitz has joined #beagle
otisolsen70 has quit [Quit: Leaving]
Shadyman has joined #beagle
argonautx has quit [Quit: Leaving]
set_ has joined #beagle
<set_>
I was studying a .bin file the other day w/ xxd...
<set_>
What should I use to understand it more? I used -g4 for 32 bit. This mildly worked.
<set_>
I mean...if I am using it on a...oh.
<set_>
I was using a 64-bit computer. Forget it.
<set_>
I sftp'd the file over to the BBB and forgot.
<set_>
Blah.
<set_>
bbl!
set_ has quit [Quit: I thought I saw a puddy-cat...]