**** BEGIN LOGGING AT Thu Jan 24 02:59:58 2013 Jan 24 07:17:33 good morning Jan 24 09:51:52 janimo, heh, i have what i think is the worst workaround i ever found ... for the sound init Jan 24 09:52:14 an upstart job with: rtcwake -u -s 1 -m mem Jan 24 09:52:26 I am also looking into it Jan 24 09:52:31 costs 1sec boot time and makes the screen flash once during boot Jan 24 09:52:42 (its a 1sec suspend) Jan 24 09:52:42 and it works if I enable HDA_INTEL Jan 24 09:52:50 but volume if off on start Jan 24 09:53:02 I need to see how to turn that on by default on boot, Jan 24 09:53:05 that should be solvable by a ucm setup Jan 24 09:53:14 I tried amixer calls and to no avail Jan 24 09:53:19 only from control center Jan 24 09:53:42 but it looks like INTEL_HDA should be on (it is in Android) even if the hw does not seem to have HDMI connectors Jan 24 09:53:49 you need to unmute the left and right channel of the speaker control separately i think Jan 24 09:54:04 why did we switch it off again ? Jan 24 09:54:15 i remember diwic asked for it to be off Jan 24 09:54:20 right, I tried sudo amixer -c 1 cset numid=1,iface=MIXER,name='Speaker Playback Switch' 1,1 Jan 24 09:54:29 no idea, the whole ALSA stack confuses me Jan 24 09:54:49 what are controls and simple controls, are they both neede, is controls a superset? Jan 24 09:55:20 so many ways to set alsa (alsactl restore, amixer, alsamixer, control-center) Jan 24 09:55:35 the fact there are 140+ controls is of great help as well :) Jan 24 09:56:13 yeah, thats awesome, isnt it ? i bet you could turn the nx7 into a recording studio if you could attach the right peripherials :P Jan 24 09:56:51 no idea what those things do, or why are they all exposed. Jan 24 09:57:06 and I thought the ac100's sound options were complicated Jan 24 09:57:11 haha Jan 24 09:57:39 I'll send a config patch to kernel devel and then see how to debug further but should hopefully only be some alsa config file tweaking Jan 24 09:57:48 and the card becomes the second, as hda will be card0 Jan 24 09:57:51 as in Android Jan 24 09:58:14 never heard of rtcwake before, good to know Jan 24 09:58:16 check the chanelog first, there was a reason why diwic wanted it off Jan 24 09:58:28 yes, he just said it is useless as we do not have HDMI Jan 24 09:58:36 hmm, k Jan 24 09:58:40 but it is on in Android and seems to be needed for suspend Jan 24 09:58:49 as long as it doesnt cause mad wakeups etc Jan 24 09:58:50 it was just pruned as poart of simplifying config Jan 24 09:59:08 yeah, then switch it on again Jan 24 09:59:25 oh, btw i uploaded an ambient light script as well yesterday Jan 24 09:59:32 it is probably just a tegra hw bit that needs to be poked for proper audio suspend even if not connected to anything Jan 24 09:59:36 great Jan 24 09:59:40 only GPS and camera missing :) Jan 24 09:59:58 oh, and BT needs another deep look Jan 24 10:00:14 yes, camera is looked at by nvidia (not sure of the status but I am talking to the dev - our own Bryan Wu) Jan 24 10:00:29 is cyphermox on BT and GPS? (and NFC) ? Jan 24 10:00:29 hehe Jan 24 10:00:38 do we have NFC ? Jan 24 10:00:45 * ogra_ wasnt aware Jan 24 10:01:00 yes the device has it, fw in the blob collection Jan 24 10:01:11 and no idea about cyphermox, but we will have some -desktop attendance on friday Jan 24 10:01:17 not too important I'd say, webcam is the real important one Jan 24 10:01:59 right and the xinput bug Jan 24 10:02:25 yes, the webcam sensorwise, xinput overall showstopper Jan 24 10:02:49 its not that bad, if you make sure to actually leave time between taps Jan 24 10:03:02 i get through for a whole evening if i tap really carefully Jan 24 10:03:29 i wonder if we could somehow just turn down the sensitivity to work around it Jan 24 10:04:03 How is the update-initramfs triggers supposed to work? When installing precise on my armel target, I see a few packages that "update-initramfs: deferring update (trigger activated)" like it should. But after the kernel has been setup, all packages installed which triggers update-initramfs all makes update-initramfs run. Many times. Is this how it should be? Jan 24 10:04:41 depends, packages can force a trigger execution Jan 24 10:04:41 What can I do to debug this thing? Jan 24 10:04:59 well, read about triggers i'd say :) Jan 24 10:05:44 Well I don't see any difference in the triggers in the packages that run and defers and those which runs it immediately Jan 24 10:08:07 If I do remember correctly, the kernel runs /etc/kernel/(pre|post)(rm|inst).d/ and thus forces update-initramfs to run. Could this be altering the behaviour of the triggers somehow? Jan 24 10:20:54 I'm not enlightened by the dpkg-trigger documentation.. But you haven't seen that update-initramfs is run multiple times during installation on your systems? Jan 24 10:24:31 sveinse: I generally only see it run multiple times when an apt run gets split into several dpkg runs to break loops or satisfy pre-depends, etc. Jan 24 10:24:57 sveinse: A good indicator of that is often seeing the "Reading dpkg database... " stuff in your terminal backscroll. Jan 24 10:25:31 sveinse: Triggers can't carry between dpkg invocations (for, I hope, obvious reasons), so you'll sometimes get more than one trigger from the same package in an apt run. Jan 24 10:26:21 infinity: No, I dont think my runs are between dpkg invocations. It's all in the "Setting up ..." section Jan 24 10:27:01 If it's a big long string of postinsts, yeah, I'd probably have to see it to debug what's happening. Jan 24 10:27:16 It could be a dpkg bug, or it could be initramfs-tools' trigger is goofy. Jan 24 10:27:27 Or it could be postinsts of certain packages calling it wrong. Jan 24 10:27:36 How does dpkg decide when to run a trigger? Jan 24 10:27:46 (The kernel forces it to run triggerless, but that's a different story) Jan 24 10:28:40 Normally, it runs them at the end of a dpkg invocation, based on registered interest or delayed triggers (the latter, in the initramfs-tools case). Jan 24 10:29:40 Anyhow, not going to get into this at 3:30am. But if you have some terminal logs that show the offending behaviour in action, feel free to reference them in backscroll, or file a bug and reference that or some such. Jan 24 10:30:09 Just don't be offended if I decide to close it as invalid after looking into it. ;) Jan 24 10:30:13 What it seems in my case is that a few packages triggers it, then dpkg runs the trigger. One more or sometimes two triggers it, dpkg runs the trigger once more. Jan 24 10:30:14 * janimo just managed to get something that sounds like a drunk and angry R2D2 out of the nexus7 by randomly toggling things in alsamixer Jan 24 10:30:23 need a way to turn it off, it persists across reboot Jan 24 10:31:06 infinity: Well, I'm more like grateful. I've been struggling with this for a while now Jan 24 10:50:09 janimo: you want to be careful with that ... I know someone who literally melted his chromebook by toggling alsamixer switches... Jan 24 10:50:37 dmart, yes, I had read hrw's account Jan 24 10:51:21 for a moment I had feared I may damage the speakers too Jan 24 10:51:24 janimo: ucm profiles for chromebook are present in raring and in sru queue for precise/quantal Jan 24 10:51:28 but it's back again now Jan 24 10:51:51 hrw, I have no chromebook, it is the nexus7 that I was toggling alsa settings on Jan 24 10:52:06 ah Jan 24 10:52:26 hrw: Are the ucm profiles purely a userspace thing? Jan 24 10:53:46 yes Jan 24 10:54:17 janimo: really, it feels like the kernel should police any settings which can actually damage the hardware... but I don't know enough about alsa to know how to do that. Jan 24 10:54:39 hrw: ^ Jan 24 10:54:42 I need to update kernel as some fixes went to kernel Jan 24 10:55:09 dmart, I agree, but maybe some hw can be broken in so many ways the kernel cannot catch all cases. No idea really Jan 24 10:55:20 this may have been a simple bug/oversight, hrw? Jan 24 10:55:30 It's possible I am missing some fixes ... I haven't updated for a bit Jan 24 10:55:46 just like one could fry monitors with VGA poking, there may be root-only things that can damage modern hw Jan 24 10:56:13 janimo: they fucked up "ASoC machine" source Jan 24 10:56:34 janimo: sure, but that's still a bug in my view. I thought the ucm profiles were more about presenting the mixer settings in a more intelligible way, since the hardware-specific mixer config can be pretty complex Jan 24 10:56:35 I know little about ALSA too, learned some the past two days but am still bewildered by the large number of concepts and config options Jan 24 10:56:36 so you can connect wrong parts of audio chip to output Jan 24 10:57:21 hrw: My guess was that the likely problem is that the hardware mixer allows you to connect two SoC outputs to the same analog sink Jan 24 10:57:37 dmart: and one of them is digital iirc Jan 24 10:58:08 hrw: oh! Jan 24 10:58:47 hrw: I wondered if bad things could be made to happen by, say, connecting the left and right DAC1 channels to a single channel of the speaker. But I didn't really want to try that... Jan 24 10:59:15 dmart: check my blog for exact steps Jan 24 10:59:38 dmart: now my left speaker can only generate heat cause it is unable to generate sound anymore Jan 24 11:00:28 hrw: on the plus side, you can now use /dev/heat to make a novel user interface... Jan 24 11:00:48 dmart: but /dev/heat is symlink to /dev/stinkysmall Jan 24 11:00:58 dmart: but /dev/heat is symlink to /dev/stinkysmell Jan 24 11:22:00 I have a custom deb package which installs a hook into initramfs. This hook relies on a file from /etc. Now when I install this package the hook is put into the filesystem early (when unpacking), yet the /etc file is put in late (when setting up I guess). However, update-initramfs is run by other packages in between these two steps and that makes update-initramfs bork since its missing the... Jan 24 11:22:02 ...file from /etc. How should I deal with that? Jan 24 12:59:54 * xnox has just flashed nexus7 using... usb-creator Jan 24 13:54:08 what's the state of ubuntu on the samsung chromebook? Jan 24 13:54:45 any chance we'll have working video acceleration anytime soon? Jan 24 14:23:27 pfui: hrw does samsung chromebook stuff. Jan 24 14:28:56 xnox: hmm... seems to have a few relevant posts on his blog. thanks! Jan 24 16:00:57 hi, all! I need connect nexus 7 with ubuntu under Windows via terminal, but the system asks for driver... Which one I need? Jan 24 16:03:58 reisei: i'm quite ignorant about windows so not sure if this is up-to-date, but the linux kernel source has documentation at http://kernel.org/doc/Documentation/usb/gadget_serial.txt (search for "Windows") Jan 24 16:04:04 * ogra_ has no idea Jan 24 16:04:58 on ubuntu you can just run screen with the right args in a terminal ... or minicom, surprising that win needs actual drivers for a serial USB port Jan 24 16:05:32 you'll probably need to write your own, since nexus 7 has it's own vid and pid Jan 24 16:05:52 (meaning you'll have to write definiton file, which tells windows to use it's generic driver) Jan 24 16:05:53 there is no generic usb serial drive in windows ? Jan 24 16:05:58 *driver Jan 24 16:06:59 yes, but you'll have to tell windows to use it on that vid/pid - that's what windows calls "driver" Jan 24 16:07:08 it is in that doc Rjs linked Jan 24 16:07:11 (I'm still ignorant but guessing:) the windows inf file that the documentation talks about is at http://kernel.org/doc/Documentation/usb/linux-cdc-acm.inf and seems to contain vendor and product IDs, so I guess you could change them there Jan 24 16:07:34 ah Jan 24 16:08:07 yeah, should be as easy as that, had to do that for one ACM USB thingy already Jan 24 16:08:17 funny how that is "driver" for windows) Jan 24 16:09:43 that file talks about something called usbser.sys, so I guess that inf file is really a configuration file for the generic driver named usbser.sys (I presume that's included in windows, since the doc doesn't speak about having to download it) Jan 24 16:14:51 hmm, does the ubuntu nexus7 really have its own vendor/product IDs? as far as I can tell from my syslog, the vendor and product IDs in the inf file I linked to appear to be correct: vid 0x0525 and pid 0xa4a7 so I'm guessing that inf file should work as it is Jan 24 16:14:51 my syslog has "New USB device found, idVendor=0525, idProduct=a4a7" from the time I still used the standard ubuntu kernel (I have later switched to the combined ethernet+serial gadget which has a different product id) Jan 24 16:16:32 maybe it doesn't, that vid is "0525 Netchip Technology, Inc." and pid is "a4a7 Linux-USB Serial Gadget (CDC ACM mode)" Jan 24 16:17:02 * Tassadar goes to look at that driver's source Jan 24 16:20:31 That's so opposite to linux simpicity... Jan 24 16:23:06 I don't get why they don't just use USB device class to find driver like Linux does Jan 24 16:26:51 yeah, the vid/pid is hardcoded Jan 24 16:27:16 apparently they donated some pids, "Thanks to NetChip Technologies for donating this product ID." Jan 24 16:27:30 then you can just use the driver as is :) Jan 24 16:47:25 Hi, I was recently thinking about getting an ARM device as my home server (irc, ftp, bittorrent, small http, etc). Cubieboard and some ODROID boards looks promising, but I even got as wild as thinking about Nexus 7. Jan 24 17:07:38 Rjs: those look different to mine. Jan 24 17:08:27 484 + 'ID_VENDOR_ID': ('18d1',), Jan 24 17:08:27 485 + 'ID_MODEL_ID': ('4e40', 'd001',), Jan 24 17:08:42 Rjs: ^^^^ for nexus7's i saw around. Jan 24 17:09:02 and that's just standard google / nexus7 id's. Jan 24 17:09:07 dont mix up kernel and bootloader though .... Jan 24 17:09:17 ah! Jan 24 17:09:33 the nexus reports different things in the different bootloader modes Jan 24 17:09:47 how dumb is that :-( Jan 24 17:09:56 and kernel wise it matters what is actually bound to the gadget setup Jan 24 17:10:37 the pid is also different if you turn on/off the debug mode (adb) Jan 24 17:11:30 XorA, not dumb, that whay the other end knows if it is in flash mode, media player mode recovery (with adb) etc etc Jan 24 17:12:38 indeed under the assumption that you have a udev rule (or windows driver) that can handle that state Jan 24 17:13:07 and the g_serial driver has the pid/vid hardcoded in drivers/usb/gadget/serial.c, if you wanna take a look Jan 24 17:15:04 ogra_: there has to be a better way, making that sort of mess has no real justification Jan 24 17:15:14 ogra_: other devices work fine with constant ids Jan 24 17:15:22 tell that to android Jan 24 17:15:34 i dont think thats actually nexus7 specific Jan 24 17:15:58 at least for the bootloader side Jan 24 17:15:59 its probably more a function of which lazy engineer did the integration Jan 24 17:17:45 wooy, go with a board, the nexus7 would be a waste in such context Jan 24 17:23:50 xnox, hrm, that upstart job is quite uglz Jan 24 17:23:55 *ugly Jan 24 17:25:44 xnox, and it will be executed for every USB device you ever plug in Jan 24 17:26:14 ogra_: well, very soon now we will have upstart user session. Jan 24 17:26:28 ogra_: then the job will move and run in the user session, if usb devices are plugged in. Jan 24 17:26:36 yeah, still Jan 24 17:26:46 ogra_: the alternative I had was: udev-rules with RUN+= Jan 24 17:26:59 i think having a udev rule that triggers something in the user session would be better Jan 24 17:27:11 apart from that cannot "spawn", if usb-creator is started the udev rules processing is blocked until usb-creator exits. Jan 24 17:27:30 another option is to have: udev rules which does "start usb-creator" to launch the upstart job. Jan 24 17:27:31 .... Jan 24 17:27:39 but that's like two hacks instead of one. Jan 24 17:27:51 yeah, no, well ... Jan 24 17:28:21 ogra_: the trouble is that, udev runs at system level. And the hops to get DISPLAY & $uid are ugly =/ Jan 24 17:28:41 ogra_: by the way upstart job is quicker to launch usb-creator than udev rule + shell wrapper Jan 24 17:28:47 * xnox has no idea why. Jan 24 17:30:08 less subshell calls probably Jan 24 17:30:54 still, i dont like to idea to fire off that job every time you insert a usb device Jan 24 17:31:43 there must be a more elegant way Jan 24 17:33:27 i wonder if there isnt a more fine grained way to use the event .... i.e. some kind of filtering Jan 24 17:37:36 =/ yeah that would be nice Jan 24 17:37:55 ogra_: anyway, I did ask james hunt to review it and see if he can offer something better. Jan 24 17:38:22 Note the bottom on upstart-udev-bridge manpage "This is a temporary tool until init(8) itself gains the functionality to read them directly; you should not rely on its behaviour." Jan 24 17:38:27 yeah, well, we could have a udev rule that emits an event Jan 24 17:39:26 so you filter on the lower level, and the upstart job just reacts to "nexus7-added" events Jan 24 17:41:28 a udev rule with ... RUN+="initctl emit --no-wait nexus7-added" Jan 24 17:42:13 we have that rule file already anyway Jan 24 17:43:30 (or at least we should, for setting the udev-acl stuff to not need root access) Jan 24 19:21:25 marvin24_, is your 3.8 ac100 kernel working well? Jan 24 19:37:24 janimo: Thinking of updating raring to something modern? Jan 24 19:38:28 infinity, sure, if it works. marvin24_ said he's working on a 3.8 port Jan 24 19:53:31 janimo: yes, 3.8 works fine Jan 24 19:53:41 but building a kernel package takes weeks ... Jan 24 19:54:01 I hope I can upload something on the weekend or so Jan 24 19:54:49 marvin24_, great. Same gitorious repo? Jan 24 19:54:56 weeks really? Jan 24 19:55:06 do you have errors building it? Jan 24 19:56:19 janimo: it's still the kernel in my old repo Jan 24 19:56:48 https://www.gitorious.org/~marvin24/ac100/marvin24s-kernel/ Jan 24 19:57:00 some modules failed, yes Jan 24 19:57:08 so I need to disabled them Jan 24 19:57:16 then I got abi errors Jan 24 19:57:35 turned out I need to specify "-eskipmodules" Jan 24 19:57:44 after several tries Jan 24 19:58:03 and each one is two hours and I'm doing it in my free time ... Jan 24 20:18:38 marvin24_, I used debuild with -nc Jan 24 20:18:42 so it does not clean the tree Jan 24 20:18:46 before rebuilding Jan 24 20:22:26 well, I use ccache (with --prepend-path=/usr/lib/ccache) Jan 24 20:22:53 marvin24_, do you know if nvidia keep some sort of wiki or updates on what is mainlined and what is pending for tegra2 and tegra3? An overview of sorts Jan 24 20:23:15 janimo: not that I know of Jan 24 20:23:26 I think they have an internal list Jan 24 20:23:40 but what's getting done, is mostly in a random order Jan 24 20:24:01 in fact, the most painful stuff missing is suspend/resume Jan 24 20:24:22 and more powermanagement stuff Jan 24 20:25:05 also some simple stuff just takes very long Jan 24 20:25:12 e.g. backlight support Jan 24 20:25:14 did graphics support land already? Jan 24 20:25:24 DRM Jan 24 20:25:25 yes, it's included in 3.8 Jan 24 20:25:33 but without backlight, only hdmi works Jan 24 20:25:44 funny Jan 24 20:25:53 I think the backlight code is discusses for nearly one year now Jan 24 20:26:06 and still no conclusion Jan 24 20:26:08 do you know whether tegra2 or tegra3 is more completely supported in mainline? Jan 24 20:26:30 so you carry the backlight code in your ac100 branch? Jan 24 20:26:35 I think they are pretty inline Jan 24 20:26:56 yes, I just one of the discussed implementations Jan 24 20:27:03 but that's already outdated Jan 24 20:27:24 in fact, now they wait for some generic framework Jan 24 20:28:31 they have working 3.8 code for all things just not mainlined though? Jan 24 20:29:01 yes Jan 24 20:29:56 the way it needs to be integrated into kernel is, well, complicated Jan 24 20:30:04 ok, thanks. Checking your branch out now Jan 24 20:30:05 in fact, you just need to program some gpios Jan 24 20:30:21 but there is no generic interface for this yet Jan 24 20:30:46 and upstream does not like soc specific backlight ... Jan 24 20:31:38 very long, sad story Jan 24 20:43:01 marvin24_, does the 3.8 kernel require uboot or is the defautl ac100 bootloader enough? Jan 24 20:59:30 janimo: both should work, but need different configs Jan 24 21:00:37 fastboot needs cmdline from kernel and u-boot needs kernel command line from u-boot Jan 24 21:00:52 but I don't plan to support 3.8 kernels with fastboot Jan 24 21:01:09 3.1 supports both Jan 24 21:05:38 janimo: http://tinyurl.com/b55syst Jan 24 21:05:43 this is what I have for now Jan 24 21:05:54 against raring 3.8 kernel Jan 24 21:06:11 ac100 specific patches are still missing Jan 24 21:06:25 but compiles at least Jan 24 21:08:26 marvin24_, nice. How many ac100 pacthes are there? Jan 24 21:10:07 well, my linux-ac100-3.8 branch contains 25 patches, mostly nvec specific Jan 24 21:10:38 but in fact, mainline also boots without any patch, but you will get no backlight ... Jan 24 21:10:41 this patch changes a few other arm flavour's config files, probably a side effect of using the config updater scripts Jan 24 21:11:00 yes, kernelconfig editconfig ... Jan 24 21:11:19 I think it would be cleaner as a first step to have a dedicated tree, not based on the current kernel source Jan 24 21:11:29 as it is unlikely they will take patches for this Jan 24 21:11:47 I don't expect ubuntu to take patches for tegra Jan 24 21:11:51 so a new linux-tegra package without any other flavours Jan 24 21:11:54 because they cannot support it Jan 24 21:12:10 right, just mentioning the resulting kernel would be cleaner than this patch suggests Jan 24 21:12:40 if we had this kernel in raring would we need to use uboot on the ac100 then? Jan 24 21:12:51 yes Jan 24 21:13:10 I need to patch the debian dir anyway Jan 24 21:13:12 isn;t that complicating the installer besides adding one other package to maintain? Jan 24 21:13:23 and most is because of the abi stuff Jan 24 21:13:51 I understand preferring to work with uboot but is fastboot support complicated? Jan 24 21:14:31 yes, because I don't have the source ... Jan 24 21:14:41 I'd like us to use this in raring but will need to speak to ogra to see whether it is a lot of effort to adapt to uboot Jan 24 21:15:29 cannot whatever 3.1 does be emulated in 3.8 without knowing what fastboot does? Jan 24 21:15:51 https://launchpad.net/~ac100/+archive/ppa/+packages has u-boot package already Jan 24 21:16:55 janimo: well, I prefer minimal patches Jan 24 21:17:06 why do you want fastboot? Jan 24 21:17:32 marvin24_, oh just so 3,8 is a drop-in replacement for 3.1 Jan 24 21:17:42 so we do not need any extra testing or image work Jan 24 21:17:59 and not introduce a new uboot flavour for the ac100 only Jan 24 21:18:08 it also causes extra work to support fastboot Jan 24 21:18:16 nothing against uboot per se, just keeping changes minimal as you say :) Jan 24 21:18:59 I'm not sure how to adapt 3.8 to make it woking with fastboot Jan 24 21:19:11 and to make installation similar to previous cycles Jan 24 21:19:20 would this also be nvflash of a bootimg and boot it? Jan 24 21:19:21 (except chaning the krnel config) Jan 24 21:20:00 no need to flash, as we planed to use tegrarcm Jan 24 21:20:57 in fact, once ogra said that he won't put more work on the ac100 port Jan 24 21:21:14 we decided to restart from something clean Jan 24 21:21:54 I know this causes more pain for users, but less for us Jan 24 21:26:01 also u-boot needs a new partition table because otherwise it cannot load the kernel Jan 24 21:26:13 and this disables nvflash Jan 24 21:28:58 because fastboot expects some proprietary partition table Jan 24 21:54:10 Now, to get Ubuntu on the Toshiba A*T*100.. haha Jan 24 21:54:32 I've got a fully-functional FS. No working kernel... Jan 24 21:56:17 Do know how to kill the Android GUI stuff to get X working, via ADB shell, but a pure native way would sure be nice... Jan 24 21:59:27 Wait, do I need U-boot to boot Ubuntu? Or is a Fastboot-based system OK? Jan 24 22:06:24 hey, yo, where do i find like a this thing: http://packages.ubuntu.com/ but exclusive to arm Jan 24 22:10:55 anyone? Jan 24 22:13:26 is there even an apt repository for arm devices? Jan 24 22:18:56 questionguy: http://ports.ubuntu.com/ Jan 24 22:23:33 thanks a ton! Jan 24 22:26:55 questionguy: It's a longstanding bug/misfeature that packages.u.c doesn't list ports, but you can see that the same packages exist on all arches by going to, say, launchpad.net/ubuntu/+source/ Jan 24 22:38:25 infinity: yeah i literally thought that i would just find it by clicking around, and its completely inexcellent that it's so well hidden Jan 24 22:38:37 but it's simple enough to remember, having seen it Jan 24 22:42:15 Heh, should've known that.... Jan 24 22:44:50 questionguy: Of course, if you have an Ubuntu armhf system installed, 'apt-cache search' is your friend. Jan 24 22:45:53 yeah, i'm of course aware of that functionality, but i don't have one setup, and trying to see if this is a suitable distro, and indeed, it is Jan 24 22:47:26 hey all, I've been told that 13.04 is supposed to work nicely on the arm-based chromebook. Is there a better way of installing 13.04 than installing the hacked-shell-script-12.04, and upgrading? (I've tried to upgrade before, that went poorly to say the least) Jan 24 23:09:28 So, where's the best place to get kernel help? Jan 25 01:55:01 Well, I've got a near-chroot method working. Jan 25 01:55:15 *chroot method near-working... Jan 25 01:55:35 Now I've figured out how the Ubuntu for Android guys did it... haha Jan 25 01:58:27 Any ARM Xorg guys on right now? Jan 25 02:26:54 ogra_: so my 'ssh hangs hard when I try to connect to my nexus7' bug is still here, even after repeated reinstalls **** ENDING LOGGING AT Fri Jan 25 02:59:58 2013