**** BEGIN LOGGING AT Fri Dec 04 02:59:56 2020 Dec 04 15:10:51 mer, post cuircuit surgery, no luck... seems the 32khz crystal is also necessary to get the device to boot up at startup.... now i gotta make the dts for the rtc onboard first and make sure it is loaded before trying to start the wifi. Dec 04 15:44:25 konsgnxx: ehh, yes the wl18xx requires that VIO, VBAT, and the 32 kHz clock are present and stable before WL_EN or BT_EN is driven high Dec 04 15:46:08 which is documented in the datasheet (power-up sequence), the hardware integration guide, and probably more places :P Dec 04 15:47:04 you're getting the 32 kHz clock from an rtc? why? Dec 04 15:47:25 that creates an awkward dependency between normally unrelated devices Dec 04 15:47:57 why not? Dec 04 15:48:00 ahh Dec 04 15:48:20 well it keeps me from having a bunch of clocks making the same osc\ Dec 04 15:49:11 but yea, next version will have that. for this one though, gunna figure out how to controd driver loading sequence Dec 04 15:49:48 also, zmatt, got any idea about that gpmc dependency for the sdio comms? Dec 04 15:50:31 I was gonna say the BBB can output its 32768 Hz osc signal on clkout 1 (P9.41) but then I remembered you were using a pocketbeagle :P Dec 04 15:50:34 the what? Dec 04 15:50:57 gpmc and sdio have absolutely nothing to do with each other Dec 04 15:50:58 one sec, lemme pull up some links Dec 04 15:51:24 https://github.com/beagleboard/bb.org-overlays/blob/92de6d0f646c5c7e53c4ea8b488d93f47bf62c06/src/arm/BB-BONE-WL1837-00A0.dts#L151 Dec 04 15:52:02 that is confusing me alot, seems the same on black wireless, the gateway cape that only works with this dts, and the green wireless Dec 04 15:52:05 sounds like you're just getting confused by the obnoxious habit of TI of naming pins after their "primary" function (which mostly just creates confusion when that pin isn't used for that function) Dec 04 15:52:27 but mode0 is the gpmc cs function Dec 04 15:52:37 it's not in gpio mode Dec 04 15:52:44 then that's a bug Dec 04 15:52:56 the comment clearly indicates the intention was using it as a gpio Dec 04 15:54:20 phew, imma try to fix that and see if it still functions. Dec 04 15:55:41 you can also check am335x-boneblack-wireless.dts for inspiration Dec 04 15:56:05 will do Dec 04 15:56:54 Thank you! Dec 04 15:57:15 honestly I'm not really sure why the level shifter enable signal isn't simply tied to 3v3 Dec 04 15:57:54 power savings? Dec 04 15:58:11 chip selecting other sdio devices? Dec 04 15:58:21 1. no 2. not allowed Dec 04 15:58:38 what if you try really really hard? Dec 04 15:59:14 not supported by linux Dec 04 15:59:33 disabling the level shifter would effectively cut power to the wl18xx by deasserting WL_EN Dec 04 16:01:01 also, I'm talking about the bbbw here where the wifi is integrated and nothing else can be on that bus (it's not shared with expansion header pins) Dec 04 16:02:19 indeed, unless you solder on an sd card holder on top. Dec 04 16:02:56 they even placed convinient resistors to make easy-to-access solder points. :) Dec 04 16:03:18 in retrospect, if they used the osd335x-sm then they could have used 1.8v for the io supply domain (VDDHV5) used for the formerly-ethernet-now-wifi/bt pins, and avoided the need for a level shifter entirely Dec 04 16:03:36 (possible pinouts for wl18xx on VDDHV5: https://goo.gl/Jkcg0w#gid=146612406 ) Dec 04 16:03:48 but maybe the osd335x-sm didn't exist yet when the bbbw was designed Dec 04 16:04:10 it's thanks to those resistors my circuit surgery was possible. and with 7 lines going into one of the translators, i didn't even have to flip the one in the center. Dec 04 16:05:21 I'm confused, what are you talking about? Dec 04 16:05:35 sorry, ranting. Dec 04 16:05:48 don't mind me. Dec 04 16:06:04 wait what circuit surgery did you do? Dec 04 16:07:01 I will just say, there needs to be a collection of circuit surgery tips. I had the lines of data going into and out of the translators flipped backwards, so i had a bunch of resistors to tombstone and wires to crisscross Dec 04 16:08:36 you mean you were exposing the wl18xx to the 3.3V side of the level shifter? Dec 04 16:09:54 noooo Dec 04 16:10:49 not that, just used the resistors on one side of the translator, tombstoned some, rotated others and added wires between the resistors other ends and the pads free'd up Dec 04 16:11:52 I'm so confused Dec 04 16:12:44 oh you're patching a cape designed for the BBB onto a pocketbeagle? Dec 04 16:12:53 or something? Dec 04 16:14:33 nope, made a custom cape for pocket, borked the design, and had to do surgery to fix the traces so they went to the right place Dec 04 16:14:47 ah Dec 04 16:14:50 I can just send a photo Dec 04 16:15:10 no, that explanation finally makes sense Dec 04 16:15:16 nvm, pastebin doesnt seem to take photos Dec 04 16:15:35 woot! Dec 04 16:29:56 probably the worst thing I've heard regarding patching a prototype design to get it working was for the rad1o (cccamp 2015 badge)... the footprint they had used the wrong pinout for the microcontroller, and they didn't have time to make a second prototype, so to patch the prototype they had to access some of its BGA balls by carefully drilling some new vias into the pcb... and more specifically drill ... Dec 04 16:30:02 ...them _at an angle_ because traces were in the way Dec 04 16:30:39 which seems like a downright heroic patch job Dec 04 16:31:25 woa! Dec 04 16:31:33 that sounds proper terrifying Dec 04 16:31:43 how would you even bond that? Dec 04 16:32:51 I mean, I don't know if they had to do the patch on a populated board or if they had an unpopulated one to patch and then populate... I hope the latter Dec 04 16:33:34 btw, switching to mode7 for the Bone-WL1837 dts breaks wifi. i even tried gpio-hog high. (this is with a beaglebone black + gateway cape setup) Dec 04 16:33:58 using a gpio hog obviously only works if the pin is actually in gpio mode Dec 04 16:33:59 in either case, that a lot of work. wow. Dec 04 16:34:16 yup, i meant mode7+ gpio hog Dec 04 16:40:37 bah! could it be an issue related to timing of wl startup and trying to talk to it where a gpmc cs gets strobed at just the right time? Dec 04 16:40:55 gpmc is not being used in any way Dec 04 16:41:08 and the lsbuf output enable needs to be constant-high, not "strobed" Dec 04 16:41:43 it's possible the gpmc cs output is output-high by default and they're (accidently or intentionally) abusing that Dec 04 16:44:00 a test would be to set that pin to input and wire in 3v3? Dec 04 16:44:12 again, I'm not sure why you'd gpio-control the level shifter enable in the first place instead Dec 04 16:44:18 instead of tying it high Dec 04 16:44:42 if you're going to wire it to 3v3 you don't need to do anything with the gpio in your overlay Dec 04 16:45:20 but are you saying the gpio hog is too late? Dec 04 16:45:26 i don't want to bork it, so i will make sure the mux is set to gpio and remove the hog.. right? Dec 04 16:45:37 maybe, it didn't work Dec 04 16:45:45 the mux is gpio by default, gpios are input by default Dec 04 16:46:02 so remove that line that muxes to 0 Dec 04 16:46:10 ? Dec 04 16:46:17 wait actually I don't know the defaults on the pocketbeagle Dec 04 16:46:24 if cape-universal is enabled Dec 04 16:46:27 im on beaglebone black Dec 04 16:46:30 oh Dec 04 16:46:32 uhh Dec 04 16:46:51 testing with black/gateway cape to see how that buff pin functions Dec 04 16:47:17 so you're saying it works with the pin configured to mode 0 but not with mode 7 + gpio hog ? Dec 04 16:47:23 yes. Dec 04 16:47:55 ew, so they probably are in fact abusing the gpmc chip select as an output-always-high signal Dec 04 16:49:03 does this cape have a pull-down on that pin? Dec 04 16:49:40 can't tell, e14 never released the schematics Dec 04 16:50:01 otherwise a pull-up (e.g. 1KΩ) to 3v3 would ensure the level shifter is enabled by default, without the risks of tying it directly to 3v3 Dec 04 16:50:04 oh Dec 04 16:50:08 sidenote, i just lost my coffee. it dissapeared. i blame the gpmc Dec 04 16:50:21 good idea Dec 04 16:53:56 does // comment out in dts files? Dec 04 16:54:02 yep Dec 04 16:54:13 thanks Dec 04 17:01:29 seems to be working with a 1.5k resistor pullup Dec 04 17:04:07 aaaand now its boot-looping... Dec 04 17:04:16 break time! Dec 04 18:41:37 welp, resistor trick seems to be intremittent success. Dec 04 18:41:47 gunna try a direct line Dec 04 18:57:21 . thouroughly confused... still intermittent Dec 04 18:57:50 used a 50 ohm Dec 04 19:00:47 konsgnxx: what is this project you are working diligently on? Dec 04 19:02:03 ... a bunch of stuff, wifi with 5ghz, usb type c, rtc, ohh and an fpga too. Dec 04 19:02:21 and a smart battery. Dec 04 19:02:42 and a low quiescent 5v regulator Dec 04 19:05:23 scratch my earlier statement, seems like it just takes forever to load the driver but it seems to be coming up Dec 04 19:06:12 ohh right, another part of the project will be to place the uboot on a spi flash so i can put some crypto keys there too. Dec 04 19:37:34 interesting, the rtc does actually start up and output values,but the 100k pullup might be a little weak, the input to the wl1837 has a 1v peak and looks more like a saw than a square. Dec 04 19:46:09 phew, now its alot more 1.8ish. Dec 04 20:03:22 "seems like it just takes forever to load the driver" ... weird, I don't recall seeing that myself Dec 04 20:18:50 konsgnxx: like, a few boot log snippets of a bbbw here: https://pastebin.com/raw/bEc2suiq Dec 04 20:19:12 80 sec, not too bad Dec 04 20:19:30 80 ? Dec 04 20:19:36 woa, i have it at the 80.xx mark Dec 04 20:20:33 yeah, I politely declined to have that sort of boot time Dec 04 20:21:21 its weird that the wlan regulator disabled at 30, then wlcore loaded at 80 Dec 04 20:21:35 that sounds normal Dec 04 20:21:41 as in Dec 04 20:23:03 if the driver hasn't been loaded yet during early boot (because it's compiled as module and the system is taking its sweet fucking time to load it) then the regulator device (whose driver is built-in) will see no clients for the regulator's output and it'll disable it until some device expresses a desire for it Dec 04 20:24:31 try it without initramfs. the default bb.org images for some reason use initramfs, but it's not needed and slows boot down quite a bit Dec 04 20:25:48 I also noticed boot is a bit slow on my bbb and the pru takes a while to be available after boot Dec 04 20:26:45 you can move/rename /boot/initrd-$(uname -r) out of the way to test temporarily, for a permanent solution you'd normally remove initramfs-tools, but bb.org kernel packages probably still have a bogus dependency on it so I have a tiny empty initramfs-tools package you can install to satisfy the dependency: https://liktaanjeneus.nl/initramfs-tools_1.0_all.deb Dec 04 20:28:10 if your system isn't the latest image then cape-universal also slows things down a lot (fixable by disabling it (n/a on pocketbeagle) or updating the bb-customizations package and updating your initramfs (if still using it)) Dec 04 20:29:17 boot graph on this bbbw-1: https://liktaanjeneus.nl/boot-bbbw.svg Dec 04 20:30:42 that's nice, how did you generate that svg, processing dmesg text? Dec 04 20:30:54 systemd-analyze plot >boot.svg Dec 04 20:31:11 really cool, didn't know that command Dec 04 20:32:27 the fsck makes this plot look a bit silly, I guess it did that since it was the first reboot in ages Dec 04 20:33:22 that is a super cool command Dec 04 20:33:23 yeah, another reboot fixed it Dec 04 20:33:37 no way you have everything up in only 8s Dec 04 20:33:41 yep it's quite informative Dec 04 20:33:48 uhh yeah way? Dec 04 20:33:58 like, there's nothing really running on the system Dec 04 20:34:06 im playing around with the interrupts right now to see if setting the wifi interrupt to level_high will cause it to register. Dec 04 20:34:09 that's very fast Dec 04 20:34:34 when I put some work into it a while back I got this: https://liktaanjeneus.nl/boot.svg Dec 04 20:36:32 konsgnxx: it must be IRQ_TYPE_EDGE_RISING Dec 04 20:36:35 anything else will break it Dec 04 20:36:53 (most likely anyway) Dec 04 20:37:15 well, can't break the broken. Ill switch back Dec 04 20:37:24 working on the pbeagle now Dec 04 20:37:26 bbl Dec 04 20:39:57 ? Dec 04 20:40:57 just for comparison my bbb takes 70s from power on for me to be able to ssh to it, and another 30s for /dev/uio* to be available (needed to use the PRUs) Dec 04 20:42:29 hmm, is bt_aud_out necessary to pull low? right now it is unconnected. Dec 04 20:45:56 https://www.linkpicture.com/view.php?img=LPic5fca9fb601d51228563683 my boot.svg Dec 04 20:49:10 I've gotten extremely fast at typing "temppwd" Dec 04 21:03:22 hehe, I chose not to use a passwd for login Dec 04 21:22:07 Hi.. Dec 04 21:22:18 Anyone knew Beagleboard x15? Dec 04 21:25:35 Vairamhcet: matt knows all beagle things, he may help you later. What do you do with it? Dec 04 21:26:48 Hi. I using the board for RT linux and doing project development..I have one question regarding cooling fan Dec 04 21:36:15 you might want to actually ask your question rather than merely sharing the fact that you have one. otherwise the probability of getting an answer is rather small :P Dec 04 21:37:11 konsgnxx: ssh supports public-key authentication which is both more secure than a password and more convenient than one Dec 04 21:38:50 konsgnxx: also bt_aud_out is the wilink8's audio data output, part of its (rarely used) audio interface Dec 04 21:39:37 ahhh, digging through the wlcore code now, trying to figure out how exactly it probes and finds devices. Dec 04 21:39:55 konsgnxx: why are you not checking these things (what various signals are) in the wilink8 datasheet or the hw integration guide Dec 04 21:40:25 konsgnxx: I mean, the same as any DT-declared device presumably Dec 04 21:40:25 They seem right, irq low at startup, clock running Dec 04 21:41:35 Is Beagleboard x15 will automatically turn ON the fan when temperature raises Dec 04 21:42:21 I'd assume so? my guess would be based on levels configured in DT. I don't actually know, I've never connected a fan to my bbx15 Dec 04 21:42:49 Ok i will dig it thanks Dec 04 21:47:05 though it seems my bbx15 is trying to run the fan (unaware none is connected), even though all thermal zones are lukewarm Dec 04 21:50:30 how would one instrument a driver? Dec 04 21:50:40 is there a way to get debug info? Dec 04 21:51:24 most drivers and other kernel code have debug messages that can be enabled at boot time, module load time, or at runtime Dec 04 21:51:38 https://www.kernel.org/doc/html/v4.19/admin-guide/dynamic-debug-howto.html Dec 04 22:00:26 welp, im out, but i just noticed that i have no error messages from wlcore, I think the driver may not be loading at all Dec 04 23:53:54 ooook Dec 04 23:54:13 so i am about to start the upgrade and beaglebone ai vision recognition tutorial Dec 04 23:54:25 i've just been playing with it, and i'm also live streaming me playing with it on twitch.tv/ajpikul Dec 04 23:54:36 mainly for the facebook group Dec 04 23:54:48 there's some lurkers watching and one of my friends came on but otherwise i'm on my own Dec 05 00:04:36 so upgrading the kernel is supposed to solve some heat issues? Dec 05 00:05:39 ugh its freezing up upgrade Dec 05 00:10:36 really dont know what to do when apt upgrade just... stop providing output Dec 05 00:10:59 I don't think I've ever seen that Dec 05 00:11:13 try "ps f -fe" in another terminal? Dec 05 00:11:17 to see what it's doing Dec 05 00:13:03 hmm its using 94% cpu Dec 05 00:13:19 maybe it's just still figuring shit out Dec 05 00:13:43 i guess yeah, i mean its the first upgrade Dec 05 00:13:46 i guess i have to let it run Dec 05 00:15:18 lol yah Dec 05 00:24:46 ugh i touched the caps below the processor to feel the heat coming through Dec 05 00:24:52 and i think i shorted it and reset the device during upgrade Dec 05 00:24:53 :-9 Dec 05 00:31:16 rip Dec 05 00:31:22 rip Dec 05 00:32:09 well i'm at least hoping i get this example program up today Dec 05 00:32:21 i mean i've been streaming for like 2.5 hours and i guess its going to take me all night but thats cool Dec 05 00:33:07 you may want to force-reinstall any packages that it thinks it has successfully installed but for which data might have been buffered during the crash Dec 05 00:33:21 i mean it had me to a repair Dec 05 00:33:24 it just crashed again Dec 05 00:33:32 and its a whole ton of packages i hate my life Dec 05 00:33:58 start from fresh image? :/ Dec 05 00:34:15 latest testing image maybe to reduce the number of packages that need to be updated Dec 05 00:35:30 that would have been a good idea but i'm explicitly trying to avoid making a new image lol Dec 05 00:36:11 i think its fine now i dontknow i dont think it actually managed to upgrade any packages previously Dec 05 00:36:20 its now actually giving me output and a progress bar Dec 05 00:37:01 there's abunch of lurkers on the stream but i think they're all bots? Dec 05 00:40:36 Not me! Dec 05 00:40:43 I am a bonified individual! Dec 05 00:40:50 I promise. Dec 05 00:43:40 GenTooMan: I ordered the be-jeezus out of the motor. Now, I some waiting will take place and some outcomes down the line. BBB! Dec 05 00:43:58 i don't think you're on the stream tho... ? Dec 05 00:44:03 Oh. Dec 05 00:44:04 No. Dec 05 00:44:11 I do not know anything about the stream. Dec 05 00:44:29 I just read over what you were typing. Excuse me. Oops. Dec 05 00:45:06 Are you guys making movies of tutorials? Dec 05 00:45:42 im just setting up the AI in general Dec 05 00:45:51 yeah i'm probably do the one they have on beaglebone.org Dec 05 00:46:02 pain to upgrade everything Dec 05 00:46:08 Oh. Nice, get the FAN. Dec 05 00:46:17 yeah i have a fan on the board already Dec 05 00:46:21 Okay. Dec 05 00:46:25 Smart move. Dec 05 00:46:25 is there any way to run this device without a fan? Dec 05 00:46:30 No. Dec 05 00:46:34 Well. Dec 05 00:46:39 Not from what I have seen. Dec 05 00:46:55 thats rough Dec 05 00:47:14 My board gets too heated w/ processing power (at least that is what I have come to believe). I could be wrong. Dec 05 00:47:27 It could be the tiny form factor. Dec 05 00:47:33 i mean you upgraded everything and thats still the case/ Dec 05 00:47:35 ?* Dec 05 00:47:40 yeah the form factor is the culprit Dec 05 00:47:45 Right. It still needs the fan. Dec 05 00:48:09 Fan or electronic death. Either/or. Dec 05 00:48:52 My heat records show that the board operates at a normal temp. when operating w/ the fan. W/out the fan, it dies most of the time. Dec 05 00:49:11 Even w/ that beaglboard.org/upgrade page instructions. Dec 05 00:50:00 But, one could always lesson the burdern of the cpu, am5729, w/ removing the heavy loads. Dec 05 00:50:41 Some of what I call "heavy loads" are exactly the things that make the board awesome. Dec 05 00:50:42 But... Dec 05 00:50:54 There are some other ideas. Like, Node Red and Cloud9. Dec 05 00:51:02 really strange it seems to be routing github and github alone through the wrong network device Dec 05 00:51:11 so i took down usb0 and 1 hoping it would move to wlan but it hasn't Dec 05 00:51:18 If you do not use those, you can stop their service and cut it out. Dec 05 00:51:19 Hmm. Dec 05 00:51:49 I have done that before w/ interfaces. Dec 05 00:52:34 I would change it back before rebooting. I remember it does not always go back during a boot to its regular format. Dec 05 00:53:33 Are you trying out wifi and having issues w/ connman or are you using another way? Dec 05 00:55:38 I changed the Network config. before on Debian and made some USB dongles work w/ the BBB but w/ the AI, it just works w/ connman, i.e. if you are close enough to your hotspot. Dec 05 00:56:39 https://paste.ofcode.org/eyw83EEHG3huq79QK6ziZhttps://paste.ofcode.org/eyw83EEHG3huq79QK6ziZ Dec 05 00:56:50 set_: i got usb, wifi, and the access point to work Dec 05 00:56:54 sorry i meant to paste that once Dec 05 00:56:58 Oh. Dec 05 00:57:00 https://paste.ofcode.org/eyw83EEHG3huq79QK6ziZ thoughts, zmatt Dec 05 00:57:04 Okay. It just craps out? Dec 05 00:58:03 what? Dec 05 00:58:14 OH. I see. Dec 05 00:58:17 the paste shows the issue Dec 05 00:58:21 Github does not want to reply. Dec 05 00:58:30 well its going through the wrong network interface Dec 05 00:58:45 it uses the correct interface for the other domains but it tries to go over usbx for github Dec 05 00:59:40 Hmm. That seems odd. I am not the networking giant in the field. I would tell github. "Your pings are not using my wlan!" Dec 05 01:00:07 Have you set up git yet? Dec 05 01:00:21 yeah of course Dec 05 01:00:43 Can you use it well yet w/ cloning and/or push/pull? Dec 05 01:00:52 uh i'm assuming Dec 05 01:00:59 Or is it just that darn ping? Dec 05 01:01:00 i can't ping git or use pull Dec 05 01:01:05 i can't go to github.com Dec 05 01:01:06 Oh. Dec 05 01:01:07 Okay. Dec 05 01:01:28 Have you been banned? Dec 05 01:01:30 Ha. Dec 05 01:01:48 I know github states when I see errors to contact them. Dec 05 01:02:07 no this isn't really the right route for this issue Dec 05 01:02:14 this is a configuration issue Dec 05 01:02:14 It just seems odd to have ping work w/ google, as usual, and not w/ github. Dec 05 01:02:16 Okay. Dec 05 01:03:08 it wont let me force the interface either hmm, or i mean it does but packet loss Dec 05 01:03:55 Well, maybe someone else will show up. I have not had this issue w/ ping in a long time or not being able to set up git on the BBB/AI. Dec 05 01:04:17 yah i restarted it didn't work either Dec 05 01:04:24 Maybe a complicated config. is the issue. Heh? Dec 05 01:04:29 Really. Dec 05 01:04:31 Wow. Dec 05 01:04:32 i checked .gitconfig Dec 05 01:04:55 You started w/ a new image and it still gave you issues, I am guessing? Dec 05 01:05:18 no i just upgraded the current image Dec 05 01:05:52 Did you go to debian yet to look over their ideas on config. for networking? Dec 05 01:06:20 i'm not completely unfamiliar with this area Dec 05 01:06:26 but this is a stumper Dec 05 01:07:27 Okay. My face was blue while I tried to make the wlan work on the BBB. But, w/ time and effort, I configured it correctly w/ wlan. Dec 05 01:07:35 I am sure you will figure it out. Dec 05 01:09:11 ayjay_t: Do you want me to plug mine in and search the board for the files you want to view? Dec 05 01:09:42 no thats okay set_ Dec 05 01:09:51 Okay. No issue. Dec 05 01:11:03 Well, if worse comes to worse, just let me know. I will chime in after a while and see if you changed your mind. Dec 05 01:17:25 huh the device seems to be failing more completely now lets see Dec 05 01:32:24 guys over in ##networking roasting the bb ai's "sysadmin" Dec 05 01:32:27 lol they're SO MEAN Dec 05 01:40:38 i just had to code of conduct i guy in there Dec 05 01:40:45 he should probably be banned Dec 05 01:42:35 ayjay_t: Did you ever figure out the issue? Do you have backports for debain on your file system? Dec 05 01:43:03 yeah i mean apparently if the DNS record pulls a ipv4, the default route is set to USB0 and it tries to use that Dec 05 01:43:13 Oh. Dec 05 01:43:14 but if the DNS record pulls an ipv6, it uses a different route Dec 05 01:43:21 Okay. Dec 05 01:44:09 I just set up my old motorings to start, stop, stay interrupted for a time, and then proceed. Yea! Dec 05 01:44:26 Now, to put this contraption together. Dec 05 01:45:16 I really should learn Linux outside of just libs. and modules. Sheesh. I am feeling like a feather in the wind. Dec 05 01:54:48 zmatt fyi this fixed the issue: https://paste.ofcode.org/6nmaAfcYWw22cMxP5TPuDu Dec 05 01:55:00 zmatt the issue being that any ipv4 addresses were ignoring the wlan0 Dec 05 02:56:38 ayjay_t: you probably mean "the default gateway via usb0 ended up getting precedence over the one via wlan0" .. that's what I assume is going on at least, kinda hard to tell based on the output of the legacy "route" tool, please use "ip route" instead Dec 05 02:58:58 that's weird though... like I can understand the reason for that default route via 192.168.178.1 but they should at least have deprioritized it using metric **** ENDING LOGGING AT Sat Dec 05 02:59:57 2020