ikarso has quit [Quit: Connection closed for inactivity]
buzzmarshall has joined #beagle
Shadyman has joined #beagle
thinkfat has joined #beagle
thinkfat_ has quit [Ping timeout: 265 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
Guest3540 has joined #beagle
Guest3540 has quit [Quit: Client closed]
tacokoneko has quit [Quit: Leaving]
samael has joined #beagle
samael has quit [Ping timeout: 255 seconds]
bzyx has quit [Read error: Connection reset by peer]
bzyx has joined #beagle
samael has joined #beagle
samael has quit [Ping timeout: 268 seconds]
samael has joined #beagle
samael has quit [Ping timeout: 240 seconds]
samael has joined #beagle
JanL has joined #beagle
JanL has quit [Client Quit]
<jduchniewicz>
tacokoneko looks awesome! I am working on GPGPU with SGX's on Beagles (right now BBB) Might eventually use GPU for other libraries acceleration
<jduchniewicz>
zmatt: how do you make such nice flame graphs?
<jduchniewicz>
how much work did this entail tacokoneko?
<jduchniewicz>
most importantly how much head-scratching and cooperation with Imagination's engineers?
tacokoneko has quit [Remote host closed the connection]
starblue has quit [Quit: WeeChat 2.3]
tacokoneko has joined #beagle
starblue has joined #beagle
<zmatt>
jduchniewicz: and I've gotten the gpu working with qt5-eglfs a while ago, it was a bit tedious but you certainly won't need "cooperation with Imagination's engineers" (not that you'd be able to get any, I'd imagine)
lucas_ has joined #beagle
lucascastro has quit [Ping timeout: 255 seconds]
<tacokoneko>
I saw your comment on my video, thank you for the pointer, I had incorrectly assumed this whole time that there was no audio controller based on some others' misleading posts. I have updated the project to support audio :)
<zmatt>
tacokoneko: it just doesn't have an audio DAC, hence no analog audio output
vagrantc has joined #beagle
<zmatt>
but it has two digital audio interfaces, as well as an on-board 24.576 MHz oscillator for use as audio master clock
<tacokoneko>
I see; for complete understanding, this is mono only right? it appears to me to be mono only, but I don't want to assume that
<zmatt>
what? no
<zmatt>
it's most definitely stereo
<zmatt>
unless the HDMI framer somehow got misconfigured or something
Guest3540 has joined #beagle
Guest3540 has quit [Ping timeout: 246 seconds]
lucas_ has quit [Quit: Leaving]
lucascastro has joined #beagle
florian has quit [Quit: Ex-Chat]
charlie5 has quit [Quit: Leaving.]
charlie5 has joined #beagle
samael has quit [Ping timeout: 240 seconds]
<tacokoneko>
ok, I see that it is supposed to be stereo in the documentation, but aplay and speaker-test mix channels into mono, which plays on both speakers. I can only find one playback device, davinci-mcasp.0-i2s-hifi i2s-hifi-0. If I use --disable-channels with aplay, mono test files play on both speakers, but for stereo test files I see "Channels count non available" . The only reference to stereo I can find is in amixer contents, which
<zmatt>
no the alsa driver supports up to 16 channels just fine, there must be some kind of weird configuration problem
<zmatt>
hdmi audio is probably not used often, so it's quite possible some breakage has gone unnoticed
<tacokoneko>
I tested with two TVs that have speakers connected to HDMI input, this behavior was consistent between them. The test files I am using are wav pcm 48khz stereo and mono, and on a different GNU/Linux system with working stereo the stereo file plays with left channel in left speaker and right in right speaker, so I know the test files work
<zmatt>
in fact, I get an error if I try to provide only 1 channel (with -c 1)
<zmatt>
which makes sense since the interface is i2s which doesn't support mono, only stereo
charlie5 has quit [Ping timeout: 255 seconds]
charlie5 has joined #beagle
calculu5 has joined #beagle
calculus has quit [Ping timeout: 258 seconds]
vagrantc has quit [Quit: leaving]
llim has joined #beagle
samnob_ has joined #beagle
samnob has quit [Ping timeout: 276 seconds]
<tacokoneko>
thanks very much for the advice, by following your suggestion of testing various aplay parameters and looking for configuration problems, I discovered that the /etc/asound.conf included with the image shows signs of hand-editing.
<tacokoneko>
looking closer, I decided to remove everything in that file after line 53, since it looked unnecessary
<tacokoneko>
as far as i can tell, doing this has completely resolved my problem. all stereo ALSA applications and stereo test files in aplay now automatically play in left and right channels correctly.
llim has quit [Quit: Client closed]
<tacokoneko>
I imagine that portion of the file is necessary for some other projects, but I think for mine it is preferable not to have it so I will add this modification to my setup scripts.
<zmatt>
interesting, it's creating mono devices on top of the stereo hardware... which itself doesn't seem too problematic, but the fact that it makes it the default device is really weird
<zmatt>
still, you can just override the output device to hw: like I did
<zmatt>
but I agree this is a weird default config
<zmatt>
tacokoneko: btw instead of removing the last few lines you may as well remove/rename the entire config file
<zmatt>
the default will do what you want
LetoThe2nd has quit [Quit: Connection closed for inactivity]
charlie5 has quit [Ping timeout: 252 seconds]
<tacokoneko>
ok I will do that and test the results
charlie5 has joined #beagle
LetoThe2nd has joined #beagle
akaWolf has quit [Ping timeout: 268 seconds]
akaWolf has joined #beagle
mattb0ne has joined #beagle
<mattb0ne>
my splitter is not working
<mattb0ne>
=(
<mattb0ne>
works when only one of the ports are in use
<mattb0ne>
that like defeats the whole purpose of having the damn thing
xet7 has joined #beagle
calculu5 has quit [Ping timeout: 252 seconds]
calculus has joined #beagle
<mattb0ne>
zmatt: how do I add beaglebone.local to linux so it get recognized
<zmatt>
mattb0ne: "works when only one of the ports are in use" .. what on earth did you buy?
<zmatt>
and I'm not sure what you mean by that question... you mean how to ensure a linux system can resolve .local names? I'd expect that to work out of the box in basically any distro, but the specific requirement is that nss-mdns (Avahi's plugin for the Name Service Switch) is installed; on debian-based distros (including ubuntu) the package name is "libnss-mdns"
<mattb0ne>
yeah evidently I bought the wrong thing
<mattb0ne>
on my laptop I have the ethernet port connected to the laptop and I use the wifi card on the laptop for internet so it was not a problem
<mattb0ne>
for the computer I had the one port and no wifi
<zmatt>
ah I see so the beaglebone wasn't connected to your school network
<mattb0ne>
right it shared my laptops
<mattb0ne>
connection
<mattb0ne>
so I am finishing it up and trying to move the project to the lab computer
<mattb0ne>
dropping the internet needs and just plugging the black into the ethernet port
<mattb0ne>
the ssh takes a while to come up I get a lot of service not known errors and then eventually it will go through
<mattb0ne>
but my program wount work giving that mess in the pastebin
<mattb0ne>
i may wipe and try to make it exactly like my lap top and put on Mint LMDE4 instead of linux mint
<zmatt>
I'm still a little confused about your situation... you're allowed to mess that much with a lab computer?
<mattb0ne>
it is brand new and dedicated to run this application.
<zmatt>
ok, what about the networking situation? has connecting the beaglebone directly to the network been OK'd? is there no spare ethernet port available to avoid the need for an extra switch? alternatively, if you want the beaglebone just connected to the PC and nothing else, why not connect it via usb?
<zmatt>
(and thus avoid the need to mess with the ethernet situation)
<zmatt>
I think you used an ethernet connection to your PC because that makes sharing your PC's internet connection to the beaglebone hassle-free?
<mattb0ne>
unfortunately no extra ethernet port
<zmatt>
but if you're not using internet sharing then there's probably on benefit over using ethernet instead of usb
<mattb0ne>
yes
<mattb0ne>
i think you made me update somethign on the computer side but it seems to have trouble just connecting to the beagelbone
<zmatt>
so I don't understand why you're connecting it to the PC via ethernet, since it can't share internet to the beaglebone anyway (since hooking up the beaglebone via ethernet to the PC makes the PC not have internet)
<zmatt>
just leave the PC connected to the network and connect the beaglebone via usb
<mattb0ne>
that will force me to change my code though
<zmatt>
why?
<mattb0ne>
well I use sockets and stuff
<mattb0ne>
tcp protocol
<zmatt>
yes, and... ?
<mattb0ne>
isnt that not compatible with USB
<zmatt>
??!??
<mattb0ne>
i dunno
<mattb0ne>
different cord different code?
<mattb0ne>
lol
<zmatt>
the beaglebone shows up as usb networking interface
<mattb0ne>
ok need to see if I have a cord long enough
<zmatt>
you can connect to "beaglebone.local" regardless of what specific type of network connection is used
<mattb0ne>
they give you a real stubby thing
<mattb0ne>
in the box
<zmatt>
but you also left a bunch of questions unanswered
<zmatt>
23:19 <@zmatt> ok, what about the networking situation? has connecting the beaglebone directly to the network been OK'd? is there no spare ethernet port available to avoid the need for an extra switch?
<mattb0ne>
the computer only has one port
<zmatt>
I'm not talking about he computer
<zmatt>
*the
<zmatt>
I'm talking about what the computer is plugging into (presumably a wall socket?)
<mattb0ne>
the beaglebone has not been cleared to access the network
<mattb0ne>
I was hoping to just plug directly to the computer to avoid all that
<mattb0ne>
there is also only one port activated in the room
<mattb0ne>
we have more but they charge per port and all that
<zmatt>
charge? what? I thought this was a school environment?
<mattb0ne>
yeah but they charge each lab for stuff
<mattb0ne>
it is weird here
<zmatt>
o.O
<mattb0ne>
so we get an IT bill
<zmatt>
what the actual fuck
<mattb0ne>
I do not make the rules
<zmatt>
okay, so forget about connecting the beaglebone via ethernet at all, just connect it to the PC via usb
<mattb0ne>
ok
<mattb0ne>
need to go to the store and get a longer micro usb
<zmatt>
mini usb you mean
<mattb0ne>
yeah mini
<mattb0ne>
why would the ssh behave so differently from computer to computer though
<zmatt>
or, I guess you could also share the ethernet connection between the PC and the beaglebone by using a router... the need to do this is absolutely asinine, but if you have only one ethernet port yet seemingly free reign to connect a device to the network (given that your lab PC is unmanaged), it may as well be a router
<zmatt>
and I don't know what you mean by that
<zmatt>
your pastebin earlier is also not useful btw since I don't know what you're trying to connect to
<zmatt>
(that information is nowhere in the stack trace)
<mattb0ne>
well I can ssh
<mattb0ne>
from the lab computer to bbb
<mattb0ne>
but the program that I run sends commands from the PC to the beaglebone break
<zmatt>
what are you connecting to?
<zmatt>
in your code
<mattb0ne>
over a socket I send a command
<zmatt>
what hostname
<mattb0ne>
00:00:00:00
<zmatt>
what's not a hostname
<zmatt>
*that
otisolsen70 has quit [Quit: Leaving]
<zmatt>
also why do I see something called "tcp_echo_client", which is just the name of an example (which was a client for an example service which literally did nothing except echo data back to the client, hence "echo server" and "echo client" ... since presumably your code is supposed to do more than just echo things, the continuing to use the name "echo client" makes no sense)
<mattb0ne>
beaglebone.local
zjason` has joined #beagle
<mattb0ne>
is what I am trying to connect to
<mattb0ne>
in my code
<mattb0ne>
as the server and the port is 7777
<mattb0ne>
brb
<zmatt>
can I maybe just see a bit of code?
<zmatt>
since if you can ssh to "beaglebone.local" then any other application can connect to that as well
zjason has quit [Ping timeout: 268 seconds]
<set_>
Hello...what is the equivalent command of echo in nodejs? I am switching some source in the cloud9-examples to handle the javascript/nodejs and I am dealing w/ user LEDs right now.
<zmatt>
console.log
<set_>
So, I can...
<set_>
So, I can say this: console.log(/sys/class/leds/beaglebone:green:usr0/ > trigger)
<zmatt>
no
<set_>
Okay.
<set_>
No issue. Off to read more.
<zmatt>
I assumed you meant echo in the sense of log output
<set_>
Oh.
<set_>
No...not this time. I am reading, writing, and using file descriptors.
<zmatt>
does the bonescript library not have stuff for configuring leds?
<zmatt>
otherwise fs.writeFileSync is the function you're looking for
<set_>
fs.writeFileSync.
<set_>
Okay.
calculus has quit [Ping timeout: 245 seconds]
<set_>
I have been readin' an older book on 'javascript' but it is really just about bonescript.
<set_>
So, off to the interwebs!
calculus has joined #beagle
<set_>
So, I am at nodejs.org/docs/../../../ where it shows the fs.writeFileSync.
<set_>
I will try one usr led at a time first before 'conquering' the entire five.
<mattb0ne>
zmatt didnt you have me create a file where i write the ip address of the BBB and beaglebone.local or something like that
<zmatt>
no
<mattb0ne>
it is confusing since if I ssh I am connected and it should know where to go
<mattb0ne>
server config or something
<zmatt>
no
<zmatt>
btw are you now connected via usb or still via ethernet?
<mattb0ne>
lol
<zmatt>
oh right you didn't have a long enough usb cable
<mattb0ne>
I need to order a cord I do not have a cord long enough
<mattb0ne>
will be a few days amazon destroyed all electronic stores
<mattb0ne>
basically foreced to order over the internet now
<zmatt>
can you try "getent ahosts beaglebone.local"
<mattb0ne>
ok
LetoThe2nd has quit [Quit: Connection closed for inactivity]
<mattb0ne>
just gives me the cursor
<mattb0ne>
back
<mattb0ne>
no output
<zmatt>
uhh so the hostname in fact doesn't resolve, but then it makes no sense that you'd be able to ssh to it
<mattb0ne>
I can only sporadically connect
<mattb0ne>
so now I cannot again
<mattb0ne>
so I am going to reboot
<mattb0ne>
and reboot the beagle
<mattb0ne>
like it never failed when I was connected to the laptop
<mattb0ne>
but I could of sworn i added a file
<zmatt>
your laptop was sharing internet access
<mattb0ne>
or edited something when I first made the switch
<mattb0ne>
oh
<mattb0ne>
so that is not it
<zmatt>
i.e. your laptop was acting as a router
<mattb0ne>
i do see activation of network failed
<mattb0ne>
in the corder
<mattb0ne>
*corner
<mattb0ne>
when I try to ssh
<zmatt>
now a router *should'nt* be needed to connect to a device using a .local address
starblue has quit [Ping timeout: 240 seconds]
<mattb0ne>
not sure how to get the log file
av500 has quit [Remote host closed the connection]
<zmatt>
but connman might be acting dumb
av500 has joined #beagle
<mattb0ne>
i am not using conman
<mattb0ne>
well it is not installed
<zmatt>
on the beaglebone? what did you replace it with?
<mattb0ne>
oh I thought you were talking about the PC
<zmatt>
no
<mattb0ne>
i have not touched anything on the beagle
starblue has joined #beagle
<zmatt>
so, I don't know why you're having trouble connecting to it, my guess would be connman is to blame... the solution is to either put the PC and the beaglebone on the same network (via a switch or a router, whether the former will work in your strange networking situation is unclear) or use usb to connect to the beaglebone