[00:08] anyone around who can help an arm n00b? :) === __bjf is now known as bjf [00:10] a friend gave me a babbageboard to play w/ (unknown state), not sure on exact model, but looks identical to this: http://ossguy.com/?p=317 [00:11] using these instructions: https://wiki.ubuntu.com/ARM/BabbageKarmicInstall [00:11] problem is, I plug it in, it's getting power, but nothing is displayed through VGA/DVI [00:13] monitor never detects a signal, nic port on switch never lights up ... I'm assuming its off, and needs to be powered on, but theres nothing i'm seeing labeled as a power button, unless i've had one too many beers. The push button (in the bottom of the pic) yields nothing (labeled sw9) === bjf is now known as bjf[afk] [00:37] vanhoof: you could try newer versions [00:37] like lucid or maverick (still on development) [00:38] rsalveti: just tried the lucid build [00:38] I'd recommend you lucid first [00:38] same result [00:38] vanhoof: do you get at least an yellow screen during boot? [00:38] this is the boot loader writing some output so you can see that it works with your monitor [00:38] rsalveti: i get nothing at all, as if its not powered on [00:39] black screen, power saving mode, no activity on the nic on the switch [00:39] oh, it's a babbage, not beagle :-) [00:40] DVI port output does not work / is unstable: Display output on Babbage 2.x boards is underpowered and relatively unstable. The board might not be able to display any image with some DVI screens. This issue is particularly visible on Babbage 2.0 boards. Freescale recommends various hardware modifications to workaround the issue. This hardware issue is not tracked in Launchpad. [00:40] from the https://wiki.ubuntu.com/ARM/KarmicReleaseNotes [00:41] * vanhoof will give vga a go again [00:42] it'd try to follow basically what is described at the wiki page first [00:43] https://wiki.ubuntu.com/ARM/BabbageImageFromScratch [00:43] can also help debugging [00:43] but I know nothing about this board :-( [00:44] thanks for the help [00:44] same result w/ vga [00:44] it really looks like its getting power properly [00:44] but needs to be 'turned on' [00:44] theres just nothing obvious labeled as a power button, and the one button that is, does nothing [00:44] and of course i cannot find this model on freescale's site :D [01:00] vanhoof: there are people here that have and test this board, like NCommander, GrueMaster and dyfet, but they are probably not on-line now [01:00] rsalveti: cool [01:01] * vanhoof just figured it'd be something fun to play around w/ this weekend [01:01] im sure im likely doing something dumb :D [01:01] :-) [01:01] vanhoof: maybe updating the bootloader and kernel could help [01:03] rsalveti: you'd still expect to see some activity once powered in, right? eg nic lights on switch, screen should come out of power saving mode? [01:04] or is the entire bootstrap process controlled within the image i put on the sd card? [01:07] vanhoof: dpm [01:07] argh [01:08] don't know if this board has nand or any other memory to boot from at the first stage [01:08] if it loads the bootloader from the sd card, then you'll probably need a sd card with the correct image on it [01:08] then it'd be important if you could track the uart output [01:09] to see what's happening [01:11] yah, got nothing to see whats going on :D === fta_ is now known as fta === jkridner_ is now known as jkridner === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta__ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta [19:19] hi all [19:19] I am not using ubuntu arm but I guess it would be fine to ask a question about arm-linux in general, right? [19:24] depends? ask? [19:26] ok [19:26] I am trying gprof on arm [19:26] and I am getting all nan's as time [19:27] even though the call tree seems fine [19:27] and time granularity is reported to be 'nan' too [19:40] moo [19:41] asac, 2.5h isnt bad i'd say :D [19:51] artz: never tried that [20:10] ogra_cmpc: yep. very good ;) === asac_ is now known as asac [20:19] rcn-ee: say, do you have a BB kernel that supports the ceph cluster fs? [20:23] kblin, probally.. is it not enabled? [20:23] haven't checked yet, actually [20:23] so far I was planning on using a hawkboard for my demo [20:24] just about everything is enabled.. it might be an external module thou [20:24] but I'm still waiting for the hardware [20:24] I'll check that [20:24] nope.. CONFIG_CEPH_FS is not set (2.6-stable) [20:25] not in 2.6.35-devel either.. [20:25] ok, I guess it's about time I figure out how to build my own kernels then :) [20:26] I still hope "embedded private cloud storage" is less stupid than it sounds [20:27] but imagine you had a bunch of nas drives you could connect to your network, and automatically your virtual central storage server would have more disk space [20:28] while all you need is a bunch of hdd enclosures spread around the house wherever there's a free power socket.. [20:28] something like http://pastebin.com/rwg9zvJ5 on top of my 2.6.35-devel script should do the job.. [20:30] oh, btw, you don't really want to build smbfs anymore [20:31] cifs is better in every aspect, smbfs has been deprecated years ago [20:32] rcn-ee: thanks for the pointers [20:32] SIGBED [20:32] i can drop that.. ;) it may have occured when i sync'd with ubuntu's config.. [20:33] i just use ext/btrfs/nfs so anything else doesn't get tested. ;) [20:33] * NCommander waves to ogra and rcn-ee [20:33] * rcn-ee NCommander your beer's empty.. ;) [20:33] rcn-ee: I haven't had any beer yet [20:33] Language barrier :-/ [20:34] what's up NCommander [20:34] rcn-ee: just saying hi, since I'm not usually awake at this hour [20:35] gotcha, what time is it there, i keep forgeting your time zone.. [20:35] rcn-ee: +8 [20:35] or +12 [20:35] * NCommander checks [20:36] no, I was right the first time