=== asac_ is now known as asac [04:47] i [04:51] i'm having some problems unzipping a tar file to copy to a partitioned 4mb stick for an arm processor using ubuntu anyone know what i need to do to get the zip file to a tar file and copy that to a Dreamplug using a marvell processor? [04:53] oops ^ using the marvell processor [04:55] i'm on the serial port using gtkterm now i have the directory set [04:59] the zip files on an x86 won't let me unzip those files because it needs marvell processor [04:59] i need a work around [05:00] current prompt is: dreamplug-debian:/media/usb0# [05:38] errors i recieve are: tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Error exit delayed from previous errors [05:41] the zip files on an x86 won't let me unzip those files because it needs marvell processor [05:43] or it's partitioned to for use of the marvell processor anyways the unit does not have a unzip program and ubuntu for x86 won't work [05:45] well maybe i'll work on it again tommorrow :) [06:12] Hi all [06:13] where can i find ffmeg for ubuntu-arm natty [06:15] by xbmc build giving error "checking for FFMPEG... no [06:15] configure: error: Could not find a required library. Please see the README for your platform." === lag` is now known as lag [07:38] morning === Guest5698 is now known as zumbi === jkridner_ is now known as jkridner [13:52] Hi! I'm trying to run ubuntu on pandaboard and after the boot logo the monitor goes to powersave mode. Do you have any idea what can be the problem? [14:02] kapinter, what's the message at serial terminal [14:04] siji: Uncompressing Linux... done, booting the kernel. [14:05] what's your bootarg [14:05] siji: I can't get the logs... [14:06] I was trying to setenv serialtty=ttyS2 but no luck [14:07] do you mean : mmcargs=setenv bootargs console=${console} vram=${vram} root=${mmcroot} rootfst} [14:07] loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr [14:07] bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr} [14:07] loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage [14:07] or how can I check it? [14:09] do you have any boot.scr at fat32 partition ? [14:11] let me check [14:15] yes [14:15] it says [14:15] fatload mmc 0:1 0x80000000 uImage [14:15] fatload mmc 0:1 0x81600000 uInitrd [14:15] setenv bootargs quiet splash ro elevator=noop vram=32M mem=460M@0x80000000 mem=256M@0xA0000000 root=UUID=9b2c0572-4d5f-43d7-b79b-745f2423fbe6 fixrtc [14:15] bootm 0x80000000 0x81600000 === prpplague is now known as prpplague^2 [15:59] ogra_, you about? [16:04] lilstevie: I think he is out on holiday until next week. [16:04] ah ok [16:04] well someone else may be able to help me anyway :p [16:05] I was looking at the flash-kernel stuff for the AC100 [16:05] and I am just wondering about modifying for my device [16:06] cause my kernel partition has the potential to be in different partitions [16:07] like it could be mmcblk0p7 p8 p9 or p10 [16:09] lilstevie: So, ogra's code ended up picking a specific partition as a convention, rather than giving the user full flexibility. [16:10] Ideally, you want to have that sit in a configuration file, and either inform the user you put it in some specific place (which depends on the model, the eMMc layout, etc.), and let the user modify it if they want to drop it somewhere else. [16:11] persia, well given my system I really could do with user config [16:12] cause like with the whole dual boot thing, [16:12] persia, so far it is just p9 or p10 [16:13] Right. So, what you do is when you run the installer, you offer the user the choice of how they want to do it, and then you store their choice in the initial configuration file., [16:14] but once I start giving the option for pure ubuntu installs that will expand even more [16:14] so far I am running now with straight ubuntu but android stuff is still in tact :p [16:15] recovery mode is booting with single appended to the cmdline :p [16:25] It's really about the installer: I'd recommend using a very flexible architecture (boot from anywhere: so have configuration that specifies all the variables), but try to present the user with choices that are based on something obvious, rather than partition names, and do the right thing. [16:26] Advanced users can fiddle things to their heart's content. Unsophisticated users can rely on the installer just doing the right thing. [16:26] well the tegraparts names are set in stone [16:26] :P [16:27] LNX and SOS are required by the bootloader to find the kernel and recovery kernel [16:35] Right, but one can't promise that those are in specific places for a specific marketing name for a device. [16:36] The translation between eMMc partition numbers and labels differs for different devices called "ac100", and "dynabook az", and any correlation between those groups is additionally accidental. [16:38] yeah well in this case the Hardware name is ventana [16:38] which means there could be many many more configs :p [18:28] janimo: did you test build bug 816053 on amd64 or i386 (figure it's faster than armel)? it'll most likely fail due to the switch to system mozjs [18:28] Launchpad bug 816053 in oolite "Sync oolite 1.75.3-1 (universe) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/816053 [19:48] I try to install libc6 but all i get is "dpkg: error processing libc6" - can anyone help? [19:57] "subprocess installed post-installation script killed by signal (Illegal instruction)" [20:00] micahg, thanks for the catch, I forwarded the issue to BTS [20:00] janimo: which issue? Debian won't have mozjs185 so they'll close wontfix [20:02] micahg, that one, ok. I saw one email thread where it was discussed it could go to experimental.But if they don't it'll get fixed in Ubuntu [20:03] well, that would be nice if it did end up in experimental [20:04] * micahg subscribes to the Debian bug === prpplague^2 is now known as prpplague