**** BEGIN LOGGING AT Wed Sep 11 02:59:59 2013
Sep 11 08:18:44 <HRH_H_Crab> ~]
Sep 11 08:18:46 <HRH_H_Crab> oops
Sep 11 12:39:36 <fenrig> Hi 
Sep 11 12:39:53 <fenrig> i'm having serious problems with angstrom v2013.06
Sep 11 12:39:57 <fenrig> and meta-toolchain-qt
Sep 11 12:40:04 <fenrig> namely qmake segfaults
Sep 11 12:40:28 <fenrig> I have this on the qemuarm machine but also on the raspberry pi (didn't test it further because of lack of hard disk space)
Sep 11 12:44:06 <cfo215> fenrig, are you using ubuntu 12.04.2 lts by any chance?
Sep 11 12:45:49 <fenrig> cfo215: archlinux :/
Sep 11 12:47:04 <cfo215> fenrig: i was having all sort of wierdness with ubuntu and qt/e, I switched to fedora 19 and everything mysteriously went away.
Sep 11 12:47:30 <cfo215> fenrig, not saying that will work for you. but it did for me.
Sep 11 12:48:03 <fenrig> cfo215: I can try :o i'll prepare another machine for the job
Sep 11 12:48:40 <cfo215> fenrig, good luck
Sep 11 12:49:10 <fenrig> cfo215: thx for the good advice, it'll probably work. (you'll hear the outcome anyway probably :p)
Sep 11 12:49:47 <cfo215> fenrig, I've been learning the hard way too.
Sep 11 12:52:16 <fenrig> cfo215: the yocto way = the hard way
Sep 11 12:52:31 <cfo215> :)
Sep 11 12:52:42 <fenrig> cfo215: I knew that it wasn't going to be easy,
Sep 11 12:53:03 <bluelightning> fenrig: to be fair, I'm not sure this problem is the Yocto Project's fault
Sep 11 12:53:05 <cfo215> fenrig, I'm hoping it will be in the end.
Sep 11 12:53:20 <fenrig> bluelightning: I'm not blaming yocto :p
Sep 11 12:54:02 <bluelightning> well, otherwise we'd be happy to have suggestions on how we can make the system easier to use
Sep 11 12:54:11 <cfo215> bluelightning, now that's funny!  lmao
Sep 11 12:54:54 <bluelightning> cfo215: sorry, what is?
Sep 11 12:56:08 <cfo215> you're the Qt guy.  It's a Qt issue he's having... my mind is a little twisted that way.
Sep 11 12:56:24 <bluelightning> ok :)
Sep 11 12:56:51 <bluelightning> FWIW, I am building meta-toolchain-qt here for qemuarm on an ubuntu 12.04 machine as we speak
Sep 11 12:57:05 <bluelightning> but with poky, not angstrom
Sep 11 12:57:43 <cfo215> i'm trying to get my rtl8192c based wifi card working... rtl8192c_common: Unknown symbol ieee80211_find_sta (err 0) trying to load the ko file.
Sep 11 12:58:44 <cfo215> actually i have it working off one SD card... I just cant remember wtf I did to get it working.  Starting fresh and trying to retrace/debug.
Sep 11 12:59:22 <bluelightning> brb
Sep 11 13:01:16 <fenrig> bluelightning: are you using the yocto 1.4 release?
Sep 11 13:01:28 <fenrig> bluelightning: i'm using the angstrom v2013.06 release
Sep 11 13:03:19 <cfo215> fenrig, me too.
Sep 11 14:08:38 <Crofton|work> bluelightning_, it seems like we should try and get together a qt team to work through setting up a complete qt ev env with oe
Sep 11 14:09:02 <bluelightning_> Crofton|work: I think that would be a good idea
Sep 11 14:09:12 <bluelightning_> Crofton|work: something we could do at ELCE in person perhaps?
Sep 11 14:09:26 <bluelightning_> or were you thinking online?
Sep 11 14:09:30 <Crofton|work> we can certainly work on getting it kicked off
Sep 11 14:09:48 <Crofton|work> it seems like there are several people collecting data
Sep 11 14:10:01 <Crofton|work> online is needed, but in person meetings are always good
Sep 11 14:10:38 <Crofton|work> I do not want to lose all the information we are collecting atm
Sep 11 14:11:21 <bluelightning_> we could always collect it in a wiki page
Sep 11 14:12:07 <Crofton|work> my main object is to get a framework setup for interest groups
Sep 11 14:12:17 <Crofton|work> and some ongoing effort to make ebedded development easier :)
Sep 11 14:12:33 <bluelightning_> right, sounds like a good idea
Sep 11 14:14:24 <Crofton|work> I am getting a bine and a screen so I can at least try and test some of the problems people have
Sep 11 14:14:38 <Crofton|work> but I draw the line at installing ubuntu :)
Sep 11 14:14:45 <bluelightning_> a bine?
Sep 11 14:14:58 <Crofton|work> line
Sep 11 14:15:45 <bluelightning_> I'm certainly not lacking in platforms to test on, just time...
Sep 11 14:16:09 <Crofton|work> :)
Sep 11 14:16:11 <Crofton|work> yeah
Sep 11 14:16:16 <Crofton|work> I am nultitaking atm :)
Sep 11 14:16:26 <Crofton|work> multitasking :)
Sep 11 14:16:27 <bluelightning_> same here, I'm in a meeting :)
Sep 11 14:16:32 <Crofton|work> rofl
Sep 11 14:30:41 <cfo215> Crofton|work,  how about a BBB?
Sep 11 14:30:53 <Crofton|work> ?
Sep 11 14:31:21 <Crofton|work> that is what I ordered
Sep 11 14:31:23 <Crofton|work> I hope :)
Sep 11 14:35:16 <bluelightning_> Crofton|work: ah, when you said "bine" you meant "bone"
Sep 11 14:35:30 <Crofton|work> heh
Sep 11 14:43:08 <carpman> hiya. Anyone know where I can get xserver-xorg-input-tslib or equivilent on angstrom?
Sep 11 14:48:57 <cfo215> BBB=Beaglebone Black.  As apposed to BBW which would be the original beaglebone (the white one, hence BBW).
Sep 11 14:57:40 <cfo215> Crofton|work, i hope you got a rev. A5(C) which is what I have.
Sep 11 15:02:57 <cfo215> I'm a bit confused.... I'm working from the origin/angstrom-v2013.06-yocto1.4 branch.  which I assume has the most recent source code for Angstrom.  If that is, in fact, the case then why is it when I do an opkg upgrade it uprades my system to newer versions of the packages?  Am I missing something?
Sep 11 15:05:42 <cfo215> where does the default repository get it's packages from?  obviously, it has more current packages than I can generate with the Angstrom-Distribution setup-scripts provided by koen.
Sep 11 15:11:04 <Crofton|work> hmm
Sep 11 15:11:47 <Crofton|work> can you browse te feeds and see what dates the packages where uploaded
Sep 11 15:13:26 <Crofton|work> as in you build a current image and opkg update/upgrade get packages from the feeds
Sep 11 15:13:34 <Crofton|work> I wonder if this is a PR server thing?
Sep 11 15:17:57 <cfo215> 09-Sep-2013 is as recent as I seen (at lease in http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/cortexa8hf-vfp-neon/machine/beaglebone/)
Sep 11 15:18:11 <cfo215> PR?
Sep 11 15:19:13 <Crofton|work> and do the packages that update have recent dates?
Sep 11 15:19:35 <bluelightning> to be honest, if you're building your own images I would not expect to be able to use the angstrom feeds
Sep 11 15:19:52 <Crofton|work> I think it shoudl work
Sep 11 15:20:01 <Crofton|work> since the versions should be sane
Sep 11 15:20:13 <bluelightning> at least, unless angstrom points you to its PR server in its configuration (and maybe it does do that, I haven't checked) the PR values definitely can be different which may well cause problems
Sep 11 15:20:48 <cfo215> it is working... which is why I'm confused.
Sep 11 15:23:15 <cfo215> wtf is PR?  sorry I know its a newbie question.
Sep 11 15:24:15 <Crofton|work> package rev
Sep 11 15:25:31 <cfo215> on my system bitbake generates /beaglebone/kernel-module-rtl8192cu_3.8.13-r23a.2_beaglebone.ipk  on the feeds it's 	kernel-module-rtl8192cu_3.8.13-r23a.53_beaglebone.ipk
Sep 11 15:25:44 <bluelightning> cfo215: it's the very last number in the package name, almost always starts with "r" by convention
Sep 11 15:25:55 <cfo215> thank you.
Sep 11 15:27:02 <cfo215> the .nn e.g .53 is a build number then?  so in theory, if i'm reading it right, those should be the same since the r23a is the same?
Sep 11 15:30:57 <cfo215> i guess I'm just asking too much of Angstrom.. silly me.. why would anyone want to use a wireless usb dongle anyway.
Sep 11 15:31:16 <Crofton|work> apparently a read-only master PR-server is not supported
Sep 11 15:31:28 <Crofton|work> so everyone doing angstrom builds can bump PR
Sep 11 15:31:32 <Crofton|work> this is a headache
Sep 11 15:34:47 <fenrig> I still have some spare time, and a spare desktop lying around :)
Sep 11 15:35:16 <fenrig> but I'm not that skilled in using yocto :/
Sep 11 15:35:52 <fenrig> allthough I have set up a angstrom/yocto (2013.06) on my raspberry pi
Sep 11 15:36:50 <cfo215> fenrig, did you happen to get wireless lan working with it?
Sep 11 15:37:32 <fenrig> cfo215: yep :)
Sep 11 15:37:36 <cfo215> fenrig, I have a RPi at home.  Maybe I'll try building an image for it to test my wireless with.
Sep 11 15:37:50 <fenrig> cfo215: if you want I can send you my image :p
Sep 11 15:37:51 <cfo215> fenrig, rtl8192c* by any chance?
Sep 11 15:38:03 <fenrig> cfo215: I think so yes :)
Sep 11 15:38:35 <fenrig> cfo215: and I used connman for configuring the wireless
Sep 11 15:38:56 <fenrig> cfo215: i'll share my image configuration with you ;)
Sep 11 15:39:39 <cfo215> fenrig, nice!  Let me try building one first.  Then if I run into trouble we can compare notes.
Sep 11 15:39:55 <fenrig> Crofton|work: I have some spare time, and I'm willing to learn more about yocto ;)
Sep 11 16:23:36 <cfo215> koen's response... http://www.codealpha.net/864/how-to-set-up-a-rtl8192cu-on-the-beaglebone-black-bbb/ to my rtl8192 issues.  yet another well documented article and if this is the fix wtf isn't he using this in the Angstrom setup-scripts?
Sep 11 16:26:49 <cfo215> and if this is in fact the "fix" why isn't there an Angstrom Setup-Scripts Howto for it?  E.g.  open a terminal ... cd into your angstrom sdk folder (/usr/...)... source the environment..., blah blah blah at nAd nauseam
Sep 11 16:27:28 <cfo215> I've lost so much time to this crap disto that it isn't even funny.
Sep 11 16:28:12 <cfo215> I know I'm a newbie but nothing should be this hard.  If you know theres a fix then just put it in.. just saying.  Instead of leaving people struggling with the crap.
Sep 11 16:38:29 <fenrig> cfo215: :/ I had no trouble whatsoever with linux-firmware
Sep 11 16:40:36 <cfo215> fenrig, its inconsistent.  some people have trouble, some don't.  I'm in the prior category.  I have one SD card image that the wireless works with.  I'll probably just have to keep cloning it.  Which is a kludge, not a resolution.
Sep 11 17:03:23 <cfo215> fenrig, are you using a Beaglebone Black?  or just the RPi?
Sep 11 20:03:31 <cfo215> So if followed the instructions, built the new 8192cu.ko file, transferred it to the BBB and behold... the wifi usb adpter still doesn't work.  At least it now tries to load the kernel module.  I guess that is progress.  pastbin of errors at http://pastebin.com/hsySczvt if anyone cares to look.
Sep 11 20:06:45 <Crofton|work> where did you get that dongle?
Sep 11 20:07:01 <cfo215> adafruit p/n 814
Sep 11 20:07:07 <Crofton|work> looks like linkage failure
Sep 11 20:07:37 <cfo215> http://www.adafruit.com/products/814#Technical_Details
Sep 11 20:08:09 <cfo215> I don't know what the means.
Sep 11 20:08:17 <Crofton|work> looks handy, how much shipping do they charge?
Sep 11 20:09:22 <cfo215> not much.  it's based on weight.  probably $5-8. can't remember
Sep 11 20:09:56 <cfo215> I always pick the cheapest, USPS.  Not Fedex or UPS.
Sep 11 20:10:44 <Crofton|work> yeah
Sep 11 20:11:03 <cfo215> I figured no one would respond to me after my little rant earlier :)
Sep 11 20:16:02 <cfo215> still, I don't understand why it works on one SD card and not on an other.  It's the exact same hardware.
Sep 11 20:17:19 <Crofton|work> it look sliek the module can't link against the kernel symbold table
Sep 11 20:17:39 <Crofton|work> I'll order one, I can test it on my custom board also
Sep 11 20:18:54 <cfo215> thanks.  I can just drive mine up to you and save you the trouble ;-)
Sep 11 20:20:44 <Crofton|work> Crofton|work: you can also import http://dominion.thruhere.net/koen/angstrom/prserv-angstrom-v2013.06-2013.09.11.txt with bitbake-prserv-tool
Sep 11 20:20:53 <Crofton|work> apparently there are way sto sync th epr-serv
Sep 11 20:20:59 <Crofton|work> but I'm afraid to mess with it
Sep 11 20:22:05 <cfo215> I'm going to order a couple of the listed dongles from the circuitco web and see if they work any better.
Sep 11 20:22:39 <Crofton|work> you do see the firmware load?
Sep 11 20:22:51 <cfo215> is that ultimately put on the file system somewhere?  if so I can diff against my working SD card's fs.
Sep 11 20:22:57 <Crofton|work> yep
Sep 11 20:23:22 <Crofton|work> look in /lib/firmware
Sep 11 20:23:32 <Crofton|work> maybe even find / -name firmware
Sep 11 20:24:39 <cfo215> i have /lib/firmware/rtlwifi/rtl8192cufw.bin
Sep 11 20:24:49 <Crofton|work> that looks like one
Sep 11 20:24:58 <cfo215> on the broken system.
Sep 11 20:25:11 <Crofton|work> but not on the working one?
Sep 11 20:25:27 <cfo215> looking...
Sep 11 20:25:57 <cfo215> yes it's there too.
Sep 11 20:27:12 <Crofton|work> watch for errors loading that
Sep 11 20:51:33 <cfo215> Crofton|work, is there a way to manually load that file (/lib/firmware/rtlwifi/rtl8192cufw.bin).  I'm not finding it or anything close to it in the logs.
Sep 11 21:16:46 <cfo215> Crofton|work, I was looking at the "official" wifi adapters and they all seem to be rtl8192 based units.  Now I hesitate to buy one.
Sep 11 21:22:29 <Crofton|work> Heh today I dueled u-boot
Sep 11 21:22:34 <Crofton|work> tomorrow I duel the kernel
Sep 11 21:22:40 <Crofton|work> for some custom zynq hw
Sep 11 23:05:50 <fenrig> cfo215: yeah just raspberry pi
Sep 11 23:11:49 <fenrig> cfo215: I'm apparently losing another dongle :/ so i'm not using that firmware
Sep 11 23:15:29 <fenrig> *using
**** ENDING LOGGING AT Thu Sep 12 02:59:59 2013