[02:51] <ipl31_> anyone know if any of the -M options for qemu-system-arm support more than 1 nic?
[04:00] <AmEv> Hmmm... I wonder if it's the command line messing things up...
[07:26] <dholbach> good morning
[09:04] <sim590> hey, I have deleted a tar file and I want to recover it. I'm using scalpel. I need to specefy the header of a ".tar" file, but I have no idea what it is..
[09:10] <sim590> anyone knows how to discover the header of a file like a tar file
[09:16] <infinity> sim590: "discover the header of a file"?
[09:16] <infinity> sim590: What are you actually trying to accomplish?
[09:18] <sim590> I want to find my deleted tar file
[09:18] <sim590> on my disk
[09:19] <sim590> I have to add something like this in the configuration file of foremost
[09:19] <sim590>  pdf     y       5000000 %PDF-  %EOF
[09:19] <sim590> where "pdf" is the extension
[09:19] <sim590> "y" is for case sensitive
[09:20] <sim590> and I also need to specefy the header
[09:20] <sim590> but I don't know what the *"!(/&*$ it is :D
[09:21] <sim590> I want to do this for "tar" file
[09:21] <infinity> # POSIX tar archives
[09:21] <infinity> 257     string          ustar\0         POSIX tar archive
[09:21] <infinity> !:mime  application/x-tar # encoding: posix
[09:21] <infinity> 257     string          ustar\040\040\0 GNU tar archive
[09:21] <infinity> !:mime  application/x-tar # encoding: gnu
[09:21] <ubot2`> infinity: I am only a bot, please don't think I'm intelligent :)
[09:21] <ubot2`> infinity: I am only a bot, please don't think I'm intelligent :)
[09:21] <infinity> That's what file(1) knows about tar files.
[09:22] <sim590> man file
[09:22] <sim590> ok
[09:22] <infinity> sim590: apt-get source file && cd file-* and browse around magic/Magdir to see what it knows about these things.
[09:22] <infinity> (The tar stuff is in "archive")
[09:23] <sim590> ok.. I'll try that thanks.
[09:48] <sim590> infinity: I've not found my file yet, but I understand now what you wrote after looking the files you told me. But how the hell did you think about that? Did you just know that it was in these files? :p
[09:50] <infinity> I did, yes.
[09:52] <sim590> ok lol.
[11:31] <sim590> #quit
[12:37] <therve> hi! I have some questions about 12.10 on pandaboard, can someone help?
[12:47] <ogra_> therve, how would we know if you dont ask your question ?
[12:48] <therve> one would wonder
[12:48] <therve> I've installed from the sd card on an external SD via USB
[12:49] <therve> can I make the USB bootable to remove the install sd card?
[12:50] <ogra_> nope
[12:51] <ogra_> you could install to the SD itself (at least in raring, not sure if all the fixes were backported to 12.10)
[12:51] <ogra_> but the panda cant boot off anything else than SD or a special USB OTG setup that requuires a second PC
[12:52] <therve> well I don't want to boot via USB
[12:52] <ogra_> thats a HW limitation
[12:52] <therve> I have a SD card plugged in a USB card reader
 can I make the USB bootable to remove the install sd card?
