**** BEGIN LOGGING AT Wed Apr 22 02:59:58 2015
Apr 22 07:18:24 <BennyB_> good moning. is ther any way to get capemgr to print a more detailed output to dmesg?  I made a cape overlay and it failes to load....
Apr 22 07:19:11 <BennyB_> kernel 3.8.13 capemgr.9: loader: failed to load slot-9 ...
Apr 22 07:21:14 <BennyB_> this is my dmesg output filtered to the relevant lines: http://pastebin.com/1SyKXCkq
Apr 22 08:39:46 <BennyB_> noone has a hint how can I find out why my overlay failed to load?
Apr 22 08:42:48 <kinkazu_> hi all.
Apr 22 08:43:04 <kinkazu_> anybody has problems with ttyS4 when using kernel 4.0?
Apr 22 08:44:29 <BennyB_> other question: how can I disable the pins P9_17+18 to be i2c ?  I tried with my dtb-file which should configure them as input, but (as aleardy said) the overlay does not load
Apr 22 08:46:47 <kinkazu_> I dunno
Apr 22 08:47:07 <kinkazu_> i2c1?
Apr 22 08:47:28 <kinkazu_> which kernel
Apr 22 08:47:30 <BennyB_> yes, i need to disable I2c1
Apr 22 08:47:33 <BennyB_> 3.8.13
Apr 22 08:51:46 <kinkazu_> that is how i dsiable i2c2
Apr 22 08:51:47 <kinkazu_> http://pastebin.com/6hdwxFNb
Apr 22 08:51:52 <kinkazu_> disable
Apr 22 08:52:02 <kinkazu_> so you can try this with i2c1
Apr 22 08:58:34 <BennyB_> OK, I try
Apr 22 10:46:38 <BennyB_> seems not to work...
Apr 22 10:47:20 <BennyB_> the pins tay in mode 2... does someone know where i2c1 p9_17+18 is enabled?
Apr 22 16:19:48 <kinkazu_> hi there
Apr 22 16:20:08 <kinkazu_> anybody had problems with running ttyS4 on 4.0 kernel?
Apr 22 16:20:40 <kinkazu_> works fine with 3.8, doesn't communicate properly in 4.0
Apr 22 16:20:50 <rcn-ee> kinkazu, initially there was... uname -r ?
Apr 22 16:21:06 <kinkazu_> 4.0.0-bone0
Apr 22 16:21:40 <kinkazu_> i am almost sure i have got dtb compiled properly
Apr 22 16:21:59 <kinkazu_> S2 S0 are working ok
Apr 22 16:23:18 <rcn-ee> do you ahve anything else using p9.11/p9.13?
Apr 22 16:23:34 <kinkazu_> nope
Apr 22 16:24:43 <kinkazu_> only can0 and ttyS0 S1 S2 S4
Apr 22 16:24:45 <kinkazu_> enabled
Apr 22 16:25:04 <kinkazu_> all works apart from S4
Apr 22 16:25:56 <rcn-ee> i'll look into, i need to branch dtb-rebuilder for v4.0.x to today..
Apr 22 16:26:10 <kinkazu_> good
Apr 22 16:26:23 <kinkazu_> I was not sure if it is compatible with 3.19
Apr 22 16:26:34 <kinkazu_> so I dited am335x-boneblack.dtb manually
Apr 22 16:26:37 <kinkazu_> edited
Apr 22 16:27:22 <rcn-ee> it mostly is, couple 'new' dts options in v4.0.x..
Apr 22 16:27:36 <kinkazu_> one more question
Apr 22 16:27:42 <kinkazu_> dtb=am335x-boneblack.dtb i uEnv
Apr 22 16:27:45 <kinkazu_> in
Apr 22 16:28:17 <kinkazu_> I will chane it now to am335x-boneblack-ttyO4.dtb
Apr 22 16:28:20 <kinkazu_> change
Apr 22 16:28:25 <kinkazu_> and reboot
Apr 22 16:28:36 <kinkazu_> I am not sure if it is going to load
Apr 22 16:28:42 <kinkazu_> but it should he?
Apr 22 16:28:46 <rcn-ee> it should
Apr 22 16:29:34 <kinkazu_> i think I have tested this and it dind't work, but will try again
Apr 22 16:30:47 <kinkazu_> in my case
Apr 22 16:30:50 <kinkazu_> it still loads
Apr 22 16:31:05 <rcn-ee> i last tested it back in 4.0-rc6? when i tweaked the config for: CONFIG_SERIAL_8250_NR_UARTS=6
Apr 22 16:31:17 <kinkazu_>  am335x-boneblack.dtb
Apr 22 16:32:32 <kinkazu_> a ok
Apr 22 16:32:42 <kinkazu_> probably rest of the uEnv is wrong
Apr 22 16:33:01 <kinkazu_> do you have 4.0 compatible uEnv somewhere pasted?
Apr 22 16:34:36 <kinkazu_> and one more question :) how often you are here? I have got a kind of bug present in 3.8, 3.19 and also 4.0
Apr 22 16:34:49 <kinkazu_> when using can0 and one of the uarts
Apr 22 16:34:58 <kinkazu_> bbb hungs up and restarts
Apr 22 16:36:10 <rcn-ee> since it's mainline, report it to the can/usart maintainers for ti
Apr 22 16:36:43 <kinkazu_> will have to learn how to do this :) i mean report
Apr 22 16:37:16 <kinkazu_> but again, this can wait till I get more info from console debug
Apr 22 16:38:27 <vagrantc> rcn-ee: your dtb-rebuilder is essentially a fork of the linux device tree files with some Makefiles to build them out-of-tree?
Apr 22 16:38:57 * vagrantc managed to use it successfully to generate a .dtb that worked with the LCD7 using jessie's kernel
Apr 22 16:39:59 <rcn-ee> vagrantc, correct, it's a stripped down version that another developer (turns out a debian developer) setup to build all *.dtb (for all arches) i just nuked everything !arm...
Apr 22 16:40:32 <vagrantc> aha
Apr 22 16:40:50 <vagrantc> i was wondering if it would make sense to do something sort of like dkms for modules for the dtb builder stuff
Apr 22 16:40:52 <kinkazu_> rcn-ee: if you find something wrong with ttyS4, where can I find info about this?
Apr 22 16:41:04 <vagrantc> i.e. on new kernel installs, rebuild all the known dtb files
Apr 22 16:41:26 <vagrantc> or is it too fragile for something like that to work?
Apr 22 16:41:44 <rcn-ee> vagrantc, here's the main repo: https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-rebasing.git/
Apr 22 16:42:23 <rcn-ee> the only thing i reallly did was ad this install part: https://github.com/RobertCNelson/dtb-rebuilder/commit/74e2071a087934108dc2c315460584f97d52216c
Apr 22 16:42:38 <vagrantc> oh, ijc. hah
Apr 22 16:42:52 <rcn-ee> but as long as dtc is installed, it's pretty safe to setup as a dkms build..
Apr 22 16:44:28 <vagrantc> ah, even using the dkms framework... i guess it doesn't have to specifically build kernel modules.
Apr 22 16:46:26 <rcn-ee> idk... you'll also run into a case where someone copyies a custom *.dtb, they don't want that to be overriten by stable kernel updates..
Apr 22 16:48:26 <kinkazu_> Anybody can share 4.0 compatible uEnv.txt with me?
Apr 22 16:49:48 <rcn-ee> kinkazu, 4.0? other then bumping the uname_r this is no difference..
Apr 22 16:50:05 <rcn-ee> (the 4.0 is a just an incrementing number, it could be random...)
Apr 22 16:50:17 <kinkazu_> hmm
Apr 22 16:50:30 <kinkazu_> but dtb=am335x-boneblack-ttyO4.dtb
Apr 22 16:50:33 <kinkazu_> deosn't work
Apr 22 16:50:51 <kinkazu_> so something must be wrong in mu uEnv, no?
Apr 22 16:50:59 <rcn-ee> <rcn-ee> i'll look into, i need to branch dtb-rebuilder for v4.0.x to today..
Apr 22 16:51:06 <rcn-ee> hold your horses..
Apr 22 16:51:11 <kinkazu_> :)
Apr 22 16:51:19 <kinkazu_> needa learn this
Apr 22 16:51:30 <kinkazu_> need to learn to hold my horses
Apr 22 16:53:36 <kinkazu_> one more question, in 3.8.13 after gpio tree has been loaded, it was automatically exportd into /sys/class/gpio
Apr 22 16:53:46 <kinkazu_> is it still possible with 4.0
Apr 22 16:57:38 <kinkazu_> have copied and modified argus cape, but after reboot none of my gpios is in /sys/class/gpio
Apr 22 16:57:48 <kinkazu_> here is the .dtsi
Apr 22 16:57:50 <kinkazu_> http://pastebin.com/hrmZuT0z
Apr 22 16:58:48 <kinkazu_> hence question
Apr 22 17:02:39 <rcn-ee> kinkazu, /dev/ttyS4 works fine..
Apr 22 17:03:15 <rcn-ee> booted with  dtb=am335x-boneblack-ttyO4.dtb then from /dev/ttyS0 : /sbin/getty -L ttyS4 115200 vt102
Apr 22 17:03:31 <rcn-ee> rx/tx works as expected...
Apr 22 17:03:46 <kinkazu_> hmm
Apr 22 17:03:55 <kinkazu_> thanks for confirmation
Apr 22 17:05:09 <kinkazu_> uEnv pretty please :) I must have something missing
Apr 22 17:05:24 <kinkazu_> i would like to check dtb=am335x-boneblack-ttyO4.dtb
Apr 22 17:05:56 <rcn-ee> https://paste.debian.net/168318/
Apr 22 17:06:16 <kinkazu_> thank you very much
Apr 22 17:10:04 <kinkazu_> hehe, doesn't boot up, that will be all for now, but I will check it after reflash from image
Apr 22 17:11:03 <rcn-ee> kinkazu, did you copy it exactly? uuid stands for: "Universally unique identifier" so i wouldn't expect it to 'work'...
Apr 22 17:11:23 <kinkazu_> I will boot form card and change uEnv
Apr 22 17:11:26 <kinkazu_> I am lame
Apr 22 17:11:33 <kinkazu_> very fresh
Apr 22 17:19:51 <kinkazu_> rcn-ee: still loads wrong dtb
Apr 22 17:19:59 <kinkazu_> do you see anything wrong in my uEnv?
Apr 22 17:19:59 <kinkazu_> http://pastebin.com/BBhghapM
Apr 22 17:21:19 <rcn-ee> Sorry, can't mix the new /boot/uEnv.txt with the old rootfs... first reflash your eMMC: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases
Apr 22 17:21:21 <kinkazu_> my uEnv is from official img downloaded from bbb website
Apr 22 17:22:14 <rcn-ee> For the "may 2014" release, but not the "march 2015" release..
Apr 22 17:22:59 <kinkazu_> a okyes
Apr 22 17:23:01 <kinkazu_> probably
Apr 22 17:23:02 <kinkazu_> :D
Apr 22 17:23:17 <kinkazu_> ok
Apr 22 17:23:21 <kinkazu_> i know wht to do
Apr 22 17:23:38 <kinkazu_> will be back tomorrow
Apr 22 17:23:45 <kinkazu_> thank you for all help
Apr 22 17:24:36 <kinkazu_> sorry one more question
Apr 22 17:24:40 <kinkazu_> wget https://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
Apr 22 17:24:48 <kinkazu_> does it go to sd card
Apr 22 17:25:04 <kinkazu_> 4gb
Apr 22 17:25:19 <kinkazu_> or directly to mmc
Apr 22 17:25:38 <kinkazu_> have got 16gb where i do clones with dd
Apr 22 17:25:47 <kinkazu_> hence question
Apr 22 17:26:22 <rcn-ee> kinkazu, "it flashes the eMMC"  you ahve to dd it first to a microSD card..
Apr 22 17:26:32 <kinkazu_> bootable 16gb with 3.8.13 for clones and other stuff
Apr 22 17:26:38 <kinkazu_> ok
Apr 22 17:26:44 <kinkazu_> all clear now
Apr 22 18:54:50 <kinkazu_> Hi, I have built 4.0 kernel using build_kernel.sh, how do I install it?
Apr 22 19:36:02 <rcn-ee> kinkazu, build the *.deb and "sudo dpkg -i linux-image*.deb ; sudo reboot" (you need the march 2015 rootfs)
Apr 22 19:37:19 <kinkazu_> i,ve got it
Apr 22 19:37:25 <kinkazu_> got files in deploy
Apr 22 19:37:27 <kinkazu_> but if easier
Apr 22 19:37:32 <kinkazu_> i will build .deb
Apr 22 19:37:42 <kinkazu_> thank you again
Apr 22 19:37:58 <rcn-ee> kinkazu, as long as you understand where to stick the zImage/modules/dtb's it's the same...
Apr 22 19:38:08 <rcn-ee> the *.deb makes it easy as a single package
Apr 22 19:38:30 <kinkazu_> i don;t know and that is the problem
Apr 22 19:38:41 <kinkazu_> you helped me before with 3.8.13
Apr 22 19:39:00 <kinkazu_> cp -v 3.8.13-bone60.zImage /boot/uboot/zImage  rm -rf /boot/uboot/dtbs/* tar xfov 3.8.13-bone62-dtbs.tar.gz -C /boot/uboot/dtbs/ tar xfv 3.8.13-bone62-firmware.tar.gz -C /lib/firmware/ tar xfv 3.8.13-bone62-modules.tar.gz -C /
Apr 22 19:39:08 <kinkazu_> but his doesn't apply here
Apr 22 19:39:09 <kinkazu_> :D
Apr 22 19:39:24 <rcn-ee> that's for the May 2014 image..
Apr 22 19:39:31 <kinkazu_> will dpkg -i linux-image*.deb do wverything for me?
Apr 22 19:39:52 <kinkazu_> I know, hence my question after updating bbb
Apr 22 19:39:53 <rcn-ee> as long as it's the march 2015 release..
Apr 22 19:39:58 <kinkazu_> it is now
Apr 22 19:40:05 <rcn-ee> yeap
Apr 22 19:40:14 <kinkazu_> perfect
Apr 22 19:42:17 <kinkazu_> build_deb doesn't work
Apr 22 19:42:20 <kinkazu_> error: object directory /root/4.0/bb-kernel/ignore/linux-src/.git/objects does not exist; check .git/objects/info/alternates. error: invalid object 100644 1185778e6a1e0731a3b33fbbf0a6c42f3cb17aa2 for 'arch/alpha/boot/tools/mkbb.c'
Apr 22 19:42:32 <kinkazu_> aaa
Apr 22 19:42:33 <kinkazu_> ok
Apr 22 19:42:35 <kinkazu_> sorry
Apr 22 19:42:38 <kinkazu_> i am stupid
Apr 22 19:42:45 <rcn-ee> you don't need to be root. ;)
Apr 22 19:44:39 <kinkazu_> i moved the folder from one place to the other, hence problem
Apr 22 19:45:10 <kinkazu_> but it is good to know that I don't need to be root
Apr 22 19:45:12 <kinkazu_> to do this
Apr 22 19:45:37 <kinkazu_> hows the dtb-rebuilder for 4.0 going?
Apr 22 19:45:42 <kinkazu_> :)
Apr 22 19:45:57 <kinkazu_> sorry for asking
Apr 22 19:46:55 <kinkazu_> and interrupting
Apr 22 19:47:35 <rcn-ee> kinkazu, it's out..
Apr 22 20:08:23 <kinkazu_> great
Apr 22 20:41:50 <fishey1> Anyone using yocto & know how to get meta-qt5 + kms working with mesa (software rendering)?
Apr 22 20:57:48 <vagrantc> so the u-boot that has shipped on the BBB for the last year or so has contained a patch more-or-less like this one: https://rcn-ee.com/repos/git/u-boot-patches/v2015.04/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch ?
Apr 22 20:59:19 <vagrantc> seems worth getting the relevent changes into upstream u-boot, no? the main blocker with switching to upstream's config_distro_bootcmd seems to be inconsistant use of bootpart...
Apr 22 21:00:05 * vagrantc thinks it'd be worth breaking backwards compatibility to have a consistant boot framework across many boards
Apr 22 21:00:50 * vagrantc will test some patches in u-boot in debian experimental
Apr 22 21:01:57 <kinkazu_> sorry for being pain in the ass, but ttyO4 still doesn't function properly after upgrading kernel to 4.0 and after use of btb-rebuilder or dtb=am335x-boneblack-ttyO4.dtb
Apr 22 21:02:54 <kinkazu_> I can't do much testing as BBB is put into lectronic board that have been developed for me and ttyO4 is hooked up with GSM and ttyO2 hooked up with GPS of SIM928 modem
Apr 22 21:03:23 <kinkazu_> ttyO2 works fine and outputs GPS position, but I can't communciate with modem
Apr 22 21:03:41 <kinkazu_> this works fine with 3.8.13
Apr 22 21:04:01 <kinkazu_> minicom can connect to /dev/ttyO4 and responds OK to AT
Apr 22 21:04:09 <rcn-ee> kinkazu, use " dtb=am335x-boneblack-ttyS4.dtb" just changed it. ;) an hour or so ago..
Apr 22 21:04:30 <ds2> sigh.... so much less confusion with board files
Apr 22 21:04:51 <kinkazu_> in 4.0 kernel doesn't
Apr 22 21:04:55 <kinkazu_> ups and crash
Apr 22 21:04:58 <kinkazu_> now
Apr 22 21:05:03 <kinkazu_>  [  772.739263] unexpected IRQ trap at vector 00 on debug
Apr 22 21:05:15 <rcn-ee> vagrantc, i'm ready if we switch u-boot to config_distro_bootcmd. ;)
Apr 22 21:05:48 <vagrantc> rcn-ee: ok, i'll be sure to CC you when i submit a patch
Apr 22 21:05:58 <kinkazu_> I was just doing cat /dev/ttyO2 but can0 is enabled (I was not veen scanning)
Apr 22 21:06:13 <kinkazu_> I know that when I disbale can0 there will be no crash
Apr 22 21:06:26 <rcn-ee> vagrantc, i have a shim i've been usign for A10/A20's.. https://github.com/RobertCNelson/netinstall/blob/master/lib/distro_defaults.cmd that emulates what i do on the bbb..
Apr 22 21:07:05 <vagrantc> rcn-ee: in general, it seems like u-boot mainline goes along with whatever the community for that board wants ... maybe CC jkridner as well
Apr 22 21:08:18 <rcn-ee> vagrantc, and if you make it generic enough, that all omap's can be converted to config_distro_bootcmd... I think Tartarus would take that in a heart beat...
Apr 22 21:08:43 <vagrantc> the main question is breaking backwards compatibility
Apr 22 21:09:25 <rcn-ee> for most omap's... u-boot is on the microSD, so you just have to worry about the nand devices.. we 'broke' the beagle a while back, when we switched to generic load... no one cared...
Apr 22 21:09:34 <vagrantc> rcn-ee: so that distro_defaults.cmd ... is that a bootscript you would make available via config_distro_bootcmd ?
Apr 22 21:10:04 <rcn-ee> vagrantc, correct, right now i use that on 'any" config_distro_bootcmd target..
Apr 22 21:10:15 <vagrantc> got it.
Apr 22 21:11:19 <vagrantc> it might need to be enabled on a case-by-case basis, if the boards with NAND has size limits, the config_distro_bootcmd stuff might break that
Apr 22 21:11:59 <rcn-ee> anything omap4/am335x+ will be safe.. it's the omap3's we will have to test, as some of them only have 128Mb's of ram...
Apr 22 21:14:11 <rcn-ee> kinkazu, can you pastebin your *.dts file and your serial boot log?
Apr 22 21:15:59 <vagrantc> rcn-ee: did you say i should drop that voltage patch?
Apr 22 21:16:17 <Tartarus> Yeah, I'd be agreeable to converting the TI platforms over to the generic distro framework
Apr 22 21:16:24 <Tartarus> OE can work with that too so arago will survive :)
Apr 22 21:17:18 <rcn-ee> vagrantc, yeah drop it... guys at ti found issues on am43xx when in the same situation, since we can't properly tell the sdram we are downclocking in kernel land, it's best to just keep the high volrage (1.5) vs brining it back down to (1.35) as random "issues" can present...
Apr 22 21:18:04 <vagrantc> Tartarus: ah, great to hear it!
Apr 22 21:18:26 <vagrantc> i made a weak attempt a while back, and it looks easier now.
Apr 22 21:18:55 <rcn-ee> vagrantc, originally, arudino folks where trying to elimiate some noise that was causing fcc testing issues, that was one source we looked at..
Apr 22 21:19:28 * vagrantc thinks that's shipping on 2014.10 in jessie at this point
Apr 22 21:19:36 <vagrantc> but i'll drop it from the next updates
Apr 22 21:19:53 <rcn-ee> it'll be fine, as the kernel will put it back to 1.5v. ;)
Apr 22 21:22:17 <rcn-ee> vagrantc, the real fix, is to build board with rev "c" of the pmic an not touch that ldo (in u-boot/kernel), as it's setup for 1.35v ddr by default...
Apr 22 21:30:52 <kinkazu_> rcn-ee: bootlog http://pastebin.com/9nT8dWG4
Apr 22 21:31:21 <kinkazu_> rcn-ee: would you like me to decompile dts after being compiled by dtb-rebuilder?
Apr 22 21:31:28 <kinkazu_> or jus .dts from rebuilder
Apr 22 21:31:54 <rcn-ee> which dtb= did you use?
Apr 22 21:35:12 <kinkazu_> behaves the same when I use dtb=am335x-boneblack-ttyO4.dtb or compiled am335x-boneblack.dts from this: http://pastebin.com/y19J64w9
Apr 22 21:36:16 <kinkazu_> ofcourse all baudrate settings are fine, and modem has got autobauding anyway
Apr 22 21:37:27 <kinkazu_> have got it working with 3.8.13, but was crashing when can0 was in use, so decided to load the newest kernel, because I guess noobody will support me will the old one
Apr 22 21:38:09 <kinkazu_> but without can0 3.8.13 works perfectly ok with GPS on ttyO2 and modem on ttyO4
Apr 22 21:38:51 <kinkazu_> and in 4.0, something is wrong with ttyO4, even if dts is fine, i am almost sure there is no mistake there
Apr 22 21:39:22 <kinkazu_> and said it works on your side, so I am crossed, why it doesn't work with the modem's uart
Apr 22 21:41:11 <kinkazu_> I don't care about can0, that must be something bigger, but why ttyO4 doesn't work withe modem anymore
Apr 22 22:12:31 <kinkazu_> if I want to run kernel with -noirqdebug, where in uEnv this should be put in?
Apr 22 22:56:17 <kinkazu_> I put noirqdebug into cmdline in uEnv.txt, problem with crash on can0 and ttyO2 seem to be gone
Apr 22 22:56:46 <kinkazu_> probem with ttyO4 is still there no matter why I do
Apr 22 23:08:46 <kinkazu_> ope
Apr 22 23:09:00 <kinkazu_> nope noirqdeub does nothing :(
Apr 22 23:12:30 <kinkazu_> unless it needst go somewhere else i uenv
Apr 22 23:54:07 <kinkazu_> setenv bootargs 'console=ttyO2,115200n8 noirqdebug debug'
Apr 22 23:54:22 <kinkazu_> is this the right place to put kernel parameters?
Apr 22 23:54:35 <kinkazu_> in uEnv?
Apr 23 00:18:23 <veremit> which uenv ...
**** ENDING LOGGING AT Thu Apr 23 02:59:58 2015