[02:40] ehlo localhost [02:40] I want to ascertain the delta between debian's ARM v5 toolchain and Ubuntu's ARM v7 [02:41] I'd like to build ARM v7 debs for the BeagleBoard [02:58] jeremiah: Create an Ubuntu chroot and build a package? [02:58] jeremiah: or use a wrapper to pass -march=armv7 to gcc [03:00] lool: Wow. Sounds pretty easy. :-) [03:00] Thanks! [03:02] lool: heh. I'm here with you at DebConf. :) === jkridner_ is now known as jkridner === hrw|gone is now known as hrw [08:02] morning === JaMa|Off is now known as JaMa|Wrk [08:25] amitk: i just got our .35 master kernel working on my panda [08:25] cooloney: cool! I see that SMP does not work? [08:25] amitk: yeah, SMP got some build error. [08:25] amitk: i already got a patch to fix that. [08:26] amitk: but got another building error [08:26] cooloney: nice! [08:26] cooloney: no patches in tony's tree for these? [08:26] but if you wanna single core Ubuntu kernel for omap2/3/4, it is ok now [08:27] amitk: i don't find that. i guess smp was never enabled in single kernel for omap2/3/4 [08:27] cooloney: it is a good first step I think [08:28] amitk: yeah, works fine with console=ttyS2 and the maverick rootfs built from rootstock [08:28] amitk: but i plan to spend sometime to take a look at the smp things. [08:29] cooloney: you should probably check if this has been discussed on linux-omap [08:29] amitk: since i turned off smp config in our master omap flavor [08:29] cooloney: understook [08:29] understood [08:30] amitk: no problem. [08:46] amitk: i saw an email from Tony in linux-omap mail list. [08:47] CONFIG_SMP we can't enable as that requires various ARM changes [08:47] to work on unicore systems. But hopefully we can enable that too [08:47] at some point with select SMP if ARCH_OMAP4. [10:01] cooloney: Have you tried to boot the latest daily build on the Panda yet? [10:01] Come to think of it, has anyone? === XorA|gone is now known as XorA [10:03] ogra: ? --^ [10:20] lag: not yet. any issue? [10:20] i just tried kernel. [10:27] You tell me :) [10:27] http://paste.ubuntu.com/472128/ [10:39] cooloney: --^ [10:40] lag: no idea about that. that's from daily image? [10:41] lag: there was no much chage recently [10:42] I'm waiting to hear back from ogra_cmpc - ogra === amitk is now known as amitk-afk === htc-linux is now known as dcordes_ [11:22] while creating a maverick ubuntu-netbook rootfs rootstock freezed on [11:22] * Installing 2 assemblies from libappindicator0.1-cil into Mono [11:22] now I would just start over but it is like the 5th failed rootstock image in a sequence and I really don't want to [11:23] is there a way to manually intervene w/o losing the entire progress again ? [11:31] I am running ubuntu lucid and the rootstock version used is rootstock 0.1.99.4 [11:39] lag, still rsyncing here, i havent tested the image yet, is that with the default boot.scr ? === asac_ is now known as asac [11:48] ogra: No [11:49] ogra: It's with console=ttyUSB and console=tty2 set [11:52] lag, but no hdmi options ? [11:55] Nope === amitk-afk is now known as amitk [11:57] weird [11:57] i'll try here soon, rsync just finished [11:58] ogra: can you please comment on the rootstock problem ? [11:59] dcordes_, build ubuntu-minimal and install the rest under real hw (or in the vm you will use the rootfs) [12:00] ogra: I did this before. iirc I had the same error installing netbook manually then [12:03] well, it works for others this way [12:06] ogra: if I see the same error during ubuntu-netbook install, do you recommned a workaround ? [12:06] there is no workaround [12:06] ogra: I know it is possible to remove mono. I did this on my current ubuntu-desktop rootfs [12:07] if it also fails for you on real hardware thats a different issue to failing on rootstock [12:07] ogra: do you think it might be related to using lucid on the host machine ? [12:07] that mono installation fails in cross arch chroots is a known issue thats not fixable unless mono changes [12:08] if it fails on real hardware, thats not known to me so likely a new bug but completely unrelated to mono being uninstallable in rootstock [12:09] ogra: ok then possibily what I have seen before was just coincidence - or rather related to the fact that mono is such a huge mess that it is not really coincidental it has tons of bugs [12:10] ogra: anyway I will try it that way and let you know. [12:10] 66M armel-rootfs-201008021300.tgz [12:10] is that expected maverick ubuntu-minimal size ? [12:11] likely bigger [12:23] ogra: likely ? how big ? [12:24] no idea, 120M ? [12:24] lag, todays image works fine with my monitor [12:32] ogra: its 160 uncompressed... [12:34] k [12:35] wow [12:35] resizing became really fast with the new inode structure on the image [12:36] like under 2min [12:36] for a 4G Sd [12:37] ogra: you guys should add the mono problem in the manpage [12:37] ogra: so people don't waste hours and hours like me. [12:38] there are open bugs about it [12:38] ogra: about documenting it or fixing it ? [12:38] about the brokeness [12:41] ogra: I can not see it. Do you have a link ? [12:42] Bug 610719 [12:42] Launchpad bug 610719 in mono (Ubuntu) "Mono hangs while running with qemu ARM user emulation (chroot) (dup-of: 530000)" [Undecided,New] https://launchpad.net/bugs/610719 [12:42] Launchpad bug 530000 in qemu-kvm (Ubuntu) "mono assembly installation under qemu-arm-static hangs (affects: 2) (dups: 1) (heat: 30)" [Medium,Won't fix] https://launchpad.net/bugs/530000 [12:42] ogra: what is 'user emulation' ? [12:43] chroot [12:51] Bug 612504 [12:51] Launchpad bug 612504 in project-rootstock "documentation: add a note on mono problem (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/612504 [12:59] morning [12:59] let me read the log [13:00] rsalveti: morning. now the rootstock team is complete :D [13:01] dcordes_: see https://wiki.ubuntu.com/ARM/RootStock/KnownIssues [13:01] this mono issue is already there [13:01] this sucks in so many ways hehe [13:02] rsalveti: yes in the wiki... yeah truly sucks [13:03] mono tries to read many files from /proc [13:03] will try to map the memory and so on, giving lots of seg faults [13:04] with qemu vanilla you'll just get a seg fault instead of a hang [13:04] I'd recommend you to not install this package, or try rootstock in a real arm hardware, avoiding qemu [13:05] if you want to generate a bigger image [13:05] or, fix the mono bug :-) [13:06] ogra: you mean, by just changing the image to add more inodes the resizes now takes less minutes? [13:08] mythripk: Ping [13:09] rsalveti: I was advised to do this already [13:09] rsalveti: thanks [13:09] rsalveti: I think it must be added in the direct documentation of the program until it is fixed upstream. [13:09] or in rootstock [13:10] dcordes_: ok, we could just add this link into rootstock's man page, would that be enough? [13:10] the known issues link [13:10] rsalveti: yes [13:13] rsalveti: additionally one could edit the wiki to draw more attention on the mono thing, i.e. moving it top and stating clearly it makes every rootstock seed fail that contains mono. [13:13] rsalveti: isn't that pretty much everything but ubuntu-minimal ? [13:13] I tried to login with my ID but wiki gives me error. [13:14] rsalveti, yeah, it finishes after the first pass instead of doing four and has no write time at the end as we had it before [13:14] dcordes_: yep, at least when related with the big ubuntu meta packages [13:15] dcordes_: sure, we can change that in the wiki too [13:15] rsalveti: ok. I think that should be mentioned in the wiki then. could you add it ? [13:15] thanks [13:15] ogra: haha, that's nice :-) as a side effect of your problem we solved another one [13:15] yeah [13:16] i first thought it was crashed since it was so breezing fast [13:16] with all the bug reporting I would like to thank you for the program. it is a really good approach [13:16] but it properly resized to 4G [13:16] s/with/beside/ [13:16] * ogra tries on the XM next [13:17] ogra: cool, will also try on my beagle [13:17] well, the C4 will likely see OOM [13:17] dcordes_: nice, thanks [13:17] at least after the installation [13:18] ogra: plymouth always gives an OOM [13:18] even if you get a very basic image with rootstock [13:18] that should be gone since a while [13:18] well, I tested 3 days ago [13:18] with what image ? [13:19] we didnt build any since mid of the sprint [13:19] a very basic image, created with rootstock, but using the latest kernel package, after generating the uInitrd [13:19] hmm, k [13:19] thats bad [13:19] yep [13:19] there were plenty kernel changes and one fix to ureadahead that should prevent the crash [13:20] will try again today, it's easy to test [13:21] do we have bugs for this issue already? [13:21] yep, i think so [13:22] Bug 600359 [13:22] Launchpad bug 600359 in ureadahead (Ubuntu Maverick) (and 1 other project) "ureadahead generating oom messages during boot. (affects: 1) (heat: 12)" [Medium,Confirmed] https://launchpad.net/bugs/600359 [13:23] thanks [13:58] NCommander: ping [14:00] mythripk: ping [14:38] hrm, resizinmg on the XM fails [14:39] seems it detects the SD as readonly media [14:39] weird [14:42] r/o? yea that is rather odd [14:46] r/o or write protected? [14:46] it says it cant access mmcblk0 in readwrite mode [14:46] it being sfdisk [14:47] checked what kernel log said? [14:47] oopses all over [14:47] and OOM all over [14:47] which is weird [14:48] I mean what kernel said about sd card [14:49] npitre: you're still nico at marvell.com? [14:49] no idea, it hardlocked after oem-config was done and now it doesnt boot anymore [14:50] so no access to dmesg [14:50] npitre: if not, http://ksummit2010.kernel.org/nominated-list should be updated [14:51] ukleinek: npitre is with canonical now and he is currently on vacation [15:18] ogra: did you have time to review and push the rootstock debdiff? [15:19] amitk: thanks [15:21] dyfet: pong? [15:21] hey, where are you this week? [15:22] dyfet: NYC, and DebConf 10 (partially) [15:22] ah, okay, excellent [15:22] dyfet: where are you? [15:23] home === ogra_ is now known as ogra [15:42] rsalveti, uploaded [15:42] ogra: nice, thanks [16:13] lag: u pinged ? [16:14] mythripk: I did [16:14] mythripk: http://paste.ubuntu.com/472128/ [16:15] ogra: Anything I should know about today's images? I'm currently flashing SD cards and getting ready to boot. [16:16] GrueMaster: Check out my paste above [16:16] lag:do you have all the patch set ? I guess you missed a patch from dispc === fta_ is now known as fta [16:17] oops .. :*do [16:17] i guess you have missed one dispc patch [16:18] This is nothing to do with me [16:18] This is our live daily builds [16:18] I don't think your patches have gone in yet [16:18] Unless cooloney ... [16:18] Wait one [16:19] lag: I guess this patch is missed http://dev.omapzoom.org/?p=axelcx/kernel-display.git;a=commit;h=2cf64e365a7ca4d7c16ab5a2858f8b0397afcf82 [16:20] lag:From the log it is crashing at the wait_for completion [16:20] can you check that / [16:21] and this is patch from the tree im talking about , not the one's that had EDID change [16:28] mythripk: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=56d2530e9a9b99188daf71855518672d80e795b0 === trip_away is now known as threezero [16:32] lag:If im not wrong isnt this 11days old tree and the one's you were all using ? Also was this a one off event or is this always seen ? . I had seen this without the above mentioned patch [16:34] I believe this is the one we are using [16:34] This is the first time I've seen this error [16:36] k , Im at home now , let me try out tomorrow to see if i can in anyway reproduce this , because i have not seen this before(with the HPD irq handler patch. === bjf[afk] is now known as bjf [16:38] mythripk: Okay. Well our branch is here if you want to take a look to see what's applied and what isn't [16:38] mythripk: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4 [16:38] I have only seen this happen with my monitor - others are okay still [16:40] sure i have link to your tree, It doesnt have to do with the monitor.. I guess you would not see this again if you reboot do u? [16:45] lag, we're definitely missing the patches from robclark [16:48] GrueMaster, i see some weird behavior on my XM, the panda image is awesome, thw new changes speed up resizing significantly [16:48] Are the new XMs out yet? [16:48] no [16:48] Mine still has a memory issue [16:48] there is a uboot patch that might fix it [16:49] i wont be able to update uboot before A3 though [16:49] I thought it was hardware? [16:49] both i guess [16:49] there is surely also a _HW issue [16:50] i dont see any memory issues though, what i see is that sfdisk fails with a weird error that seems to indicate the SD is locked [16:53] With the latest image? [16:54] yep [16:54] while the omap4 image works like a breeze, the omap3 one on the XM is failing badly [16:55] mythripk: I'll test it and let you know [16:55] mythripk: Ping me tomorrow morning [16:55] mythripk: Enjoy your evening [16:56] ogra: Thanks. I don't have an XM yet. I will be getting JamieBennett's in a couple of weeks while I'm in Oxford. [16:56] hrm [16:56] jamies is pre-production [16:56] that should be replaced first [16:57] ogra: XMs are pre-production anyway [16:57] I have the panda image up and sitting at oem-config already. [16:57] hrw, well, but there are some that are closer to the final product than others [16:57] hrw, the ones i'm talking about dont even boot with the same uboot [16:57] Well, any way we look at it it is easier for me to hand-carry it back & get a replacement from Tx. [16:57] auch [16:58] GrueMaster, awesome, please check the rootfs size etc (assuming the resizing was as fast for you as it was for me) [16:58] fdisk -l and df output :) [16:59] It looked pretty fast. What changes did you make? [16:59] i changed the inode allocation on the original image [16:59] ah [16:59] by default the gap between two inodes is 4096 bytes ... i doubled that [17:00] Not seeing it in livecd.sh bzr branch. Need to check my copy. [17:00] it was uploaded [17:00] else you wouldnt see it in the image [17:01] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/livecd-rootfs/maverick/revision/117 [17:01] ah, there it is. [17:02] I had a glitch at the same time I did a pull. [17:02] ah === fta_ is now known as fta [17:02] Funny how easy it is to lose track of what is going on when you have 5 systems running on 4 monitors. [17:02] heh, yeah [17:03] add 3 keyboards and mice you shuffle between these :) [17:03] My office looks like the control desk from the matrix. [17:03] hehe [17:03] Only 3? [17:03] how did your monitor behave with the panda image btw ? [17:04] Didn't. Had to reboot with the dvi settings as before. [17:04] I don't have an HDMI monitor. [17:04] oh, right [17:04] i was just wondering if you saw the same issue as lag [17:05] he apparently hits an oops from the display code [17:05] Nope. I didn't see anything. :P [17:05] GrueMaster: brunets, blonds etc? [17:05] I boot once. If no vid, then I add the cmdline parameters for video & serial console. [17:06] be careful that you dont shut down in the middle of the resize :) [17:06] hrw: I'm partial to redheads. [17:06] No, I still have enough serial console to see when a reboot takes place. [17:06] ah, k [17:07] And besides, if I do for some reason, I usually reflash before moding the cmdline. [17:08] btw ... https://edge.launchpad.net/ubuntu/maverick/+source/ubuntu-netbook-efl-default-settings/0.2 [17:08] if you see any issues with panels or applets in the efl session, its likely that the settings arent right yet, please file against the above package [17:08] for now its just a copy of the unity settings with very few mods. [17:09] Ok. [17:09] i will fix that during A3 prep [17:09] but need to know whats missing ... [17:09] A3 is this week. [17:09] the next build will have it in it [17:09] thu, yes [17:09] ok [17:10] freeze starts tomorrow morning, but the package is arch specific anyway so i'll get exceptions as needed [17:10] and after all its all bugfixes :) [17:10] yep. [17:11] GrueMaster, oh, and also please watch the launcher closely, asac is just preparing an upgrade to latest upstream, tomorrows image will have it [17:12] joy. [17:12] i'm a bit worried we get some untested code in [17:12] (though i'm happy asac does it, striked off one TODO from my list :) ) === JaMa|Wrk is now known as JaMa|Off [17:38] rsalveti: ping [17:39] prpplague: pong [17:39] rsalveti: zippy and zippy2 support, you planning to have that in 10.10 , correct? [17:40] prpplague: that's the idea, but we still need to upload the patches for review, and wait to see if it gets approved for 10.10 [17:40] rsalveti: 10.10 is going to be based on 2.6.35 kernel? [17:40] I just got a few patches and will start looking what can be sent to our upstream kernel [17:40] prpplague: yep, that's the idea [17:41] rsalveti: dandy thanks [17:41] prpplague: but I can only test zippy2, as I don't have a zippy 1 board [17:42] rsalveti: prpplague for sure can test z1 ;d [17:42] rsalveti: did you already send me your contact info? [17:42] I think dyfet also has a zippy one [17:43] prpplague: nops [17:44] rsalveti: please send me your shipping and contact info to danders@tincantools.com [17:44] prpplague: sure, will do it now, thanks [17:45] I do have it [17:46] The ethernet works on it [17:46] serial and sd too? [17:47] probably needs additional patches [17:47] I had not tested those...I could do so quickly. I was surprised when the ethernet worked on the latest kernel ;) [17:48] dyfet: yep, at least the ethernet port should work, as this is the default in the kernel [17:48] for zippy 2 we have to change it and find out the argument from u-boot [17:49] dyfet: yea the enc28j60 support has been there for awhile and is pretty decent [17:49] * prpplague wrote the first enc28j60 driver for 2.4 kernel [17:50] well, I do have a device node for ttyS3....no device node for the other mmcblk device, though [17:51] dyfet: the additional uart should be on ttyS1 iirc [17:52] I have S0-S3 [17:53] dyfet: we generally test the uart with a serial loop back connector and a uart loop back app [17:53] I used to have a serial loopback plug... [17:53] rsalveti: i'll include a loopback connector when we send the zippy [17:54] prpplague: nice === amitk is now known as amitk-afk [17:57] the zippy serial works [17:57] I started a getty to login on it, and it came up...ttyS1 [17:59] prpplague: sent [17:59] have a nice rest of day === hrw is now known as hrw|gone [17:59] dyfet: dandy [17:59] rsalveti: got it [17:59] dyfet: nice to know, can you check the sd? [18:02] It works too! at least as far as dmesg tells me when I stick a sd in... [18:02] and it gave me the dev nodes for the partitions on that sd...so it seems to read it [18:03] dyfet: great [18:03] so you can basically test if I'm breaking zippy 1 instead of making it work :-) === fta_ is now known as fta === XorA is now known as XorA|gone === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta [19:39] bad news [19:41] I did what you told me [19:42] Hello, I'm working on iPhone port of Ubuntu, I'm using the evdev driver for the touchscreen. This works perfecly when the screen is in a portrait orientation. [19:42] james [19:43] I'm now working on a landscape orientation, I have the framebuffer landscape and have used swapaxes and invertY in xorg.conf [19:43] I know how to solve the prob for tslib [19:43] The touchscreen works fine and is acting correctly, but the top section of the screen is now "untouchable" I also cant "drag" the mouse up there. [19:44] you need to add a rotate option in the input section for the tslib. [19:44] Is there a touchscreen calibration tool for evdev [19:44] oh ok [19:44] that is something different then [19:44] never seen untouchable area [19:45] how about trying tslib [19:45] dcordes: I have to use evdev, I've tried installing tslib evtouch and mutouch from .deb and the latest from source, non pick up the touchscreen automatically or configured manually using xorg.conf, [19:46] do you set the correct env variab.le. ? [19:46] Hm, what/where is that? [19:46] TSLIB_TSDEVICE=/dev/input/eventn [19:47] it is in the manpage [19:47] Yes I've done that then have tried using the tslib calibrator [19:47] ogra ping [19:47] Simply said It could find the touchscreen device [19:47] ok [19:47] it couldn't sorry [19:48] are you 100% you set right fevice? [19:48] Yes [19:48] It's /dev/input/event1 [19:48] Confirmed using the evdev driver [19:48] And also by using cat /dev/input/event1 [19:49] ok [19:49] typo? [19:50] Nope, worked on trying to get tslib working for a few days, I won't have typo'd the entire time [19:51] aight then [19:52] The touchscreen works fine in portrait [19:53] It's also quite accurate [19:53] evdev mailing list ? [19:53] It's almost as if the the resolution is wrong, but I've tried switching the MaxX and MaxY values [19:53] The touchscreen behaved the same [19:54] dcordes: I've tried googling the hell out of it, I have a feeling that using xinput might do the trick, I just can't get my head around the syntax [19:54] uhm [19:54] not google [19:55] write email to evdev mailing list [19:55] Ok, I'll see what they say [19:55] or tslib..... [19:55] Doesn't evdev have an option to change orientation? [19:55] btw [19:56] Seems to me I remember something like that. [19:56] how can I get in touch w/you james [19:56] I want to help your project [19:56] dcordes: I'm available in irc.osx86.hu in #ix , my projects blog is ixproject.org [19:57] cool [19:57] GrueMaster: I've managed to change the orientation, I now have a section at the top of the screen I can't move the mouse to [19:57] where is the rootstock crew when you need them :p [19:58] dcordes: Ping rsalveti. He's been fixing it up recently. [19:58] james are you using the ma maverick? [19:58] Nope, I can apperently only use Karmic [19:59] Armv6 support was dropped with Luci [19:59] dcordes: yep, need anything? [19:59] * dcordes slaps WinCE on screen keyboard for stuttering [20:00] * JamesWstubbs91 slaps his keyboard, for the hell of it [20:00] rsalveti hi [20:01] cross installed ubuntu-minimal [20:01] hi [20:02] natively installed ubuntu-netbook in it [20:02] likr 2GB of it [20:02] like [20:02] ok [20:02] errored on mono [20:02] while running it on a native environment? [20:03] but at a different point than the known qemu one [20:03] yes. [20:03] Anyone got anymore ideas on my evdev issue before I dissapear into repeated trial and error insomnia ? [20:03] dcordes: argh, mono does sucks [20:04] lol dont [20:04] Ok, thanks anyway [20:04] write tslib than evdev ml and wait. [20:04] dcordes: what distro version are you using? lucid? [20:04] dcordes: I can test it here, but please try to see if there are any bugs reported already at launchpad [20:05] host or target? [20:05] dcordes: target [20:05] target maverick [20:05] host lucid [20:05] ok, mono on maverick may be broken, never tested [20:05] rootstock latest [20:06] I'm just creating a new maverick rootfs, will try to install ubuntu-netbook on it [20:06] I did same thing before and think err was same [20:06] dcordes: what error are you getting? [20:07] so its not me [20:07] freeze on [20:07] =\ [20:07] installing two foo of bar into mono [20:08] I noted it [20:09] but can't loop mount ext2 in wince :> [20:24] ogra, meant to be here... [20:34] rsalveti, do you know how to work around such error? [20:35] not yet, it's supposed to work when installing it in a native environment, that's why I'm testing it [20:36] but the repo just got out of sync, will try again in some minutes [20:41] cool thanks a bunch my friend === fta__ is now known as fta === fta_ is now known as fta [21:37] rsalveti, got past mono in your test install yet ? [21:46] GrueMaster: what arguments are you using on panda to get the serial output from kernel? [21:46] it seems mine is freezing during boot, and I want to get the kernel log to check it [21:46] also using an lg monitor, seems the one that lag was also using [21:47] rsalveti: console=ttyO2,115200 console=tty0 for serial console. [21:47] GrueMaster: that explains why ttys2 doesn't work :-) [21:47] GrueMaster: thanks man [21:47] Is your monitor HDMI? [21:48] GrueMaster: yep, hdmi and dvi [21:48] Ok. I don't have an HDMI monitor, so I have to force the mode. [21:48] GrueMaster: the monitor detects the signal only when I'm using the hdmi port with a hdmi->dvi adapter [21:49] GrueMaster: oh, ok, so to use the dvi what argument should I use? [21:49] omapdss.debug=1 omapdss.hdmimode=0 omapdss.hdmicode=35 [21:49] dcordes_: doing it right now, waiting lots of packages to get installed :-) [21:49] The debug part just adds more messages to the log. [21:49] GrueMaster: nice [21:50] GrueMaster: is there a wiki listing these arguments or something like that? or the source code is the only documentation? :-) [21:50] Yes. Let me find the link. [21:50] rsalveti, I think it took around 3 hours until I arrived tat the mono error starting from ubuntu-minimal [21:50] dcordes_: ouch [21:50] rsalveti, with 1000MHz cpu clock and ~390MB ram [21:51] ok, so ping me in a few hours :-) [21:51] rsalveti, my rootfs lives on a class4 uSD it might be the bottleneck [21:51] I have one class 6 that GrueMaster gave me, but I always get some weird errors on beagle [21:52] so I'm basically using the old c4 too [21:54] rsalveti: http://omappedia.org/wiki/Bootargs_for_enabling_display [21:54] GrueMaster: nice, thanks again === fta_ is now known as fta [22:07] GrueMaster, do I also get a GrueMaster class6 uSD ? [22:13] :( [22:13] it would certainly be useful investment [22:13] some 4 or 8G with class 6 [22:20] dcordes_: Sure. Log in to amazon.com... [22:21] rsalveti: What issues are you seeing with the class 6 I gave you? [22:22] GrueMaster, maybe it's 2fast for the beagle so it gets hick ups [22:22] ;> [22:22] rsalveti, how much space does your maverick take up so far ? (I kept typing 'df -h' during the install) [22:22] * dcordes_ is an impatient person [22:23] sorry :) [22:23] dcordes_: There is a known issue being worked on in the current kernel for beagle. Bug 591941. [22:23] Launchpad bug 591941 in linux (Ubuntu Maverick) (and 1 other project) "SDHC card not recognized (affects: 2) (dups: 1) (heat: 80)" [High,In progress] https://launchpad.net/bugs/591941 [22:24] GrueMaster: I got some i/o errors with it, at least on beagle [22:24] but don't remember if it was lucid or maverick [22:24] I found that class 4 cards are the only ones that work reliably on beagle at the moment. [22:24] I need to test it again [22:24] GrueMaster, hmm don't get this wrong but don't you think that's something to discuss upstream with rwhitby and friends ? [22:24] GrueMaster, to me it looks malplaced in ubuntu bugtracking system [22:24] dcordes_: Kernel team is already on it. [22:25] well ok if you have some mechanisms to pass it upstream.. [22:25] argh, forgot to watch for the reboot and now my console arguments are gone [22:25] then I didn't say it :) [22:25] I report the bugs, others fix them. :P [22:25] GrueMaster, forgot you guys are actually no small community but massive company :) [22:26] Other way around. Small company, massive community. [22:26] :P [22:27] GrueMaster, are you also canonical employee ? [22:27] dcordes_: I'm using just one serial, so let's just wait some more :-) [22:27] I'd tell you, but then I'd have to pkill you. :P [22:27] haha === bjf is now known as bjf[afk] === fta_ is now known as fta [23:07] somebody knows how to extract a single filesystem (as file) from a raw device image ? [23:07] that has bootstectore multiple partitions etc [23:07] the beagle sd images use such raw file [23:12] I would just write it to some SD device node but don't have such as I work in remote vm [23:17] Are you talking about mounting a partition from maverick-preinstalled-netbook-armel+omap.img? [23:22] dcordes_: ^^^ [23:22] GrueMaster, no. meego :D [23:22] GrueMaster, but it's same [23:22] GrueMaster, some raw image supposed to be copied to sd [23:22] Not familiar with that image, but you should be able to get the start sector with "file [23:23] x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 32, 3320288 sectors; partition 2: ID=0x83, starthead 3, startsector 3320320, 499968 sectors [23:25] Ok. Now, say you want to mount partition 2. sudo mount ./mnt -o loop,offset=$((512*3320320)) [23:25] The starting byte offset is what is needed. [23:25] And each sector should be 512 bytes. [23:37] dcordes_: did that work for you?