**** BEGIN LOGGING AT Thu Mar 05 02:59:57 2020 Mar 05 03:00:35 granted Mar 05 03:13:18 I just finished a burn to SD from BBB but the uEnv.txt file in /boot does not have the eMMc flasher line? Mar 05 03:13:50 How are you supposed to restore this? Mar 05 03:17:37 Never mind. Mar 05 03:21:25 only if you are using it to burn the eMMc actually Mar 05 03:22:21 reminds me I have to get a few cheap SD cards so I can flash my BBB rev B's with the IoT image. Mar 05 03:26:17 Amazon has some good deals Mar 05 03:26:51 I like the Samsung 32GB EVO cards. work great Mar 05 03:30:30 Sigh... 32G (heh). Is the SD interface DDR or SDR for data? I know QSPI can be DDR (which is handy) however I never quite figured out the spec for SD the SD association was quite cryptic for decades on there interface. Mar 05 03:36:41 All I know is the offered drive was a Samsung 32GB EVO and it works. Mar 05 03:37:43 Here: https://www.amazon.com/gp/product/B06XWN9Q99/ Mar 05 03:38:40 They have up to 512GB. Mar 05 03:39:48 up to 95MB/s Mar 05 03:42:09 You can always try the Lexar. It's a bit cheaper https://www.amazon.com/dp/B012PLSCQ0/ Mar 05 03:49:09 GenTooMan, you there? Mar 05 03:55:01 somewhat it's about time I get sleep however. one has to be careful with SD cards as China had been manufacturing fake ones for a number of years. Mar 05 03:58:07 I agree. Samsung has a good name. Good night. Mar 05 09:24:43 GenTooMan: https://pastebin.com/rfLzRK0G summary of card types/speeds/modes Mar 05 09:25:18 GenTooMan: note that the BBB does not support any UHS modes, the max is 48 MHz HS mode Mar 05 09:38:36 interesting, useful, thanks Mar 05 13:17:53 I thought they might need to go with some sort of differential signalling for the higher data, I wonder if they are using PCI-x like many SSD's are? Mar 05 13:51:29 just installed latest debian9.9 lxqt from beagleboard.org, cannot start ssh server any hint ? Mar 05 14:24:27 and.... is there any reason I can't find any debian10 lxqt image ? Mar 05 14:54:04 m Mar 05 14:57:18 m 2 Mar 05 14:57:29 ssh issue gone, fixed LCD resolution, touchscreen dead, where to start check from ?? Mar 05 14:59:38 touchscreen likely isn't physically broken so I suggest "inoperative" or "non-functional" although dead is much shorter I admit Mar 05 15:06:42 yep....this display has always worked with all previous LXDE-LXQT beagle images, with this latest one doesn't work.... how to check how is managed and if it has been recognized ? Mar 05 15:33:30 if I run xinput_calibrator it says "no calibratable device found"... :-( Mar 05 16:01:49 every new version....something working broken :( Mar 05 17:41:01 the touch sensor drivers may not be loaded so it can't calibrate the sensors. You may wish to check if the module is in and such. Mar 05 21:11:01 GenTooMan: the new "sd express" uses pcie and will replace UHS-II/III Mar 05 21:41:50 zmatt, does that effect the BBB? Mar 05 21:42:12 not in the slightest bit Mar 05 21:42:35 since like I said, the BBB doesn't support any UHS modes (not even UHS-I) in the first place Mar 05 21:42:55 and the BBAI only supports UHS-I Mar 05 21:43:19 zmatt, my little wifi adapter came in today. Well I'm using Samsung 32GB ENV SD-card. Mar 05 21:43:39 which are modes supported by all modern SD cards, and which will continue to be supported Mar 05 21:45:10 Get to try out my wifi adapter tonight Mar 05 21:45:54 usb wifi adapters tend to be kind of hit and miss in terms of driver support Mar 05 21:47:03 it even happens that you can have two adapters of the same brand and model number yet one is supported and one isn't because the manufacturer silently switched chipset Mar 05 21:47:48 This one is supposed to be supported. Mar 05 21:48:41 I guess I'll find out when I plug it in. Mar 05 21:49:37 This one: https://www.amazon.com/gp/product/B008IFXQFU/ Mar 05 21:49:51 Not made in China. Mar 05 21:50:20 Made in Vietnam! Mar 05 21:56:37 based on some quick googling it seems like it uses the RTL8188EUS chipset which is not natively supported in linux... there is some out-of-tree driver but getting those to work can be a significant headache Mar 05 21:59:17 Here I go again. Mar 05 21:59:43 I thought the 8188 was supported in the BBB? Mar 05 22:00:15 the bbb supports what linux supports, there's nothing bbb-specific about usb drivers Mar 05 22:00:32 OK. What wifi is supported out of the box? Mar 05 22:01:49 lots of them... rcn made sure that firmware and even some out-of-tree drivers for a variety of wifi adapters is included so that they work without having the user install additional packages Mar 05 22:02:24 but manufacturers usually don't bother to list which chipset they're using... and like I said, sometimes they even switch which chipset they're using without changing the model number of their product Mar 05 22:02:58 *chip ... dunno why I keep saying chipset when it's almost certainly a single chip :P Mar 05 22:03:30 like I said... usb wifi adapters tend to be kind of hit and miss Mar 05 22:33:40 zmatt, got it working. How to use wlan0 but still usb0 alive? Mar 05 22:35:53 zmatt, Here is what I did: http://paste.debian.net/1133648/ Mar 05 22:36:39 usb and wifi shouldn't conflict in any way Mar 05 22:36:57 usb networking and wifi I mean Mar 05 22:44:54 If I do a route the default GW still points to the USB port Mar 05 22:45:25 it normally will never point there, it only points there because you fiddled with settings Mar 05 22:46:11 conversely, normally wifi and ethernet should work fine out of the box, so whatever you did probably broke it :P Mar 05 22:47:13 Here is what it says: http://paste.debian.net/1133650/ Mar 05 22:50:46 Traffic not going over wifi. : ping: www.cnn.com: Temporary failure in name resolution Mar 05 22:51:10 just undo whatever you did and presumably wifi will work again Mar 05 22:56:37 zmatt, you have wht i did Mar 05 22:56:52 ? Mar 05 22:58:38 My upload Mar 05 22:59:23 I know that the default gateway pointing to usb0 and messing with /etc/resolv.conf are things you did in an attempt to give the bbb internet access via usb, and most likely that's why wifi isn't working right now Mar 05 23:02:32 resolv.conf says nameserver 8.8.8.8 Mar 05 23:03:21 I stand corrected it is: nameserver 10.128.128.128 Mar 05 23:03:26 normally it should be a symlink to some file managed by connman. but the default gateway is the first issue to fix Mar 05 23:03:34 okay sounds like resolv.conf is fine Mar 05 23:04:01 so the default gateway is the only issue. most likely because you manually forced to default gateway to usb0, connman doesn't dare to touch it Mar 05 23:14:20 Activated connmanctl lines in interfaces, reboot, seems OK. See new route output http://paste.debian.net/1133654/ Mar 05 23:14:47 "connmanctl lines in interfaces" ?? Mar 05 23:15:49 wrong file see : http://paste.debian.net/1133655/ . Yes they are in there but commented out Mar 05 23:16:06 I'm not sure what you're talking about Mar 05 23:16:57 on my BBB Debian 9.9 in /etc/network/interfaces Mar 05 23:17:30 /etc/network/interfaces is the config file for ifupdown, which is a different network manager than connman (and using two network managers at the same time is almost always trouble) Mar 05 23:18:24 I don't know what to say. Mar 05 23:19:51 oh I see, rcn put some comments in that file on how to use connman, presumably because people keep looking in that file for network stuff Mar 05 23:20:07 those are not "commented out" config lines, they're literally just comments Mar 05 23:20:50 they're not syntactically valid for /etc/network/interfaces ... so most likely you just rendered your /etc/network/interfaces unparseable and that's why wifi works again (because connman isn't getting interfered with anymore) Mar 05 23:22:09 here is the file : http://paste.debian.net/1133657/ Mar 05 23:22:56 yep, you simply broke that file, thus as a side-effect negating the changes you made that were causing your wifi problems Mar 05 23:23:18 that's my guess anyway Mar 05 23:24:34 lines 22-28 are 100% certainly not syntactically valid for /etc/network/interfaces, they were just comments showing a transcript of an interactive connmanctl session Mar 05 23:26:41 OK. commented out again. rebooted. comes up ok Mar 05 23:27:08 So how many times do I need to use connmanctl? Mar 05 23:27:16 zero Mar 05 23:27:20 after initial setup Mar 05 23:27:43 afaik you use it once to connect to your wifi network Mar 05 23:27:54 and it should remember that config Mar 05 23:28:17 maybe me deleteing the default GW to the USB0 port helped Mar 05 23:28:59 that's not a "maybe" ... that's literally what I said :P Mar 05 23:29:51 I commeneted out route add default in interfaces file and nameserver entry Mar 05 23:29:52 but also yuck, I don't know why rcn uses a mix of ifupdown and connman.. I'd just ditch ifupdown entirely Mar 05 23:30:48 Some of the info out there suggests manually editing interfaces file Mar 05 23:31:05 which is unfortunate Mar 05 23:31:15 Dinners here. Got to go. Be back later Mar 05 23:48:52 heh Mar 06 00:23:36 Hello... :] Mar 06 00:33:18 :D Mar 06 01:04:11 I'm here and not here Mar 06 01:58:20 mostly writting code to ray trace letters :D Mar 06 02:09:46 l **** ENDING LOGGING AT Fri Mar 06 03:00:02 2020