**** BEGIN LOGGING AT Mon Jan 11 03:00:17 2021 Jan 11 14:47:23 is there a way for another driver to access the charge_on bit from fusb303 driver being set here: Jan 11 14:47:24 https://github.com/beagleboard/linux/blob/d99758333215af825ef3e053dc6ba8492cab687a/drivers/staging/typec/fusb302/fusb302.c#L863 Jan 11 14:47:44 ideally without modifying the fusb302 driver Jan 11 14:49:38 sorry, wrong link, https://github.com/beagleboard/linux/blob/219d54332a09e8d8741c1e1982f5eae56099de85/drivers/usb/typec/tcpm/fusb302.c#L754 Jan 11 14:49:49 is the current one i am working with... Jan 11 15:45:53 anyone on here well versed in X11 Jan 11 15:46:04 which part of it? Jan 11 15:46:21 display size Jan 11 15:46:34 that's rather vague Jan 11 15:46:38 what is your problem? Jan 11 15:46:44 my problem is I set my screen size with the -geometry argument Jan 11 15:46:50 but I get the following one second Jan 11 15:47:26 https://imagebucket.io/uploads/view/mysjk/ Jan 11 15:47:49 I am not sure why the program is not using the entire space Jan 11 15:48:30 this is on 7" touch screen Jan 11 15:48:32 what am I looking at? Jan 11 15:49:21 that is the screen shot of what I get when I start X11 with xinit -geometry 800x480-0+0 Jan 11 15:49:38 then lauch a program called pylonviewer Jan 11 15:49:52 its a package made by Basler to drive their cameras Jan 11 15:53:01 what are those black squares? Jan 11 15:53:09 i am not sure Jan 11 15:53:26 i did not really pay attention to them Jan 11 15:53:30 not part of hte program Jan 11 15:53:39 when I first start with xinit Jan 11 15:53:41 they are not there Jan 11 15:53:56 are you trying to run just "pylonviewer" as the only X client? Jan 11 15:54:02 no window manager? Jan 11 15:54:03 yes Jan 11 15:54:10 right no window manager Jan 11 15:54:20 since I will only have this program running i figured I did not need it Jan 11 15:54:28 that should be fine Jan 11 15:54:53 i guess a manager would just allow me to maxmize right Jan 11 15:54:59 what happens if you start it as "xinit pylonviewer" Jan 11 15:55:00 maximize* Jan 11 15:55:08 hmmm let me try Jan 11 15:55:13 never combined before Jan 11 15:55:18 one sec Jan 11 15:58:37 ha that worked!!! Jan 11 15:58:45 you are a genius Jan 11 15:58:53 why would doing it in two steps matter Jan 11 15:59:37 I'm not sure what went wrong for you Jan 11 15:59:55 i can just run with this Jan 11 16:00:03 I simply suggested what I would've tried first Jan 11 16:00:26 one quick one when I do the xinit I do not get my command prompt back Jan 11 16:00:44 and so I always ctrl+z Jan 11 16:00:49 to get my prompt Jan 11 16:00:54 and then I can type stuff Jan 11 16:01:13 is there a way to launch a server and keep the focus on my terminal Jan 11 16:01:23 xinit ... & Jan 11 16:01:31 aha Jan 11 16:01:34 cool Jan 11 16:01:41 thank you thank you Jan 11 16:02:05 now the only thing that remains is to ssh into the bbai without a usb Jan 11 16:26:30 anyone know what the expected current draw of say the beaglebone black is when shut-down? I'm getting ~500uA, which is hugmongus Jan 11 16:27:07 does that seem right? is the pmic that bad at being in power off state? Jan 11 16:35:47 hmm, found some notes from when I did pmic testing that say "0.0 mA" ... but that was powered via the battery terminals rather than the barrel input Jan 11 16:37:58 pmic says OFF current is typ 6 μA Jan 11 16:39:03 *pmic datasheet Jan 11 16:40:31 though that says "Total current into VSYS, VINDCDCx, VINLDO", which leaves current drawn into the AC/USB inputs undefined :P Jan 11 16:42:50 hmmm, that is quite odd. Jan 11 16:43:13 wondering if there is something different with the pocketbeagles octavo package Jan 11 16:44:10 if you're somewhat sure about the value you measured you could try asking Octavo about this Jan 11 16:51:09 poking some more at the localized current draw rather than battery now... Jan 11 16:52:18 the lm61460 is pretty great. it seems to have really low quiescent draw. Jan 11 17:54:08 Does anyone know the standard that the BeagleBoneBlack uses for the uSD card reader, as well as the speed class? Jan 11 17:57:40 Paul87: it uses 48 MHz bus speed (so 24 Mbit/s max raw transfer speed) Jan 11 17:58:19 awesome, thanks, would it prob be better to use the USB slot for a higher transfer speed then? Jan 11 17:58:41 on-board eMMC is probably fastest, the usb controller is fairly potato Jan 11 17:59:06 yeah, my issue is the size of the onboard eMMC Jan 11 17:59:06 usb might still be faster, dunno, but it also uses a lot of cpu time Jan 11 17:59:19 why? are you using it for storing video or something? :P Jan 11 18:00:00 (I know, stuff is incredibly bloated nowadays, it sucks...) Jan 11 18:00:20 Im running cmd-Line debian, using the Beagle as a middle man, since we have devices that don't fit the security requirements to interface directly with the network. Jan 11 18:00:53 files get dropped into the beagles SD card and then through a script are pushed onto network shares Jan 11 18:01:05 that sounds awful Jan 11 18:01:45 haha its not ideal, but its kind of the difference between not being able to use the device at all or this solution Jan 11 18:02:29 so you're using the beaglebone as the network-side of an air-gap to another machine? Jan 11 18:02:35 probelm we were having now though is files going over the alotted 16gb cards we were using Jan 11 18:02:37 (a non-networked machine) Jan 11 18:02:39 no air gap Jan 11 18:03:13 then I'm confused about what you're doing Jan 11 18:03:39 how do the files get onto the beaglebone? Jan 11 18:03:53 Device ------>USB-Beagle-Ethernet------->Server Jan 11 18:04:29 the usb between the beagle and the device is using the local area network thing that the beagles come with Jan 11 18:04:56 you realize that this doesn't really provide more security than just connecting them to the network via a restrictive firewall? Jan 11 18:05:31 (in fact, it provides less security than connecting them to the network via a firewall) Jan 11 18:06:12 regardless, you could just mount the fileshare on the beaglebone and drop files directly into it from the device Jan 11 18:06:24 yes that is how it is done Jan 11 18:06:41 so then the file is never stored on the beaglebone, why would you still need an sd card? Jan 11 18:06:46 the fileshare doesnt stay connected though, it only mounts when a sync button is clicked Jan 11 18:07:21 or alternatively, create a fileshare on the device and mount that and the server fileshare on the beaglebone and transfer the files Jan 11 18:08:05 the files are dropped from the device that isnt connected to the network and when the sync button is pressed the beagle mounts the share and forwards the files onto the share and then unmounts after its done Jan 11 18:08:41 yes I understand that description, I just don't understand why you'd do it like that Jan 11 18:09:58 I'm not actually the designer of the whole process, there are some weird things and rules with how stuff has to be done here, but i just needed to find out what the capacity of a uSD card could be on the device, as well as the speed. Jan 11 18:09:59 nor why you don't mount the filesystem directly on the device (e.g. setting up the beaglebone as router that allows the device _only_ access to the fileserver) Jan 11 18:10:33 particularly I do not like having a device with only a fastethernet port moving data, when we are connected through a 1gig access port Jan 11 18:10:47 capacity is not a relevant question, if the host operating system (i.e. linux) supports cards larger than 2 GB then it supports any card capacity that eists Jan 11 18:11:18 yes, the beaglebone also sounds like a bad choice for this application Jan 11 18:11:37 so the SDSC, SDHC, SDXC standards dont pertain to the hardware? Jan 11 18:12:30 nope. SDHC and SDXC don't even have protocol difference, that's mostly just a marketing term Jan 11 18:12:51 What I was trying to figure out was that if we put a card in over 32gb would the beagle beale to use it? Jan 11 18:12:54 SDSC and SDHC have a protocol difference, but that just means software needs to know how to deal with it Jan 11 18:13:09 a 32GB card does not behave differently from a 4GB card Jan 11 18:13:34 the only way for a device to support one but not the other is if they do something really dumb or bizarrely have some explicit check Jan 11 18:13:51 okay, thank you for clearing that up. Jan 11 18:15:35 SDXC also tweaked a few definitions with regard to performance measurements, and has some new bit the host can use to tell the card it's allowed to draw more power (to get better performance) ... but both of these just depend on software, and neither creates backwards-incompatibility Jan 11 18:16:43 okay, we had a 512gb card that did not work, and we had a vendor telling us the reason was because it wasnt supported. Jan 11 18:17:06 vendor is full of shit. what was the symptom? Jan 11 18:17:44 it would not write to the card, from what I'm told. Didnt have the pleasure of troubleshooting the issue Jan 11 18:17:46 note that SDXC cards are by default formatted as exFAT instead of FAT32.. though for use on linux you'll probably want to reformat it anyway Jan 11 18:18:18 I think since the devices connected to the beagles are Windows we cant use ext formats Jan 11 18:18:35 why does that matter if you're not using the sd card to transfer files? Jan 11 18:18:54 anyway, you can reformat it as FAT32 on linux... windows refuses to do that for cards that big, but it will happily accept them Jan 11 18:19:13 (max for FAT32 is 2 TB) Jan 11 18:19:56 awesome man thanks for the info. I'm more of the network guy, but was asked to look up info pertaining to this, and I said no problem, so i greatly appreciate your help. Jan 11 18:22:28 hahaha, I'm more of a microcontrollers guy, so when asked to build a computer, I said no problem, lets add usb-typeC and fpga interface while we're at it! Jan 11 18:22:33 like, if I wanted a device I didn't trust to transfer files to a fileserver, I'd just create an account for it on the fileshare with access limited to only a specific directory for this purpose, and connect the device to the network via a firewall that only allows access to the fileserver. or if I were extremely paranoid I'd use a separate fileserver process on a separate port, sandboxed to only have ... Jan 11 18:22:39 ...access to that directory Jan 11 18:22:53 Tis how you never stop learnin Jan 11 18:23:43 Paul87: that would actually isolate the device, while allowing it to log in on a beaglebone that itself has access to the network means it's not actually isolated from the network Jan 11 18:25:23 (though this indirect route does mean it's probably isolated enough for most purposes, it might just not be against sufficiently advanced targeted attacks... depends a bit on why exactly the device is untrusted) Jan 11 18:27:46 the device in question has no outside access and is actually used for taking images, the only way i could see it being an issue is if somebody using it wanted to infiltrate, and in that case they could just plug it right into the network Jan 11 18:28:37 its not so much that we think it is an issue security wise, but more like the security standards for a device to be on the network could not be met due to the way the instrument device was imaged Jan 11 18:29:38 and how it allowing it to access a beaglebone that itself is connected to the network okay, but giving it extremely limited direct access via a firewall not okay? Jan 11 18:29:39 like installing certain anti-malware/ virus protection/ Anomololy detection Jan 11 18:30:44 i agreed with you there, but then these devices will be scattered through out the network, and the costs assoicated with that many firewalls is another factor. I'm not arguing there isnt a better way, this is how they were doing it when i got hired. Jan 11 18:31:18 yeah, and maybe it was good enough, except it isn't really since the performance sucks bad enough to apparently make it worthwhile for you to spend this much time on it :P Jan 11 18:33:00 as a compromise I'd at least suggest the fileshare-to-fileshare sync method (i.e. create fileshare on this device, mount it and server fileshare on the beaglebone or a faster placement for it) to avoid having to intermediately store the files Jan 11 18:33:09 agreed, the only thing here is, instrument is being used and work not being held up, vs not working at all. I believe we also have a team looking at different avenues as well. Jan 11 18:33:33 i believe that is the latest change that was made, now that you mention it. Jan 11 18:33:33 and probably replace the beaglebone with something else, preferably with two gigabit ethernet ports Jan 11 18:33:52 YES! Jan 11 18:33:53 if it is then why are you asking about sd card / usb storage? Jan 11 18:34:08 if you're doing fileshare-to-fileshare sync then the data is never stored by the beaglebone Jan 11 18:34:12 remeber network guy here. I cringe when I hear fastethernet Jan 11 18:34:44 we have a device running an image that will only accept the usb-storage exchange Jan 11 18:34:44 yeah the AM335x supports gigabit (in fact it supports two gigabit ethernet ports), but the BBB has a 100Mbit PHY attached to it Jan 11 18:35:00 oh Jan 11 18:35:08 well that changes everything Jan 11 18:35:26 it's also not what you said earlier Jan 11 18:35:48 "the device is using the local area network thing that the beagles come with" Jan 11 18:35:49 yep, annoying little pre-canned devices from vendors that people buy and then ask us after to get it working Jan 11 18:36:10 so you're using the beaglebone to pretend to be a usb stick? Jan 11 18:36:31 yeah, basically in the case of the SD card one Jan 11 18:39:03 ugh... that definitely makes avoiding intermediate storage harder.. like you could use some kind of network block device storage (NBD or iSCSI) server, have the beaglebone as client to that and share it as usb mass storage gadget Jan 11 18:40:40 I still question the use of a beaglebone for this, but I guess it was just something that happened to be at hand Jan 11 18:40:52 yeah, I wanted to see if there might be another single board device that would support both issues better than the beagle, but again its not necessarily my avenue Jan 11 18:40:57 I'd probably use one too if I needed this just because we have 'em lying around Jan 11 18:41:55 yeah thats how it started here I believe, it was down to the last minute and a project needed to be started in a couple of days and this was the solution someone put together in a night Jan 11 18:42:14 that's exactly what this solution sounds like Jan 11 18:42:32 and as always, a quick hack that works *just* well enough has a tendency to stick around forever Jan 11 18:43:33 so does this thing have network capability at all? Jan 11 18:44:58 it also sounds like just sticking an usb disk into it and then plugging that into a device responsible for sync'ing it to the server would probably be faster than this, but I guess having to physically replug it is annoying Jan 11 18:46:21 (maybe someone has made something that can switch a usb device between two hosts, like a KVM switch but for usb) Jan 11 18:48:12 USB's are banned from use lol Jan 11 18:48:21 ? Jan 11 18:48:26 sticks Jan 11 18:48:36 but.. you're usnig a usb stick, just a really big, ugly, slow one Jan 11 18:48:49 that was the original way Jan 11 18:48:57 yeah, i know lol Jan 11 18:49:25 I guess this keeps people from finding a USB laying on the ground and plugging it in and infecting stuff Jan 11 18:49:32 a usb stick is some kind of storage with a chip that has a usb device port and implements the usb mass storage class protocol Jan 11 18:50:25 I mean fair, but this would be something limited to this specific purpose.. like, usb disk would never move, it would only be plugged between this device and the sync device (which could be the beaglebone right next to it) Jan 11 18:50:44 you could tape it down if need be :P Jan 11 18:51:47 (and it would mean you could replace the beaglebone by anything that has ethernet and a usb host port, instead of requiring a usb device port which is much rarer) Jan 11 18:51:54 use the chain from the pens at the bank Jan 11 18:53:25 here at work we also have a usb stick with like a 30cm foam block attached to it with two wide banks of bright pink tape, so it can't exactly be overlooked :P Jan 11 18:53:36 *bands Jan 11 18:53:59 though that's more to keep people from misplacing it Jan 11 18:54:27 haha, sounds like the block of wood and the bathroom key idea Jan 11 18:55:19 yeah, except weighing nothing to avoid putting physical stress on a usb port Jan 11 18:55:58 alright man, i gotta grab some food, i appreciate the chat. Jan 11 21:19:39 is it possible to mount a usb flash drive partition on the board? or can it only be done using a micro sd card Jan 11 21:20:39 why would you think you can't mount a usb drive? on a linux system that has a usb host port Jan 11 21:21:16 I know, but I was skeptical because Molloy's book only talks about mountain an SD card but not a usb flash drive Jan 11 21:21:41 good to know though, since I'd prefer to use the sd card to re-flash the emmc instead of storing important files on it Jan 11 21:21:57 mounting* Jan 11 21:22:33 the usb controller on the bbb isn't great though, so dunno how it performs Jan 11 21:22:43 and you can't boot from a usb drive Jan 11 21:23:34 yeah, though the bbgw has 4 usb ports, so maybe they put more emphasis on usb performance Jan 11 21:24:02 no, and the more usb devices you attach the more the bbb will struggle Jan 11 21:24:53 there's nothing you can do external to the AM335x to improve usb on the AM335x ... the only thing that could improve it is improving the linux driver Jan 11 21:25:57 having said that, I almost never use usb on the BBB so maybe things have already improved over time, I probably wouldn't know Jan 11 21:27:00 it's not encouraging that the 4.19.94-ti-r51 still has DMA disabled for usb Jan 11 21:27:21 *the 4.19.94-ti-r51 kernel Jan 11 21:27:30 only external usb I would need is one for storage space, so performance isn't all that crucial Jan 11 21:28:23 hmm, seems like mine is 4.19.94-ti-r57 Jan 11 21:29:03 unlikely to make a difference, but you can do grep CONFIG_MUSB_PIO_ONLY /boot/config-$(uname -r) Jan 11 21:29:23 (if this config var is =y then DMA is disabled for usb) Jan 11 21:29:51 yeah, it's =y Jan 11 21:30:12 which means all usb data transfer involves the cpu manually copying data between ram and the usb controller Jan 11 21:31:31 so if DMA was enabled, then that wouldn't be the case (better performance)? Jan 11 21:33:04 it should yes, but I think DMA was disabled because of reliability problems (i.e. probably driver bugs) Jan 11 21:49:32 does the bbb accept usb 3.1? Jan 11 21:50:04 it has no superspeed lines if thats what you're asking Jan 11 21:50:09 "accept" ? any usb3 device is backwards compatible with usb2, hence the bbb will _accept_ any usb3 device Jan 11 21:51:20 zmatt: there is actually a defined use case for a fixed superspeed only device that is attached permanently and has no usb2.0 data Jan 11 21:54:14 actually, it's somewhere in between: they're required to implement usb2 but it's allowed to be a trivial implementation: "A USB 3.1 peripheral device must provide support for both Enhanced SuperSpeed and at least one of the USB 2.0 speeds. The minimal functional requirement for the USB 2.0 speed implementation is for a device to be detected on a USB 2.0 host and allow system software to direct the ... Jan 11 21:54:20 ...user to attach the device to an Enhanced SuperSpeed port." Jan 11 21:55:05 so yeah, I guess that means my statement is not quite true: while the BBB might _accept_ any usb3 device, it might not be useful Jan 11 21:57:17 hmm, it does seem that there is a means to send the usb2.0 data via the usb ss lines. Jan 11 21:57:35 bypassing the usage of the usb 2.0 lines entirely Jan 11 21:57:50 like: https://www.ioiusb.com/Hub/U3H442S.htm Jan 11 21:58:56 as long as I can plug a usb 3.1 flash drive into the board and the board can read and write to it Jan 11 21:59:16 also "For product installations where support for USB 3.1 operation can be independently assured between the device and the host, such as internal devices that are not user accessible, device support for USB 2.0 may not be necessary. USB 3.1 device certification requirements require support for USB 2.0 for all user attached devices." ... not quite sure if that implies user attached devices are ... Jan 11 21:59:18 yea, it should work at usb2.0 speeds Jan 11 21:59:22 ...required to be properly functional via usb 2.0 Jan 11 22:00:05 Zalymo: regardless of whether the standard actually requires it (what the standard requires doesn't always guide real-world devices anyway), I'd expect most usb 3 devices to be backwards compatible with usb 2 Jan 11 22:00:11 i think it's the difference between on-board devices eg: and rtc module, vs hot-plugged Jan 11 22:01:10 I,ve never seen what i mentioned in the wild, no sure exactly how that would be declared either. Jan 11 22:06:46 is it possible to run executables if they are stored on the flash drive? from the bbb Jan 11 22:07:26 what underlying storage is used is irrelevant for that Jan 11 22:08:28 filesystem is slightly more relevant, since non-linux filesystems may not have the ability to mark individual files as executable. though a common workaround for that with e.g. FAT32 is to just mark all files as executable (this depends on the options used when mounting the fliesystem) Jan 11 22:08:34 *filesystem Jan 11 23:49:40 if you are connected to the bbb by usb and ethernet and you ssh Jan 11 23:49:51 does usb always win in terms of how you connect Jan 11 23:55:55 if you connect by IP then it will depend entirely on the IP you connect to (which is different per interface), the ethernet one may also be reachable by hostname (provided by the router on ethenet), if you connect by .local address then it will be arbitrary Jan 11 23:57:31 in the default configuration the usb networking interfaces have static IPs (192.168.7.2 for RNDIS, 192.168.6.2 for CDC-ECM/NCM), the Ethernet interface will use DHCP to acquire an IP address from the local router Jan 12 00:42:12 so if I wanted to connect via the ethernet I just would not attached the usb and allow my computer to set an IP that I would use for the ssh Jan 12 00:43:05 ??? Jan 12 00:43:38 the ethernet will use DHCP Jan 12 00:43:39 whether or not you're connected via usb has relevance to whether you can reach the beaglebone via ethernet Jan 12 00:43:54 *has no relevance Jan 12 00:44:20 ok but I want to connect via ethernet so what debian@IP should I use Jan 12 00:46:11 the IP of the beaglebone on your ethernet network... if you're lucky you can use its hostname (debian@beaglebone) but that depends a bit on your router, otherwise just check what the beaglebone's IP is (either in your router or more easily in the beaglebone (after logging in via usb) using "ip addr show eth0") Jan 12 00:47:24 https://pastebin.com/Y5Ldb7vU Jan 12 00:47:41 or if you're using mac or linux (or _maybe_ win10 but it's still not clear to me whether or when it works on windows) you can connect to debian@beaglebone.local but then you should avoid being connected via usb at the same time since it would make it undefined whether you connect via ethernet or usb (but only in that case) Jan 12 00:47:57 ok Jan 12 00:47:57 well there's your answer, 10.42.0.250 Jan 12 00:48:15 (or fe80::e615:f6ff:fef4:b500 for IPv6) Jan 12 00:48:31 so i would disconnect and then ssh again with that ip Jan 12 00:48:54 so you tried connecting by hostname and that didn't work? Jan 12 00:49:21 like, I normally never connect to devices by IP since that's just annoying Jan 12 00:51:54 naming dozens of devices is annoying too Jan 12 00:51:55 but if connecting by hostname doesn't work then yeah Jan 12 00:52:12 mru: not as annoying as remembering their IPs Jan 12 00:52:32 I know which subnet they're on Jan 12 00:52:46 only need to remember the last number Jan 12 00:53:06 the alternative would be to name them foo-1, foo-2, etc Jan 12 00:53:12 and then have the same problem Jan 12 00:53:25 except those are at least stable Jan 12 00:53:29 and shorter Jan 12 00:54:22 the IP addresses are stable Jan 12 00:55:09 if the dhcp server is working properly Jan 12 00:55:31 and mac addresses are stable, obviously Jan 12 00:55:48 perhaps, perhaps not... I see no reason to even have to worry about it when you can just connect by hostname Jan 12 00:56:08 but then I have to first give it a hostname Jan 12 00:56:11 that's extra effort Jan 12 00:56:20 they *have* hostnames regardless :P Jan 12 00:56:34 many of them have the same default hostname Jan 12 00:56:35 and I'd personally definitely want those to be unique yes Jan 12 00:56:56 also because it's shown in the shell prompt remindimg me what device I'm logged in on Jan 12 00:57:10 ok the beaglebone.local works Jan 12 00:57:15 but it is giving me that key error Jan 12 00:57:25 where I would have to remove it and regenerate Jan 12 00:57:36 MattB000ne: remove it and regenerate? Jan 12 00:57:48 my situation is probably different from the average tinkerer Jan 12 00:57:49 are you talking about the known hosts error? Jan 12 00:58:07 WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! Jan 12 00:58:16 is that known host Jan 12 00:58:20 error? Jan 12 00:58:38 yes that just means the ssh server's public key is different from the last time you connected to "beaglebone.local" Jan 12 00:58:53 lots of prototype boards that are used for a few days only Jan 12 00:59:07 either because that was a different beaglebone or because you reflashed the beaglebone (and didn't preserve the ssh private key) Jan 12 00:59:42 mru: hey, if it works for you, you do you :) Jan 12 00:59:44 will my computer keep beaglebone.local consistent Jan 12 01:00:22 MattB000ne: when you connect to a .local address you computer will just yell on the network "HEY, who here is beaglebone.local?" Jan 12 01:00:23 "real" computers and long-lived devices do have names Jan 12 01:00:33 ok cool Jan 12 01:01:01 kind of like arp but for names Jan 12 01:01:04 MattB000ne: if you have multiple beaglebone, be sure to give them unique hostnames... Jan 12 01:01:05 would bbai have a beaglebone.local Jan 12 01:01:15 (or just preemptively do that) Jan 12 01:01:34 sudo hostnamectl set-hostname namegoeshere Jan 12 01:02:10 (I don't know if avahi automatically picks up on the hostname change, just to be sure you could "sudo systemctl restart avahi-daemon" after changing hostname) Jan 12 01:02:47 and yes I think the bbai also has "beaglebone" as default hostname, not 100% sure though Jan 12 01:03:50 you can check the hostname using "hostname", or iirc it's shown in the default shell prompt (not 100% sure since I always replace the default bashrc by my own so I don't remember the default prompt with certainty) Jan 12 01:08:48 why would you need a custom shell Jan 12 01:09:30 a custom bashrc? it just sets my preferred defaults/config for the shell (including the prompt) Jan 12 01:39:08 what port would I use for ethernet Jan 12 01:44:00 the default Jan 12 01:45:55 port number of a server normally does not depend on which interface you're using (unless you explicitly configured an interface-specific listener, which some servers may support (sshd does)) Jan 12 02:39:11 i am using filezilla to transfer some files Jan 12 02:40:38 ok got it to work with sftp:// Jan 12 02:40:43 then beaglebone.local Jan 12 02:41:02 hi ther Jan 12 02:41:17 hi Jan 12 02:43:54 i see your playing having fun Jan 12 02:44:07 i dont know about fun Jan 12 02:44:10 but i try Jan 12 02:44:32 lol... well thats all that counts Jan 12 02:45:35 Fun? Jan 12 02:45:38 Did someone say fun? Jan 12 02:46:40 its always about fun Jan 12 02:46:54 Yeppers. I can second that notion. **** ENDING LOGGING AT Tue Jan 12 02:59:57 2021