**** BEGIN LOGGING AT Sun Jun 03 02:59:59 2012 Jun 03 08:46:39 lilstevie: you still here? Jun 03 09:46:45 janimo: not really Jun 03 10:02:06 lilstevie: lookslike there is no SYS V IPC in your kernel Jun 03 10:03:00 lilstevie: rebuilt a kernel but it does not boot. will retry with the defconfig from your sources Jun 03 10:05:40 janrinze: yeah, sysvipc is missing from the released kernel Jun 03 10:05:50 but the kernel on git has it Jun 03 10:06:14 lilstevie: apparently that is causing the XShm to fail.. Jun 03 10:06:25 also, use the android ndk toolchain to build the kernel Jun 03 10:06:39 tegra is really really dodgy Jun 03 10:06:44 and breaks easy Jun 03 10:06:45 :p Jun 03 10:06:56 huh android ndk toolchain? why? Jun 03 10:07:14 because that is what works without errors Jun 03 10:07:21 does gcc from Ubuntu not build working kernels? Jun 03 10:07:25 and what asus use Jun 03 10:07:33 gcc from ubuntu "works" Jun 03 10:07:38 I was using it Jun 03 10:07:47 but it causes more problems than its worth Jun 03 10:07:57 what kind of problems? Jun 03 10:08:12 compile errors galore Jun 03 10:08:30 ah during module build, right? Jun 03 10:08:34 and in some cases non booting kernels Jun 03 10:08:42 not only during module builds Jun 03 10:09:24 hmm.. that would be a serious issue.. does that mean Tegra is not fully ARM compatible? Jun 03 10:09:51 or does it mean Tegra has bugs that need work-arounds? Jun 03 10:10:50 no, just that it is fragile Jun 03 10:11:25 hmm.. weird. I have not had that problem with any other ARM platform before. Jun 03 10:12:01 I have had it on hummingbird Jun 03 10:12:24 hummingbird, Samsung? Jun 03 10:12:46 yes Jun 03 10:12:58 same as Exynos? Jun 03 10:13:25 it is older Jun 03 10:13:33 they call them exynos now Jun 03 10:13:55 oh, ok because the Exynos (dual core A9) works fine here too.. Jun 03 10:14:01 but the cpu that powers the original galaxy tab, and the galaxy s i9000 Jun 03 10:14:09 these are single core A8s Jun 03 10:15:07 hmm.. rebuilt a kernel but that one does not boot either.. Jun 03 10:16:06 lilstevie: tf101-gnu-linux-defconfig is what i have used.. is that correct? Jun 03 10:17:48 lilstevie: i built the kernel natively on the TF101. Jun 03 10:18:31 yeah probably an error there Jun 03 10:19:00 most likely. But how do you 'see' the console output or the boot log ? Jun 03 10:19:57 if you haven't seen it there isn't any Jun 03 10:20:08 :-( Jun 03 10:20:21 so no way to figure out what goes wrong? Jun 03 10:20:42 you could enable the android ramconsole driver Jun 03 10:20:54 with that enabled it will be at /proc/last_kmsg Jun 03 10:21:10 hmm.. Jun 03 10:21:39 serial console over USB would be a lot more sensible ;-) Jun 03 10:24:28 lilstevie: do you use the latest version of your git repo? the initrd in the OLiFE download may be to blame.. Jun 03 10:30:32 lilstevie: weird.. the original kernel won't boot either anymore now. Jun 03 10:36:20 janrinze: if you want serial console, ask asus for the pinout, I asked and got no response Jun 03 10:36:38 also are you flashing it with nvflash or blobs Jun 03 10:36:59 I use OLiFE.. so i think nvflash Jun 03 10:37:31 to primary or recovery boot Jun 03 10:37:54 recovery i guess, the primary is Android Jun 03 10:38:05 k Jun 03 10:38:10 IDK then Jun 03 10:38:12 should be working Jun 03 10:40:32 i saw something about 'wiping' the disk.. perhaps i need to reinstall everything.. Jun 03 10:45:10 :/ Jun 03 10:46:32 ok.. my bad, still was copying my own kernel to the device :/ Jun 03 10:47:13 linux has booted again.. Jun 03 10:49:07 lilstevie: can you send me a working .config for your git kernel? Jun 03 13:23:55 lilstevie: apparently self-built kernels won't boot.. how do i get a kernel with SYS V IPC enabled? Jun 03 13:45:22 lilstevie: the compiler supplied with the Android-NDK is not able to compile your kernel. many errors like "arch/arm/mach-tegra/suspend-t2.c:75: error: pllx causes a section type conflict" and more conflicts Jun 03 13:47:24 must be an ancient kernel ... Jun 03 13:47:32 3.1 already? Jun 03 13:47:41 (sorry, just jumped in) Jun 03 22:54:02 lilstevie: i managed to build a working kernel :-) Jun 03 22:55:26 unfortunately the file browser in unity does not allow to add custom file handlers to be configured Jun 03 22:56:12 looks like 12.04 is a neutered version of Ubuntu Jun 03 22:58:31 i had better get Debian running on this device.. Ubuntu has become a toy OS.. unity seems to be built for noobs that need to be kept away from configuring anything at all... Jun 03 23:02:59 umm, isn't that nautilus? Jun 03 23:07:35 nautilus on Debian is easy to reconfigure, on 12.04 however it seems to be stripped of all configuration possibilities Jun 03 23:08:14 actually most stuff in unity seems to work counter intuitive Jun 03 23:08:44 I would think that's more upstream decisions, are you trying the version in unstable or stable? Jun 03 23:08:48 it probably is just me but i feel extremely restricted by unity Jun 03 23:09:20 i use 12.04.. Jun 03 23:10:00 i have a program that is a raw file viewer. it needs to be associated to dng, pef, nef etc.. Jun 03 23:10:31 apparently there is no way to do that in ubuntu 12.04 Jun 03 23:11:42 micahg: do you know a work-around? Jun 03 23:13:28 if you haven't tried Debian unstable or testing recently, I'm saying that it might have been upstream GNOME that restricted it, as for associating, does a ~/.mailcap file help? Jun 03 23:13:49 #ubuntu might be able to help further Jun 03 23:15:51 hmm.. the irc client just crashed Jun 03 23:51:13 today comes my pandaboard \o/ Jun 03 23:51:47 hmm... *will be delivered Jun 03 23:51:51 so ^^" Jun 03 23:53:08 at #ubuntu there is no help for changing file associations Jun 03 23:53:39 quite frustrating Jun 03 23:55:59 janrinze2, so you say, there is no way to define to use e.g. mplayer for avis? Jun 03 23:56:46 hmm... i'm quite tired... so my grammar is getting worse and worse Jun 03 23:59:27 nope only select from the list that is presented Jun 04 00:08:30 nice... **** ENDING LOGGING AT Mon Jun 04 02:59:58 2012