**** BEGIN LOGGING AT Fri Nov 25 02:59:57 2022 Nov 25 03:01:04 Hello! Nov 25 03:01:15 Do not give up on Linux. Nov 25 03:01:42 Use udev rules instead. Nov 25 03:03:36 TheConceptBoy: I think the missing permissions are due to an error in udev or the older firmware that one may be using. Nov 25 03:04:14 Anyway, w/ power comes responsibility. Right! Nov 25 03:05:19 sounds like it failed changing the pin mode, which suggests to me maybe he was trying to use a pin that was already in use e.g. for hdmi Nov 25 03:09:11 oh! Nov 25 03:09:15 That makes sense. Nov 25 03:10:08 he seems agitated. Linux can get the best of 'em! Nov 25 03:10:26 Maybe some cool soothing music? Nov 25 03:10:46 hummmmm. Clank but w/out the bang, bang? Nov 25 03:14:04 Soothing music calms the calamity of Linux when things get adjusted in a manner in which needs special attention. Nov 25 03:14:54 @zmatt: I thought you already told him about the uEnv.txt file that is available on the beagleboard.org images? Nov 25 03:26:04 is pathlib broken w/ the newer images? Nov 25 03:30:53 never mind me. Nov 25 03:31:01 It seems w/ the newer images, blah. Nov 25 04:47:59 no? Nov 25 05:01:54 no? Nov 25 05:02:18 @zmatt: Today was Thanksgiving. I am thankful for you and our kind words. Nov 25 05:02:31 Yes. our. Nov 25 05:02:35 Ha. Nov 25 05:03:12 Anyway, I was using libgpiod again on the newer images w/ a .dts file but the .dts file was a sysfs file. Nov 25 05:03:22 So, things broked. Nov 25 05:03:41 Blah. Nov 25 05:12:04 I was using the RelayCape and found that the CIS (Cape Interface Spec) is using sysfs instead of libgpiod for writing a .dts file. Nov 25 05:12:11 Anyway, this is common still! Phew. Nov 25 05:12:56 At least the libgpiod file I wrote does not keep the gpio high now when the file exits/ends. Nov 25 05:13:39 It used to keep the pin high. Now, it just breaks the gpio pin, still, but not as a floating high pin. Nov 25 05:13:50 It returns low. Nov 25 05:22:55 happy thanksgiving! Nov 25 05:27:12 set_: it sounds like all of your problems are caused by using libgpiod... have you considered the simple fix of not using libgpiod ? Nov 25 05:37:20 Yes Nov 25 05:37:25 I have considered it. Nov 25 05:37:34 Hey ds2. Nov 25 05:37:40 Happy thanksgiving. Nov 25 08:44:43 i want to start internet on BBB connected to ubuntu 18.04 Nov 25 08:45:04 what steps i have to perfrom Nov 25 12:54:21 hi Nov 25 12:54:53  i want to connect to internet from BBB Nov 25 12:55:05 internet running on ubuntu Linux 18.08 Nov 25 12:55:09 18.04 Nov 25 12:55:21 please reply , what the steps i have to perfrom Nov 25 12:55:27 Hello. Nov 25 12:57:05 Guest9196: I think the beagleboard.org people have shied away from Ubuntu to dive deeper in Debian for their images. Nov 25 12:57:18 Let me see if I can find something. Nov 25 12:58:41 Here is a wishbone: https://repos.rcn-ee.com/ubuntu/ Nov 25 12:59:03 Now, I cannot tell you that will work b/c I have not tested it recently. Nov 25 13:11:27 he meant ubuntu on his host pc I'm pretty sure, not on the bbb Nov 25 13:11:57 Guest9196: if the bbb is connected via ethernet to your pc, and your pc has internet via wifi, then you need to enable internet sharing to share your pc's internet to the bbb Nov 25 13:14:04 I'm off to work, afk Nov 25 15:00:01 Hello, i'm struggling with a BBB which does not reads some USB drives (or better, reads only the one i've shipped with it, and not any of the drives the Korean customer tried) Nov 25 15:00:23 I've found this very old thread: Nov 25 15:00:23 https://beagleboard.narkive.com/lT3z4Vmy/caution-musb-babble-interrupt-occurred Nov 25 15:00:45 are you actually seeing babble errors in the kernel log? Nov 25 15:00:58 i would like to know if the USB problem discussed there is still an issue or was solved. Nov 25 15:01:25 babble is generally a hardware issue Nov 25 15:01:49 but I haven't really heard people talking about it in many years, I'm pretty sure the current kernel driver recovers from them Nov 25 15:02:04 what are you actually seeing in the kernel log? Nov 25 15:02:13 zmatt: i dont have ANY access to the BBB there. All i know is that my kiosk app does not automatically shows the drive content, which to me means that the sda1 was not mounted by the system Nov 25 15:02:23 is the usb stick FAT-formatted? Nov 25 15:02:28 (and not exFAT or NTFS) Nov 25 15:02:32 yes, FAT32 Nov 25 15:02:54 but mine here works also with NTFS. Nov 25 15:03:00 k Nov 25 15:03:09 anyway, we told the customer to format with Fat32 Nov 25 15:04:42 there's this line in FSTAB: /dev/sda1 /media/usb auto user,uid=1000,gid=1000,fmask=0137,dmask=0027,noauto 0 0 Nov 25 15:05:50 and my app check for the media folder every second and shows the content when the folder exists. Nov 25 15:08:10 "but I haven't really heard people talking about it in many years, I'm pretty sure the current kernel driver recovers from them" Nov 25 15:08:11 I found that thread 'cause i've see the word "babble" in dmesg on my BBB here. It happened when i removed the USB drive, so i'd say that it should not be related to the old babble issue. Am i right? Nov 25 15:08:40 that just sounds like an electrical glitch as you removed the usb drive Nov 25 15:08:50 yup. Nov 25 15:09:20 but i'm still unable to think at any cause of my problem there in Korea. Nov 25 15:10:21 the kernel for Debian 10 was already patched for the "babble" problem? Nov 25 15:10:51 that's going to be very hard to debug without having one of 1. access to the bbb, 2. access to logs, or 3. access to an usb stick that exhibits the problem Nov 25 15:11:32 I have no idea, but the babble issue was afaik limited to fairly specific hardware scenarios, I don't think it ever happened simply with a usb stick Nov 25 15:12:09 ues, i see. what i meant is if you never heard of the problem from before Debian 10 or after Nov 25 15:12:31 I don't remember Nov 25 15:12:37 kk Nov 25 15:12:55 thanks Nov 25 15:58:16 Hi everyone! I'm new to Beagle and am now working with a BeagleBoneBlack. My beagle was shipped with Debian 10 on the eMMC and what it seems like there is no FAT partition so the SPL and U-Boot would be written in RAW somewhere on the eMMC. Does anyone have a memory layout for the eMMC, i.e. where are SPL, U-Boot and (especially) U-Boot enviroments Nov 25 15:58:16 written on the eMMC? I cannot find this information anywhere online. Must urgently I now need to configure /etc/fw_env.config so I can use fw_setenv. Later on I will also need to overwrite SPL as well as U-Boot (using dd). Any help would be greatly appreciated! Nov 25 16:03:02 Guest20: why not just completely reflash eMMC with a new image? Nov 25 16:03:32 and the default u-boot on beagleboard.org images do not support persistent environment Nov 25 16:04:03 Aaah ok well that explains a lot already Nov 25 16:04:10 oh wait you have the latest image, I keep thinking debian 10 is older than buster Nov 25 16:04:57 SPL with configuration header is at sector offset 256, u-boot.img is at sector offset 768 Nov 25 16:06:40 I cannot do a complete eMMC reflash as I will use my own custom Linux rootfs that I have cross-compiled and my eMMC will be divided into two partitions and to support system update. Then after every update I will use fw_setenv to set a persistens variable that U-Boot will use to know which partition to boot. Nov 25 16:07:56 I see, then you may need to build u-boot yourself Nov 25 16:08:33 zmatt thanks! So in the latest Debian image (U-boot is at U-Boot 2019.04-00002-g31a8ae0206 (May 13 2020 - 09:26:17 -0500), Build: jenkins-github_Bootloader-Builder-139) there is no support to for persisting U-boot enviroment? Nov 25 16:09:12 correct, it only supports the built-in environment Nov 25 16:11:35 Ok thanks once again! Saved me a lot of trouble trying to find what cannot be found :) I will tweak my own SPL and U-Boot binaries a bit still to make sure the will support persistent variables and then dd them into the memory sectors and hope for the best that it will boot **** ENDING LOGGING AT Sat Nov 26 02:59:56 2022