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