**** BEGIN LOGGING AT Mon Nov 28 02:59:57 2011
Nov 28 08:56:03 <punxos> Hi
Nov 28 10:28:15 <ppisati> ogra_: do i remember misremember, or does the preinstalled image resize during the first boot?
Nov 28 10:28:42 <ogra_> it does
Nov 28 10:29:04 <ogra_> it resizes, does some config bits and then does an auto-reboot
Nov 28 10:31:17 <ppisati> ogra_: but there's no output on console
Nov 28 10:31:30 <ogra_> on which image ?
Nov 28 10:31:34 <ppisati> ogra_: previously i remeber something was written out
Nov 28 10:31:41 <ppisati> preinstalled oma3
Nov 28 10:31:42 <ppisati> omap3
Nov 28 10:31:45 <ogra_> desktop images write to the splash only
Nov 28 10:31:56 <ogra_> its just the server image that writes to console
Nov 28 10:32:26 <ppisati> ok
Nov 28 10:33:16 <ogra_> what are you installing, desktop ?
Nov 28 10:33:40 <ogra_> you will need a monitor for that, else you cant use oem-config on the second boot
Nov 28 10:38:34 <ppisati> ogra_: saw it
Nov 28 10:38:43 <ogra_> :)
Nov 28 10:38:58 <ppisati> ogra_: actually, the image from friday still had a 3.0.x kernel (and thus broken usb) but the video was ok
Nov 28 10:39:09 <ppisati> ogra_: 28nov image has kernel 3.2.x
Nov 28 10:39:23 <ppisati> ogra_: so good usb but my monitor says "out of range freq"
Nov 28 10:40:00 <ppisati> ogra_: now i wonder if it's a "new feature" of the new kernel or any other new component
Nov 28 10:40:18 <ogra_> we didnt change anything in arm land yet
Nov 28 10:40:39 <ogra_> the build should be identical to oneiric, modulo the general package updates we inherit
Nov 28 10:40:48 <ppisati> all the pkgs are still O? at least the kernel is not
Nov 28 10:40:49 <ogra_> (which indeed could be at fault)
Nov 28 10:41:04 <ppisati> btw, this on a xm rev c
Nov 28 10:41:17 <ogra_> no, thats what i mean ... there were package updates ... but no specific arm changes yet
Nov 28 10:41:24 <ppisati> ok
Nov 28 10:41:52 <ogra_> does linaro have rev C's ? they probably know what could cause it
Nov 28 10:43:17 <ppisati> the problem with the rev c was usb only
Nov 28 10:43:23 <ppisati> but has been fixed upstream
Nov 28 10:43:33 <ppisati> what i discovered this morning
Nov 28 10:43:42 <ppisati> is that we lost video output now
Nov 28 10:44:10 <ogra_> right, which could be either xorg or the kernel DSS driver
Nov 28 10:44:36 <ppisati> right
Nov 28 10:46:33 <ogra_> and to my knowledge nothing in xfbdev (which is our default Xserver on all arm images) has changed
Nov 28 10:51:35 <ogra_> to me it smells like an EDID issue
Nov 28 10:51:44 <ppisati> we dropped one patch in 3.2
Nov 28 10:51:55 <ppisati> but according to the maintainer, it was not needed anymore
Nov 28 10:52:57 <ogra_> well, i know rsalveti tried to get some EDID stuff upstream for omap3 since a while, that might have landed and be broken or something similar
Nov 28 10:53:26 <ppisati> is there a deafult user before oem-config completes?
Nov 28 10:54:17 <ogra_> no
Nov 28 10:54:34 <ogra_> do you get the out of sync message only when x starts or already before
Nov 28 10:54:39 <ppisati> sorry
Nov 28 10:54:54 <ppisati> during the boot, i get a yellow/orange screen
Nov 28 10:55:05 <ppisati> then during boot it says "no signal detected"
Nov 28 10:55:08 <ppisati> and it turns off
Nov 28 10:55:32 <ppisati> and gitweb on kernel.ubuntu.com is slow...
Nov 28 10:55:35 <ogra_> orange screen ?
Nov 28 10:55:43 <ogra_> nothing in ubuntu creates orange screens
Nov 28 10:56:09 <ogra_> are you sure there is no nand on that XM ?
Nov 28 10:56:23 <ppisati> it's a brand new xm
Nov 28 10:56:35 <ogra_> (which carries something like an angstrom u-boot ... (which in turn uses orange screens on u-boot))
Nov 28 10:57:01 <ppisati> btw, we dropped this oneiric/master @ 1704827e32f20204b6af9b8143aff226211ac270
Nov 28 10:57:05 <ogra_> i know theoretically there shouldnt be nand, but i know that a handfull XMs were producsed with it
Nov 28 10:57:11 <ppisati> "UBUNTU: ARM: Adding regulator supply for vdds_sdi."
Nov 28 10:57:20 <ogra_> hmm
Nov 28 10:58:18 <ppisati> http://paste.ubuntu.com/752363/
Nov 28 10:58:23 <ppisati> here's my boot
Nov 28 10:58:34 <ppisati> i added ttyO2 to /etc/init
Nov 28 10:58:43 <ppisati> now let me add a root user
Nov 28 10:59:07 <ogra_> OMAP3 Beagle board + LPDDR/NAND
Nov 28 10:59:12 <ogra_> there you have your issue
Nov 28 10:59:19 <ppisati> wait
Nov 28 10:59:29 <ppisati> with a 3.0.x kernel the video output was working
Nov 28 10:59:30 <ogra_> it doesnt even seem to load the boot.scr
Nov 28 10:59:40 <ogra_> looks like you boot from NAND
Nov 28 10:59:57 <ppisati> no no
Nov 28 11:00:03 <ppisati> it loads boot.scr
Nov 28 11:00:04 <ogra_> or no, it actually reads boot.scr a bit later
Nov 28 11:00:05 <ppisati> "Loaded script from boot.scr"
Nov 28 11:00:19 <ogra_> *after* it complained it couldnt find it
Nov 28 11:00:33 <ogra_> *** Warning - readenv() failed, using default environment
Nov 28 11:00:56 <ogra_> it definitely uses the wrong x-loader
Nov 28 11:01:16 <ogra_> our x-loader comes from the u-boot package since oneiric, it would have the same build data
Nov 28 11:01:36 <ogra_> which it apparently doesnt
Nov 28 11:01:53 <ogra_> there must be a key combo to enforce loading from SD ...
Nov 28 11:01:58 <ppisati> "Texas Instruments X-Loader 1.5.1 (Jul 15 2011 - 21:29:14)"
Nov 28 11:02:03 <ppisati> is it wrong?
Nov 28 11:02:09 <ogra_> try holiding down the user button wuring boot and see
Nov 28 11:02:17 <ogra_> *during
Nov 28 11:02:22 <ppisati> let's try
Nov 28 11:03:14 <ogra_> you should never see an organe screen on an ubuntu boot
Nov 28 11:03:19 <ogra_> *orange
Nov 28 11:03:38 <ppisati> but that's when i press the reset button/during the bootloaders
Nov 28 11:03:56 <ppisati> perhaps is an artifact of the reboot
Nov 28 11:04:03 <ogra_> i doubt that
Nov 28 11:04:04 <ppisati> (some regs have some values etcetc)
Nov 28 11:04:07 <ppisati> btw
Nov 28 11:04:15 <ogra_> i would think its x-loader
Nov 28 11:04:15 <ppisati> can you confirm me the X-loader version?
Nov 28 11:05:07 <ogra_> should be from the same build as u-boot
Nov 28 11:05:13 <ogra_> they come from the same source package
Nov 28 11:05:24 <ogra_> and your u-boot clearly states it finds NAND
Nov 28 11:06:08 <ppisati> no
Nov 28 11:06:10 <ogra_> hmm, though it matches the actual last x-loader upload
Nov 28 11:06:10 <ppisati> it says
Nov 28 11:06:13 <ppisati> "NAND:  0 MiB"
Nov 28 11:06:23 <ogra_> i wonder why ...
Nov 28 11:06:25 <ppisati> IMO the bootloader part is correct
Nov 28 11:06:41 <ppisati> let's see if i have an O installation on anotther sd
Nov 28 11:06:43 <ogra_> but you see orange if the board powers up ...
Nov 28 11:06:46 <ppisati> i can try that kernel
Nov 28 11:06:52 <ppisati> on the other installation
Nov 28 11:07:01 <ppisati> true
Nov 28 11:07:11 <ogra_> and the only thing loaded first is x-loader
Nov 28 11:07:30 <ppisati> ok
Nov 28 11:07:34 <ppisati> now i resetted the board
Nov 28 11:07:38 <ppisati> and pressed the button
Nov 28 11:07:41 <ppisati> i'm at the
Nov 28 11:07:47 <ppisati> u-boot prompt
Nov 28 11:07:55 <ppisati> and i've the yellow/orange screen
Nov 28 11:07:56 <ppisati> so
Nov 28 11:08:02 <ogra_> hmpf
Nov 28 11:08:04 <ppisati> it loaded x-loader and u-boot only
Nov 28 11:08:09 <ppisati> let me try with a cold boot
Nov 28 11:09:28 <ppisati> ah!
Nov 28 11:09:31 <ppisati> with a cold boot
Nov 28 11:09:35 <ppisati> no orange screen
Nov 28 11:09:41 <ogra_> aha
Nov 28 11:09:47 <ppisati> the screen stays off
Nov 28 11:10:11 <ppisati> no matter how many times i reset it
Nov 28 11:10:19 <ppisati> if i stop the board at the u-boot promp
Nov 28 11:10:20 <ppisati> t
Nov 28 11:10:23 <ppisati> the screen is off
Nov 28 11:11:26 <ppisati> first boot completed
Nov 28 11:11:31 <ppisati> screen is still off
Nov 28 11:11:35 <ppisati> reset
Nov 28 11:11:35 <ogra_> hmm
Nov 28 11:11:42 <ogra_> auto-reset ?
Nov 28 11:11:45 <ppisati> and there we go
Nov 28 11:11:49 <ppisati> orange screen
Nov 28 11:11:54 <ppisati> no, reset button
Nov 28 11:12:06 <ppisati> let me try thus kernel on O
Nov 28 11:12:11 <ogra_> k
Nov 28 11:28:08 <fisuk> is there a bug in video hw decode on oneiric or am i doing something wrong (custom rootstock + omap4-extras installed + totem as a video player) as totem crashes from time to time (segfault) and there's strange artefacts displayed on the screen?
Nov 28 11:28:25 <fisuk> video scaling seems to be a bit off too..
Nov 28 11:28:49 <fisuk> (on pandaboard that is)
Nov 28 11:32:43 <ogra_> rootstock shouldnt be used anymore
Nov 28 11:33:32 <ogra_> use a properly built image
Nov 28 11:41:26 <fisuk> so like, ubuntu core?
Nov 28 11:43:12 <ogra_> ubuntu-aerver if you want without desktop, ubuntu-desktop if you want with desktop
Nov 28 11:43:21 <ogra_> ubuntu-core if you know how to build images
Nov 28 11:44:01 <ogra_> -core is just a base for building your own stuff if you exactly know what you are doing, its completely unconfigured and doesnt even have things likd dhcp support by default
Nov 28 11:47:27 <fisuk> hmm, alright
Nov 28 11:51:05 <fisuk> well, i'll give the server a spin and if it feels too bloaty, i'll go for the core... thanks for the pointers.
Nov 28 13:14:37 <rsalveti> ogra_: edid should be in for 3.3, at least robclark said it's now at staging-next
Nov 28 13:15:01 <rsalveti> we could backport it easily I believe, as it'll only affect staging
Nov 28 13:15:22 <rsalveti> ppisati: but I don't believe we tested beagle with 3.2 upstream yet
Nov 28 13:16:08 <ppisati> ok
Nov 28 13:16:22 <ppisati> when you test it, tell me if get video out
Nov 28 13:19:53 <rsalveti> ppisati: is this issue happening with the current precise tree?
Nov 28 13:20:01 <rsalveti> ppisati: will give it a try here
Nov 28 13:20:17 <ppisati> yes
Nov 28 13:20:23 <ppisati> P/master
Nov 28 13:20:41 <ppisati> i was trying the preinstalled image from 28Nov
Nov 28 13:21:11 <ppisati> when i noticed that my screen was blank
Nov 28 14:39:15 <ppisati> ogra_: seems it's the 3.2 kernel
Nov 28 14:39:20 <ogra_> aha
Nov 28 14:39:28 <ppisati> ogra_: installing it on a brand new O/omap3
Nov 28 14:39:34 <ogra_> intresting that it gets orange
Nov 28 14:39:34 <ppisati> ogra_: kills the video
Nov 28 14:39:38 <ppisati> wait
Nov 28 14:39:43 <ppisati> it's orange even in O
Nov 28 14:39:48 <ppisati> what is strange is that
Nov 28 14:39:51 <ppisati> X starts
Nov 28 14:40:13 <ppisati> but my mionitor stays off
Nov 28 14:40:47 <ogra_> hmm, sounds like EDID again
Nov 28 14:41:35 <ppisati> but rsalveti said it didnb't enter mainline
Nov 28 14:41:50 <ppisati> now i'm uptading it
Nov 28 14:41:54 <ogra_> but it could also be that it is caused by the resolution we set on the cmdline
Nov 28 14:42:05 <ogra_> you could tzry to mangle boot.scr
Nov 28 14:42:05 <ppisati> well
Nov 28 14:42:12 <ppisati> uhm
Nov 28 14:42:18 <ppisati> actually IMO
Nov 28 14:42:29 <ppisati> X thinks is connected to something else
Nov 28 14:42:43 <ppisati> else it wouldn't start
Nov 28 14:42:44 <ogra_> it uses /dev/fb0
Nov 28 14:42:59 <ogra_> however that was set up by the kernel
Nov 28 14:43:17 <ogra_> it doesnt mangle anything and just adopts the existing data the kernel has set
Nov 28 14:43:27 <ogra_> (resolution, frequency etc)
Nov 28 14:44:05 <ppisati> i'll try to see if there's any difference in dmesg
Nov 28 14:44:09 <ogra_> yeah
Nov 28 14:44:20 <ppisati> and X log
Nov 28 14:44:26 <ogra_> yup
Nov 28 14:45:00 <ogra_> if its just the splash, it could well be a plymouth bug
Nov 28 14:46:56 <ppisati> [    3.394592] omapfb omapfb: no driver for display: dvi
Nov 28 14:46:56 <ppisati> [    3.394622] omapfb omapfb: cannot parse default modes
Nov 28 14:46:58 <ppisati> uhm
Nov 28 14:47:08 <ogra_> aha
Nov 28 15:01:05 <rsalveti> ppisati: iirc there's a new dvi driver, or something like that
Nov 28 15:01:12 <rsalveti> maybe it's just not enabled at the config
Nov 28 15:01:14 <rsalveti> not sure
Nov 28 15:03:15 <ogra_> i'm still stunned that it turns your screen orange :)
Nov 28 15:06:25 <rsalveti> ogra_: that's u-boot
Nov 28 15:07:01 <ogra_> evil, can we disable that =
Nov 28 15:07:02 <ogra_> ?
Nov 28 15:07:20 <rsalveti> ogra_: probably, any reason to disable it?
Nov 28 15:07:34 <ogra_> its orange !
Nov 28 15:08:22 <rsalveti> ogra_: haha, guess we can change to any other color
Nov 28 15:08:32 <rsalveti> ideally it'd be nice to have a picture of something there
Nov 28 15:08:41 <ogra_> the ubuntu splash
Nov 28 15:08:43 <ogra_> ;)
Nov 28 15:09:09 <infinity> Or just the same purple that the Ubuntu plymouth theme uses.
Nov 28 15:09:28 <infinity> Since grub does that too.
Nov 28 15:10:46 <ynezz> but I've heard, that orange color shows you better the crappy color reproduction of your LCD :p
Nov 28 15:11:26 <Wellark> ogra_: thanks for the invitation :)
Nov 28 15:12:29 <rsalveti> infinity: yeah, should be easy to change it to purple
Nov 28 15:20:13 <rsalveti> ppisati: ogra_: cool, just noticed my edid changes at the dvi driver was applied at the kernel
Nov 28 15:20:17 <rsalveti> that's why, we have a new panel now
Nov 28 15:20:20 <rsalveti> panel-dvi.c
Nov 28 15:20:25 <rsalveti> that's based on my implementation
Nov 28 15:20:35 <rsalveti> that in theory probes and parses the edid
Nov 28 15:31:40 <rsalveti> ppisati: I believe it's just a config change here, I'm building the kernel now and will check in a few
Nov 28 15:37:48 <ppisati> ah
Nov 28 15:37:59 <ppisati> i was just reverting some changes in omapfb
Nov 28 15:38:32 <ppisati> "OMAPFB: find best mode from edid"?
Nov 28 15:38:34 <ppisati> this one?
Nov 28 15:38:37 <ppisati> rsalveti: ^^
Nov 28 15:38:47 <rsalveti> ppisati: I don't believe we need to revert anything
Nov 28 15:38:59 <rsalveti> ppisati: panel_dvi is =m
Nov 28 15:39:03 <rsalveti> should probably be =y
Nov 28 15:39:09 <rsalveti> and generic_panel should be disabled
Nov 28 15:39:14 <rsalveti> that's my guess
Nov 28 15:40:51 <ppisati> saw it
Nov 28 15:43:41 <ogra_> rsalveti, and i suspect we should drop the hardcoded resolution from boot.scr
Nov 28 15:43:45 <ogra_> :)
Nov 28 15:43:56 <rsalveti> ogra_: probably :-)
Nov 28 16:13:43 <ppisati> rsalveti: yes it works
Nov 28 16:13:49 <ppisati> with panel_dvi=y
Nov 28 16:14:18 <rsalveti> ppisati: awesome, and should also be working with edid
Nov 28 16:14:27 <rsalveti> ppisati: try removing the cmd line that forces a resolution
Nov 28 16:17:45 <ogra_> awesome that this didnt break it :)
Nov 28 16:36:01 <ppisati> ok, pushed
Nov 28 16:37:02 <ppisati> so, you want me to drop:
Nov 28 16:37:09 <ppisati> "omapfb.mode=dvi:1280x720MR-16@60"
Nov 28 16:37:13 <ppisati> right?
Nov 28 16:37:56 <rsalveti> ogra_: https://blueprints.launchpad.net/u-boot-linaro/+spec/spl-enablement-for-omap3
Nov 28 16:38:00 <rsalveti> ppisati: yes
Nov 28 16:39:03 <ogra_> rsalveti, awesome !
Nov 28 16:41:41 <ppisati> yes, it works
Nov 28 16:43:42 <rsalveti> ogra_: https://blueprints.launchpad.net/u-boot-linaro/+spec/investigate-common-spl-for-omap3-and-omap4
Nov 28 16:43:48 <rsalveti> ppisati: great!
Nov 28 16:45:31 <rsalveti> ogra_: seems you can now remove the omapfb cmd line from the kernel then
Nov 28 16:45:52 <ogra_> rsalveti, well, once that kernel is in
Nov 28 16:46:00 <ogra_> or that config change rather
Nov 28 16:46:11 <rsalveti> ogra_: well, the current kernel doesn't work anyway
Nov 28 16:46:16 <ogra_> yeah
Nov 28 16:46:28 <ogra_> not a good start of the milestone freeze :/
Nov 28 16:46:59 <rsalveti> at least we found the fix at monday
Nov 28 16:47:38 <ogra_> ppisati, do you see any chance there will be a kernel upload today or tomorrow with that fix ?
Nov 28 16:53:37 <ppisati> ogra_: hope so
Nov 28 16:53:46 <ogra_> k
Nov 28 16:53:57 <ogra_> we need to tell GrueMaster to hold off on omap3 testing
Nov 28 16:54:37 * GrueMaster holding off.  (will read backscroll to get rest of what he is holding off from).
Nov 28 16:54:47 <ogra_> broken display driver
Nov 28 16:55:07 <ogra_> you might be able to test server omap3 if you feel like ... but that will also need re-testing for the new kernel
Nov 28 20:26:49 <micahg> suihkulokki: did you try to just disable webrtc w/out reenabling system vpx for chromium?
**** ENDING LOGGING AT Tue Nov 29 02:59:57 2011