<set_>
So, why is it that the 5.10.x builds with all the sysfs gpio pins call the root:root user:group and root:gpio user:group when root has no root:gpio :group?
<set_>
I mean, it is or can be solved but I do not think it should be solved.
<set_>
I can see me jumping in the river again while going from rock to rock! Send rations!
Shadyman has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
xet7 has quit [Quit: Leaving]
xet7 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
libredev has quit [Ping timeout: 240 seconds]
DrPatater has quit [Quit: Explodes into a thousand pieces]
xet7 has quit [Remote host closed the connection]
libredev has joined #beagle
<set_>
Do not worry about the user:group issue...
<set_>
My PSU is busted.
<set_>
I have no basis on anything because of the PSU not allowing any amperage to level out the total wattage.
<set_>
So basically, I was running a motor on 12v at 0.7A and I can use it at 12v at 3A total (give or take)...
<set_>
8.4W is not collective for this motor to run.
<set_>
I put more voltage in the PSU via dial, the amperage goes lower, and the motor does not move like usual.
<set_>
hence, broken PSU...
<set_>
Lucky...yes. Thankful the machine still works...yes. Knowing I am still believing and living...priceless.
<set_>
Do not get a Hiltex 40531 10 A 30 V DC Digital Power Supply ever, i.e. even if it works. They do not sell them for now for a reason. Phew.
<set_>
Final breathing techniques! Sheesh. I am lucky-stucky over here.
DrPatater has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
<set_>
Remember, cheap does not mean charm. Some things were not meant to be purchased. Like the hair follicle renewal substances should stay out of every day purchases. Geaux BBB!
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #beagle
Shadyman has quit [Quit: Leaving.]
Stat_headcrabed has joined #beagle
<set_>
Now, the waiting game. Wait until the new PSU arrives and hope for miracles!
xet7 has joined #beagle
KREYREN_ has joined #beagle
KREYREN__ has quit [Ping timeout: 240 seconds]
<zmatt>
"chown root:gpio FILES" just means change ownership to root and change the group to gpio
<zmatt>
(it's shorthand for "chown root FILES" followed by "chgrp gpio FILES")
<zmatt>
changing the ownership is kinda redundant since they already were owned by root, so it's just equivalent to "chgrp gpio FILES"
Stat_headcrabed has quit [Quit: Stat_headcrabed]
<set_>
I understand.
<set_>
user:group
<set_>
Why is root my user to begin my day when I just installed the image?
<set_>
I thought it should be something like debian:gpio or something else...
<set_>
I can change each file that needs changing or use udev at /etc/udev/rules.d/.
libredev has quit [Ping timeout: 260 seconds]
<set_>
But...I just do not get why or for what reason it is being done this way.
<set_>
su - root will bring me to a root console. So, why the backlash on the debian user for beginnings?
<set_>
I mean...
<set_>
If it is for users that are determined to do wrong. Okay. No issue.
<set_>
I can try something or other...
<zmatt>
set_: there's no reason for sysfs files to be owned by debian
<set_>
Okay.
<zmatt>
user debian is a member of group gpio
<zmatt>
so giving rights to group gpio is sufficient
<set_>
Right. Oh.
<set_>
I use namei or at least I tried this command once or twice.
<zmatt>
wtf is namei
<set_>
So, with that command, I noticed what is listed as root and what is listed as debian all the way to root.
<set_>
it shows what user:group is listed down to root.
<zmatt>
ok, why do you care?
<set_>
So, namei -l /dev/bone/pwm/* will show that user:group and everything down to root from that file down to root.
<zmatt>
that's normal and expected yes
<set_>
Okay. So, some are user debian while others are listed as user root.
<zmatt>
why are you always messing with ownership and permissions? like they should almost always be correct by default
<set_>
B/c...something always stupid or monumentous happens in my life where what I purchase is garbage that makes me triple guess everything and everyone.
<zmatt>
unless you've been doing stuff as root inappropriately, or the occasional issue with udev rules in some new/testing images
<set_>
I got a regular 10-07-2023 image.
<set_>
Bullseye 5.10.x kernel.
<set_>
This time, it is what I think is a faulty PSU now.
<zmatt>
??
<set_>
Not you guys. But, I had to go through Venice and Hell to find out.
<zmatt>
what does a psu have to do with privileges?
<set_>
My motor needs to run, the PSU controls the driver, and I use the BBB for GPIO.
<set_>
Nothing.
<zmatt>
okay, again what does any of this have to do with privileges?
<zmatt>
if it doesn't have anything to do with privileges, why are you messing with them?
<set_>
The PSU, which is faulty, made me believe incorrect things.
<set_>
I made a mistake.
<set_>
Is root:gpio okay?
<zmatt>
for what?
<set_>
For using gpio without root or sudo usage...
<zmatt>
the udev rules on the 2023-10-07 bullseye IoT image look correct to me
<set_>
Okay.
<zmatt>
for gpio
<set_>
Just making sure. This is what I was unaware of currently. I should have checked before flipping Wilson over here...
<set_>
Sorry.
<set_>
So, root:gpio and debian:gpio work because of Udev?
<zmatt>
?
<set_>
So, root:gpio and debian:gpio work because of udev.
<set_>
Now, I have not clue why or for what reason.
<zmatt>
??? udev is responsible (among other things) for setting permissions of things based on rules
<set_>
But that file is misterious.
<set_>
I am glad you are still around.
<zmatt>
in particular, the 80-gpio-noroot.rules file is responsible for granting the group "gpio" access to sysfs gpio
<zmatt>
debian is a member of group gpio
<set_>
Oh! Right, I remember.
<set_>
So, my darn PSU. Sorry. I am off to cry some. See you later!
<zmatt>
you can use the "id" command to see all groups you're a member of
<set_>
I just type groups
<zmatt>
or that
<set_>
I have not used the id command before today.
<set_>
I will look into it.
<zmatt>
groups actually has nicer output for this purpose, didn't know it existed
<set_>
Anyway, thanks again. Gosh.
<set_>
Did you try namei yet?
<set_>
It damn near lists everything.
<set_>
Some person on Unix stack exchange taught me that one.
<set_>
So, it should really be called POSIX instead of Unix.
<zmatt>
yeah, seems a bit obscure but it has its uses... never heard of that one either. there's too many utils on a linux system ;P
<set_>
Aw!
<set_>
Tons.
<zmatt>
is namei a posix utility? I don't think it is
<zmatt>
it's part of util-linux
<set_>
Right.
<set_>
I was talking about the Unix name in front of Stack Exchange.
<set_>
They have people that hate me more than most. Sometimes, once in a blue moon, I get answered.
<set_>
Gollee.
<set_>
util-linux. Yeppers.
<zmatt>
most likely you're just asking vague/incomprehensible questions ;)
<set_>
As usual. Simplifying is my enemy.
<zmatt>
and that community is for unix-like operating systems.... POSIX is not a synonym for that
<set_>
Oh. But POSIX is over Unix and Linux, right?
<set_>
It is like the overseer.
<zmatt>
POSIX is an interoperability standard, it prescribes functions and commands that should exist and how they should behave, it doesn't care about the underlying architecture of the operating system
<set_>
Okay. Understood.
<set_>
I really need to stop asking why or why not when I can ask when, where, what, how, why, and do, and are, and who?
<set_>
You know. There is not limitation.
<set_>
Get this, sir.
<set_>
So, my BBAI-64 would not work. I blamed me, you, and everthing. Everyone was the culprit (including myself).
<set_>
So, my USB ports are labeled USB 3.0 Gen 1 and Gen 2. But, they are no blue.
<set_>
So, this made me think.
<set_>
Maybe the 3A is not available w/ my USB 3.0 ports.
<zmatt>
yeah people kinda stopped making usb3 ports blue I think, my laptop's USB ports aren't blue either
<set_>
And maybe my USB C...
<set_>
Hmm.
<set_>
Okay.
<set_>
Odd.
<set_>
They should be labeled.
<set_>
Have you tested the amperage out on your USB Ports?
<zmatt>
unless they actually are usb2 ports, it's possible I guess
<zmatt>
blue does not mean 3A anyway
<zmatt>
usb3 ports don't guarantee more than 900 mA if I remember correctly
<set_>
Hmm. I thought USB 3.0 Gen 1 and Gen 2 need to be blue to signify their A.
<zmatt>
no, blue is just used to mark usb3 ports and connectors
<set_>
Right.
<set_>
Blue is the marking of the connector.
<set_>
Which would cut down on people thinking of nothingness instead of knowning somethingness.
<set_>
I would rather use my BBAI-64 with a host that has a visually listed setting of a USB peripheral.
<zmatt>
specifically for Standard-A connectors/receptacles, since without color coding it's pretty much impossible to tell the difference between usb2 and usb3
<set_>
Right. except for A output.
<zmatt>
standard-B and micro-usb connectors look quite different for usb2 and usb3
<zmatt>
and they just stopped caring with type-C which makes everything look the same :P
<zmatt>
amperage has never been indicated visually
<set_>
But that is part of it.
<zmatt>
not really
<set_>
No issue.
<set_>
yea. Like, if I was going to draw with a red crayon and it said blue on it.
<set_>
Not matter what is says, it is a red crayon that I was about to use.
<set_>
And if it was not red, I would think something is wrong with me.
<set_>
"Did I just go blind or can I not see red any longer?"
<set_>
I mean it. how should I test my USB peripherals on anything if I do not say okay, you are right, that is blue and it outputs what you say without me testing?
<set_>
I get it.
<set_>
If and when...
<zmatt>
documentation
<zmatt>
of the product
<set_>
I was believing my current host did not meet the requirements for the BBAI-64 USB C to USB A.
<zmatt>
and/or labeling on the product (e.g. usb chargers are normally labeled with amperage in tiny print)
<zmatt>
for the what?
<set_>
I have four black usb ports. Each labeled SS and 10.
<set_>
I am thinking they are not USB 3.0 Gen 1 nor USB 3.0 Gen 2.
<zmatt>
can you explain the situation more coherently? are you talking about powering the BBAI-64 or are you talking about having the BBAI-64 power some device?
<zmatt>
gen1/2 is about data speed and has nothing to do with power
<set_>
Powering the BBAI-64 and having a tethered connect was the purpose.
<set_>
Oh.
<set_>
I was unaware.
<set_>
I thought one could deliver greater amperage.
<set_>
I will need to read more.
<zmatt>
if you want to connect the BBAI-64 to a computer via usb I'd suggest you power the BBAI-64 via the barrel jack (5V 3A)
<set_>
Anyway, I found a link. With greater GBPS (gigabits per second), one would think that the a higher amperage would need to take place.
<zmatt>
jkridner: also, Fig 59 in the quick start contradicts the text below it... it shows a USB A to USB C connection labeled "5V >= 3A" (which isn't officially supported with USB-A) while the text below it correctly says "using a USB-A to Type-C cable which will always require power from the DC barrel jack"
<set_>
Odd stuff, man. Anyway, thank you for my lesson today. I cannot wait for this darn PSU!
<zmatt>
jkridner: it would probably be better to have two images side by side, one showing a USB-C to USB-C connection and one showing USB-A to USB-C + separate power adapter for the barrel jack
<zmatt>
right now it seems likely it will make users who don't read carefully think they can just plug it into their laptop and expect it to work
<jkridner>
yeah. :-/
libredev has joined #beagle
<set_>
I would say that fine details may work but who knows? I was havin' another issue without knowing it and thinking the current host was to blame. The SD Cards that used to work on the BBB did not work any longer. I figured out the issue. It had nothin' to do with the host or target (BBAI-64)...
<set_>
I read from eaton/tripp-lite about their ideas revolvin' around the USB Spec. for power and 500mA and 900mA are normal.
<set_>
You are right @zmatt.
<set_>
I saw charging could get up to 1.2A too.
<set_>
Anyway, I know, boring. Sorry.
libredev has quit [Ping timeout: 255 seconds]
buzzmarshall has joined #beagle
libredev has joined #beagle
starblue has quit [Quit: WeeChat 3.8]
KREYREN__ has joined #beagle
KREYREN_ has quit [Ping timeout: 240 seconds]
xet7 has quit [Remote host closed the connection]
starblue has joined #beagle
renrelkha has quit [Quit: bye]
renrelkha has joined #beagle
libredev has quit [Ping timeout: 268 seconds]
libredev has joined #beagle
libredev has quit [Ping timeout: 256 seconds]
xSkkarf has joined #beagle
darkapex has quit [Remote host closed the connection]