[04:14] hi i am a novice and am trying to boot linux over pb11mpcore through an sdcard. How do i configure the sdcard so that i can set the environment variables in the arm board [06:46] Can ubuntu 11.10 install on I.MX51 board? [06:56] leekic: It can almost certainly run on one, but no, we have no installer for them right now. [06:56] leekic: (Since every new installer image on ARM needs a different boot loader and kernel, we don't produce one for every board...) [12:13] Hi === ericm|ubuntu is now known as ericm-Zzz [15:54] hello [15:55] does anyone know if 11.10 will run on an arm plug server [15:55] such as TonidoPlug === zyga is now known as zyga-afk [17:49] hmm that guy disappeared before anyone answered... [17:58] Not that it matters. I don't think that system is armv7 compatible. Seems based on Shivaplug processor. Can't find better details. === prpplague is now known as prpplague_afk === prpplague_afk is now known as prpplague [20:14] anyone got some handy dandy instructions for using ubuntu 11.10 with dual displays on the pandaboard? [20:42] prpplague, plug in two monitors, see what happens? [20:43] prpplague, I guess it "should just work", at least if the two monitors have a similar pixel clock [20:43] robclark: yea, only thing i had to do was enable the secondary display [20:43] (but in reality, I dunno.. I only have one monitor) [20:44] robclark: nhg was wanting to know if there was some specific docs for it [20:44] it should come up mirrored by default [20:44] open monitors control panel, unclick "mirror" (or whatever it says) to get virtual desktop.. [20:44] ie. it should just work like on PC [20:45] (or PC without nvidea binary driver, at least) [20:53] robclark: interesting, i had to enable it via sysfs first, then it showed up in the monitors panel [20:53] hmm, one of the displays not getting enabled properly? [20:53] hdmi? [20:54] robclark: dvi [20:54] robclark: hdmi comes up ok [20:54] hmm.. dvi relies on external (to dvi) i2c to detect connection.. [20:55] so it should not care about the dss state, whether it shows up in monitor control panel or not [20:56] prpplague, anyways, the code (if you care) is in omap_connector.c, in omap_connector_detect() [20:57] robclark: interesting, thanks for the info [20:57] np [21:27] GrueMaster, any news on the NM hangs on boot and oem-config doesn't uninstall itself bugs? [21:28] nm hangs? Not sure I know of that one. As to oem-config, that is documented in the release notes with a workaround. [21:29] Essentially, you need to open a console (ctrl-alt-F1), login, and type "sudo oem-config-remove && sudo reboot". [21:30] ubuntu [21:30] erp. wrong window. [21:31] you told me about this nm hang :( something about NM stalling on boot which may have caused a long, long wait before oem-config ran in the first place [21:31] I think that was fixed prior to release. [21:31] okay.. as for the oem-config thing I was hoping that there was a real fix and not just a "workaround in the release notes", even a particular knowledge of what caused the breakage in the first place even if nobody touched it yet [21:33] We are still debugging it. I can hit it with the right SD card 99% of the time, others are only hitting it ~%60. And there are no relevent messages in any logs. I need to tweak the scripts that launch oem-config to generate their own output logs. [21:34] Even then, this will not be fixed in Oneiric. Can't fix images w/o respin, which never happens after release. [21:34] okay, the release note says "in some corner cases" but the bug doesn't relate what those cases might be [21:35] The "corner cases" are that I can easily reproduce it, but others can't. Since I have at least 1 of every board rev released, I have a wider variety to test with. And I also have a large collection of SD cards. [21:36] Some combinations reduce the repeatability greatly. Others cause it to manifest everytime. I can reproduce it 99% of the time with one SD card on every platform rev. [21:36] so it's related to... extremely slow disks? [21:38] Not sure. The one I have that reproduces more frequently is a Micro Center Class 6 16Gb SD. My class 10 16G work most of the time, and my class 2 4GB rarely. [21:38] It appears to be highly timing related. [21:40] I'll look at debugging it more soon. I was in Orlando since 10/26 so haven't been able to look at it yet. And I'm busy with other priority work atm. [21:41] Best case scenario is that I can root cause the issue or come up with a workaround that can be scripted and applied between resize and oem-conifg steps. It would be semi-manual though, so a bit of a cludge any way you look at it. === NekoXP is now known as Neko