[05:10] <vipzrx> hello
[05:14] <vipzrx> anybody here?
[05:25] <vipzrx> [   32.533843] omapdss DISPC error: SYNC_LOST on channel tv, restarting the output with video overlays disabled
[05:25] <vipzrx> [   32.627380] omapdss DISPC error: timeout waiting for digit out to stop
[07:48] <dholbach> good morning
[08:09] <mjrosenb> morning all.
[08:11] <mjrosenb> I have the new(ish) ARM chromebook, i'd like to put the 13.04 prerelease  on there, is this remotely possible yet?
[08:26] <fabo> mjrosenb: there's several way to do that. the easiest (imo) is to use http://chromeos-cr48.blogspot.fi/ then enable https://launchpad.net/~chromebook-arm/+archive/ppa and dist-upgrade to 13.04.
[08:28] <fabo> ikepanhc: arndale kernel oops is fixed. you can pick up latest arndale kernel.
[08:28] <mjrosenb> fabo: so I've used the first part before
[08:28] <mjrosenb> fabo: and upgrading has bricked it before
[08:28] <mjrosenb> fabo: although I was attempting to upgrade to 12.10
[08:29] <mjrosenb> fabo: I take it this doesn't brick the machine with high probability.?
[08:29] <ikepanhc> fabo: many thanks, the fix on linux-linaro-tracking.git tree?
[08:30] <fabo> ikepanhc: yes
[08:31] <fabo> mjrosenb: it can't brick it. you're using a separate sdcard.
[08:32] <mjrosenb> fabo: at the time the shell script installed to the main sd card
[08:32] <mjrosenb> and it certainly rendered ubuntu unbootable.
[08:33] <fabo> mjrosenb: though it could be tricky because of an issue with plymouth. you shouldn't reboot in the process until you get 13.04 dist-upgrade done
[08:34] <mjrosenb> fabo: yeah, I think my pandaboard ran into that one recently.
[08:34] <mjrosenb> fabo: is it possible to just disable plymouth, and use the textual boot?
[08:34] <ikepanhc> fabo: thanks again. I see it and I will give it a try.
[08:34] <fabo> mjrosenb: if you have an usb ethernet dongle, you're safe as you could still restore graphics driver if it goes wrong with plymouth.
[08:35] <fabo> mjrosenb: it doesn't brick, it's just that you're stuck at plymouth stage and X doesn't start
[08:37] <fabo> ikepanhc: you're welcome. it works like a charm. now I'm looking for a guid on arndale to resolve random mac address issue.
[08:37] <fabo> ikepanhc: is that the reason you use an usb ethernet dongle on arndale?
[08:40] <ikepanhc> fabo: I have no idea, I am far away from the board and it is setup in a lab with remote power control and serial.
[08:40] <ikepanhc> I can check with my colleague why they choose a usb-ethernet dongle
[08:41] <fabo> ikepanhc: arndale has onboard ethernet (asix driver) but the driver assign random mac address because the chip doesn't have a valid one
[08:41] <mjrosenb> fabo: thanks, I'll try it out in the next few hours hopefully.
[08:42] <fabo> ikepanhc: if you use dhcpd, dhcpd lease will be full at some point...
[08:42] <ikepanhc> fabo: the ethernet is asix indeed, its on usb bus right?
[08:43] <fabo> ikepanhc: I used an udev rule to work around but assign a specific address
[08:43] <fabo> ikepanhc: yes
[08:43] <ikepanhc> fabo: I can see it on lsusb
[08:43] <ikepanhc> fabo: oh, then its not dongle, what we use is on board ethernet
[08:44] <fabo> ikepanhc: it's problematic if you have several boards in the lab... so I'm looking for a guid
[08:44] <ikepanhc> fabo: that's alright, we assign static ip for them
[08:44] <fabo> ok
[08:45] <fabo> mjrosenb: feel free to ping, I'm around
[09:27] <diwic> ogra, hi, tried flashing my Nexus7 using the GUI tool to have another stab at the audio, but it hung on "Erasing boot partition"
[09:30]  * diwic cancels and tries again
[09:32] <diwic> ok, worked after restarting the bootloader
[09:54] <nils_> diwic, I had problems with the setup of ubuntu after starting the nexus installer
[09:54] <nils_> the window of the language selection was to far at the right side and it was difficult to continue.
[09:55] <nils_> can you confirm that?
[10:10] <diwic> nils_, I wonder if I got the latest image, I thought I did, but it looks old
[10:20] <nils_> uname -a shows: 3.1.10-9-nexus7 ... Thu Jan 31 12:23:44
[10:21] <diwic> nils_, yeah, mine showed 3.1.10-7 something, so I'm reflashing it now
[10:39] <diwic> nils_, hrm, it still says 3.1.10-7-nexus7 after a reflash! I guess I have to download the image manually or something
[10:40] <diwic> ...or why not download the latest ubuntu-nexus7-installer first, argh
[10:40] <nils_> good idea
[11:15] <mjrosenb> fabo: ok, I tried that script for an external drive
[11:15] <mjrosenb> fabo: it did not work, it looks like it made a filesystem that was too big for the partition that it made
[11:15] <mjrosenb> then failed to do anything after that
[11:16] <mjrosenb> and just rebooted the laptop instead.
[11:19] <fabo> mjrosenb: external drive or sdcard? the script expect a sdcard
[11:20] <mjrosenb> sdcard
[11:20] <mjrosenb> sorry,
[11:20] <ogra> diwic, if your PC is on raring, usb-creator will offer you the installation, no need for the extra installer
[11:21] <ogra> diwic, and i would just do a manual install, it's just three four commands to flash manually (see the wiki)
[11:21] <ogra> -three
[11:22] <ogra> nils_, btw, did you notice that we have usbnet on by default now ?
[11:37] <nils_> ogra, yes I was excited. I am studying about networking, ifconfig and so forth. I am already pinging a lot back and forth.
[11:37] <ogra> thanks again for the suggestion :)
[11:38] <nils_> I first tried out to set up the network manually with ifconfig but the two systems forgot their ip-addresses after a while.
[11:39] <nils_> then I took the easy way and configured manually ip-addresses through the gnome interface.
[11:39] <nils_> now it's stable.
[11:39] <nils_> next what I have to understand is routing ;-)
[11:42] <nils_> ogra, I tried to understand where I can see the changes of the build.
[11:42] <mjrosenb> fabo: any idea?
[11:42] <nils_> I thought I should find the changes here: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-nexus7.git;a=summary
[11:42] <mosasaur> For an ARMv7 chroot, should I use an armhf or an armel core rootfs?
[11:43] <ogra> in /usr/chare/doc/<packagename>/changelog.gz if you have the package installed, and on launchpad in the changelog indeed
[11:43] <ogra> */usr/share
[11:47] <nils_> sorry ;-) where on launchpad? I tried to search for the latest changes here: https://launchpad.net/~ubuntu-nexus7
[11:48] <diwic> hrm, now I got the latest image (I hope), but the "who are you?" section in the installer does not accept input
[11:49] <diwic> tried both the onboard and keyboard over OTG cable
[11:49] <ogra> diwic, reboot, there is a race between onboard and compiz, it doesnt seem to happen after a reboot
[11:49] <ogra> that and the corrupt wallpaper are known issues
[11:50]  * diwic hopes that doesn't corrupt the sound
[11:51] <ogra> does pulse have a new bling-test module that looks if your desktop is beautiful ? :)
[11:52] <diwic> ogra, I was referring to the reboot :-)
[11:52] <ogra> ah
[11:52] <diwic> ogra, did you see my latest comment in bug 1068804 ?
[11:52] <ubot2> Launchpad bug 1068804 in ubuntu-nexus7 "sound only works after suspend/resume cycle" [Critical,In progress] https://launchpad.net/bugs/1068804
[11:53] <ogra> did you see mine ?
[11:53] <diwic> ogra, ok, now I saw it
[11:55] <diwic> nils_, yeah, the "system configuration" screen is far to the right after a reboot, but it wasn't before the reboot
[11:55] <diwic> nils_, and if you rotate it to "portrait" there is no "system configuration" screen at all
[11:58] <nils_> diwic, I had the same. Then I managed to show Onboard and could press Enter in order to proceed.
[11:58] <nils_> This for a few more screens and after the installation everything fine.
[12:00] <ogra> file a bug please, i know xnox loves them :P
[12:00] <diwic> nils_, hrm, I have a keyboard connected to it, but pressing Enter does nothing
[12:02] <diwic> ogra, btw, does the installer run things differently than the install? I see the installer has a sound indicator but no device in sound settings
[12:02] <ogra> the installer uns as root
[12:02] <ogra> *runs
[12:03] <ogra> i think pulse or teh indicator have some prevention builtin
[12:03] <ogra> so you cant use it as root
[12:04] <diwic> ok
[12:04] <diwic> anyway, this stuff isn't working; I can't proceed in the installer
[12:04] <ogra> (i would actually like to hide that stuff from the panel ....
[12:04] <ogra> i diont see a reason to play with sound settings during install (if sound works at least)
[12:05] <ogra> diwic, try without kbd attached
[12:05] <ogra> i know it works after a reboot for me ... and i stopped using mice or kbds a while ago on the nexus
[12:06] <diwic> ogra, right, but I can't reboot it, because the "ok" for the reboot is off the screen too
[12:06] <ogra> heh
[12:06] <ogra> just hold down the power button
[12:06] <ogra> it auto-reboots
[12:07] <diwic> ok
[12:07] <nils_> ogra, found it now: https://launchpad.net/ubuntu/raring/+source/linux-nexus7
[12:08] <ogra> right, clicking the version numbers gets you the changelog details on that page
[12:09] <ogra> https://launchpad.net/ubuntu/+source/linux-nexus7/3.1.10-9.24
[12:09] <ogra> thats the change that added g_composite
[12:09] <diwic> nils_, ogra ok, now I was able to complete the dialogs in portrait mode
[12:10] <ogra> great
[12:10] <ogra> we should probably disable auto-rotation during install
[12:10] <ogra> and force it to portrait
[12:10] <ogra> or simply switch back to metacity
[12:10] <ogra> which didnt have any of these probs
[12:11] <ogra> though thats xnox' decision
[12:19] <diwic> ogra, sound works after reboot if removing /etc/init/alsa-store.conf and /var/lib/alsa/asound.state
[12:19] <ogra> funny
[12:19] <diwic> ogra, would be nice if you or someone else could verify
[12:19] <ogra> i triesd the latter several times
[12:20] <diwic> you need to remove both
[12:21] <ogra> rebooting
[12:21] <ogra> we shouldnt need to remove the state file if we override the upstart job from the beggingin
[12:22] <ogra> -in
[12:22] <diwic> ogra, correct
[12:22] <ogra> though i /me hugs diwic
[12:22] <ogra> err
[12:22] <ogra> - though i indeed :)
[12:22] <ogra> works fine !
[12:23] <diwic> ogra, TheMuso deserves a hug too
[12:23]  * ogra hugs TheMuso 
[12:23] <ogra> twice !
[12:23] <ogra> so what if i copy the upstart job back ?
[12:24] <ogra> would that work ?
[12:24] <ogra> i assume we still want to store the volume and states  on shutdown
[12:25]  * ogra does it and reboots
[12:33] <diwic> ogra, so assuming this actually is the culprit, is there an easy way to remove /etc/init/alsa-store.conf from the nexus7 image without removing it from the entire distro?
[12:33] <ogra> sure
[12:34] <ogra> its a simple .override file i need to put in place
[12:34] <ogra> though it would still be good to know why using a state file doesnt work (and fix the root cause)
[12:34] <ogra> btw, copying back the upstart job leaves me without sound again
[12:35] <diwic> ogra, and that creates the asound.state file so you must again remove both to have sound back I assume
[12:35] <ogra> well, bot upstart jobs then
[12:35] <ogra> *both
[12:36] <ogra> but that means that volume settings wont persist over reboots
[12:36] <diwic> ogra, no I don't think so - PulseAudio should have its own store/restore system
[12:36] <ogra> ah, k
[12:38] <diwic> ogra, that said, because we always run both, I guess we haven't tested PulseAudio alone much
[12:55] <ogra> diwic, workaround uploaded
[12:57] <diwic> ogra, thanks, could you write that in the bug and point to the workaround?=
[12:58] <ogra> the bug should auto-close
[12:58] <diwic> ogra, let's hope this is the one :-)
[12:58] <ogra> oh, wait, needs a task for the defaults package
[12:58] <diwic> we've had too many red herrings for this bug already
[12:58] <ogra> well, it works just fine here
[12:58] <ogra> just the muted state is left for me
[13:30] <diwic> ogra, did you confirm it was still working even though you override *both* alsa-store and alsa-restore?
[13:31] <diwic> ogra, alsa-restore falls back to some default values if it finds no asound.state
[13:31] <ogra> yes, indeed, i tend to test uploads before i send them upwards :)
[13:31] <ogra> it isnt executed at all
[13:32] <ogra> thanks to the override file
[13:33] <diwic> ogra, there are two different calls to "alsactl restore", one in alsa-restore.conf and one in /lib/udev/rules.d/90-alsa-restore.conf
[13:33] <ogra> ah, well, the udev rule is indeed still executed, i didnt do anything to prevent that
[13:33] <diwic> ogra, which one that gets executed, if I understand things correctly, depend on what comes up first of file system and sound device, or something like that
[13:34] <ogra> in any case it works here atm
[13:34] <diwic> ogra, so, what is the reason for overriding alsa-restore.conf too?
[13:34] <ogra> if i hear complaints from users i will look again
[13:35] <ogra> well, i didnt think about the udev rule, but essentially to prevent users that actually have the state file from having it restored
[13:35] <ogra> and instead leave the initilization to the kernel
[13:35] <diwic> ogra, hmm ok
[13:35] <ogra> though if the udev rule kicks in thats indeed moot
[13:36] <diwic> ogra, it just feels inconsistent to disable one but not the other
[13:36] <ogra> it seemed like a better way than having to do postinst hackery to remove the state file
[14:38] <diwic> janimo, ogra https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068804/comments/31
[14:38] <ubot2> Ubuntu bug 1068804 in ubuntu-nexus7 "sound only works after suspend/resume cycle" [Critical,In progress]
[14:39] <ogra> diwic, will test later today (havent got the latest kernel source here atm)
[14:40] <diwic> ogra, thanks
[14:41] <diwic> ogra, I did my own test: I took the asound.state file, removed the "Register Control" entry, and let alsa-restore run as normal after a reboot, and audio still worked
[14:41] <diwic> ogra, so I'm hopeful
[14:41] <ogra> awesome !
[16:05] <xnox> ogra: inhibitting autorotation seems fine.
[16:05] <xnox> is the portrait mode intended as the "default" while configuring these days?
[16:06] <xnox> (we used to be landscape only, but that's before autorotation worked)
[16:06] <ogra> xnox, yeah
[16:06] <ogra> the bootloader sets portrait as default, we dropped all hacks that change this
[16:07] <xnox> ogra: so how does one "inhibit" autorotation? stop the daemon?
[16:07] <ogra> xnox, i'm really wondering if we shouldnt go back to metacity though
[16:07] <ogra> you can stop the upstart job, but make sure to start it again when stopping ubiquity
[16:08] <ogra> though better talk to janimo, not sure if we will keep the upstart bits in the long run
[16:08] <ogra> he ports everything over to gnome-settings-daemon
[16:09] <ogra> (so we'll probably have a dconf key thats better suited for the task)
[16:11] <xnox> let me upload with more compiz plugins enabled and then I'll maybe will have an opinion about it.
[16:12] <xnox> (e.g. keep compiz vs switch back to metacity)
[16:12] <ogra> yeah
[16:13] <ogra> the focus thing is really bad
[16:13] <ogra> and that a simple reboot fixes it is irritating
[18:01] <scottb> lool, ping
[18:03] <lool> scottb: in a call, but please leave a msg
[18:21] <mjrosenb> fabo: still around?
[18:36] <mjrosenb> alternately, has anyone succeeded in installing ubuntu on the sdcard of a chromebook?
[18:36] <mjrosenb> it seems to die after partitioning because it made the filesystem too large
[18:55] <janimo> xnox, good point. We probably need some user visible settings to disable rotation
[18:56] <ogra> janimo, i think there is a setting in gsettings already for the xrandr module
[18:56] <ogra> (for g-s-d)
[18:57] <ogra> hmm, or was that just for the touchscreen input rotation ... i forgot
[19:28] <janimo> ogra, maybe if you disable the g-s-d orientation plugin entirely
[19:29] <janimo> but that's not enough as it needs a restart to take effect
[19:29] <janimo> I think a toggle in the current Display Panel would be most appropriate
[19:29] <ogra> yeah
[20:59] <drizzy> howdy everyone
[21:08] <TheMuso> diwic: Good find.
[21:08] <TheMuso> I suspected there might be something along those lines as well.