<set_>
GenTooMan: What are you working on these days?
<GenTooMan>
for some reason I've been working on crossfire cleaning up a 20 year old game LOL.
<set_>
Nice.
<set_>
I am not sure what that exactly entails but crossfire sounds interesting w/ it being attached to cleaning.
<set_>
You mean, you got fired, and are bow hunting an old puzzle?
<set_>
Anyway, like most things, this is most likely none of my business.
<set_>
I just thought I could get you to joke around a bit.
<set_>
Someone bamboozled my speaker on the ole desktop.
<set_>
I get no sound out of it now.
<set_>
Boo!
<GenTooMan>
hmm likely it's not being driven could be a loose wire.
<set_>
oh.
<set_>
I would use a none-solid strand. Them things break easily.
<set_>
I got one stuck in the MotorCape once.
<set_>
Hey GenTooMan: Do you recommend any specific organization/business for embedded training in Linux?
<set_>
I am asking b/c I found bootlin, doulos, and toradex but those businesses are out of state or country.
<set_>
I contacted duolos once or twice. It seems their five day exercises are a bit pricey for a single individual like me. So, I figured, why not reach out to the ole .org? BBB!
<set_>
When in the hell are you guys going to teach some and get paid?
<set_>
It is not about the money. I know but snookie, come on! Some people would like to learn more, me-me-me, and it is not easy w/out tracks of depedence.
<GenTooMan>
Sadly for the software in the beagle bone series it has always been a moving target and yocto confusion didn't help things. I'm still trying to figure out how to setup yocto.
<GenTooMan>
Actually beagle org. I have a beagle board (original) which is 2007.
<GenTooMan>
The software went sideways 2 years after it was released.
<set_>
Oh.
<set_>
Hmm.
<GenTooMan>
It's frustrating for everyone just some are more adept at finding what they need to know. No one is perfect.
<set_>
yea. I guess. Things change.
<set_>
I mean...look at me. I can already copy and paste. Who'd a thought that one up?
<set_>
Slow 'mo here only knows so much.
<set_>
Oh! And now! There are all these new, easy-to-handle libs. that may be coming.
<set_>
That will be neat but it takes away from my Linux Admin. 'background' and usage. Right?
<set_>
esp. w/ that nice PRU lib. people are working on.
<set_>
It is not an easy field, embedded soft/hardware, to grasp. I say that b/c you have security, BSPs if you go big, and then updating breaks in the system.
<set_>
Oh and yocto. Do not get me started. I jump in and out of that fluidly.
<set_>
If I was to grab three to 10 people for training, it would make it easier on me and financial burdens.
<set_>
Sharing is caring.
<GenTooMan>
some people shouldn't be allowed to touch anything embedded namely people who only think Javascript. :D
<set_>
Ha.
<set_>
JavaScript is so Google.
<set_>
Ha.
<set_>
Did Ubuntu and Google partner up to make the next RISC-V processor board a reality?
<set_>
B/c that is some big targets making some nice hardware.
<set_>
Sorry. It was SiFive HiFive.
<set_>
But...the gpio issue is still a mystery to me.
<set_>
That is a big thing that has changed recently w/ the newer kernels.
<set_>
GPIO is so popular.
<set_>
I see one libgpiod lib. available to handle the confusion so far.
<set_>
config_gpio_aggregator=y
<set_>
So, it seems once this is enabled, you can use libgpiod and then sysfs.
<set_>
But first, the device tree needs to be officially notified.
<set_>
Oh!
<set_>
GenTooMan: I just got my hands on a 12v photocell and electronic gate mechanism that I 'may' be able to work on.
<set_>
Starting small never hurt too bad.
<set_>
Chains, motors, photocells, and gates, both types, ha.
<set_>
Now, if my boss will allow me to fix it, i can and will. First, spray the hornets down w/ killer and then proceed.
<set_>
I may use the BBGG.
<set_>
I will have to imitate their controller board or make one.
<set_>
MotorCape!
<set_>
It can be handled via 12v battery or 24v battery.
<set_>
Anyway...I am learning about python i/o and other python stuff from this book, "The Python Stadard Library by Example."
<GenTooMan>
well the unfortunate reality is that people who only focus on one thing are only good at one thing. They tend to be purposefully ignorant of things.
<set_>
Right. That is true. Some people have many years of experience in dealing w/ many things deal w/ many facets of things...while specifics on only a few subjects highlight those subjects.
<set_>
GenTooMan: IT is like a block vs a sphere. IT is not so easy to compare I guess.
<set_>
Remember those toys! One would put a block in the block (square) hole while the sphere would be placed in the circular hole?
<set_>
Anyway...I would jam the sphere in the square hole and quit.
<set_>
ha.
<set_>
if one more elif statement finds its way onto my BBB w/ errors, I am going to loss it.
starblue has joined #beagle
starblue3 has quit [Ping timeout: 248 seconds]
<GenTooMan>
lose loss or loose :D
<set_>
All, none, and both/neither. Argh.
<set_>
lose
thinkfat has joined #beagle
<GenTooMan>
lesdyxic?
thinkfat_ has quit [Ping timeout: 258 seconds]
<set_>
Nope.
<set_>
Just tired of the grass growing into my mind-yiand-yiand-yiand.
<set_>
GenTooMan: Did you like the wammy bar effect?
<set_>
30 minutes!
<GenTooMan>
set_, good way to detune your guitar in a few minutes
<set_>
Yep...stretching those strings will break 'em or detune the tuneage.
<GenTooMan>
that's why they created a DSP to create a wammy bar effect
<set_>
Ha. DSP. Ha. Oh!
<GenTooMan>
a DSP program I should say.
<set_>
I found some neat books on DSPs, java, and some others on computer music theory.
<set_>
Some which were free, hard to believe, and some that cost me only $23.00 about.
<set_>
Let me see if I can find them.
<GenTooMan>
I use to have a program called sapphire that would play midi sequences in 3d positions so that it would sound like it was in a specific location pretty interesting abuse of I/r^2 law mixed with reflections. Required a 3d model of the environment.
<set_>
Check it out, musicandcomputersbook.com, one day. It is a bit visual, interactive, and silly.
<set_>
The guy puts in jokes every so often.
<set_>
I think that fellow put in jythonmusic.com as a partial work(s).
<set_>
instead of .com, I think it was .me.
<set_>
I tried some of the java JVM 8 source he proposed.
<set_>
it is neat. I can even exchange out some of the backends that java has for midi and things but use an updated, 'nicer' versioning of another backend.
<set_>
The source this fellow put together kind of went aloof b/c of java updates like everything else that is put down in 'writing'.
<set_>
Fade an LED?
<set_>
On, barely on, off, bright, dim, off.
<set_>
elif
<set_>
Ha.
<set_>
All jokes aside, GenTooMan, I guess it is time I retire for the night. It is late, I hate my job, and I may retire from that too. Who knows?
GenTooMan has quit [Ping timeout: 245 seconds]
GenTooMan has joined #beagle
GenTooMan has quit [Excess Flood]
GenTooMan has joined #beagle
mattb0ne has quit [Ping timeout: 248 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
m-atoms has quit [Ping timeout: 268 seconds]
rob_w has joined #beagle
LetoThe2nd has joined #beagle
neudeep has joined #beagle
neudeep92 has joined #beagle
neudeep has quit [Ping timeout: 246 seconds]
Shadyman has quit [Quit: Leaving.]
florian has joined #beagle
neudeep92 has quit [Quit: Client closed]
neudeep92 has joined #beagle
Stanto has quit [Read error: Connection reset by peer]
neudeep92 has quit [Quit: Client closed]
Guest27 has joined #beagle
<Guest27>
Hi
Guest27 has quit [Client Quit]
neudeep92 has joined #beagle
Posterdati has quit [Ping timeout: 268 seconds]
Posterdati has joined #beagle
xet7 has joined #beagle
xet7 has quit [Remote host closed the connection]
av500 has quit [Read error: No route to host]
av500 has joined #beagle
neudeep92 has quit [Quit: Client closed]
neudeep92 has joined #beagle
Guest-eMMC has joined #beagle
rob_w has quit [Ping timeout: 268 seconds]
rob_w has joined #beagle
Guest-eMMC has quit [Quit: Client closed]
neudeep92 has quit [Quit: Client closed]
Guest40 has joined #beagle
<Guest40>
hello
<Guest40>
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
<Guest40>
could you help me to solve this
<zmatt>
uhh what on earth did you do to your system?
<Guest40>
its on beaglebone black
<zmatt>
sudo works fine out of the box, that error message implies you've broken things pretty badly
<Guest40>
sudo is not working in BBB
<zmatt>
if there's nothing important on your beaglebone I suggest just reflashing it (to the latest image) to fix things
<Guest40>
after reflashing also i got same problem
<zmatt>
what image did you flash?
<Guest40>
debian
<Guest40>
kernel 5.4.106
<Guest40>
and u-boot is 2019.v4
<zmatt>
there's no released image with that kernel
<Guest40>
so could you tell me? what should i have to do?
<Guest40>
for solving this problem
<zmatt>
I'm trying to think what exactly you've done that could begin to explain your claimed observations, since none of it makes much sense
rob_w has joined #beagle
<Guest40>
see i dont know why sudo is not working and even i downlode new kernel source code and u-boot source code compiled it and flashed it more than 2-3 time still that problem is not solving
<zmatt>
okay so you have been doing weird things to your system
<zmatt>
kernel and u-boot are completely irrelevant for sudo
<Guest40>
okk
<zmatt>
you must have done something after flashing that broke sudo
<zmatt>
that's still the only explanation that makes sense, since I know for a fact that sudo works fine on that image
<Guest40>
so i have to dawnlode new img file and flash it again on BBB
<Guest40>
.img
<zmatt>
that's probably the easiest way to undo whatever you did to your system
<Guest40>
could you send best version of .img file so i can flash it again on my BBB
<zmatt>
btw, the easiest way to make a flasher sd card is by downloading a flasher image ("AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher" under Flasher Debian images on https://beagleboard.org/latest-images ), that way you don't have to mess with /boot/uEnv.txt to make it a flasher
<tiget_xyz>
Hi Good Morning! I have a program calls Bluetooth driver. If it runs with command line and terminates by Ctrl-C. hcitool lescan still works. If the program is started through a script and stopped using pkill in the script, then hcitool lescan fails with error: [Set scan parameters failed: Input/output error ]
<tiget_xyz>
It seems to me that pkill doesn't clean every thing or the handle to the BLE driver is still open, not closed after the program is killed by pkill.
<zmatt>
could be either the program's fault or the driver's fault, hard to say without more context
<zmatt>
certainly, if the program cleans stuff up on SIGINT (ctrl-C) but not SIGTERM (kill), that would be the program's fault
<zmatt>
btw afaik hcitool is deprecated
<zmatt>
yeah, the following tools are deprecated: hciattach hciconfig hcitool hcidump rfcomm sdptool ciptool gatttool
<tiget_xyz>
Yeah, I was aware that hcitool is deprecate. I didn't write the program.
<zmatt>
"All the tools using raw socket shall be considered deprecated, these tools may interfere with the so called Management interface since they can alter the controller state in a way that other applications cannot detect. Note that for the most part bluetoothctl will be able to do pretty much everything you want and more, for those operations not supported over D-Bus that are usually at HCI level you ...
<zmatt>
...may want to use btmgmt"
<zmatt>
someone in a stackoverflow thread mentioned they had that same error with hcitool while using bluetoothctl to scan worked fine
<tiget_xyz>
with hcitool, hciconfig hci0 reset, will fix the driver fault, which may caused by the program
<tiget_xyz>
Let me try bluetoothctl
<zmatt>
it might not be a "fault", it may be that the application has configured the interface in a way that interferes with being able to scan as before
<zmatt>
that's just a guess though
<zmatt>
especially since you said that the problem doesn't happen if you exit the program with ctrl-C, that suggests to me that it performs some explicit cleanup in that case
<tiget_xyz>
I guess the handle open to the driver is not closed gracefully.
<zmatt>
that guess is almost certainly wrong
<zmatt>
there's no way for an application to leave a driver handle open after exit, other than by passing the file descriptor to another program that will keep it open
<zmatt>
the problem is more likely some form of persistent configuration, state, or mode of operation
<zmatt>
examining whatever cleanup the program presumably performs on ctrl-C will likely provide insight into what's going on
neudeep92 has quit [Quit: Client closed]
neudeep92 has joined #beagle
<tiget_xyz>
How to examine what cleanup is done on Ctl-C?
<zmatt>
find the cleanup handling code in the program's source code?
<tiget_xyz>
I don't have the source code at the moment. It is not my program. I will do later
<tiget_xyz>
I found that using " kill -INT pid " is the same as Ctrl-C to terminate the program. After that hcitool lescan works.
<tiget_xyz>
If using "kill -9 " or "kill -SIGTERM", or "killall ", hcitool lescan needs a reset
<zmatt>
correct, you can send a SIGINT (similar to ctrl-C) by passing the -INT flag to kill or pkill
<zmatt>
presumably the program intercepts SIGINT and upon receiving it performs cleanup and then exits, but fails to perform similar cleanup upon receiving SIGTERM (the default signal for kill and pkill)
<tiget_xyz>
But the program can include code to do the same clean-up after receiving SIGTERM, right?
<zmatt>
yep, it can intercept SIGTERM in exactly the same way as SIGINT
<tiget_xyz>
I think that will resolve the issue through adding application code