**** BEGIN LOGGING AT Fri Dec 30 02:59:56 2022 Dec 30 13:17:44 Can I have Friday Funday today? Dec 30 13:17:54 Oh! Dec 30 13:18:19 I tried to build to port the sound arch. to the BBB. Some things built. u-boot is a halt. Dec 30 13:18:27 Tough crowd! Dec 30 13:20:39 Whelp. Friday Funday is out. Sorry I asked. I should have known. Anyway...bbl! Dec 30 16:39:22 Hello? Dec 30 16:39:37 It is Friday...sheesh. Dec 30 16:39:47 You know...the end of the work week! Dec 30 16:49:18 Come on... Dec 30 16:49:19 Sheesh. Dec 30 17:07:30 If I was to search online, what are some keywords for making my server work for me? I mean...you can update via USB but how can I update via USB? Dec 30 17:08:15 Not w/ apt. W/ my own git channel? Dec 30 17:08:34 So, I would have to host my own git channel or be a part of apt? Dec 30 17:08:50 Things get too difficult too early on. Dec 30 17:14:54 Oh! Dec 30 17:15:39 I found something like it was magick. Image Magick! Dec 30 17:16:55 Could I do the git server from the BBB? Dec 30 17:31:50 You know something... Dec 30 17:31:56 This keeps getting more interesting! Dec 30 17:36:34 No freakin' way! Dec 30 17:36:46 I am slow mo' again...sheesh. Dec 30 17:55:01 I always held my stance against no init. Now, I am changing my ways. Dec 30 18:00:03 Banging my head != git Dec 30 18:08:51 and I know what you are thinking... "Did he just type that out in public?" Dec 30 18:09:02 Yes. Okay, I am damn slow. Okay! Dec 30 18:09:37 You saw @zmatt yell at me constantly for not knowing anything... Dec 30 18:47:13 Okay, maybe init is stil my worstest. Dec 30 19:32:12 Hi. I'm trying to get a BeagleBone Blue set up over USB with windows systems, and unable to do so. I connect the BBBlue over USB to the PC, install the driver (DBONE_64.exe, which works after disabling driver signature enforcement). No RNDIS network adapter / connection shows up, however (with or without rebooting). I've tried with a Windows 10 and Dec 30 19:32:12 a Windows 11 PC, with the same result. Dec 30 19:32:13 What can I do? Thanks! Dec 30 19:55:06 Never mind. It was a bad USB cable. Dec 30 20:59:33 It works! Dec 30 21:03:19 Now, my two servers are out. Man, this job...sheesh. Dec 31 00:02:01 oops. Dec 31 00:39:59 Up, up, and otay! Dec 31 00:40:10 Took me long enough...sheesh. Dec 31 00:47:31 This git server is not getting any younger! Dec 31 00:50:59 Hey all, I have a somewhat random question, i figure someone here might be able to give me some pointers. What library/vendor is "libsrv_um.so"? It's invoked by openCL, which is in turn invoked by OpenCV, in my current case. I'm on an AI-64 with a recent Bullseye image. I see mentions of it as a vendored ARM-related binary but I am not seeing clear Dec 31 00:51:00 origins in search results. Dec 31 00:51:19 Context: Dec 31 00:51:19 Thread 1 "python3" received signal SIGABRT, Aborted. Dec 31 00:51:20 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 Dec 31 00:51:20 50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. Dec 31 00:51:21 (gdb) bt Dec 31 00:51:21 #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 Dec 31 00:51:22 #1  0x0000fffff7cf6aa0 in __GI_abort () at abort.c:79 Dec 31 00:51:22 #2  0x0000ffffe17cc47c in  () at /usr/lib/libsrv_um.so Dec 31 00:51:23 #3  0x0000ffffe183e860 in  () at /usr/lib/libOpenCL.so Dec 31 00:51:23 #4  0x0000ffffe184dec0 in  () at /usr/lib/libOpenCL.so Dec 31 00:51:24 #5  0x0000ffffe186c674 in  () at /usr/lib/libOpenCL.so Dec 31 00:51:24 #6  0x0000fffff359cffc in cv::ocl::haveOpenCL() () at /usr/lib/aarch64-linux-gnu/libopencv_core.so.4.5 Dec 31 00:51:25 #7  0x0000fffff35b3e54 in cv::ocl::useOpenCL() () at /usr/lib/aarch64-linux-gnu/libopencv_core.so.4.5 Dec 31 00:51:25 #8  0x0000fffff3604ce8 in cv::UMat::getStdAllocator() () at /usr/lib/aarch64-linux-gnu/libopencv_core.so.4.5 Dec 31 00:51:26 #9  0x0000fffff3605580 in cv::UMat::create(int, int const*, int, cv::UMatUsageFlags) () at /usr/lib/aarch64-linux-gnu/libopencv_core.so.4.5 Dec 31 00:51:26 #10 0x0000fffff357da04 in cv::_OutputArray::create(int, int const*, int, int, bool, cv::_OutputArray::DepthMask) const () at /usr/lib/aarch64-linux-gnu/libopencv_core.so.4.5 Dec 31 00:51:27 #11 0x0000fffff34df720 in cv::Mat::copyTo(cv::_OutputArray const&) const () at /usr/lib/aarch64-linux-gnu/libopencv_core.so.4.5 Dec 31 00:51:27 #12 0x0000fffff4f5d2c0 in  () at /usr/lib/python3/dist-packages/cv2.cpython-39-aarch64-linux-gnu.so Dec 31 00:51:47 * set_ usually uses pastebin.com. Dec 31 00:52:09 Not asking for help debugging the crash (yet, at least...) just for pointers on the binaries. Dec 31 00:52:24 Good point, will use an online sharing service next time. Dec 31 00:52:54 Yea. I get a lot of people not chatting b/c of my odd behavior. Dec 31 00:55:25 Git. Sheesh. This is harder than porting sound from the kernel to the BBB i2s. Dec 31 01:09:20 re: my query, it seems that binary might be from PowerVR, which would make sense given the context. I still haven't found a definitive reference. And, more importantly, my question becomes: if I believe I've identified a bug in this OpenCV/OpenCL/PowerVR stack, who is it most appropriate to report to? All I'm really asking is where the BeagleBoard Dec 31 01:09:21 images get the binary from. If it's provided through TI then I'll report it to them. Dec 31 01:10:09 The people that deal w/ the mfg. of the SGX. Dec 31 01:10:22 I would think they would have a forum and support. Dec 31 01:10:55 I know they do. I was just thinking if it is a bug in the stack, people may be more inclined to pitch in! Dec 31 01:11:17 Imag. Tech. Dec 31 01:11:34 I am pretty sure they mfg. the chip on the BBB. SGX. Dec 31 01:12:01 kaelin: That is difficult stuff to handle. I am glad someone stuck it out! Dec 31 01:12:07 It beat me. Dec 31 01:13:36 Here: https://developer.imaginationtech.com/ Dec 31 01:14:13 I failed until my face turned Purple. My hair went already w/ the purple hue. Dec 31 01:14:23 Yeah, I guess it depends on how much the GPU manufacturer is invested in supporting all the software that others have built on top. I'm fairly sure this is an oversight in the interface between either OpenCV/OpenCL or OpenCL/PowerVR drivers, but I don't know where it is. They might just throw it back to me as "can't repro". Dec 31 01:14:52 Right...that is always a concern. Dec 31 01:15:20 kaelin: Maybe wait around for someone else who deals w/ the SGX more often these days... Dec 31 01:15:56 I know there was an image from beagleboard.org and they handled the port. I actually got some graphics displayed but not my own. Dec 31 01:17:51 I really am not doing anything low-level with the SGX hardware. This is high-level libraries internally dispatching to OpenCL and the hardware accelerators. In this case I was fully ready to blame TI's deep learning library for memory corruption issues at first :D  I did some digging and experimentation and it turns out that this happens any time Dec 31 01:17:51 you pass floaing-point pixel coordinates into OpenCV drawing functions. Usually OpenCV would detect it and error but something about this accelerated backend isn't checking for that case. Someone gets passed a float when they didn't expect it... Dec 31 01:18:43 I'll wait to see if anyone has more precise suggestions and otherwise I'll ask the imagination guys and go from there. Dec 31 01:19:22 Right, when I consumed my time around the SGX, I found them very helpful. At least the remainder of the men/women who were around that knew the chip. Dec 31 01:20:20 That last sentence makes no sense. Sorry. Dec 31 01:20:45 ... could have helped or could help. That should have been the ending to that sentence. Dec 31 01:21:05 haha I get the point, yeah that company/IP has been around a long time Dec 31 01:22:30 I have been following the beaglboard.org people and their moves in the field for some time, e.g. getting the books, learning Linux, and doing hardware type things. I was surprised they wanted to go ahead w/ it all. Dec 31 01:22:49 The BBAI has another type on it. Dec 31 01:23:09 And then, the BBAi_64, I believe may have another type on it as well. Dec 31 01:23:12 I can check... Dec 31 01:24:01 PowerVR® Rogue™ 8XE GE8430 3D GPU Dec 31 01:24:21 That is what is on the AI-64. **** ENDING LOGGING AT Sat Dec 31 02:59:56 2022