[00:01] <dcordes> MrCurious: serial port ?
[00:02] <MrCurious> yes
[00:02] <MrCurious> a bluetooth serial port
[00:04] <MrCurious> http://www.satistronics.com/serial-port-bluetooth-module-masterslave-hc05_p2863.html
[00:04] <MrCurious> works fine with Mac
[00:07] <MrCurious> they are very nice modules for connecting serial devices wirelessly
[00:08] <MrCurious> like AVR's, MSP's
[00:09] <dcordes> do you think that's a problem specific to ubuntu arm on the device ?
[00:14] <MrCurious> well, i imagine first step would be checking the os for the os prescribed method of associating
[00:15] <MrCurious> then drop to the device to see if its wired wrong.
[00:15] <MrCurious> wouldn't you agree?
[00:20] <dcordes> MrCurious: I fear I am not following
[00:20] <MrCurious> i am saying wouldnt you look to how something is done in the os before declaring  the motherboard at fault?
[00:21] <MrCurious> in otherwords, until i learn how ubuntu would associate with a bluetooth serial device, there is no sense pointing fault at the hardware
[00:21] <MrCurious> if the answer is ubuntu has no concept of bluetooth then i can move on
[00:24] <MrCurious> dcordes: never mind, i think there is a language translation issue at play here, and i dont wish to frustrate you
[00:27] <dcordes> MrCurious: oh sorry, I didn't mean to say it is a hardware problem. let me restate: did you try that serial connection in a different environment ?
[00:28] <dcordes> MrCurious: or: did you ever have a working bluetooth connection on your pandora board in ubuntu ?
[00:28] <dcordes> (maybe something more trivial like blueooth hid device
[00:29] <MrCurious> the module has been tested working with mac osx
[00:29] <MrCurious> discoverable, pairable, and serial communications tested working
[00:30] <MrCurious> yes, so the only unknowns are ubuntu on pandaboard
[00:30] <MrCurious> all else tested previously working
[00:30] <MrCurious> apologies for not stating that or stating it clearer :) i am juggling too many things
[00:34]  * persia points at irclogs.ubuntu.com for logs of this channel
[00:34] <dcordes> persia: ok thanks
[00:34] <dcordes> persia: maybe orga can put a reference in the topic
[00:34] <persia> dcordes, I don't know where the bug needs to be filed, but my recommendation would be to dig through the library docs, and find out what is supposed to check the environment variable: make sure that is loaded.
[00:34] <dcordes> MrCurious: unfortunately I am not very familiar with bluetooth at all, just trying to check if you have a working test environemnt and are narrowing down the error
[00:35] <MrCurious> thats fine. i was just asking to see if anyone knew how to get the bluetooth associate with device dialog up
[00:35] <persia> MrCurious, I'm certain that ubuntu-11.04-preinstalled-netbook-armel+omap4.img.gz isn't corrupt, as I used it to install a panda :)
[00:35]  * MrCurious nudges someone to remove the 11.04 omap4 image, its broked
[00:36] <MrCurious> i tried it on multiple sd's
[00:36] <MrCurious> multiple machines to burn it, multiple procedures
[00:36] <persia> Did you check the checksums of your download?
[00:36] <persia> It really worked for me.
[00:36] <MrCurious> doesnt TCP guarantee error free transmission
[00:36] <dcordes> persia: nice
[00:36] <persia> Theoretically.  In practice, not so much.
[00:37] <dcordes> persia: http://doc.qt.nokia.com/main-snapshot/qapplication.html#setGraphicsSystem found this
[00:37] <MrCurious> i could try it again.
[00:37] <MrCurious> but it seems many are having issues
[00:37] <persia> dcordes, That looks like a good place to start.
[00:37] <MrCurious> from the mail lists
[00:37] <persia> As you like.  It worked for me.
[00:38] <dcordes> persia: worst case I could grep the unity-2d-* code for setGraphicsSystem and default to native
[00:38] <persia> dcordes, I very strongly disbelieve that the unity-2d-* code has anything to do with that: it's very likely to be something with Qt
[00:40] <persia> I may be wrong though :)
[00:40] <dcordes> persia: the thing that makes be believe they should take the QT_GRAPHICSSYSTEM env var is that they do read the -graphicssystem switch
[00:41] <MrCurious> persia: while i am re-downloading it, do you by chance have any experience with bluetooth devices in ubuntu :)
[00:41] <persia> Do you think that is being done by unoty-2d, or automatically because unity-2d instantiates qapplication?
[00:41] <dcordes> e.g. "unity-2d-launcher -graphicssystem=native" will give me native graphicssystem while "QT_GRAPHICSSYSTEM=native unity-2d-laucnerh" will not
[00:41] <persia> MrCurious, Far too much, sadly.  I have no idea if the bluetooth device the panda claims to have works (I think there's no antenna, and I haven't played with it).
[00:42] <MrCurious> it has a onboard ceramic
[00:42] <MrCurious> i can turn on bluetooth
[00:43] <MrCurious> but i dont know where to go to get the list of bluetooth devices to pair with
[00:43] <persia> Use any of the bluetooth management tools.  What's your environment?
[00:44] <persia> If it's the netbook environment you're currently downloading, you'll get a bluetooth indicator when bluetooth is available, and can launch the discovery widgets from there.
[00:44] <dcordes> persia: I don't know. I will download the code
[00:44] <persia> dcordes, Makes sense.  Someone might have overridden the default to force 2D, although that seems unfortunate to me.
[00:45] <persia> dcordes, But if you don't find it, don't be discouraged: it may be something about how qapplication is instantiated, etc.
[00:45] <dcordes> persia: not sure what qapplication is
[00:45] <dcordes> persia: I will just stupidly grep for the setGraphicsSystem
[00:46] <persia> QApplication: http://doc.qt.nokia.com/main-snapshot/qapplication.html : the parent class for most Qt applications.
[00:46] <persia> (you may already have this page open)
[00:47] <dcordes> ah right :)
[00:54] <dcordes> persia: why do you think it's unfortunate ?
[00:54] <dcordes> persia: at least they had a reason for it :
[00:54] <dcordes>     /* Forcing graphics system to 'raster' instead of the default 'native'
[00:54] <dcordes>        which on X11 is 'XRender'.
[00:54] <dcordes>        'XRender' defaults to using a TrueColor visual. We do _not_ mimick that
[00:54] <dcordes>        behaviour with 'raster' by calling QApplication::setColorSpec because
[00:54] <dcordes>        of a bug where black rectangular artifacts were appearing randomly:
[00:55] <persia> That would be unfortunate because of a choice to work around a bug rather than fixing it.
[00:56] <dcordes> oh that makes sense
[00:56] <persia> The more so because it causes other problems (like the one you are experiencing)
[00:56] <dcordes> well it seems they fixed that bug already because running with the native works just fine on my device
[00:56] <persia> We have no idea.  There's no documentation of the bug, nor the environment in which it was produced.
[00:57] <dcordes> maybe I should let them know via https://bugs.launchpad.net/unity-2d/+bug/734143
[00:57] <ubot2> Ubuntu bug 734143 in unity-2d "Black rectangular artifacts appearing when opening a few launcher contextual menus" [High,Fix released]
[00:57] <dcordes> the url is from above comment
[00:57] <persia> Oh, there was a URL!  Excellent.  That's doing it right.
[00:58] <dcordes> status: In Progress → Fix Committed
[00:58] <persia> I'd recommend getting someone to try it on a macbook pro 7.1 with -gtgraphicssystem=native
[00:58] <persia> Maybe it's something unique to that hardware, or something in that render path, etc.
[00:58] <dcordes> I wonder if by fix fboucault means the default raster
[00:59] <persia> The "fix" is http://bazaar.launchpad.net/~fboucault/unity-2d/dont_set_colorspec/revision/447
[01:00] <dcordes> ok
[01:00] <persia> The missing part is the investigation of the render path on the hardware showing the bug to find the underlying bug.
[01:00] <dcordes> so what about s/raster/native/ ?
[01:00] <persia> So, unity-2d is "fixed" with the workaround.
[01:00] <persia> *but* the underlying bug still remains, and needs investigation.
[01:00] <persia> If that is fixed, the workaround may be removed from unity-2d
[01:00] <persia> Which then solves your issue.
[01:01] <persia> I strongly suspect that use of "native" on the hardware reported in 734143 will continue to show the issue.
[01:01] <dcordes> ok
[01:01] <persia> So it's not safe to just randomly assign it to "native", unless you want to carry a fork for some time.
[01:02] <persia> Depends on your goal, really.  If you want Ubuntu 11.10 to just work on your device, you'll want to fix the issue with the MacBook Pro.
[01:02] <persia> If you want Ubuntu 11.04 to work on your device *now*, you'll fork the code.
[01:03] <persia> (yes, fixing a MacBook Pro to help make an ARM handheld work better seems counter-intuitive, but it's all in the spirit of collaboration :) )
[01:03] <dcordes> persia: my suggestion: switch back to native and work around on the macbook pro. according to bill filler, unity-2d is supposed to provide support for devices with no hardware accelerated graphics, especially ARM devices
[01:03] <persia> Why not just fix the macbook pro issue?
[01:04] <persia> Then nobody needs any workarounds.
[01:04] <dcordes> that would be best
[01:05] <persia> I'd probably start by finding someone with the hardware, and having them test (we know kaleo has such an environment: others may).
[01:05] <dcordes> a) I don't have a macbook b) I have the impression that I have the smaller lobby, with only one person reporting raster problems.
[01:05] <dcordes> my two issues with that
[01:05] <dcordes> which forbid moving the process on
[01:05] <persia> Try to make a simpler test-case, which can then be given to the X team, who may be able to sort the rendering path issue.
[01:06] <persia> a) doesn't matter: there are lots of other people with the hardware.  Just find one.
[01:06] <persia> b) Who cares if it's just you reporting an issue: 734143 was also just one person.
[01:06] <dcordes> if I prepare such a well working natty image for easy install t housands will download it in short time
[01:06] <dcordes> and use it on that device
[01:07] <persia> That's not interesting in terms of bugfixing (although interesting in other ways).
[01:07] <persia> What's interesting in terms of bugfixing is the investigation of the issue.
[01:08] <persia> So, you'll want to find someone with the hardware (I gave you one name: randomly asking in #ubuntu+1 or #ubuntu-testers will probably get you some more)
[01:08] <persia> Then you'll want to work with them to find out precisely when the black rectangles occur
[01:08] <persia> Then you'll want to prepare a minimal program that generates the black rectangles
[01:08] <persia> Then you'll want to submit that to the rendering folk (as a new bug), who will likely sort it.
[01:08] <dcordes> ok
[01:09] <dcordes> maybe the potential testers can even help a bit with that
[01:09] <persia> If Kaleo has time to help, he'll probably be glad to help make the minimal program (he's the reporter of 734143)
[01:09] <dcordes> I am not a good programmer :)
[01:09] <persia> Yet :)
[01:09] <MrCurious> any idea which device would be the bluetooth radio?
[01:10] <persia> But seriously, 99% of this is just a matter of tracking down who can reproduce, and who understands the rendering path, and getting them to discuss/test the issue.
[01:11] <persia> MrCurious, When you say "which device", what do you mean? (as I doubt answering with the chip model will help you)
[01:11] <MrCurious> trying to get a lead on the bluetooth modem. working with hcitool now
[01:12] <MrCurious> trying to give myself a bluetooth clue
[01:12] <MrCurious> its not going as fast as i would like :(
[01:12] <persia> hcitool is *very* low level.
[01:12] <persia> (and incredibly hard to use, in my experience)
[01:12] <persia> What's your high-level goal?
[01:12] <MrCurious> got a better tool that i can explore
[01:12] <MrCurious> want to see devices that i can pair with (for the purpose of a serial port)
[01:13] <MrCurious> i have tested bluetooth serial port modules
[01:13] <MrCurious> work with mac
[01:13] <MrCurious> wanting to get them working with linux now
[01:13] <dcordes> persia: I see. So the problem is basically that the workaround situation satisfies most and potential problems are not being noticed
[01:13] <persia> dcordes, That's my opinion, yes.
[01:14] <persia> dcordes, And further that you've exposed one of the problems, so they aren't just "potential"
[01:14] <persia> MrCurious, So, if you boot to the desktop, do you have a bluetooth icon on the indicator?
[01:14] <dcordes> persia: Ok then, thanks a lot
[01:15] <MrCurious> yes
[01:15] <MrCurious> currently it shows as turned on
[01:16] <MrCurious> i know teh mac address of the serial port bluetooth device 20:11:02:17:10:97
[01:16] <persia> OK.  Now, choose "Set up new device..."
[01:16] <MrCurious> where do i find set up new device?
[01:16] <persia> Should be in the indicator menu
[01:16] <dcordes> persia: hope I can catch kaleo around tomorrow. need to take a nap now. good night !
[01:16] <MrCurious> it has turn off, and preferences
[01:16] <MrCurious> preferences has a recieve files button
[01:16] <MrCurious> and a big turn on button
[01:17] <persia> Press the "Turn on" button
[01:17] <MrCurious> i did
[01:17] <MrCurious> the bluetooth  drop down remains un changed
[01:17] <persia> Hrm.  For me, the indicator menu has "Set up new device..." and the preferences window has a "Set up new device..." button.
[01:18] <persia> You're running Ubuntu 11.04?
[01:18] <MrCurious> 10.10 upgraded to 11.04
[01:18] <persia> That shouldn't make a difference.
[01:18] <MrCurious> thinking its time to do the re-download, re-install thing
[01:18] <persia> That's typically pointless, unless you want to change filesystems for some reason.
[01:18] <persia> If it's not pointless, that's a bug.
[01:20] <persia> So, you're looking for something that looks like http://library.gnome.org/users/gnome-bluetooth/stable/figures/bluetooth-properties.png.en
[01:20] <persia> Is this very different from the bluetooth preferences dialog you see?
[01:20] <persia> (ignore the language differences)
[01:20] <MrCurious> persia: this command similar to what you used? zcat ubuntu-11.04-preinstalled-netbook-armel+omap4.img.gz | dd of=/dev/sda bs=16M
[01:21] <persia> I verified the checksums, ran gunzip, and then (separately) ran `dd if=... of=/dev/sdg bs=4M`
[01:21] <persia> Shouldn't matter that much though.
[01:22] <persia> Did you make sure that /dev/sda is not mounted?
[01:23] <MrCurious> did NOW :D
[01:24] <MrCurious> could swear it wasnt mounted when i started
[01:24] <persia> The automounter is kinda aggressive :)
[01:24] <MrCurious> doing it on a chumby
[01:24] <MrCurious> because its stable-ish
[01:24] <MrCurious> and has a not-used sd slot
[01:25] <MrCurious> although since i switched to a USB SSD for rootfs, the panda has been rock solid
[01:25] <MrCurious> something about SD cards i just dont trust
[01:26] <persia> Unfortunately the panda cannot function without one
[01:26] <persia> (although one doesn't really need it post-boot, if one configures everything just so)
[01:27] <MrCurious> that i did, but then i turned the SD card into SWAP
[01:27] <MrCurious> seemed tolerable once there was no FS on it compeeting for bandwidth
[01:27] <persia> That will give it a nice short lifetime )
[01:27] <MrCurious> persia: this 16g 20mb/s card has offended me by constantly corrupting with the 11.04 image
[01:28] <MrCurious> persia: i might point out to you that the ubuntu image's have swap on the ssd enabled by default
[01:28] <MrCurious> so seems short lives are not a concern in these parts ;)
[01:28] <MrCurious> see the file in the root directory
[01:28] <MrCurious> SWAP.swap
[01:28] <MrCurious> and check your free, its turned on
[01:31] <persia> Oh, I know.  First thing I turn off.  The issue is that some folk want to be able to run with 256MB, which simply cannot work without swap: the swapfile was turned on to avoid OOM issues on first-boot.
[01:34] <MrCurious> ahhh
[01:34] <MrCurious> so in future, it will self-disable after resize?
[01:34] <persia> Not soon, no.
[01:35] <persia> It doesn't turn on until after resize.
[01:35] <MrCurious> thats what i mean
[01:35] <MrCurious> i think it stayed on well into first boot
[01:35] <MrCurious> possibly second boot
[01:35] <persia> And it's likely to remain until the vast majority of available devices work well without swap.
[01:35] <persia> It stays on forever unless manually disabled or removed.
[01:36] <MrCurious> i dont feel so bad about swapping to sd now :D
[01:36] <MrCurious> but i think i will move over to swapping to spinning disk soon
[01:37] <persia> That should get you expanded SD life.
[01:38] <persia> Although if you really want speed, you want to swap to battery-backed RAM or similar.
[01:38] <persia> (which is designed for the sort of random-access treatment swapping needs)
[01:40] <MrCurious> does battery backed ram exist?
[01:41] <persia> Yes.
[01:42] <persia> I haven't seen any in the shops in a couple years, but it used to be common with PATA and PCI interfaces.
[01:42] <MrCurious> pata...
[01:42] <persia> I suspect someone has put together some SATA or USB devices like this, although they may only be available by special order.
[01:44] <persia> Ah, The Acord ANS-9010 apparently goes up to 64GB.  You can't use this for real memory, but it makes for decent swap, if you have that sort of performance requirement (gamers, heavily-loaded servers, etc.)
[01:44] <MrCurious> for now, i have a 4gig CF spinning disk with a usb attachment
[01:44] <MrCurious> that will work for swap
[01:45] <MrCurious> hitachi 4g microdrive
[01:45] <persia> Depends on the disk.  Some of the early microdrives were *really* slow.
[01:45] <MrCurious> how about that instead. wee bit less expensive
[01:46] <persia> Oh, once Hitachi had the "microdrive" brand, most were fairly good.
[01:46] <MrCurious> thats the one i have
[01:47] <MrCurious> uave a virgin 11.04 image now
[01:48] <persia> And did you ever get the bluetooth dialog similar to the one I posted?
[01:49] <MrCurious> just getting ready to try the image
[01:49] <MrCurious> had to burn it first
[01:50] <MrCurious> seems like the ubuntu shutdown from the upper right ui turned into a logoff user
[01:50] <MrCurious> had to logback in, get shell and shutdown manually
[01:52] <MrCurious> persia: are you on a pandaboard
[01:52] <MrCurious> and seeing bluetooth options?
[01:57] <persia> My panda is currently headless.
[01:58] <persia> I did see bluetooth on it back when it was connected to KVM
[01:58] <persia> I didn't test it, as I thought there was no antenna (failed to see the obvious antenna on the board)
[02:11] <MrCurious> i didnt see it. had to ask
[03:13] <MrCurious> persia: i have reinstalled a fresh 11.04, and i get no such options in my bluetooth menu :(
[03:29] <MrCurious> nope. no bt menu like the help pages infer. guess there is a issue with pandaboard
[07:29] <ppisati> morning
[07:50] <MrCurious> sigh, ubuntu cant find the package ubuntu-omap4-extras
[07:56] <MrCurious> ah hah! http://omappedia.org/wiki/Ubuntu_PPA
[11:37] <ogra_> janimo, are you already working on lightspark ?
[11:37] <ogra_> woglinde seems to have probs building it
[11:38] <janimo> ogra_, yes, I am looking at it on and off but did not build on ARM yet. I'll have a look
[11:38] <janimo> I just know it takes a lot of time to build
[11:38] <ogra_> yes, and takes a lot of ram too apparently
[11:38] <janimo> ogra_, btw I put two merge request related to the SD alignment BP
[11:39] <woglinde> janimo you need a machine with 1 gig
[11:39] <janimo> woglinde, ok I have a Panda
[11:39] <janimo> with 1G
[11:39] <woglinde> the amf3_parser file needs it
[11:39] <ogra_> woglinde, cant be since it built on the buildds
[11:39] <ogra_> unless thats something very new
[11:39] <woglinde> the ac100 with 512 and swap isnt working
[11:39] <woglinde> I gave up after 1 1/2 hours
[11:39] <ogra_> the babbage boards we use as buildds are
[11:39] <woglinde> compiling this file
[11:40] <ogra_> woglinde, try booting with nosmp ;)
[11:40] <woglinde> ogra its not compiled with -j
[11:40] <woglinde> 2
[11:40] <woglinde> its a boost or gcc error
[11:40] <ogra_> no, but memory management in kernel is different
[11:41] <ogra_> all i know is that it builds fine on the build machines
[11:41] <ogra_> and they only have 512M
[11:41] <janimo> woglinde, I'll do a build on oneiric - that is our target now
[11:41] <ogra_> but they are also UP machines
[11:41] <woglinde> janimo I tried with latest boost
[11:41] <woglinde> still the same problem
[11:42] <woglinde> you need to add armel in the control file
[11:42] <ogra_> shouldnt be needed in ubuntu
[11:42] <woglinde> but I think you are clever enough to find it our yourself
[11:42] <ogra_> i thing that was already patched
[11:42] <ogra_> *think
[11:42] <woglinde> I tried latest bazaar
[11:42] <woglinde> and its really only the amf3_parser
[11:42] <woglinde> all other files compiling
[11:43] <ogra_> you should have tried the latest packaging branch
[11:43] <woglinde> I wanted 0.4.8
[11:43] <woglinde> *g*
[11:44] <ogra_> you should have tried the latest packaging branch with a new upstream tarball :)
[11:44] <woglinde> ogra I doubt it changed something on the amf3_parser
[11:44] <ogra_> https://code.launchpad.net/ubuntu/natty/+source/lightspark is the most recent packaging branch
[11:45] <woglinde> 0.4.6.1
[11:45] <woglinde> to old
[11:45] <ogra_> woglinde, no, but you dont need to care about hacking the control file etc
[11:45] <ogra_> ??
[11:45] <ogra_> dch -i will make it 0.4.8
[11:45] <janimo> woglinde, the AMF parser was just rewritten yesterday upstream :)
[11:46] <woglinde> ogra why care=
[11:46] <woglinde> janimo lol
[11:46] <woglinde> okay
[11:46] <ogra_> you get the tarball, unpack it, cd into  the dir, bzr branch the debian dir, type dch -i and fire off a build
[11:46] <woglinde> I will take look
[11:46] <janimo> woglinde, but we are only packaging git master and ,ater for oneiric
[11:46] <woglinde> why I am always to early
[11:46] <janimo> via debian sync most likely
[11:47] <janimo> woglinde, but good that you reminded me, I'll do a git master build on ARM to see if anything broke lately
[11:50] <woglinde> hm I will try it too
[11:51] <woglinde> looks like the rewrite dont will fail
[11:55] <janimo> woglinde, are you trying to run latestt lightspark on natty?
[12:06] <woglinde> janimo yes
[12:06] <janimo> woglinde, it may be the case that even x86 fails to build on natty
[12:07] <janimo> did not check recently
[12:07] <woglinde> janimo as I said it was only the amf3 parser
[12:07] <woglinde> all other files compiled
[12:07] <woglinde> so its only linking left
[12:07] <janimo> ok
[12:07] <woglinde> but I will see it in a few minutes
[12:08] <woglinde> I will try it against the boost libs from oneiric
[12:15] <woglinde> so now lets see whats happen
[12:18] <ndec> lool: hi. is there any tool that i can use to parse a 'local PPA' and process the associate data e.g. list of packages (src, bin), dependencies, versions, .... ideally I think I am looking for a parse of files Packages and Sources...
[12:18] <woglinde> ndec look into apt-get code?
[12:20] <ogra_> ndec, grep-dctrl
[12:20] <ndec> woglinde: thx ;-) i was looking at a tool more 'ready to use'...
[12:20] <ogra_> with the Packages.gz file in /var/cache/apt
[12:22] <lool> ndec: Yes, launchpadlib
[12:23] <lool> ndec: http://paste.ubuntu.com/619829/ list-ppa-dsc.py
[12:23] <ogra_> yeah, lp-lib for remote stuff ...
[12:24] <ndec> lool: ogra_: thx! it looks like grep-dctrl might be want i need... i will dig into this.
[12:25] <lool> ndec: BTW I got the script from a Launchpad developer, it's not my writing
[12:25] <ogra_> you just dont want to be blamed for bugs ... :P
[12:41] <woglinde> *sigh*
[12:43] <janimo> woglinde, FWIW I successfully built LS HEAD on ARM/Oneiric without issues
[12:43] <woglinde> janimo I am fighting with scripting/abc.cpp
[12:44] <woglinde> maybee I should switch to a usbdisk
[12:45] <woglinde> instead of the sdcard
[12:45] <janimo> woglinde, most definitely
[12:45] <woglinde> but all other files compiles
[12:45] <janimo> It did not even occur to me you use SD
[12:45] <woglinde> I have enough
[12:45] <janimo> enough if one large file needs swapping
[12:46] <janimo> if SD is used that is becoming very slow
[12:46] <woglinde> yes
[12:46] <woglinde> I know
[12:46] <woglinde> ;)
[12:46] <janimo> I gave up on SD cards except for testing our images
[12:47] <janimo> and for boot partition
[12:58] <hrw> good move
[12:58] <woglinde> so now lets see with external harddisk
[13:41] <woglinde> its linking
[15:56] <rsalveti> In 5 min we'll start the linaro public plan review
[15:56] <rsalveti> https://wiki.linaro.org/Cycles/1111/PublicPlanReview
[15:56] <rsalveti> today presenting the Android and Dev Platform teams
[15:56] <rsalveti> Dev Platform is the one also working with Ubuntu on ARM
[15:56] <rsalveti> so folks here can probably be interested in hearing it
[16:32] <MrCurious> once one installs the omap4 add ons, is there a step after that to get them working ? (sound, bluetooth)
[17:39] <ppisati> rsalveti: do you know what it takes to get a linux-linaro-2.x kernel work with an ubuntu userland?
[17:40] <rsalveti> ppisati: should work just fine, we have the packages for that available at the repo, but if you want to grab from sources, just use the same config used by the packages
[17:40] <rsalveti> and should be fine
[17:40] <ppisati> rsalveti: uh... i'll try again, but it hanged at boot
[17:40] <rsalveti> ppisati: which kernel?
[17:40] <rsalveti> could be that the kernel is broken also ;-)
[17:40] <rsalveti> if you got 39
[17:41] <ppisati> i tried 39 for sure
[17:41] <ppisati> don't remember if i tried .38 too
[17:41] <ppisati> anyway, i'll do that
[17:41] <ppisati> and i'll use the .config from linux-linaro-natty
[18:01] <MrCurious_> does anyone here have a pandaboard with latest ubuntu, working sound, and a bluetooth menu that has more than just on/off?  If so, can I discuss the install procedure with you to work out what i missed?
[18:04] <gildean> MrCurious_: just the same conversation as minutes before, rsalveti said that those can be found as readymade packages at the repo
[18:05] <gildean> someone with an irc-shell should make a public log
[18:06] <gildean> i don't have enough diskspace on salaliitto.com to do that, as i already log more than one big channel
[18:06] <GrueMaster> MrCurious_: There is a known issue with audio and a workaround.  See bug 746023 comment 45.
[18:06] <ubot2> Launchpad bug 746023 in alsa-utils "No sound on omap4" [High,In progress] https://launchpad.net/bugs/746023
[18:07] <GrueMaster> I will be testing bluetooth with a BT keyboard here shortly.  Just finally got one in.
[18:19] <MrCurious_> gruemaster: can you ping me when you do that, i cant work out how to get my bluetooth to scan for devices, or be findable by another computer. i have installed the omap4 ubuntu add-ons, but still, it doesn't work like it appears in the help pages
[18:20] <GrueMaster> Ok.  Just imaged my new 16G class 10 SD so I can kill two birds as it were.  :P
[18:21] <MrCurious_> i got significantly better performance by moving root to a USB drive
[18:21] <GrueMaster> Well, duh.  :P
[18:21] <MrCurious_> and the SD's stopped getting corrupted
[18:21] <MrCurious_> i have weak sd's
[18:21] <GrueMaster> SD is horribly slow on every system I have seen (not just panda).
[18:22] <MrCurious_> my robot design depends on being able to do bluetooth serial ports.
[18:25] <GrueMaster> Just curious, but what are you using for a controller?
[18:27] <MrCurious_> you mean as the main computer, or to control the motors/servo's
[18:27] <GrueMaster> Motor controls.
[18:27] <MrCurious_> to control the motors, the plan is to use bluetooth modules + atmega328 + 754410 + some passives
[18:28] <MrCurious_> that way i can easily pair the subsystems with other pieces, like a lego brick approach, but wireless for all but power
[18:29] <GrueMaster> Do you have a link to a supplier or are you building this out of components & making your own boards?
[18:31] <MrCurious_> designing my own board
[18:31] <GrueMaster> ah.
[18:31] <MrCurious_> but i can send you a link for the $10 serial bluetooth modules if you want
[18:33] <GrueMaster> I have a ProXR 410 serial relay from http://controlanything.com that I plan on using for test automation.
[18:33] <GrueMaster> Having "fun" relearning how to program the serial port in C, especially since they only have examples in VB6 and .net.
[18:45] <MrCurious_> grue: http://www.satistronics.com/serial-port-bluetooth-module-masterslave-hc05_p2863.html 3.3v ttl serial port, any speed. very easy to configure and work with
[18:45] <MrCurious_> documentation is only slightly errored. just ignore everything above the command set, and you will be fine
[18:46] <GrueMaster> Cool
[18:49] <GrueMaster> Heh.  FAQ on their website:  Can I trust Satistronics?
[18:53] <MrCurious_> i tried a look alike module from elsewhere, and it was locked into 9600 8n1
[18:53] <MrCurious_> and a lame name
[18:53] <MrCurious_> but the satistronics ones are completely unlicked
[18:55] <GrueMaster> unlicked?  Reminds me of my test lab back at Intel.  We put "Do not lick" stickers on our high output powersupplies to appease the safety managers.
[18:56] <MrCurious_> un locked
[18:56] <MrCurious_> sorry
[18:56] <MrCurious_> heh
[18:57] <GrueMaster> Heh, I understood what you meant.  The typo just triggered a flashback.
[18:59] <GrueMaster> Ok, install went semi-smooth on my class 10.  oem-config restarted once but kicked through on second retry.  Not sure why, but I have seen that issue sporadically.
[19:03] <MrCurious_> my class 10, 16g 20m/s SD corrupts every install.
[19:05] <GrueMaster> Very odd.  Have you been able to get any logs from this?
[19:08] <MrCurious_> i just see write errors, then it remounts ro
[19:08] <MrCurious_> i believe it to be a bad sd, or that the SD timings are not compatible with the pandaboard
[19:09] <GrueMaster> You could try flashing the image to it then resizing the partition manually (if you have a linux desktop/laptop).
[19:12] <GrueMaster> Hmmm.  Massive disk i/o waits just running update manager.
[19:21] <MrCurious_> i can live my life happy believing that one SD card is evil
[19:22] <MrCurious_> i am more interested in working out how to verify i have all the omap4 proprietary drivers installed correctly
[19:22] <GrueMaster> Getting there.  :P
[20:25] <GrueMaster> MrCurious_: I seem to remember something about bluetooth support being added in the kernel after Natty release.  I'll check with the kernel guy in the am (he's in Italy).
[20:26] <GrueMaster> rsalveti: Does that sound right?  BT in kernel update?
[20:27] <rsalveti> it is in, but userspace doesn't support it properly
[20:27] <rsalveti> you still need to do some hacks to make it work
[20:27] <rsalveti> from what I heard this should be fixed with 39, but probably not for natty :-(
[20:28] <GrueMaster> Do we have steps for natty?
[20:28] <rsalveti> think so, is the same instructions I gave you while testing before the release, let me try to find it
[20:30] <rsalveti> http://paste.ubuntu.com/603343/
[20:30] <rsalveti> guess that's it
[20:30] <rsalveti> GrueMaster: ^
[20:30] <GrueMaster> Yep, looking.
[20:32] <MrCurious_> gruemaster: thanks!
[20:35] <sveinse> Does anyone have debs of a newer qemu (which doesn't fail on rootstock with "qemu: uncaught target signal 11 (Segmentation fault) - core dumped"
[20:35] <sveinse> The version in natty crashes this way while trying to compute the SSH RSA keys
[20:41] <GrueMaster> MrCurious_: Bug 789095 has more info.
[20:41] <ubot2> Launchpad bug 789095 in linux-linaro-omap "Bluetooth does not work on PandaBoard" [Undecided,Confirmed] https://launchpad.net/bugs/789095
[20:43] <MrCurious_> ty
[20:44] <MrCurious_> this is good info
[20:46] <MrCurious_> i think if i canreplicate what warmcat (last comment) did i will be happy
[20:47] <sveinse> Is it possible that bug 674146 is the same as I'm seeing in qemu/rootstock?
[20:47] <ubot2> Launchpad bug 674146 in gcc-4.5 "dpkg segfaults during debootstrap on natty armel" [High,Fix released] https://launchpad.net/bugs/674146
[20:51] <sveinse> Anyone? Sorry for my persistence. I'm a bit in a drag here, as our build server is down due to this bug. Some pointers to what to do would be nice, thanks.
[21:51] <sveinse> I'm trying to run chroot dir /bin/bash into a armel rootfs, but I'm getting chroot: failed to run command `/bin/bash': No such file or directory
[21:51] <sveinse> This being on a server, it is possible that either the server or the FS stops this operation. How can I check that?
[22:23] <gildean> sveinse: chrooting to armel-ubuntu from different arch?
[22:24] <sveinse> gildean: yes from i386
[22:25] <sveinse> I'm strace'ing it, and I see the chroot() then chdir("/"), but the following execve("/bin/bash",...) fails
[22:33] <sveinse> I'm comparing the strace against a strace from my amd64 desktop where everything works, and I see minimal differences, and just the execve() call which fails
[22:56] <sveinse> Anyone knows if server apps (like apparmor) could interfer with qemu and binfmt?
[22:58] <sveinse> I don't understand why my chroot fails. The error is foo, and strace doesn't reveal anything.
[23:11] <sveinse> I think I'm going crazy. This, of course, being the day when the armel build server stops working combined with the exceptional occasion with almost no response in the forum. Tough luck...
[23:36] <persia> sveinse, Just to verify, you're using qemu-debootstrap to create the chroot (or some mechanism that depends upon this)?
[23:37] <sveinse> yes, i believe rootstock is using qemu-debootstrap, doesn't it?
[23:39] <sveinse> I'm suspecting that the reason rootstock/qemu crashes, and the fact that I cant run chroot into a armel rootfs, might be related
[23:40] <persia> I think it tries to do the same sort of thing with it's own (separate) debootstrap wrapper, but it's close enough.
[23:41] <sveinse> The weird part is that I don't trigger the crash on my desktop machine (which is amd64)
[23:41] <persia> Have you tried just executing a static armel binary?
[23:42] <sveinse> where can I get one?
[23:42] <persia> That would help differentiate whether qemu is completely not working or whether it's something more complicated.
[23:43] <sveinse> I wonder if there are any files within a normal ubuntu-minimal installation which are static
[23:43] <persia> I usually just create a quick hello.c and gcc -static it :)
[23:43] <sveinse> hold on
[23:46] <sveinse> ok, I'm able to run the static app from my bash shell (proving the binfmt+qemu works)
[23:49] <sveinse> Interesting:  "./hello" works (hello is armel static). But running (as root) "chroot . /hello" does not work!
[23:50] <cipher> "does not work" isn't very descriptive
[23:50] <sveinse> chroot: failed to run command `/hello': No such file or directory
[23:51] <cipher> try chroot . ./hello
[23:51] <sveinse> same result
[23:51] <cipher> file ./hello
[23:52] <sveinse> ./hello: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, for GNU/Linux 2.6.16, not stripped
[23:52] <cipher> it was exact same error for chroot . ./hello?
[23:53] <persia> Aha!  That sounds like /usr/bin/qemu-arm-static doesn't exist in the chroot
[23:53] <sveinse> interesting
[23:53] <persia> This needs to be manually copied in, unfortunately, and updates are ugly.
[23:53] <sveinse> yeah, let me try
[23:54] <persia> Essentially, binfmt-misc is calling /usr/bin/qemu-arm-static when attempting to run the foreign binary.
[23:54] <sveinse> voila!
[23:54] <persia> And if there's not an extra copy in the chroot (which wouldn't be created by debootstrap normally), then it fails with "command not found"
[23:55] <persia> Excellent.  So, I think this probably represents a bug in rootstock: it probably needs to be ported to use qemu-debootstrap from qemu-user-static rather than whatever it's doing now.
[23:55] <sveinse> This means that a rootstock image is not purely without clutter or change from the host pc which created it?
[23:55] <persia> From the dependencies, it looks like it still expects the deprecated qemu-kvm-extras-static
[23:56] <sveinse> If it puts /usr/bin/qemu-arm-static in it, I mean
[23:56] <persia> rootstock may have some provision to delete this file, but I doubt it's clean.
[23:56] <sveinse> At least it sheds light on a large mystery for my part
[23:56] <persia> rootstock is a fun toy, but I wouldn't use it for any production purpose.
[23:58] <sveinse> I know you/ubuntu doesnt use it any more, but what other options are there to putting together a rootfs image?
[23:58] <sveinse> Because using it for production is exactly what it's used for today... :o
[23:59] <persia> Lots of folk here use it, but it was never used for the Ubuntu images.
[23:59] <persia> Do you have access to an armel development host?  Could you build images there?
[23:59] <sveinse> Takes a list of packages and outputs a rootfs. Nice.
[23:59] <persia> Not cross-building is the first step to reliability.