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