**** BEGIN LOGGING AT Wed Sep 27 03:00:01 2017 Sep 27 03:58:15 4.9.x! Sep 27 03:59:26 set_: what distro? Sep 27 03:59:43 i'd use a systemd service, just like any other linux computer Sep 27 03:59:55 but idk much about the beaglebone distros, they do weird shit Sep 27 04:02:01 Debian Sep 27 04:03:01 use a serviced service file. Do you want me to walk you through creating one? Sep 27 04:03:15 Sure...pastebin? Sep 27 04:03:47 i mean, most if it is tweaking options (what directory do you want it run in, what user/group do you want it to run in, what part of the boot process...) Sep 27 04:03:49 Or...you can give me hand by hand instructions. Sep 27 04:03:53 lemme dig up a base Sep 27 04:04:05 Okay...let me start my machine again. Sep 27 04:05:56 alright Sep 27 04:06:02 so here's a pretty simple base: https://ncry.pt/p/EfHn#GBseL-F5NRf5MOc29aGKLnNCJ4zXXGtZ1cMaRcK7iG0 Sep 27 04:06:02 Okay. Sep 27 04:06:35 what site is that? Sep 27 04:06:43 at bare minimum you'll want to update the Description (line 2) and ExecStart (line 9) Sep 27 04:06:54 Can we use Pastebin? Sep 27 04:06:58 ew Sep 27 04:07:00 i guess Sep 27 04:07:03 Yea! Sep 27 04:07:14 Please master Me-Oggi? Sep 27 04:07:32 Judo reference! Sep 27 04:07:43 pastebin is now trying to get me to sign up for an account Sep 27 04:07:48 amazing, they made it even worse Sep 27 04:07:50 https://pastebin.com/ML6b5pym Sep 27 04:07:52 No... Sep 27 04:07:55 Oh...okay. Sep 27 04:07:59 hey at least they got https Sep 27 04:08:09 took them long enough Sep 27 04:08:52 OTay! So, I just follow instructions and bam? Sep 27 04:08:59 what instructions? Sep 27 04:09:09 update lines 2 and 9 at bare minimum Sep 27 04:09:12 I forgot what directory to do to. Sep 27 04:09:28 sorry...to go to. Sep 27 04:09:32 oh Sep 27 04:09:36 okay... gl Sep 27 04:09:47 goes in /etc/systemd/system/whatever-your-service-is-called.service Sep 27 04:09:52 Augh! Sep 27 04:10:27 Hey thefinn93: Why did they take the blah.service section out of the LFS201 course? Sep 27 04:10:49 i have no idea what "LFS201" is Sep 27 04:11:23 linux from scratch 201? Sep 27 04:11:25 lol Sep 27 04:11:29 just guessing Sep 27 04:11:30 Oh. They have a license you can get for Linux. I was into it and still am. I got the LinuxFoundation course to get a cert. Sep 27 04:11:49 a license? Sep 27 04:11:54 Yea boy! Sep 27 04:11:54 you mean like a certification? Sep 27 04:11:57 Yea! Sep 27 04:11:59 oh Sep 27 04:12:03 Cool, heh? Sep 27 04:12:04 that sounds pretty silly Sep 27 04:12:12 I know but people hire people with certs. Sep 27 04:12:34 if you say so Sep 27 04:12:40 Not just degrees, employers want to see what has heppened since graduation. Sep 27 04:12:44 I guess. Sep 27 04:13:02 I make believe stuff, I guess. Sep 27 04:13:25 I am going to set up my system and I will let you know what happens. Sep 27 04:13:30 uh okay Sep 27 04:13:36 ping me if you've got questions i guess Sep 27 04:13:42 OTAY! Sep 27 04:21:32 thefinn93: Hey! It is me. I am lost. Sep 27 04:21:42 I need help with the service again. Sep 27 04:29:40 <<<< on break Sep 27 04:37:53 Oh shit hang on lemme get my laptop back out Sep 27 04:38:04 set_: what's up Sep 27 04:38:07 Otay! Sep 27 04:38:10 Notta. Sep 27 04:38:25 Just shutting down the machine. Sep 27 04:38:55 what help do you need Sep 27 04:39:03 https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/doc/run_config-pin_during_startup.md Sep 27 04:39:10 Does this work for me in my situation? Sep 27 04:40:05 ... Sep 27 04:40:09 i would change Type to oneshot Sep 27 04:40:16 so that it doesn't try to re-run it Sep 27 04:40:23 but idkgenerally looks right Sep 27 04:40:26 I know I am not getting pins to run but getting a file to run. Sep 27 04:40:46 I have a MotorBridgeCape and some software I wrote on the board. Sep 27 04:40:48 oh hrm i wouldn't put it there Sep 27 04:40:50 but that's just me Sep 27 04:40:59 i'd put it in /etc/systemd/system Sep 27 04:41:09 yeah idk about pins and such Sep 27 04:41:29 Okay...I have a Debian Distro with kernel 4.9.x on it. Sep 27 04:41:37 I mostly just do software stuff, learning a bit of hardware Sep 27 04:42:28 Oh. I am running some motors to go forward and then make a u-shape before going forward again, i.e. two motors. Sep 27 04:42:52 cool Sep 27 04:43:15 Yep. I have this metal piece of something. It runs but I need it to mow in lines without going to far. Sep 27 04:43:43 Then, once it reaches the end, it turns 180 degrees and then goes back the way it came. Sep 27 04:44:23 I got as far as 50 cycles of the motors and the u-turn. Sep 27 04:44:38 ... Sep 27 04:44:50 thats pretty cool Sep 27 04:45:04 The issue is that I do not know just how far 50 cycles of the motors is in feet. Sep 27 04:45:21 annd i am not the right person to ask about that :P Sep 27 04:45:29 so, I need it to be around the length of my yard. Sep 27 04:45:30 Okay. Sep 27 04:45:48 The bbb does the brains and the motors are the muscle. Sep 27 04:46:06 So... Sep 27 04:46:15 Back to services and startup scripts? Sep 27 04:46:19 ... Sep 27 04:46:21 sure Sep 27 04:46:24 Cool! Sep 27 04:46:45 the Type value will be important Sep 27 04:47:01 Type=oneshot will run once and after the script is done it wont run again Sep 27 04:47:12 Type=simple will run and if the script exits it will restart it Sep 27 04:47:12 Perfect. Sep 27 04:47:19 Okay. Sep 27 04:47:51 So, let me get my bearings on this quickly. Please hold. Sep 27 04:47:58 sure thing Sep 27 04:48:00 * thefinn93 holds Sep 27 04:48:09 Ha! Sep 27 04:49:47 I do not see where it states type. I see line 10 where it states Restart=always Sep 27 04:50:29 oh sorry, i was referring to the one you linked Sep 27 04:50:35 mine doesn't have a Type value Sep 27 04:50:38 Oh...okay. Sep 27 04:50:39 the default is simple Sep 27 04:50:43 so mine will use that Sep 27 04:51:09 if you want to use oneshot, just add it below the [Service] heading Sep 27 04:51:27 you'll also probably want to modify the user and group that it runs as Sep 27 04:51:42 Okay...do I need to add anything else? For instance, ExecStart? Sep 27 04:51:52 ExecStart and Description Sep 27 04:51:58 like, my service is called taco.service. Sep 27 04:52:06 okay Sep 27 04:52:34 put the command you want in ExecStart Sep 27 04:52:54 note that you have to provide the full path to the binary, there is no default $PATH Sep 27 04:53:25 so eg if it's python you'd do /usr/bin/python /path/to/script.py Sep 27 04:53:47 Okay... Sep 27 04:54:16 So: Sep 27 04:54:59 [Unit] Sep 27 04:54:59 Description=Enable I2C pins Sep 27 04:54:59 After=generic-board-startup.service Sep 27 04:54:59 [Service] Sep 27 04:54:59 Type=simple Sep 27 04:54:59 ExecStart=/usr/bin/enable-i2c-pins.sh Sep 27 04:55:00 [Install] Sep 27 04:55:00 WantedBy=multi-user.target Sep 27 04:55:09 ... Sep 27 04:55:24 Description=Whatever Sep 27 04:55:24 okay for future reference, anything over 3 lines goes in a paste service Sep 27 04:55:32 Okay. Sep 27 04:55:54 some channels will auto-kick-ban you, apparently not this one though :) Sep 27 04:56:11 After=generic-board-startup.service Sep 27 04:56:17 I will pastbin it. Sep 27 04:56:21 mk Sep 27 04:56:22 ...Please hold. Sep 27 04:58:37 https://pastebin.com/icPRRdqQ should show what in the hell I understand versus what is really going on. Sep 27 04:59:39 looks about right Sep 27 04:59:45 not sure how well quotes will work out Sep 27 04:59:55 on the ExecStart line Sep 27 05:00:01 I am going to try it again. Oh, do not worry. i will not use those quotes. Sep 27 05:00:04 i'd suggest pasting what you actually use Sep 27 05:00:08 Okay. Sep 27 05:00:11 Please hold. Sep 27 05:00:14 your filesystem can't be that secret Sep 27 05:00:21 it is not. Sep 27 05:02:19 https://pastebin.com/tyUg8Wat Sep 27 05:03:10 okay, should work Sep 27 05:03:11 I can cp that file to another directory if necessary but it has to be in the MotorBridgeCapeforBBG_BBB/BBG_MotorBrigeCape directory. Sep 27 05:03:22 ... Sep 27 05:03:28 Cool, I will try it. Sep 27 05:03:33 does it need to be executed from a particular directory? Sep 27 05:03:45 also, does the file have a #! line? Sep 27 05:03:50 No. Sep 27 05:03:55 it'll need one of those Sep 27 05:04:00 or give the path to the interperter Sep 27 05:04:21 ExecStart=/usr/bin/python3 /var/lib/cloud9/MotorBridgeCapeforBBG_BBB/BBG_MotorBridgeCape/DCIII.py Sep 27 05:04:42 (unless you use ancient python 2.x, in which case /usr/bin/python /var/lib/cloud9/MotorBridgeCapeforBBG_BBB/BBG_MotorBridgeCape/DCIII.py) Sep 27 05:04:58 Dang. So, for a .py file, it is #!/bin/python? Sep 27 05:05:10 I use 2.7.x. Sep 27 05:05:14 jesus Sep 27 05:05:19 Ha! Sep 27 05:05:54 anyway, it's usually #!/usr/bin/env python Sep 27 05:06:08 Okay. Sep 27 05:06:20 then you need to run chmod +x on it Sep 27 05:06:23 chmod +x /var/lib/cloud9/MotorBridgeCapeforBBG_BBB/BBG_MotorBridgeCape/DCIII.py Sep 27 05:06:34 Right. Sep 27 05:08:57 then you'll need to make it automatically start: systemctl enable taco.service Sep 27 05:09:05 Ha! Sep 27 05:09:07 Okay. Sep 27 05:09:24 and if you want to start it without rebooting, systemctl start taco.service Sep 27 05:13:37 ...well. Sep 27 05:13:50 That was an issue for me for some amount of time now. Sep 27 05:14:12 It is late. I am going to try this out tomorrow most likely. Sep 27 05:14:18 ok Sep 27 05:16:05 That you, thefinn93. Sep 27 05:16:11 np Sep 27 05:16:33 I can use this now for starting scripts when they are not .js files. Sep 27 05:17:11 The autorun folder on our systems, BBB and variants, has a .js file fondness or something. Sep 27 05:17:18 ... Sep 27 05:19:02 Anyway...if you need anything for promoting motors to run, let me know. Sep 27 05:19:14 I like to dabble in making two motors do things with specific software. Sep 27 05:21:45 Cool Sep 27 05:22:10 Yeah idk what the beaglebone software does by default Sep 27 05:22:17 I try to avoid using it Sep 27 05:22:46 Its like "Debian" but heavily modified in crazy ways that make me scared Sep 27 05:25:13 It is just something more to learn, I guess. Sep 27 05:31:54 I opted for building clean Debian, seemed to work fine and with much less surpises Sep 27 05:32:43 Well, clean ish. Found some shit on GitHub that would build images without all the crazy additions like cloud9 Sep 27 05:33:17 Which seems to be a glorified web-based backdoor for anyone on the same network last I checked Sep 27 05:34:08 Some people like Cloud9 while others dislike it. I noticed. Sep 27 05:36:30 My only issue is having it pre-loaded with no warning Sep 27 05:37:05 Oh...I dislike that it makes me program software more. I found that I cannot copy and paste when I choose. Sep 27 05:37:31 I need practice but sometimes I am just lazy. Sep 27 05:37:50 Oh, I never got beyond realizing what it was and removing it as quickly as possible Sep 27 05:38:15 Should I be paranoid about Cloud9? Sep 27 05:38:38 Idk Sep 27 05:38:58 Haha. I guess not. It is just another IDE. Sep 27 05:39:39 No other IDE that I'm aware of provides full access to your system to anyone on the same network Sep 27 05:39:45 If someone wanted info, they could get it. People are way more talented than me and they can use their own software. Sep 27 05:39:55 Damn. I did not know that. Sep 27 05:40:11 Maybe they fixed it since I looked last Sep 27 05:40:16 I doubt it Sep 27 05:40:19 Maybe so. Sep 27 05:40:48 Who knows? Sep 27 05:41:03 I do not care so much. I do not go to diners with free WiFi. Sep 27 05:41:07 thefinn93: at least you can no longer (by default) log in as root with blank password :P Sep 27 05:41:37 thefinn93: and of course now plenty of people complain about that since they considered it convenient Sep 27 05:41:59 Oh they fixed that finally? Sep 27 05:42:08 Still never using any software from them ever Sep 27 05:42:46 though it still tells you the default username and password when you try to log in, and that user is a sudoer... so yeah :P Sep 27 05:43:06 Lol Sep 27 05:43:08 and yet we still get people here who are unable to log in Sep 27 05:43:37 I'm not sure there's an easy fix for all this Sep 27 05:44:07 I think for quite a few users it makes enough sense to just be able to log in if you're on the same physical network Sep 27 05:44:22 (and cloud9 isn't really any more of a security threat then either) Sep 27 05:44:33 Fine but distribute that separately and with large warnings Sep 27 05:46:53 That's not okay for the default os Sep 27 05:46:54 don't get me wrong, I don't use it either :P I've always started with a console image, removed any crap I don't care about, and installed stuff I do care about Sep 27 05:47:27 It's okay for the default os of an "tinkering" embedded system I think Sep 27 05:48:06 but it would be nice to maybe have a setup wizard to configure such choices initially Sep 27 05:48:06 Maybe at least distribute a secure one and don't call the insecure one "Debian" Sep 27 05:48:49 * zmatt shrugs Sep 27 05:49:03 I kinda agree, but I also kinda get their approach Sep 27 05:49:48 at least security improved over time, maybe it eventually ends up with secure defaults (if they can figure out a way to make that usable) Sep 27 11:09:02 BBBW noob here. Could anyone help me with configuring uEnv and UARTs & SPI? Sep 27 11:09:11 I have some questions about it Sep 27 11:13:44 start out by ensuring you are running a recent image Sep 27 11:17:06 Hmmm I'm using bone-debian-9.1-iot-armhf-2017-08-31-4gb.img Sep 27 11:17:25 Should I use bone-debian-9.1-iot-armhf-2017-09-21-4gb.img.xz ? Sep 27 11:24:41 sounds recent enough Sep 27 11:25:16 please note that most of the "guides" and "exactsteps' you'll find on the internet are heavily outdated in this respect Sep 27 11:27:09 Something I haven't understood, even the other times. With my BBBW I want to run it with the SD. So I turn emmc off Sep 27 11:27:28 But sometimes they say to push USR button while it's booting or something similar Sep 27 11:27:50 Why? Should I do it now that I burnt the latest image in the SD card? Sep 27 11:28:11 In my BBBW I have RESET, POWER and S2 button Sep 27 11:28:40 how did you disable the eMMC? Sep 27 11:29:12 I usually edit uEnv.txt once I ssh into the BB Sep 27 11:29:29 With 31/08/17 image I uncommented disable_uboot_overlay_emmc=1 Sep 27 11:29:38 I think it's enough Sep 27 11:30:30 actually there are things that are active way before that will apply Sep 27 11:30:51 e.g. it's possible that SPL and U-Boot itself will be read from eMMC Sep 27 11:31:18 holding down the S2 button prevents that, so does wiping the first few hundred kb of the eMMC Sep 27 11:31:31 Only the first time, right? Sep 27 11:32:03 until a hard reset or power down Sep 27 11:32:09 in case of S2 Sep 27 11:32:33 Hmmm everytime I turn my BB on? Sep 27 11:33:26 With usb or the 5V plug Sep 27 11:35:23 For example. Now: Sep 27 11:35:35 - Burnt the latest image with Etcher Sep 27 11:35:54 - Holding S2, I plugged the usb into BBBW Sep 27 11:36:02 PWR led is on but nothing is happening Sep 27 11:36:12 I released s2 but nothing is not booting Sep 27 11:38:13 I unplugged usb and plugged it, without holding s2 and now it's booting Sep 27 11:43:57 Ok now I'm in. I edited uEnv.txt disabling emmc and video Sep 27 11:44:08 Reboot Sep 27 11:44:17 Should I see cape_universal in my slots? Sep 27 11:44:43 There is not Sep 27 11:45:18 ? Sep 27 11:56:17 if it does not boot with s2 held down, then your SD card is not properly prepared Sep 27 11:58:03 Hmmm I can retry even if I didn't nothing special but download+etcher+put the sd in Sep 27 11:58:17 What about my previous questions? Sep 27 11:58:26 do you have anything on the emmc that you need? Sep 27 11:59:44 Nope Sep 27 12:00:05 Never used it Sep 27 12:00:43 remove the sd-card, boot the bone, dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=1 Sep 27 12:00:51 that will permanently wipe your eMMC Sep 27 12:01:04 then you also don't need to press S2 to boot from SD card Sep 27 12:02:07 Hm I'll do it now Sep 27 12:02:37 A question. I will need, for example, 100 BBBW with all the same config Sep 27 12:02:57 Shall I erase all their emmc first? Sep 27 12:03:14 Can't I make 100 sd cards and just put them inside and turn the BB on? Sep 27 12:03:16 :/ Sep 27 12:03:22 that depends on what you plan to do Sep 27 12:03:52 They will have sensors and connectivity Sep 27 12:04:05 I expect to have the same pins active on every boards Sep 27 12:05:28 you could incorporate the necessary functionality into your SD-card image (check if eMMC is blanked, if not blank the first 1MByte) Sep 27 12:06:13 or make a flasher card to flash tha image onto each BBBW's eMMC Sep 27 12:06:21 *that image Sep 27 12:06:31 or that Sep 27 12:06:40 Right Sep 27 12:06:46 that's why I said it depends Sep 27 12:06:55 there are many ways to skin a beagle Sep 27 12:07:32 I'll have lunch and I will try to erase emmc Sep 27 12:09:44 blkdiscard /dev/mmcblk1 Sep 27 12:14:43 (will erase entire eMMC) Sep 27 12:18:35 much more elegant, indeed Sep 27 12:25:43 Ok blkdiscarded Sep 27 12:26:08 Now, put the sd in, boot without s2 held? Sep 27 12:28:33 yes Sep 27 12:28:50 you can first verify by not putting in a sd card Sep 27 12:28:54 and powering it up Sep 27 12:28:58 it should not do anything Sep 27 12:29:56 Yep confirmed Sep 27 12:30:18 good, then you can now be sure that whatever you do is only SD card related Sep 27 12:30:56 that's the main reason I suggested it. It can easily happen that you get confused by U-Boot being loaded from e.g. eMMC and being a different version or differently configured Sep 27 12:34:06 Ok now I see GPIO allocated in my dmesg Sep 27 12:34:07 but debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots cat: /sys/devices/platform/bone_capemgr/slots: No such file or directory Sep 27 12:34:31 Is it ok? :/ Sep 27 12:34:44 (I'm still here) Sep 27 12:36:43 which kernel is that image running? Sep 27 12:36:54 also not sure where that should reside currently Sep 27 12:37:00 Linux beaglebone 4.4.88-ti-r125 Sep 27 12:37:59 find /sys |grep capemgr Sep 27 12:40:06 https://pastebin.com/kGSs5Cs0 Sep 27 12:40:32 The file /sys/firmware/devicetree/base/bone_capemgr/#slots is empty Sep 27 12:41:55 try throwing some dtbo files at it? or whatever was the way to load slots Sep 27 12:42:58 What do you mean? Sep 27 12:44:31 https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md#capemgr-enabledisable-capes-with-slots Sep 27 12:45:03 though I'm a bit confused that there is a hash character in your slots file Sep 27 12:45:33 Me too :/ Sep 27 12:46:16 The kernel became social lol Sep 27 12:46:42 you could try this (correct the path?): sudo sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots" Sep 27 12:47:38 oot@beaglebone:/home/debian# sudo sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots" sh: 1: cannot create /sys/devices/platform/bone_capemgr/slots: Permission denied Sep 27 12:47:44 Note that I was root Sep 27 12:47:54 (correct the path?) Sep 27 12:48:18 try /sys/firmware/devicetree/base/bone_capemgr/#slots Sep 27 12:48:24 Ok I'll try Sep 27 12:48:30 not sure if that's the right thing Sep 27 12:49:26 Permission denied Sep 27 12:50:16 try the uEnv.txt route? Sep 27 12:51:13 Already edited it Sep 27 12:51:13 https://pastebin.com/ERJiU6dB Sep 27 12:51:27 disable_uboot_overlay_emmc=1 Sep 27 12:51:27 disable_uboot_overlay_video=1 Sep 27 12:51:35 enable_uboot_cape_universal=1 Sep 27 12:52:01 Do you mean, opening uart via bone_capemgr.enable_partno= ? Sep 27 13:00:08 yes Sep 27 13:07:40 Let me try Sep 27 13:22:11 Hmm I added Sep 27 13:22:12 cape_enable=bone_capemgr.enable_partno=BB-UART1 Sep 27 13:22:46 dev /dev/ttyS1 was there even before Sep 27 13:24:07 I have a sensor plugged to UART1_RXD but the script is not reading ttyS1 Sep 27 13:24:21 Something is not working :/ Sep 27 13:24:25 Should I try another image? Sep 27 13:24:28 Gorgo_: there's no need to load an overlay for that Sep 27 13:24:42 you need to configure the pins with config-pin Sep 27 13:25:13 Even if my slots file is missing? Sep 27 13:26:23 Gorgo_: that is a bit odd Sep 27 13:26:34 config-pin won't care, but it's still odd Sep 27 13:26:39 Hmmm ok it's working after config-pin p9.26 :) Sep 27 13:27:30 tbr: nothing in /sys/firmware is writeable Sep 27 13:27:47 in /sys/firmware/devicetree/base I mean Sep 27 13:29:09 Gorgo_: also, using sudo when you're already root is completely pointless Sep 27 13:30:11 Right :D Sep 27 13:36:23 I'm trying SPI0 now Sep 27 13:54:39 Hmmm in order to ssh -X to my BB, is it ok installing xorg? Sep 27 13:54:59 uhhhh Sep 27 13:55:29 you don't need xorg (X server) to run X clients via ssh X11 forwarding Sep 27 13:56:12 Hmmm If I run my camera q4 app, it returns Sep 27 13:56:12 cannot connect to X server Sep 27 13:56:36 I've installed qt4-dev-tools as described here Sep 27 13:56:41 https://github.com/groupgets/LeptonModule/tree/master/software/beagleboneblack_video Sep 27 13:58:06 this is a camera connected via spi ? Sep 27 13:58:26 Yes Sep 27 13:58:28 And i2c Sep 27 13:58:29 ah, flir Sep 27 13:59:24 you want to display the video to a display connected to the beaglebone? Sep 27 13:59:36 or via ssh X11 forwarding to your own computer? Sep 27 14:00:44 Hmmm via ssh to my pc Sep 27 14:00:47 for the latter, I'm pretty sure that you don't need to install any additional packages on the beaglebone, just use ssh -X from a linux system to the beaglebone and it should work Sep 27 14:01:39 Ok I logged out and relogged it and it's working :O Sep 27 14:01:46 I was with -X before as well Sep 27 14:02:09 ¯\_(ツ)_/¯ Sep 27 14:02:34 ༼ ºل͜º ༽ Sep 27 14:03:12 maybe your beaglebone heard me saying that it should work, and it was like "oh, it should? crap, I'll stop pretending it doesn't then" Sep 27 14:04:02 ;) Sep 27 14:04:43 Ahahah the AI is moving forward lately Sep 27 15:01:49 Using ttyS5 or ttyO5 is the same thing? Sep 27 15:02:00 *ttyO5 Sep 27 15:04:57 Gorgo_: S5 and O5 differs between which driver. Usually they are the same thing. Sep 27 15:24:38 Hello, I was reading up on the IRC archives about someone that had a similar issue but it never was resolved. I am dealing with a "RuntimeError: Unable to export UART channel" when I run my python code after importing the Adafruit PyBBIO library. I went into more detail on StackOverflow if you think this might be something you can help fix: https://stackoverflow.com/questions/46437393/unable-to-export-uart-channel-on-beaglebone Sep 27 15:30:24 probably means the PyBBIO library is outdated or broken Sep 27 15:31:19 actually, I don't think you need it for anything at all, just use the serial module Sep 27 15:32:53 Gorgo_: only one of the two is real, the other is a symlink Sep 27 15:33:16 (the symlink is created for backwards compatibility) Sep 27 15:33:57 I can get my code working flawlessly when I connect my device via usb port Sep 27 15:34:05 however, this port is taken on the final project Sep 27 15:34:58 * zmatt stares confusedly at spaceman Sep 27 15:35:04 what does usb have to do with serial? Sep 27 15:36:16 nothing apparently haha. I'm a bit new to beaglebone..and programming on it in general Sep 27 15:36:47 so you're talking about the pins that are just inside the P9? Sep 27 15:39:33 you were talking about the Adafruit_BBIO UART module. I immediately guessed that the error is due to the module doing something silly and/or obsolete. (overall the Adafruit stuff is pretty crappy and poorly maintained) Sep 27 15:40:11 upon taking a closer look, I noticed that its UART module actually performs no useful function at all anymore and can simply be removed Sep 27 15:40:47 the code snippet you linked to already uses the 'serial' module for the actual serial communication, that part is fine Sep 27 15:41:37 be sure to configure the pins you want to use for uart communication using the 'config-pin' tool Sep 27 15:42:36 Huh, interesting. Maybe some project background might help as well. I have an arduino that is connected to an array of sensors, in the console I can turn on a sensor through the serial console like { t 1 }....this would turn the temperature sensor on and display on the console. Now I've been tasked with being able to "talk" to the arduino serial console through a beaglebone. I developed some python code that reads and writes to and Sep 27 15:42:46 needed to move it to a UART pinout I thought Sep 27 15:43:11 config-pin tool, hmm, that's definitely not in my code Sep 27 15:44:23 it's a commandline utility to configure pins (hence the name) Sep 27 15:46:59 note: be careful when interfacing with an external microcontroller that has its own power supply. you should ensure that no external voltage is being applied to the beaglebone's I/O pins when the beaglebone is powered down Sep 27 15:47:36 Alright zmatt, thanks so far. Looks like I have a write error "no such file or directory" error loading device tree overlay file: cape-universala Sep 27 15:47:48 when trying to config P9_21 as a uart Sep 27 15:47:57 (powering the external microcontroller from the beaglebone's 3.3v supply is a possibly solution, if it can be powered from 3.3v and the bbb can supply enough current) Sep 27 15:48:05 it said I needed to config-pin overlay cape-universala Sep 27 15:48:11 uhh, have you made changes to /boot/uEnv.txt ? Sep 27 15:48:20 no, it shouldn't be necessary to load any overlay Sep 27 15:48:34 it's loaded by default in all current images (since quite a while already) Sep 27 15:48:56 hmm i dont even have that file structure, says that uEnv.txt is no directory Sep 27 15:49:07 i seem to remember seeing it somewhere else tho Sep 27 15:49:11 ehm what? Sep 27 15:49:14 what are you running? Sep 27 15:49:27 uname -r Sep 27 15:49:30 cat /etc/dogtag Sep 27 15:49:32 Debian 3.3.9-ti-r25 Sep 27 15:49:38 O.O Sep 27 15:49:43 kernel 3.3 ?! Sep 27 15:49:47 what? Sep 27 15:49:50 whoops Sep 27 15:49:51 4.4 Sep 27 15:49:54 ohh Sep 27 15:49:54 4.4.9 Sep 27 15:49:59 typos :') Sep 27 15:50:10 what does /etc/dogtag say ? Sep 27 15:50:25 Beagleboard.org Debian Image 2016-05-13 Sep 27 15:50:40 ouch, pretty ancient Sep 27 15:50:59 huh strange, it should have flashed the most recent.. Sep 27 15:51:06 very clearly not Sep 27 15:51:15 of course :P Sep 27 15:51:31 latest is 6 days old Sep 27 15:51:42 wait, if I run the beaglebone with the memcard it runs a different image, one sec Sep 27 15:52:33 to reflash eMMC, make a flasher card (either by downloading a flasher image, or by turning a standalone card into a flasher card by editing one line in /boot/uEnv.txt ) Sep 27 15:52:56 regardless btw, even in 2016 there most definitely was a /boot/uEnv.txt Sep 27 15:53:11 so with the memcard inserted it's a 2017-08-31 build Sep 27 15:53:33 that's plenty recent Sep 27 15:53:44 here let me screenshot Sep 27 15:53:56 if you want to flash that onto eMMC, follow these instructions: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC Sep 27 15:53:59 https://snag.gy/cboTRs.jpg Sep 27 15:54:06 (note: that will completely wipe eMMC) Sep 27 15:54:29 ehm, /boot/uEnv.txt is a file, not a directory Sep 27 15:54:38 oh Sep 27 15:54:40 duh Sep 27 15:54:48 note that it says "Not a directory" rather than "No such file or directory" Sep 27 15:55:12 thanks for dealing with my mistakes haha, okay I have that txt file open Sep 27 15:55:36 see here it says my uname is 3.8.13 Sep 27 15:56:17 eh what? on the image from 2017-08-31 ? Sep 27 15:56:52 what does /etc/debian_version say there? Sep 27 15:56:56 yea...okay so this might be because the pybbio library i was trying to use, said that it wasn't compatible with newer kernels Sep 27 15:57:01 one sec Sep 27 15:57:12 you mean you installed an ancient kernel ? Sep 27 15:57:30 that's really not a good idea Sep 27 15:57:53 yea well, I was following instructions haha Sep 27 15:57:59 low and behold, that lib didnt work Sep 27 15:58:11 plenty of stupid stuff gets put on the internet Sep 27 15:58:16 it was a library meant to emulate the arduinos Wire library Sep 27 15:58:26 so woulda been handy for me Sep 27 15:58:59 btw debian_version says 9.1 Sep 27 15:59:43 okay, so you're indeed running a nice uptodate system... now please ditch that prehistoric kernel in favor of a 4.4 or 4.9 kernel :P Sep 27 16:00:21 lol :D so I've tried to reflash off of the memcard but I guess it isn't updated the kernel? Sep 27 16:00:42 it sounds like you didn't reflash eMMC at all? Sep 27 16:00:50 I just hold down the button near the usb port till the 4 lights turn on right? Sep 27 16:01:05 no Sep 27 16:01:18 huh wat Sep 27 16:01:38 I explained reflashing eMMC less than 10 minutes ago Sep 27 16:01:45 oh that Sep 27 16:01:55 sorr Sep 27 16:01:57 sorry* Sep 27 16:02:24 the button you're referring to is only very rarely needed to force booting from sd Sep 27 16:02:24 those were the instructions that I read on the bbb getting started page hmm Sep 27 16:02:30 ah Sep 27 16:02:56 if held down during power-on (you can let go as soon as any led lights up), it removes eMMC from the boot order Sep 27 16:03:19 however normally u-boot will already prefer booting from μSD over eMMC anyway Sep 27 16:04:23 alright going through flashing process steps you linked, one sec Sep 27 16:05:57 rebooting Sep 27 16:09:05 yep taking longer than in the past, and leds are rippling back and forth, actually flashing! I've had networking problems with connecting the bbb so hopefully i can git pull the new kernel as well with no issues Sep 27 16:15:45 hey matt, still around? lights are off so I think flashing is complete. is there anything you'd like to check? Sep 27 16:16:17 sounds indeed like flashing is complete Sep 27 16:16:30 as the wiki says, don't forget to remove the card before turning it on again Sep 27 16:16:35 right :~) Sep 27 16:16:49 removed and powering on Sep 27 16:19:57 all 4 USR LEDS are still solid, normal after flash? Sep 27 16:20:01 nope Sep 27 16:20:10 ugh Sep 27 16:20:50 ohh, you still had that prehistoric kernel installed Sep 27 16:21:00 yeah that's not gonna work Sep 27 16:21:12 lol Sep 27 16:21:30 it is possible to fix this without reflashing Sep 27 16:21:48 though, hmm, not very easily Sep 27 16:22:04 how do i update that if I cant even access the file manager thru putty? Sep 27 16:22:13 (just looking at the kernel upgrade process on that doc u sent) Sep 27 16:22:21 you have a linux host system right? Sep 27 16:22:35 Windows work laptop Sep 27 16:22:41 oh Sep 27 16:22:41 @zmatt: Could you please tell me again the command to erase emmc? :) Sep 27 16:22:49 Gorgo_: blkdiscard /dev/mmcblk1 Sep 27 16:22:51 Tnks Sep 27 16:22:53 (sudo) Sep 27 16:23:18 spaceman: that's a problem since you need to fix the /boot/uEnv.txt on the card Sep 27 16:23:29 and you can't mount an ext4 filesystem on windows Sep 27 16:23:46 so it might actually be easier to just reflash the sd card with the image you downloaded Sep 27 16:24:38 you can then boot from sd card, and either reflash eMMC again or manually fix the /boot/uEnv.txt on eMMC to select the 4.x kernel instead of the 3.8 kernel you installed Sep 27 16:24:39 the one that you said was ancient? Sep 27 16:24:44 ? Sep 27 16:24:51 no, the very recent one Sep 27 16:25:50 the one you downloaded a few days ago presumably (since it was dated 2017-08-31) Sep 27 16:25:56 ok, hopefully I can explain my confusion. I just flashed from SD card and got stuck on boot afterwards, so you just want me to try and reflash the same thing again? Sep 27 16:26:21 ok, the problem is: you installed a 3.8 kernel on that card right? by following some random instructions on the internet Sep 27 16:26:42 of sorts yes haha Sep 27 16:26:47 then you turned the card into a flasher, so it flashed that recent-image-but-with-3.8-kernel onto eMMC Sep 27 16:27:21 that won't boot (I'll spare you the reasons) from eMMC Sep 27 16:27:28 and you can't boot the sd card since you turned it into a flasher Sep 27 16:28:13 and you can't change the sd card back into a normal system since you can't edit a file on it if you don't have a linux system available Sep 27 16:28:37 https://snag.gy/KfcEsM.jpg these were the steps I took to downgrade kernel, if that helps Sep 27 16:28:40 so my suggestion is to create a clean sd card based on the 2017-08-31 image you downloaded Sep 27 16:29:06 you can then boot the beaglebone from that image Sep 27 16:29:09 *that card Sep 27 16:29:22 and then I'll tell you how to fix eMMC Sep 27 16:29:31 (there's no need to reflash eMMC) Sep 27 16:30:17 this is the image i have on the SD card rn, https://snag.gy/b6opy4.jpg plug it in and boot from that? Sep 27 16:30:52 yeah Sep 27 16:31:06 btw, if you don't specifically need a GUI, you might want to consider the "iot" image instead of the "lxqt" image Sep 27 16:31:23 the lxqt image doesn't leave much free space on eMMC Sep 27 16:31:59 wait! Sep 27 16:32:03 I just realized something Sep 27 16:32:05 gotcha, alright so confused again. I mean we edited the env.txt reflash the beaglebone every time a card is added Sep 27 16:32:17 whats that? Sep 27 16:32:34 insert any random sd card into the beaglebone, one that's not bootable (e.g. a blank card) Sep 27 16:32:37 then power it on Sep 27 16:32:59 uh okay, I don't have an extra haha, just wipe my current one I guess? Sep 27 16:34:49 if so, I need to run upstairs into the lab, brb Sep 27 16:37:43 alright, formatted sd card and inserted back into the beaglebone and powered on. Still have 4 solid LED Sep 27 16:38:19 dang, that should have worked Sep 27 16:38:36 then there's some other problem going on that's preventing it from booting I guess Sep 27 16:39:03 bummer :/ Sep 27 16:40:25 then back to previous plan I guess: write the 2017-08-31 image to card again and boot from that Sep 27 16:40:27 i guess i dont understand the differences between kernels and actual os but what about flashing a version of debian that uses that kernel Sep 27 16:40:35 okay one sec Sep 27 16:41:50 fashing, says about 5 mins Sep 27 16:41:55 fyi Sep 27 16:41:57 3.8 kernel is really really really old Sep 27 16:42:30 it was the default in debian wheezy (7) Sep 27 16:42:51 debian jessie (8) already used 4.x kernels, and you're now running a debian stretch (9) system Sep 27 16:43:15 wheezy is obsolete and unmaintained Sep 27 16:43:27 so, I wouldn't recommend going down that path Sep 27 16:43:44 yea, I didn't realize unfortunately. I don't have to do much with the BBB so I thought dropping the kernel version wouldn't cause conflicts. Shoulda known better Sep 27 16:44:04 basically just read/write to the console to control the arduino Sep 27 16:44:41 everything is a learning process though, I do appreciate your help so far Sep 27 16:46:08 the issue with the old kernel here btw is probably that the bootloader (u-boot) is too new for it Sep 27 16:46:42 although I can't be sure, there might be other issues as well Sep 27 16:47:13 do you think there's any correlation to the old kernel and the bbio library? Sep 27 16:47:20 the adafruit one Sep 27 16:47:34 note that the instructions you screenshotted actually say "If you are using a recent Debian image with a 3.14 kernel" ... 3.14 is just as ancient and obsolete as 3.8 ;-) Sep 27 16:47:44 i.e. those instructions are also ancient and obsolete Sep 27 16:48:17 that was a diff library haha Sep 27 16:48:34 the problem (well, one of the problems) with the adafruit library is that it seems to be barely maintained Sep 27 16:49:03 parts of it anyway Sep 27 16:49:31 last commit was in august but yea, parts of it Sep 27 16:50:25 yeah, basically sometimes people care enough about some part of it to fix it and send a pull request :) Sep 27 16:50:35 okay flash is done, just plug in card and reboot? and true :P Sep 27 16:50:55 yeah, and then I'll guide you through fixing eMMC Sep 27 16:51:17 okay, booting now Sep 27 16:51:32 alternatively you can reflash eMMC the same way you did before, if you don't mind the loss of whatever was on the card Sep 27 16:52:07 uhhh so, lights are flashing and not solid, lets give it a sec haha Sep 27 16:52:29 oh wait reflashing isnt it hmm Sep 27 16:52:53 no, it's just booting Sep 27 16:53:10 flashing required editing its /boot/uEnv.txt if you recall Sep 27 16:53:33 lol so confused, well it's booting you're right. The file manager just came up Sep 27 16:54:06 alright ive opened up putty Sep 27 16:54:12 so, right now you've booted from sd card, but you can also access eMMC Sep 27 16:54:34 right Sep 27 16:56:29 sudo mkdir -p /mnt/tmp Sep 27 16:56:35 sudo mount /dev/mmcblk1p1 /mnt/tmp Sep 27 16:57:04 now the contents of eMMC is accessible at /mnt/tmp Sep 27 16:57:29 two commands inputted Sep 27 16:57:45 alright i cd'd over there Sep 27 16:57:48 if you check the contents of /mnt/tmp/boot you'll see that (at least) two kernels are installed Sep 27 16:58:02 your 3.8 kernel but also still the 4.4 kernel that was originally on it Sep 27 16:58:22 i see a lot lol, lemme screen shot but yes 3.8's or 4.9's Sep 27 16:58:34 or 4.9 even Sep 27 16:58:49 https://snag.gy/fwRrJh.jpg Sep 27 16:59:25 yeah, so you have three kernels installed: 3.8.13-bone79, 3.8.13-bone86, and 4.9.45-ti-r57 Sep 27 16:59:43 ah the first three on the list ok Sep 27 17:00:09 yeah, for each you have multiple files: config, initrd.img, System.map, and vmlinuz Sep 27 17:00:12 Ok I quit, thanks zmatt and tbr :) Sep 27 17:00:25 that makes sense! Sep 27 17:00:29 (and more files elsewhere) Sep 27 17:00:41 so, you'll need to edit the uEnv.txt there Sep 27 17:00:56 in it will be a line saying uname_r=3.8.13-bone86 Sep 27 17:01:07 change that to uname_r=4.9.45-ti-r57 Sep 27 17:01:14 i see that, ok one sec! Sep 27 17:01:57 done Sep 27 17:02:10 leave the /mnt/tmp directory Sep 27 17:02:14 sudo umount /mnt/tmp Sep 27 17:02:26 sudo poweroff Sep 27 17:02:31 remove card, power on again :) Sep 27 17:03:23 okie! Sep 27 17:03:32 powering off Sep 27 17:04:13 i did get a message that said /mnt/tmp target is busy Sep 27 17:04:32 but it added an new input line and I typed poweroff Sep 27 17:04:44 lights still on tho Sep 27 17:04:52 oh jk Sep 27 17:05:39 cat /dev/mmcblk0 > /dev/mmcblk1 Sep 27 17:05:43 woups. wrong window. Sep 27 17:06:03 if you're following instructions but get an error or unexpected response at some step, it's typically a good idea to pause there and ask for guidance instead of continuing :) Sep 27 17:06:05 I would not recommend doing that line. Sep 27 17:06:35 spaceman: fortunately, it's not a problem in this case since the umount was kinda unnecessary anyway (poweroff will unmount all filesystems) Sep 27 17:06:50 ah okay :) lights are flashing, just waiting for file explorer to pop up Sep 27 17:06:51 Spidler: indeed Sep 27 17:07:50 zmatt: Works for me since it's read/only mounted from a initrd, but yeah. (also, I don't have dd in my initrd for some reason) Sep 27 17:08:14 spaceman: and then you'll want to consider: sudo apt-get purge linux-image-3.8.13-bone79 linux-image-3.8.13-bone86 Sep 27 17:08:44 while optionally saying out loud "begone, thy foul beast!" Sep 27 17:08:54 ;) Sep 27 17:09:02 Hah. Sep 27 17:09:04 gotcha, still waiting on the bbb to come up Sep 27 17:09:24 leds still doing blinkyblinky stuff ? Sep 27 17:09:55 One of these days I'll sit down and figure out how to get the RTS pin to work in a modern serial driver. Sep 27 17:10:01 yea USR0 heartbeat and and USR2 blinking fast Sep 27 17:10:19 spaceman: note that you can probably already log in with putty at this point Sep 27 17:10:41 Spidler: for hw flow control? Sep 27 17:10:45 zmatt: yea Sep 27 17:10:49 ill give it a shot Sep 27 17:10:52 zmatt: necessary for rs485 Sep 27 17:11:04 Spidler: that's not hw flow control Sep 27 17:11:15 No, its rcn Sep 27 17:11:20 no luck on putty Sep 27 17:11:21 that's driver enable Sep 27 17:11:21 Which is weirder and worse Sep 27 17:11:35 Spidler: hw flow control *is* supported by both drivers Sep 27 17:11:53 okay, then I have to re-do my tests Sep 27 17:12:17 should I try restarting? Sep 27 17:12:18 I think using rts pin for rs485 driver-enable is too, but iirc it requires configuration in DT (with different syntax depending on driver) Sep 27 17:12:26 spaceman: in general, no Sep 27 17:12:29 Yea, it does. Sep 27 17:12:32 okay Sep 27 17:12:49 spaceman: hard to say what could be going wrong this time :/ Sep 27 17:13:20 oh, maybe I should have made you check on the amount of free space on eMMC Sep 27 17:14:04 how do i do that? Sep 27 17:14:29 boot from card, mount eMMC (same as before), then: df -h /mnt/tmp Sep 27 17:15:32 alright, one moment Sep 27 17:17:17 though, regardless of whether that's indeed the issue or not, at this point it's probably easiest to just reflash the eMMC. if you still have any important files on it (that were previously on the sd card before you wiped it) you can rescue those while you have it mounted Sep 27 17:18:52 I just need my one python code file Sep 27 17:19:46 so since I am booting from my card, how do I get to that file? It was in /var/lib/cloud9/python_code Sep 27 17:19:55 and going there with card is different obvs Sep 27 17:20:13 after mounting emmc at /mnt/tmp it would be /mnt/tmp/var/lib/cloud9/python_code Sep 27 17:21:13 do i make the directory again too? Sep 27 17:21:28 it should still be there Sep 27 17:21:59 you can mount a filesystem at any empty directory Sep 27 17:22:50 ugh wait it was probably on the card, it's okay wasn't difficult code Sep 27 17:23:51 you mean it was probably on the emmc before you reflashed it (I did warn this would wipe emmc) Sep 27 17:23:52 anywho i have 476M available Sep 27 17:24:03 yea it was my fault Sep 27 17:24:12 it was just 40 or so lines Sep 27 17:24:18 easily replicated Sep 27 17:24:22 okay, so it didn't run out of free space Sep 27 17:24:33 then I have no idea why it's not booting Sep 27 17:24:45 flashing a fresh image should fix it anyway Sep 27 17:25:22 okay, same method on that link you sent at the beginning? Sep 27 17:26:12 yes Sep 27 17:26:17 same as before Sep 27 17:27:06 alternative you can download a pre-made flasher image from that same wiki page Sep 27 17:27:11 ok Sep 27 17:27:34 (look for "Flasher: (stretch-lxqt)" for an image with GUI or "Flasher: (stretch-iot)" for one without GUI) Sep 27 17:28:01 (no GUI means faster boot, more free space, etc) Sep 27 17:28:38 just saw the new messages, just rebooting rn Sep 27 17:29:24 I'm heading home, will be back online later Sep 27 17:29:44 maybe I can add you on hangouts? Sep 27 17:29:58 no thanks, I prefer IRC Sep 27 17:30:02 okay Sep 27 17:30:08 afk Sep 27 17:30:15 thanks for your help so far Sep 27 17:57:28 np Sep 27 18:06:42 hi how do i upgrade only a single package like openssl? i don't want to use apt-get upgrade since it will (may) upgrade other packages Sep 27 18:07:27 apt install PKG Sep 27 18:07:50 though "openssl" is split up between several packages, depending on what parts you want Sep 27 18:08:24 such as openssl and libssl* Sep 27 18:09:27 vagrantc: not apt-get install? Sep 27 18:09:46 if you must, you could use apt-get Sep 27 18:10:07 unless you're on a very old version, then "apt install" wouldn't work. Sep 27 18:10:53 upgrading to 1.1.0, i was hoping for 1.0.2 to match ubuntu Sep 27 18:12:36 vagrantc how do i revert to 1.0.2? Sep 27 18:13:25 that's an adventure Sep 27 18:15:17 Hi all! Sep 27 18:15:31 vagrantc: now i have 1.1.0 but i need 1.0.2 Sep 27 18:17:07 apt-get install libssl1.0.2 Sep 27 18:17:39 Can anyone help me on how to get started with beagleboard as i want to contribute Sep 27 18:18:06 zarzar2: debian has separate packages for libssl1.1 and libssl1.0.2 Sep 27 18:18:23 zarzar2: likewise there's libssl1.0-dev if you need the headers Sep 27 18:18:46 but not the openssl package Sep 27 18:18:53 depends on what you really need Sep 27 18:19:01 zmatt: i upgraded to openssl 1.1.0, not sure how to go back Sep 27 18:19:06 oh well Sep 27 18:19:38 vagrantc: I can't think of any reason why you'd want to downgrade that Sep 27 18:19:49 * vagrantc can't either Sep 27 18:20:01 the only reason to specifically want 1.0.2 is because libssl1.1 isn't backwards compatible Sep 27 18:20:36 (which is exactly why libssl1.0.2 has been packaged separately) Sep 27 18:21:01 i just want by BBB to match my dev ubuntu machine\ Sep 27 18:21:11 ubuntu is still at 1.0.2 Sep 27 18:21:51 might be easier to find a newer version for ubuntu Sep 27 18:22:00 no newer version available Sep 27 18:22:13 for ubuntu Sep 27 18:22:16 zarzar2: apt-get install libssl1.0-dev Sep 27 18:22:18 surely, they're not behind debian Sep 27 18:22:24 will replace libssl-dev Sep 27 18:22:38 they are behind debian Sep 27 18:22:46 as for libssl itself, the two library versions happily coexist Sep 27 18:23:23 wow, ubuntu must be making a lot of effort to keep openssl at an older version... Sep 27 18:23:26 what are the things that i should learn as prerequisites for contributing to this org? Sep 27 18:23:28 vagrantc: he seems to be right: https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=libssl-dev Sep 27 18:24:19 zmatt: yes, i checked too Sep 27 18:24:28 Anirban: your questions are too vague to give meaningful answers Sep 27 18:24:48 Anirban: really depends on what you want to do Sep 27 20:11:39 hi there channel :-) Sep 27 20:11:55 hi there zmatt Sep 27 20:12:21 zmatt, got rev.C BBB Sep 27 20:12:54 lighttpd like a webserver Sep 27 20:16:37 good afternoon Sep 27 20:17:14 I cannot find in the docs what is the root default password on the image bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img Sep 27 20:17:35 I flashed it on a microSD and I loaded it, but I can login only as debian:temppwd Sep 27 20:17:38 how do I configure lighttpd Sep 27 20:18:01 default passwd - "temppwd" Sep 27 20:18:47 charlls, you want to change passwd? Sep 27 20:20:07 charlls, desktop environment or just console? Sep 27 20:36:01 webserver BBB http://83.213.20.85/ but how do I configure like this one, a list http://hypem.com/download/ Sep 27 20:55:44 zmatt, are you there? Sep 27 21:06:31 good afternoon Sep 27 21:07:08 ok, I'm booting my BBB from bone-debian-9.1 and this is my dmesg log: https://pastebin.com/VB1XVptT Sep 27 21:07:43 when I do this: root@beaglebone:~# export SLOTS=/sys/devices/bone_capemgr.9/slots root@beaglebone:~# cat $SLOTS cat: /sys/devices/bone_capemgr.9/slots: No such file or directory Sep 27 21:08:41 there seems to be a slots object somewhere different, but it does not show the eMMC or HDMI virtual capes: Sep 27 21:08:42 # cat /sys/devices/platform/bone_capemgr/slots 0: PF---- -1 1: PF---- -1 2: PF---- -1 3: PF---- -1 Sep 27 23:03:50 is PRU usable at this point? Sep 27 23:08:12 a lot of pages i'm reading about it say tools are still in development Sep 28 02:00:15 Hello - how can the beagle X15 be booted from an external USB hard drive running debian 9? Sep 28 02:14:02 Just watched the makerfair "live" video Sep 28 02:14:20 about the PocketBeagle Sep 28 02:14:24 A few comments: Sep 28 02:14:51 First of all, the presentation looked very interesting, but there is very little info a the beagleboard.org main site **** ENDING LOGGING AT Thu Sep 28 03:00:01 2017