**** BEGIN LOGGING AT Tue Aug 03 02:59:57 2010 Aug 03 03:04:58 GrueMaster: yep, I'm getting the same error lag is facing with his lg monitor Aug 03 03:05:41 probably this is fixed already with robclark patches Aug 03 03:05:57 Interesting. Aug 03 03:06:24 I don't have an HDMI monitor, but will test this when I am at the QA sprint in a couple of weeks. Aug 03 03:06:51 GrueMaster: when are you going to be off for the qa sprint? Aug 03 03:07:16 I leave next Friday and will be in Oxford until the 22nd. Aug 03 03:07:41 GrueMaster: oh, ok :-) Aug 03 03:07:41 Food's cooking, gotta run. Aug 03 03:07:45 see ya Aug 03 03:17:33 fyi, for DVI monitors, I pushed a patch: http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commit/37050de250e570d67a435cb36ecfa9763a98e5ff Aug 03 03:18:01 it won't make any monitor that wasn't working at all start working.. but it will make some DVI monitors that were defaulting to 640x480 pick a better resolution Aug 03 03:18:26 (this at least helps with my DVI monitor at home ;-)) Aug 03 05:50:01 lag:ping . do you see it always ? Aug 03 05:50:23 oops : *do you see it always ? Aug 03 06:41:50 mythripk: Morning Aug 03 06:48:29 morning lag Aug 03 06:48:35 did you see it again ? Aug 03 06:48:43 i tried and could not reproduce Aug 03 06:48:54 I see different things depending on my cmdline Aug 03 06:49:18 can you send your cmdline ? Aug 03 06:49:19 omapdss DISPC error: SYNC_LOST_DIGIT Aug 03 06:49:19 omapdss HDMI error: Failed to lock PLL Aug 03 06:49:41 quiet splash ro elevator=noop console=ttyO2,115200n8 vram=32M mem=463M fixrtc Aug 03 06:49:53 failed to lock pll is because the first block is 1920 1080 with 138.5Mhz Aug 03 06:50:04 Okay Aug 03 06:50:13 that will be fixed with the patches i sent you , which will be part of out L24.9 release Aug 03 06:50:21 Okay Aug 03 06:50:25 So they're not out yet? Aug 03 06:50:44 not yet! , will be by this friday Aug 03 06:50:51 Have they been approved? Aug 03 06:50:57 yes Aug 03 06:51:12 Excellent, well done Aug 03 06:51:26 that is anyways our internal tree :) though Aug 03 06:51:28 I guess I'll wait for those before doing anymore Aug 03 06:51:54 I'll try and get them into our tree asap Aug 03 06:52:32 but this is a strange error you see , it is failing in dispc_set_digit_size which would mean x and y res are goofed up, in case you see that again a full log with debug enabled would be great Aug 03 06:53:02 I'm sure I can reproduce Aug 03 06:53:05 Wait one Aug 03 06:57:55 mythripk: I don't get the whole log (I guess most of it is printed to the monitor (which isn't working) Aug 03 06:57:57 http://paste.ubuntu.com/472531/ Aug 03 06:58:50 mythripk: setenv bootargs vram=32M mem=463M console=ttyO2,115200n8 console=tty2 root=/dev/mmcblk0p2 fixrtc Aug 03 06:59:27 If I remove the console=tty2 it does something different Aug 03 07:02:46 I correct myself Aug 03 07:02:55 Its actually this cmdline: setenv bootargs quiet splash ro elevator=noop console=ttyO2,115200n8 vram=32M mem=463M fixrtc Aug 03 07:04:48 That's more like it Aug 03 07:04:59 When I remove the console=tty2 I get this:# Aug 03 07:05:02 http://paste.ubuntu.com/472534/ Aug 03 07:06:22 alo Aug 03 07:17:24 ogra: ping Aug 03 07:33:37 lag : I suspect that it is becasue of the wrong x and y timing value. which ideally shouldnt , you are using console = ttyo2 which is ok , this would be needed to redirect your prints to TV when enabled. Can you wait for the patch set to be pushed ? Aug 03 07:34:50 ttyO2 won't push the prints to the TV/Monitor, only to the serial console Aug 03 07:34:58 tty2 will push them to the TV/Monitor Aug 03 07:40:22 lag: my bad . "lag : When I remove the console=tty2 I get this:#" that would when it is trying to redirect the contents to TV where you get the pll_not locked state Aug 03 07:42:33 persia: could you check http://revu.ubuntuwire.com/p/glmark2 for alf`? Aug 03 07:43:05 mythripk: If you read on you'll find that I was incorrect Aug 03 07:43:44 mythripk: In fact, the only think that differs when I removed console=tty2 is that I receive more output on the serial Aug 03 07:43:53 I'll wait for the new patches Aug 03 07:46:03 lag: I shall update you when its pushed to our tree Aug 03 07:46:51 mythripk: Great thanks Aug 03 07:52:54 ericm|ubuntu: I would have expected from me to notice the breakage even though it was your patch :-) Aug 03 08:16:07 ukleinek, nah - you are fine Aug 03 08:17:22 ericm|ubuntu: have you worked with the Freescale guys in Shanghai? Aug 03 08:17:38 amitk, a bit Aug 03 08:17:41 amitk, but not much Aug 03 08:18:05 amitk, knows some guys there as well as cooloney Aug 03 08:18:12 ericm|ubuntu: ok, one of them joined Linaro today (just introducing around) Aug 03 08:18:38 amitk, in #linaro? Aug 03 08:18:53 amitk, I missed that part Aug 03 08:18:59 ericm|ubuntu: yes Aug 03 08:36:07 amitk: is he/she based in Shanghai? Aug 03 08:36:20 cooloney: yes, come to #linaro to meet him Aug 03 08:51:38 amitk: I have a mx51evm here and it seems to be broken with CONFIG_FIXED_PHY=y; CONFIG_MDIO_BITBANG=y; CONFIG_MDIO_GPIO=y Aug 03 08:52:14 amitk: Did you see this already, too? Aug 03 08:53:11 ukleinek: hi, how's broken? Aug 03 08:53:19 ukleinek: unfortunately no, haven't had a chance to test mx51 for a few -rcs since my board broke. :-/ I just got a new one now so should be able to test. Aug 03 08:53:50 ukleinek: in our ubuntu fsl-imx51, those configs are all off, Aug 03 08:54:27 amitk: the fec doesn't work so I cannot nfsrootboot Aug 03 08:55:18 cooloney: you fixed the fec driver for MDIO support, right? Do you have time to look at this today? Aug 03 08:56:06 ukleinek: yeah, my patch was merged sometime ago and there are some updates in Dave's netdev-next tree Aug 03 08:56:18 amitk: yeah, ^^ Aug 03 08:56:30 but too bad, i don't have the hardware now Aug 03 08:56:46 my babbage is broken Aug 03 08:56:50 bricked Aug 03 08:58:12 ukleinek: I'll try to look at it as soon as I setup the new board Aug 03 08:58:44 amitk: this issue is in my way, I can do it myself, too. Aug 03 09:00:53 ukleinek: ok, I can't help you right away (so you might consider looking at it) Aug 03 09:00:58 * ukleinek just wanted to check if it's a known (or even fixed) issue Aug 03 09:01:30 ukleinek: no it isn't (we've had HW availability issues). Thanks for the report Aug 03 09:04:46 CONFIG_FIXED_PHY=y is the trigger Aug 03 09:06:59 lag, yes ? Aug 03 09:07:59 ogra: Do you have a uboot which omits the memory error on XM? Aug 03 09:08:53 i have an yet untested patch http://cgit.openembedded.org/cgit.cgi/openembedded/diff/?id=b4c5ef7e0e06890b1369bfbd5c767820024adb21&id2=b738634ead43d9ebcc8f8a4840366528ec91045a Aug 03 09:10:05 ukleinek: pls take a look at this http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commitdiff;h=0e5e6e2a981eeab61dcc184d51ab769a33af6589 Aug 03 09:10:26 ukleinek: and this http://bugs.launchpad.net/bugs/457878 Aug 03 09:10:30 Ubuntu bug 457878 in linux-fsl-imx51 (Ubuntu Lucid) (and 1 other project) "imx51 on board ethernet plug/unplug events not detected (affects: 2) (heat: 15)" [Medium,Fix released] Aug 03 09:11:33 cooloney: is this a fix or a work around? Aug 03 09:12:56 ukleinek: i simply turned that off. Aug 03 09:13:03 cooloney: the plug/unplug event thing is fixed upstream Aug 03 09:14:19 ukleinek: CONFIG_FIXED_PHY will cause a sysfs conflict when I was trying to add phylib support in fec driver Aug 03 09:41:41 ogra: What SD card are you using for your XM? Aug 03 09:50:33 lag, traxdata 4G currently Aug 03 09:51:31 ogra: Have you seen the "mmc0: USB HID whilst initialising SD card" issue? Aug 03 09:53:06 ogra: Is the Traxdata a High Capacity (SDHC) card? Aug 03 10:02:18 hands out free samples of his slc 4gb flash crack :) Aug 03 10:14:44 cwillu_at_work: ? Aug 03 10:14:55 lag, I buy silly sd cards Aug 03 10:15:11 they don't break when you pull power from them mid-write Aug 03 10:15:56 cwillu_at_work: The XM's kernel doesn't like my SanDisk Micro SDHC card :( Aug 03 10:16:42 !info ttf-larabie-straight Aug 03 10:16:44 cwillu_at_work: ttf-larabie-straight (source: ttf-larabie): Straight fonts from www.larabiefonts.com. In component multiverse, is optional. Version 1:20011216-1.1 (lucid), package size 3462 kB, installed size 7860 kB Aug 03 10:17:00 that doesn't want to install on arm Aug 03 10:17:21 reports that it's a virtual package Aug 03 10:17:31 makes me want to cry Aug 03 10:18:15 ... or I just don't have multiverse enabled.... Aug 03 10:19:25 if I give you ssh to my server, can you call my cell if the build breaks again? Aug 03 10:19:28 I need to go for a walk :/ Aug 03 11:26:24 ogra: Am I correct in assuming you have fully booting XM and Panda boards? Aug 03 11:30:52 lag, no, XM doesnt Aug 03 11:31:26 i see some mmc issues but have lost the dmesg data for it before i could look Aug 03 11:31:41 it finds the mmc though, but the device is readonly Aug 03 11:31:59 (sfdisk complains it cant open the device for writing) Aug 03 11:33:02 Okay Aug 03 11:33:28 I'm just compiling a kernel which should eradicate my -110 error Aug 03 11:33:40 Once that's gone, I'll look into any other errors Aug 03 11:33:58 Can you send me the kernel logs you have? Aug 03 11:34:07 For XM and Panda would be helpful Aug 03 11:35:52 will do after the next image test (i just triggered a build) Aug 03 11:36:06 the XM is totally trashed atm Aug 03 11:36:19 Kernel error, or userspace? Aug 03 11:36:55 the filesystem dissolved itself at some point after i did reset the system several times Aug 03 11:37:11 i think the root cause is a kernel or bootloader issue with the SD bus though Aug 03 11:38:00 Well if you can get me some logs, I can try to do something about it Aug 03 11:41:36 ogra.. just fixed the ro bit last night.. http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/2.6.35-devel/annotate/head:/patches/rcn/xm-wp-testing.diff Aug 03 11:41:58 verified by another user, i'll clean up the patch a little. Aug 03 11:42:07 lag, ^^^ Aug 03 11:42:19 can i has that ? pleeeease Aug 03 11:42:51 basicly, the xm schematic has no wp, the current kernel defaults to a bx or cx non-existent wp line on the beagle.. (bad) Aug 03 11:43:02 hrm, yeah Aug 03 11:44:50 but there's another weird bug in 2.6.35 i'm going after.. on both my Bx and Cx boards, the mmc card is defaulting to 'ro' on boot. Have you guys seen that too on your kernel? Aug 03 11:45:52 yes, thats what i described above Aug 03 11:46:06 it appears like its locked Aug 03 11:46:50 yeap, well that patch fixes the xm.. the Bx and Cx have a gpio issue, playing around with the write protect lever it seems to be ignored.. Aug 03 11:48:25 this brings ti back to 2.6.34/2.6.33 behavor in my testing: http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/2.6.35-devel/annotate/head:/patches/rcn/regression-disable-wp.diff but i think there's bigger issues in the mmc write protect detection as it doesn't register the write protect lever in my testing.. Aug 03 11:49:50 it's basicly revert ed8303fc111e58530e22bd29b0d7e08dced75999 introduced in 2.6.35-rc1 Aug 03 12:05:59 ping: ogra Aug 03 12:10:28 rcn-ee: Have you seen the -110 error? Aug 03 12:10:36 rcn-ee: On XM? Aug 03 12:15:39 lag, probally.. i see lots of errors on mine.. 'sudo aptitude' opps it for me.. (i really need to get production hardware.. very early proto "P7" full of extra solder wires for traces..) Aug 03 12:16:04 i think that's the usb -110 error right? Aug 03 12:16:17 rcn-ee: "mmc0: USB HID whilst initialising SD card" Aug 03 12:16:38 You'd know if you had it, because it dies on the way up Aug 03 12:16:51 It doesn't find the SD card Aug 03 12:18:07 that's very weird.. mine finds the SD: (last saved dmesg) http://pastebin.com/4Dtysi8W Aug 03 12:19:04 It must like your MicroSD card Aug 03 12:19:08 Which one are you using? Aug 03 12:19:15 just generic sandisk.. Aug 03 12:19:27 SDHC? Aug 03 12:19:30 Or SC? Aug 03 12:19:41 4Gb/2Gb sdhc.. Aug 03 12:19:51 That's interesting Aug 03 12:19:55 Are you using our kernel? Aug 03 12:20:04 but i almost think they are clones.. the adapters don't work and i had to use another one.. Aug 03 12:20:12 yeap that's mine kernel.. Aug 03 12:20:21 Okay Aug 03 12:20:31 Our kernel doesn't like SDHC cards Aug 03 12:20:38 weird... Aug 03 12:20:43 We have to turn off preemption to get them to work Aug 03 12:21:03 does it also fail with the Bx/Cx's? Aug 03 12:21:11 (sdhc) Aug 03 12:21:12 No idea Aug 03 12:21:20 I don't have either of those Aug 03 12:21:26 I haven't heard of it Aug 03 12:21:30 Only XM Aug 03 12:21:43 rcn-ee: bug 591941 Aug 03 12:21:46 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 Aug 03 12:23:25 that actually might be 'too' cheap cards...... cat-ing my config, wondering if? # CONFIG_MMC_SDHCI is not set Aug 03 12:24:37 It's a SanDisk Aug 03 12:27:44 you guys don't off hand happen to know where the mmc keeps there error code list.. (looking 110) Aug 03 12:28:31 Not off hand, sorry Aug 03 12:29:34 rcn-ee: 110 is usually ETIMEOUT Aug 03 12:29:36 i found another reference in the plug computer forums, looked like a bad sandisk card.. Aug 03 12:30:03 thanks ukleinek Aug 03 12:30:11 I've seen it happen with others Aug 03 12:31:24 which isn't good... reading the bug report, it's pretty consistent, but is there a specific image i should test with my xm and collection of sd cards? Aug 03 12:33:03 Please :) Aug 03 12:33:30 rcn-ee: http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/ Aug 03 12:33:45 gunzip it and dd it to your MicroSD card Aug 03 12:35:24 cooloney: CONFIG_FIXED_PHY is enabled in mx51_defconfig Aug 03 12:35:30 got it.. i'll pull it down at work in a bit, just getting ready at the moment.. i'll log back in a couple hours with my findings.. Aug 03 12:35:50 rcn-ee: Great, thanks Aug 03 12:43:16 lag: any news regarding the problem you had yesterday with your lg monitor? Aug 03 12:43:24 lag: I got the same problem with mine :-) Aug 03 12:43:39 lag: with panda Aug 03 12:44:09 What's it doing? Aug 03 12:45:46 lag: http://paste.ubuntu.com/472128/ Aug 03 12:45:58 ukleinek: hmmm, but do we use CONFIG_FIXED_PHY in ARM system Aug 03 12:46:10 mythripk: ping Aug 03 12:46:13 rsalveti: Wait one Aug 03 12:46:23 rsalveti: What monitor are you using? Aug 03 12:46:50 lag: lg with hdmi Aug 03 12:47:32 cooloney: mx51 is the only defconfig that has it Aug 03 12:47:45 lag: is this regarding the dump from rsalveti ? Aug 03 12:49:21 mythripk: Yep Aug 03 12:49:29 Mine is LG with HDMI too Aug 03 12:49:42 rsalveti: Which model? Aug 03 12:50:57 lag: W2253V Aug 03 12:51:16 ukleinek: if we don't need it, we can disable it in mx51 Aug 03 12:51:25 rsalveti: Okay mine is W2261VP Aug 03 12:51:32 ukleinek: it looks like just for x86 Aug 03 12:51:58 cooloney: then it should depend on X86, no? Aug 03 12:53:31 lag: any news regarding this bug? still didn't look for patches into other trees Aug 03 12:54:22 ukleinek: from the code, 'Fixed MDIO bus (MDIO bus emulation with fixed PHYs)' Aug 03 12:54:35 ukleinek: i am not sure about what is Fixed PHY Aug 03 12:54:53 * ukleinek isn't either Aug 03 12:55:16 rsalveti: Ask mythripk Aug 03 12:55:35 mythripk: were you debugging this lg monitor issue? Aug 03 12:58:42 rsalveti: yes i was and the issue is fixed now but then the patches will be pushed to our tree only by this friday. Aug 03 12:59:16 mythripk: and where can I find these patches? is it just an internal tree? Aug 03 12:59:35 rsalveti : The issue is because in the lg monitor block 0 has 1080P timing with 138.5Mhz which is not a standard Aug 03 12:59:50 its still in the internal tree Aug 03 12:59:59 =\ Aug 03 13:00:03 oh wait let me check robclark's tree Aug 03 13:00:10 he must have pushed Aug 03 13:00:11 ok Aug 03 13:02:16 nice to know that my monitor doesn't follows the standard :-) Aug 03 13:02:53 http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commit/f2fa54fcfe8fa09ad14f104ae64d1bb5c93982bc and this http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commit/5553031b56322a7dbaa2f57b8f773be9ae2baaff Aug 03 13:03:16 rsalveti : other block timings are still ok :) Aug 03 13:03:40 mythripk: nice, thanks for the links Aug 03 13:07:30 rsalveti : you dont have to give any bootargs with this if you were giving any for HDMI , just try and let me know. Aug 03 13:07:49 mythripk: sure, will do Aug 03 13:07:50 thanks Aug 03 13:22:49 amitk: mx51 doesn't use IMX_IO_ADDRESS. Do you prefer the mx51's current approach or did this just slip through? Aug 03 13:25:07 rsalveti: What are you going to do with that patch/ Aug 03 13:25:09 ? Aug 03 13:25:46 lag: test it? :-) Aug 03 13:26:02 And then/ Aug 03 13:26:03 ? Aug 03 13:26:27 lag: will let you all know if it worked or not Aug 03 13:26:35 Okay Aug 03 13:26:47 and then we can think if we're going to merge or wait for friday's tree Aug 03 13:26:50 Those patches should all be coming to us sooner or later anyway Aug 03 13:26:54 yep Aug 03 13:27:07 Let me know how you get on and we'll have a chat Aug 03 13:27:16 the sooner the better Aug 03 13:28:07 yep Aug 03 13:36:01 ogra: It matters not Aug 03 13:36:22 lag, it does Aug 03 13:36:42 we'Re way behind on the omap arches and need the HW to work Aug 03 13:40:52 I'm still getting OOM Aug 03 13:41:00 on XM Aug 03 13:41:09 I thought this was a HW issue Aug 03 13:41:22 We can only work with what we've got Aug 03 13:49:03 lag: i guess mdelay is missed in the patch from rob's tree can you please point that out to rsalveti ? Aug 03 13:50:08 lag, yes, and there are a ton of patches for XM that surely arent applied to our tree Aug 03 13:50:20 some crappier some not Aug 03 13:50:54 i know that people in #beagle do some work on booted XMs so we have to be missing a lot Aug 03 13:53:34 rsalveti: ping Aug 03 13:53:39 lag: pong Aug 03 13:55:01 http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=blobdiff;f=drivers/video/omap2/dss/hdmi.c;h=0830bbc6baed30e04afca7b1c1a5b83ec298c890;hp=a8bedb1facd324eb6d2f07767ae6399f7c24ec3a;hb=76dd0768b77f731bbe6ad4df55379734f3a38770;hpb=f6c95ac85cfa087a84cd82564dcaea8ce4a6c867 Aug 03 13:55:17 mythripk says this is missing from robclark's patches Aug 03 13:55:29 Insure you add it, or your monitor won't work Aug 03 13:55:38 yes it is Aug 03 13:55:48 robclark: Don't shoot the messenger Aug 03 13:55:51 ukleinek: MX51_IO_ADDRESS should be replaced with IMX_IO_ADDRESS at some point Aug 03 13:55:51 ;) Aug 03 13:56:02 amitk: ok, will do Aug 03 13:56:04 you need that one from mythripk's patches :-) Aug 03 13:56:09 no shooting involved :-) Aug 03 13:56:24 ("yes it is" == "yes it is missing") Aug 03 13:56:33 sorry, I noticed my wording wasn't so clear Aug 03 13:56:34 lag: ok, will apply the patches and test it here, thanks for the link Aug 03 13:56:36 ukleinek: thanks Aug 03 13:56:44 robclark: Ah, lost in translation (from US to English) ;) Aug 03 13:57:07 no.. I just haven't had my coffee yet this morning ;-) Aug 03 13:57:19 texan vs australian you mean ? Aug 03 13:57:26 heheh Aug 03 13:57:57 * lag kicks ogra in the nether-regions Aug 03 13:58:10 ouch Aug 03 13:59:48 geez ! Aug 03 13:59:57 :) Aug 03 13:59:59 logging out on the panda steals my display Aug 03 14:00:09 no signal anymore Aug 03 14:00:28 ah, its just slow Aug 03 15:28:22 what adds flash-kernel to the /etc/kernel-img.conf file? It is currently not enabled in the 20100802 image, so updating to the latest kernel doesn't run flash-kernel. Aug 03 15:29:09 GrueMaster: Usually, it's flash-kernel-installer, but it might be the image generation script Aug 03 15:34:57 Thanks. I see it in the changelog as being added in May, but I see nothing in the code now. Looking at actual diffs. Aug 03 15:53:12 lool: It looks like this was heavily discussed in the last few cycles, but never really resolved (that I can see). See bug 365053. Aug 03 15:53:13 Launchpad bug 365053 in initramfs-tools (Ubuntu) (and 1 other project) "On armel (Babbage platform), kernel image upgrading breaks if Ubiquity is instructed not to install a bootloader (heat: 12)" [Medium,Triaged] https://launchpad.net/bugs/365053 Aug 03 15:54:00 Of course this bug is moot with preinstalled images as we don't use ubiquity (except for oem-config). Aug 03 15:55:18 I would think that it should be up to the flash-kernel-installer.postinst script to ensure that it is added to /etc/kernel-img.conf. Aug 03 15:56:55 rcn-ee: Hey Robert Aug 03 16:27:03 GrueMaster, lool, kernel-img.conf isnt used anymore by flash-kernel (debian dropped it) flash-kernel is always run by update-initramfs now Aug 03 16:27:33 Hmmm. It didn't run on this update. Aug 03 16:28:05 does /etc/flash-kernel.conf exist ? Aug 03 16:28:44 yes Aug 03 16:29:13 then there is nothing that could block it from being executed at least Aug 03 16:29:33 are you sure you got a new kernel ? Aug 03 16:29:53 with this update i mean Aug 03 16:29:54 I manually ran flash-kernel and it updated the boot partition with the new kernel. It just didn't run when installing the new kernel. Aug 03 16:30:01 Yes. Aug 03 16:30:39 thats pretty weird since our kernel packages usually run update-initramfs from their postinst Aug 03 16:31:31 which in turn should run flash-kernel Aug 03 16:32:50 the 20100802 image has 2.6.35-13-omap kernel installed. Updating pulled in 2.6.35-14-omap. Aug 03 16:33:14 Flash-kernel should have run, but it didn't. Aug 03 16:33:15 really the kernel or just meta ? Aug 03 16:33:21 kernel. Aug 03 16:33:29 i didnt actually see a linux upload Aug 03 16:33:30 I'm looking at /boot Aug 03 16:33:37 but there was a meta upload yesterday Aug 03 16:34:01 thats on a panda ? Aug 03 16:34:08 beagle. Aug 03 16:34:10 ah Aug 03 16:34:24 (hence th 2.6.35-14-omap kernel) ;P Aug 03 16:34:37 if you run update-initramfs, does it run flash-kernel ? Aug 03 16:37:18 checking... Aug 03 16:38:05 dmesg Aug 03 16:38:09 oops Aug 03 16:38:15 heh Aug 03 16:39:34 I didn't see that it ran. is there a log I can check? Aug 03 16:40:08 i dont think so Aug 03 16:40:28 it should tell you it runs, its actually still very noisy Aug 03 16:40:32 Nevermind. timestamp on mmcblk0p1/uInitrd is an hour old. Aug 03 16:40:50 So no, it isn't running. Aug 03 16:41:25 hmm Aug 03 16:42:00 if you run: sudo flash-kernel --supported; echo $? Aug 03 16:42:04 Grrrr. terminal reset. Aug 03 16:42:07 whats the return value ? Aug 03 16:42:38 running flash-kernel manually works fine. I already tested that to make sure (and rebooted to verify new kernel loads). Aug 03 16:43:33 The return value is 0 (which I assume is good). Aug 03 16:43:41 yep Aug 03 16:43:54 means your HW is supported Aug 03 16:44:32 if flash-kernel --supported >/dev/null 2>&1; then Aug 03 16:44:32 flash-kernel Aug 03 16:44:36 ... Aug 03 16:44:44 thats what update-initramfs executes Aug 03 16:45:27 urgh Aug 03 16:45:44 i think i see the issue Aug 03 16:49:58 It doesn't even run that test. Aug 03 16:51:09 no, because there is still old code lool added once to check for the postinst_script value in kernel-img.conf Aug 03 16:51:26 i thought i had dropped that when i merged the new flash-kernel Aug 03 16:51:32 oops Aug 03 16:52:27 comitted and pushed Aug 03 16:52:58 i dont think its critical to upload it now though, we'll get just in the way of other arches ... Aug 03 16:54:18 ok. Aug 03 16:54:31 As long as it makes beta Aug 03 16:54:31 as a quick fiox you can just edit update-initramfs Aug 03 16:54:41 Planned on it. Aug 03 16:54:54 jumpo to flash-kernel and remove the outer if statement Aug 03 16:55:12 the one that checks for kernel-imf.conf contents Aug 03 16:58:43 yep, that fixed it. Aug 03 16:58:51 great Aug 03 16:59:14 Should I post a bug against initramfs-tools to track this? Aug 03 16:59:21 nah Aug 03 16:59:29 the fix is already in the tree Aug 03 17:00:04 It's in the debian git tree. Will we pull an update prior to Beta? Aug 03 17:00:11 next image will have an up to date kernel and before the next kernel comes we'll have the update in Aug 03 17:00:21 ok Aug 03 17:00:31 its in the ubuntu bzr branch Aug 03 17:00:49 Oh. Didn't find that. Only found the debian git tree. Aug 03 17:01:27 Didn't look too hard either. Aug 03 17:07:15 rcn-ee: And now? Aug 03 17:14:57 GrueMaster, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/initramfs-tools/maverick/revision/210 btw Aug 03 17:15:25 Yea, got it. Aug 03 17:49:56 ogra_cmpc: Are we supposed to be generating netboot images for dove & imx? Aug 03 18:46:35 GrueMaster, no, but i wont switch them off unless they cause failures Aug 03 18:46:55 Just emails from iso.tracker. Aug 03 18:47:00 they are built automatically if debian-installer is built Aug 03 18:47:17 oh, they should be removed Aug 03 19:35:56 hi my friends Aug 03 19:38:43 lag, same mmc bug as your guys xm boards: http://pastebin.com/R0tTmXjE Aug 03 19:39:16 however this sandisk card works fine with my 2.6.35 kernel, so it's got to be a patch/config difference... Aug 03 19:40:41 rcn-ee, did you get the mmc from GrueMaster ?? Aug 03 19:41:55 nope, off amazon. ;) Aug 03 19:42:30 back in april when i realized i should stock up before everyone found out the xm's used micro sd cards. .;) Aug 03 19:42:34 What is it? (class/size) Aug 03 19:42:43 Sandisk 4GB SDHC Aug 03 19:43:18 Should work, although you have oops that I haven't seen yet. Aug 03 19:44:07 Yeah, this XM rev P7 (256Mb) isn't 100% anyways.. ;) Aug 03 19:44:47 rcn-ee: what filesystem are you using by default? Aug 03 19:45:29 oh this was lag's image he wanted me to test this morning.. just a dd of http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/ Aug 03 19:45:40 normally i rootstock my own over ext4 Aug 03 19:46:18 for some reason my kernel 2.6.35-dl12 works fine with these sd cards, but ubuntu's kernel can't load the mmc.. since most of the xm patches are similar we are left with the config... Aug 03 19:46:22 There is an updated kernel, but I am not sure how you would install it w/o booting. Aug 03 19:46:45 that's what the bx is for.. ;) give me 5mins.. Aug 03 19:47:05 with a rootstock rootfs you can generate it, with qemu user emulation Aug 03 19:47:29 rcn-ee: I had to drop using your patched kernel :-( Aug 03 19:47:39 or just mount the dist, copy qemu-arm-static there and install it with qemu user emulation Aug 03 19:47:44 *disc Aug 03 19:47:45 yeap.. i read that... Aug 03 19:48:47 500Mhz sucks,,, Aug 03 19:49:08 blah.. i've built kernels on a Bx at 400Mhz.. (debian etch 'arm').. Aug 03 19:49:14 I'm doing a build now, almost to the part that kept causing trouble, so I";ll let you know how it goes Aug 03 19:49:41 beats my 200Mhz Sharp Zarus... Aug 03 19:50:43 rsalveti, may I ask which zaurus you have ? Aug 03 19:51:10 rsavoye: ^ Aug 03 19:51:22 me, I've got several, the 3200 clamshell being my favorite Aug 03 19:51:26 crap there goes the upgrading idea, my Bx's musb port isn't coming alive... ;) Aug 03 19:51:36 rsalveti, :) Aug 03 19:51:51 rsavoye, :) Aug 03 19:52:01 rsavoye, the akita is a lovely device Aug 03 19:53:32 I wound up doing a project a bunch of years ago for NASA, and we used 6000Ls, cause I could install ipsec Aug 03 19:54:09 I was pumping air traffic data over the network to it for monitor alerts Aug 03 20:06:15 dyfet: are you at DebConf? They have you on the schedule giving a talk? Aug 03 20:18:48 rsalveti, nice. I love the nasa Aug 03 20:20:15 rsalveti, 6000 are the potrait orientation ones right ? Aug 03 20:20:27 oops Aug 03 20:20:36 :-) Aug 03 20:20:36 rsalveti, sorry that was for the other guy also starting with rs Aug 03 20:53:07 mythripk: now I'm finally able to test the patches, but didn't work that well :-( Aug 03 20:53:43 now I'm able to get something on the screen but the image is really big and distorted Aug 03 20:53:52 probably still missing some patches from robclark Aug 03 20:55:04 and I don't have a console because of the oem-config, needs to generate a minimal image Aug 03 20:57:01 another weird thing is that I need to recreate the first partition every time I need to update uImage or uInitrd Aug 03 20:57:09 otherwise u-boot doesn't like it Aug 03 20:57:44 GrueMaster: did you ever make any kernel update with panda? Aug 03 20:57:46 rsalveti: how are you partitioning and mounting the sd card? Aug 03 20:58:04 this is the pre-installed image generated by ogra Aug 03 20:58:05 that's a little weird.. Aug 03 20:58:21 standard fat16/32 partition? Aug 03 20:58:25 prpplague: mounting without any extra options at my desktop Aug 03 20:58:27 yep Aug 03 20:58:30 fat 32 Aug 03 20:58:35 rsalveti: not yet, but I found a bug in the initramfs-tools. It won't run flash-kernel unless it is in /etc/kernel-img.conf Fix committed). Aug 03 20:58:47 if I just copy the new uInitrd or uImage file on top of the older one I'm not able to boot Aug 03 20:58:48 rsalveti: interesting Aug 03 20:58:54 u-boot will complain about it Aug 03 20:59:10 ** Unable to read "uImage" from mmc 0:1 ** Aug 03 20:59:10 mmc read: Invalid size Aug 03 20:59:14 after updating.. then rebooting.. is "fatls mmc 0:1" still show a clean fat? Aug 03 20:59:19 ## Booting image at 80000000 ... Aug 03 20:59:19 Bad Magic Number Aug 03 20:59:41 if I create the vfat fs again and copy the files, everything works Aug 03 20:59:50 I'll try here. I thing I pulled an updated kernel during the massive updates I've done today. Aug 03 20:59:58 rsalveti: i normally only see that problem when the FAT index tables are corrupted or it contains data that can't be parsed by u-boot Aug 03 21:00:01 rcn-ee_: didn't try this yet Aug 03 21:00:30 prpplague: the weird thing is that once I created it again and try for the second time, I get the same error Aug 03 21:00:43 so it's not a problem on how ogra is creating it Aug 03 21:01:13 rsalveti, it just seems very weird, i've been doing stuff like: http://pastebin.com/ccM2tDH5 for a good 2 years on my beagle.. Aug 03 21:01:18 rsalveti: yea, i suspect that is some bug, i'll see if i can recreate the issue here and have a look Aug 03 21:01:26 argh, my screen size is totally wrong Aug 03 21:02:12 rcn-ee_: yep, but I'm doing this on panda, with beagle it works fine Aug 03 21:02:46 GrueMaster: try updating and running flash-kernel to see how it goes Aug 03 21:02:57 ah sorry... wrong board.. i still haven't got my panda's usb port to work yet for any upgrade.. ;) Aug 03 21:03:00 if flash-kernel is not called by default Aug 03 21:04:35 prpplague: could be something wrong with our u-boot version too Aug 03 21:08:00 * rsalveti still needs to get the u-boot hash we're using for omap4 Aug 03 21:12:31 rsalveti: i suspect there is a minor fat bug in the u-boot we are using Aug 03 21:12:36 rsalveti: it is rather old Aug 03 21:13:14 prpplague: oh, ok, do you know if we already have the fix somewhere? Aug 03 21:13:53 rsalveti: i've only seen the problem occur a couple of times, and i just assumed i had damaged the partition with my testing Aug 03 21:14:01 rsalveti: so, no, i doubt there is a fix Aug 03 21:14:16 rsalveti: i'll put it on my bug list to see if i can get to the bottom of it Aug 03 21:15:50 prpplague: do you know where can I find the "upstream" development of the uboot for panda? Aug 03 21:16:04 * rsalveti is just new regarding panda work Aug 03 21:16:17 GrueMaster: you may also know it Aug 03 21:17:02 Not sure, but it is part of the image, so the packaging tools should know. Aug 03 21:20:43 GrueMaster: L24.7git20100624 Aug 03 21:22:51 rsalveti: sakoman is doing some contracting for TI to upstream all the new support to u-boot Aug 03 21:22:52 http://git.omapzoom.org/?p=repo/u-boot.git;a=summary Aug 03 21:22:59 rsalveti: negative Aug 03 21:23:13 rsalveti: he has a repo somewhere Aug 03 21:23:29 prpplague: this link I guess is the one used for our package Aug 03 21:23:39 rsalveti: basically yea Aug 03 21:23:45 rsalveti: one sec, getting you some urls Aug 03 21:23:57 but I guess I have sakoman's repo too Aug 03 21:24:14 rsalveti: you need the patches related to framebuffer supporting resizing Aug 03 21:24:32 and you need to plugin monitor before xserver starts.. Aug 03 21:24:40 (because no KMS yet) Aug 03 21:24:41 robclark: the patches I got from mythripk made my hdmi work, but with a very wrong size Aug 03 21:24:49 640x480? Aug 03 21:24:58 robclark: but I'm not even using X11 :-) Aug 03 21:25:03 is it a DVI monitor? Aug 03 21:25:10 robclark: probably something like that Aug 03 21:25:15 has dvi and hdmi Aug 03 21:25:23 but I'm using just the hdmi Aug 03 21:25:34 so there were a few patches that I think might be interesting to you... hang on Aug 03 21:25:36 robclark: the fonts are huge and distorted (from console) Aug 03 21:26:03 is the picture scrambled, or just distorted? Aug 03 21:26:19 rsalveti: my core development has been to get the hardware verification done, now that it _is_ done, i'll be looking at getting all the code consoladated Aug 03 21:27:09 rsalveti: from here: http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commits/L24.7_panda-hdmi-patches I think you might want Aug 03 21:27:17 "add callback to notify client of resolution change" Aug 03 21:27:18 rsalveti: do you care to get his ppt with slides describing the status, or just the url? Aug 03 21:27:26 "register callback to get notified of resolution change" Aug 03 21:27:34 prpplague: could be the whole thing, np Aug 03 21:27:40 that should at least give you an ok picture.. Aug 03 21:28:41 and then for some monitors that are falling back to 640x480, when a higher resolution would be possible, "better support for DVI monitors".. although I think that will mainly matter when you plug in over DVI.. it is basically adding support for parsing parts of EDID that HDMI screens don't seem to use Aug 03 21:29:48 rsalveti: you've got spam Aug 03 21:30:14 prpplague: nice, so the idea is to get most of this support directly on u-boot upstream Aug 03 21:30:19 prpplague: nice, thanks Aug 03 21:31:01 robclark: http://www.flickr.com/photos/rsalveti/4857717987/ Aug 03 21:32:11 rsalveti: Ok, I am finally finished with the updating. flash-kernel updates the boot partition, but somehow it is getting clobbered. I think it may be a file order thing. Will do some more testing. Aug 03 21:32:30 GrueMaster: ok Aug 03 21:32:59 rsalveti: that's a "feature" for people who have visual handicaps Aug 03 21:33:11 rsalveti: I suspect you need the patches related to resizing Aug 03 21:33:15 for sure :-) Aug 03 21:34:10 rsalveti: what you might want to do before spending much time, is just pull my branch and build it.. or send me an email addr and I can send you my uImage.. Aug 03 21:34:10 robclark: will try some of your patches Aug 03 21:34:17 just to try and see if that solves Aug 03 21:34:23 robclark: yep, that's why I'm doing now Aug 03 21:34:27 *what Aug 03 21:34:28 then you can try and merge on top of ubuntu kernel Aug 03 21:34:33 ok, cool Aug 03 21:35:00 if that still doesn't work, email me the contents or /sys/devices/omapdss/display0/edid Aug 03 21:35:28 Interesting. The fat partition has a date stamp of 1969-12-31 16:00 Aug 03 21:35:40 GrueMaster: ops Aug 03 21:35:59 The files are ok and have the correct timestamp. Aug 03 21:36:29 GrueMaster: when I tested the md5 was ok, but u-boot didn't like it Aug 03 21:36:35 had to recreate the fs Aug 03 21:37:35 Don't tell me we found another mkfs glitch. Aug 03 21:39:09 u-boot just didn't like it, probably Aug 03 21:40:36 What I am seeing is that when I mount the filesystem on my x86, the date of the mount directory becomes 12-31-1969. That is a glitch somewhere in the filesystem, and I am willing to bet it is during fs creation. Aug 03 21:40:46 mount Aug 03 21:40:49 gah. Aug 03 21:42:38 Nevermind. I have a new SD that still has the factory format. same issue there. Aug 03 21:43:09 yep, the bug happens every time with me Aug 03 21:43:48 back to my earlier theory. It is a location issue on the drive. testing now. Aug 03 21:52:54 rsalveti: I'm thinking it is an issue with the uboot fat code. I don't think it can read beyond a certain point or something, as flash-kernel renames the existing files and creates new files. That or uboot can't handle file fragmentation. Aug 03 21:53:43 GrueMaster: it's also happening when I just copy a new file on top of an older one Aug 03 21:53:53 but yes, probably on u-boot Aug 03 21:53:58 still needs more debugging Aug 03 21:54:26 Copying a new file over an old one without syncing could be a separate issue. Aug 03 21:54:41 GrueMaster: so currently if we get a new kernel on a pandaboard the panda is not going to boot anymore :-) Aug 03 21:55:57 Yep. That's what my test currently shows. Aug 03 21:56:18 I have another part of the test to run. Give me a few. Aug 03 21:56:28 GrueMaster: ok Aug 03 21:56:50 GrueMaster: would you mind to open a bug later on about this issue? Aug 03 21:58:40 will do after this reboot. Aug 03 21:58:59 nice, thanks :-) Aug 03 22:08:06 very interesting. As a test, I renamed the new kernel & initrd as uI*.old and renamed the old kernel & initrd from uI*.bak to uI* (shortened for explanatory reasons). It still loaded the new kernel. Aug 03 22:10:19 interesting Aug 03 22:10:57 I'm not even sure what that suggests. iirc, the fat system should just change the entry in the directory table, not the order or the fat table starting point. Aug 03 22:11:57 Ok, filing a bug, then doing more research. Aug 03 22:27:44 rsalveti: Bug #613230 Aug 03 22:27:47 Launchpad bug 613230 in u-boot-omap4 (Ubuntu) "u-boot fails to load new kernel fromm boot partition after kernel update (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/613230 Aug 03 22:30:39 GrueMaster: interesting, after renaming the old files it's still trying to load the newer ones Aug 03 22:30:47 yep Aug 03 22:39:46 something is trashing the fat directory tree in uboot. Try running "mmcinit 0;fatls mmc 0". Aug 03 22:39:54 ugly Aug 03 22:40:20 probably u-boot itself is trashing the fat directory tree Aug 03 23:04:01 robclark: now my monitor is on but I get nothing at the screen Aug 03 23:04:22 will try to get a console at the image, oem-config is turned on by default Aug 03 23:04:50 hmm.. can you add omapdss.debug=1 to bootargs.. and send me bootlog and /sys/devices/omapdss/display0/edid? Aug 03 23:04:58 omapdss DISPC error: SYNC_LOST_DIGIT Aug 03 23:05:13 this is the only error message I'm getting Aug 03 23:05:15 sure, 1 min Aug 03 23:05:21 hmm.. Aug 03 23:05:33 this is with L24.7_panda-hdmi-patches branch? Aug 03 23:06:07 L24.7_panda-hdmi-patches yep Aug 03 23:06:25 hmm Aug 03 23:06:31 tested with ubuntu's config file Aug 03 23:06:47 just removed the commit 109fd14008275c9be56562612e3f8d8628e444b0 as it didn't compile with it Aug 03 23:07:08 "add support for external tracing" Aug 03 23:07:15 ok, that won't matter.. Aug 03 23:07:22 yep Aug 03 23:07:37 (I need to update that one.. but I guess ubuntu config enables trace..) Aug 03 23:07:47 probably Aug 03 23:07:57 let me get the kenel log with debug Aug 03 23:08:09 k, thx Aug 03 23:08:12 GrueMaster: do you know from top of your head how to disable oem-config? Aug 03 23:08:45 not off hand. Never really tried before. Aug 03 23:09:24 I'm sure there is a way to get it to run oem-config instead of oem-config-gtk. Aug 03 23:09:32 * rsalveti will just remove it to see if works Aug 03 23:29:10 My brain is fried. bugging out for the evening. Ping me if you need me. Aug 03 23:41:53 robclark: I'm now finally able to get a console! will send you the logs in a minute Aug 03 23:47:02 robclark: sent Aug 03 23:47:23 ok, got it.. lets see now Aug 03 23:48:58 rsalveti: does it seem reasonable for it to be trying to pick 1680x1050? Aug 03 23:49:19 hm, it's a full hd monitor Aug 03 23:49:40 but it should work, I guess Aug 03 23:49:50 it sees a couple 1920x1080 resolutions.. but doesn't like them for some reason.. Aug 03 23:50:09 maybe pixel clock isn't matching.. I have to compare to the all_timings table.. Aug 03 23:51:31 hm Aug 03 23:52:34 ok.. mythripk had one more patch.. that disregards exact timing (backporch/frontporch/syncwidth).. as long as the sum of them still matched.. with that patch, your monitor would pick 1920x1080.. Aug 03 23:52:49 I'm not sure if that would help with the sync lost.. but let me see if I can find the patch.. Aug 03 23:53:00 robclark: ok, I can test it here Aug 03 23:54:06 rsalveti: do you mind doing a bit of surgery to apply patch, or do you want me to quickly rebase it first? Aug 03 23:54:31 robclark: just send me the patch, I can try change it here Aug 03 23:54:31 it looks like it won't directly apply, but mostly of a result of nearby changes in debug printouts.. Aug 03 23:54:44 ok Aug 03 23:55:54 ok, sent.. if you have any trouble with making it apply, let me know.. it's not a problem to rebase it on latest branch Aug 03 23:56:16 robclark: ok, thanks Aug 03 23:56:36 basically instead of doing a straight memcmp() of the contents of the timing struct, it is checking if the sums of the h or v fields matches Aug 03 23:57:03 (I'm not entirely sure if that is a valid thing to do or not.. so it would be interesting to know if it works) Aug 03 23:58:51 ok, give me a minute Aug 03 23:59:04 ok, no prob Aug 04 00:04:56 building Aug 04 00:16:24 robclark: Timing Info pixel_clk = 148500 Aug 04 00:16:24 Xresolution =1920 Aug 04 00:16:24 yresolution =1080 Aug 04 00:16:39 ok.. is that working any better? Aug 04 00:16:50 or same behavior, different resolution? Aug 04 00:18:45 it seems to be better, let me just try with the full X11 image Aug 04 00:19:38 ok.. I think then it should work w/ x11 as long as the monitor is detected before x11 opens the framebuffer and reads the resolution.. Aug 04 00:50:06 robclark: hi Aug 04 00:50:16 hi rsalveti Aug 04 00:50:19 robclark: X11 is able to find the correct resolution but I get nothing on the screen Aug 04 00:50:26 just a black screen Aug 04 00:50:40 hmm.. console is ok, but X11 is not? Aug 04 00:50:44 that is a strange one.. Aug 04 00:50:59 robclark: nops, console seems not to work fine either Aug 04 00:51:22 hmm.. what changed between now and the one that was working? Aug 04 00:51:55 do you still have omapdss.debug=1 in your bootargs? Aug 04 00:52:25 if so you should be able to unplug and replug the monitor, and it will re-detect and print out all the same info about what resolution it picks and so on.. Aug 04 00:52:36 the other one is not working, I thought it worked because my monitor turned on and so on Aug 04 00:53:04 but when I changed to get the console messages I got nothing :-( Aug 04 00:53:19 oh, but you never actually saw anything on screen with will X11 fs or with console only fs? Aug 04 00:54:11 robclark: nops, my monitor shows the resolution and etc and tuns on, that's why I thought it would work better Aug 04 00:54:40 oh.. darn.. Aug 04 00:54:48 but while testing it better I found that I can't see anything in the screen Aug 04 00:55:33 do you have parse-edid? If so you can check whether your monitor is requiring negative hsync or vsync pulse.. (which isn't implemented yet) Aug 04 00:55:50 if you don't, I will check in a couple minutes Aug 04 00:55:55 robclark: nops Aug 04 00:56:03 where can I find it? Aug 04 00:56:21 sudo apt-get read-edid :-) Aug 04 00:56:27 easy :-) Aug 04 00:56:45 yup Aug 04 00:57:01 1 sec, let me install this package Aug 04 01:04:26 installed on the target, easier, let me just boot it again Aug 04 01:05:02 rsalveti: don't need to reboot Aug 04 01:05:07 just run: Aug 04 01:05:19 I removed the card to install the package, that's why Aug 04 01:05:26 parse-edid /sys/devices/omapdss/display0/edid Aug 04 01:05:28 oh, ok Aug 04 01:06:07 brb Aug 04 01:06:15 robclark: http://paste.ubuntu.com/472889/ Aug 04 01:07:11 robclark: nops, it seems fine Aug 04 01:07:17 weird Aug 04 01:09:54 rsalveti: hmm, weird.. Aug 04 01:10:47 well, let me fwd your boot log and edid to mythripk and see if she has any suggestions when she wakes up Aug 04 01:11:04 robclark: ok, thanks Aug 04 01:11:07 hang on.. I'll drop off momentarily when I login to vpn Aug 04 01:11:12 ok Aug 04 01:14:33 rsalveti: ok, well I think if you revert mythripk's patch that I fwd'd, and my "better support for DVI monitors" patch, that you should at least get a good picture at 640x480... Aug 04 01:15:08 one other thing to try first, if your monitor has both HDMI and DVI ports, you and you have an HDMI->DVI adapter, you could try the DVI port.. Aug 04 01:15:23 robclark: I'm trying it now Aug 04 01:15:24 sometimes you will get a different EDID on DVI vs HDMI port.. Aug 04 01:16:02 (and might be worth to forward to mythripk and myself the edid file and bootlog on DVI port too, just for good measure) Aug 04 01:16:17 robclark: do I need to use omapdss.hdmimode=0 omapdss.hdmicode=35? Aug 04 01:16:45 no.. those will be ignored now with mythripk's patches to configure the resolution based on EDID.. Aug 04 01:17:19 although you could still try to echo different values to the custom_edid_timings file under sysfs.. and see if there are some other working resolutions.. Aug 04 01:17:32 oh, true Aug 04 01:17:40 see http://omapedia.org/wiki/Bootargs_for_enabling_display Aug 04 01:17:45 yep, my monitor doesn't even turns on Aug 04 01:18:01 with dvi port -> hdmi->dvi adapter Aug 04 01:18:18 for ex, echo 350 > custom_edid_timings... will be equiv to hdmimode=0, hdmicode=35 Aug 04 01:18:27 nice Aug 04 01:18:31 hmm, ok.. Aug 04 01:19:11 well, I guess since you had a scrambled picture when it was falling back to 640x480, at least that resolution should work.. it is just a matter of figuring out why it doesn't like the higher resolutions.. Aug 04 01:20:05 (but try this with a console only build.. the console driver will handle the resolution switch when you write different values to custom_edid_timings.. but X11 won't) Aug 04 01:20:35 sure Aug 04 01:20:42 robclark: so, back to the older kernel Aug 04 01:20:56 to many new issues with this tree :-) Aug 04 01:21:15 sigh Aug 04 01:21:32 I take it 1280x1024 was working ok when you hard-coded it? Aug 04 01:22:08 robclark: never actually tried with dvi, was mainly debugging hdmi Aug 04 01:22:16 this is the combination GrueMaster is using, that's why Aug 04 01:22:17 :-) Aug 04 01:22:25 oh, ok Aug 04 01:22:47 first day I'm actually trying to make the panda display work Aug 04 01:23:49 well, fwiw if GrueMaster has a different monitor, his issues could be different... but sending a boot log with omapdss.debug=1 and edid file to mythripk and myself are a good idea for everyone who is having hdmi issues Aug 04 01:25:29 lag is also using a lg monitor (different version) and he's getting the same issues I'm getting with mine Aug 04 01:25:45 so ti seems that some lg monitors may have this issue Aug 04 01:26:04 *it Aug 04 01:26:15 hmm.. I thought lag's monitor was working after one of mythripk's patches.. or was that only the monitor he was using at the sprint? Aug 04 01:26:42 * robclark is wondering whether he missed one of mythripk's patches? Aug 04 01:27:11 robclark: could be the one he was using at the sprint Aug 04 01:27:18 hmm, ok Aug 04 01:58:06 robclark: echo 161 > /sys/devices/omapdss/display0/custom_edid_timing sets to the correct resolution with the older kernel Aug 04 01:58:34 and it works fine, I can log in the console successfully Aug 04 01:58:59 just need to debug why the first resolution is wrong Aug 04 01:59:29 hmm.. Aug 04 02:00:02 the kernel I'm using is the maverick one plus http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commit/c6019735b852b625918c9f3788058f7b0fd5f607 Aug 04 02:00:14 and http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commit/1e8b137986d8f53a393e5e0e44baa8fc62bcd254 Aug 04 02:00:22 hm, shit Aug 04 02:00:35 there's one other change that I had to add to this kernel Aug 04 02:00:45 + mdelay(500); Aug 04 02:00:48 what was it using when you added mythripk's patch? 820? Aug 04 02:00:58 maybe this is the cause of not working with the latest tree Aug 04 02:01:13 at least mythripk said that without this patch it wouldn't work Aug 04 02:01:31 oh.. hmm, I have mdelay(50) instead of mdelay(500).. Aug 04 02:01:38 http://kernel.ubuntu.com/git?p=lag/ubuntu-maverick.git;a=blobdiff;f=drivers/video/omap2/dss/hdmi.c;h=0830bbc6baed30e04afca7b1c1a5b83ec298c890;hp=a8bedb1facd324eb6d2f07767ae6399f7c24ec3a;hb=76dd0768b77f731bbe6ad4df55379734f3a38770;hpb=f6c95ac85cfa087a84cd82564dcaea8ce4a6c867 Aug 04 02:01:40 maybe I pulled that from an earlier version of her patch Aug 04 02:02:12 could you go back to my branch plus mythripk's patch, but change 50 to 500? Aug 04 02:02:28 and if that doesn't work, cat /sys/devices/omapdss/custom_edid_timing Aug 04 02:02:40 that will tell if it is picking 820 instead of 161 Aug 04 02:03:32 yep, will recompile it here and grab a beer Aug 04 02:03:47 sure, sounds like a good plan :-) Aug 04 02:04:43 beer is always a good plan :-) Aug 04 02:05:23 indeed Aug 04 02:29:26 robclark: nops, same result :-( Aug 04 02:29:41 can you cat custom_edid_timings? Aug 04 02:29:55 I'm curious if it is picking 820 instead of 160.. Aug 04 02:30:10 and you should be able to manually overwrite by writing 160 to that file Aug 04 02:30:54 (sorry, I mean 161) Aug 04 02:32:59 root@beagle-maverick:~# cat /sys/devices/omapdss/display0/custom_edid_timing Aug 04 02:33:00 161 Aug 04 02:33:19 default with your kernel + mythripk's patch Aug 04 02:33:26 hmm, ok.. odd.. same timings and it is working with the old kernel.. Aug 04 02:33:38 yep Aug 04 02:33:52 and this is with mdelay(500) instead of 50? Aug 04 02:35:06 robclark: yes Aug 04 02:35:38 hmm.. ok, so not a matter of picking which timings.. and not an mdelay() issue.. Aug 04 02:35:49 yep Aug 04 02:36:03 so I guess there must be some other patch missing.. or one of the new patches breaks something.. hmm Aug 04 02:36:18 probably Aug 04 02:38:07 hmm, I don't see any other patches if I look in the commitlog of ubuntu kernel.. Aug 04 02:38:31 ugh Aug 04 02:38:52 probably a new patch that breaks something Aug 04 02:39:02 yeah Aug 04 02:39:04 cause the ubuntu kernel is still using a quite old hash Aug 04 02:40:02 well, most of the patches are related either to resolution switch (which shouldn't matter in this case, because you are still picking 1920x1080 which is the default startup resolution).. and EDID parsing.. so it must be something more subtle.. **** ENDING LOGGING AT Wed Aug 04 02:59:57 2010