[13:31] wow, many people [13:31] hi all :) halp! [13:32] I'm trying to follow the instructions on https://wiki.ubuntu.com/ARM/OMAPMaverickInstall but only get a black screen [13:32] BeagleBoard-xM Rev C, Panasonic HDMI TV, 16GB microSD; stock microSD gives some kind of picture [13:33] both the regular kernel and the other kernel have the same symptoms; when using a serial console I at least can see that the disk gets resized [13:39] sorry, xM B [13:53] TheCount: that's all you see on the serial console ? [13:57] dcordes: nah, I see a bit more when I turn on the serial console .. [13:57] dcordes: but without turning on the serial console it's "uncompressing linux, done, etc" and then nothing. [13:58] dcordes: eventually the network link comes up, but all ports are closed [13:58] I'm just trying http://elinux.org/BeagleBoardUbuntu#Maverick_10.10_2 [13:59] the stock microSD gives a slightly misaligned and garbled FB display on my TV, is that normal? [13:59] i.e. some overscan issue and the picture is repeated [13:59] horizontally [14:01] what about official image? doesn't support beale ? [14:03] it should. according to the docs this should be perfectly fine. [14:13] well then why not using it = [14:14] because it DOES not work? :) [14:14] guess why I'm here? ;) [14:15] like I said: I'm getting a black screen, and a black screen only [14:15] * TheCount is trying the netinstall now *sigh* [14:16] maybe netinstall via serial gets me to a state where I can at least login to the box and debug on itself [14:17] that image in the wiki you are pointing to is not an official ubuntu image [14:17] git clone git://github.com/RobertCNelson/netinstall-omap.git [14:17] sorry [14:17] git clone git://github.com/RobertCNelson/netinstall-omap.git [14:17] copy-waste [14:17] https://wiki.ubuntu.com/ARM/OMAPMaverickInstall isn't? [14:17] it's the very first thing I tried, and it doesn't work. [14:18] seems pretty official to me. [14:19] * TheCount is slightly frustrated :( [14:42] TheCount: did you replace the kernel like said in the wiki page? [14:42] this black screen issue is usually the problem described at the wiki page [14:48] rsalveti: yes, I did. no difference :( [14:49] interestingly, the packaging says xM B, but the bootloader says xM A. hm. [14:50] TheCount: the only change from rev B is the processor revision [14:50] so it's basically like the A [14:50] A3 actually [14:52] hmm. okay, there's no number with the A. but it was sold as a Rev B [14:52] I'm just running a maverick netinst via serial [14:53] maybe I can get something showing afterwards [14:53] what worries me a bit is the slightly wrong FB display with the testing image [14:53] rsalveti, hi, I got another crash yesterday still zero logs and no way to reproduce, probably a cumulative thing [14:53] guerby: :-( [14:54] guerby: if you want you can try natty's kernel [14:54] rsalveti, is there a way through apt-get? [14:55] guerby: yep, but you need to change to the natty's repo, and it'll probably pull more than wanted [14:55] guerby: http://ports.ubuntu.com/ubuntu-ports/pool/main/l/linux-ti-omap4/linux-image-2.6.35-1101-omap4_2.6.35-1101.3_armel.deb [14:56] rsalveti, I'm fine in dist-upgrade if this is known to work [14:56] dpkg -i and flash-kernel should install all that's needed [14:56] rsalveti, ah ok, trying that [14:56] it's a good test but not a known to work [14:56] and updating it now will probably break other stuff [14:56] rsalveti, I'm trying dpkg -i/flash kernel stuff [14:57] guerby: http://ppa.launchpad.net/rsalveti/armel/ubuntu/pool/main/x/x-loader/x-loader-omap4-panda_1.4.4+git20101223+6f3a261-1ubuntu1ppa2_armel.deb [14:57] you also need this new x-loader [14:57] rsalveti, dpkg -i too ? [14:57] just replace the MLO file from this deb into your first partition [14:58] guerby: if you install it you'll find it at /usr/lib/x-loader/omap4430panda/MLO, or something like that [14:58] guerby: you can just extract it [14:58] from your host, and then copy to the first partition [14:58] dpkg -X . [15:05] rsalveti, ok copied MLO, dpkg -i, flash-kernel now reboot ... [15:05] guerby: cool, good luck :-) [15:07] $ cat /proc/version [15:07] Linux version 2.6.35-1101-omap4 (buildd@crabapple) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.1-12ubuntu1) ) #3-Ubuntu SMP PREEMPT Tue Dec 14 16:05:04 UTC 2010 [15:07] rsalveti, now running my build loop again :) [15:07] guerby: cool :-) [15:08] rsalveti, it's always better when few commands are needed to try new kernels :) [15:08] rsalveti, whta's that MLO thing? [15:08] guerby: is the x-loader, a very small boot loader needed by the omap platforms [15:09] that initialize some very basic stuff and then loads the u-boot [15:09] rsalveti, strange it needs upgrade when kernel changes? [15:09] guerby: it's just because there are still some stuff that are initialized just by the x-loader [15:09] and then the kernel expect it to be initialized [15:10] rsalveti, ah ok [15:10] rsalveti, thanks for the info :) [15:10] what changed with this kernel is that more stuff went from the x-loader to the kernel [15:10] what's the correct path [15:11] rsalveti, BTW I noticed in /var/log/kern.log I get plenty of: Dec 19 22:55:01 gcc44 kernel: [57571.922210] smsc95xx 1-1.1:1.0: usb0: kevent 2 may have been dropped [15:11] guerby: that's something I also get with the previous kernel [15:11] you probably also got it sometimes [15:12] rsalveti, many identical messages per millisecond [15:12] yeah, this is something it seems to be fixed with the 37 but I still didn't have time to find the fix to backport it [15:12] rsalveti, ok :) [15:13] rsalveti, build running, let's see what happens. for reference cmdline=text ro elevator=noop vram=32M mem=768M root=UUID=b5d2dfb1-270c-4966-abe6-dfe7a2a17efd fixrtc smsc95xx.macaddr=32:57:F8:93:E1:CD [15:16] hopefully it'll be better [15:17] * rsalveti bbl, lunch [17:09] Any armel-cross guys around here now? [17:14] I updated my Maverick amd64 host and got a new version of binutils-arm-linux-gnueabi (from 2.20.51.20100908-0ubuntu2cross1.50 to 2.20.51.20100908-0ubuntu2cross1.52) [17:16] Now it seems I'm unable to cross build my applications "/usr/lib/gcc/arm-linux-gnueabi/4.5.1/../../../../arm-linux-gnueabi/bin/ld: this linker was not configured to use sysroots" [17:16] This could seriously limit our ability to build apps, since we rely on sysroot for building [17:17] I'll throw in a bugreport if noone else is familiar with this [17:42] Already reported : https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/582645 [17:42] Launchpad bug 582645 in gcc-4.4 (Ubuntu) "Linker was not configured to use sysroots (affects: 5) (heat: 36)" [Undecided,Fix released] [17:42] Yes, I'm commenting on it. Thanks [17:43] It really is a blow for us, so we need to take some steps back [17:45] I think it's a regression failure [17:47] Yes, but the fix is not elegant, as an excellent feature of the toolchain is removed to fix it [18:29] oups ... [18:29] asoc: interface omap-mcbsp-dai-0 hw params failed [18:29] what the heck does that mean? [18:33] and why do I still not have output on my HDMI port *sigh* (Beagleboard-xM Rev B after Maverick Netinstall - the preconfigured image didn't work either :() [18:35] hm. at least I can SSH to the box now, yay! :D [19:06] *sigh* [19:09] Martyn: http://www.linuxfordevices.com/c/a/News/ZT-Systems-R1801e-/ <- is that yours? [19:20] hah. okay. now I've got omapfb.mode=dvi:1280x720MR-16@60 in my /proc/cmdline, but still no picture. what could be the problem? [19:21] TheCount: Does dmesg tell you anything useful in regards of omapfb? [19:24] wait a sec, just copied the kernel cmdline from the stock microSD [19:25] hm. quite different [19:25] root@beagleboard:~# cat /proc/cmdline [19:25] console=tty0 console=ttyS2,115200n8 mem=80M@0x80000000 mem=384M@0x88000000 mpurate=1000 buddy=none camera=lbcm3m1 vram=16M omapfb.vram=0:8M,1:4M,2:4M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi root=/dev/ram0 rw ramdisk_size=131072 initrd=0x88000000,128M rootfstype=ext2 [19:26] root@beagle:~# dmesg|grep omapfb [19:26] [ 0.000000] Kernel command line: console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p5 ro vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none mpurate=800 [19:26] sveinse: I'd call that a 'nope' .. [19:29] *fiddle* [19:32] oh. yay. [19:32] with the different kernel parameters I see a different broken display ;) [19:33] armin76 : No comment [20:06] A slide to unlock feature for the gnome lock screen program would be nice for touchscreen only devices [20:14] okay, now I got a broken 1024x768 mode displaying on HDMI. yay! [20:15] the other modes are all not listed in modedb.c - I wonder how they were supposed to work?!? [20:18] ah. on the fly calculation. [20:19] what is the recommended kernel for a beagleboarx-xM rev B? [20:19] currently using 2.6.35-1008-linaro-omap .. [20:19] and, how would I nail down that damn MAC address properly? [22:24] rsalveti, no luck, freeze again after two hours [22:24] Cpu(s): 60.5%us, 27.0%sy, 0.0%ni, 4.7%id, 0.9%wa, 0.0%hi, 7.0%si, 0.0%st [22:24] Mem: 734472k total, 572936k used, 161536k free, 912k buffers [22:24] Swap: 524284k total, 4568k used, 519716k free, 481424k cached [22:24] rebooting [22:25] rsalveti, interestingly one of the board LED is on, the D1 [22:25] the other D2 is off