**** BEGIN LOGGING AT Thu Apr 18 02:59:57 2019 Apr 18 09:09:35 Hi, anyone has used BBBWL and connected it to the internet via USB Apr 18 09:10:56 BBBWL? Apr 18 09:12:39 BeagleBoardBlack Wireless Apr 18 09:13:50 I am unable to perform even a "ping 192.168.7.1" for instance for BBBWL to connect to the hos PC via USB (network) Apr 18 09:15:09 hello, i've upgraded my kernel to 4.19-rt branch and can no longer see anything PRU in /sys/class/uio or dmesg; the driver is compiled in, dts looks ok, what else could i miss? Apr 18 09:20:45 do you have the uio-pruss overlay enabled in /boot/uEnv.txt? Apr 18 09:21:20 it should work on the latest 4.19-ti branch, I don't know to what other branches rcn has applied the patch Apr 18 09:21:55 with "4.19-rt" you mean 4.19-ti-rt ? Apr 18 09:22:20 no, i mean https://github.com/beagleboard/linux/tree/4.19-rt Apr 18 09:23:10 ok so yes, 4.19-ti-rt Apr 18 09:23:21 i don't have no overlays because i haven't quite figured how they work and prefer to wait for the mainline inclusion, so i just modify the board dts as needed Apr 18 09:23:49 overlays are handled by the bootloader nowadays, overlay support in the kernel is deprecated and will never reach mainline Apr 18 09:24:03 but you can use a custom dts too of course Apr 18 09:24:28 btw if you build a custom kernel, you might want to consider using the build repositories instead of the snapshots of the patched kernel trees Apr 18 09:25:04 https://bpaste.net/show/3c9c8e4c891b my am335x-boneblack.dts Apr 18 09:25:21 i'm using the repo Apr 18 09:25:44 anyway, if it worked previously it should still work, so it's probably an issue with the kernel Apr 18 09:25:49 or i don't understand what are you referring to Apr 18 09:26:25 i've modified the dts since i needed to accommodate the dts changes while going from 4.14 to 4.19; maybe i've messed up, but i couldn't find any culprits Apr 18 09:26:27 https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-rt-4.19.y Apr 18 09:26:33 that's the build repository Apr 18 09:27:06 some notes about these repos: https://pastebin.com/eLhrp1Hg Apr 18 09:28:02 it does seem like the 4.19-ti-rt branch includes my uio-pruss patches Apr 18 09:28:50 ehh, your dts however is definitely not right if you want uio-pruss, you're enabling remoteproc-pru Apr 18 09:29:03 but this also wouldn't have worked in 4.14 Apr 18 09:29:05 in fact i want it to work with machinekit Apr 18 09:29:20 i'm not really sure which interface does it use Apr 18 09:29:58 but it fails at init with a cryptic error message on my 4.19 Apr 18 09:30:08 neither do I, I know nothing about machinekit Apr 18 09:30:23 and wanted to insmod uio-pruss so i suppose it's uio Apr 18 09:31:20 insmod/modprobe uio-pruss never makes any sense anyway. if the module isn't loaded automatically, manually loading the module is unlikely to have any effect either Apr 18 09:31:41 (unless your module index is broken, in which case you just need to depmod) Apr 18 09:32:31 anyway, if you want uio-pruss you'll need a few lines more in your dts Apr 18 09:36:34 ah, so there's a patch in the build repo that adds a dtsi file to enable uio-pruss, but it's commented out in patch.sh: https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-rt-4.19.y/patch.sh#L471 Apr 18 09:37:15 that patch creates an am335x-uio-pruss.dtsi which you could #include to enable uio-pruss: https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-rt-4.19.y/patches/drivers/ti/uio_pruss/0005-ARM-dts-dra7-am335x-dtsi-files-for-enabling-uio-prus.patch#L13-L29 Apr 18 09:38:08 it's interesting that i don't have am335x-uio-pruss.dtsi in my tree Apr 18 09:38:11 or you could just put those two DT fragments in your dts directly Apr 18 09:38:12 thanks Apr 18 09:38:31 that's what I just said: the patch (that creates that file) is commented out in patch.sh Apr 18 09:38:51 oh, i've missed that line Apr 18 09:38:58 so if you'd build your custom kernel using the build repo, you could just uncomment that line in patch.sh and rebuild, then you'd have the file Apr 18 09:43:55 which reminds me that I was still going to change the driver to not require the ti,pintc-offset property (since it can be inferred from the compatible-string)... oh well Apr 18 09:45:17 btw if you have a custom kernel config, make sure you have CONFIG_SIMPLE_PM_BUS=y Apr 18 14:38:17 Hi, I just want to understand pin assignment of BBBW and BBB.Does BBBW uses the same pins of BBB ethernet for WiFi? Apr 18 14:57:01 yes Apr 18 14:57:41 oh he left Apr 18 21:33:59 Hi, I'm trying to flash the latest Ubuntu on my BBB (industrial edition). I'm trying to follow instructions here: https://elinux.org/BeagleBoardUbuntu However, I'm not sure if I'm supposed to reformat my microSD card as, say, FAT32 or whatnot, before running the setup_sdcard.sh command. What do I do? Apr 18 21:35:37 Also, if there was some other way besides using this script, like flashing via Etcher. Apr 18 21:37:14 Hmm, I guess I grabbed the wrong image. It appears there is a way to flash via Etcher. Apr 18 22:01:08 galaxie: why specifically ubuntu? Apr 18 22:01:58 galaxie: it's rarely used hence poorly tested Apr 18 22:03:29 galaxie: in general you should probably just use the latest debian IoT image from https://beagleboard.org/latest-images (instructions for flashing to eMMC are below the links) Apr 18 22:58:41 zmatt: Because I've tried Debian and while it somewhat worked, for some things I was tired of failing at compiling some software and for my purposes almost everyone used Ubuntu anyways. Apr 18 22:59:43 uhh, what software on earth compiles on ubuntu but not on debian? generally whether something compiles or not is merely a matter of having the appropriate dependencies installed Apr 18 22:59:57 and who are "almost everyone" Apr 18 23:00:02 ? Apr 18 23:00:21 I meant, there's a PPA for Ubuntu that will save me the trouble of compiling everything. Apr 18 23:00:50 and using it on debian resulted in dependency problems? Apr 18 23:01:10 which software are you referring to? Apr 18 23:02:46 zmatt: It said something about no release file, and I think I tried stretch and dependency issues resulted. Apr 18 23:02:54 zmatt: I'm trying to install Podman. Apr 18 23:03:56 zmatt: So I flashed the image and all, but now when I hold the boot (i.e. closest to SD card) button and power it on the lights.. I'm not sure what to call it, ping pongs back and forth for a minute or two then shuts down? Apr 18 23:04:26 ping-pong means it's flashing eMMC Apr 18 23:04:41 a minute or two suggests a really tiny image... console image probably? Apr 18 23:05:11 Console. Whatever this is: https://rcn-ee.com/rootfs/2019-04-10/flasher/am57xx-eMMC-flasher-ubuntu-18.04.2-console-armhf-2019-04-10-2gb.img.xz Apr 18 23:05:29 So was I not supposed to hold down the boot button?? I don't want to flash eMMC necessarily. Apr 18 23:05:42 the boot button usually has no impact Apr 18 23:06:10 That is the correct term right? The one right next to the card slot? Apr 18 23:06:16 also what? am57xx ? but you said you have a BBB... that shouldn't even be able to boot at all Apr 18 23:06:39 Oh sorry, I meant: https://rcn-ee.com/rootfs/2019-04-10/flasher/BBB-eMMC-flasher-ubuntu-18.04.2-console-armhf-2019-04-10-2gb.img.xz Apr 18 23:07:13 Now all LEDs flashed and stayed on, then power off. Now what? Remove power then power on again without holding down any buttons? Apr 18 23:07:13 I mean, if you didn't want to flash eMMC... maybe you shouldn't have used an image with "eMMC-flasher" in the name :P Apr 18 23:07:22 remove the card first Apr 18 23:07:31 like I said, the boot button usually has no impact Apr 18 23:07:54 So is the setup_sdcard.sh script for flashing on the SD and not eMMC? Apr 18 23:08:32 Or was this the one I needed: https://rcn-ee.com/rootfs/2019-04-10/microsd/bone-ubuntu-18.04.2-console-armhf-2019-04-10-2gb.img.xz Apr 18 23:09:11 in rare cases it may be necessary to force booting from sd card, when the eMMC has some ancient, weird, or broken bootloader, or one that's not compatible with the system on sd card Apr 18 23:09:38 I don't know anything about a "setup_sdcard.sh" script, like most people here I've never used ubuntu on a BBB Apr 18 23:09:47 that image name sounds plausible however Apr 18 23:26:07 galaxie: I just added the ppa to my debian system, and apt doesn't seem to have any problem with it Apr 18 23:27:04 I'm using a debian buster system though, I'm too lazy to boot up a debian stretch system to test it there Apr 18 23:29:57 https://pastebin.com/raw/G58zQiTn Apr 18 23:30:55 OK. Where's a buster image available? Apr 18 23:32:49 what problem are you having on stretch? you said something about a release file, but that just sounds like a problem with the apt-sources line Apr 18 23:34:43 and this was a stretch-console system I manually upgraded. there are buster-iot images in testing (e.g. https://rcn-ee.com/rootfs/bb.org/testing/2019-04-14/buster-iot/ ) but I have no idea what state they are in currently Apr 18 23:35:40 I changed it from whatever weird release name is had to xenial I believe. Apr 18 23:35:47 using those would defeat the whole purpose of using debian: namely to be able to use the recommended and tested images Apr 18 23:36:55 yeah xenial seems to work too Apr 18 23:38:37 https://pastebin.com/raw/uGmqib3x Apr 18 23:49:55 zmatt: The ubuntu images still receive updates right? For the BBB specific stuff? Apr 18 23:50:35 I don't really know anything about the ubuntu images other than that they exist Apr 18 23:51:32 Who's in charge of it? Apr 18 23:52:30 noone is "in charge" of them since they're not official images. rcn is the one who makes them (and also the official debian images) Apr 18 23:59:31 * zmatt -> bed Apr 19 00:11:43 Bed! Apr 19 00:19:58 OK, so I ran the grow_partition.sh script like it's mentioned in all the docs and now I can't seem to connect to my BBB, yet the LEDs and stuff are still flashing normally, looks like a lot of disk activity. What do I do? Did I brick my newly-flashed system, or do I just wait, or what? Apr 19 00:31:36 Apparently I just had to wait a few minutes. That's good. **** ENDING LOGGING AT Fri Apr 19 02:59:57 2019