[00:22] <ework> mattman, ok X works it just doesnt seem to like using a DVI to VGA adapter also since its using a framebuffer you can't change the resolution
[00:42] <ework> mattman, added some minor changes about the framebuffer device node and using DVI directly which fixes my X11 problems
[00:43] <ework> mattman, should be sufficient now for someone to get an ubuntu desktop running on that board
[00:44] <mattman> ework: so what are the parameters you're passing into the frame buffer?
[00:44] <ework> nothing just created the device node
[00:44] <ework> it works at 1024x768x60 without any changes
[00:44] <mattman> ework: that's good to know
[00:46] <ework> mattman, yah there should be enough tips and instructions there now to get ubuntu 10.04 installed from scratch
[00:47] <ework> mattman, to the desktop
[00:47] <mattman> ework: great
[00:48] <ework> mattman, thanks for your help I wouldn't have gotten this far without your pointers
[00:50] <GrueMaster> Great.  Now I am seeing soft lockups on cpu0.  Very frustrating
[01:13] <cooloney> hquit
[03:05] <rsalveti> GrueMaster: with beagle or panda?
[03:09] <prpplague> the beanda
[03:09] <prpplague> evening folks
[06:47] <GrueMaster> rsalveti: Panda.  And I'm out for the night.
[06:47] <rsalveti> GrueMaster: with the latest kernel?
[06:47]  * rsalveti also needs to get some sleep :-)
[06:48] <GrueMaster> Not sure.  20100809 build + updates.  Not your kernel.
[06:48] <GrueMaster> Had to update to get the latest oem-config before filing a bug against it.
[06:48] <rsalveti> GrueMaster: hm, because 2.6.34-903-omap4 should be our latest
[06:48] <rsalveti> and we got an update to this version days ago
[06:48] <rsalveti> so it could be a regression
[06:49] <GrueMaster> I think 902 is on the image.  Not sure what was pulled with the update.
[10:48] <lag> mythripk: ping
[10:52] <mythripk> hi lag
[10:54] <lag> Hey :)
[10:55] <lag> I'd like to pull your (and robclark's) patches to make my Panda work
[10:55] <lag> What commit shas do I need?
[11:22] <lag> mythripk: ?
[11:24] <mythripk> lag : do you want me tosend
[11:24] <mythripk> the commit id's of mine and rob's patch ?
[11:25] <lag> mythripk: Yes please
[11:25] <mythripk> 1 sec
[11:25] <lag> Thank you
[11:32] <mythripk> http://dev.omapzoom.org/?p=axelcx/kernel-display.git;a=shortlog;h=refs/heads/display-next
[11:32] <mythripk> from  commit 0ec1de9609d2b42bf47f63f9e8a4a50de30b381e- Patch to Enable autodetect with EDID in HDMI
[11:33] <mythripk> to b128c1648c6f0d39645f0424ac45a5c5b848bcc0 HDMI:Move the functions from HDMI Irq handler to work queue
[11:37] <ogra> grmpf
[11:59] <lag> mythripk: Just those too?
[12:00] <mythripk> entire set from the first commit
[12:00] <mythripk> to the last one in that path
[12:48]  * ogra whacks d-bus
[13:01] <ogra> why the heck do i get an exec format error running a python app ... damned
[13:04] <amitk> ogra: stop compiling python apps :-p
[13:05] <ogra> amitk, heh, tell that to the oem-config guys
[13:07] <ogra> i dont think its python spilling the error but a subprocess it calls
[14:49] <ogra> GrueMaster, do you have any beagle that boots the current image ?
[14:49] <ogra> GrueMaster, so that you could test if oem-config fails the same way on omap3
[15:25] <GrueMaster> ogra: I had it doing upgrade testing, but will try it today.
[15:27] <GrueMaster> Also, I had already filed a bug yesterday on oem-config yesterday.  Bug 616581.
[15:27] <ubot2> Launchpad bug 616581 in ubiquity (Ubuntu) "oem-config fails to run (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/616581
[15:29] <lag> ndec: Hi
[16:03] <rsalveti> lag: http://gitorious.org/ubuntu-experimental/kernel-maverick/commits/rsalveti-ti-omap4
[16:03] <rsalveti> the patches I'm using for the monitor issue
[16:03] <rsalveti> the 9 patches I got from mythripk plus some more from robclark that I got to test the dvi support
[16:04] <rsalveti> lag: do you have any plan to merge any of these patches?
[16:04] <rsalveti> I know you have a similar monitor :-)
[16:05] <lag> rsalveti: We have plans to
[16:05] <lag> rsalveti: I'm looking at it right now
[16:05] <lag> rsalveti: They should be in there by Testy Tiger
[16:08] <GrueMaster> lag: I hope you aren't referring to an ubuntu release by that name.
[16:09] <lag> GrueMaster: Yep
[16:09] <rsalveti> haha
[16:09] <GrueMaster> Jesh.  You aussies are slow... :P
[16:09] <lag> =:-D
[16:09] <lag> GrueMaster: Don't make me get personal
[16:09] <GrueMaster> heh
[16:10] <rsalveti> lunch time :-)
[16:10] <lag> The TI tree is a bit of a mess
[16:10] <lag> We're discussing how we should move forward currently
[16:26] <GrueMaster> Bah.  Today's omap4 image hangs past checking rootfs with no indicators.
[16:27] <ogra_cmpc> worked for me
[16:27] <GrueMaster> sigh.
[16:30] <lag> These things always work for the person how develops them ;)
[16:37] <ogra_cmpc> well, i didnt do anything specific
[16:38] <ogra_cmpc> the image behaves the exact same way for me as yesterday
[16:38] <ogra_cmpc> (which was the 09 image i tested)
[16:40] <GrueMaster> And the omap image fails oem-config.
[16:43] <ogra> GrueMaster, ok, thanks, thats what i wanted to know
[16:43] <ogra> can you check in the rootshell if dbus is running for you ?
[16:44] <GrueMaster> I see dbus-daemon --system --fork in the ps ax output.
[16:45] <ogra> weird
[16:45] <ogra> i dont on omap4
[16:46] <GrueMaster> My omap4 doesn't get very far, unfortunately.
[16:46] <ogra> do you see anything in 7var/crash ?
[16:46] <GrueMaster> ubiquity-dm
[16:46] <ogra> only that ?
[16:46] <ogra> i got some more files there on omap4
[16:50] <GrueMaster> My omap4 doesn't appear to have actually mounted rootfs.  Last item is :
[16:50] <GrueMaster> fsck from util-linux-ng 2.17.2
[16:50] <GrueMaster> /dev/mmcblk0p2: clean, 155074/1858304 files, 536382/3895762 blocks
[16:51] <ogra> thats after first reboot ?
[16:51] <GrueMaster> yes.  First boot succeeds.
[16:52] <ogra> very strange
[16:52] <GrueMaster> Between boots, I have to stop and fix boot.scr to get video.  But it is the same settings I have always used, so I don't think they have any influence.
[16:55] <ogra> nah, shouldnt
[16:55] <GrueMaster> And I checked.  Both today's and 0809 have the same kernel.
[16:56] <GrueMaster> (it would be nice to have a manifest to do full image comparisons - hint hint).
[17:18] <GrueMaster> ogra_cmpc: Rebooted panda.  Now I get X (still no oem-config).  Not sure why it started hanging like this.  Works fine with the Alpha 3 image.
[17:19] <GrueMaster> Now it just hands randomly with today's image, or 0809 image manually updated.
[17:20] <prpplague> GrueMaster: you doing any audio on the panda?
[17:21] <GrueMaster> prpplague: Not yet.  Still working on gettng a stable image.  I can go back to Alpha 3 and do more testing there.
[18:22] <GrueMaster> ogra_cmpc: What would I file a bug against to note that the linux-headers-omap4 are not installed on the omap4 image?  We have omap, dove, and imx51, but no omap4.
[18:31] <rsalveti> GrueMaster: the package is there, do you know who should depend on it?
[18:33] <GrueMaster> Not really.  I know the package is there.  Also, I am running the Alpha 3 image at the moment and doing an update, but it doesn't see the linux-image-2.6.34-903-omap4_2.6.34-903.7_armel.deb kernel as an upgrade option, even with dist-upgrade.
[18:33] <GrueMaster> And today's image isn't using it either.
[18:34] <rsalveti> GrueMaster: yep, that's what I saw now
[18:34] <rsalveti> the new package is there but the package linux-image-omap4 is depending on the older one
[18:34] <rsalveti> Depends: linux-image-2.6.34-902-omap4, linux-firmware
[18:34] <rsalveti> that should be the reason
[18:35] <GrueMaster> yea, that would be it.  sigh
[18:35] <rsalveti> now we need to know why it was not updated with the kernel update
[18:40] <rsalveti> hm, is just the meta package
[18:40] <GrueMaster> yes.  But why isn't it getting updated?  Or is it stuck in the build queue?
[18:41] <rsalveti> GrueMaster: could be
[18:42] <GrueMaster> Looks like 903.7 was built on the 7th.  Should have had a meta package by now.
[18:44] <rsalveti> GrueMaster: but the meta package wasn't updated with the kernel package
[18:44] <rsalveti> or should it be automatically updated?
[18:44] <GrueMaster> Not sure.  Something for the kernel team.
[18:44] <rsalveti> let me try to understand how it works
[18:44] <rsalveti> argh, and we had the new kernel days ago and because of this you're testing an older version =\
[18:45] <GrueMaster> yep.
[18:46] <GrueMaster> Of course the images, while building, are currently broken due to bug 616581.
[18:46] <ubot2> Launchpad bug 616581 in ubiquity (Ubuntu) "oem-config fails to run (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/616581
[18:46] <GrueMaster> Which is why I am running A3 and updating.  Very slowly updating.
[18:46] <rsalveti> yep, but at least the kernel issues you got could be fixed already
[18:47] <rsalveti> tell me about it
[18:47] <rsalveti> that's why for development I'm using a external usb hd
[18:49] <GrueMaster> usb HD is faster than the SD?
[18:49] <GrueMaster> I hadn't benchmarked it.
[18:49] <hrw|gprs> on omap3?
[18:49] <rsalveti> panda
[18:49] <hrw|gprs> probably same
[18:49] <rsalveti> it seems faster
[18:49] <hrw|gprs> on omap3 you get 5MB/s read from sd and 14MB/s from same sd in usb card reader
[18:50] <rsalveti> ouch
[18:50] <hrw|gprs> thats from my tests on beagleboard
[18:50] <GrueMaster> I don't think the drive is the limiting factor.  Pulling updates from ports.ubuntu.com is slow on a good day.
[18:50] <hrw|gprs> and I have 0.5$ worth card reader
[18:51] <GrueMaster> Sounds like something plars could look into.  He's into performance issues.
[18:51] <plars> I am?
[18:51] <GrueMaster> I'm mainly concerned with functionality atm.
[18:52] <GrueMaster> I thought that was your focus this cycle.
[18:53] <plars> hrw|gprs: that's interesting, haven't looked at it personally though
[18:53] <plars> GrueMaster: technically, my focus is tools
[18:54] <GrueMaster> ah.
[18:54] <plars> which got turned into s/tools/infrastructure
[18:54] <GrueMaster> heh.
[18:55] <plars> would be a good thing for the landing teams to look at
[18:55] <plars> it makes me wonder what the results of the same test would be on dove or babbage
[18:55] <plars> and others
[18:55] <plars> is this an arm thing, or a beagle specific thing
[18:56] <GrueMaster> Right now, I am more concerned with getting a working image.  How fast it fails is irrelevant.  :P
[18:56] <hrw|gprs> arm or omap3 or a beagle
[18:57] <hrw|gprs> I have to check one day how fast beagleboard is with my 1.5TB sata harddrive when it is on usb bus.
[18:57] <hrw|gprs> over sata it does 110MB/s, over usb with sheevaplug it did 30MB/s without problems
[18:58] <plars> hrw|gprs: what are you testing with?
[18:59] <hrw|gprs> it was simple 'hdparm -tT'
[18:59] <hrw|gprs> on beagle I used dd
[19:00] <GrueMaster> rsalveti: omap4 meta package is being looked into.
[19:00] <rsalveti> GrueMaster: yep. ot
[19:00] <rsalveti> it's missing an update
[19:00] <rsalveti> I'll forward it to tgardner
[19:00] <GrueMaster> helps having two kernel crunchers in my town.
[19:01] <rsalveti> I'm just updating it and will send to the kernel devs
[19:01] <rsalveti> argh, some io is killing my machine
[19:01] <rsalveti> and pulse get stuck everytime
[19:02] <hrw|gprs> but if you give me armv4t rootfs then I can do any set of strange tests
[19:18] <rsalveti> GrueMaster: ogasawara is updating the linux-meta package
[19:18] <rsalveti> we should get it updated soon
[19:18] <GrueMaster> rsalveti: I know.  I have a back channel to her and others in Portland.  But thanks.
[19:20] <rsalveti> GrueMaster: oh, you cheated
[19:20] <rsalveti> :-)
[19:20] <GrueMaster> Of course.
[19:20] <GrueMaster> Something I learned at Intel.  It is sometimes easier to use back channels to get things done quickly.
[19:23] <rsalveti> GrueMaster: sure
[19:24] <rsalveti> the kernel seems to be a little mess
[19:24] <rsalveti> you have to update the kernel and also update the meta package
[19:24] <rsalveti> they are at a git tree, and not bzr, so merge proposals don't basically work
[19:26] <rsalveti> and the meta package is with a wrong version
[19:26] <rsalveti> and wrong description
[19:34] <rsalveti> GrueMaster: at tomorrow's image you'll get the latest kernel :-)
[19:34] <GrueMaster> Yes, I know.
[19:34] <rsalveti> with new fixes and hopefully without any other new bug
[19:34] <rsalveti> :-)
[19:34] <rsalveti> GrueMaster: yeah, why I'm talking with you, you must be cheating again
[19:34] <rsalveti> :P
[19:36]  * rsalveti starts looking for his beagle xm
[19:37] <rsalveti> GrueMaster: do you know what is the memory chip that we have issues with xm?
[19:37]  * rsalveti now needs to find about the xm known issues
[19:37] <GrueMaster> I think it is a kingston, but not sure.  I don't have an XM yet (next week).
[19:55] <GrueMaster> rsalveti: Have you seen the issue with panda where the sd interface shuts down?  I have this message:  INFO: task mmcqd:46 blocked for more than 120 seconds. followed by other blocked tasks.
[19:55] <GrueMaster> And it appears to be SD related.
[19:56] <GrueMaster> I have mouse, but no keyboard.  That means the USB is semi-functional.
[19:58] <rsalveti> GrueMaster: hm, never saw it
[19:59] <rsalveti> GrueMaster: how do you generally hits this issue?
[19:59] <GrueMaster> I was running apt-get update.  Just stopped during logrotate upgrade.
[20:02] <GrueMaster> Unfortunately there are no log entries and nothing on serial console (beyond what I posted).
[20:03] <rsalveti> hm
[20:03] <rsalveti> GrueMaster: are you updating from alpha 3 to current?
[20:03] <rsalveti> if you can reproduce it, we could try with 903
[20:04]  * GrueMaster patiently waits for the beagle to finish updating the highly needed voodo graphics drivers and other X drivers.
[20:04] <rsalveti> lol
[20:04]  * rsalveti hates that
[20:04] <GrueMaster> I plan on it.   Unfortunately, reproducing these types of bugs can be problematic at best.
[20:05]  * GrueMaster wonders if his flyswatter would be useful in this situation.
[21:36] <GrueMaster> mpoirier: Cool find on the mtd support issue for beagle.  Let me know when you have a kernel you need me to test.
[21:37] <mpoirier> GrueMaster:  Ok, I'll compile something toghether...
[22:25] <rsalveti> ahh... coffee
[22:29] <rsalveti> GrueMaster: http://gitorious.org/pandaboard/u-boot/commits/omap4_panda_es2.0
[22:30] <rsalveti> GrueMaster: http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_es2.0
[22:30] <GrueMaster> rsalveti: Thanks.
[22:30] <rsalveti> http://gitorious.org/pandaboard/kernel-omap4/commits/L24.8_panda_es2.0
[22:30] <GrueMaster> New kernel as well?
[22:31] <prpplague> GrueMaster: yea, it adds the EHCI support
[22:31] <rsalveti> hm
[22:32] <rsalveti> GrueMaster: I can grab the patches and generate a deb file for you, if needed
[22:33] <mpoirier> GrueMaster: http://people.canonical.com/~mpoirier/linux-image-2.6.35-15-omap_2.6.35-15.22_armel.deb
[22:33] <rsalveti> I have my dev environment setup already
[22:33] <rsalveti> GrueMaster: at least for kernel
[22:33] <GrueMaster> rsalveti: I have a pbuilder environment on my dove.  Decently fast native builds.
[22:34] <GrueMaster> mpoirier: Thanks, will test today.
[22:34] <rsalveti> GrueMaster: cool, so np :-)
[22:34] <mpoirier> dyfet: is https://bugs.launchpad.net/bugs/b608279 still valid ?
[22:36] <mpoirier> GrueMaster: do you know anything about  https://bugs.launchpad.net/bugs/608279
[22:39] <GrueMaster> mpoirier: That was based on some really early testing I did with read-edid.  dyfet should be actively involved with this issue.
[22:40] <mpoirier> GrueMaster: I was able to read the EDID from u-boot.
[22:40] <mpoirier> what user space tool did you use ?
[22:41] <GrueMaster> read-edid.
[22:41] <mpoirier> ok, I'll try.
[22:42] <GrueMaster> mpoirier: See https://blueprints.launchpad.net/ubuntu/+spec/mobile-m-omap-edid-autodetection.
[22:43] <mpoirier> got that thanks.
[23:55] <GrueMaster> rsalveti: I think you will need to build the required files.  I am not setup for this type of build.  I am setup for package building.
[23:56] <rsalveti> GrueMaster: np, I just wanted to know the es2 specific patches so I can put it my ubuntu tree for the moment
[23:56] <rsalveti> and build the package like any other ubuntu tree
[23:56] <rsalveti> let me take a look at it
[23:59]  * GrueMaster needs a break.