**** BEGIN LOGGING AT Thu Jan 31 02:59:58 2013 Jan 31 07:23:10 good morning Jan 31 08:38:22 ogra_, do we still have freezes and image respins occasionally? Why are there .1 and .2 updates to yesterday's image? Jan 31 08:47:05 janimo: Because some people (I was one of them) spun nexus7 by hand. Jan 31 08:48:02 infinity, I was more intrigued by the reason actually :) Is this Thursday some sort of alpha or why the urgency? Jan 31 08:48:22 janimo: Because the image builder was down for 6 days, and I was testing things when it came back. Jan 31 08:48:27 just fixing image build bugs is a good reason Jan 31 08:48:28 janimo: Nothing release-related at all. Jan 31 08:48:39 infinity, ok Jan 31 09:33:47 janimo, hmm, i dist-upgraded yesterday and have all your changes installed, butu seems acceld is still running and if i stop it i have no rotation Jan 31 09:34:17 ogra_, so you have u-d-n-0.49 and gsd -ubuntu3 ? Jan 31 09:34:30 janimo, do we need to do anything for the device permissions perhaps ? Jan 31 09:35:22 ogra_, sudo udevadm info --query=property --name=iio:device Jan 31 09:35:38 does this show ID_INPUT_ACCELEROMETER=1 among others? Jan 31 09:35:42 i have both packages, yeah Jan 31 09:36:09 acceld is started in the X session hook (which I thought I had deleted) Jan 31 09:39:23 I planned on installing a fresh image but will wait the first image with these packages in it - yesterday's last does not yet Jan 31 09:41:17 didnt you remove the upstart job for acceld ? the Xsession script checks if it is enabled iirc Jan 31 09:41:21 * ogra_ checks his code Jan 31 09:42:21 yeah Jan 31 09:42:34 it looks for /sys/bus/iio/devices/iio:device0/buffer/enable Jan 31 09:42:58 janimo, if you are actually sure it works, just wipe acceld completely, it wasnt meant to stay :) Jan 31 09:43:27 ogra_, I thought it is only started from the X session hook Jan 31 09:43:43 kept the upstart bits as they initialize sysfs attributes with root privileges Jan 31 09:45:40 ah, indeed, you use them too Jan 31 09:45:45 err, no Jan 31 09:46:11 you at least dont read them dircetly, do they affect the /dev behavior ? Jan 31 09:51:48 we do not read anything from /dev actually, just from sysfs Jan 31 09:53:09 I thought I'd keep acceld along if someone wants to still debug rotation in the near future if g-s-d has issues Jan 31 09:57:07 janimo, you pointed out binary firmware for the accelerometer, where is that ? Jan 31 09:57:38 (or how is it called) Jan 31 09:57:39 there exists on android (inside executables) not as a separate file Jan 31 09:57:47 ah, k Jan 31 09:57:48 ogra_, the driver claims to provide polled interfaces when it has firmware loaded Jan 31 09:57:49 apw, ^^^ Jan 31 09:57:50 it's a few Kb of microcode only Jan 31 09:58:07 apw, it does, but the firmware is not only not free but it is unavailable Jan 31 09:58:27 seems to have been partially (?) reverse engineered by the libi2cdev project Jan 31 09:58:43 well that sucks Jan 31 09:58:52 janimo, ogra_: hello Jan 31 09:58:54 apw, the dirver indeed even provides orientation as a sysfs attribute when enabled Jan 31 09:58:57 pitti, hello Jan 31 09:59:03 hey pitti Jan 31 09:59:21 janimo, it was the 'poll' able interface i was interested in, but that doesn't work without Jan 31 09:59:34 apw, right, my understanding also Jan 31 09:59:38 so we don't have to poll, sigh Jan 31 09:59:52 we may get it to work but it seemed nonobvious techinically and murky license-wise Jan 31 09:59:58 yeah Jan 31 10:00:12 still I plan on looking into it, as this particular sensor is going to be in many other devices Jan 31 10:00:19 janimo: do you happen to know if we can use the triggers feature instead of having to poll all the time? Jan 31 10:00:20 it is in the galaxy nexus and the transformer at least Jan 31 10:00:25 variations of the MPU Jan 31 10:00:37 pitti, i guess only with binary firmware Jan 31 10:00:42 pitti, no idea, but I plan on looking at the kernel side to check this Jan 31 10:00:57 to see if we can without firmware that is Jan 31 10:01:13 though it shouldnt be to hard to move the acceld logic into the driver, would it ? Jan 31 10:01:14 btw android on the nexus7 seems to read the raw data from sysfs, and has no fw loaded Jan 31 10:01:30 janimo, i've just been reading the driver and all the event driven stuff is dependant on dmp being enabled, and that is dependant on the firmware Jan 31 10:01:35 maybe it uses some cleverer approach that eluded me as I did not look much into the kernel Jan 31 10:01:36 ogra_, to make the kernel poll for you ? Jan 31 10:01:44 waking up every 1 s is suboptimal I agree Jan 31 10:02:08 apw, well, the kernel processes these numbers anyway at some point, no ? Jan 31 10:02:17 ogra_, only on read Jan 31 10:02:37 apw, a middle road would be to have a kernel timer, have it do the calculations and only fire a kevent if it detects orientation chaneg Jan 31 10:02:46 hmpf, ok, i thought you could just run them through a filter that sends a trigger Jan 31 10:02:50 janimo, and that would be better how Jan 31 10:02:52 so less process wakeups but policy and hacks in the kernel driver Jan 31 10:03:12 how would there be less process wakeups, a kernel thread is a process too Jan 31 10:03:40 apw, ok, I plead ignorance then. I thought kernel timeouts would be more lightweight somewhat Jan 31 10:04:07 not really, it would look pretty much the same as a userspace process doing it Jan 31 10:04:31 the most efficient way would be to find something which is already polling Jan 31 10:04:40 and poll in that same process Jan 31 10:04:40 and piggyback on that? Jan 31 10:04:48 so you have one wakeup Jan 31 10:05:23 * pitti cannot think of something else on the desktop which is polling regularly Jan 31 10:05:25 I was hoping g-s-d already does that and our poll would just tail on an existing one, but other timeouts in g-s-d are usually largert Jan 31 10:05:56 no, g-s-d's orientation/media keys plugins mostly listens to XF86Rotate input events and similar, they don't poll Jan 31 10:06:15 so I guess we could at least put luxd and acceld into one C process which does the polling for both Jan 31 10:06:27 pitti, I mean other plugins, if they are in the same process (g-s-d) couldn't glibs timeout code wake them up at the same time? Jan 31 10:06:46 I was hoping g_timeout_add_second wakes up at second boundaries for this reason Jan 31 10:06:52 janimo: that's what I said, there are no polling plugins right now Jan 31 10:07:03 pitti, cirtainly wherever they go, we should poll them based on one timeout Jan 31 10:07:06 we need to introduce one Jan 31 10:07:18 pitti, ok. I grepped the source for g_timeout_add and there were a few, but they may not be enabled then Jan 31 10:07:24 screensaver and powermanager come to mind Jan 31 10:07:39 ogra_, when you read those values from sysfs the kernel gets the value 'now' from the actual h/w registers by the looks of it Jan 31 10:07:43 janimo: yeah, those use long timeouts, not subsecond polling Jan 31 10:07:48 so it isn't polling internally Jan 31 10:07:49 we'll need similar polling for the light sensor (but I need to check, that may provide some trigger) Jan 31 10:08:18 apw, from the buffer which we set the length to 200 at the moment Jan 31 10:08:23 janimo: I profiled g-s-d in a running desktop session, it got about 20 wakeups a minute; i. e. it doesn't currently poll devices, but it's as good a place as any to do that Jan 31 10:08:43 janimo: e. g. g-s-d's orientation plugin would be ideal in the sense that you can immediately hook into the "action" parts Jan 31 10:08:43 we can still tweak the accel to only use low power mode, and use 1.25HZ frequency Jan 31 10:08:56 but that only helps with its internal power savings, not the process wakeups Jan 31 10:09:13 pitti, btw, do you know if we already have a list of g-s-d modules we want to disable ? Jan 31 10:09:33 (or who is reviewing it) Jan 31 10:09:50 ogra_: yes, http://pad.ubuntu.com/nexus7-desktop-profiling Jan 31 10:10:21 ogra_: I came up with three which are definitively "out", and a handful which I'm uncertain about whether we need these features; but as they only add a negligible overhead my feeling is that we should leave them on for now Jan 31 10:10:22 pitti, 20 wakeups a minute sound ok. Does the desktop still have frequent waker-uppers? (1/s or more frequent) ? Jan 31 10:10:59 janimo: actually, compiz does Jan 31 10:11:12 janimo: that wakes up 60 times a second for vsync wakeup etc. Jan 31 10:11:20 janimo: (or the unity plugin) Jan 31 10:11:21 pitti, oh, right, i even commented already Jan 31 10:11:35 janimo: that's pretty much the only process which wakes up that often Jan 31 10:12:07 janimo: it might not actually be bad to put that polling into the unity plugin? it's "our" code anyway so we don't need to maintain huge patches against g-s-d, and can piggyback on the wakeups? Jan 31 10:12:41 janimo: oh, the second is firefox when you have JS pages open; but I guess we can safely discard that :) Jan 31 10:12:46 pitti, g-s-d was the most straightforward place as it dealt with accel and rotation already Jan 31 10:12:51 janimo, oh, btw, i was wondering if we couldnt "DPMS blank" and unblank the screen before and after rotating ... to hide the screen corruption Jan 31 10:13:02 no idea about how it would fit in unity but I am open to the idea Jan 31 10:13:26 pitti, or a g-s-d unity plugin? Jan 31 10:13:36 * janimo has no idea whether such a thing even exists Jan 31 10:13:53 janimo: I think g-s-d's orientation plugin is the most obvious one, but will require hard-to-maintain patches and additional wakeups; unity's is the most efficient in terms of wakeups, but might be harder to change Jan 31 10:14:25 pitti, this particular patch is small btw, not sure what else we may need in term of orientation Jan 31 10:14:28 janimo: g-s-d unity plugin> not right now Jan 31 10:16:33 I mostly considered this code as a stop-gap proof of concept until we figure out a better way possibly post 13.04 when we run into more types of accel sensors and have a better idea what may work across them Jan 31 10:17:43 pitti, is the etherpad above only about nexus7 g-s-d modules, will we have nexus specific module blacklist? Jan 31 10:22:43 well, i would call it tablet specific Jan 31 10:23:52 janimo: no, these three plugins are not really n7 specific; I think we should disable them for all mobile devices Jan 31 10:24:14 wacom and color apply even less to phones than to tablets Jan 31 10:24:16 pitti, great, I hope we have as little divergence between n7 and the rest as possible Jan 31 10:24:54 actually i think the unity formfactor gsetting needs to be enhanced ... and g-s-d should enable/disable them based on this Jan 31 10:24:59 janimo: we can disable those in the -defaults package Jan 31 10:25:28 (it currenly only has "netbook", "desktop" and "automatic" options) Jan 31 10:25:58 pitti, but thats very nexus7 specific, long term g-s-d should detect the right thing Jan 31 10:26:26 (for 13.04 the settings package will surely do though) Jan 31 10:26:57 ogra_: we can disable the updates plugin globally even; that's the one which is really useless on ubuntu Jan 31 10:27:43 as for color and wacom, that's more like a matter of choice; wacom is actually quite harmless (again, only triggered when you actually have such a device), but color is quite costly because of activating colord Jan 31 10:30:04 which doesnt even work on our LCD Jan 31 10:44:31 ogra_: dpms blank and unblank at rotation sounds like it is working around a bug in the X.org driver (i.e., if the nvidia driver was free software, you'd probably try to fix the screen corruption there?) Jan 31 10:44:31 ... so maybe the right place for a workaround would be in the X server, as some sort of wrapper for rotate requests before they get passed to the nvidia driver? or would that be too intrusive? Jan 31 10:44:31 hmm, or actually, does it use kms or something similar to rotate? if it does, you could possibly work around or even fix the corruption in the kernel driver, which is free software? (also, I've seen lots of display-related patches lately while browsing the linux-tegra list, but I don't know enough of the hardware to know if they have any relevance to the nexus7...) Jan 31 10:45:13 i fear that might be to intrusive since it would also affect sanely working drivers Jan 31 10:45:33 effectively nvidia needs to fix it Jan 31 10:46:16 but there is also compiz or nux that is redrawing really slow, i havent tested on lxde, but i bet the corruption will be a lot less there Jan 31 10:55:16 hrw, have you considered uploading a chromebook kernel to ubuntu? Jan 31 10:55:50 or some sort of exynos kernel Jan 31 10:55:52 ++ Jan 31 11:04:19 janimo, btw udevadm info --query=property --name=iio:device doesnt exist iio:device0 and 1 do though, 0 has the ID_INPUT_ACCELEROMETER=1 property but also 0600 permissions and is root owned (no udev-acl in place) Jan 31 11:04:50 ah yes the 0 dropped off in the paste Jan 31 11:05:12 ogra_, I don't remember doing anything with udev-acl or permissions Jan 31 11:05:28 root owned is ok as we do not read from it Jan 31 11:05:33 well, doesnt the user need read access at least ? Jan 31 11:05:34 sysfs is user readable Jan 31 11:05:38 ah, k Jan 31 11:05:43 i thought you read from the device Jan 31 11:05:54 no, we coudl read from there too but sysfs seemed simpler Jan 31 11:06:05 well doing exactly as the go/dash scripts did, read form sysfs files Jan 31 11:06:29 no idea why acceld is still running there though Jan 31 11:06:34 and why g-s-d does nothing Jan 31 11:07:04 ogra_, ah you mentioned screen blanking above. I guess we could do something to cover the ugly rotation effects Jan 31 11:07:07 not sure how blanking would look Jan 31 11:07:24 unfortunately we cannot do animated rotation as android does :) Jan 31 11:07:34 hopefully just like "flash to black and back" Jan 31 11:08:26 (WW) TEGRA(0): LVDS-1: Error querying display modes: No such device. Jan 31 11:08:41 i'd really like to know which device it talks about :/ Jan 31 11:10:51 right, weird xorg.log spa, Jan 31 11:10:53 spam Jan 31 11:11:09 well, xrandr prints that too Jan 31 11:11:10 you can strace and see what it checks for Jan 31 11:11:19 maybe we have some etc permissions wrong? Jan 31 11:11:31 I mean /dev permissions Jan 31 11:14:22 i dont think so Jan 31 11:15:18 all tegra* devices are handled by ACLs Jan 31 11:15:30 all nv* devices too Jan 31 11:16:05 oh ! Jan 31 11:16:17 i never noticed /dev/lightsensor before Jan 31 11:17:01 /dev/fb0 and 1 are ACL handled as well Jan 31 11:17:19 ogra_, lightsensor is only used for debugging from what I saw Jan 31 11:17:25 ah, k + Jan 31 11:17:28 how sad Jan 31 11:17:28 to ioctl on it and toggle printks Jan 31 11:17:58 hmm there is a knvmap Jan 31 11:18:15 nvmap is ACL'ed but not knvmap ... i wonder what that does Jan 31 11:19:02 oh, i tried gpsd for laughs ... seems it connects and initialized the device fine (according to xgps) but it never starts connecting Jan 31 11:33:33 ogra_, when are the daily nexus7 images built? Jan 31 11:37:13 14:something UTC Jan 31 11:43:53 janimo: after fosdem I will have kernel which I consider uploadable Jan 31 11:46:20 hrw, janimo, I think it should be quite possible to have a single exynos5 kernel supporting arndale/chromebook/nexus10 Jan 31 11:46:46 suihkulokki: arndale uses 3.8, nexus10 uses 3.4(?), chromebook uses 3.4 Jan 31 11:48:15 suihkulokki: if someone wants to work on 3.8 for chromebook then I can test from time to time. But prefer something "stable" for each day use Jan 31 12:14:54 suihkulokki, that would be great indeed Jan 31 12:15:08 hrw, do you know about these? I was pointed to by fabo http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/using-an-upstream-kernel-on-snow Jan 31 12:15:36 * janimo has no chromebook or any exynos btw, just thinks that having the kernel in 13.04 is a good idea Jan 31 12:17:31 janimo: I know Jan 31 12:17:43 janimo: note that it also says "text console only for now" Jan 31 12:17:53 no x11, no usb, no keyboard, no charging Jan 31 12:18:10 hrw, ok I wasn't aware of the status of that effort Jan 31 12:18:21 or the uptodatedness of the page Jan 31 12:19:02 works: serial (if you have debugboard == work for google), i2c (except one with keyboard and pmic), power button/lid switch, emmc/sd Jan 31 12:19:34 not work: x11, usb, i2c4 (keyboard, pmic), display, hdmi, wifi, rtc, trackpad, audio Jan 31 12:19:52 but it is good that they list status Jan 31 12:20:03 and its 2 months old now so maybe got better Jan 31 12:21:07 ogra_: bug 1110408 - I may have been a bit confused, as I didn't realise that we'd deliberately switched to portrait mode by default, so it was mostly just an upgrade surprise. I guess the main bug was that touch was miscalibrated, then, and that no longer seems to be true. Should I just close it? Jan 31 12:21:08 Launchpad bug 1110408 in ubuntu-defaults-nexus7 (Ubuntu) "Log out → lightdm comes back in portrait mode" [Undecided,New] https://launchpad.net/bugs/1110408 Jan 31 12:22:58 I probably Jan 31 12:23:07 just hadn't rebooted since some relevant bit of the upgrade, or something Jan 31 12:23:50 janimo: new chromebook kernel requires also new opengles driver for which I need to write new packaging with license stuff etc Jan 31 12:24:22 cjwatson, that lightdm does not rotate is a bug though, it has some overlap with your experience Jan 31 12:24:39 seb128 knows about that too so it's targeted Jan 31 12:25:02 hrw, is that package that you needed the license stuff for yesterday? Jan 31 12:25:07 yes Jan 31 12:25:39 janimo: well, ok, but lightdm does now seem to work properly in portrait mode for me ... Jan 31 12:25:50 as in I can actually touch "Log In" Jan 31 12:25:55 I have first version but it complains about debconf not being interactive even when debconf is dialog or readline Jan 31 12:26:32 right, so that bug as you said is not valid. It's just that it would show up in portrait when you log out of an otherwise landscape session Jan 31 12:26:42 I found this out only yesterday after seeing your report Jan 31 12:39:22 janimo: btw - what do I have to check before pushing chromebook kernel to archive? Jan 31 12:40:42 hrw, if the packaging (naming, structure) is more or less like other kernels' and there are no ambiguously licensed bits in it it should be ok Jan 31 12:41:04 janimo: I used linaro kernel packaging which is based on ubuntu one Jan 31 12:41:24 it won't go into the archive unless an archive admin reviews it (infinity most likely) anyway Jan 31 12:41:31 sure Jan 31 12:41:44 the ac100 and nexus7 kernels are based on linaro packaging too Jan 31 12:42:37 and infinity thinks having exynos in archive is a good idea - I asked you because I remembered him saying it :) Jan 31 12:42:52 ;) Jan 31 12:43:04 janimo: OK, so, do you want my bug open or closed? Jan 31 12:43:09 hrw, do you know if the SoC on chromebook and nexus10 is the same? Jan 31 12:43:23 janimo: iirc same Jan 31 12:43:26 cjwatson, closed or renamed to 'no rotation in lightdm' I'd say Jan 31 12:43:27 exynos5250 Jan 31 12:43:57 hrw, great, but likely much different peripherals Jan 31 12:44:05 janimo: indeed Jan 31 12:44:09 hrw, btw are there inertial sensors on the chromebook? Jan 31 12:44:19 accel/gyro/compass like on a mobile Jan 31 12:44:40 janimo: no idea really Jan 31 12:46:23 git-buildpackage sometimes is nasty but in general roxx Jan 31 12:46:24 hrw, doesn't look like from a quick search. Probably not much value in them Jan 31 12:46:26 Xorg on my Nexus 7 died with the error http://paste.ubuntu.com/1593004/ while running these tests https://wiki.ubuntu.com/Nexus7/BrowsingSimulation , is it a known issue? Jan 31 12:46:53 I need to buy usb3 hub and usb3 case for 3.5" hdd Jan 31 12:47:12 jibel, not that I know of. Do you know if it fails on other similarly specced ARM hw? Jan 31 12:47:14 my 320GB hdd is wasting bandwith of exynos5 usb... Jan 31 12:47:55 cjwatson, right close it ... (sorry was afk) Jan 31 12:48:11 janimo, no idea, I just have tested on this device Jan 31 12:48:41 and didn't find anything interesting on the web yet Jan 31 12:49:11 jibel, feel free to file it under the ubuntu-nexus7 project then Jan 31 12:49:23 janimo, k Jan 31 12:49:36 it will get reproduced and kept track of. thanks Jan 31 12:49:57 ok, closing, thanks Jan 31 12:55:17 ogra_, -9.25 in the can and building Jan 31 12:55:35 apw, yep, saw it, thanks Jan 31 13:11:46 E: linux-chromebook-3.4 source: build-depends-indep-without-arch-indep Jan 31 13:11:55 thats only what left from lintian ;) Jan 31 13:16:13 hrw, so your package probably is the cleanest ubuntu kernel package then :) Jan 31 13:16:55 * janimo wishes we had an uptodate git kernel-package repo which all kernel package sync up with from time to time Jan 31 13:17:04 janimo: https://github.com/hrw/chromebook-linux Jan 31 13:17:11 it's too much gratuitous divergence in packaging Jan 31 13:17:39 janimo: we have such one at Linaro Jan 31 13:18:15 hrw, I'd name the package linux-exynos5 or something. There may be a new chromebook or two in the future Jan 31 13:18:50 same with exynos5 hardware Jan 31 13:19:03 but I understand Jan 31 13:19:19 x86 chromebooks for example should be ~fine with default ubuntu kernel Jan 31 13:21:04 janimo, i noticed that my desktop now comes up in portrait by default and you need to rotate it once to activate rotation at all ... did you set the default orientation to "right" in g-s-d ? Jan 31 13:21:19 (should be "normal" in protrait) Jan 31 13:24:41 jibel, hmm, that uses chromium ... afaik out package is pretty outdated and it crashes for me after a while when using it Jan 31 13:25:17 (it breaks all font rendering here, likely due to an incompatible cairo version thats shipped in the chromium package) Jan 31 13:25:35 ogra_, yes I noticed that too, I need to see what the issue is :) Maybe the same bug as I ad in acceld Jan 31 13:25:45 yeah Jan 31 13:27:29 ogra_, I wonder if we should test all X related bugs in lubuntu as well to rule out compiz/unity/3d Jan 31 13:28:02 would make some sense i guess Jan 31 13:28:12 not that i'm eager to install lxde though :P Jan 31 13:28:17 ogra_, it shouldn't make X crash, does it? Jan 31 13:28:43 chromium ? no it just breaks font rendering Jan 31 13:29:13 but the testsuite might break sue to it, no idea Jan 31 13:29:15 *due Jan 31 13:57:33 hrw, for the final upload the skipabi and skipmodule bits need to be removed, so these tests get performed Jan 31 13:57:37 annoying as they are Jan 31 13:59:17 ok, thanks Jan 31 13:59:46 did some tweaks and sent package to pbuilder now Jan 31 14:17:58 bug 951827 Jan 31 14:17:59 Launchpad bug 951827 in gnome-power-manager (Ubuntu) "Power Statistics window blank" [High,Fix released] https://launchpad.net/bugs/951827 Jan 31 15:36:28 I need to compile wpa_supplicant for a ubuntu-server image for beagleboard. Linux ubuntu2 3.2.0-23-omap #36-Ubuntu Tue Apr 10 20:24:21 UTC 2012 armv7l armv7l armv7l GNU/Linux. can anyone tell me how I can do it? Jan 31 15:36:47 geez, my N4 was just sent ! i only ordered today ! Jan 31 15:37:10 angs, whats wrong with the wpa-supplicant package we have in ubuntu ? Jan 31 15:39:01 I am trying to predefine the cell ID for an ad-hoc wlan and using " bssid=92:4B:23:9D:30:DA " on wpa_Supplicant for it. however it never gets that cell id. on #linux-wireless I am told that the current wpa_supplicant that I am using is too old (0.7.3) and I need a newest one Jan 31 15:40:52 the latest one is 2.0 Jan 31 15:41:13 is there any instruction how I can compile a package for ubuntu-arm? Jan 31 15:49:25 just compiling it on the board is the easiest Jan 31 15:50:17 what do I need to do after I download the package on the board? Is there any instruction for that? Jan 31 15:50:23 are you sure about 1.0 ? Jan 31 15:50:34 the latest releas in debian and ubuntu is 1.0 Jan 31 15:50:41 err about 2.0 indeed Jan 31 15:51:01 yeah it is 2.0 Jan 31 15:52:08 well, the general triplet of commands should do (configre/make/make install) if you use an upstream source Jan 31 15:52:43 you probably might need some build dependencies installed, i would look at the build deps from the ubuntu package and just make sure you have these Jan 31 15:53:35 thanks for your help ogra_ Jan 31 16:30:43 I'm having trouble booting Ubuntu 12.04. After a few tweak to the boot.scr I got to get to the UI, once to the language selection window, otherwise I get the Ubuntu background for a while then it reboots. Jan 31 16:30:51 Pandaboard ES Jan 31 16:31:59 Wondering what logs files I can look to to diagnose the problem Jan 31 16:40:12 actually just found this in the syslog right before reboot - Unable to determine the model from DMI Jan 31 17:19:34 janimo: ok, source package renamed to linux-exynos5-3.4 but is binary package linux-image-VER-ABI-chromebook fine? Jan 31 17:19:47 hrw, a moment Jan 31 17:19:52 ok Jan 31 17:21:17 hrw, thats what we use for ac100 and nexus7, should be good Jan 31 17:21:26 cool Jan 31 17:22:00 they should give devices some names ;) Jan 31 17:23:32 I've got some pretty bad graphical corruption after flashing the current N7 daily. The background isn't rendered properly and half the screen is shifted over (and oem-config is off the side and is unusable). Anyone seen this? Jan 31 17:26:28 hrw, should 3.4 be in the source package name? I don't think we have that elsewhere Jan 31 17:27:20 can kill Jan 31 17:28:50 Has anyone gotten hardware accelerated video decoding working on the Nexus 7 under Ubuntu? Jan 31 17:30:09 https://picasaweb.google.com/lh/photo/25VNEPdfiynNV9ZIrFj15dMTjNZETYmyPJy0liipFm0?feat=directlink Jan 31 17:30:12 like that Jan 31 17:31:47 looks painful Laney Jan 31 17:32:06 hrw, I'd also say the binary package image should be the same as the source's. I'd suggest using the same scheme as ac100 and nexus Jan 31 17:32:16 as they are in the archive and noone complained about their naming :) Jan 31 17:32:38 although they are named after the product not the soc Jan 31 17:32:45 janimo: they had product names Jan 31 17:33:10 I was just thinking the exynos kernel may be used by other devices using that SoC Jan 31 17:33:21 if I make linux-daisy or linux-snow + linux-image-3.4.0-5-daisy or linux-image-3.4.0-5-snow who will know what it is? Jan 31 17:33:47 hrw, I'd consult infinity on this issue as well Jan 31 17:34:17 next week then Jan 31 17:34:22 maybe exynos indeed would be too generous if it only worked with chromebook and contained chromebook specific code Jan 31 17:34:30 I plan to go to sleep in ~2h Jan 31 17:34:42 04:00 trip to fosdem starts Jan 31 17:34:58 hrw, have a good trip and conference! Jan 31 17:35:25 thanks Jan 31 17:35:30 Can I install a version of ubuntu on a galaxy note GT-N7000? I mean native. Jan 31 17:42:01 https://wiki.ubuntu.com/ARM/DeviceSupport Jan 31 17:42:19 I suppose that it's not easy Jan 31 20:02:54 I went to Ubuntu site but cannot find the ARM version to download - help please Jan 31 20:14:05 gmulak1 installing on ARM devices is very different than installing on X86 Jan 31 20:14:12 it isn't "one download fits all" Jan 31 20:14:18 Generally installing is different on every device. **** ENDING LOGGING AT Thu Jan 31 22:46:41 2013 **** BEGIN LOGGING AT Thu Jan 31 22:48:23 2013 **** ENDING LOGGING AT Fri Feb 01 02:59:58 2013