**** BEGIN LOGGING AT Tue May 25 03:01:36 2021
May 25 06:31:17 <jkridner-webhack> zmatt: https://beagleboard.org/chat links to Freenode restored
May 25 06:57:50 <zmatt> jkridner: yeah like I said, I think moving is a good idea but not until the channel registration on libera has been fixed
May 25 06:58:14 <zmatt> right now we can't even set a channel topic
May 25 08:32:22 <kveremitz> re: libera -
May 25 08:32:24 <kveremitz> [Tue  8:32 am]-ChanServ- Information on #beagle:
May 25 08:32:24 <kveremitz> [Tue  8:32 am]-ChanServ- Founder    : tbr, jkridner
May 25 08:32:43 <kveremitz> time to oper-up and get sorted!
May 25 08:40:24 <rob_w> is this channel about to move ?
May 25 08:44:03 <zmatt> hopefully
May 25 08:44:48 <zmatt> the channel on libera (the network set up by the former freenode operators) is in the process of being set up
May 25 08:45:39 <rob_w> same name ?
May 25 08:45:47 <zmatt> yes
May 25 08:46:30 <rob_w> see u on the otherside
May 25 08:50:29 <kveremitz> :wave:
May 25 11:28:18 <chetan> Hello , how can we get display up on iot image
May 25 11:30:22 <chetan> i can see login prompt can connect via ssh but nothing on display
May 25 19:55:55 <biggi_> Probably more of a networking/IT question than one related to Beaglebone, but thought I'd ask.  If I have 2 BBB on an unmanaged switch and want to access them; I can't just do beaglebone as I'm not sure which one I'll be connecting to.  Is there a good way to fix this?  I also can't set a static IP as if I need internet, work will block anything
May 25 19:55:56 <biggi_> outside a specified IP range and I don't want to cause an IP issue with them going forward.
May 25 19:58:07 <zmatt> give them different hostnames
May 25 19:58:27 <zmatt> sudo hostnamectl set-hostname beaglebone2
May 25 19:58:41 <zmatt> then connect by hostname
May 25 19:59:15 <zmatt> (probably pick a better name than "beaglebone2")
May 25 19:59:29 <biggi_> That is so much easier than the route I was going.
May 25 19:59:35 <biggi_> I was setting up an eth0 alias XD
May 25 20:00:17 <zmatt> I'm not even sure I want to know what you mean by that
May 25 20:00:52 <biggi_> I was setting up eth0:1 to a static IP
May 25 20:01:14 <zmatt> ew
May 25 20:01:20 <biggi_> So that way eth0 would still be on the work network for internet and I would have a static IP to also access it by
May 25 20:01:35 <zmatt> yeah that's just silly
May 25 20:01:56 <kos_tom> has anyone seen some regressions on USB over Ethernet in recent upstream kernels on BBBW ?
May 25 20:01:58 <biggi_> I mean it would have worked
May 25 20:02:03 <kos_tom> it "works", but lots of packets are lost
May 25 20:02:11 <kos_tom> (currently testing on upstream 5.10.38)
May 25 20:02:28 <zmatt> usb over ethernet?  do you mean ethernet over usb?
May 25 20:02:47 <kos_tom> ethernet over usb yes, sorry :)
May 25 20:03:49 <biggi_> zmatt: so I did that and it still wants to use beaglebone as the hostname?
May 25 20:03:50 <zmatt> by "upstream" you mean a mainline kernel rather than one of rcn's -ti or -bone kernel packages?
May 25 20:03:52 <biggi_> even after a reboot
May 25 20:04:07 <zmatt> biggi_: uhh no it shouldn't, how did you conclude that?
May 25 20:04:08 <kos_tom> zmatt: correct
May 25 20:04:08 <biggi_> when trying to login with putty
May 25 20:04:24 <biggi_> putty wouldn't login with beaglebone2, it still wanted beaglebone
May 25 20:04:38 <biggi_> wonder if the work DHCP hadn't updated?
May 25 20:05:04 <zmatt> biggi_: I mean, if you reboot then it should get a new lease, but I guess it depends on how quickly your local DHCP updates
May 25 20:05:14 <zmatt> can you use beaglebone2.local instead? (i.e. mDNS resolution)
May 25 20:05:45 <biggi_> i use beaglebone.local now
May 25 20:05:51 <biggi_> and beaglebone2.local doesn't work
May 25 20:06:44 <zmatt> did you reboot cleanly or power-cycle?  did the hostname change not get committed to eMMC ?
May 25 20:06:44 <biggi_> sudo reboot
May 25 20:06:46 <biggi_> i'll pull the power
May 25 20:06:49 <zmatt> no no
May 25 20:07:04 <zmatt> power-cycle is definitely worse
May 25 20:07:29 <kos_tom> zmatt: looks like this: https://paste.ack.tf/944b69
May 25 20:08:55 <zmatt> biggi_: I'm guessing the hostname change somehow just got lost?  I think I've seen changes somehow get lost even after clean reboot, even though that really shouldn't happen
May 25 20:09:21 <zmatt> biggi_: try explicitly doing "sync" after the change and wait a few seconds before rebooting
May 25 20:09:29 <zmatt> are you booting from eMMC or SD ?
May 25 20:09:32 <biggi_> emmc
May 25 20:09:34 <zmatt> hm
May 25 20:09:37 <biggi_> and just do sudo sync?
May 25 20:09:45 <zmatt> no sudo required
May 25 20:09:58 <zmatt> kos_tom: that is indeed not looking great
May 25 20:10:05 <biggi_> after i logged in with beaglebone.local it shows debian@beaglebone2
May 25 20:10:12 <zmatt> biggi_: huh
May 25 20:10:15 <biggi_> but putty won't connect to the host using beaglebone2.local
May 25 20:10:20 <zmatt> that's really bizarre
May 25 20:10:31 <biggi_> i'll just run the command again
May 25 20:10:38 <biggi_> and do a sync then reboo
May 25 20:10:44 <zmatt> no, pointless
May 25 20:10:59 <zmatt> if it shows the correct hostname after login, the change has cleanly been done
May 25 20:11:06 <biggi_> after reboot again now it doesn't even seem to be connecting to beaglebone.local
May 25 20:11:11 <biggi_> this is interesting
May 25 20:11:47 <biggi_> time to reimage
May 25 20:11:51 <biggi_> :shrug:
May 25 20:12:00 <zmatt> kos_tom: what's particularly weird is that usb-networking has no business ever dropping packets, it's a reliable link
May 25 20:12:06 <zmatt> biggi_: that seems a big hasty
May 25 20:12:21 <biggi_> i can't log into it
May 25 20:12:28 <biggi_> and our IT dept can't tell me the IP address easily at all
May 25 20:12:39 <biggi_> It's probably legit the fastest way to get back into it
May 25 20:12:52 <zmatt> beaglebone2 without .local also still doesn't work?
May 25 20:12:56 <biggi_> correct
May 25 20:13:03 <zmatt> I don't see how reimaging would help
May 25 20:13:16 <biggi_> it should bring it back to default hostname correct?
May 25 20:13:51 <zmatt> yeah but... this doesn't make sense.  like, it should be reachable as beaglebone2.local
May 25 20:14:15 <biggi_> let me reimage and then i'll try again and we'll go from there
May 25 20:14:37 <zmatt> like, if it's not reachable as beaglebone2.local right now, I also don't see a reason it would be reachable as beaglebone.local after reflashing
May 25 20:14:39 <kos_tom> zmatt: yeah, I know
May 25 20:14:41 <biggi_> i had already setup the alias on this one too
May 25 20:14:49 <biggi_> it only reached it at beaglebone.local once
May 25 20:14:52 <biggi_> then wouldn't again
May 25 20:15:02 <zmatt> can't you connect to that IP then?
May 25 20:15:03 <biggi_> and the beaglebone2.local (or without local) didn't work either
May 25 20:15:13 <biggi_> i dont' have the ip
May 25 20:15:20 <biggi_> was going solely off hostname
May 25 20:15:28 <biggi_> and i have no way to find the IP without going through our contract IT firm
May 25 20:15:28 <zmatt> isn't that what you meant with "i had already setup the alias on this one too"
May 25 20:15:33 <zmatt> the "alias" being the static ip thing?
May 25 20:15:45 <biggi_> Ah; I could if I set an alias up on my desktop
May 25 20:15:52 <biggi_> Which is where I stopped and asked here before doing that
May 25 20:16:14 <zmatt> this is not making any sense though
May 25 20:16:37 <biggi_> I know. Nothing in my life makes any sense whatsoever.
May 25 20:16:50 <zmatt> is it unable to resolve the hostname, or is it able to resolve it but it can't connect?
May 25 20:16:52 <biggi_> Let me get back to a clean image (should be done soon) and I'll try it again
May 25 20:17:29 <zmatt> instead of reflashing you could just have booted from SD card and changed the hostname on eMMC,
May 25 20:17:53 <biggi_> I didn't know you could do that
May 25 20:18:05 <zmatt> or use the usb-serial console (unless you've disabled the usb gadget)
May 25 20:18:06 <biggi_> I'm EE by the way; hardware guy
May 25 20:18:24 <biggi_> I got thrown into software so I do what I can :D
May 25 20:19:03 <biggi_> Alright reflash done
May 25 20:19:05 <biggi_> Let's go again
May 25 20:19:10 <biggi_> and i'll write the IP down this time XD
May 25 20:20:55 <zmatt> I was also gonna say, try beaglebone2-2.local since avahi still has a bug that causes it to sometimes manage to collide with its own registration, causing it to rename itself... but you were really hasty with reflashing :/
May 25 20:21:13 <biggi_> sudo hostnamectl set-hostname beaglebone2
May 25 20:21:15 <biggi_> right?
May 25 20:21:17 <biggi_> sorry!
May 25 20:21:53 <zmatt> or whatever you want the hostname to be
May 25 20:21:58 <biggi_> for now i'll just use this
May 25 20:22:04 <biggi_> makes it clearer communication
May 25 20:22:09 <biggi_> then: sync
May 25 20:22:12 <biggi_> then sudo reboot?
May 25 20:23:02 <zmatt> the sync is purely paranoia, it shouldn't be needed (but it doesn't hurt)... instead of rebooting you could also try changing the avahi hostname manually, that way you can stay connected while testing the new .local
May 25 20:23:21 <zmatt> sudo avahi-set-host-name beaglebone2
May 25 20:23:29 <zmatt> should make it immediately visible as beaglebone2.local
May 25 20:23:50 <biggi_> ok i did that
May 25 20:23:53 <biggi_> no reboot
May 25 20:24:00 <biggi_> so now i'll have to reconnect with putty right?
May 25 20:24:07 <zmatt> well I'd leave your existing connection open
May 25 20:24:13 <zmatt> and open a second connection
May 25 20:24:15 <biggi_> it's hung up
May 25 20:24:17 <biggi_> kk
May 25 20:24:29 <zmatt> hung up? what?
May 25 20:25:02 <biggi_> after i did the sudo avahi-set it said unable to resolve host beaglebone2: Temporary failure in name rsolution
May 25 20:25:15 <zmatt> what did?
May 25 20:25:20 <biggi_> however my 2nd putty instance connected to beaglebone2.local
May 25 20:25:29 <biggi_> the beaglebone.local putty instance
May 25 20:25:32 <biggi_> is the one that foze
May 25 20:26:09 <biggi_> but now i'm connected with hostname beaglebone2.local as well
May 25 20:26:11 <biggi_> so i think it worked?
May 25 20:26:57 <zmatt> I have not even the slightest clue what you could possibly be describing on your first putty instance... there's no reason for it to ever resolve a hostname while connected, and nothing we did should affect any existing connections (we didn't change network settings)
May 25 20:27:17 <biggi_> man i wish i could stream it somehow
May 25 20:27:36 <biggi_> after i did the last command you said to and hit enter, it just went down a bar and sat there like it was thinking and didn't do anything
May 25 20:27:54 <zmatt> ohh, that's sudo being obnoxious
May 25 20:28:00 <zmatt> hold on, there's a fix for that
May 25 20:32:58 <zmatt> enter a root shell using 'sudo -i' then execute this:
May 25 20:33:29 <zmatt> echo 'Defaults !fqdn' >/etc/sudoers.d/no-fqdn
May 25 20:33:33 <kos_tom> zmatt: just tried on 5.12, same issue
May 25 20:33:45 <biggi_> will do here in just a few :D  updating/upgrading this bb
May 25 20:33:46 <zmatt> biggi_: that should keep sudo from trying to resolve the system hostname
May 25 20:33:50 <biggi_> gotcha!
May 25 20:33:58 <biggi_> This all works now; not sure what happened the first time
May 25 20:34:03 <biggi_> And much easier than setting up an alias
May 25 20:34:11 <biggi_> appreciate the help as always!
May 25 20:35:07 <zmatt> kos_tom: you could try looking at the interface statistics on the beaglebone side to see if the pings are being received and their replies being transmitted
May 25 20:35:16 <zmatt> kos_tom: and check the kernel log for errors/warnings of course
May 25 20:37:54 <kos_tom> ah, the logs have some weird
May 25 20:37:55 <kos_tom> [  249.082184] configfs-gadget gadget: packet filter 0c
May 25 20:37:55 <kos_tom> [  249.082203] configfs-gadget gadget: ecm req21.43 v000c i0000 l0
May 25 20:38:02 <kos_tom> [  249.168830] configfs-gadget gadget: notify connect true
May 25 20:38:19 <zmatt> that looks like debug logs of some sort
May 25 20:40:13 <kos_tom> maybe my magic script setting up the gadget is no longer correct: https://paste.ack.tf/e6615f
May 25 20:40:49 <zmatt> I don't see how that could cause a flaky connection
May 25 20:41:21 <zmatt> oh you're using dma? (cppi41) .. that's disabled on rcn's kernel due to a history of causing reliability problems
May 25 20:41:50 <zmatt> also none of those modprobes should be needed other than libcomposite
May 25 20:42:03 <zmatt> those modules get modprobes automatically when the hardware is detected
May 25 20:42:33 <zmatt> *modprobed
May 25 20:43:32 <kos_tom> I don't have udev running
May 25 20:43:54 <zmatt> ....  i see
May 25 20:44:21 <kos_tom> if I don't load cppi41, then:
May 25 20:44:22 <kos_tom> [    3.331533] udc-core: couldn't find an available UDC or it's busy
May 25 20:44:40 <zmatt> yeah if it's enabled in your kernel config you cannot choose at runtime to not use it
May 25 20:45:32 <kos_tom> probably need musb_hdrc
May 25 20:45:45 <kos_tom> my kernel config is omap2plus_defconfig, stock from upstream
May 25 20:46:19 <zmatt> if this is a regression I suggest bisecting to find when the regression was introduced
May 25 20:47:35 <kos_tom> yeah, of course this is the last resort solution :)
May 25 21:02:25 <biggi_> zmatt: if it makes you feel better i found the issue
May 25 21:02:31 <biggi_> i had an underscore in the hostname
May 25 21:02:33 <biggi_> forgot it's not valid
May 25 21:12:04 <zmatt> they're not? I'll admit I don't think I've ever used an underscore in a hostname, I use dashes
May 25 21:13:06 <biggi_> apparently not?
May 25 21:13:36 <biggi_> https://kb.iu.edu/d/afqs
May 25 21:20:11 <zmatt> a bit weird that hostnamectl lets you set an invalid hostname
May 25 21:20:26 <biggi_> Yup; but it did.
May 25 21:20:38 <biggi_> The 2nd time I did it I literally did beaglebone2 and it worked
May 25 21:20:41 <biggi_> so then i investigated
May 25 21:20:48 <biggi_> instead of bbb_descriptionhere
May 25 21:40:18 <kos_tom> zmatt: tested on 5.4, I can also reproduce the issue, which is odd, since I'm pretty it used to work ok on 5.4
May 25 21:40:37 <kos_tom> tested with a different BBBW, different USB cable, even by powering the BBBW using a separate 5V power supply
May 25 21:40:41 <kos_tom> really odd
May 25 21:46:07 <kos_tom> on the host side:
May 25 21:46:08 <kos_tom>         RX errors 16373  dropped 0  overruns 0  frame 0
May 25 22:47:12 <kos_tom> zmatt: 4.19 works like a charm, 5.4 doesn't
May 26 01:57:15 <set_> I am testing the BBAI w/ the MotorCape. I saw a /lib/firmware/BBAI_BBORG_MOTOR_00A2.dtbo and off to try now!
May 26 02:00:19 <set_> Oops.
May 26 02:00:24 <set_> It does not boot now.
May 26 02:00:34 <set_> Okay. Reflash. Dang it.
May 26 02:03:49 <set_> What pins does the FanCape take up?
May 26 02:09:25 <set_> https://pastebin.com/YRU65EFh is the section for the AI for the MOtorCape.
May 26 02:09:48 <set_> Can I call the 'old' pin numbers like on the BBB when using the BBAI w/ the MotorCape?
May 26 02:09:58 <set_> Or...do I need to find the new pin(s) for usage?
May 26 02:33:28 <set_> Okay, okay. W/ the recommended image, kernel 4.14, the image does not have a normal uEnv.txt file w/ some uboot-overlays sections.
May 26 02:33:35 <set_> What is going on?
May 26 02:36:55 <set_> Okay...so, I add the .dtb for the correct usage or what?
May 26 02:52:52 <set_> Who in the world typed up that .dtb file, i.e. am5729-beagleboneai.dtb?
May 26 02:53:07 <set_> That seems like a lot of work to just not get more into it...
May 26 02:55:52 <set_> On reg = _______ && phandle = ______, what are their...never fret. I will look it up.
May 26 02:56:14 <zmatt> this sounds like you're decompiling a dtb, don't do that
May 26 02:56:24 <zmatt> a decompiled dtb is an unreadable mess
May 26 02:57:23 <zmatt> the 2020-04-06 bbai image does not include overlay support, maybe the latest testing image does (dunno)
May 26 02:58:08 <set_> Okay. No issue.
May 26 02:58:16 <set_> I will keep looking around and learning more.
**** ENDING LOGGING AT Wed May 26 03:00:34 2021