User1: User2 http://support.google.com/chromeos/bin/answer.py?hl=en&answer=1080595   how to recover chromebook
User2: User1 as I said earlier, I can recover it
User2: also, I suspect that won't work on my laptop
User3: good morning
User2: morning.
User2: http://pastebin.mozilla.org/2001455
User2: that is from my pandaboard, I just tried to upgrade a fresh install to 12.10, and got a black screen.
User2: I also got this in dmesg
User2: [    7.703308] init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory
User2: ok, I have the sd card plugged into my laptop, and I want to enable the ssh server... is there an easy way to do this?
User4: User2 You're missing libdrm-omap1, looks like.
User4: User2 Also, it's not so much "enabling" the ssh server as installing the package, which you'd need to do either on an ARM machine, or with emulation.
User2: qemu-system-arm does not have an omap4 option from what i can tell
User2: i'm actually kind of surprised there isn't a pandaboard option
User4: I'm not.
User4: Emulating a Panda isn't something qemu upstream would care to do, and TI didn't see the value in writing a board-specific emulator (most vendors don't)
User4: Anyhow, I didn't mean full system emulation.
User4: qemu-user-static would be fine.
User4: Mount your SD card to somewhere (we'll say /mnt), apt-get install qemu-user-static && cp /usr/bin/qemu-arm-static /mnt/usr/bin && chroot /mnt su -
User4: Presto, you're in your ARM system as a chroot.
User4: apt-get install ssh libdrm-omap1
User4: apt-get install pvr-omap4 # if you wanted some non-free 3D action.
User4: Which is probably necessary, if you're running Ubuntu/Unity.
User2: for whatever reason, ssh seems to already be installed
User2: but it isn't starting
User2: and it isn't bringing up the network
User5: User4 can you share /var/log/Xorg.0.log from panda with opengles support?
User4: User2 If your network is wireless-only, that could explain it.
User4: User5 My Panda has no X right now.
User2: User4 nope, eth0 is the pandaboard's onboard connection
User4: User2 Oh, curious.  Maybe it hates you/
User5: User4 ok
User2: sweet, I can ssh into my pandaboard again
User2: ok, I know I did this on my last install; what do I need to run in order to get a non-hf library installed?
User2: or better yet, what on earth is it called?
User2: i'm searching for multilib
User2: but that is giving man irrelevant results
User4: User2 Depends on which non-hf library you need.
User4: User2 If it's just libc6 (and a gcc that can build sf binaries), there are multilib versions.
User2: looks like the answer was
User2: dpkg --add-architecture armel
User2: which is surprisingly hard to find via google
User4: User2 If it's more comprehensive, you want multiarch (dpkg --add-architecture armel && apt-get update && apt-get install libfoo1:armel)
User4: That said, I wouldn't rely on armhf/armel multiarch going forward, since we've dropped armel in raring...
User4: What are you doing that *needs* soft-float libraries?
User2: y'all are making my life really hard, you know that?
User2: i'm testing fennec, which is supposed to run on android which is armel.
User4: .. unless it's newer Android, then it's not. :P
User2: how does that work from a packages' point of view?
User4: That said, fennec could be rebuilt...
User2: do they need to upload two .apks, one for armel, one for armhf?
User4: I have no idea how Android is handling the sf/hf transition.
User4: Then again, most apps aren't C binaries, so the point is moot for them.
User2: you know what version they made the transition in?
User4: It could also be that this is all a bit different with bionic, I have no idea.
User4: I just know they were doing the transition (or maybe had done so).
User6: Does anyone know if Network Manager regularely scans for a list of available networks in precise? We're having some problems with communication locking up for 2-3 seconds and wondering if this could be related to nm scanning the networks
User4: User2 It's possible they haven't actually made the switch yet for bionic-based systems (ie: Android), though they definitely did for ChromeOS.
User4: Confusing world.
User4: User2 Still, for an open-source project like fennec, surely you'd want to build it for Ubuntu to run it on Ubuntu anyway?
User4: User2 Since an Android build wants bionic, which means running shims and other horrors.
User2: User4 we don't build for ubuntu, ubuntu does :-p
User4: s/Ubuntu/glibc/? :P
User2: bionic?
 * mjrosenb googles
User4: bionic is Android's libc.
User4: It's not even remotely compatible with glibc.
User2: FUN.
User4: There is a project that produces a disturbing translation shim that allows glibc systems to run bionic binaries with an LD_PRELOAD.
User4: It's not pleasant.
User4: I don't recommend it for a project you actually have the source to.
User2: we already have NSPR
User4: User2 Err, NSPR doens't give you portability at runtime, kristen89@example.net.
User4: A bionic-using nspr won't do you a lick of good on a glibc system.
User2: yeah, but I don't think it has ever been our goal to have a single executable that runs on all arches.
User4: (bionic is vaguely BSD-derived, think about how well it wouldn't work to take a binary from FreeBSD and run it on Linux, even if you had the kernel syscalls emulated)
User4: No, it shouldn't be your goal to run a binary on multiple arches.  I agree.
User4: Hence why I'm suggesting you might just want to rebuild it.
User4: Cause libc6:armel still won't be bionic, so multiarch isn't going to help you here.
User2: http://pastebin.mozilla.org/2001793
User2: ahh. yes, but I like testing in an environment that is as close to what we'll be seeing in a shipping product as possible
User2: the js engine doesn't really have to deal with libc that much
User2: but it does need to deal with the likes of math.sin math.atan2
User4: The wrapper lies, it's linux-ti-omap4-tools-3.5.0-215
User2: where the armel/armhf distinction comes into play
User4: Oh, wait.  You're doing this to test for Android?
User2: yup.
User4: Then you should build an Android chroot.
User2: that sounds neat.
User4: Testing against glibc won't really tell you anything.
User2: as previously stated, I have basically 0 interaction with glibc.
User2: but I *am* intrigued by the concept of an android chroot.
User4: Well, you must have some, or would wouldn't care about ABI.
User4: Since if you were talking to the kernel directly, it's meaningless.
User2: Error: sys_perf_event_open() syscall returned with 19 (No such device).  /bin/dmesg may provide additional information.
User2: :(
User4: I didn't say perf would work, just pointed at the package that ships it!
User4: (Sorry, I haven't slept in a while, that's about as helpful as I can be right now)
User2: as previously stated, there are math functions that are called that I need to be able to call correctly.
User4: I should probably nap instead of being flip on IRC.
User2: not a problem, I may have to build my own kernel, wouldn't be the first time
User4: Well, you'll also want an Android kernel for your test environment, so yeah.
User4: Though, Linaro provides Panda Android builds that might be up your alley.
User2: well, I like using linux because it has a sane debugging strategy
User7: the disturbing shim thing is called libhybris: https://github.com/stskeeps/libhybris
User7: currently does libgles and stuff, but should be adabtible for any libraries
User2: right now, getting perf to work is a higher priority.
User2: was the source for linux-image-3.5.0-215-omap4 provided by linaro?
User8: Morning folks sfeole are you around?
User9: User8 i am
User8: User9 I was told you are the one to speak to about finding current docs on how the Ubuntu fastboot image is created for flashing to the nexus 7
User9: User8 hm, give me a few
User8: Sure sfeole - I'll be lurking for the better part of today.
User2: huh, was CONFIG_PERF_COUNTERS removed from the kernel?
User2: unrelatedly, is there a way to un-brick a chromebook that does not involve re-initializing all of chrome's state?
User2: ok, I have built my own kernel, but I am not sure how to get a bootable uimage out of it
User2: oh, make uImage, evidently
User10: User2 https://code.launchpad.net/~ubuntu-nexus7/ubuntu-nexus7/build_script
User10: look at the abootimg bits
User10: line 71
User10: User2 http://paste.ubuntu.com/1445967/
User2: make uimage sounds much easier
User10: User2 likely, but just givin' ya whats easiest for me :)
User2: well, thank you for that
User2: hopefully, i'll remember that if i'm ever in a situation where that is more aprpriate than make uImage.
User2: tar -xzvf $TARBALL $packaged_path/initrd.img-$kver $packaged_path/vmlinuz-$kver
User2: that makes it look like the initrd is a tarball?
User2: oh no
User2: i am a fool $TARBALL is a tarball.  it has two files in it
User2: User10 you happen to know anything about perf?
User11: did password/user in raring for nexus 7 changed? It says "Login incorrect" when I try ubuntu/ubuntu
User10: User11 should boot to oem-config
User10: User11 choose your own user/pass
User11: yeah, it does not start GUI, it just stays in tty1, so I am trying to find out what is wrong
User10: first boot is a bit slow
User11: yeah, I know, but not 5-10 minutes slow
User10: i sometimes see a few sec delay from tty1 to oem-config on vt7 (i assume)
User10: yeah not that slow
User10: oem/oem should get you in
User10: but it should launch oem-config
User11: well, it does not, so I am trying to log in to tty1 to find what went wrong
User11: (it might not be [probably is not] ubuntu issue though)
User11: well, I guess I'll just chroot into it from recovery and change the password/create my own user
User2: ok, different approach, does anyone have perf working on an omap4 running 12.10?
User11: oh, yeah, I guess that read-only root is not such a great idea :)
User2: relatedly, I followed the directions at http://seabright.co.nz/2011/03/29/building-the-ubuntu-pandaboard-kernel/ -- how do I build an initrd now?
User10: User11 how did you flash the device
User10: User11 make sure cmdline is tty0 if you came from quantal
User11: it's okay now
User10: ah ok
User11: onboard still does not show up in oem-config for me, though
User10: fresh flash?
User11: yeah, basically
User10: i flashed friday on 8gb model, no issues w/ onboard
User10: User2 played w/ perf on x86 not on arm, but should be in linux-tools binary wise
User10: linux-tools-nexus7 iirc
User11: all the ext4 partitions on my nexus7 has the same UUID, what the hell Oo
User2: User10 http://pastebin.mozilla.org/2002447
User10: User2 looks like we need
User10: Fatal: No CONFIG_PERF_EVENTS=y kernel support configured?
User10: User2 mind opening a bug against lp/ubuntu-nexus7 ?
User2: User10 this is on a pandaboard.
User2: and;
User2: mrosenberg@panda:~$ grep CONFIG_PERF_EVENTS /boot/config-3.5.0-215-omap4
User2: CONFIG_PERF_EVENTS=y
User2: so unless /boot/config-`uname -r` is out of sync with the kernel, I should have that.
User10: ah i thought you were talking n7
User10: will have to look at omap4
User2: I realize that the perf event system is basically totally hosed on omap4
User2: but I just need the timer-based perf working
User11: User10 could you please check which version of onboard is installed on your n7?
User2: so nobody uses a pandaboard in here/
User12: lol
User12: How do i install the nightlies?
User12: i downloaded them in .gz format or whatever and every tool i have to open a .gz shows a .raw file
User12: i dunno how to get an .img from them
User10: User12 https://launchpad.net/~ubuntu-nexus7/+archive/ubuntu-nexus7-installer
User10: User11 gimme a sec, charging atm
User11: it looks like something crashes, because a while after I tap into the textfield, the windows lose the decorations (the title bar)
User10: User11 want an older nightly?
User11: hmm, yeah, I suppose I could try that
User10: i need to let this guy charge up for a bit
User2: speaking of which, does the upgrade process know how to upgrade the kernel on a chromebook
User10: User2 doubtful
User10: at least I dont think so
User2: and if not, I assume that I need to do it myself
User10: i could be wrong
User2: is there a time of the week when people knowledgable about the pandaboard or chromebook would be online/
User10: User2 january 2nd? ;)
User10: User2 not sure, no cb experience here myself
User10: User11 http://people.canonical.com/~vanhoof/tassadar/UbuntuNexus7.tar.gz
User10: User11 from thursday'ish last week
User11: thanks
User11: nah, does the exact same thing :(
User10: :\
User10: i get through just fine
 * vanhoof wtfs
User11: it is probably my fault, I am dual-booting it and probably got something wrong
User11: seems kinda weird though, it is doing exactly the same thing as it did when it didn't work for anyone
User2: checking whether the chosen combination of compiler flags (-march=armv6 -mfpu=vfp -mfloat-abi=hard) works... configure: error: no
User2: :-/
User4: User2 Do I want to know why you're targetting v6?
User2: User4 because i have a raspberry pi.
User4: (Though, that combination should work, in theory, it's what Raspbian uses)
User4: I'd assume the configure test itself is doing something silly.
User4: Like possibly tacking on a -mfpu=neon or something? :P
User2: configure:5745:1: sorry, unimplemented: Thumb-1 hard-float VFP ABI
User4: User2 Give it a -marm
User2: i already tried that, it produced executables that don't run :/
User4: User2 Though, if you're cross-compiling from Ubuntu, you may find that you'll also end up compiling in static bits from our toolchain, which are v7/thumb-2, and it will all fail to run on the Pi anyway.
User4: User2 Jinx. :P
User2: ugh.. -march=armv6 should mean 'don't do that'
User4: "Don't link the static bits that you need to run the binary" is a tall order.
User4: libgcc_s, crt*.o, etc.
User2: i mean, how does a gcc that can target both x86 and x64 handle that?
User4: Well, crt*.o should be pure ARMv5 or so, but you get my point.
User4: biarch GCC relies on having two copies of everything.
User4: As does our biarch armel/armhf GCC.
User4: But ours was never designed to target older CPUs.
User4: Just as a biarch Ubuntu x86 GCC can
User4: 't actually build binaries for i386.
User4: Well, probably not.  Again, it depends on if any of the static bits use [456]86 instructions.
User4: Which, in the ARM case, they do use v7 bits.
User2: this is a toolchain acquired from emdebian from well before ubuntu properly supported cross compilation
User4: An armhf one though, right?
User4: Debian's armhf has always been armv7-a/thumb-2
User2: armel, with -mfloat-abi=hard
User4: As has nearly everyone's, to be fair.  Raspbian is one of the only strange attempts to do armhf on v6.
User4: User2 Err, what?  "armel with -mfloat-abi=hard" *is* armhf.
User2: what is the difference/
User2: *difference?
User4: Or do you mean this is an ancient compiler that was only armel?  If so, you're producing binaries that don't run for other reasons.
User4: Either because the static bits aren't armhf or because you're cooking in the wrong path to the PI.
User4: What's the failure mode when you try to run the binaries?
User2: this compiler has been producing binaries that have worked on armv7el and armv7hf systems for quite some time.
User2: sigill
User2: looks like it is getting confused about thumb mode.
User4: Or that it's compiling in some v7 bits.
User2: oh hey
User2: i am using the armhf compiler
User4: This is a well-known problem among Pi people trying to cross from Ubuntu.
User2: sounds reasonable
User4: You can manually copy various static bits like libgcc from your Raspbian system to your cross environment.
User4: There's also a Raspbian cross toolchain.
User4: That targets the right thing by default.
User2: yeah, as hacked as this system is, i don't like having programs installed that aren't managed by my package manager
User2: i'll have to find some way of making a .deb out of the cross toolchain
User13: does anyone here have any input on the Nexus 7 install wiki page ?
ubuntu-arm
Ubuntu IRC