**** BEGIN LOGGING AT Fri Jun 03 02:59:58 2016 Jun 03 03:40:51 oldguy .. well shit .. method should be just the same for 2gb or 4gb Jun 03 03:47:35 he already left Jun 03 03:48:27 hence the 'well shit' .. but he can read the logs if he can really be bothered Jun 03 04:02:10 eyo Jun 03 04:02:19 hi Jun 03 04:02:39 hows it goin Jun 03 04:02:54 good thanks Jun 03 04:09:15 hey all, super noob question here. Having what appears to be a common problem: "UART.setup("UART1") RuntimeError: Unable to export UART channel." Jun 03 04:09:42 I've followed as much as I can, and I cant seem to fix the issue. Any thoughts? Jun 03 04:09:58 TheoM: language/board/etc ? Jun 03 04:10:17 python/BBBr3 Jun 03 04:12:11 err BBB rev C Jun 03 04:12:36 hmm not conversant in python here, I'm afraid Jun 03 04:12:53 it should be something fairly easy .. do you have permissions on the uart device? Jun 03 04:13:22 oh you're using the adafruit library? Jun 03 04:13:44 yep, using the Adafruit lib Jun 03 04:14:02 not sure about the permissions on the UART device Jun 03 04:14:19 I'da thought their guides would cover that Jun 03 04:14:27 that Limor is quite good .. :D Jun 03 04:15:45 okay so it's a device tree issue i think Jun 03 04:15:57 the adafruit guides fail miserably (for me at least) since its written for linux 3.8, looks like 4.1.15 has a few file location changes Jun 03 04:16:40 i've had that problem before, using bonescript, but i just looked through the library and found the paths and then "find / -name *path*" and correct the library Jun 03 04:16:43 ayjay, seems reasonable, just not sure the next actual step. I bet its something ismple Jun 03 04:16:59 i can't be sure that'll work for you though Jun 03 04:18:11 do you smell what i'm stepping in? Jun 03 04:18:15 I'm not sure the adafruit lib has updated for kernels >3.8 yet .. Jun 03 04:18:33 veremit has a good point Jun 03 04:18:39 I do, just need to get lines up on the specifics Jun 03 04:18:42 oh.... Jun 03 04:18:56 well thats a good point Jun 03 04:19:21 but if you want to see if you can fix it yourself go ahead and dig through their library a little bit, sometimes its really not too hard like < 1 hr Jun 03 04:19:30 if they have a debug flag you can turn on, all the better Jun 03 04:19:54 because the specific error you're getting is vague Jun 03 04:20:12 it's good learnins Jun 03 04:20:39 okay, I can hunt around in there library Jun 03 04:20:51 I'll try that first for a bit Jun 03 04:20:57 seems worth it Jun 03 04:21:54 might be worth a mail to support@adafruit to entice them to fix it Jun 03 04:21:57 its a bit long overdue Jun 03 04:23:09 Will do Jun 03 04:24:06 I want them to source a 1.2" versin of their 0.56" blue 4-digit 7-seg display in blue with backpack.. they do all the other colours .. ;( Jun 03 04:25:26 whats your project TheoM? Jun 03 04:26:26 Flight computer on a liquid rocket project. Jun 03 04:28:29 perfect for a bbb Jun 03 04:29:22 Yep, bunch of sensors, few I2C devices, telemetry. BBB seems like a perfect candidate. Jun 03 04:30:18 yeah the only issue is the steep learning curve that comes with these top of the line devices Jun 03 04:30:41 good for people who like to climb tho ;-) Jun 03 04:31:11 yep. I expected this. Jun 03 04:32:57 its probably the best 'tool' for the job out there though Jun 03 04:33:48 veremit: i just started looking at TIs higher end chips, wowww Jun 03 04:33:59 ayjay: like? Jun 03 04:34:13 i think it's the 45?? series Jun 03 04:34:23 it's the one with dps's and pru's and >1Ghz and PCIe Jun 03 04:34:27 dsps* Jun 03 04:36:43 5k2ex actually Jun 03 04:36:45 i just looked it up Jun 03 04:37:36 ayjay: you've seen the BB-x15 ? Jun 03 04:39:12 meh i can't find the one i was looking at earlier Jun 03 04:39:30 i just googled it Jun 03 04:40:14 oh man i want that Jun 03 04:40:48 beware the price tag though for that bit of kit :) Jun 03 04:41:32 i would buy that instead of a new computer Jun 03 04:41:38 thanks duders for the help. Back at it in the AM. Jun 03 04:41:44 later Jun 03 04:42:00 where can i even find it? Jun 03 04:42:23 ayjay: pre-register .. they'll mail when it finally passes FCC/CE Jun 03 04:44:12 yeah i'm probably gonna preregister for it Jun 03 04:45:09 where can i even do that Jun 03 04:46:48 i'm getting way too excited reading this google groups thread Jun 03 04:47:34 honestly i find google groups intimidating. is it e-mail? is it not e-mail? i don't know Jun 03 04:48:41 man the semiconductor guys at TI must be top notch dumping out all this hardware, without the software support. Jun 03 04:50:38 ayjay: http://beagleboard.org/x15 Jun 03 04:50:48 oh yes :D Jun 03 04:54:05 howwww Jun 03 04:55:31 lol the seeed wifi bbg is unavailable outside he US .. seemst hey didn't bother with proper certification then .. :D Jun 03 04:58:43 okay i should go to bed Jun 03 04:58:50 jeez until tomorrow Jun 03 04:58:54 that x15 tho Jun 03 05:00:42 jeeez i looked at that evaluation module for that processor its 600 dollars! Jun 03 06:20:40 Greetings for the day! I am a newbie to IRC, so kindly excuse if my question is trivial. Jun 03 06:20:58 I want to ssh into my BBB from Ubuntu host Jun 03 06:21:06 I'm unable to do so Jun 03 06:21:38 nor am I able to access the webserver on BBB at 192.168.7.2 Jun 03 06:22:16 I tweaked the udev rules so as to match the idVendor and idProduct of the BBB Jun 03 06:22:19 is the board connected by USB? Jun 03 06:22:39 yes, it is connected via usb Jun 03 06:22:48 do the LEDs blink? Jun 03 06:23:07 yes, it does Jun 03 06:23:24 which software/OS is the board running? Jun 03 06:24:00 the board is running on Angstrom linux distribution Jun 03 06:24:21 in fact I am able to ssh into it from windows Jun 03 06:24:37 angstrom? oh dear, that's ancient Jun 03 06:24:52 why not reflash it to the current debian? Jun 03 06:25:19 thank you very much sir. I am ready to do that. Jun 03 06:27:20 strange .. I'da picked windows bein stupid over ubuntu .. but then it -is- ubuntu ... Jun 03 08:46:07 hey guys, past months ive been struggling with osx (el capitan) tethering to BBG and rebooting mac works but im soooo sick of that, is there !ANY! fixes, solution or something ? BBG oly has 1 freggin USB port which i need for BLE development. also screening is out of question since i need FTP access as well Jun 03 12:58:27 hello Jun 03 12:58:47 i can't start my beagle bone black anymore Jun 03 12:59:30 when i power it on, only the power LED is on, the others never get falsh Jun 03 13:01:51 Is there anybody who can give me some ideas Jun 03 13:03:34 have a look at the debug console Jun 03 13:33:53 hello Jun 03 13:35:16 i have installed the latest (debian wheezy) image. how can i disable hostapd at boot? i would like to use wlan0 to connect to an existing access point. Jun 03 13:35:58 read: https://debian-handbook.info/ Jun 03 13:36:09 feel free to /msg me to get my attention here in the channel Jun 03 13:36:58 KotH that handbook is for jessie not wheezy Jun 03 13:37:05 beagleboner: the latest image is Debian Jessie Jun 03 13:37:45 beagleboner: 1) what dirkk said, 2) it's not like everything has changed in jessie. it's linux not windows, after all Jun 03 13:37:51 ok thanks Jun 03 13:38:21 well things have changed quite a bit in the beaglebone images Jun 03 13:38:33 only superfically Jun 03 13:38:50 KotH: with the way _some_ people react to systemd "it's not like everything has changed in jessie" <- might be disputed by some ;) ps. not me Jun 03 13:39:02 perhaps, but this business of hostapd starting automatically is rather annoying Jun 03 13:39:30 zykotick9: well, only requires a simple config option for apt to get back to the old behaviour, and it's even documented in the release notes Jun 03 13:39:39 zykotick9: and yes, systemd is a fucking nuisance Jun 03 13:40:16 networking seems to have changed a fair bit. for example trusty old /etc/network/interfaces doesn't seem to work anymore :( Jun 03 13:40:36 that's because you run networkmanager Jun 03 13:40:39 dont Jun 03 13:40:40 just dont Jun 03 13:40:59 i didn't run anything like that. it is a (new) default i suppose Jun 03 13:42:08 i am trying to figure out connman, but i can't get it to do anything because wlan0 is being used by hostapd Jun 03 13:43:29 * beagleboner wants to connect wlan0 to an existing ap Jun 03 13:48:19 ok... in the debian-handbook there is a section on configuring the network which covers ethernet, but not wifi... where can i get info for that? Jun 03 13:49:25 there is something in the beaglebone image which starts up hostapd at boot. just trying to figure out how to disable it... Jun 03 14:07:05 beagleboner: sorry, no experience with connman. but you can of course try just "apt-get purge hostapd" Jun 03 14:07:09 (sudo) Jun 03 14:07:51 I personally use systemd-networkd as network manager, but that requires a more recent systemd than available in debian jessie (last time I checked at least) Jun 03 14:08:48 together with a simple wpa_supplicant config it works quite decently (on my laptop where I also use systemd-networkd, haven't tried it on a bbb but I see no reason it would work differently) Jun 03 14:10:07 zmatt i don't feel like tracking down a new version of systemd. it seems like i should be able to connect wlan0 to an existing ap without _too_ many headaches... Jun 03 14:11:33 well the first I do to any bbb is upgrade it to debian stretch Jun 03 14:11:40 which does include a recent enough systemd Jun 03 14:11:56 but you're right that presumably you can set it up with connman as well Jun 03 14:12:00 but I know absolutely nothing about connman Jun 03 14:12:09 so I can't give any useful advice there Jun 03 14:12:20 zmatt thanks anyhow Jun 03 14:13:08 it seems that although hostapd is disabled at boot, something is holding on to wlan0 and i am unable to configure it. Jun 03 14:13:23 how are you trying to configure it? Jun 03 14:14:30 normally wpa_supplicant manages the interface, and is either configured manually or configured dynamically by the network managed Jun 03 14:14:34 *manager Jun 03 14:14:44 i have tried several ways... my old habit was to edit /etc/network/interfaces, but that doesn't work... so then i tried editing wpa_supplicant.conf or something similar, but it did not work, presumably because hostapd was using wlan0... Jun 03 14:15:37 I'd first check connman's config, it seems to me it's most likely responsible for starting wpa_supplicant or hostapd Jun 03 14:16:27 purging the hostapd package would in any case prevent it from started Jun 03 14:16:59 hostapd did not start at the last boot, thanks for that.. Jun 03 14:17:13 if wpa_supplicant is started by connman rather than as a standalone service then it'll probably get its config from connman rather than from wpa_supplicant.conf Jun 03 14:17:30 * beagleboner opens man connman.conf Jun 03 14:18:09 I *think* connman has utilities to do configuration, but that's pretty much where my knowledge thereof dries up Jun 03 14:18:48 thanks zmatt you have been helpful Jun 03 14:29:37 argh, so that's why CDC-EEM doesn't work on osx... it's actually implemented in the driver, but disabled Jun 03 14:35:13 "connmanctl scan wifi" reteruns an error (No Carrier) Jun 03 14:36:47 "conmanctl services" shows no services Jun 03 14:37:02 (connmanctl services, that is) Jun 03 14:50:38 Hello Everyone, I am having a memory issue with my BBB. So when I execute the command df -h, for rootfs it is showing 3.4GB has been completely utilized Jun 03 14:50:58 Can someone please guide me with this. Jun 03 14:54:06 Aren't you the one who had a crash, and it was generally believed a log had consumed all the storage? That's what it seems like. If you can login and do df, you should be able to manage /var/log manually. Jun 03 14:54:24 du -hs /var/log Jun 03 14:55:11 yes I am the who had crash Jun 03 14:56:31 Rangrok and zmatt when I executed the command du -hs /var/log I got following output: 1.6G /var/log Jun 03 14:56:38 well there ya go Jun 03 14:56:43 Quick hack is locate a log file you can live without and "echo > thatLog" Jun 03 14:57:06 I'd still suggest using only the journal, and just "apt-get purge rsyslog" Jun 03 14:57:17 That'll free up space so you can figure out how to manage log size automatically. Jun 03 14:57:23 then in /etc/systemd/journald.conf configure limits Jun 03 14:58:15 I am not able to install anything since ethernet is not working at all on my BBB Jun 03 14:58:39 you don't need to install anything, it's already installed Jun 03 14:58:54 rsyslog is just duplicating the work of journald Jun 03 14:58:56 both are running Jun 03 14:59:29 I am getting error E: Write error - write (28: No space left on device) Jun 03 14:59:34 If you delete a log as described above the system may start working normally again. Then you can do whatever, including migrating to journald if you desire. Jun 03 14:59:37 but journald by default limits the max space used (by default to max 10% or 15% of the disk space iirc) Jun 03 14:59:45 rsyslog doesn't Jun 03 14:59:51 A__: then first delete some log files Jun 03 15:00:35 ls -lSh /var/log | head should list the biggest offenders first (unless the biggest offenders are in subdirectories of /var/log) Jun 03 15:01:27 I appreciate your help zmatt and Rangrok. Jun 03 15:01:34 total 1.6G -rw-rw-r-- 1 root utmp 744M Nov 12 16:41 wtmp.1 Jun 03 15:02:11 This is what I am getting on execution of command you mentioned zmatt Jun 03 15:02:16 hmm, that file keeps track of logins Jun 03 15:02:37 the .1 indicates it's a rotated file, so you can safely delete it anyway Jun 03 15:02:44 One is happy to be of service. You should have multiples of some logs, and some of those may have . or ..gz. Those are backups you might consider deleting. Jun 03 15:03:13 Well historical / rotated is more accurate than backup, but there it is. Jun 03 15:03:31 Where is other 1.4GB going? The total it shows is 1.6GB. Jun 03 15:04:31 I can't see your system but I expect it's a number of files all smaller than 744M. Four 400MB files will be 1.6GB. Jun 03 15:05:09 find /var/log -type f -exec ls -lSh {} \+ | head Jun 03 15:05:18 that will also cover files in subdirectories Jun 03 15:05:26 but as Ragnorok said, many smaller files can easily add up Jun 03 15:06:34 My /var/log has only two subdirectories and those generally are never the issue. It's nearly always syslog, kern.log, messages, or a some hisotory/rotation of them. Jun 03 15:07:25 the fact that wtmp is the culprit is indeed a bit odd, it suggest a very high rate of logins. possibly due to a periodic service that runs in a user login session (like cron) Jun 03 15:07:35 The history/rotation logs may simply be deleted. If for some reason you want to delete syslog for instance, then you should do the "echo > syslog". Jun 03 15:08:04 Okay I will do that Jun 03 15:08:13 bbl Jun 03 15:08:31 zmatt yes I do have cron jobs Jun 03 15:09:10 Can you guys please stay online while I try to fix this issue. I will need your help Jun 03 15:09:45 I will be back later, but I gotto go to the pharmacy which closes in 20 min Jun 03 15:10:07 I'll be here but I'm working. Cycles will be limited. Jun 03 15:10:28 okay. zmatt will it be possible for you to share your email ID? Jun 03 15:11:18 Rangrok I am having syslog.1.gz syslog.2.gz and so on in the log folder. Jun 03 15:11:20 I am not your personal assistant Jun 03 15:11:25 now afk, bbl Jun 03 15:11:48 Thank you zmatt Jun 03 15:11:57 sorry for that Jun 03 15:12:16 Unless you know you need any *..gz file, I would consider deleting them. Jun 03 15:12:43 Okay. Jun 03 15:13:33 What can be the possible reason for creation of those garbage files? Jun 03 15:13:39 If that frees up even a few dozen megs then you should be back in business, and able to figure out how to prevent this in the future. Jun 03 15:13:55 They are NOT garbage files. They are archived logs. Jun 03 15:16:02 Typically the system administratore configures it to retain a certain number of archives, then delete the rest automatically. Linux (nor Unix) assume what that configuration should be, so you have to do it. Jun 03 15:18:20 -rw-r----- 1 root adm 461M May 1 2016 daemon.log.1 Jun 03 15:18:30 -rw-r----- 1 root adm 110M May 2 2016 syslog.1 Jun 03 15:19:08 I am considering deleting these files Jun 03 15:19:41 Unless you know those archives have valuble information in them, you may delete them without issue. Jun 03 15:22:15 How can I check what is there inside these daemon.log file? Is there a way to access it? Jun 03 15:24:22 You must have enough free space to uncompress it. Jun 03 15:25:25 Thanks rangrok Jun 03 15:25:38 So my BBB did boot up normally now. Jun 03 15:26:00 Upon deleting one file that was consuming 400MB Jun 03 15:29:43 One is happy to be of service. Glad you got it working. Now you can research how to prevent this from happening again. Jun 03 15:41:18 Hello rangrok and zmatt sorry I got disconnected Jun 03 15:42:01 So my BBB did start to work but the ssh connection is not working for it. Jun 03 15:43:01 What does the console say? Jun 03 15:52:02 Hello Rabgrok, On terminal I am not getting any message. I tried to look for IP address for my BBB on my router settings but that does not show anything Jun 03 15:52:47 What's ifconfig -a say? Jun 03 15:53:28 It should have eth0 and some IP info, if Ethernet is working. I don't recall what USB shows up as. I don't have that enabled to check. Jun 03 15:53:46 Then there's dmesg. Did you check there? Jun 03 15:54:43 These suggestions, including the log bit, are all plain jane Unix/Linux issues. They should be easily discoverable. Jun 03 15:55:22 It is not showing eth0 Jun 03 15:55:52 I presume you are trying to use ssh on Ethernet. If you're doing USB then you have to find out how it appears. Jun 03 15:56:58 If you are using Ethernet and it's not there, then you need to troubleshoot that, which is dmesg and maybe journalctl to see boot messages. Jun 03 15:58:25 Poo. I do have USB still. Have to fix that. journalctl says it's usb0, so I expect that should appear. Ha. And it does. Jun 03 16:00:29 I am trying to SSH using Ethernet thats true Jun 03 16:12:42 Hello Rangrok Jun 03 16:13:06 my ethernet connection is not working at all Jun 03 16:14:11 I mentioned troubleshooting above, which is basically looking at boot logs to see why eth0 isn't working. Or you could look up how to manually start eth0 and see if it dumps anything useful. Jun 03 17:20:03 Help Jun 03 17:20:31 Hello Jun 03 18:05:11 hello Jun 03 18:05:37 hey boner Jun 03 18:05:43 hi ayjay Jun 03 18:06:15 Hi Jun 03 18:06:20 sup temp Jun 03 18:07:38 i am having trouble connecting my bbb to an existing wireless ap. the bbb was starting up with hostapd running. i got it to stop doing that, but it is still unable to negotiate an ipv4 address from the dhcp server on the existing ap. Jun 03 18:08:23 When I am doing ifconfig, on my BBB it shows eth0, lo, and usb0, but the eth0 it is not allocating any ip address. The BBB is connected to router via ethernet. Jun 03 18:08:46 temp try running dhclient eth0 Jun 03 18:09:24 Okay I did that. Jun 03 18:09:36 okay... so what happened? Jun 03 18:09:41 Now I need to restart? Jun 03 18:10:16 should not need to restart. was there any output from that command? have you re-run ifconfig? Jun 03 18:10:21 Thanks beagleboner it did work. Jun 03 18:10:30 temp yw Jun 03 18:10:31 Thanks beagleboner it did work. Jun 03 18:10:47 May I know what does that command exactly do? Jun 03 18:10:56 temp try man dhclient Jun 03 18:11:12 it will explain better than i can Jun 03 18:11:38 Thanks a lot. Jun 03 18:11:44 yw Jun 03 18:12:57 so beagleboner i've never used wan with bbb Jun 03 18:13:36 i think you mean wlan Jun 03 18:16:32 thats a fact Jun 03 18:18:02 I had one more question for you guys, when I am restarting my system again the ethernet connection is not working Jun 03 18:18:12 I had one more question for you guys, when I am restarting my system again the ethernet connection is not working Jun 03 18:18:24 temp: how were you enabling it? Jun 03 18:18:35 dhclient eth0 Jun 03 18:19:06 you probably need to edit /etc/network/interfaces Jun 03 18:20:05 Afaik my BBB "just worked", in that I didn't have to do anything for it to operate when DHCP was available. Many BBB use "conman" which makes it ignore the normal /etc/network/interfaces configuration, but perhaps dhclient brining it up contra-indicates that. Jun 03 18:21:52 Ragnorok you may have done something else which wrote to /etc/network/interfaces Jun 03 18:22:16 Nope. I've edited that extensively attempting to change the settings, all ignored. Jun 03 18:22:55 I will try rebooting again to see if it solves the issue Jun 03 18:23:22 If it is running conman one must apt-get remove conman (or so) to make it work "like normal". I don't know how common that is though. Jun 03 18:25:37 conman is not there in my system Jun 03 18:26:38 \o/ My xp is it's more hassle than it's worth. Jun 03 18:26:52 connman Jun 03 18:27:08 D'oh. Jun 03 18:27:44 note that even with connman, ethernet *should* afaik "just work" Jun 03 18:28:06 indeed Jun 03 18:28:10 Oh it does. It's just a PITA to alter its configuration, imo. Jun 03 18:28:40 dhcp?! Jun 03 18:28:48 or fix it .. how hard is that!? lol Jun 03 18:29:14 if you use ifupdown instead, with eth0 enabled to use dhcp, it has a rather large annoyance that if ethernet isn't plugged in then boot takes ages for it to timeout Jun 03 18:29:44 What you think I should do now to make sure ethernet works every time I reboot my system? Jun 03 18:29:52 Since /etc/network/interfaces is ignored when connman is in play, it's not just teletubbie simple. We only need static IP. Jun 03 18:29:59 zmatt: still not found a solution to that? .. usually its a limitation of the dhcp client .. you -can- detect whether there's a carrier normally .. Jun 03 18:30:21 veremit: I've been using systemd-networkd for a very long time now and it works beautifully Jun 03 18:30:33 We know how to do it now, but it wasn't just edit one file and be done. It was counter-intuitive. Jun 03 18:30:46 ah ofc yes.. why wouldn't you... Jun 03 18:30:55 Ragnorok: typical :) Jun 03 18:31:13 on the few jessie systems I've had to deal with I just added stretch as a low-priority repository to be able to upgrade systemd to a not-ancient version Jun 03 18:31:29 Not in my Linux xp. Too much automagic creeping in, all windows-like. Vexing it is. Jun 03 18:31:55 What should I do ? I do not want to run the dhclient etho command everytime I reboot Jun 03 18:33:20 temp: I don't know connman so I can't give advice on that. if you know for sure ethernet is always plugged in then ifupdown (which uses the configuration in /etc/network/interfaces) should do the job okayish. I just mentioned what my preferred solution is Jun 03 18:35:01 systemd-networkd does also work in jessie, but (unless it's been updated) it's a rather early version which doesn't even have 'networkctl' to check the status of interfaces Jun 03 18:35:27 Ragnorok++ Jun 03 18:39:58 http://pastebin.com/iUQnFhip <-- how you configure eth0 for dhcp when using systemd-networkd Jun 03 18:40:35 lol Jun 03 18:40:41 * beagleboner is somewhat frustrated with systemd networking and considers installing devuan Jun 03 18:41:23 beagleboner: I thought you were still using connman rather than systemd-networkd ? Jun 03 18:41:58 no standard debian image currently uses systemd-networkd out of the box afaik Jun 03 18:42:20 not using systemd-networkd. connman isn't working. the tried and true /etc/network/interfaces seems to be ignored on systemd Jun 03 18:42:35 * beagleboner misses the ease of /etc/network/interfaces Jun 03 18:42:43 This systemd thing looks distrubingly like svhost - one process to rule them all. Again far too windows-like. Jun 03 18:43:17 beagleboner: systemd has nothing to do with that, /etc/network/interfaces is the config file of ifupdown, hence used if and only if that's your network manager Jun 03 18:43:38 ifupdown isn't working either Jun 03 18:43:52 which is because your network manager is connman, not ifupdown Jun 03 18:44:08 i have tried both connman and ifupdown Jun 03 18:44:29 both exist on the beaglebone image Jun 03 18:44:43 You could nuke connman and ifupdown will work again, as will /etc/network/interfaces, and the easy days of yore. Jun 03 18:44:50 I know ifupdown works, although it kind of sucks Jun 03 18:45:03 Depends on use case. Jun 03 18:45:11 Ragnorok: so what apt-get --purge remove connman? Jun 03 18:45:27 Ragnorok: true for some cases it's adequate Jun 03 18:45:31 I don't know about --purge, but the rest looks like what I recall. Jun 03 18:45:37 Ragnorok: though I'd still prefer systemd-networkd Jun 03 18:45:41 and yes I'd recommend purge Jun 03 18:45:41 Not just adequate. Desirable. Jun 03 18:45:55 --purge removes config files, etc. Jun 03 18:45:57 Hi Jun 03 18:46:12 hey mrtamburino play a song for me Jun 03 18:46:19 someone can help me on issue on PWM configuration? Jun 03 18:46:19 Ragnorok: well, I used ifupdown before systemd-networkd and consider switching to be a significant improvement Jun 03 18:46:31 For simple static IP? Jun 03 18:47:10 beagleboner: i just want to say. i started with the "base" beagle image, from the sd card, installed what i wanted (and am using /etc/network/interfaces for my networking) - then flashed it. i found using debian pretty f'n amazing on the bbb. ymmv... Jun 03 18:47:11 Ragnorok: static IP is rarely desirable, but just as easy under systemd-networkd Jun 03 18:47:39 zykotick9: which base image? Jun 03 18:48:26 debian has been great for me on many machines. however, this is my first experience with a system running systemd Jun 03 18:49:11 * beagleboner is not enchanted Jun 03 18:49:21 I use debian with kernel 4 Jun 03 18:49:28 zmatt: In my case static IP is the only option for deployment, and I don't have to learn some new "let's put it all under one process" thing to use interfaces. (shrug) Seriously not a fan that. Jun 03 18:49:50 I load the tree BB-PWM0, but the pin mode do not change Jun 03 18:53:49 after load the tree if I list the pin mux i see the p9_22 with mod 7 and not 3 Jun 03 18:54:45 beagleboner: i'm sorry. i'm no longer clear which image i used? initially i installed one of the default ones, and trim it down. until i found this almost netinst base like image? but now i don't know where i got it from - or what it was called ?!?!? https://debian.beagleboard.org/images/ Jun 03 18:55:54 I use this OS: Linux beaglebone 4.1.22-ti-r59 #1 SMP Sat Apr 23 09:38:21 UTC 2016 armv7l GNU/Linux Jun 03 18:56:30 Ragnorok: well it may still save on boot time, and it integrates better with other services. e.g. if you run avahi it'll know to automatically start reregistering stuff when you plug in ethernet Jun 03 18:56:32 oh, i had the file still. bone-debian-8.4-console-armhf-2016-04-03-2gb.img Jun 03 18:56:35 Ragnorok: http://pastebin.com/6LDGwJDW some examples btw Jun 03 18:57:29 ok, I try to load the device tree BB-PWM0 usling: echo BB.PWM0 > slots Jun 03 18:57:46 Ragnorok: we tend to lug around beaglebones often enough so good behaviour in the face of hotplugging and such is something I do consider valuable Jun 03 18:57:53 it work, i can see the tree with the command: cat slots Jun 03 18:58:26 Ragnorok: I can appreciate the "I'm used to this, hence I prefer to keep doing it this way" Jun 03 18:58:44 bur i f I list the pins: cat pins | grep 950 , to see the configuraion of the pin p9_22 I see that the mode is 7 not 3 Jun 03 18:58:50 Ragnorok: but I've noticed that boot services consisting of shell scripts tend to eat up a lot of startup time for some reason Jun 03 18:59:04 and the pwm not work Jun 03 18:59:05 so the systemd way actually turned out to be quite an improvement Jun 03 18:59:54 and networkd is not harder to configure than ifupdown I think Jun 03 18:59:54 the outpput of the command config-pin -q p9_22: P9_22 Mode: default Direction: in Value: 1 Jun 03 19:01:50 in dts i can see this line :0x150 0x03 /* (A17) spi0_sclk.ehrpwm0A */ Jun 03 19:02:28 mrtamburino: btw, a simpler/nicer way to dump pin config: http://gerbil.xs4all.nl/show-pins-v3.pl.tgz Jun 03 19:02:56 the problem is probably that you have cape_universal enabled in /boot/uEnv.txt Jun 03 19:03:06 which conflicts with pretty much all pins Jun 03 19:03:29 (note that 'config-pin' depends on cape_universal though afaik) Jun 03 19:03:44 *which conflicts with pretty much all overlays Jun 03 19:03:46 sorry Jun 03 19:04:42 yes, I the cap universaln loaded Jun 03 19:04:53 but because it is a problem? Jun 03 19:05:04 if I remove it the PWM work fine Jun 03 19:05:22 zmatt: That is a rationale for investigating it. I'll add it to the pile along with journald. (grin) Jun 03 19:05:36 my tree doesn't overlay the universal? Jun 03 19:05:54 mrtamburino: check also your kernel log (type "dmesg") Jun 03 19:06:11 cape-universal claims basically all pins Jun 03 19:06:12 apt-get removed connman. edited /etc/network/interfaces. rebooted. wlan0 came right up. conclusion: connman is the suxor Jun 03 19:06:39 beagleboner: that's also why I never really bothered learning it Jun 03 19:06:45 thanks to everyone who helped point me in the right direction. Jun 03 19:06:50 [ 179.012582] bone_capemgr bone_capemgr: slot #5: dtbo 'BB-PWM0-00A0.dtbo' loaded; overlay id #1 Jun 03 19:06:58 "oh it seems to have a problem" .. *uninstall connman* "oh, problem solved" Jun 03 19:07:22 zmatt: i had no desire to learn anything about it, but the "official" beaglebone black image for jessie has it by default. Jun 03 19:07:25 it is loaded, but doean't work with universaln cape Jun 03 19:07:39 mrtamburino: no errors/warnings about pinmux conflict? that's odd Jun 03 19:07:52 one minute.... Jun 03 19:08:42 yes ther eare errors inside dmesg Jun 03 19:08:48 for example: [ 178.869174] pinctrl-single 44e10800.pinmux: pin 44e10950.0 already requested by ocp:P9_22_pinmux; cannot claim for ocp:helper Jun 03 19:09:24 that actually sounds like cape-universal lost there Jun 03 19:09:38 or maybe not, not sure Jun 03 19:10:10 but "helper" sounds like the pinmux helper from cape-universal Jun 03 19:10:53 there is also this message: [ 178.881320] pinctrl-single 44e10800.pinmux: pin-84 (ocp:helper) status -22 Jun 03 19:11:16 in general, cape-universal conflicts with almost anything Jun 03 19:11:40 so I should to remove it? Jun 03 19:11:50 I'd personally recommend disabling it yes Jun 03 19:12:40 ok, with the command echo -4 > slots, rigth? Jun 03 19:12:57 I tried and in this way the pwm work Jun 03 19:13:18 after if I reload the unuversal the beagle freeze Jun 03 19:13:28 I strongly suggest disabling it in /boot/uEnv.txt (look for the cmdline option) and rebooting Jun 03 19:13:39 the kernel often reacts very badly to removing overlays Jun 03 19:13:39 ok Jun 03 19:14:01 either causing a kernel panic right away, or when you later try to apply a different overlay Jun 03 19:15:48 ah Jun 03 19:17:38 I try you suggest: update uEnv and reboot, than i load BB-PWM0 and now the pin is configurate correctly Jun 03 19:17:54 thaks for your help Jun 03 19:18:46 but in case of two overlay try to configurethe same pin, the first overay work and the other fail? Jun 03 19:20:51 normally yes Jun 03 19:21:42 I've been working on better tools for working with device trees and overlays that would catch should problems early on, but got too many things going on at once so progress has been slow Jun 03 19:22:15 thanks Jun 03 19:22:21 (I'm considering dumping python and rewriting it in perl to regain some productivity) Jun 03 19:22:32 now I know more about the cape on beagle Jun 03 19:22:49 you mean overlay Jun 03 19:23:02 yes overlay Jun 03 19:25:08 it is a very useful tools Jun 03 19:26:05 I'm a newbe, but if you can think that i can help you cantact me Jun 03 19:26:56 beagle the world Jun 03 19:33:21 mrtamburino: note that there's also a newer way to apply overlays that doesn't use capemgr but configfs. I've also created some tools that make its use easier -> http://pastebin.com/QVJZK2Er Jun 03 19:33:48 if you inspect the pwm1.dtsi you'll also see it's much more readable than the source code of an overlay usually is Jun 03 19:33:59 +1 for zmatt's py-uio Jun 03 19:34:11 not actually using py-uio in this example though ;) Jun 03 19:34:19 +1 for overlays tools too Jun 03 19:34:36 I should probably split the overlay tools off to a separate project or so Jun 03 19:35:54 ok thank, I check your tools Jun 03 19:36:45 the project is like at it's embryo stage Jun 03 19:36:59 itll differentiate further in development Jun 03 19:37:02 yes I see the source of the PWM0 and 1 and it is clear Jun 03 19:37:52 mrtamburino: note: the dtsi files included with the project should probaly be ignored unless you intend to use uio Jun 03 19:38:12 the pwm1.dtsi file I downloaded separately in my example however uses the normal kernel driver Jun 03 19:38:46 there's also an spi1.dtsi in the same location Jun 03 19:40:09 you use /bin/add-overlay instead of slots Jun 03 19:40:46 not /bin/, bin/ Jun 03 19:41:07 they're utilities included with my project to make it easier to use configfs for overlays Jun 03 19:42:17 yes right Jun 03 19:57:49 thanks to all and good nigth Jun 03 21:03:24 elho Jun 03 22:43:04 helo Jun 03 23:08:00 http://www.catb.org/esr/faqs/smart-questions.html Jun 03 23:12:22 jkridner: that irc survival guide has gone MIA .. might be an idea to remove from the /chat page .. :) **** ENDING LOGGING AT Sat Jun 04 02:59:58 2016