[09:36] <hrw> mjrosenb: building kernel for chromebook is not rocket science
[10:16] <hrw> https://launchpad.net/chromebook-arm - for Chromebook users/hackers
[10:18] <tassadar_> does anyone know if there is a package made from http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-nexus7.git;a=summary ?
[10:42] <infinity> tassadar_: Yes.
[10:42] <infinity> tassadar_: https://launchpad.net/ubuntu/+source/linux-nexus7
[10:45] <tassadar_> hmm, packages.ubuntu.com did not find that one
[10:46] <tassadar_> I suppose that is the kernel in raring image, and will not get into 12.10..?
[10:46] <infinity> Right.
[10:46] <infinity> No reason to backport it.
[10:46] <infinity> This is all for development purposes, after all.
[10:46] <tassadar_> yeah, that means I'll have to use the raring image for multi-boot
[10:47] <infinity> And packages.ubuntu.com only indexes amd64 and i386, which is why you wouldn't find it, being an armhf-only kernel.
[11:06] <tassadar_> haaa
[11:06] <tassadar_> I rebooted to recovery from kernelspace
[11:06] <tassadar_> good :)
[11:07] <asiekierka> ugh, my tf101 seems to be a paperweight now
[11:07] <asiekierka> can't get into APX, read -71 everywhere in dmesg
[11:19] <RaYmAn> it's usually a problem with cable and/or host usb port
[11:19] <RaYmAn> it's rather..sensitive.
[11:20] <RaYmAn> APX mode itself can't really break, so it has to be a hardware issue. (also, is it nvflash or wheelie failing?)
[11:21] <asiekierka> RaYmAn: nvflash
[11:21] <asiekierka> i have a B50
[11:21] <asiekierka> as I said, I believe it's because it ran out of battery power during nvflashing
[11:21] <asiekierka> in the middle of it, installing the large system image
[11:21] <RaYmAn> that doesn't matter
[11:21] <asiekierka> it SHOULD technically run the bootloader, though
[11:21] <asiekierka> that's odd
[11:21] <RaYmAn> APX mode is in bootrom
[11:21] <RaYmAn> you can't break it
[11:21] <asiekierka> i know
[11:21] <asiekierka> APX mode boots up but it quickly shuts down
[11:21] <asiekierka> as i said, seems it doesn't want to charge
[11:22] <asiekierka> thus connecting it to USB 3.0 may help
[11:22] <asiekierka> then i can both charge and APX
[11:22] <RaYmAn> not really
[11:22] <RaYmAn> it's a bit of a myth
[11:22] <RaYmAn> the charger switches to 15v to charge properly, which usb 3.0 certainly doesn't provide :P
[11:22] <asiekierka> so what should I do?
[11:22] <asiekierka> by charge i mean just enough to boot the thing up
[11:22] <asiekierka> so i can get into APX and make it run reasonably
[11:23] <asiekierka> the dock does charge, sadly i can't tell if the tablet does
[11:23] <asiekierka> all i can tell is that it partially boots into APX
[11:23] <RaYmAn> let it fully run out of battery
[11:23] <asiekierka> already done
[11:23] <asiekierka> at least twice
[11:23] <RaYmAn> then plug it into the charger and let it charge for a day or so
[11:23] <asiekierka> left it by itself for a week
[11:23] <asiekierka> oh, that
[11:23] <asiekierka> hmm
[11:23] <asiekierka> okay
[11:23] <asiekierka> http://paste.ubuntu.com/1401724/
[11:23] <asiekierka> here's what Linux says
[11:24] <RaYmAn> probably battery issue I guess
[11:24] <asiekierka> i can tell
[11:24] <asiekierka> should i charge the dock as well?
[11:24] <RaYmAn> doesn't really matter - you shouldn't nvflash through dock anyways
[11:24] <asiekierka> the same happens when i nvflash dockless
[11:25] <RaYmAn> it refuses to enter nvflash and stuff if battery is too low, even if it's charging
[11:25] <asiekierka> yes, i noticed
[11:25] <asiekierka> what i can tell from the logs is:
[11:25] <asiekierka> - the PC detects a new USB device
[11:26] <asiekierka> - the tablet either refuses to boot up properly or runs out of the minimal amount of battery
[11:26] <asiekierka> - the PC does that again
[11:26] <asiekierka> - same happens
[11:26] <asiekierka> - then the tablet stops accepting any data from the PC
[11:26] <RaYmAn> did you leave it charging for a long time? and by long I do mean like 24 hours at least (in real charger)
[11:26] <asiekierka> IIRC yes
[11:26] <asiekierka> as i said, the main problem is that it ran out of battery in the middle of APXing
[11:27] <RaYmAn> yeah, that's not really relevant
[11:27] <asiekierka> okay, now that's odd
[11:27] <asiekierka> it stopped accepting APX the moment that happened, even if i tried to recharge
[11:27] <asiekierka> i wonder if the battery's just dead
[11:27] <RaYmAn> APX mode doesn't care about the eMMC at all
[11:28] <RaYmAn> so you can half-flash anything you want and it'll still be fixable
[11:28] <RaYmAn> so I'd say either cable or battery
[11:28] <RaYmAn> It's probably just a freak coincidence
[12:40] <davecheney> i hate sd cards
[12:40] <davecheney> lucky(~/Downloads) % sudo dd if=boot.img-serial of=/dev/mmcblk0
[12:40] <davecheney> 31457792 bytes (31 MB) copied, 10.9471 s, 2.9 MB/s
[12:40] <davecheney> lucky(~/Downloads) % sudo dd if=boot.img-serial of=/dev/mmcblk0
[12:40] <davecheney> 31457792 bytes (31 MB) copied, 12.6877 s, 2.5 MB/s
[12:40] <davecheney> top one is a $5 no name sdcard I got at the supermarket
[12:41] <davecheney> bottom one is a top spec fujistu class 10
[12:41] <RaYmAn> try with a more suitable blocksize
[12:42] <davecheney> does dd really default to 1 ?
[12:42] <davecheney> this is for a pandaboard
[12:42] <davecheney> which has a really slow sd interface
[12:43] <RaYmAn> no,but that didn't mean the blocksize it uses it's well suited for sd
[12:43] <davecheney> bs=1m, 31457792 bytes (31 MB) copied, 0.023563 s, 1.3 GB/s
[12:43] <davecheney> somehow I don't think that is accurate
[12:43] <davecheney> gah
[12:43] <davecheney> too hot, too tired tonight
[12:45] <lilstevie> davecheney, it is rather warm here too
[12:45] <lilstevie> :/
[12:46] <tassadar_> winter's beginning here)
[12:46] <lilstevie> First day of summer here