=== sv is now known as discopig === chihchun is now known as chihchun_afk === _Lucretia__ is now known as _Lucretia_ === chihchun_afk is now known as chihchun [05:08] Snark: nothing works, 'ghjk' keys get up to 95°C, touchpad is 147° rotated and screen works in 320x180 resolution only. === optimusprimem is now known as optimus-afk [05:08] Snark: hdmi works only if keyboard is connected to usb3 port and SD slot works only on tuesdays [05:25] hrw: Speaking of. Can I get you to verify your alsa* SRUs so I can release them? Pretty please? [05:26] hrw: https://bugs.launchpad.net/chromebook-arm/+bug/1085392 [05:26] Launchpad bug 1085392 in Cross distro support for Samsung Chromebook (ARM based) "Merge Chromebook UCM profiles into ALSA packages" [Critical,Triaged] [05:47] hrw: hmmm... may I remind you that I own an AC100, where the latest kernel makes hdmi and sound work, but suspend+resume fails, while using an older kernel makes suspend+resume fail but not hdmi and sound [05:49] hrw: additionally, there *is* a page describing what works and what doesn't for ubuntu touch on the nexus 7 [05:49] so, I don't think my question is as laughable as you make it sound... [05:52] so, my question is: what part of the following list works when running ubuntu on the samsung chromebook (wifi, hdmi, bluetooth, suspend+resume)? [05:53] s/an older kernel makes suspend+resume fail but not hdmi and sound [05:53] /an older kernel makes suspend+resume fail but not hdmi and sound [05:53] rrraahhh... [05:54] I meant the older kernel had suspend+resume work, but didn't make it possible to use hdmi and sound [06:11] infinity: sorry, forgot totally [06:12] Snark: we use the same kernel source as chrome os doe [06:12] s [06:12] Snark: so what works under chromeos works under ubuntu. but we do not ship opengles stuff or hw accelerated codecs [06:16] maybe during saucy cycle it will change as I plan to build 3.8 or 3.10-rc kernels [06:47] Hi! [06:48] Is it to be expected that UbuntuArm 12.10 on BeagleBone Black only gives a handful of package updates (after apt-get update)? [06:58] How many were you hoping for? === doko_ is now known as doko [07:28] hrw good! [07:28] thanks [07:34] death to slow sd cards... [07:34] started debootstrap over hour ago [09:22] ogra_: I see that android-tools are now in main - nice [09:50] hrw: why is usb-storage a module in chromebook kernel? Makes testing kind of difficult [09:50] XorA: my mistake [09:50] XorA: open a bug please - otherwise no SRU can be done [09:51] hrw: oh its an official package now? [09:51] yes, it is [09:51] hrw: wont have time today Ill postit to do that tomorrow [09:51] XorA: no rush [09:51] * XorA has year end accounts to sort out + Linaro [10:10] infinity: rebooting chromebook to check after-reboot sound state [10:13] infinity: passed [10:15] hrw: Awesome. Can you do Q too, or shall we just fudge that based on the diffs being the same? :P [10:15] infinity: with my sd card it will take another few hours to populate rootfs [10:16] diffs are same and chromebook users are on 12.04 or 13.04 usually [10:16] hrw: Yeah, diffs being the same (just double-checked) is good enough for me. [10:17] infinity: I though that SRU bugs should be verified by !reporter [10:18] hrw: Nah, that's crazy talk. They should be verified by someone who knows how to verify them. [10:18] ;) [10:19] hrw: I'm happy with it being the reporter as long as it's obvious that they actually did so (which you clearly did), instead of them just lying to me to get their crap code in. :P [10:20] right [10:21] infinity: I hope that 3.10 will be able to work on chromebook - or 3.11 in worst case [10:25] Linux 3.11 for Workgroups will only work on 486s. [10:26] hehe [10:27] infinity: good that I still have Vortex86SX somewhere... [10:28] 486sx 300MHz noFPU [10:28] I might still have an AMD 5x86/133 in a closet. [10:29] From the unclever days when "5x86" meant "486DX compatible, but we gave it a higher number to sound impressive". [10:29] Amazing how my opinions of them flipped right around with the K7. [10:30] ;) [10:30] my first PC was AMD Duron 600MHz [10:30] Good little CPUs those. [10:30] worked fine as 850MHz after some pencil fun [10:30] I had a Duron 600 clocked at 900, if I recall. [10:31] mine was not stable at 900 [10:31] 850's close enough. [10:31] probably cooling needed update [10:31] Given they were, what, like 50 dollar parts at OEM wholesale cost? [10:31] no idea - cheap it was [10:31] and switch from 68040/40 to Duron/600 was huge [10:32] Hahaha. No shit. Amiga or Atari? [10:32] and 720x480x4(grey) -> 1024x768x16(color) [10:32] infinity: Amiga 1200 [10:32] infinity: my first Linux experience was on this hw. Check potato installation guide for Amiga ;D [10:33] I was still tracking music on my A1200 while playing video games on my K7 machines. [10:33] infinity: I sold a1200 to have money for pc [10:33] Speaks volumes to the quality of both the software and hardware in the Amiga world. [10:34] But, eventually, I got sick of rebooting it before laying down a track to avoid clock skew over time, and other such oddities, bit the bullet, and learned to use inferior PC tracking software. [10:34] motherboard, apollo 1240/40 (real 40MHz), 2x32MB simms, fastata controller [10:34] (And then, over time, the PC software got less shit) [10:34] vga mono with AGA was usable. but I would not go for >4 bit of grey (or colours) :d [10:35] All the cool kids had colour! [10:35] infinity: so I was not cool kid;) [10:35] Heck, I had color on my old 6809 machine. [10:35] That fancypants RGB monitor cost a fortune, if I recall. [10:35] infinity: atari 65xe with green monitor, then amiga600, then a1200 with same monitor. [10:36] then monitor died for 3rd time and I decided to buy vga mono instead of resurrection [10:36] Heh. [10:36] 720x480 27.5kHz 58.5Hz - no other vga monitor was able to sync it [10:36] Yeah, when my parents stopped being a source of cool tech, I was cheap about monitors too. [10:37] After I moved out, I had the same old 800x600 14 inch monitor until. Uhm. 2002? [10:38] When a friend forced me to buy a new monitor because he couldn't stand me using a 15yo CRT with brand new computers. [10:38] in 2000 I was more limited by 2MB ATI Mach64 graphic card then monitor. [10:38] And now I've just given up on the whole desktop thing and buy laptops, which come with "free" monitors, so yay. [10:38] few months later Matrox G400 arrived and situation changed [10:39] infinity: maybe one day I will find a use for laptop other then 'machine for use at conference' - then I will look at something fast [10:39] (Though my test bench does have a decent enough 24inch HDMI 1080p screen that mostly sits idle) [10:40] If my laptop didn't have the evil hybrid graphics setup of doom, I'd use it as a second display... [10:40] intelvidia? [10:41] Yeah. [10:41] I run it straight Intel to save battery life and my sanity. [10:41] But the displayport connector no workie unless you're in nvidia mode, or some such. [10:41] Silly setup. [10:41] you get what you paid or sth like that [10:42] There wasn't a pure Intel option on the laptop I wanted. Such is life. [10:42] External displays aren't important to me anyway. [10:42] infinity: which model you have? [10:42] T420s [10:43] And I should revise that. If I'd customised online, I think I could have gotten an Intel-only setup (maybe), but I was buying retail in HK. [10:43] (gtk-update-icon-cache-3.0:3644): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/arm-linux-gnueabihf/gdk-pixbuf- [10:43] 2.0/2.10.0/loaders.cache': No such file or directory [10:44] and 'gdk-pixbuf-query-loaders > /usr/lib/arm-linux-gnueabihf/gdk-pixbuf-2.0/2.10.0/loaders.cache' hint is useless as command is not present... [10:44] life. [10:52] hrw: did you cut off the USB part? [10:52] XorA: not yet but plan to === chihchun is now known as chihchun_afk [11:34] fun. linux-next on chromebook shuts it down during bootup [12:08] hrw: multitasking in action === sbrown is now known as blinky42 === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [21:09] hi there, I'm trying to recover android in my nexus 7 after an unsucessfull try for ubuntu-arm and it's talking so much time, I've looked at ps and it seems a have a 'D+' which stand for 'uninterruptible sleep', do any of you had any similar problem? [21:30] so, after rebooting with another kernel, and retrying the procedure, it agains hangs at $ fastboot -w update image.zip, this time however I could launch strace, and this is its output: http://paste.ubuntu.com/5649198/ after the last line, it just stay in the 'D+' state and it doesn't show more output [22:21] ok, I think I got it know, it seems like the usb subsystem is very delicate, this time I made sure the tablet didn't move even a milimeter and it worked