**** BEGIN LOGGING AT Tue Dec 30 02:59:58 2014 Dec 30 03:58:26 the ADC truely blows Dec 30 04:03:48 roughly 8 bits of useable resolution :( Dec 30 04:11:17 you can make up for poor resolution with a fast sample rate and filtering Dec 30 04:17:48 ds2, what does it blow Dec 30 04:50:23 emeb: this is after averaging 8 samples Dec 30 04:50:45 no more sample rate overhead available to reduce noise Dec 30 04:52:15 Hmmmm Dec 30 04:52:21 something odd is going on Dec 30 05:00:13 whoa... wonder if this is a hw bug Dec 30 05:11:29 gained 1.5bits Dec 30 05:44:53 shave and a hair Dec 30 05:45:00 1.5 bits! Dec 30 06:17:27 +1 Dec 30 06:31:12 got about 10 bits of useful range...up from 6.5-7 Dec 30 06:59:28 hi, last night I have installed 3.19 and now I trying to find the /sys/devices/bone_capemgr.9/slots Dec 30 07:00:06 in order to load my settings, but this device, bone_capmgr is missing Dec 30 07:00:08 find / -name "bone_capemgr.*" Dec 30 07:00:37 nope, gone Dec 30 07:00:51 Linux beaglebone 3.19.0-rc1-bone0 #1 Mon Dec 22 10:50:40 UTC 2014 armv7l GNU/Linux Dec 30 07:01:17 is it in apt someplace perhaps? Dec 30 07:01:57 the deb that rcn-ee offered and installed this kernel? Dec 30 07:03:04 your installing random .deb's? Dec 30 07:03:10 from random sources? Dec 30 07:03:34 apt-cache search Dec 30 07:04:23 I used https://rcn-ee.net/deb/wheezy-armhf/v3.19.0-rc1-bone0/ Dec 30 07:05:16 did you dl the .deb and install it or did you add the repo to your /etc/apt/sources.list or /etc/apt/sources.list.d/* Dec 30 07:05:38 I ran the update-kerenl.sh script Dec 30 07:05:53 it took the deb files from there and installed them Dec 30 07:06:19 why? Dec 30 07:06:33 when you update your kernel you need to rebuild your modules for it Dec 30 07:06:58 I think it includes that, cause the bbb booted fine Dec 30 07:08:25 doesnt mean its loading all the modules you want loaded Dec 30 07:08:52 which module is the gpio? Dec 30 07:09:00 why are you installing random .deb's out side of your package manager anyway? Dec 30 07:10:29 I assumed this included the gpio support Dec 30 07:10:43 assumption is the brother of all fsckups! Dec 30 07:11:58 hmmmm, my bbb appears to have fallen off my network:| Dec 30 07:12:26 j0rd: what kernel? Dec 30 07:12:59 will eyeball it now. just rebooted it and it came bk. havnt been eyeballing my network for the last few days Dec 30 07:13:50 which gpio module is running on your bbb j0rd? Dec 30 07:13:56 lsmod|grep gpio Dec 30 07:14:47 sec, need to remember my password / username Dec 30 07:16:06 wut r the default credentials for debian on the bbb? Dec 30 07:16:38 root nopassword Dec 30 07:17:41 hmmm Dec 30 07:18:54 fsck Dec 30 07:19:16 fror whatever reason i appear to have forgotten what i changed the password to Dec 30 07:22:55 weird, the debian/debian acct isnt letting me in either Dec 30 07:23:21 meh, i'll relash it later Dec 30 07:30:36 cityLights: ive not got any gpio module loaded Dec 30 07:31:24 cityLights: this might be of use: Dec 30 07:31:26 debian@beaglebone:~$ apt-cache search gpio Dec 30 07:31:28 ledmon - Enclosure LED Utilities Dec 30 08:48:25 av500: have you got an idea why I can't find the slots file to load my device tree overlay in 3.19 Dec 30 08:48:26 ? Dec 30 08:51:01 because capemanager as you know it doesn't exist there? Dec 30 08:54:05 morning tbr Dec 30 08:55:07 I don't see /sys/devices/bone_capemgr.*/slots Dec 30 08:55:48 is this a special module ? Dec 30 08:58:37 > because capemanager as you know it doesn't exist there? Dec 30 08:59:30 yes tbr, did this change 3.8->3.19? Dec 30 09:02:00 yes, it did Dec 30 09:02:50 http://elinux.org/Capemgr didn''t reflect the change, when can I read on the change? Dec 30 09:03:11 I want to load my overlay to pullup gpio48 Dec 30 09:06:02 is it https://github.com/RobertCNelson/rscm ? I think I found it, it changed in 3.13 Dec 30 09:34:36 tbr ok I tried to run the build.sh in the rscm as described in https://github.com/RobertCNelson/rscm/README.md Dec 30 09:34:54 how ever the boot files paths have changed: Dec 30 09:35:23 script is looking for /boot/uboot/dtbs/am335x-bone.dtb Dec 30 09:35:34 and its now: /boot/dtbs/3.19.0-rc1-bone0/am335x-bone.dtb Dec 30 09:35:55 is there an upgraded script, or should I fix it for myself? Dec 30 09:37:08 looks like an easy fix Dec 30 09:37:19 submit a pull request once your done ;) Dec 30 09:38:28 yes, will also ask to add a note in the kerenel wiki to direct to this Dec 30 10:47:44 for the beagleboard xm should i set my VIDEO_CARDS="fbdev" or to omapfb? Dec 30 10:53:34 cant try both and see which works? Dec 30 11:05:02 not yet lol Dec 30 11:05:13 and which ever one i chose will determine what is built Dec 30 11:05:17 gentoo Dec 30 11:05:47 but i know the fbdev will work but wont have accel Dec 30 11:06:18 i read somewhere that the drivers for the accel were built using softfp so would not work in a hardfp system Dec 30 11:06:20 different abi Dec 30 11:38:06 on a beagleboard Xm what is my tty because ttyS0 and ttyS1 and ttyS2 dont work Dec 30 11:40:04 probably ttyOx unless you have a really ancient kernel Dec 30 11:40:49 i tried tty01 too Dec 30 11:41:10 i MAY have an older kernel Dec 30 11:41:29 the only kernel i could get to work was the one that came on the angstrom test cf card Dec 30 11:42:45 S:2345:respawn:/sbin/getty 115200 ttyS2 Dec 30 11:42:55 thats what is on p2 of the test flash in its inittab Dec 30 11:43:02 but i tried that and it doesnt work for me Dec 30 11:43:55 i get "is not a character device" error Dec 30 11:46:05 yup, ttys2 does not work. i have a --noclear on thatline and the screen clears at boot Dec 30 11:46:09 FUCKING annoying Dec 30 11:46:32 how the hell is anyone supposed to debug their boot like that Dec 30 11:47:22 i cant get netowork working. i cant get the console working Dec 30 11:47:23 .redraw Dec 30 11:48:52 i have to insert the test flas. hit reset. wait to boot. discover what IP address it got. ssh in. chroot to my gentoo. edit the inittabl. insert the gentoo boot flash (makes it boot off sda2 as root not mmcblk0p2) Dec 30 11:48:57 FAIL. start over Dec 30 11:49:29 i need to know what tty this boot is using. how do i find out Dec 30 11:49:38 because its not tty01 Dec 30 11:52:22 does it matter where in the agetty line i put the --noclear Dec 30 11:55:45 i need help Dec 30 11:56:00 i need to find out what tty this stupid freeking thing is using at boot Dec 30 11:56:04 so i can freeking LOG IN Dec 30 11:56:11 and stop the damned thing from clearning Dec 30 11:56:21 what TTY does a beagleboard XM use Dec 30 12:07:14 can someone please help me Dec 30 12:07:38 ive tried ttys0,s1,s2 00,01,02 and NONE of themn work Dec 30 12:07:52 when i boot i get stuff on the display but no keyboard interaction Dec 30 12:08:07 after a minute i get a s0 respawning too fast message Dec 30 12:08:11 but ttys0 does NOT work Dec 30 12:15:04 its not tty1 either Dec 30 12:19:49 anyone? Dec 30 13:16:29 how can i find the tty that i should use with minicom for my gps on my beaglebone black Dec 30 13:27:24 andreas: you'll need to make sure the pins you are connecting it to are MUXed correctly and the reference voltage matches Dec 30 13:39:18 how can i mux the pins i use? and what if i dont know what pins i am using Dec 30 13:39:59 then start by finding out Dec 30 13:40:03 read the SRM Dec 30 13:40:51 the srm of beaglebone black or gps? Dec 30 13:40:54 also the web search enginen of your least distrust should know about things like "beaglebone black uart" and keywords like "add" or "mux" Dec 30 13:41:25 is the GPS a cape or what is it? Dec 30 13:41:33 yes its a cape Dec 30 13:41:55 then I'd expect there to be documentation how to make it work Dec 30 14:03:40 hello, my gps shield uses the pins P9. 10,19,20,11,13,14 and P8.17. how can i mux them so i can use them\ Dec 30 14:03:44 ? Dec 30 14:05:36 andreas: Have you folowed any of thw advice tbr just gave you? Dec 30 14:07:03 yes i found the pins the gps is using Dec 30 14:07:40 the GPS cape should have documentation on how to make it work. have you searched for it? Dec 30 14:28:52 hello, trying to use minicom. i am supposed to use tty04. the dev diectory has only tty4. when i use tty4 i dont get any data from my gps Dec 30 14:29:25 YOu have not yet muxed the pins for ttyO4, so the device does not exist. Dec 30 14:29:38 Please try following all of tbr's advice. Dec 30 14:29:39 how do i mux the pins though? Dec 30 14:30:00 Google "beaglebone black mux uart5" Dec 30 14:30:01 trying for hours now Dec 30 14:33:29 you need a device tree overlay agmlego Dec 30 14:33:37 well, look into that Dec 30 14:34:18 you can specify the pins you want in a dts file, and then compile it into a dtbo with dtc Dec 30 14:34:54 look at Derek Molloy's blog and videos on YouTube (Google his blog site) Dec 30 14:36:27 tb__: I am aware Dec 30 14:37:32 then i don't understand why you are baffled about why it's not working Dec 30 14:38:08 does the GPS shield manufacturer offer a DTO for it? Dec 30 14:38:09 tb__: there are two nicks starting with a Dec 30 14:38:28 tb__: I am not confused, andreas is. Dec 30 14:38:38 oh, sorry! Dec 30 14:38:39 LOL Dec 30 14:38:44 my apolgies Dec 30 14:38:44 tb__: Or are you and tbr the same person... ;-P Dec 30 14:38:49 no, lol Dec 30 14:39:12 no Dec 30 14:39:40 andreas, the GPS shield maker must have a DTO available Dec 30 14:39:47 look in /lib/firmware Dec 30 14:39:58 if not there, check their website Dec 30 14:46:58 well, andreas must have gotten it to work? Dec 30 14:47:07 (or gave up) Dec 30 14:47:29 sorry again for the mistaken identity agmlego Dec 30 14:47:34 No worries. Dec 30 14:47:51 I know all 8-character nicks starting with the same letter look the same. ;-P Dec 30 14:48:07 (this is why I have a colorizer script installed, to help differentiate nicks) Dec 30 14:48:12 when they are mixed line-after-line, yeah...it runs together Dec 30 14:48:21 would be nice Dec 30 14:48:42 tb__: nickcolor.pl, if you use IRSSI. Dec 30 14:48:50 mhm, should look to get a decent irssi nick colour thing going too Dec 30 14:48:52 no, xchat here Dec 30 14:48:57 although I rarely find to need it Dec 30 14:49:05 tb__: Ah, then, get a real client, then use nickcolor.pl. ;-P Dec 30 14:49:20 there might be a config option in xchat though Dec 30 14:49:33 i think i've use irrsi once Dec 30 14:51:37 Yeah, x-chat is a tolerable client. Dec 30 14:52:06 woohoo...it does have colored nicks Dec 30 14:52:11 Yay! Dec 30 14:52:18 it even works! Dec 30 14:52:58 wouldn't you think (about andreas' GPS) the GPS maker would have a DTO for that thing? Dec 30 14:53:11 Not necessarily. Dec 30 14:53:29 But I would expect a user to be able to figure this out reasonably well from the wealth of information out there. Dec 30 14:53:31 if it's a commercial product, it would seem as though they would have gone to the trouble of making one Dec 30 14:53:42 Again, not necessarily. Dec 30 14:53:55 Hell, it might be a cape for a white version. Dec 30 14:53:56 worth a look-see anyway Dec 30 14:54:01 yeah Dec 30 14:54:02 Oh, sure. Dec 30 14:54:03 good point Dec 30 14:54:12 i have a BBW by the way Dec 30 14:54:13 love it Dec 30 14:54:24 Good to know. Dec 30 14:54:27 i just sent in two BBB units for RMA Dec 30 14:54:47 i've had the BBW for 18+ months, and it has seen countless circuits Dec 30 14:55:12 one BBB stopped working when just sitting there (no circuit attached) as an SSH host Dec 30 14:55:38 I use them equally, but the lack of software support on the white frustrates me. Dec 30 14:55:53 oh? Dec 30 14:55:55 interesting Dec 30 14:56:01 i hadn't considered that Dec 30 14:56:06 My hackerspace has a pretty good stack of each at the moment, so I try to use the white ones when I can in projects to use them up. Dec 30 14:56:23 hopefully they can fix my two BBB units, but I am not sure what's wrong--seems that there's a shorted IC Dec 30 14:56:28 Good morning all =) Dec 30 14:56:32 good morning Dec 30 14:56:33 tb__: As far as I can tell, no one is doing anything on the white anymore software-wise, so things like SPI are awkward at best. Dec 30 14:56:36 hey tb__ Dec 30 14:56:42 i see Dec 30 14:56:53 And certainly no DT there. Dec 30 14:57:03 yeah, i did have a problem using Derek Molloy's SPI examples with the BBW, as I recall Dec 30 14:57:15 Not surprising. Dec 30 14:57:25 but there was a DTO in /lib/firmware Dec 30 14:57:28 I would imagine they would just swap out the BBB and send you a new one. Dec 30 14:57:34 THe two devices are very different. Dec 30 14:57:37 we'll see i guess Dec 30 14:57:37 Considering the cost... that's better than "fixing it". Dec 30 14:57:40 My opinion... Dec 30 14:57:49 tb__: Oh? YOu must have gotten a 3.8 kernel on yours somehow. Dec 30 14:57:52 i would like to know what went wrong with them Dec 30 14:58:02 The one thing that would make the BBB for me killer would be the Raspberry Pi Camera Board... that would ROCK Dec 30 14:58:04 tb__: All of the ones at the space are still running 3.2 under Angstrom. Dec 30 14:58:11 i downloaded a Debian version with 3.8 kernel Dec 30 14:58:19 right Dec 30 14:58:26 the BBB has no CSI port Dec 30 14:58:31 so the rpi cam wont work Dec 30 14:58:32 av500, ahhh Dec 30 14:58:44 well, ... was just wondering that. Dec 30 14:58:51 $ uname -a Dec 30 14:58:51 Because that $30 rPi cam is amazing. Dec 30 14:58:51 Linux beaglebone 3.8.13-bone50 #1 SMP Tue May 13 13:24:52 UTC 2014 armv7l GNU/Linux Dec 30 14:58:52 also, the rpi has nothing to encode video Dec 30 14:59:09 so get yourself an usb cam that encodes by itself Dec 30 14:59:10 knob: If you want that, you want a beagleboard xm, which does have a camera interface. Dec 30 14:59:12 and done Dec 30 14:59:13 av500, I dunno about that. I pull a video, then feed the h264 into ffmpeg... and off I go Dec 30 14:59:18 wow, nick coloring is really helpful...lol Dec 30 14:59:21 agmlego, googling right now Dec 30 14:59:37 av500, any suggestions as to a usb cam that does encoding itself? Dec 30 14:59:38 usb cams deliver h264 already Dec 30 14:59:38 knob: And there are even camera modules for it. Dec 30 14:59:44 knob: a lot of them do Dec 30 14:59:50 agmlego, I googled... yet everything was kinda iffy Dec 30 14:59:51 google will know Dec 30 14:59:56 agmlego, how do you typically power your BBB units? Dec 30 15:00:01 knob: How do you mean, "iffy"? Dec 30 15:00:30 tb__: High-efficiency high-output DC-DC converters running off of space battery infrastructure. Dec 30 15:00:38 iffy in the sense that the rPi cam I can plug in the csi cable, and off I go. The googling I did for the BBB, they were shields and... odd things. Dec 30 15:00:44 wow Dec 30 15:00:46 tb__: I like the LM2576 line of switchers. Dec 30 15:00:55 interesting... Dec 30 15:01:08 knob: I did not say the beagle *bone*, I said the beagle *board xm*. Dec 30 15:01:13 knob: These are different. Dec 30 15:01:17 agmlego, I am looking at it now Dec 30 15:01:21 150$... Dec 30 15:01:38 Yet, one thing I want to say guys: I am super happy to be working with the BeagleBone.... it rocks./ Dec 30 15:01:42 time to go learn about logic analyzers Dec 30 15:01:50 talk to you guys later Dec 30 15:01:51 Just speaking up on some things I see from my side. Dec 30 15:01:54 later tb__ Dec 30 15:03:17 Judging now a good USB camera that streams h264 Dec 30 15:03:26 Anybody have experience with one they can recommend? Dec 30 15:05:34 I like the Logitech ones. Dec 30 15:05:53 But I cannot recommend any serious use of the USB on the bone. Dec 30 16:43:18 ok Dec 30 16:43:22 how come agmlego ? Dec 30 16:43:27 Slow chipset? Dec 30 16:46:03 knob: If you do any reading on the subject at all, you will know that USB on the bone is not reliable. Dec 30 16:46:44 agmlego, I have not done any reading on the subject, at all. Was just making conversation in quiet channel. Sometimes people chime in and contribute. Dec 30 16:46:49 Get the conversation going. Dec 30 16:49:41 anyone remember what the operating specs are regarding temperature? Dec 30 17:16:48 Anyone here ever run steam on a bbb? Dec 30 17:17:10 agmlego, do you have a source for your usb comment Dec 30 18:09:14 agmlego: links? everything i've read seems to indicate bone's USB is as good as any USB on linux. it's the rpi that has horrible, miserable USB Dec 30 18:09:33 in general though, the USB subsystem has fundamental flaws on linux. any linux. Dec 30 18:10:39 (some discussion: http://linuxaudio.org/mailarchive/lau/2010/9/17/173735 ) Dec 30 18:15:15 kenrestivo, py0: My source for the comment is several years' idling in this channel. It comes up regularly and frequently. Dec 30 18:19:34 kenrestivo: Afaik its just the generally the Linux driver for USB Hosts on ARM doesn't get as much attention as on intel, but as apposed to rpi the HW should be fine Dec 30 19:16:49 interesting Dec 30 20:27:33 rcn-ee is you here? last night I installed your 3.19 kerenl, but I couldn't find /sys/devices/bone_capemgr.*/slots Dec 30 20:28:36 I tried https://github.com/RobertCNelson/rscm and replaced my am5x*.dtb in the /boot Dec 30 20:28:46 but couldn't now boot Dec 30 20:43:54 I mean, that I found out that at 3.13 the device tree was changed, and that project was born Dec 30 20:44:42 so I fixed the script to use /boot/uboot ->/boot and compiled the dtb files, then installed them Dec 30 20:45:12 so I can restore the original files, but I still need a way to load my overlay Dec 30 21:17:17 oh ya I asked about how to use the device tree overlay , about 12hours ago, so anyone from the US that can help me, is welcome Dec 30 21:17:32 I just need a pointer to go and read up Dec 30 21:17:36 good night Dec 30 21:59:18 Hey rcn-ee, did you really put uEnv.txt on the eMMC? That makes modifying it on failure kinda hard :) Dec 30 21:59:39 Got someone in #u-boot that bricked their board updating it and is having a hell of a time loading the old kernel Dec 30 22:00:24 Tartarus, uEnv.txt is in the /boot/ location... in both microSD & eMMC cases.. (nothing special about the eMMC, other then really hard to access) Dec 30 22:01:46 Tartarus, it'll always default to 'microSD', there's a ton of "boot scripts" it looks for: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0#Boot_Partition_.28omap4.2B_.28am335x.29.29 Dec 30 22:03:56 Hi. I renamed zImage/initrd.img in /boot/uboot/ with _'s at the end of the filenames, and then added my own files there. Obviously a stupid thing to do, but how do I recover? Dec 30 22:04:15 I'm trying to get my debian system to boot (the one that the BBB came with) Dec 30 22:04:22 rcn-ee, fchmmr is the person I was talking about :) Dec 30 22:04:43 I want to boot /boot/uboot/zImage_ and /boot/uboot/initrd.img_ Dec 30 22:05:02 fchmmr, grab the small "console" microSD/standalone image (it's 175mb of space) http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-12-19 Dec 30 22:05:09 currently it is loading uEnv.txt which tries to boot the broken one that I put there Dec 30 22:05:27 hold down the boot button and boot with the microSD, then mount the boot partition from the eMMC and remove that modifcation.. Dec 30 22:05:41 herein lies the problem: I have no micro sd card.. Dec 30 22:05:53 I do however have an SD card (big one) and a USB card reader. will that work? Dec 30 22:07:34 i suppose you could wire it up, but you might cause more damage, can you borrow a microSD card? Dec 30 22:07:48 I'll see if I can find one Dec 30 22:08:19 it doesn't have to very big, the console/recovery image is about as small as a debian image can be.. Dec 30 22:10:45 ok, I asked someone, and got a micro sd card now Dec 30 22:10:48 2GB Dec 30 22:10:52 perfect.. Dec 30 22:11:11 do I just dd that recovery image to it? Dec 30 22:11:16 or just copy it to a fat filesystem? Dec 30 22:11:39 just dd it.. Dec 30 22:11:53 wget https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz Dec 30 22:11:53 md5sum: 88714867510610420c1594cbde13c6e6 Dec 30 22:11:55 well. "unxz *.img.xz" then dd the *.img file.. Dec 30 22:11:58 that one Dec 30 22:12:01 ? Dec 30 22:12:13 use the small recovery: https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/console/bone-debian-7.7-console-armhf-2014-12-19-2gb.img.xz Dec 30 22:12:22 ok, thanks Dec 30 22:12:26 unless you want to flash the latest "eMMC" snapshot.. Dec 30 22:12:49 miraculously the person I asked didn't need it, it was a "spare" Dec 30 22:12:52 The may 2014 release is pretty old, one of these weeks CircuitCo will switch over.. Dec 30 22:12:57 so he just said I could have it (the micro sd) Dec 30 22:13:05 nice Dec 30 22:13:42 and I have a microsd to sd adapter, so my card reader will work for the dd'ing Dec 30 22:14:09 correct.. and with the *.img it doesn't matter what os you use... linux/mac/win.. Dec 30 22:14:19 i use gnu/linux Dec 30 22:15:14 actually, this card reader has a microsd slot on it. I'll just use that Dec 30 22:16:16 dd to sdd or sdd1 ? Dec 30 22:16:28 (sdd is the micro sd) Dec 30 22:16:31 /dev/sdd Dec 30 22:16:43 (raw drive) Dec 30 22:17:09 ok Dec 30 22:17:46 sudo dd if=./bone-debian-7.7-console-armhf-2014-12-19-2gb.img of=/dev/sdd ;) Dec 30 22:17:49 dd'ing now Dec 30 22:18:02 no bs=8M or anything? Dec 30 22:18:14 not that it matters.... I'll also run "sync" afterwards Dec 30 22:18:32 it shouldn't matter... it only takes around 5-6 minutes.. Dec 30 22:19:34 g_dbgp Dec 30 22:19:45 I need that kernel module. That's why I tried building my own kernel Dec 30 22:20:07 the standard debian one didn't have it Dec 30 22:20:54 I might do it on the microsd instead Dec 30 22:20:58 and leave the emmc alone Dec 30 22:21:56 Do it on the microSD, kernel development is a "challenge" on the eMMC.. as it's not trivial to just swap the kernel out. Dec 30 22:22:11 yes, I learned that today. Dec 30 22:22:34 it's lucky I had a microsd, else I'd have had to order one (which would delay me by a few days) Dec 30 22:23:12 btw, the version your flashing to the microsd, supports installing the kernel via a *.deb: so you can just: sudo dpkg -i linux-image* ; sudo reboot Dec 30 22:23:27 OH Dec 30 22:23:30 oh* Dec 30 22:23:42 I can't just dpkg in the default debian on the emmc? Dec 30 22:23:59 I was thinking of trying to simple build the kernel module separately and add it the the stock kernel Dec 30 22:24:03 I fixed that around Mid August... ;) so it didnt' make the May 2014 release ;) Dec 30 22:25:12 to support that, there is only one patch for mainline (make deb-pkg) https://github.com/RobertCNelson/linux-dev/blob/master/patches/packaging/0002-deb-pkg-install-dtbs-in-linux-image-package.patch Dec 30 22:25:55 welll I'll just not use the emmc at all Dec 30 22:26:14 or re-flash it later. using an external microsd Makes Sense Dec 30 22:27:33 btw, once your happy with the microSD, you can transfer it to the eMMC, by enabling this boot option: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC (just reboot and the eMMC will be flashed) Dec 30 22:30:24 so been away a bit, any kernels that support device tree and accel graphics together yet? Dec 30 22:31:24 rcn-ee, thanks. Dec 30 22:31:33 I dd'd it to the microsd and put it in, it boots Dec 30 22:31:43 seems it actually boots microsd by default (if present) Dec 30 22:31:48 nyt, what graphics "acceleration" are you interested in? we have framebuffer and qt5's egl thing... Dec 30 22:32:15 fchmmr, that's so it's hard to brick it... It'll always try the microSD first... Dec 30 22:32:36 well, for X Dec 30 22:32:39 now how do I mount the emmc? Dec 30 22:32:42 that still rocking fb or is there any sgx support? Dec 30 22:32:57 I tried mounting /dev/mmcblk1p* but that didn't work Dec 30 22:33:00 fchmmr, mkdir disk ; sudo mount /dev/mmcblk1p1 disk Dec 30 22:33:07 sorry, false alarm. I made a typo Dec 30 22:33:37 actually it's p1 that has /boot Dec 30 22:33:39 nyt, framebuffer only (aka "full" screen X).. The qt5 thing is windowed... Dec 30 22:33:42 as you pointed out Dec 30 22:34:09 yes, microsd by default was a smart move. it's a good protection against idiots like me Dec 30 22:34:42 oh it was for the developers too... ;) Dec 30 22:35:21 I restored the old kernel/initrd on the emmc and now the emmc system boots again Dec 30 22:35:26 u-boot's doing a lot of things behind the scene to make sure it boots... Dec 30 22:35:32 uboot is awesome Dec 30 22:35:42 Yes, I know what you mean Dec 30 22:35:48 I run the libreboot project ;) Dec 30 22:36:10 very cool Dec 30 22:36:11 making things "fool proof". uboot is way harder to use than grub, though, as I learned today (libreboot uses GRUB bootloader) Dec 30 22:37:15 I'll try installing a new kernel again, until I get it right. the microsd card makes me feel safer now Dec 30 22:37:30 i think Tartarus is getting it closer... on mainline u-boot some newer targerts now init the hdmi screen and usb kinda works. The next step is probally tweaking u-boot from hdmi/usb. ;) Dec 30 22:37:51 I haven't actually used the video output yet. Dec 30 22:37:59 I probably won't ever need it. I bought the BBB for 2 things: Dec 30 22:38:12 * use as a SPI flasher (already setup on my other 2 BBB's, and working) Dec 30 22:38:25 * EHCI debug device (this is what I need to build a kernel for) Dec 30 22:38:51 I use SSH or FTDI serial and just do everything in cli Dec 30 22:39:20 http://www.coreboot.org/EHCI_Debug_Port#DIY_.2F_BeagleBone_Black Dec 30 22:42:11 humm interesting.. i never looked to far into the CONFIG_USB_G_DBGP, it looks useful, just reading the config label i though it was internal to the gadget subsystem for debugging... thus disabled.. Dec 30 22:42:33 I'll enable it as a module by default, sorry it doesn't help you "yesterday"... but it'll help the next user.. Dec 30 22:47:24 rcn-ee, that would be nice! Dec 30 22:47:40 could you ping me when/if a new debian image is released with this module included by default? Dec 30 22:47:49 I know a few other people who will benefit from this Dec 30 22:49:26 fchmmr, it's on my backport list: https://github.com/RobertCNelson/linux-dev/commit/c3ac3359f2a36f8340cf64d9f0172b7b84d7a1bc i have a few other tweaks from Charles on 3.8.x, i usally push out kernel builds at the end of the week (so this wednesday).. Dec 30 22:50:38 I see, so I could just dpkg -i the new kernel? Dec 30 22:50:53 when it get's pushed out, you can just grab the "2014-12-19" snapshot and then just: sudo apt-get update ; sudo apt-get install linux-image-3.8.13-bone69 ; sudo reboot Dec 30 22:58:00 rcn-ee, you might also want to look at enabling UMS support in U-Boot, so taht we could export the eMMC and whack it from another box Dec 30 22:58:16 That stuff works on odroid/etc Dec 30 23:02:10 Tartarus, I'll look into that... Haven't heard back from Jason/CircuitCo, so the massive update to the default May 2014 release still has room for updates.. (right now it's 2015.01-rc4) Dec 30 23:02:24 k Dec 30 23:02:25 otherwise it's so hard to push u-boot updates. ;) Dec 30 23:07:26 Tartarus, that looks pretty cool actually, and will help jason's goal of implementing something like "NOOBS" for bbb.. Dec 30 23:30:39 fchmmr: there's this xzcat utility Dec 30 23:32:40 idwer, how would that utility benefit me? Dec 30 23:41:17 pipe xzcat output to dd, so you don't have to extract *.xz first Dec 30 23:41:38 I hoped you could put 1+1 together yourself.. :) Dec 31 01:11:54 sup Dec 31 01:28:24 idwer, or I could just extract and then dd. simple. Dec 31 01:32:08 or pipe wget output to xzcat, xzcat output to dd Dec 31 01:32:13 saves disk space Dec 31 01:32:36 then have lunc or whatever Dec 31 01:32:38 lunch Dec 31 01:36:56 simple to follow, yes, but not easier per se Dec 31 01:38:38 * kl0wn tips fedora Dec 31 02:40:32 Wholly lag, batman. Dec 31 02:40:38 5.8s lag Dec 31 02:43:16 Is that how you spell "Wholly"? Dec 31 02:43:20 * tb__ did not know that Dec 31 02:43:39 Thought it was the "holy" variety **** ENDING LOGGING AT Wed Dec 31 02:59:58 2014