**** BEGIN LOGGING AT Sun Feb 07 02:59:58 2016 Feb 07 05:56:46 Building debian image from scratch per, and getting internal compiler error with iofopen64.o Feb 07 05:58:07 sorry - a bit more clear: Following instructions on how to build BBB from scratch, at the bitbake build virtual/kernel stage and the compiler is choking with an internal error. Feb 07 05:58:43 the specific file it is choking on is: iofopen64.o - google is not finding a workaround, etc. Feb 07 06:00:17 What I want is a crossbuild environment for BBB. As a test I thought i would follow the debian build steps. Those steps fail. Feb 07 08:20:42 good morning Feb 07 08:29:13 How to cancel or withdraw a post after we have posted it on the BB forum? Feb 07 08:30:07 Since I fixed the bugs and would like to now withdraw my post, Is that possible? Feb 07 08:30:28 no idea, check the googlegroups help/documentation? Feb 07 08:31:12 K kool Feb 07 08:31:24 how to log out from here? Feb 07 08:32:11 just close the tab/window Feb 07 10:58:33 how to open a browser? Feb 07 10:58:34 :D Feb 07 12:45:41 is it possible to program the TPS65217 to completely ignore VUSB (usb input) ? As in: cut 5V from the dc jack and the board is off even if usb serial is connected ? Feb 07 12:48:27 I know - Disable USB power: i2cset -y -f 1 0x24 0x01 0x2f → USB_EN=0 at PPATH register. But after power is down on the dc jack, the board powers up again through USB. Feb 07 14:11:40 dl9pf: those registers are volatile and are reset by powerdown... unfortunately you didn't stick around to learn that answer Feb 07 14:11:50 woops Feb 07 14:11:51 you did Feb 07 14:11:54 I mistabbed Feb 07 14:12:25 shame on you dor using an "l" that looks suspiciously like an "1" in your nick :P Feb 07 14:12:42 ok I can't spell today clearly Feb 07 14:15:03 dl9pf: basically, the tps65217 is a pretty awful. I can't imagine why anyone would think it's a good idea to reset all registers after shutdown (but with some supply still available to the pmic) Feb 07 14:15:59 so, e.g. you can also (after power up) customize the power-up and power-down sequences... but only the customized power-down sequence will be honored since after that the registers are reset to default again Feb 07 14:16:12 likewise with the USB_EN bit Feb 07 14:25:20 I'm pretty sure the only way to avoid power being drawn from from usb at all times is by cutting the trace between the usb connector and the pmic. you'd need to ensure the connection from usb connector to the vbus-detect input of the am335x stays intact though (or there might be a way to override vbus detection in software, but if so it's not really clear how exactly) Feb 07 17:14:25 does anyone here have knowledge of how to configure iptables to use both a wired eth0 interface and a cellular modem wwan0 interface? Feb 07 17:14:53 this is the system's default routing table: http://www.fpaste.org/319636/45486342/ Feb 07 17:15:51 i've brought up the wwan0 by attaching to the network with a qmicli command and then running dhclient wwan0 Feb 07 17:16:21 what i'm not seeing is a gateway for the wwan0 interface Feb 07 17:17:40 curiously, the /var/lib/dhcp/dhclient.wwan0.leases file is present but empty Feb 07 17:19:16 let me back up: i want to see if this interface (wwan0) is REALLY up. how to do? Feb 07 17:20:50 i do get wwan0 listed in an "ifconfig" command Feb 07 17:21:04 with an ipv4 address, so it looks like it's coming up. Feb 07 17:44:26 anyone? Feb 07 17:45:59 like switching between one and the other automatically, or as a bridge? Feb 07 17:50:15 i don't even know. i'm too ignorant to answe rthat. Feb 07 17:51:41 something seems to be seriously wrong anyway. as soon as i bring up wwan0, lose internet connectivity, i.e., i can ssh in. curiously, existing ssh sesseions remain connected and working. Feb 07 17:51:55 s/i can ssh/i cannot ssh/ Feb 07 17:58:26 aha. Feb 07 17:58:52 iptables plays no role here (hopefully), that's the firewall Feb 07 17:59:03 ip route? Feb 07 17:59:46 so, that routing table looks okay, what is your intended behaviour? Feb 07 18:00:58 "I can ssh in" .. on what IP, from what IP ? Feb 07 18:01:23 i cannot ssh in to the bbb from my desktop Feb 07 18:01:31 (all on my local network) Feb 07 18:01:57 ah you meant you *can't* ssh in Feb 07 18:01:58 what i'm callin ghte "bbb" is really our custom board, fyi. Feb 07 18:02:02 yes. Feb 07 18:02:30 from an ip located in the 192.168.1.0/24 range on ethernet? Feb 07 18:03:02 yes, my own local 192.168.1.0/24 local network here on my router at my house. the bbb is connected there vai eth0 Feb 07 18:03:07 as well as my desktop Feb 07 18:03:30 but that goes away if i rewrite my /etc/resolv.conf with 8.8.8.8 Feb 07 18:04:14 normally one should not have to manually maintain etc/resolv.conf Feb 07 18:04:20 yeah, i know. Feb 07 18:05:12 zmatt: i how far did you read back? about 50 minutes ago i wrote some background Feb 07 18:06:02 yeah I read it, though I overlooked that you brought up the interface manually Feb 07 18:06:15 what is suspicious is that dhclient doesn't seem to get a gateway assigned to wwan0 Feb 07 18:06:17 is there no network manager of any sort running, like connman? ( pgrep connman ) Feb 07 18:07:08 nope Feb 07 18:07:31 i manually run dhclient after configuring the modem Feb 07 18:07:48 here's the entire sequence: Feb 07 18:08:55 1) power up the modem from userland code. 2) ttyusbx get enumerated and qmi_wwan driver is loaded 3) qmiclient command is run to start the network and activate to a specific APN, 4) dhclient is run to a) get an ip address, and b) bring up wwan0 Feb 07 18:09:27 at that point ip route looks like that pastebin Feb 07 18:10:27 eth0 comes up automatically cause it's in the /etc/network/interfaces file Feb 07 18:10:36 but i have not put wwan0 in that file Feb 07 18:10:41 ah so you're also using ifupdown Feb 07 18:10:51 indirectly, i guess. Feb 07 18:11:00 it just comes up at boot. Feb 07 18:11:20 multiple default routes can cause interesting problems... Feb 07 18:11:27 there's only one listed though Feb 07 18:11:34 the wwan doesn't get a default route Feb 07 18:13:09 yes. and curiously the /var/lib/dhcp/dhclient.wwan0.leases file is present but empty Feb 07 18:13:11 yates: when you lose the internet connection (but with an ssh still open) try: ip route get 192.168.1.1 (or any other IP on your LAN) Feb 07 18:13:27 okay so maybe also inspect your journal for errors Feb 07 18:14:18 what is the journal? Feb 07 18:14:26 also just in case check whether iptables is in fact loaded (lsmod | grep tables) Feb 07 18:14:29 journalctl? Feb 07 18:14:32 yes Feb 07 18:15:00 it's the systemd logging daemon Feb 07 18:15:53 * vagrantc looks around for trolls Feb 07 18:17:15 lsmod | grep tables returns nothing Feb 07 18:18:16 btw, if you don't want to upgrade to debian stretch entirely, I would still recommend at least installing the systemd-228 from stretch (and whatever dependencies it pulls in) ... I recently used a jessie system again and frequently noticed the tools were a lot crappier then :P Feb 07 18:19:08 (with systemd-228 I also recommend ditching ifupdown in favor of systemd-networkd) Feb 07 18:19:28 but ok, no tables, that's good (unless they're compiled in, not sure actually) Feb 07 18:19:42 did you to the 'ip route get' thing? Feb 07 18:19:44 here is the ip route command: http://www.fpaste.org/319651/86916814/ Feb 07 18:20:00 that also looks fine Feb 07 18:20:06 but you can't ping it? Feb 07 18:20:24 and yet i cannot ssh in to bbb from desktop.. Feb 07 18:20:49 i don't know why sshd needs to do a dns lookup, but apparently it does. Feb 07 18:21:08 that really slows things down yes, I always disable it Feb 07 18:21:32 oh wait Feb 07 18:21:35 UseDNS no Feb 07 18:21:41 ssh DOES work. it just takes a long time. Feb 07 18:21:43 in /etc/ssh/sshd_config Feb 07 18:21:45 yeah Feb 07 18:22:01 while you're there, make use UsePAM yes Feb 07 18:22:04 *make sure Feb 07 18:22:54 I also recommend enabling keepalive to ensure dead connections get cleaned up reasonably quickly Feb 07 18:23:40 ClientAliveCountMax 1 Feb 07 18:23:40 ClientAliveInterval 30 Feb 07 18:24:09 i'm guessing 63.84.143.13/14 is AT&T's dns server. and it's slow, at least from the external network. Feb 07 18:24:31 btw, sudo can be very slow for similar reasons Feb 07 18:24:40 to fix, add a line: Feb 07 18:24:44 Defaults !fqdn Feb 07 18:25:03 i did ip route get 63.84.143.13 it's getting it through via my home network, not over the cell connection Feb 07 18:25:28 yes your routing table is showing eth0 as default route Feb 07 18:25:34 default via 192.168.1.44 dev eth0 Feb 07 18:25:40 yes, i saw that. Feb 07 18:26:05 how do i find the gateway for wwan0, and how do i set that as the default gateway? Feb 07 18:27:04 should the gateway be assigned via dhcp for any network i/f? Feb 07 18:27:06 find it? normally it's supplied by dhcp (or in Ye Olde Days perhaps given to you in a long list of settings printed on a slice of dead tree) Feb 07 18:27:20 yes. so dhcp supplied it, where is it? Feb 07 18:27:29 find, yes. Feb 07 18:27:47 it either didn't supply it, or the dhcp client is misconfigured Feb 07 18:28:06 on what basis are you stating that? (just to learn, not to contradict) Feb 07 18:28:22 what is your reasoning? Feb 07 18:28:44 what would be different if it was supplied, or the dhcp client was configured correctly? Feb 07 18:28:57 maybe add wwan0 to /etc/network/interfaces (but without "auto wwan0") and then do "ifup wwan0" as soon as you did the modem setup stuff Feb 07 18:29:07 my reasoning is: the entry isn't there Feb 07 18:29:30 you mean in "ip route" output? Feb 07 18:29:33 yes Feb 07 18:30:03 so you would expect to see two "default..." lines? Feb 07 18:30:23 that's allowed if they have different metric ("priority") Feb 07 18:30:35 aha. Feb 07 18:30:40 an actual network manager would more likely pick only one to add Feb 07 18:30:43 but you're not using one Feb 07 18:30:53 not that i know of, no. Feb 07 18:31:05 you checked "pgrep connman" ? Feb 07 18:31:15 yes Feb 07 18:31:26 just double-checked. Feb 07 18:31:35 ah yes I remember I asked earlier. it's the default in lxqt images, but you have a more spartan system Feb 07 18:31:47 dude, spartan'r'us. Feb 07 18:32:10 i gotta go pee. Feb 07 18:32:33 well, thing is ifupdown isn't really "spartan" yet fails to be a proper network manager Feb 07 18:33:03 (hence my switch to systemd-networkd once it became usable, i.e. in the version available in stretch) Feb 07 18:35:50 you mentioned however the leases file was empty Feb 07 18:36:04 so it would seem it's not getting a dhcp lease at all Feb 07 18:36:18 which is kind of contradicted by having an ip Feb 07 18:36:46 (unless that was done by the modem-specific tools you mentioned) Feb 07 18:38:01 I suggest inspecting the logging from dhclient Feb 07 18:39:04 you can even run it in the foreground using the -d option and if necessary add -v for more verbosity Feb 07 18:39:11 I gotto go other stuff for a bit, back later Feb 07 18:39:14 ok Feb 07 18:39:16 thanks Feb 07 18:47:58 here is the relevent portion of daemon.log: http://ur1.ca/ohphc -> http://paste.fedoraproject.org/319658/45487086 Feb 07 18:51:33 looks good to me. isn't it? Feb 07 18:55:40 I am trying to install PRUspeak on BBB.However on executing run.sh I get the following error:IOError: [Errno 2] No such file or directory: '/sys/class/misc/pru_speak/pru_speak_abort' Feb 07 18:57:24 Can someone please help me? I am running kernel 3.8.13 bone-63 Feb 07 19:17:46 got it! Feb 07 20:55:57 zmatt: yes, I see. thanks **** ENDING LOGGING AT Mon Feb 08 02:59:58 2016