[13:03] <XavB> fabo: Hi, I am having a look to the ubuntu-build-service git tree and I am trying to "play" with quantal-armhf-ubuntu-desktop. I have installed the packages/live-build_3.0~a47-1_all.deb from the tree, but when I run configure I have: unrecognized option '--hostname'  andunrecognized option '--username'
[13:03] <XavB> fabo: is it expected?
[13:15] <fabo> XavB: yes, live-build 3.0a45 is required
[13:16] <fabo> XavB: I need to update the configs to latest live-build but it wasn't a high prio
[13:16] <XavB> fabo: thx for the answer, to play with the tool, I have just removed hostname and username in a first stage...
[13:17] <XavB> fabo: can you give me the most "up to date" wiki doc about lb?
[13:18] <fabo> XavB: I should drop a47 from the tree to avoid confusion
[13:19] <fabo> XavB: best doc is upstream > http://live.debian.net/manual-3.x/
[13:19] <fabo> everything else is straight forward as we use pristine live-build
[13:20] <fabo> XavB: feel free to poke for any questions
[13:30] <XavB> fabo: ok, so the config is up to date, I am just missing a new version of live-build, correct? I looked for the last build on linaro-maintainers/tools ppa, but only 45 is there...
[13:30] <XavB> thx for the doc link
[13:41] <ppisati> rsalveti: lp 1065902
[13:41] <ubot2> Launchpad bug 1065902 in linux-ti-omap4 "black/blue screen before installer, tty switch fixes it" [Medium,Confirmed] https://launchpad.net/bugs/1065902
[13:42] <ppisati> rsalveti: do you think we have any chance to get a fix for that?
[13:42] <ppisati> rsalveti: before release i mean
[13:53] <fabo> XavB: correct
[13:54] <rsalveti> ppisati: I'll check if a newer driver improves that, but I'm unable to reproduce this issue with my pandas
[13:54] <fabo> XavB: take the one coming from the git repo
[13:54] <rsalveti> ppisati: which panda are you using? (rev, es x normal)
[13:54] <ppisati> rsalveti: panda es
[13:54] <rsalveti> seems the issue is just happening on a quite recent panda rev
[13:54] <rsalveti> which is known to TI
[13:55] <ppisati> rsalveti: and did they fix it?
[13:55] <rsalveti> nops
[13:55] <ppisati> ogra_: which panda do you have?
[13:55] <ogra_> EA1, several ESes
[13:56] <ogra_> and i think one was called an A1 (older one first gen)
[13:56] <ppisati> i've other pandas here, i can check if it appears with every of them
[13:56]  * ppisati tries
[13:56] <ogra_> it doesnt appear on mine
[13:57] <ppisati> ogra_: are you sure?
[13:57] <ppisati> ogra_: did yoiu try beta2?
[13:57] <ogra_> the only screen issue i have is the green screen on dpms
[13:57] <ogra_> indeed i did
[13:57] <ogra_> but i dont need to switch ttys fo rthe green stuff
[13:57] <ogra_> i also did test the recent dailies
[13:57] <rsalveti> yeah, seems to be related with a more recent rev
[13:58] <rsalveti> I installed the image just a few days ago, without any issues
[13:58] <ogra_> same for me
[13:59] <ogra_> all recent images i tried were fine apart from the dpms stuff
[13:59] <ogra_> (and the webkit breakage)
[14:00]  * ppisati tries a panda reva4
[14:01] <ppisati> i've the same problem
[14:01] <ppisati> panda reva4
[14:04]  * ogra_ uses HDMI all the way btw
[14:04] <ogra_> no adapters, no DVI involved here
[14:05] <ppisati> i'm attached to the port closest to the nic
[14:05] <ppisati> i tried with and without adapter
[14:05] <ppisati> (i've a dvi to vga adapter)
[14:05] <ppisati> and in both cases, with a panda rev.a4 i get a black screen
[14:07] <ogra_> but you dont have a plain HDMI monitor you could use ?
[14:08] <ogra_> port closest to the nic is HDMI
[14:08] <ogra_> if oyu use DVI on the monitor dside you need to use the other port
[14:09] <ppisati> ogra_: no, vga and dvi input-p input
[14:09] <ppisati> ogra_: i've always used that port and it has always worked
[14:09] <ogra_> hmm, k
[14:09]  * ppisati tries with the other port
[14:14] <ppisati> ok, using tje other port i get a displat but it's like 800x600
[14:14] <ppisati> jsalisbury: ^
[14:14] <ppisati> ogra_: anyhow, can you add your findinds to the bug report?
[14:14] <ppisati> rsalveti: anyhow, can you add your findinds to the bug report?
[14:14]  * ppisati tries again with the ES
[14:25] <jsalisbury> ppisati, I can give it a try too
[14:27] <ppisati> ok, connecting to my tv (native hdmi) it works
[14:30] <jsalisbury> ppisati, I don't get any display at all when using the other(HDMI) port.  Even if I switch ttys
[14:31] <ppisati> jsalisbury: wait
[14:31] <jsalisbury> ppisati, ack
[14:31] <ppisati> jsalisbury: it takes longer
[14:31] <jsalisbury> ppisati, ahh ok.
[14:31] <ppisati> jsalisbury: i get a display, but with a crappy resoltion like 800x600
[14:31] <ppisati> jsalisbury: while attaching the board to a device with a native hdmi port (my plasma tv), i get the video output ok
[14:32] <ppisati> jsalisbury: your monitor has a dvi input, right?
[14:32] <jsalisbury> ppisati, correct.  I use the DVI port on the panda.  Then I have a HDMI cable that attaches to a HDMI->DVI converter
[14:32] <ppisati> jsalisbury: same here
[14:33] <ppisati> jsalisbury: so the 3d driver changed "something" and we can't use the hdmi port (the one closest to the usb tower+nic) anymore
[14:33] <ppisati> jsalisbury: did you get a video output now?
[14:34] <jsalisbury> ppisati, just restarted and waiting still
[14:35] <ogra_> ppisati, i'm using the HDMI port just fine ... it might be that HDMI->DVI doesnt work though
[14:35] <ppisati> ogra_: you use the hdmi port with an hdmi monitor?
[14:35] <ogra_> yes
[14:35] <ogra_> straight
[14:35] <ppisati> ogra_: the cable/converter has worked fine so far
[14:35] <ppisati> ogra_: same here, it's just a cable
[14:35] <ppisati> i've another i can try that
[14:36] <ppisati> *another cable
[14:36] <ogra_> your TV works you say ?
[14:36] <rsalveti> my hdmi is working just fine
[14:36] <rsalveti> at es and 4430
[14:37] <ppisati> yes, with my tv everyhing was ok
[14:37] <ogra_> rightm, so its only DVI that has issues
[14:37] <ogra_> one way or the other
[14:37] <ppisati> well, two persons with the same issue
[14:37] <ppisati> sounds weird at least
[14:37] <ogra_> on DVI
[14:38] <ppisati> ogra_: i've used this setup since... maverick?
[14:38] <ppisati> ogra_: no prob at all
[14:38] <ogra_> sure
[14:38] <ogra_> but a lot changed
[14:38] <ppisati> yeah, but people who will try Q will still use the same setup
[14:38] <ogra_> there is a new xserver-xorg-video-omap we use now for exapmple
[14:39] <ogra_> that pvr driver made a leap jump version wise
[14:39] <ogra_> and there is new DSS code in the kernel
[14:39] <ppisati> ok, but if it worked before IMO it's a bug
[14:39] <ogra_> i dont say it isnt :)
[14:39] <ppisati> we can't just say "use a device with a native hdmi"
[14:39] <ogra_> we can
[14:40] <ogra_> well, we actually have to if it doesnt get fixed in time :)
[14:41] <ppisati> i'll update the lp bug with my findings
[14:41] <jsalisbury> ppisati, Using the HDMI port, I did eventually get the login screen.  However, after logging in, the screen went blank and never came back
[14:42] <ogra_> thats with a recent desktop image ?
[14:43] <jsalisbury> Thats with the daily image from the 11th
[14:44] <ppisati> i'm using autologin
[14:44] <ppisati> ah
[14:44] <ppisati> it goes black if i leave it idle
[14:44] <ppisati> uhm
[14:44] <jsalisbury> ppisati, hmm, I cant switch to any other ttys either
[14:45] <xnox> ogra_: bug 1066880
[14:45] <ubot2> Launchpad bug 1066880 in ubiquity "12.10 Beta 2 arm image acts like an ISO not like 12.04" [Undecided,New] https://launchpad.net/bugs/1066880
[14:45] <ogra_> jsalisbury, the daily desktop image from the 11th still had the webkit breakage, how did you install it ?
[14:47] <jsalisbury> ogra_,  The usual way.  I dd'd the image to the sd card, powered up and access the installer.
[14:47] <ogra_> hmm, k
[14:47] <jsalisbury> ogra_, I ran into this other bug we are talking about now, but not the webkit breakage
[14:48] <ogra_> well, webkits bnreakage was when the installer dies right after the user setup page
[14:53] <st3fan> so my pandaboard with 12.10 keeps hanging/crashing .. what can i do to debug this?
[14:54] <st3fan> this morning it was frozen in xscreensaver
[14:54] <ppisati> jsalisbury: bug updated
[14:54] <jsalisbury> ppisati, ack
[14:55]  * ppisati tries with another cable, just in case
[14:56] <ogra_> st3fan, xscreensaver ? we dont install that ...
[15:00] <st3fan> ogra_: it is a not an xscreensaver problem .. i've also had many of the same same freezes on an idle unity desktop
[15:01] <st3fan> i have a console hooked up to the serial port but it only prints 'Booting kernel' and then goes silent. Is there a way to get all kernel diagnostics out there?
[15:01] <ogra_> well, my board was last installed on friday and idled over rthe weekend, no such issue here
[15:02] <ogra_> yes, drop quiet from /etc/default/flash-kernel and run sudo flash-kernel
[15:02] <ogra_> that should print all rteh kernel messages
[15:03] <st3fan> cool i will try that
[15:03] <ogra_> oh, wait, you said serial
[15:03] <st3fan> yes
[15:03] <ogra_> you also want to add: console=ttyO2,115200n8
[15:03] <ogra_> the redirects the output to serial
[15:03] <ogra_> same file, same line
[15:03] <st3fan> also in flash-kernel?
[15:03] <ogra_> yes
[15:03] <st3fan> i'm at work now but i will try tonight
[15:04] <ogra_> just replace "quiet" with the console option
[15:04] <st3fan> yup
[15:05] <st3fan> what does flash-kernel do?
[15:08] <st3fan> is the kernel loaded from flash storage on the pandaboard?
[15:10] <ogra_> there is no flash in pandaboards
[15:10] <ogra_> the kernel comes from your SD card
[15:11] <ogra_> flash-kernel originally only used flash this the name ... but with other methods showing up it also flashes to SD or whatever your board requires
[15:11] <ogra_> s/this/thus/