[13:37] <ogra_> rsalveti, pvr drivers uploaded to NEW, talk to infinity for an archive admin review to get them out there ;)
[14:55] <GrueMaster> ogra_: Know any logical reason why the arm team was assigned bug 856988?
[14:55] <ubot2`> Launchpad bug 856988 in gstreamer0.10 "totem cannot play quicktime file after upgrade to oneiric" [High,Confirmed] https://launchpad.net/bugs/856988
[14:56] <GrueMaster> Bug was filed against amd64.  Not a single arm reference in the bug that I saw.
[15:00] <ogra_> just unassign it
[15:00] <ogra_> seriously not an arm prob
[15:04] <NCommander> GrueMaster: with apt-setup, my test failed, and I'm not sure why, I'll stab it more in my today
[15:07] <ogra_> GrueMaster, i pinged kate about it, she will look after the meeting why she assigned it to arm
[15:08] <GrueMaster> She probably wanted the ubuntu-audio team.
[15:08] <ogra_> or -desktop since i see that seb did set the importance already
[15:08] <ogra_> we'll hear after the meeting i guess ;)
[15:12] <GrueMaster> Oh, beta 2 has opened up in the iso tracker.  Guess I can shut down the daily image tests I have automated.
[15:42] <jimerickson> not getting any hdmi output after todays update.
[15:56] <Riddell> ogra_, GrueMaster, Daviey: bug 961133 updated with logs from today's image
[15:56] <ubot2`> Launchpad bug 961133 in linux "Ubuntu Desktop ARM Images do not boot on my Pandaboard ("EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)")" [Medium,Confirmed] https://launchpad.net/bugs/961133
[16:00] <ogra_> Riddell, looks all proper, are you sure you have the monitor plugged in to the right port ?
[16:00] <ogra_> (try changing them for a test)
[16:01] <ogra_> it definitely boots and also seems to do the reboot after resizing the FS just fine ... theoretically it should now sit with ubiquity on the screen
[16:01] <Riddell> ogra_: no I'm not sure because I have had inconsistent advice from this channel and from tests, it works with the DVI port with oneiric images.  ubuntu server requires the HDMI port
[16:02] <GrueMaster> ubuntu server is headless.  Doesn't care about video ports.
[16:02] <ogra_> well, just pulg it over to the other port, i'm never sure which one the kernel driver supports in which TI kernel
[16:02] <ogra_> right, server runs on serial
[16:02] <GrueMaster> (kernel might).
[16:02] <ogra_> Riddell, in any case that looks like a successful boot
[16:03] <ogra_> if there are issues i would blame the graphics driver ot the monitor
[16:03] <ogra_> s/ot/or/
[16:04] <Riddell> ogra_: and yet it's not
[16:04] <ogra_> ??
[16:04] <ogra_> not what ?
[16:04] <Riddell> ogra_: the graphics driver works fine with ubuntu server precise and ubuntu desktop oneiric
[16:04] <Riddell> not successful
[16:04] <ogra_> so what do you see on the screen then between the two u-boot runs i see there ?
[16:05] <Riddell> ogra_: there is no output to the monitor
[16:05] <ogra_> how long does it take approximately beweeen the two boot runs ? and does the left LED blink in a consant ~1sec fequency after it sits there on the serial ?
[16:07] <Riddell> I don't know, I haven't timed it, would it help you if I did?
[16:07] <ogra_> the reszizing run usually takes about 1-2min, then it reboots (note that only happens once if you first boot a new image)... if after that you see the left LED blink constantly it means that everything is fine but the screen doesnt output
[16:07] <Riddell> I don't know which is the left LED but one LED is currently doing two blinks in rapid succession then about 1 sec off
[16:07] <ogra_> sounds about right
[16:07] <ogra_> it has definuitely to do with the graphics/monitor
[16:08] <Spider-Pork> hi, i need to edit boot.script and then get the boot.scr. What should I do? Thank you
[16:08] <ogra_> what kind of monitor is that ?
[16:08] <Riddell> ogra_: acer DVI
[16:08] <ogra_> Spider-Pork, already installed image ?
[16:08] <ogra_> Riddell, is it capable of doing 720p and 1080p modes ?
[16:09] <Riddell> ogra_: I don't know what that means
[16:09] <ogra_> do you know which modes it supports ?
[16:09] <Riddell> ogra_: no
[16:09] <Spider-Pork> ogra_: yep
[16:09] <Spider-Pork> ogra_: i need to enable DVI output
[16:09] <Spider-Pork> as reported here http://omappedia.org/wiki/PandaBoard_FAQ#How_do_I_enable_DVI_output.3F
[16:09] <ogra_> the graphics driver reads the monitors EDID usually, if it doesnt find modes it can support it can actually fall over
[16:10] <ogra_> Spider-Pork, after you edited /boot/boot.script, just run sudo flash-kernel
[16:10] <ogra_> it will update boot.scr
[16:10] <Spider-Pork> cool thank you
[16:10] <Spider-Pork> my problem now is that i can't log in with X  :)
[16:11] <Spider-Pork> i can't see no output on my DVI monitor
[16:12] <ogra_> Riddell, when you used the precise server image, did you actually see anything before X came up ? (plymouth ... console etc)
[16:12] <Spider-Pork> before apt-get install omap4-extras was connected to HDMI
[16:12] <Spider-Pork> but after upgrade i can't see anything on HDMI
[16:12] <Riddell> ogra_: no I had to start X from the serial command line
[16:12] <GrueMaster> Riddle;  What monitor do you have?  What are the specs?
[16:12] <ogra_> Riddell, aha, sounds like an issue with the framebuffer driver and your monitor
[16:13] <Riddell> GrueMaster: this one http://search.acerdirect.co.uk/acer/V223hqv
[16:15] <ogra_> Riddell, between oneiric and precise the graphics driver was cvompletely redone by TI, that might explain your issues (though i would still love to know where your weird bootmessages came from when you fiddled with the image)
[16:16] <ogra_> Riddell, talk to robclark if he knows anything about issues with that monitor (he maintains the graphics stack and we actually know that some monitors and brands dont work well at all)
[16:16] <Riddell> ogra_: robclark is a TI guy?
[16:16] <ogra_> yes
[16:17] <GrueMaster> Looking at the specs for that monitor, It is 1920x1080 (HD 1080).  But, port wise it only lists vga.  Does it have DVI & HDMI?
[16:17] <ogra_> Riddell, and about your complaint that it is hard to install ubuntu on panda, 100s of other users dont have any probs at all ;)
[16:17] <Riddell> GrueMaster: DVI yes, HDMI no
[16:18] <ogra_> right, intrestingly http://www.acerdirect.co.uk/ACER_55cm_21.5_Wide_16_9_FHD_5ms_20000_1_ACM_black_MPRII_EURO-UK_EMEA_200ni_ET.WV3HE.017/version.asp says 0 for DVI and HDMI ports
[16:18] <GrueMaster> As to today's image, I am not getting video either.  Until that gets sorted, please stick with beta 1.
[16:19] <robclark> Riddell, the display part should be largely similar..  but I'd start w/ just trying to get fbcon (ie. text) up, without yet starting x..
[16:19] <robclark> drm.debug=7 in bootargs, and pastebin the boot log would be helpful
[16:19] <Riddell> robclark: what is fbcon?
[16:19] <robclark> ie. text console
[16:19] <GrueMaster> You can use today's ubuntu-server image for this test.
[16:20] <Riddell> GrueMaster: why is that better?
[16:20] <robclark> or just put "text drm.debug=7" in your bootargs
[16:20] <ogra_> right, it shoudl come up with a framebuffer console after install and show you a login prompt onm the screen
[16:20] <jimerickson> GrueMaster: am not getting any hdmi output after todays update either.
[16:20] <ogra_> Riddell, because you cant run the desktop installer without a screen
[16:21] <Riddell> boot args are set like that? http://omappedia.org/wiki/PandaBoard_FAQ#How_do_I_saveenv_for_boot_args_on_a_PandaBoard.3F
[16:22] <ogra_> Riddell, just run through the server install, then edit /boto/boot.script and change the bootargs there ... then you run sudo flash-kernel and reboot
[16:22] <GrueMaster> robclark: THis might be an indicator:  sysfs: cannot create duplicate filename '/devices/platform/omap/omapdss_dss'
[16:22] <ogra_> oh
[16:22] <robclark> hrm?
[16:22] <ogra_> s/boto/boot/
[16:22] <robclark> how can that happen?
[16:23] <ogra_> wasnt there a fix from rsalveti for exactly such an issue ?
[16:23] <GrueMaster>  One sec and I'll pastebin a dmesg.
[16:23] <robclark> maybe, I've not seen that before
[16:24] <ogra_>   * debian/patches/111_armel-drv-fallbacks.patch:
[16:24] <ogra_>     - Avoid loading the driver to test if it's available. Xorg will later load
[16:24] <ogra_>       and validate the module, and if it's already loaded it'll trigger an
[16:24] <ogra_>       error and invalidate the driver (LP: #959928)
[16:24] <ogra_> though i think that was focusing on pvr
[16:24] <GrueMaster> http://paste.ubuntu.com/896634/
[16:25] <Spider-Pork> ogra_: I done the steps you suggest to me. Now the board won't boot
[16:25] <GrueMaster> dmesg log from my ubuntu-server install (preseeded btw - woot!)
[16:25] <ogra_> Spider-Pork, well, i have no idea about the omappedia stuff, we otften have people that follow outdated stuff from there, what exactly did you change in your boot.script ?
[16:26] <robclark> hmm, do we somehow end up with two omapdss platform devices?  That would cause all hell to break loose...
[16:26] <Spider-Pork> ogra_: as suggested here http://omappedia.org/wiki/PandaBoard_FAQ#How_do_I_enable_DVI_output.3F I added "omapdss.def_disp=dvi" at the end of the file
[16:27] <ogra_> no idea if that works or not with the current images
[16:27] <Spider-Pork> the problem is that don't boot
[16:27] <Spider-Pork> the SD card led are dead
[16:27] <Spider-Pork> SD card and run led
[16:28] <ogra_> and you definitely only added that arg and properly ran flash-kernel after that ?
[16:28] <Spider-Pork> yep
[16:28] <ogra_> sounds like your boot partition is trashed somehow ...
[16:28] <Spider-Pork> cool
[16:28] <ogra_> this was an official ubuntu image ?
[16:28] <Spider-Pork> fortunately I got a safe copy of boot.scr
[16:28] <ogra_> (downloaded from cdimage.ubuntu.com)
[16:28] <Spider-Pork> ogra_: yep
[16:29] <robclark> fwiw, I'm not sure, all the legacy omapfb bootargs are ignored, omapdss bootargs, not sure if they could have some unintended result..
[16:29] <Spider-Pork> https://wiki.ubuntu.com/ARM/OMAP
[16:29] <ogra_> i dont think its your boot.scr
[16:29] <robclark> omapdrm will just use any/all displays that it detects a connection on
[16:30] <ogra_> if the LEDs dont light up the bootloader (MLO) is not found ... if your boot.scr would be trashed it would still boot into a bootloader session
[16:30] <Spider-Pork> oh well, 3 hours of ubuntu installation and upgrade in the trash
[16:30] <ogra_> did you install any third party stuff ?
[16:30] <Spider-Pork> only omap4-extras
[16:30] <ogra_> an ubuntu install usually doesnt take more than 20min on the panda
[16:30] <Spider-Pork> for video acceleration
[16:30] <Spider-Pork> the installation yep
[16:30] <Spider-Pork> but the upgrade ...
[16:31] <ogra_> using the icon on the desktop ? or following some weird omappedia docs again ?
[16:31] <Spider-Pork> http://omappedia.org/wiki/Ubuntu_PPA
[16:31] <ogra_> sigh
[16:31] <Spider-Pork> with shell command
[16:32] <Spider-Pork> I apologize if I followed wrong guide. What link should follow?
[16:32] <ogra_> you shoudl just click the TI icon on the desktop
[16:33] <ogra_> (note that this only is available on released images, for 12.04 there is no working GLES driver yet)
[16:33] <Spider-Pork> I'm using 11.10
[16:33] <ogra_> well, there you have the TI icon on the launcher after first boot
[16:33] <ogra_> it does all you need
[16:34] <Spider-Pork> OK, I'll reinstall the whole prebuild image
[16:34] <ogra_> (and the person who added the sed command to that wikipage to trash your sources.list should be smacked ... this should rather link to the launchpad documentation for enabling PPAs)
[16:35] <Spider-Pork> ah ok :)
[16:35] <Spider-Pork> image i took here are ok? https://wiki.ubuntu.com/ARM/OMAP
[16:35] <Spider-Pork> *images
[16:35] <ogra_> https://wiki.ubuntu.com/ARM/OMAP has links to ubuntu wikipages that document enabling the PPA and the like
[16:35] <ogra_> or the respective subpages have, cant remember ...
[16:36] <ogra_> yeah, folllowing the ubuntu wiki should generally get you everything working
[16:36] <ogra_> at least for released images we test and verify the docs and images every time before release
[16:37] <Spider-Pork> ok so I'll follow that guide, thank you
[16:38] <ogra_> :)
[16:50] <Riddell> Daviey: today's ubuntu server image gives me 100s of lines like this: Use of uninitialized value $value in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 65, <$__ANONIO__> line 23345.
[16:57] <GrueMaster> Riddell: Where are you seeing that?
[16:58] <Riddell> GrueMaster: "today's ubuntu server image"
[16:59] <GrueMaster> can you be a little more specific?  As in "I am not seeing this anywhere, but would like to try to reproduce it".
[17:00] <Daviey> Riddell: Can you provide more before/after logging.
[17:00] <Daviey> on a call.. will investigate shortly after
[17:00] <Riddell> GrueMaster: booted the server image, it did the resizing fine, on second boot I get that message repeated indefinately
[17:00] <GrueMaster> ogra_: btw:  using your boot.scr & preseed.cfg, system booted straight through to login w/o human intervention.
[17:01] <GrueMaster> Riddell: I am not seeing that at all.
[17:01] <GrueMaster> Can you double check your md5sum on the image?
[17:01] <GrueMaster> Also, try blanking and reflashing the SD (in case it has some corrupted bits).
[17:02] <Riddell> GrueMaster: 4b7d83d50edd57024bcc370ecb248224  precise-preinstalled-server-armhf+omap4.img.gz
[17:11] <ogra_> GrueMaster, cool, well, i tested it, so i would be surprised if it would stop working within two days ;)
[17:11] <GrueMaster> ogra_: Only issue I have is it doesn't pull the hostname.  I'll double check my preseed though.
[17:12] <ogra_> did you put in a hostname actually ?
[17:12] <ogra_> the original pressed you added didnt have one
[17:12] <ogra_> (it used the system fallback in the preseed ... which would be localhost)
[17:13] <GrueMaster> d-i netcfg/get_hostname string unassigned-hostname is what netboot uses.
[17:13] <ogra_> right, that means "use the default"
[17:14] <ogra_> if you set foo instead of unassigned-hostname it should set it to foo
[17:15] <GrueMaster> I thought it would get it from dhcp.  Maybe I am using a boot cmdline for that.
[17:15] <ogra_> hmm, probably another bug we need to hunt down
[17:16] <ogra_> i thought it uses the system default, but dont quote me on that
[17:18] <GrueMaster> Might be a d-i thing.
[17:53] <Riddell> robclark: here's the serial output from adding drm.debug=7 http://paste.kde.org/445214/
[17:53] <Riddell> is that what you mean by boot log?
[18:01] <robclark> Riddell, hmm, you might need some loglevel=10 or something like that.. so that we actually see the traces..
[18:01] <robclark> or just try and run dmesg
[18:02] <robclark> (if the kernel is built w/ large enough log buffer we might not loose the traces we want to see)
[18:02] <Riddell> robclark: http://starsky.19inch.net/~jr/tmp/dmesg
[18:03] <robclark> oh, and you need to add drm.debug=7 in bootargs
[18:03] <robclark> looks like that is still missing
[18:12] <Riddell> robclark: http://starsky.19inch.net/~jr/tmp/dmesg any better now?
[18:16] <robclark> Riddell, yes, much..
[18:19]  * Riddell wanders off in hunt for other monitors to try
[18:19] <robclark> hmm, what was the issue now?  Looks like it finds and configs hdmi for 1080p..
[18:19] <Riddell> robclark: the monitor does not show anything
[18:20] <robclark> hmm..
[18:20] <Riddell> robclark: I have a DVI-D monitor which is plugged into the HDMI port
[18:20] <robclark> oh, I think you need to add one more bootarg..
[18:20] <robclark> you are missing console=tty0
[18:20] <robclark> (you should have two console='s
[18:20] <robclark> )
[18:20] <Riddell> works fine manually installing ubuntu-desktop and starting lightdm from login
[18:21] <GrueMaster> Also, what image is this?  Beta 1?  It isn't the same issue as the daily image.
[18:21] <Riddell> (from an ubuntu-server image)
[18:21] <Riddell> GrueMaster: it is ubuntu server beta 1
[18:21] <Riddell> works fine with oneiric plugging the same monitor into the DVI port
[18:22] <robclark> well, at least the display part looks ok.. if you add the second console= you should see boot console on screen as well..
[18:22] <robclark> I'm not sure about lightdm, etc..  I'm using 12.04 but hadn't updated for a week or so, so I guess I'm not on latest
[18:23] <Riddell> well that just starts X
[18:23] <Riddell> anyway starting again with an ubuntu server install to try the console= thing
[18:24] <robclark> fwiw, might be quicker to just change bootargs..
[18:24] <robclark> ctrl-alt-f1, see if that can switch you to another VT
[18:24] <robclark> (if you have no other way to login and edit boot.script and flash-kernel)
[18:24] <Riddell> alas I already started wiping the card in preparation for going hunting monitors
[18:25] <robclark> heheh, ok
[18:29] <Riddell> robclark: is DVI the right port for oneiric and HDMI right for precise?
[18:29] <GrueMaster> Riddell: I only test on HDMI.  Since Maverick.
[18:29] <robclark> GrueMaster, Riddell, in theory which ever one is plugged in should work..
[18:30] <GrueMaster> (I do test DVI occasionally, but not as default).
[18:30] <robclark> maybe not a bad idea to test.. but it works for me w/ upstream (linus's tree) kernel
[18:30] <Riddell> why does it have two if DVI monitors can work with HDMI ports?
[18:30] <rsalveti> hdmi is known to work
[18:30] <rsalveti> ogra_: thanks
[18:31] <GrueMaster> Dual monitor support maybe?
[18:31] <rsalveti> Riddell: is this the issue that is happening just after the latest upload?
[18:31] <robclark> Riddell, to confuse people about which one to plug in :-P
[18:31] <robclark> (just kidding)
[18:31] <rsalveti> might be some conflict with the upstream changes
[18:31] <rsalveti> I need to check with the latest kernel
[18:31] <rsalveti> one upload was to sync with ti lt's 3.2 tree
[18:31] <rsalveti> and another to sync with ubuntu's changes and stable updates
[18:31] <GrueMaster> rsalveti: I think he is seeing other issues.  But the daily desktop does have a separate issue.
[18:32] <GrueMaster> rsalveti: See http://paste.ubuntu.com/896634/
[18:32] <GrueMaster> No video out.
[18:32] <Riddell> rsalveti: no
[18:32] <Riddell> why would minicom be giving me this corruption? http://paste.kde.org/445262/
[18:32] <rsalveti> GrueMaster: yeah, that's the one I saw a bug for
[18:32] <rsalveti> GrueMaster: can check that
[18:33] <GrueMaster> Riddell: That looks like bug 924399.
[18:33] <ubot2`> Launchpad bug 924399 in ubiquity "oem-config-debconf window size issue on keyboard selection screen" [Low,Confirmed] https://launchpad.net/bugs/924399
[18:33] <rsalveti> did you get the same behavior with screen?
[18:34] <Riddell> rsalveti: who me?
[18:35] <Riddell> GrueMaster: my screen looks not very much like that screenshot, no colours and the non US ascii characters are all garbled
[18:36] <rsalveti> Riddell: yeah
[18:36] <GrueMaster> Riddell: Minicom doesn't look the same as screen.
[18:37] <Riddell> rsalveti: I don't run screen, are you suggesting I run minicom inside a screen session?
[18:37] <rsalveti> no, just open screen directly instead minicom
[18:37] <Riddell> GrueMaster: well no, what does screen have to do with it?
[18:37] <GrueMaster> Riddell: screen /dev/ttyUSB0 115200.
[18:37] <Riddell> ah
[18:37] <GrueMaster> for one, it displays differently.
[18:38] <Riddell> this experience really does remind me of linux on a PC a la 1999
[18:51] <Riddell> robclark: added console=tty0 nothing on monitor
[18:53] <robclark> Riddell, if you still have "quiet splash" in bootargs, drop that and replace w/ "debug" (and possibly "text" if you don't want x to start)..
[18:54] <Riddell> how do I save the output with screen?
[18:54] <GrueMaster> robclark: Is there a way to see what his system reads for edid?
[18:54] <GrueMaster> Riddell: <ctrl>-A, H
[18:54] <robclark> GrueMaster, drm.debug=7.. will enable enough  traces to see the edid parsing.. (which looked  fine, btw)
[18:55] <GrueMaster> That should toggle logging on/off.
[18:56] <GrueMaster> robclark: ok.
[18:57] <Riddell> GrueMaster: that only saves what is currently on my terminal not the scrollback
[18:58] <GrueMaster> Riddell: What do you need in scrollback that you can't reproduce with your console history?
[18:58] <GrueMaster> (i.e. running dmesg again).
[18:58] <Riddell> GrueMaster: with screen I have no console history
[18:58] <GrueMaster> up arrow?
[18:59] <Riddell> um that depends on the context in which it is pressed
[18:59] <Riddell> there is no ability to use konsole's scroll function when running screen
[19:00] <GrueMaster> This I am painfully aware of.
[19:02] <Riddell> robclark: http://starsky.19inch.net/~jr/tmp/dmesg updated with quiet splash changed to debug
[19:02]  * Riddell goes in hunt for monitors again
[19:05] <robclark> well, looks like it is detecting the monitor, and parsing edid fine..
[19:05] <robclark> so I don't think another monitor would help..
[19:05] <robclark> from text console, try (possibly as root):  cat /dev/urandom > /dev/fb0
[19:05] <robclark> should produce snow/noise on the display
[20:38] <Riddell> robclark: well another monitor did not help
[20:38] <Riddell> http://starsky.19inch.net/~jr/tmp/dmesg-chris
[20:39] <Riddell> robclark: cat /dev/urandom > /dev/fb0 does nothing
[20:44] <robclark> oh, btw, if dvi doesn't work, I expect this is the reason:
[20:44] <robclark> omapdrm omapdrm.0: dvi has no driver.. skipping it
[20:44] <robclark> for hdmi, looks like there is some PM issue:
[20:44] <robclark> [    5.430938] Failed to start PHY
[20:44] <robclark> [    5.434265] omapdss HDMI error: failed to power on device
[20:45] <robclark> not sure if there were recently some kernel updates?
[20:45] <robclark> I do get something like that the very first time I try to power on HDMI, but on upstream kernel don't have all the other hdmi errors..
[20:46] <robclark> my guess is that tomi fixed something, and the fix isn't backported to ubuntu kernel..
[20:46] <robclark> at omapdrm level, all looks as it should be, no EDID or hot plug detect or similar issues
[20:47] <Riddell> mm
[20:47] <Riddell> ogra, GrueMaster: is there any arm guy in canonical in britain that I could meet up with to debug in person?
[20:47] <Riddell> e.g. in millbank?
[20:52] <robclark> Riddell, maybe give a try w/ the linux-ti-omap from ppa:tiomap-dev/omap-trunk ?
[20:52] <robclark> it is 3.3 based.. and the shape of omapdss has been steadily improving over last few kernel release cycles
[20:53] <Riddell> robclark: so I just add that PPA and install linux-ti-omap and that's all it needs?
[20:53] <robclark> I think so
[20:54] <robclark> I'm usually rebuilding kernel manually myself, but I think the one from the ppa should work (ie. not depend on anything else)
[20:56] <Riddell> http://starsky.19inch.net/~jr/tmp/dmesg-hdmi-projector  dmesg when plugged into hdmi projector
[20:57] <robclark> this stuff is very funny looking:  sysfs: cannot create duplicate filename '/devices/platform/omap/omapdss_dss'
[20:57] <robclark> something is a bit odd about that kernel, not sure if a bad merge of some patch or something??
[20:57] <robclark> Even back in 3.2 days, I didn't see stuff like that
[21:20] <Riddell> linux-ti-omap4: Installed: 3.3.0.1481
[21:21] <Riddell> http://starsky.19inch.net/~jr/tmp/dmesg-linux-ti-omap4-3.3.0.1481
[21:21] <Riddell> no change
[21:21] <Riddell> I do believe I have now lost the will to live
[21:21] <Riddell> oh my god
[21:22] <Riddell> it works
[21:22] <Riddell> just in time to save my life
[21:22] <Riddell> of course it doesn't work on the HDMI port, that would be too consistent
[21:22] <Riddell> it only works on the DVI port
[21:24] <Riddell> ogra, GrueMaster: well I have found a solution to bug 961133
[21:24] <ubot2`> Launchpad bug 961133 in linux "Ubuntu Desktop ARM Images do not boot on my Pandaboard ("EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)")" [Medium,Confirmed] https://launchpad.net/bugs/961133
[21:25] <Riddell> ogra, GrueMaster: who do I poke to get that backported?
[21:27] <GrueMaster> Not sure.  Part of the problem is that yours is a very isolated situation.  Have you been able to get video from the HDMI port on any previous image (Oneiric, Angstrom test image, etc)?  As I said earlier, I test the HDMI port almost exclusively as it is the default port.
[21:27] <GrueMaster> Now there is a possibility that the precise kernel has issues with the dvi port, I just haven't had the cycles to test tat use case.
[21:28] <GrueMaster> I am more concerned that you don't have HDMI, as that could indicate a defective board.
[21:31] <Riddell> well I'm out of lifeforce for today, if you have suggestions on how I can help more do let me know (such as finding other people in britain I can meet to debug with)
[21:32] <GrueMaster> If you can't get HDMI working with the images I suggested, my next suggestion would be for you to bring your board to UDS where I can test it directly, and possibly swap it for one of mine that is known to work.  Unfortunately, My status of UDS is uncertain at this moment.
[21:39] <Riddell> GrueMaster: yeah that's what I'll do but it would be nicer to be able to meet up with someone with the skills and hardware sooner
[21:39] <Riddell> slangasek: sladen is suggesting you will know such people ^^
[21:40] <GrueMaster> Outside of IS, I don't know of any internally.  Externally, I'm sure Linaro has people.
[21:42] <slangasek> Riddell: hi, skills and hardware for what?
[21:47] <Riddell> slangasek: for getting a working pandaboard
[21:47] <infinity> Riddell: I've not been paying attention here, but how on earth did we decide that your inability to mount a rootfs was a video driver ug?
[21:47] <infinity> s/ug/bug/
[21:48] <Riddell> infinity: because ogra decided my previous advice on editing the boot files was incorrect and that was his next idea
[21:48] <infinity> That error looks like what you'd see if you try to mount ext4 as ext3, though no idea how that would affect you, and only you.
[21:49] <infinity> Riddell: Or, was that error with some whacky modified bootfiles that forced rootfstype to ext3?
[21:49] <Riddell> maybe
[21:49]  * Riddell goes to make dinner with the last scrapes of his lifeforce
[22:00] <GrueMaster> infinity: I think what happened is he somehow clobbered his boot.scr, and that was the default boot environment from u-boot.
[22:01] <GrueMaster> I would have to reboot a system here and poke around in u-boot to confirm.
[22:06] <GrueMaster> As to his hdmi not working, up until today's image I would suspect a hardware issue.  Everything up to today has worked fine for me and others on this channel.
[22:20] <GrueMaster> rsalveti: I filed a bug for today's video issue.  Didn't see anything in LP prior to mine.  Bug 963512.
[22:20] <ubot2`> Launchpad bug 963512 in linux-ti-omap4 "Latest kernel updates broke video on omap4" [Critical,Confirmed] https://launchpad.net/bugs/963512
[22:21] <rsalveti> GrueMaster: ok, thanks
[22:21] <rsalveti> need to run a bisect
[22:25] <GrueMaster> Well, looks like it was uploaded into 20120322 image.  20120320 had 3.2.0-1409.12 kernel.
[22:26] <GrueMaster> And I know it worked.
[22:27] <rsalveti> yeah
[22:27] <rsalveti> the difference between 09 and 10 is the "stable" fixes :-)
[22:28] <GrueMaster> Pfft.  Figures.
[22:28] <GrueMaster> Last time a kernel guy told me that, they fried two of their babbages.  Literally.
[22:29] <GrueMaster> That was in Dublin iirc.
[22:29] <rsalveti> lol
[22:29] <rsalveti> true
[22:29] <chris_> quit
[22:30] <GrueMaster> resume
[22:39] <steev> suspend
[22:58] <GrueMaster> rsalveti: Do you know if someone will fix bug 943058 before 12.04 release?  This is becoming critical, as the start-r rev boards replaced earlier versions and started shipping in December.
[22:58] <ubot2`> Launchpad bug 943058 in linux-linaro-lt-mx5 "Kernel doesn't support usb on newer rev quickstart boards." [High,New] https://launchpad.net/bugs/943058
[23:39] <rsalveti> GrueMaster: I discussed that with the freescale landing team, and they said they would try to fix these issues in the next following days
[23:39] <rsalveti> so I hope to get a better kernel before release
[23:39] <GrueMaster> cool.  It would be a shame not to support the newer rev hw.
[23:41] <infinity> rsalveti: What are the odds on that "better kernel" also being 3.2? :/
[23:41] <rsalveti> infinity: I believe that's the goal
[23:41] <rsalveti> as currently 3.2 only works for mx6
[23:42] <infinity> rsalveti: If that goal is met, I'll buy you ridiculous amounts of beer at UDS (and you have no obligation whatsoever to take them back to the LT if you don't want to)
[23:42] <rsalveti> infinity: hahah, that's easy ;-)
[23:43] <GrueMaster> heh.  I'd add to that, but I'm not sure if I am going.
[23:43] <infinity> GrueMaster: It's a short trip, drive down.
[23:43] <rsalveti> well, it's a quite short travel for you
[23:43] <rsalveti> yeah
[23:43] <GrueMaster> Then what, sleep in NCommander's car?  Have you seen his car?
[23:44] <infinity> Get a cot in Oli's room.
[23:44] <infinity> He'll love that.
[23:44] <GrueMaster> Darth Vader sleeping mask and all.
[23:44] <infinity> But I just meant swing down for a day and say hi.
[23:44] <infinity> Ideally a party day. ;)
[23:45] <GrueMaster> Erm, it is an 8 hour drive, one way.
[23:45] <infinity> That's short!
[23:46] <GrueMaster> Not for me.  I'd have to stop and piddle every 2 hours, just to keep up with the coffee I'd need.
[23:48] <GrueMaster> infinity: While you are here, care to look at https://code.launchpad.net/~gruemaster/bacula/960761/+merge/99137 and tell me if I'm doing it right?  It can wait until post beta thaw.
[23:50]  * GrueMaster is learning the ropes of bug fixing where he can.
[23:52] <infinity> GrueMaster: Erm, yeah.  _Description implies that there are pofiles being merged into a final template.  I assume that's not the case here? :P
[23:53] <GrueMaster> I have know idea what the implication is.  In the case of the mysql package, I get a dpkg error on the one line with _Description.  On the pgsql, all lines had the error.
[23:54] <GrueMaster> I haven't looked to see if there are pofiles for these, but since the error is being generated, I would say no.
[23:58] <GrueMaster> At the very least, the templates should be consistent.  Either all _Description with po or not (s my patch changes).