**** BEGIN LOGGING AT Mon Aug 23 02:59:57 2010 Aug 23 06:40:01 Nice job: http://theironlion.net/blog/2010/06/06/ubuntu-arm-board-and-i-walk-bar/ Aug 23 06:40:03 RON LION Aug 23 06:40:12 That's what I get at 150% fullzoom. Aug 23 07:20:18 morning Aug 23 10:21:45 lool, what are you fiddling with upstart ? it didnt FTBFS since two uploads Aug 23 10:22:08 ogra: Fiddling? Aug 23 10:22:08 * ogra wonders if the -fpic is still needed Aug 23 10:22:40 ogra: I don't understand your remark Aug 23 10:23:02 lool, oh, it was -fpie not pic, why did you make that change to libnih ? Aug 23 10:23:13 ogra: I reverted an armel-specific workaround, read the changelog Aug 23 10:23:18 oh, oops Aug 23 10:23:24 sorry, misread Aug 23 10:23:26 * Re-add -fPIE to the testsuite on armel, removing all armel-specific tests; Aug 23 10:23:29 current gcc-4.4 don't seem affected by the ICE anymore (see LP #398403). Aug 23 10:23:30 Launchpad bug 398403 in upstart (Ubuntu) (and 4 other projects) "[PR40735] gcc-4.4 fails to build upstart 0.6 on armel due to an internal compiler error (affects: 2) (heat: 20)" [Undecided,Fix released] https://launchpad.net/bugs/398403 Aug 23 10:23:32 yeah Aug 23 12:47:42 mythripk: how do you identified all the supported timing values for omap4 in the hdmi driver? Aug 23 12:47:59 I was thinking if it can be compatible with omap 3 too Aug 23 12:48:32 robclark: maybe you also know the answer :-) ^ Aug 23 12:52:41 lool, wrt your filesystem corruption issue from the weekend, do you use the initrd from the image and also the boot.scr ? Aug 23 12:53:20 lool, i wonder how you even got fsck output on stdout, the scripts in initramfs redirect all that to the jasper.log Aug 23 12:54:34 lool, also you wont be able to use that image without dd'ing it to a bigger img file (or min. 4G SD card), did you do that ? Aug 23 12:55:36 (thre images we produce are really not suited for qemu usage without a lot of fiddling) Aug 23 13:01:01 rsalveti: not sure how the timings were identified.. I think that is a question for mythripk Aug 23 13:01:39 but I'm not sure how similar the beagle hdmi driver is.. but I assume there must be a table somewhere that the bootargs map to Aug 23 13:02:12 robclark: yeah, could be, will have a look at it Aug 23 13:02:38 robclark: omap3 did not checked edid Aug 23 13:02:44 because the hdmi driver basically fetch the edid and then finds the best resolution that has a matching timing Aug 23 13:03:15 hrw: but I assume it still uses timings somewhere under the hood... when you set code/mode bootargs, those must map to some supported timings Aug 23 13:03:34 don't know if the code/mode is actually supported at beagle Aug 23 13:03:42 there is a map of resolutions in omap3 driver Aug 23 13:04:01 we have a spec to implement using EDID under omap3 Aug 23 13:04:06 fyi Aug 23 13:04:15 ogra: I know, that's why I'm asking all these questions :-) Aug 23 13:04:17 that map should contain the timings, I would guess.. since at some point that needs to be programmed in to the hw to generate correct signal Aug 23 13:04:32 ogra: but without going to highest possible I hope Aug 23 13:04:55 robclark: hm, true, will try to find it Aug 23 13:05:33 hrw, with going to highest possible the current monitor and driver support Aug 23 13:08:19 ogra: 1680x1050x16@24 omap3 can generate, my display probably will display but I prefer to not go more then 1280x800 on it Aug 23 13:08:47 hrw, you are free to change the generated cmdline Aug 23 13:08:59 its just to get a good default entry Aug 23 13:09:14 sure Aug 23 13:09:54 indeed preferably the omap3 driver would do the same the omap4 one just learns and wouldnt need cmdline args :) Aug 23 13:10:24 but since we dont put much effort into omap3 development the cmdline will do for now Aug 23 13:20:40 armel-cross-toolchain 1.16 sent to PPA for build Aug 23 13:32:21 ogra: As noted in my email, I don't touch the image at all and run it without resizing Aug 23 13:32:45 lool, yeah, but did you use the cmdline from boot.scr and the initrd from the image ? Aug 23 13:32:51 ogra: I understand it might not be expected to work out of the box under QEMU, but my experience seems to indicate an underlying bug which might be worth looking into Aug 23 13:32:59 ogra: I'm not touching the image Aug 23 13:33:06 ogra: So it uses everything in there Aug 23 13:33:08 (the corruption is surely on buildd side, i'm just wondering why you get that output at all) Aug 23 13:33:28 so you use u-boot to boot it ? Aug 23 13:33:35 The u-boot in your image Aug 23 13:33:39 right Aug 23 13:33:42 thats weird Aug 23 13:33:59 and when do you see the error ? before or after the automatic reboot Aug 23 13:34:35 (there shouldnt be an fsck at all apart from teh jasper one before the boot and all jasper output is logged silently to a file) Aug 23 13:34:44 s/boot/reboot/ Aug 23 13:37:22 ogra: On first boot Aug 23 13:37:33 thats strange Aug 23 13:38:17 there is only one forced fsck during the resize process, then it should reboot right after jasper prints "reboot check" Aug 23 13:38:43 if you see the fsck after "reboot check" its likely not following the process Aug 23 13:38:52 i.e. reboot doesnt work Aug 23 13:40:11 its also very likely that it doesnt do the resizing and reformatting at all in your case, which will definitely cause issues Aug 23 13:41:20 (partitioning or filesystem size doesnt matter at all since we rewrite the whole partition table and reformat/resize the filesystems before the rootfs gets ever mounted) Aug 23 13:41:52 so the corruption doesnt matter for functionality if the resizing works Aug 23 13:46:51 ndec, try to re-upload to the PPA, it should build armel now Aug 23 14:10:12 ogra: well, in fact it's not showing armel, but it does show sparc and powerpc ;-) Aug 23 14:10:26 ogra: you should be able to see the PPA, i have uploaded Aug 23 14:10:36 well, it was just changed, it should build armel now Aug 23 14:10:46 i think you need to re-upload Aug 23 14:11:03 ogra: I uploaded after you told me about it... is there any delay? Aug 23 14:15:55 ndec, ok, i'm told it should be fixed *now* Aug 23 14:17:19 ogra: i just tried to upload a package with arch=armel only, and it seems that the upload worked. we will see in a few mins. Aug 23 14:17:28 yep Aug 23 14:17:37 seems armel needed special treatment for enabling Aug 23 14:17:51 enabling the ports just gave ia64, sparc and ppc Aug 23 14:18:15 ah, your ubuntu4 upload looks good Aug 23 14:18:48 ogra: ubuntu3 looks good too. it has arch=any, and armel is there. Aug 23 14:19:35 ah, i didnt look at 3 :) Aug 23 14:19:45 but right, seems ok now Aug 23 14:20:08 ndec, so i'd say enjoy your PPA :) Aug 23 14:20:35 (and give me a list with other trusted uploaders at some point) Aug 23 14:20:54 ogra: i can add them myself since you made me admin, no? Aug 23 14:21:14 i didnt make you admin, i think asac did though Aug 23 14:21:24 but yes, you should be able to Aug 23 14:21:58 ogra: i will try. for now we will try to put all the packages in the PPA for review, and let you know. Aug 23 14:22:27 great :) Aug 23 14:51:30 mopdenacker: hey, do i need to send another confirmation for my ELF-EU presentation, or was that just for the people who were CC'd on that email? Aug 23 14:54:45 prpplague: no, you don't have to. I already have your confirm. :-) Aug 23 14:55:05 mopdenacker: dandy Aug 23 14:55:42 mopdenacker: i've got to finish testing some new boards this morning, then this afternoon i'll be back on your display issue Aug 23 14:56:23 prpplague: perfect. Thank you very much! I'm excited to meet you in Cambridge at last :-) Aug 23 14:56:30 Good luck! Aug 23 14:57:47 mopdenacker: me too Aug 23 16:16:19 robclark: hey, so you think we need to trace through the resize notification to track down this issue? Aug 23 16:20:07 hmm, that bit about the log redirecting to jasper.log... shouldn't it use "tee"? Aug 23 16:20:21 prpplague: yes.. I think so Aug 23 16:20:46 robclark: can you recommend a function call to start looking at? Aug 23 16:21:02 DanaG, why = Aug 23 16:21:08 s/=/?/ Aug 23 16:21:32 So you can get them over stdout. Aug 23 16:21:49 Or is it not possible to lose jasper.log anyway? Aug 23 16:22:11 Say the thing fails in some way that makes you unable to retrieve the log... can that even happen? Aug 23 16:22:28 prpplague: hang on, I'll swing by Aug 23 16:23:10 DanaG, it cant get lost but in some stages it can get hard to access the log Aug 23 16:23:50 robclark: thanks Aug 23 16:24:44 Ah, pidgin died: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/622831 Aug 23 16:24:45 DanaG: Error: Bug #622831 is private. Aug 23 16:25:23 ah Aug 23 16:25:31 Would pidgin bug logs have passwords? Aug 23 16:27:54 ah yeah, the core dump has my irc password. Aug 23 16:58:52 GrueMaster, so the oem-config fix works fine, as soon as dyfet has fixed telepathy-glib the images should build again and we should have a working install process again Aug 23 17:03:01 cool, finally :-) Aug 23 17:04:00 and oem-config has a cute panel now Aug 23 17:04:12 which suspiciously looks like upanel Aug 23 17:04:37 (the thing we dropped because DX didnt provide the code for it) Aug 23 17:05:31 anyway Aug 23 17:05:34 * ogra calls it a day Aug 23 17:05:48 cool Aug 23 17:06:55 ogra: I'm going to be spending the day trying to figure out how I am going to manage 3 new platforms into my office layout. Should be ready for testing later today. Aug 23 17:38:04 robclark: looks like i can replicate that problem with the dvi display Aug 23 17:53:25 rsalveti: Timings supported by omap4 are based on functional spec and max /supported pixel clock values that can be generated by hdmi pll Aug 23 17:53:54 mythripk: hm, ok Aug 23 17:54:34 mythripk: I was thinking about omap 3, how can we check the supported timings? Aug 23 17:56:23 rsalveti:not all omap4 timings are supported by omap3,it has limited set of timings is what i believe ,I can check with pulukuru,srinivas in case you dont have his contacts and get back to you. Aug 23 17:56:51 mythripk: nice, that would for sure help :-) Aug 23 17:57:12 because then we can try to identify the best supported video mode for omap 3 Aug 23 17:58:32 prpplague: oh good.. I can swing by in a bit Aug 23 18:00:37 rsalveti:720P is the maximum supported timing in omap3 is what im aware of.. other timings i need to confirm Aug 23 18:01:31 mythripk: hm, I thought it would support higher timings Aug 23 18:01:44 mythripk: but please, confirm it if possible :-) Aug 23 18:12:46 rsalveti : confirmed max omap3 supports is 720P Aug 23 18:18:27 I think, that you can do 1080i/1080p@30 on beagle Aug 23 18:22:51 ynezz: the pixel clock seems to limit you Aug 23 18:22:55 mythripk: nice, thanks Aug 23 18:23:35 rsalveti: yes, it depends on TV/monitor also, if it can do lower sync rates Aug 23 18:24:06 but I've read, that somebody was able to run 1080p30 at beagle Aug 23 18:30:07 ynezz: cool Aug 23 18:32:15 http://markmail.org/message/b7fii2z6qcf3di3x Aug 23 18:57:37 heh, I'm blind or need more cofee, but where could I enter here new bug/feature request? :-) https://bugs.launchpad.net/~beagleboard-kernel Aug 23 19:07:45 ynezz: If you wish to file it as a bug against the Ubuntu kernel for omap3, file it against linux-image-omap. Use linux-image-omap4 for omap4 kernels. Aug 23 19:08:02 Mark importance as wishlist. Aug 23 19:08:42 Oops, excuse me, that should be linux-ti-omap & linux-ti-omap4. Aug 23 19:10:56 ah, thanks :) Aug 23 19:14:07 is there a mobile meeting tomorrow? Aug 23 19:15:17 ian_brasil_: yep, every week Aug 23 19:15:37 ian_brasil_: 9 am for you, I guess Aug 23 19:16:25 rsalveti: thx Aug 23 20:11:31 weird... plymouth doesn't work on the beagleboard. Aug 23 20:13:04 ah, I see... it won't splash if serial console is present. Aug 23 21:34:06 ogra: FYI libnih built fine Aug 23 22:29:51 Weird... flash-kernel hangs the board at "erasing kernel NAND space..." Aug 23 22:30:01 er, wait, it unfroze. Aug 23 22:30:33 to upgrade to maverick but leave the kernel, uboot, and firmware alone on a iMX51, is using update-manager a stupid idea ? Aug 23 22:31:19 It's spewing: [ 6632.227600] uncorrectable error : Aug 23 22:31:30 [ 6631.614959] Buffer I/O error on device mtdblock3, logical block 124 **** ENDING LOGGING AT Tue Aug 24 02:59:57 2010