**** BEGIN LOGGING AT Mon Sep 18 03:00:01 2017 **** BEGIN LOGGING AT Mon Sep 18 08:08:04 2017 Sep 18 10:45:48 is there some clever way of disabling the default user password login in image-builder without touching the common chroot.sh script? Sep 18 10:49:13 after some grep: should rfs_console_user_pass="disable" do the trick? Sep 18 10:50:12 (and same for rtf_ssh_user_pass) Sep 18 11:20:11 Ionakka: what do you mean with "disabling the default user password login" ? Sep 18 11:21:28 zmatt: not letting the user to log in with a password Sep 18 11:21:48 (nor printing the password in ssh hello message) Sep 18 11:24:07 chroot.sh seems to add it unconditionally Sep 18 11:24:52 the two variables you found just control the messages about the default login/password Sep 18 12:39:41 zmatt: yeah, changing those fields didn't do the trick Sep 18 12:40:27 chroot.sh seems to add it unconditionally <--- there was some parameters such as the rfs_password that has some impact whether the chroot.sh would print them out but ... Sep 18 12:42:03 that is configuring rfs_(console|ssh)_user_pass as empty Sep 18 12:42:08 let's see what that does ... Sep 18 12:45:51 i was basically thinking if someone has thought about a case where user shouldn't be able to log in using a password (and add alternative method for example authorized ssh key in conf specific chroot script) Sep 18 12:48:14 ...that is without modifying the common chroot.sh that is used to build all the images Sep 18 12:53:05 evidently it's not a use case that was considered. why not just customize either the script or the resulting image for your needs? Sep 18 13:40:18 Hello, I'm having troubles with my newly bought BeagleBone Black Wireless. I have installed the latest Debian image (9.1 IoT) via the official beagleboard site and burned it to an sd card. The beaglebone boots fine and I get a terminal window on my screen on which I can log in and start typing commands just as it should be. After one or two minutes the screen freezes and I cannot do anything except rebooting. Also the heartbeat led Sep 18 13:41:01 . Power, wifi and bluetooth leds stay on. The beaglebone also keeps emitting its SSID (BeagleBone-1EBA), but I am unable to connect to it though. I tried older Debian versions or flashing them to the EMMC, but with thesame results. If I try the same with Ubuntu 16.04.3, eveerything works fine without any problems. Also I had another beaglebone black wireless were the same Debian versions used to work fine (altough I broke this one Sep 18 13:41:18 program which relies on Debian on Ubuntu or Angstrom it doesn't work. Have you got any idea what causes this problem and if I can fix it? Sep 18 13:42:08 does the screen really freeze or go black? Sep 18 13:42:24 also what have you changed after installing that? Sep 18 13:42:44 anything interesting in dmesg? Sep 18 13:43:08 also do you have access to its debug UART output? Sep 18 13:43:42 zmatt: yeah, i'm trying to just passwd -l debian at the end of target-specific chroot script but it seems somehow strange to me that building images with access limited to holders of specific key wasn't really considered õ.O Sep 18 13:43:52 (think about all the industrial applications etc) Sep 18 13:47:54 The screen actually freezes, I can even plug or unplug the hdmi and the screen pops back up. Yet I cannot type anything. Sep 18 13:49:47 I have no way of connecting the UART output at work, although I can try this at home. Sep 18 13:51:22 if anything, then there might be console messages around the time when things go wrong Sep 18 13:52:17 you mention wifi, specifically AP mode being on. If this is the wl18xx chipset, then its horrible. Try if turning it off makes that problem go away. Sep 18 13:54:20 I disabled the wifi with the connmanctl but after a minute it still freezes. Sep 18 13:57:36 I am using only usb power from my laptop to boot the bone and noticed I sometimes have to plug it in twice to get it booting. Sep 18 13:58:05 Might the lack of available current cause this (sudden voltage drop). Sep 18 14:10:42 Hi does someone knows if it's possible to run a RTOS on the BeagleBoard-X15? Sep 18 15:04:57 henkbakker: seems highly likely that qnx is available for it Sep 18 15:05:55 TI also has its own rtos for it Sep 18 15:08:41 apparently Mentor Nucleus too Sep 18 15:09:09 I think I've done enough googling for you :P Sep 18 15:09:48 tbr: AP mode on wilink8 is problematic? Sep 18 15:10:30 zmatt: what on wl18xx isn't problematic? Sep 18 15:11:15 so far it Just Worked™ in our (admittedly limited) tests Sep 18 15:11:23 but haven't tried AP mode yet Sep 18 15:11:24 zmatt: I guess I meant "wl18xx and its driver is terrible" && "AP mode is ofen a problem" Sep 18 15:11:43 in the past AP mode was far less well tested than client mode Sep 18 15:11:53 so many chipsets behaved "interesting" Sep 18 15:12:19 that sounds mostly like a good reason to make sure stuff is uptodate Sep 18 15:12:52 a lot improved once Google made AP mode mandatory in 2011 or 2012 Sep 18 15:13:07 I'm actually trying to figure out how to enable dual-role mode (simultaneous AP and station) Sep 18 15:13:38 I've only seen that with Atheros SoCs so far Sep 18 15:14:15 surprisingly it worked fairly well. One limitation is both client and AP must be on the same channel. Sep 18 15:14:31 same on wilink8 Sep 18 15:16:17 but I haven't yet found yet to get it to show up as two interfaces... the wiki page just references some script in TI's sdk to set it up and I can't be arsed to... oh wait a minute I think I already have that sdk unpacked Sep 18 15:19:21 hah, that was easy Sep 18 15:22:09 ( iw phy phy0 interface add wlan1 type managed ) Sep 18 15:23:12 now I guess time to play with hostapd Sep 18 20:58:58 can i deploy and cross compiled executable to BBB via makefile as part of build for a unit test? **** ENDING LOGGING AT Tue Sep 19 03:00:01 2017