=== ApOgEE__ is now known as ApOgEE === XorA|gone is now known as XorA [08:41] morning [10:02] guys, anyone know how to preserve a working serial console after framebuffer start? [10:25] ogra: do you know how i can preserve a working serial console even after the framebuffer start? [10:26] preserve ? [10:30] flag_: yep, when the framebuffer starts, my console dies and i have to switch to my monitor to see what's going on [10:31] you should get all boot messages if you set the cmdline to point to serial and drop the "quiet" from the cmdline [10:31] just edit /boot/boot.script and run sudo flash-kernel [10:36] ogra: and what if one the variable in my uboot environment is longer than 80 chars? on do i print it in its entirety? [10:37] you editor should display it fine [10:38] no no [10:38] i mean, i'm in uboot and i try to "printenv $var" [10:38] but the content of var is longer than 80chars [10:38] thus it's truncated [10:41] there is only the hardcoded env (which just loads the boot.scr file) you will have to change a lot if you dont just edit boot.scr [10:41] so printenv wont get you very far [10:41] if it cuts off after 80 chars thats an issue with your terminal program [10:41] or with the TERM variable you use [10:43] ogra: i'm using minicom [10:45] well, i'd really recommend to rather change your boot.scr than to poke around in the uboot env [11:26] ogra: ok, deleted quiet from bootargs in boot.scr, but still my console dies after: [11:26] ogra: Starting kernel ... [11:26] Uncompressing Linux........................................................................................................................................................................................... [11:26] you should get all boot messages if you set the cmdline to point to serial and drop the "quiet" from the cmdline [11:26] ogra: setenv bootargs root=UUID=e18764f5-7859-4509-gj48-bbcc01a1ff77 ro splash [11:27] did you set the cmdline to point to the serial terminal ? [11:28] ogra: bootargs=console=ttyS0,115200n8 root=UUID=54ec8187-d25e-413a-ac5b-99af9cc379fc (from u-boot) [11:28] is it like that in your boot.scr ? [11:30] ogra: bootargs in u-boot and boot.scr should match, right? [11:30] ogra: ah, got it [11:34] ogra: my bad, there was no console= in /boot/boot.scr but only in u-boot bootargs and i thought the kernel picked the console variable from u-boot [11:35] no, as i said above the u-boot stuff is totally irrelevant [11:35] its overriden as soon as boot.scr was loaded [11:39] ogra: k, thanks === zul_ is now known as zul [12:16] heh.. I forgot how long can arm system need to upgrade.. [12:17] heh [12:17] i did an ac100 update-manager upgrade over the weekend [12:17] took 36h [12:17] though on a very slow SD card [12:17] apt-get dist-upgrade from alpha3 to current - started >1h ago on sd [12:18] ogra: I reinstalled all packages on my dualcore atom in ~30 minutes. on 60MB/s sata [12:28] hmm [12:28] who fired off a netbook buid [12:28] *build [12:29] oh, not netbook, headless [12:46] http://www.computerworld.com.au/article/379549/calxeda_arm_chips_designed_480-core_servers/ - want one ;D [12:51] hrw: you can try convincing Rob or Martyn in Budapest [12:51] amitk: calxeda people? [12:52] hrw: yeah, you might know them as smoothstone people from previous UDSes [12:53] ah, right [12:53] the company which changes names === ogra is now known as Guest42034 === Guest42034 is now known as ogra_ [13:13] k, finally unity-2d on ac100 [13:19] you did not had it before? [13:19] we didnt have neon runtime detection in QT [13:19] ah, right [13:20] and after that i had to find out that the natty libc doesnt woork on tegra2 [13:20] o.. hows that? [13:20] http://gitorious.org/ac100/kernel/commit/227af643e6253e9a5c2a2f74468f855686c44117?diffmode=sidebyside [13:20] see #linaro, was just discussed there [13:21] time to blag a ac100 now then :-D [13:21] unity-2d is really snappy here [13:23] * hrw -> lunch [14:25] janimo, poke [14:26] ogra_: cool, so new qt really worked well for you? [14:26] yep [14:26] currently using it afer i spent the whole weekend to get natty running [14:26] nice [14:27] ogra_, hello [14:27] ogra_: did you find what were the issues? [14:27] libc is really badly broken on the ac100 [14:27] you said you had many issues last week [14:27] someone pointed me to http://gitorious.org/ac100/kernel/commit/227af643e6253e9a5c2a2f74468f855686c44117?diffmode=sidebyside [14:27] i'm currently running with the maverick libc pinned [14:27] janimo, so did you test headless ? [14:27] ogra_, not yet [14:28] seems we have a bunch of issues with oem-config/ubiquity [14:28] ogra_: ouch, got it [14:28] was trying tosee why images fail [14:28] ogra_, I saw you made some changes around oem-config/upstrart last week [14:28] janimo, the oem-config UI never comes up on serial [14:28] unless no tty exists at all [14:29] (i.e. it immediately works if i use a broken omapfb mode so ttys cant be started) [14:29] i suspect ubiquity/oem-config simply has no code for that and uses the first console it finds [14:30] the second big bug i see is that no user is created at all [14:30] what would a fix be? We need to keep ttys I think [14:30] no idea yet [14:30] i would suggest looking at d-i how it determines the used console [14:30] if werial is set we should defautl to use it i think [14:31] ok [14:31] effectively it doesnt seem like oem-config finishes its job [14:31] the most funny part is that the debconf package removal that runs afterrrr oem-config defaults to serial [14:31] so right now one can log in but even if oem-config is started by hand it does not run [14:31] ? [14:31] oem-config runs fine [14:32] but on tty1 [14:32] while it takes input from serial (since the kernel defaults to it as first console) [14:32] i can use my laptop kbd to fiddle with oem-config on the panda dvi screen [14:32] :) [14:33] it seems to just not use the right output [14:33] besides oem-config what else is broken? [14:33] i havent found ut why we dont have build attempts since three days (ampty mails usually suggest that the connection to the image builder failed= [14:34] well, oem-config doesnt create a user at all atm [14:34] ogra_, telepathy-glib FTBFS (regression) which holds up empathy [14:34] janimo, shouldnt affect headless at all [14:34] ogra_, indeed [14:34] we get empty build failure mails and i see no logs at all on the imagebuilder [14:35] who can debug that? [14:35] someone has changed livecd-rootfs or debian-cd ... or the ssh connection from cdimage to the image builder is broken [14:35] * ogra_ will research that [14:40] so there was one change in livecd-rootf that only affects edubuntu [14:42] * ogra_ cant see any changes that could have made our builds fail [14:42] lets try a manual build [14:52] seems to run flawless === zyga is now known as zyga-ill [15:32] http://cdimage.ubuntu.com/ubuntu-headless/daily-preinstalled/20110314/ [15:32] hmm, worked fine [15:41] janimo, ^^^ === XorA is now known as XorA|gone [17:27] ogra_, janimo: It still has issue with oem-config. The program is displaying the user interactive screens on the attached monitor, but only taking input via serial console. [17:27] ubuntu [17:27] oops [17:32] It also failed to create a user. May be due to no network. Not sure. [17:35] GrueMaster, yes, as discussed above [17:35] Bugs filed? [17:35] GrueMaster, fi you give a broken frambuffer setting it works (i.e. if ttyS/O is the only console around) [17:36] and the debconf bits after oem-config are on serial too [17:36] oem-config was simply never used on serial i think [17:36] so we are the first ones to face these issues [17:37] no bugs filed yet, no [17:37] I do see something interesting in the /var/log/oem-config.log. It has an error open: /dev/tty not found. [17:37] oh really ? [17:37] I'll file a bug soon. Flashing another SD to try on beagleXM. [17:37] k [17:38] it worked fine for me with the old kernel btw [17:38] But it is near the end of the log (after other activity). [17:38] because the omapfb setting completely broke the framebuffer [17:38] Also, it failed to create a user, but that may be due to lack of network. [17:38] unlikely [17:39] wither we dont call all modules from the debconf frontend or what i suspect is my hack to rename the machine to localhost by default is bad [17:39] Hey, I find unlikely bugs all the time. I'm good at it, remember? :P [17:39] heh, yeah [17:39] but i really doubt missing network has anything to do with it [17:40] Same here, but I have seen weirder issues. [18:31] rsalveti: ping [18:32] rsalveti: i've begun cleaning xbmc's packaging and install scripts. it would be nice to have a mentor that i could speak with about best practices. know of anyone who might be willing/able to help? [18:32] TheUni: I can try to help on that [18:33] persia would be the best guy around for that [18:33] he knows a lot about packaging [18:33] TheUni: is it still the packaging tree? [18:33] yes [18:34] i have some work done locally to begin consolidating packages, but i'd like to know that i'm making things better and not worse [18:34] TheUni: and how is the daily builds, did you manage to get it to work? [18:34] rsalveti: yes, daily builds are up. but they're not publicized yet because i'd like to rework the packages first [18:34] oh, ok [18:34] incase we end up causing some conflicts while shifting things around [18:35] https://launchpad.net/~team-xbmc/+archive/unstable [18:35] TheUni: at the moment it seems you're building for arm [18:36] at least Architecture: i386 amd64 powerpc ppc64 [18:36] is that because of the daily builds? [18:36] cool [18:36] rsalveti: simply because we haven't tackled packaging it yet [18:38] but afaik current git is building/working on beagle [18:38] TheUni: cool, nice to know [18:38] rsalveti: ok, i'll work up a list of questions and hand them off to you. you can pass me along if you'd like :) [18:39] some XBMC_CONFIG_OPTIONS would be arch specific, as for ARM we'd like to have gles support, and not gl and vdpau [18:39] TheUni: sure [18:40] right [18:40] gles is default for arm [18:40] but it does seems to be better [19:47] Not sure what changed, but unity-2d-places is less than usable in the 20110311 image. Can't even get to a terminal without crashing. [19:47] s/hanf/hang/ [19:48] pmathews: ??? [19:50] GrueMaster: wrong wide post [19:50] GrueMaster: that was for me [19:50] ah [19:58] oops [19:59] kgilmer: you still working for bug? === renato is now known as renatofilho === unitylogger is now known as gnomeshellogger [22:10] hi prpplague, yep sure am. [22:12] kgilmer: just ran across a post on linuxdevices, and just reminded me to ask [22:13] kgilmer: http://www.linuxfordevices.com/c/a/News/Bug-Labs-BugSecure/ [22:14] yep, that's our next bug version. [22:15] kgilmer: don't suppose you guys are looking into omap4? [22:15] the pb chip is pretty cool [22:15] kgilmer: i was curious about the pb chip [22:16] kgilmer: i have heard that pb does a lot of cool designs that they keep pretty quiet about [22:17] sorry prpplague, in support crisis mode for a demo atm, got to get back to you later. [22:18] kgilmer: np, later bud [22:18] kgilmer: i understand all too well === ogra_ is now known as ogra === gnomeshellogger is now known as TheHarald