**** BEGIN LOGGING AT Mon Nov 21 02:59:57 2022
Nov 21 03:23:54 <set_> I found it. Forget it for now.
Nov 21 05:27:24 <Guest38> hello
Nov 21 05:27:43 <Guest38> is their anyone
Nov 21 13:17:51 <set_> Monday, not-so-funday?
Nov 21 13:18:16 <set_> Or...is it? Is it funday for this Monday?
Nov 21 13:18:27 <set_> Anyway, either/or, the show must go on!
Nov 21 13:19:01 <set_> @zmatt: Did you see what I typed earlier in the day/night/day?
Nov 21 13:19:46 <set_> I am going to pitch in w/ the docs. since I am still terrible w/ programming. This may be useful to people looking to achieve specific tasks.
Nov 21 13:20:27 <set_> Anyway, I do not know if I need your permission or not. I wanted to use some of your ideas.
Nov 21 13:21:12 <set_> udev rules, some source, and ideas in general are three things that I can accredit to you for helping me see daybreak.
Nov 21 13:25:17 <set_> Anyway, I will wait on your call.
Nov 21 13:25:27 <set_> text...whatever.
Nov 21 14:27:26 <GenTooMan> welcome to TG week
Nov 21 14:31:26 <set_> TG all day every day! BBL!
Nov 21 19:33:42 <set_> I made it.
Nov 21 19:33:44 <set_> I am back!
Nov 21 22:53:14 <set_> Hello? @zmatt, have you been watching my movement? I was trying to get your permission to boast about something that may help future users but you never replied...
Nov 21 22:57:45 <jfsimon1981> Good evening
Nov 21 22:58:25 <zmatt> set_: I have no idea what you're asking of me, I mostly just hope you're just heaping confusion onto new users
Nov 21 22:58:32 <zmatt> *not just
Nov 21 22:59:54 <zmatt> like, you're not being specific at all about what you're talking about.... what files? use in what way?
Nov 21 23:00:52 <jfsimon1981> Something about reading gpio ? Unsure.
Nov 21 23:09:56 <set_> Oh.
Nov 21 23:10:01 <set_> Ha. Not. Got it.
Nov 21 23:10:17 <set_> Um...yes.
Nov 21 23:10:46 <set_> I was trying to not confuse people by allowing them insight on how to be guided into a C program via the BBB and RelayCape.
Nov 21 23:11:12 <set_> This is when I remembered that you had that udev rule for /dev/gpio/ and a fixed file in python3.
Nov 21 23:11:20 <set_> You fixed my terrible python3 file already.
Nov 21 23:11:39 <set_> Anyway, the docs. seem to be an easier way for me to give back.
Nov 21 23:12:04 <set_> I am learning git a bit better and learning how to merge, give, take, and reward.
Nov 21 23:18:11 <set_> Anyway, as senseless as that seems to you, I need to learn more.
Nov 21 23:19:10 <set_> So, I will be trying to show off some artifacts and incorporate them in the docs. if allowed. But only if allowed...this means the git from above needs to allow my whereabouts to post at times.
Nov 21 23:19:12 <set_> See.
Nov 21 23:19:54 <set_> I know what I do is not a big deal to you guys/gals.
Nov 21 23:19:59 <set_> That is okay by me.
Nov 21 23:25:45 <set_> @zmatt: Can I use your udev rule for /dev/gpio/relay-jp3?
Nov 21 23:26:17 <set_> The issue is that I do not think I am using it any longer, i.e. like it self-destructed.
Nov 21 23:29:34 <set_> anyway, I will stick to enable_uboot_cape_universal=1 for using the thing. Sorry to disturb you.
Nov 22 13:07:02 <jfsimon1981> set_ i don't see how you'd disturb anyone but it's not easy to follow you
Nov 22 19:06:53 <NishanthMenon> ok - off we go with ai64 - go upstream https://lore.kernel.org/all/20221122190209.jwfj56d6kxpxdkua@untreated/
Nov 23 00:50:16 <TheConceptBoy> Good day, everyone.
Nov 23 00:57:38 <TheConceptBoy> I'm trying to figure out the next course of action. I have this project I worked on using Python and Pygame on Raspberry Pi 4. Due to the chip shortage I am forced to look into other options for a linux based SoC to run my project on and I landed on Beaglebone black. I am currently trying to get my project running on it but it seems that, based on
Nov 23 00:57:38 <TheConceptBoy> the input from the pygame userbase, it will require a whole lot of stuff I have no idea about like ,recompile SDL2 from source, recompiling Pygame from source to use a different frame buffer,  install all the dependencies for evdev/kmsdrm/input/directfb et cetera.
Nov 23 00:58:25 <zmatt> recompiling all that is needed? o.O
Nov 23 00:58:31 <zmatt> wtf
Nov 23 00:58:40 <TheConceptBoy> See, I don't know if that is true or not
Nov 23 00:58:47 <TheConceptBoy> for all I know that's what i have to do
Nov 23 00:59:11 <zmatt> I don't really know anything about SDL... with qt5 you can just select the desired backend using environment variables
Nov 23 00:59:19 <TheConceptBoy> At this point I am wondering, would it not be easier to just.... not use pygame and just recode my project using something else that just works natively on beaglebone? What would that be? I only used pygame to display simple text, rectabled, simple textures
Nov 23 00:59:30 <TheConceptBoy> qt5
Nov 23 01:00:27 <TheConceptBoy> There was one thing that pygame offered, and that is post processing, it's almost shader like, where I could create chromatic abberation and screen distoprtion effect
Nov 23 01:00:50 <TheConceptBoy> qt is a software framework so I don't know if it's possible to do that sort of stuff there
Nov 23 01:01:12 <zmatt> "You can set the environment variable "SDL_VIDEODRIVER" to the name of the driver you want to use."
Nov 23 01:01:37 <TheConceptBoy> Is that in regards to pygame?
Nov 23 01:02:12 <zmatt> for sdl yeah
Nov 23 01:02:17 <TheConceptBoy> Oh I need to also point out that I was using headless rasbian.
Nov 23 01:02:26 <TheConceptBoy> so no gui, just console.
Nov 23 01:02:38 <TheConceptBoy> when I launched my pygame application, it just shows up fullscreen
Nov 23 01:02:52 <zmatt> sounds like it was already using one of the framebuffer backends then
Nov 23 01:03:07 <TheConceptBoy> So now I was trying to run it on beaglebone IoT but it doesn't show the game window
Nov 23 01:03:32 <TheConceptBoy> I put together a quick python application to cycle through a list of display drivers to determine which one beaglebone IoT was using
Nov 23 01:03:48 <TheConceptBoy> https://media.discordapp.net/attachments/1038626269870444696/1039666292560511076/PXL_20221108_222207182.jpg?width=930&height=523
Nov 23 01:04:22 <TheConceptBoy> This was the output
Nov 23 01:05:26 <TheConceptBoy> https://pastebin.com/yZqku0XS
Nov 23 01:05:30 <TheConceptBoy> This was the script
Nov 23 01:06:01 <zmatt> most of those are sdl1, sdl2 video drivers on linux are x11, wayland, kmsdrm, and directfb ... kmsdrm should be the correct one
Nov 23 01:06:05 <TheConceptBoy> It basically just cycled through a list of possible display drivers supported by SDL2, which pygame used. and attempted to run
Nov 23 01:06:19 <TheConceptBoy> kmsdrm
Nov 23 01:06:30 <TheConceptBoy> That's what I figured the best option is
Nov 23 01:06:43 <TheConceptBoy> it's not installed on beaglebone IoT however
Nov 23 01:07:04 <TheConceptBoy> but beaglebone black still outputs an HDMI signal so some sort of display framebuffer must be involved
Nov 23 01:07:25 <zmatt> I would assume these are built into libsdl, not separate installables
Nov 23 01:07:44 <TheConceptBoy> That I honestly have no idea
Nov 23 01:07:46 <zmatt> yeah I don't see any separate libsdl2 packages for individual video backends
Nov 23 01:08:06 <TheConceptBoy> So what does that mean that it's built into libsdl2?
Nov 23 01:08:20 <TheConceptBoy> as in what does that imply in relation to my issue?
Nov 23 01:08:27 <zmatt> btw are you using debian buster or debian bullseye?
Nov 23 01:08:38 <TheConceptBoy> let me check
Nov 23 01:10:24 <set_> Hello.
Nov 23 01:10:31 <TheConceptBoy> buster console image 2022-11-01
Nov 23 01:11:01 <zmatt> TheConceptBoy: just to confirm, /dev/dri/card0 exists?
Nov 23 01:11:11 <TheConceptBoy> I was trying to save on as much processing as possible by not running the desktop envrionement,
Nov 23 01:11:13 <TheConceptBoy> let me check
Nov 23 01:15:06 <zmatt> debian bullseye has a newer version of libsdl (and other packages) than debian buster, so it may be worth trying a debian bullseye (iot or minimal) image from https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280
Nov 23 01:16:29 <TheConceptBoy> Confimed dev/dri/card0 exists
Nov 23 01:16:51 <zmatt> my current intuition says maybe sdl's kmsdrm backend doesn't like the tilcdc kernel driver for some reason (probably a dumb reason)
Nov 23 01:18:09 <TheConceptBoy> Is I see
Nov 23 01:18:30 <TheConceptBoy> Ok so I should try iOT or minimal instead
Nov 23 01:18:37 <TheConceptBoy> which wone do you recomend I start with?
Nov 23 01:18:45 <zmatt> using strace to trace kernel syscalls may be informative, although you'd preferably want to do that on some minimal sdl example written in C/C++ rather than something like pygame... but trying a newer sdl version by using bullseye may be a better thing to start with since maybe the issue is already fixed
Nov 23 01:20:17 <zmatt> if you're comfortable with installing whatever debian packages you need using apt, I'd start with minimal.   the iot image comes with a bunch of stuff preinstalled which may not be relevant to you at all and just wastes disk space
Nov 23 01:21:17 <TheConceptBoy> gotcha, I'll start with minimal
Nov 23 01:21:59 <TheConceptBoy> At this junction I either have to try to get pygame running, or I need to use something else like perhaps Adafruit GFX.
Nov 23 01:22:08 <TheConceptBoy> Can GFX be rendered to HDMI?
Nov 23 01:22:22 <TheConceptBoy> or will I have to use some SPI screen?
Nov 23 01:22:45 <zmatt> I've never heard of "adafruit gfx" ... in my experience, most adafruit stuff for the beaglebone is of dubioous quality
Nov 23 01:23:02 <TheConceptBoy> Ah gotcha
Nov 23 01:23:30 <TheConceptBoy> Adafruit GFX is a custom graphics library, used most frequently to write text and deaphical interface to SPI driver displays
Nov 23 01:23:35 <zmatt> you shouldn't need anything special, if sdl kmsdrm isn't working on the beaglebone that's a bug in sdl
Nov 23 01:24:12 <zmatt> (or a bug in *some* library anyway)
Nov 23 01:40:19 <set_> Is someone trying to use the GPU on the BBB or is not what this is about right now?
Nov 23 01:40:31 <zmatt> this has nothing to do with the gpu
Nov 23 01:40:35 <set_> Oh.
Nov 23 01:40:37 <set_> No issue.
Nov 23 01:41:45 <set_> If the kernel has it loaded, pre installed on the image, user space allows for accessing many things.
Nov 23 01:43:06 <set_> For instance, I would need to account for a file in user space when accessing, what @zmatt said about strace, usable kernel modules.
Nov 23 01:43:57 <zmatt> wtf are you talking about
Nov 23 01:44:13 <set_> SDL2 gives issues to everyone who uses it.
Nov 23 01:44:56 <set_> It is not an issue w/ SDL2 or a backend. I found that kiosk mode is available somehow.
Nov 23 01:45:36 <set_> Now, did I remember or account for this change. No. But, I like this subject. I do not want to see it die just yet.
Nov 23 01:45:46 <zmatt> ???
Nov 23 01:46:23 <set_> @zmatt, I thought you guys were having trouble w/ promoting a kiosk mode type setting.
Nov 23 01:46:43 <zmatt> wtf is "kiosk mode"? what are you talking about?
Nov 23 01:47:18 <set_> It could be a floating captured graphic or whatever graphic.
Nov 23 01:47:43 <set_> Kiosk mode, is just a term for screen w/ graphics only.
Nov 23 01:48:03 <TheConceptBoy> installing the dependencies on minimal
Nov 23 01:48:17 <TheConceptBoy> anyone ever tried to replace the 4gb onboard emmc with a larger capacity?
Nov 23 01:48:34 <set_> Yes.
Nov 23 01:48:40 <set_> I saw one person to it.
Nov 23 01:49:10 <set_> I saw one person do it but did they make it work, no clue.
Nov 23 01:49:35 <zmatt> I guess if you're comfortable reworking bga chips you could just swap it out
Nov 23 01:49:48 <zmatt> and hope the board survives :P
Nov 23 01:50:01 <zmatt> not sure why you'd want to, 4G is a lot of space
Nov 23 01:56:06 <TheConceptBoy> buster minimal doesn't fit on the mmc
Nov 23 01:56:14 <zmatt> what? yes it does
Nov 23 01:56:16 <TheConceptBoy> or at least that forum page did not provide an option
Nov 23 01:56:35 <TheConceptBoy> I assume that if they don't provide a download then it didn't work out?
Nov 23 01:56:43 <zmatt> there's no "buster minimal" image btw, do you mean buster console?
Nov 23 01:56:58 <TheConceptBoy> my mistake
Nov 23 01:57:03 <TheConceptBoy> Debian 11.x (Bullseye) Minimal Snapshot
Nov 23 01:57:22 <TheConceptBoy> the only options I see there for minimal is microSD
Nov 23 01:57:28 <TheConceptBoy> so it runs off the microsd
Nov 23 01:57:39 <TheConceptBoy> On the side note. Something I noticed
Nov 23 01:58:07 <zmatt> for bullseye there's no flasher images for some reason, you need to boot from sd card, log in, do "sudo enable-beagle-flasher" and then reboot
Nov 23 01:58:17 <TheConceptBoy> oh
Nov 23 01:58:18 <TheConceptBoy> I see
Nov 23 01:58:24 <zmatt> this is mentioned in the post
Nov 23 01:58:27 <TheConceptBoy> so you do it manually
Nov 23 01:58:36 <TheConceptBoy> yeah I read that part but I did not comprehand
Nov 23 01:58:46 <TheConceptBoy> what it was reffering to
Nov 23 01:58:54 <zmatt> yeah there's a weird mistaken comment in that section it seems
Nov 23 01:59:04 <TheConceptBoy> On the side note. How come I cannot download pip for python3 using sudo apt-get install python3-pip until I do sudo apt-get update
Nov 23 01:59:13 <TheConceptBoy> I know that pip usually comes with python
Nov 23 01:59:19 <TheConceptBoy> but not in this minimal release
Nov 23 01:59:41 <TheConceptBoy> I have to install pip manually and the command to do so:
Nov 23 01:59:45 <TheConceptBoy> sudo apt-get install python3-pip
Nov 23 01:59:47 <TheConceptBoy> was failing
Nov 23 01:59:54 <TheConceptBoy> until I updated using sudo apt-get update
Nov 23 01:59:55 <zmatt> that's just how apt works, you need to do apt-get update occasionally to download the package lists, and in particular need to do it at least once to begin with
Nov 23 02:00:03 <TheConceptBoy> Oh
Nov 23 02:00:06 <TheConceptBoy> package list is stored locally
Nov 23 02:00:09 <TheConceptBoy> I see
Nov 23 02:00:19 <TheConceptBoy> that's why it said it could not find package
Nov 23 02:00:40 <TheConceptBoy> sudo apt-get update retreives a new up to date package list
Nov 23 02:00:49 <zmatt> yep
Nov 23 02:00:53 <TheConceptBoy> gotcha
Nov 23 02:04:50 <TheConceptBoy> OH
Nov 23 02:04:53 <TheConceptBoy> HOLY
Nov 23 02:04:54 <TheConceptBoy> hold on
Nov 23 02:05:01 <TheConceptBoy> the driver test didn't fail
Nov 23 02:05:06 <TheConceptBoy> it stopped on kmsdrm
Nov 23 02:05:09 <TheConceptBoy> could it
Nov 23 02:05:17 <TheConceptBoy> could it possibly be salvation?
Nov 23 02:05:25 <TheConceptBoy> Ok now I need to set up the actual game project
Nov 23 02:05:27 <zmatt> \o\
Nov 23 02:05:29 <zmatt> /o/
Nov 23 02:05:32 <zmatt> \o/
Nov 23 02:05:46 <TheConceptBoy> brb
Nov 23 02:06:22 <zmatt> that's the best kind of debugging... when you don't actually have to do it because the issue has already been fixed
Nov 23 02:06:39 <TheConceptBoy> lol
Nov 23 03:20:37 <TheConceptBoy> ok
Nov 23 03:20:45 <TheConceptBoy> looks like I'm on the last few dependencies left
Nov 23 03:20:56 <TheConceptBoy> gotta give user permission to use i2c-2 port
Nov 23 03:21:21 <TheConceptBoy> this used to work, I tried debian@BeagleBone:~$ chmod g+rw /dev/i2c-2
Nov 23 03:21:38 <TheConceptBoy> but even though it goes through, python still says user permissions denied
Nov 23 03:22:15 <zmatt> what does "ls -l /dev/i2c-2" show?
Nov 23 03:22:37 <TheConceptBoy> debian@BeagleBone:~$ ls -l /dev/i2c-2
Nov 23 03:22:38 <TheConceptBoy> crw-rw---- 1 root root 89, 2 Nov 23 03:16 /dev/i2c-2
Nov 23 03:22:45 <zmatt> looks like a missing udev rule
Nov 23 03:23:04 <TheConceptBoy> I'm not familliar with what udev is
Nov 23 03:23:21 <zmatt> the thing that, among other things, is responsible for setting device permissions
Nov 23 03:24:15 <TheConceptBoy> I see
Nov 23 03:24:33 <TheConceptBoy> looking at the documentation page for this
Nov 23 03:24:34 <TheConceptBoy> https://www.ddcutil.com/i2c_permissions/
Nov 23 03:24:48 <TheConceptBoy> sudo cp /usr/share/ddcutil/data/45-ddcutil-i2c.rules /etc/udev/rules.d
Nov 23 03:25:02 <zmatt> you're looking at documentation for a random utility
Nov 23 03:25:27 <TheConceptBoy> I figured the url address looked unfammiliar
Nov 23 03:26:56 <TheConceptBoy> sudo chown :i2c /dev/i2c-2
Nov 23 03:26:59 <TheConceptBoy> did the job
Nov 23 03:27:14 <zmatt> I see the problem
Nov 23 03:27:33 <zmatt> mabye
Nov 23 03:28:09 <zmatt> never mind
Nov 23 03:28:32 <zmatt> hold on let me test something
Nov 23 03:30:50 <zmatt> TheConceptBoy: so you don't have an /etc/udev/rules.d/80-i2c-noroot.rules file?
Nov 23 03:31:14 <TheConceptBoy> This is a fresh installation of minimal so if it doesn't come with one already then no
Nov 23 03:31:26 <zmatt> I am asking whether it comes with one
Nov 23 03:32:19 <TheConceptBoy> I do see it there
Nov 23 03:32:36 <zmatt> can you pastebin its contents?
Nov 23 03:32:42 <TheConceptBoy> sure thing
Nov 23 03:33:27 <TheConceptBoy> https://pastebin.com/Chm10S6V
Nov 23 03:34:16 <zmatt> huh, that looks like it should change the group of the device to gpio, so why didn't that happen....
Nov 23 03:34:40 <TheConceptBoy> the reason would escape me even if it was staring me in the face
Nov 23 03:34:51 <TheConceptBoy> but that last command did stop the permission error
Nov 23 03:34:56 <TheConceptBoy> so now I's onto the last stretch
Nov 23 03:35:08 <zmatt> that's not persistent across reboot though
Nov 23 03:35:31 <TheConceptBoy> huh let me try
Nov 23 03:36:26 <TheConceptBoy> youre right
Nov 23 03:36:33 <TheConceptBoy> just got the error again
Nov 23 03:36:38 <zmatt> the exact same udev rule is working fine on my beaglebone, so I don't really get what's going on
Nov 23 03:37:08 <TheConceptBoy> literally didn't change that file at all aside from doing:
Nov 23 03:37:21 <TheConceptBoy> sudo groupadd i2c-2
Nov 23 03:37:25 <zmatt> it's written a bit weirdly (normally conditions like ACTION=="add" should be before actions like GROUP="i2c") but I don't see how that could matter
Nov 23 03:37:33 <zmatt> that command is nonsense
Nov 23 03:38:22 <TheConceptBoy> it's from here
Nov 23 03:38:23 <TheConceptBoy> https://lexruee.ch/setting-i2c-permissions-for-non-root-users.html
Nov 23 03:40:26 <zmatt> TheConceptBoy: can you pastebin the output of:  udevadm info -a /dev/i2c-2
Nov 23 03:41:35 <TheConceptBoy> https://pastebin.com/Mnp8tRNQ
Nov 23 03:42:17 <zmatt> oh, huh
Nov 23 03:42:41 <zmatt> no that should still be fine
Nov 23 03:43:04 <zmatt> and:  udevadm info /dev/i2c-2
Nov 23 03:43:41 <TheConceptBoy> https://pastebin.com/YmdsYu7b
Nov 23 03:43:59 <TheConceptBoy> oops
Nov 23 03:44:07 <TheConceptBoy> copied a bunch of stuff that's not needed
Nov 23 03:44:09 <TheConceptBoy> one second
Nov 23 03:44:29 <TheConceptBoy> https://pastebin.com/C34hqWMV
Nov 23 03:44:59 <TheConceptBoy> PS according to all the google results, to get into the super user, no password is requires
Nov 23 03:45:03 <TheConceptBoy> and yet it asks for one
Nov 23 03:45:03 <zmatt> wait hold on
Nov 23 03:45:23 <zmatt> uhh, then I don't know what you've been googling or what you've found
Nov 23 03:45:32 <zmatt> a password is always required
Nov 23 03:46:05 <zmatt> but hold on, I'm doing some testing on my beaglebone
Nov 23 03:46:05 <TheConceptBoy> https://www.dummies.com/article/technology/computers/hardware/beaglebone/beaglebone-and-the-root-superuser-144936/
Nov 23 03:46:16 <TheConceptBoy> By default, no password is required to log in as root, but if you’ve defined one, you’re prompted to type it.
Nov 23 03:46:26 <TheConceptBoy> but then again
Nov 23 03:46:29 <TheConceptBoy> article from 2016
Nov 23 03:46:31 <zmatt> TheConceptBoy: that.
Nov 23 03:46:37 <TheConceptBoy>  ugh
Nov 23 03:46:54 <TheConceptBoy> for all the benefits the internet brings us, outdated documentation is not one of them
Nov 23 03:46:55 <TheConceptBoy> lol
Nov 23 03:49:35 <TheConceptBoy> I have absolutely no ide how I managed to grant user permissions to i2c-2 port last time but I certainly don't remember messing with the udev file
Nov 23 03:49:43 <TheConceptBoy> I miss arduino
Nov 23 03:49:47 <zmatt> this is 100% an udev rule issue
Nov 23 03:50:09 <zmatt> normally you should have access by default to i2c on beaglebone images, this is a bug
Nov 23 03:50:12 <zmatt> in the bullseye image
Nov 23 03:50:21 <zmatt> I'm trying to figure out what might be going on
Nov 23 03:50:26 <TheConceptBoy> I see
Nov 23 03:52:46 <TheConceptBoy> On rasbian we have to manually go into the configuration and enable i2c, perhaps the same was adopted for bb?
Nov 23 03:53:00 <TheConceptBoy> users's job to only enable ports that users need
Nov 23 03:53:01 <zmatt> no it's just a broken udev rule
Nov 23 03:53:18 <zmatt> I think I may be onto it
Nov 23 03:53:38 <zmatt> I've reproduced the issue, just hold while I figure this out
Nov 23 03:53:45 <TheConceptBoy> yeppers
Nov 23 03:53:57 <TheConceptBoy> after this there's one more thing before I think it'll launch
Nov 23 03:54:47 <zmatt> ohhhhhhhhhhh d'oh, 80-i2c-noroot.rules has nothing to do with this
Nov 23 03:55:03 <zmatt> sudo apt-get install i2c-tools
Nov 23 03:56:26 <zmatt> TheConceptBoy: the i2c-tools package includes an udev rule that sets up the permissions of /dev/i2c-* and my guess would be that this package is missing from the minimal image
Nov 23 03:57:17 <TheConceptBoy> installed
Nov 23 03:57:22 <TheConceptBoy> rebooting to test
Nov 23 03:57:40 <TheConceptBoy> it was indeed one of the steps I missed
Nov 23 03:58:10 <zmatt> I'm honestly not even sure what 80-i2c-noroot.rules is supposed to accomplish
Nov 23 03:58:14 <TheConceptBoy> ok it's no longer complaining
Nov 23 03:58:27 <TheConceptBoy> last thing is the video error
Nov 23 03:58:34 <TheConceptBoy> video system not initalized
Nov 23 03:58:41 <zmatt> from what?
Nov 23 03:58:51 <TheConceptBoy> oygame.error: Video System not initialized
Nov 23 03:58:57 <TheConceptBoy> pygame*
Nov 23 03:59:43 <zmatt> stackoverflow says you may have forgotten pygame.init() ?
Nov 23 04:00:41 <zmatt> I don't know anything about pygame so I'm no more useful than google is for this
Nov 23 04:01:12 <TheConceptBoy> https://pastebin.com/SsfX1DcY
Nov 23 04:01:47 <TheConceptBoy> https://snipboard.io/SgPlHo.jpg
Nov 23 04:01:58 <TheConceptBoy> I can consult the pygame discord
Nov 23 04:02:07 <TheConceptBoy> might be able to get continuation there.
Nov 23 04:02:14 <TheConceptBoy> As the problem if video drivers is resolved now
Nov 23 04:02:21 <TheConceptBoy> thank you very much btw
Nov 23 04:02:27 <TheConceptBoy> I don't know what I would have done without you
Nov 23 04:02:44 <zmatt> it's now successfully loading the kmsdrm video driver?
Nov 23 04:03:12 <TheConceptBoy> KK
Nov 23 04:03:13 <TheConceptBoy> UJ
Nov 23 04:03:16 <TheConceptBoy> pp[s
Nov 23 04:03:20 <TheConceptBoy> oops
Nov 23 04:03:25 <zmatt> cat on keyboard?
Nov 23 04:03:30 <TheConceptBoy> face on the keyboard
Nov 23 04:03:39 <TheConceptBoy> It's not complaining about it
Nov 23 04:03:45 <TheConceptBoy> the driver that is.. not the face
Nov 23 04:04:09 <TheConceptBoy> I did
Nov 23 04:04:10 <TheConceptBoy> os.putenv('SDL_VIDEODRIVER', 'kmsdrm')
Nov 23 04:04:14 <zmatt> ok!
Nov 23 04:05:09 <TheConceptBoy> Oh btw
Nov 23 04:05:23 <TheConceptBoy> what does it mean when the comand line just looks like this
Nov 23 04:05:25 <TheConceptBoy> >
Nov 23 04:05:51 <zmatt> incomplete command, it's waiting for more input
Nov 23 04:05:58 <TheConceptBoy> aah
Nov 23 04:06:02 <TheConceptBoy> any way to terminate?
Nov 23 04:06:09 <zmatt> like, if you press enter with an unclosed { or whatever
Nov 23 04:06:10 <zmatt> ctrl-C
Nov 23 04:06:11 <TheConceptBoy> esc or ctrl+C don't work
Nov 23 04:06:21 <TheConceptBoy> n
Nov 23 04:06:30 <TheConceptBoy> oops wrong keyboard
Nov 23 04:06:37 <TheConceptBoy> got it
Nov 23 04:07:15 <TheConceptBoy> thank you
Nov 23 23:28:59 <TheConceptBoy> Good day, again
Nov 23 23:31:33 <TheConceptBoy> I've gotten a bit of progress in getting my pygame project running on beaglebone. This issue may or may not be related with pygame, which means I may or may not find the answer here but I thought I'
Nov 23 23:31:37 <TheConceptBoy> i'd try
Nov 23 23:31:38 <TheConceptBoy> https://pastebin.com/wYedKf1w
Nov 23 23:32:29 <TheConceptBoy> I've gotten most of the errors resolved. The pygame actually runs if I sed the sdl video driver envirionment variable to dummy, which of course, doesn't make the application window appear, but I can hear it play sound and effects based on what I know is supposed to happen
Nov 23 23:33:01 <TheConceptBoy> I'm honestly thinking of just re-writing the visual end with something else
Nov 23 23:33:13 <TheConceptBoy> Something that just works on beaglebone out of the box
Nov 23 23:33:34 <TheConceptBoy> What can I use to make this text based game with? QT is one solution
Nov 23 23:34:37 <zmatt> ugh, gbm stuff again... I'm not really sure how this stuff is *supposed* to work or why it doesn't just.... work.   I think gbm is trying to load a driver-specific shared library for buffer allocation or something, though I don't really understand why since tilcdc supports the generic driver-independent buffer allocation ("dumb buffer") kernel api
Nov 23 23:35:25 <TheConceptBoy> This may be why I was told I'
Nov 23 23:35:33 <TheConceptBoy> I'd have to recompile pygame from source
Nov 23 23:35:41 <zmatt> this has nothing to do with pygame
Nov 23 23:35:50 <zmatt> recompiling pygame would get you absolutely nothing
Nov 23 23:36:04 <TheConceptBoy> Me not being able to tell the difference if it does or not certainly doesn't bode well
Nov 23 23:36:46 <TheConceptBoy> Ok so - to be honest - this is a text based game with only a few quirks like screen distortion for aestetic
Nov 23 23:37:42 <TheConceptBoy> Most of the code is just python moving data between dictionary key value pairs
Nov 23 23:38:26 <TheConceptBoy> What else can I make use to build a GUI application for debian minimum?
Nov 23 23:39:36 <zmatt> I don't really have advice to offer, I haven't done any gui development in the last decade
Nov 23 23:40:05 <zmatt> I don't understand why shit like this _still_ doesn't JUST WORK
Nov 23 23:47:35 <TheConceptBoy> I'm honestly considering just running an SPI display through python and Adafruit GFX library
Nov 23 23:47:43 <TheConceptBoy> and completely forgetting about onboard hdmi
Nov 23 23:55:20 <zmatt> it looks like gbm tries to use the internal backend by default and if this fails it falls back to trying to load an external backend, which ends up giving that error (since no such external backend exists or has any reason to exist), so the question is why the internal backend fails
Nov 23 23:57:35 <zmatt> but that internal backend looks like a maze of indirection
Nov 23 23:58:12 <zmatt> and it all seems to be integrated with stuff for opengl which we don't have, need, or care about
Nov 23 23:58:52 <zmatt> I don't understand why buffer allocation has to be such a complex mess
Nov 24 00:00:28 <zmatt> part of the problem is libraries like SDL using GBM as a generic buffer allocation library while in reality GBM is deeply tied to Mesa
Nov 24 00:07:52 <TheConceptBoy> I see
Nov 24 00:09:42 <zmatt> though this doesn't explain why it's not working.... like, even opengl via mesa should still work using software rasterization
Nov 24 00:09:48 <zmatt> so this _feels_ like a mesa/gbm bug
Nov 24 00:10:44 <zmatt> not something I can really dig into right now
Nov 24 00:12:43 <TheConceptBoy> That's alright. I think I'm going to experiment with using an spi display and custom gui library via python
Nov 24 00:13:02 <TheConceptBoy> is there an hdmi-less beaglebone version?
Nov 24 00:13:56 <zmatt> everything in me is screaming "this is dumb, such a hacky workaround shouldn't be needed" but I understand why you're discouraged by these library issues
Nov 24 00:14:33 <zmatt> you can just disable hdmi if you want to (uncomment the "disable_uboot_overlay_video=1" line in /boot/uEnv.txt)
Nov 24 00:14:53 <TheConceptBoy> Oh yeah, for sure I can do that as well
Nov 24 00:15:12 <zmatt> there are also beaglebone derivatives without hdmi like the beaglebone green but they have other changes as well
Nov 24 00:16:05 <zmatt> btw have you tried the "directfb" sdl backend as alternative to "kmsdrm" ?
Nov 24 00:16:52 <zmatt> it might work (albeit presumably using the legacy fbdev rather than the new kmsdrm api)
Nov 24 01:27:14 <set_> Hello.
Nov 24 01:29:25 <set_> Is it libgpiod in .c files that creates the gpiod_line_release(line); and gpiod_chip_close(chip); not being able to close the file, in this effort it is a LED or Relay opened from a fd, or is it the BBB that is situated in a specific way that creates this issue?
Nov 24 02:30:43 <TheConceptBoy> Welp I think I just killed my beaglebone...
Nov 24 02:31:02 <TheConceptBoy> short somewhere along spi pins or something else
Nov 24 02:31:13 <TheConceptBoy> maybe the 5b got sunk to ground directly
Nov 24 02:31:16 <TheConceptBoy> 5v
Nov 24 02:31:18 <TheConceptBoy> rip
Nov 24 02:36:49 <zmatt> yeah the tiny tiny transistors of the AM335x don't tolerate too much abuse, it ain't an arduino :P
Nov 24 02:37:30 <zmatt> although probably the most common way to murder a beaglebone is through overvoltage, e.g. putting 5V on any digital I/O
Nov 24 02:37:36 <TheConceptBoy> I lost 2x Cm4 compute modules this way
Nov 24 02:38:21 <zmatt> I don't even know how many beaglebones we lost here at work over the years, but it's quite a few
Nov 24 02:41:11 <zmatt> today I actually found a box on my desk with three beaglebones in it and a post-it asking "All dead?" ... dunno their story but presumably they want me to verify whether these bbbs are in fact deceased
Nov 24 02:49:04 <zmatt> yep, they're super dead... power led blip of doom, all three... I wonder what they did to them
Nov 24 05:34:05 <Guest43> how to get /dev/input for tsadc
Nov 24 05:34:18 <Guest43> https://stackoverflow.com/questions/74555669/how-to-get-dev-input-for-tsadc-touchscreen
Nov 24 10:16:15 <keesj> Hi, is there a tool similar to code sourcery to do bare bones development on the ai-64 ?
Nov 24 10:29:16 <keesj> https://github.com/beagleboard/beaglebone-ai/issues/21 still relevant?
Nov 24 10:46:24 <keesj2> and can the bootloader be build using buildroot e.g. https://github.com/beagleboard/beaglebone-ai/tree/master/SW/buildroot ?
Nov 24 11:22:11 <Parduz> Hello, I have a problem on a BBB located in Korea (i'm Italian).
Nov 24 11:22:11 <Parduz> There's a "Kiosk" app running on it that shows the content of a Fat32 USB drive when inserted.
Nov 24 11:22:12 <Parduz> This works fine with a USB drive i've sent there, with all the drives i tested here, but the Korean user cannot make his one working, as if the OS did'nt detect it.
Nov 24 11:22:21 <Parduz> The BBB is running debian 10.
Nov 24 11:22:58 <Parduz> My question is: there's known issues, or incopatibilities, between the BBB, or Debian, and some USB drives?
Nov 24 13:16:12 <keesj> Hi
Nov 24 15:47:24 <Parduz> Could it be possible that the BBB, once an usb drive is inserted, creates a file different than /dev/sd* ?
Nov 24 16:23:51 <Guest9074> Hi,
Nov 24 16:24:27 <Guest9074> Display resolution Begelbone AI-64?
Nov 24 19:09:35 <Guest9154> hi
Nov 24 19:10:01 <Guest9154> i want to start internet on BBB  connected to ubuntu 18.04
Nov 24 19:10:09 <Guest9154> what steps i have to perfrom ?
Nov 24 19:10:43 <Guest9154> if i connect ethernet port to rj45 connector , it is letting me to ssh
Nov 24 19:10:56 <Guest9154> but if i type ping www.google.com
Nov 24 19:11:00 <Guest9154> it is not working
Nov 24 19:11:06 <Guest9154> what the things i have to do ?
Nov 25 01:54:59 <TheConceptBoy> Good evening, everyone.
Nov 25 01:55:20 <TheConceptBoy> I've gotten a fresh installation of beaglebone black debian
Nov 25 01:55:48 <TheConceptBoy> I went with the website advertised version instead of the nightly builds this time due to a library dependency being made for that version
Nov 25 01:56:05 <TheConceptBoy> I need to grant debian user permissions to gpio
Nov 25 01:56:18 <TheConceptBoy> I'm not sure why it's not already there by default
Nov 25 02:00:31 <TheConceptBoy> The reason I suspect it's the permissions is because of a python error
Nov 25 02:00:32 <TheConceptBoy> ValueError: Set gpio mode failed, missing file or invalid permissions.
Nov 25 02:00:54 <TheConceptBoy> it mentions permissions so that's what I'm on to checking first
Nov 25 02:04:07 <TheConceptBoy> Also, on an unrelated question
Nov 25 02:04:17 <TheConceptBoy> what's the point of root if everything can be sudo overwritten
Nov 25 02:09:38 <TheConceptBoy> hmm... I'm honestly this close to just abandoning linux altogether, going back to esp32, slapping a big ass spi ram chip so I can work with json data and stick wit the land where everything... just... works...
**** ENDING LOGGING AT Fri Nov 25 02:59:57 2022