[12:52] <ogra_> oh, ok
[12:52] <therve> sorry I meant the SD used in USB right now
[12:53] <ogra_> well, if you have the exact same partitioning for the vfat partition, you chouls be able to just dd the contents from one card to another and swap them
[12:53] <ogra_> s/chouls/should/
[12:54]  * ogra_ glares at his fingers
[12:54] <therve> hum
[12:54] <ogra_> the panda needs a vfat partition in the beginning of the card and that needs to have all the bootloader stuff in it
[12:55] <therve> ok I see
[12:55] <therve> sounds like something doable, maybe by installing on a SD with the boot vfat ready
[12:56] <ogra_> right
[12:56] <therve> cool, thanks
[12:57] <therve> the other question I had was about graphic support/video playback
[12:57] <therve> is there anything I can check to make sure I have the proper drivers enabled?
[12:57] <ogra_> duplicate the SD (write the image to both cards) then only delete the second partition but leave the first one intact ... after install dd the partition from one card to the other
[12:57] <ogra_> with 12.10 the drivers are oreinstalled and used from the beginning
[12:57] <ogra_> *preinstalled
[12:58] <therve> I'm asking because it feels pretty slow, so I was wondering if that was expected
[13:52] <sim590> Anyone has made the sound work on the TF101 under ubuntu with lilstevie's kernel? I've red a wiki speaking about this, but I don't know how alsamixer works.. I don't know where to find the "playback" and DMIC option
[13:53] <sim590> http://forum.xda-developers.com/showthread.php?p=25608362&highlight=sound#post25608362 -> A guy says he makes the sound work, but the playback thing.. Idk
[14:28] <janimo> orientation and backlight testing app for the nexus7 http://people.canonical.com/~jani/a
[14:29] <janimo> to be ran with DISPLAY=:0 set if via ssh and with sudo
[14:29] <janimo> it's a static executable , the golang source is https://code.launchpad.net/~jani/+junk/nexus
[14:34] <ogra_> janimo, wow, without kernel tweaks ?!?
[14:34] <janimo> ogra_, well, apparently everything was there already
[14:34] <ogra_> yay
[14:34] <janimo> just hidden in sysfs
[14:34] <ogra_> i wish the backlight control would be there too
[14:35] <ogra_> the device is so bright it hurts my eyes after a few hours
[14:35] <janimo> ogra_, well this app has backlight control
[14:35] <ogra_> oh, wow
[14:35] <janimo> bt probably needs some tweaking
[14:35] <ogra_> ah, i see the code, yeah
[14:35] <janimo> I did not see it workin gonly starting with andorid 4.2.1
[14:36] <janimo> and seeing it works there it made sense to look harder at where it is exposed
[14:36] <janimo> for a while I thought it simply is not working at all
[14:36] <janimo> but I need to ask around how to best integrate these in some daemons and control center
[14:36] <ogra_> i looked at the sysfs stuff for quite a while already, but only played with echoing stuff into the respective files
[14:36] <ogra_> which always failed with write errors
[14:36] <janimo> to have nice UI for it and non extra daemon running
[14:37] <janimo> right, some files are read only or einval
[14:37] <ogra_> yeah
[14:37] <janimo> birghtness is the only knob that should work
[14:37] <janimo> but it's enough for our purpose
[14:38] <janimo> the x input bugs are still annoying though, I think I'll have another go at those
[14:39] <janimo> after a rotation or two or a few minutes taps are still not working
[14:39] <ogra_> woah
[14:39] <ogra_> the UI is really slow
[14:40] <ogra_> (in redrawing the content rotated)
[14:40] <ogra_> janimo, you rock !
[14:40] <ogra_> we should package that as a daemon with proper upstart file etc
[14:40] <janimo> ogra yes it redraws slowly if the axis changes
[14:41] <janimo> but if it's a 180 degree rotation it is really quick :)
[14:41] <ogra_> i blame compiz
[14:41] <ogra_> heh
[14:41] <janimo> I guess copying is much easier if you do not have different line lengths and can do rectangle copies
[14:42] <janimo> as contiguous pixels in one case are still contiguous in 180 rotation, but not with 90 or 270
[14:42] <ogra_> funny that onboard fully wortks while rotated input doesnt in the rest of the UI
[14:42] <janimo> ogra_, I'll mail ubuntu-devel for some input. While a daemon is fine I'd still rahter add this functionality to some existing plumbing daemons
[14:43] <ogra_> not even the restore button inside firefox responds in portrait
[14:43] <janimo> otherwise it is yet another 1-2MB hit for our footprint
[14:43] <ogra_> ugh
[14:43] <janimo> I did not test apps too much TBH
[14:43] <ogra_> well, i doubt it is the app
[14:44] <ogra_> but onboard works flawless, i can type in a terminal no matter what the rotation is
[14:44] <janimo> just saw that cursor is where it should be, but may it be some apps get confused if screen size or orientation changes?
[14:44] <ogra_> launcher and FF dont take any taps
[14:44] <ogra_> they do if rotated back to landscape
[14:44] <janimo> maybe those that do their own drawing as oppposed to using a GUI toolkit get confused when screen rotates, no idea
[14:45] <janimo> hmm, maybe we coudl try xrandr + firefox on x86
[14:45] <ogra_> oh, it was only the recovery button that didnt work
[14:45] <ogra_> i can scroll with grab n drag in FF and click links
[14:46] <ogra_> hmm
[14:46] <ogra_> i can klick links but they dont get executed
[14:46] <ogra_> (but undelined)
[14:47] <ogra_> i guess i'll need to test that with a mouse plugged in so the pointer gets visible
[14:48] <ogra_> janimo, why does the footprint raise so much ? GO ?
[14:49] <janimo> well GO - at least the official compiler - creates static executables and includes the Go runtime in them
[14:49] <janimo> so they are standalone
[14:49] <janimo> that makes the executable about 1.2 M, but runtime footprint I guess is also due to runtime bookkeeping
[14:50] <janimo> it's not as much as it would be in python but C (or even dash) may be leaner
[14:50] <ogra_> heh, lux sensor seems to work fine too ...
[14:50] <ogra_> i can use a torch and point at the camera area and the display reacts
[14:50] <janimo> the formula is ad-hoc, a better fit is likely possible
[14:50] <ogra_> but its slow
[14:50] <janimo> yes, I used my desklamp for testing, went up to 40000 lux
[14:51] <janimo> passing -v shows lux and accel reading values
[14:51] <ogra_> ah, nice
[14:51] <janimo> slow in reacting to it?
[14:51] <ogra_> yes
[14:51] <janimo> well both accel and light are poll loops with 1s delays
[14:51] <ogra_> my torch is a tiny LED one pretty focused
[14:51] <ogra_> ah, thats it then
[14:52] <ogra_> 1s seems to match what i see
[14:52] <ogra_> i wonder if we could make it trigger uevents so you dont need to poll
[14:52] <janimo> there may be interrupt based interfaces for these sensors, but maybe not via sysfs
[14:52] <ogra_> but that would indeed be kernel side
[14:53] <ogra_> and probably still cause latency
[14:53] <janimo> right, eventually having triggers is better than waking up for no reason periodically
[14:53] <janimo> but, on android actually the lag is a few seconds
[14:53] <ogra_> but i think thats for 13.10 ;)
[14:53] <janimo> so  I guess it adapts once it decides this is really ambient light change and not a transitory flashlight
[14:53] <ogra_> i'd set it to 0.5s though, will likely feel a lot smoother
[14:54] <janimo> maybe eve 5 seconds lag on android
[14:54] <janimo> a bit confusing for test purposes but for real use cases it may be better
[14:54] <ogra_> wow, 5s is long
[14:54] <janimo> especially since light adjusts very seldom and incrementally
[14:54] <janimo> well, if you read and the sun slowly sets you don't really care about a few seconds
[14:55] <ogra_> indeed
[14:55] <janimo> I think are tests are artificial
[14:55] <janimo> our tests that is
[14:55] <Tassadar> well, on Android 4.1, when the backlight is turned to maximum because of ambient light and then you put it to dark place, the brightness never goes down again
[14:55] <Tassadar> so you can't really do worse than that)
[14:55] <janimo> Tassadar, I know my nexus did not seem to change backlight at all until this week
[14:56] <janimo> not sure if due to 4.2.1 (which I had before), a clean reinstall, or just me being more determined to wait for the change
[15:07] <Tassadar> just in case you posted it because you want someone to test it - it works for me too, but that touchscreen input in portrait orientation is really weird)
[15:07] <ogra_> well, onboard works just fine, thats the puzzling bit
[15:08] <Tassadar> you can also drag icons in dash
[15:08] <ogra_> right
[15:08] <ogra_> and i can scroll firefox pages with drag'n grab enabled
[15:09] <ogra_> links get marked if i tap them but never get executed
[15:09] <Tassadar> I can open terminal menu (the one on top bar) if I keep the finger on screen
[15:11] <ogra_> heh, xchat copes fine though
[15:11] <Tassadar> kernel crashed when rotating the screen :x
[15:12] <ogra_> kernel ?
[15:12] <ogra_> how do you know ?
[15:12] <ogra_> did you get an oops ?
[15:12] <Tassadar> http://pastebin.com/AY6Cg9R6
[15:12] <Tassadar> it was after i managed to bug the touch input by clicking too fast
[15:13] <ogra_> that looks like cpufreq issue ...
[15:15] <ogra_> nothing in my dmesg, looks all fine
[15:16] <Tassadar> maybe just some rare crash
[15:16] <Tassadar> dunno which kernel does Ubuntu use as base, but 4.2 kernel is not that stable even on Android
[16:42] <achiang> ogra_: can every Ubuntu package in 12.04 and beyond assume that NEON is supported in the hardware?
[16:43] <ogra_> achiang, nope, NEON is not allowed at build time at all, if a binary wants to use NEON it has to have runtime support
[16:43] <achiang> janimo: ^^
[16:44] <achiang> ogra_: interesting....
[16:44] <ogra_> by default all packages in the archive need to be non-NEON
[16:44] <janimo> achiang, what ogra said. Even if we do not have official images, people run Ubuntu on Tegra2 which has no neon
[16:44] <qengho> achiang: yo.
[16:45] <janimo> And ac100 actually had 12.04 images
[16:45] <achiang> qengho: hi, let me paste a bit of scrollback for you re: neon
[16:45] <ogra_> and as long as we potentially (or actively) support something like tegra2 or armadaxp it will have to stay that way
[16:45] <qengho> No neon.  Saw that.
[16:45] <janimo> ogra_, oh armadaxp too, I forgot
[16:45] <ogra_> well, NEON, but only at runtime :)
[16:45] <qengho> Got it.  Thanks!
[16:46] <achiang> qengho: is the chromium build FTBFS due to NEON?
[16:46] <ogra_> not sure which packages have actual code for this, Qt could be and possiblly pixman
[16:46] <janimo> Qt does indeed
[16:46] <ogra_> (if you want to look at code for runtime support)
[16:46] <achiang> ogra_: qengho is the chromium maintainer for ubuntu engineering, and he's trying to get something going for 12.04
[16:47] <qengho> 13.04 mostly, but anything I can.
[16:47] <achiang> qengho: are you seeing a NEON-related build failure?
[16:47] <janimo> achiang, chromium/v8 probably works without neon too but their build system is complicated so some flags may get set inconsitently
[16:47] <janimo> some with neon support some without
[16:47] <ogra_> qengho, did you talk to micahg already ? he used to do the chromium builds in the past
[16:48] <ogra_> probably something wheer exxperience can help ....
[16:48] <qengho> achiang: Yes.  janimo has it right.  It's mostly build flags.
[16:48] <janimo> I also had (scarring) chromium FTBFS experiences
[16:48] <qengho> ogra_: I did.
[16:49] <janimo> qengho, the only thing I remember is flags either not being passed correctly from debian/rules or build files needed patched to turn neon off
[16:50] <janimo> qengho, Launchpad may still preserve chromium changelog history and you could find neon FTBFS bugs there
[16:50] <janimo> it may be a recurring one due to dropped patches or changed upstream build system
[16:51] <qengho> It's changing upstream, AFAIK, janimo.
[16:51] <qengho> Okay, thanks all.
[16:55] <qengho> Er, it looks like I might have to write a function that does what I want. What's the best way to test for NEON support programatically at runtime?
[16:56]  * qengho hopes it's not "parse /proc/cpuinfo".
[16:58] <qengho> Oh good. Assembly.
[17:00] <ogra_> iirc it was somewhere in /proc/self
[17:01] <ogra_>  /proc/self/auxv ? not sure
[17:03] <ogra_> actually i'm pretty sure libjpeg-turbo has the code for runtime switching, just grep for auxv in the source
[17:03] <morphis> ogra_: thanks for your response about gstreamer/ti/omap some days ago
[17:04] <ogra_> welcome
[17:05] <morphis> :)
[17:11] <morphis> ogra_: seems like I have to investigate a little bit more
[17:12] <ogra_> well, the guys that used to maintain the TI PPA packages are still around in #pandaboard (some of them at least) they can probably tell you what happens to the PPA stuff and if anyone goes on maintaining it
[17:15] <morphis> ogra_: good hint, will join there and ask
[17:40] <qengho> does someone have a device that lacks NEON support?  I want to test something.  http://pastebin.ubuntu.com/1542106/
[17:40] <qengho> ogra_, achiang, ^
[17:41] <Tassadar> I have raspberry sitting in here, if that's enough
[17:41] <ogra_> not near me today, sorry
[17:41] <qengho> $ make foo; ./foo
[17:41] <qengho> Tassadar: Ooo, that just might!
[17:41] <ogra_> i will have my ac100 (tegra2) around tomorrow again though
[17:42] <Tassadar> okay
[17:42] <ogra_> what OS is on there ?
[17:42] <Tassadar> that debian wheezy they have on their download page, raspbian or whatever
[17:42] <Tassadar> you only need to test if it correctly detects the CPU, right?
[17:43] <Tassadar> it should be enough
[17:43]  * ogra_ isnt sure if a test on an armv6 debian rebuild is actually reliable
[17:43] <qengho> Tassadar: yes, just the CPU.
[17:43] <ogra_> your kernel definitely needs hwcap support though
[17:45] <ogra_> (or was that libc ... its so long ago i had to tinker with it)
[17:45] <Tassadar> compiled okay, says "
[17:45] <Tassadar> pi@saffron ~ $ ./test
[17:45] <Tassadar> this CPU has no NEON support.
[17:45] <Tassadar> "
[17:45] <qengho> Tassadar: Thanks.
[17:47] <achiang> qengho: i don't have a device like that near me, unfortunately
[17:51] <Tassadar> My LG P500 (~same cpu as raspberry) with debian in chroot also says "no neon support"
[17:57] <ogra_> for a positive match,, i get proper output on the chromebook
[17:57] <ogra_> ogra@chromebook:~$ ./foo
[17:57] <ogra_> this CPU has NEON support.
[17:57] <qengho> ogra_: ah, thanks.  Good data all.  Thanks.
[18:23] <vhadil> hy friend
[18:24] <vhadil> besides cmus what applications you install