[00:26] rsavoye: hm, are you using currently maverick's kernel? [00:26] yes, it should be [00:27] it's about 2 months out of date [00:27] I was curious if the xM worked yet with maverick :-) [00:29] rsavoye: yeah, it should work, at least it was tested with the pre-installed image [00:29] that's why it could happen that you got a bug while upgrading it [00:30] so maybe I should grab another image and reflash the mmc card ? [00:31] or will it segfault all the time like it used too ? [00:31] rsavoye: depends, if it's easier for you :-) [00:31] rsavoye: what is your xM rev? [00:31] Beagle xM Rev A [00:31] https://wiki.ubuntu.com/ARM/OMAPMaverickInstall [00:31] Die ID #6ac80000061000000156166b0a01002a [00:32] don't know if the software is getting when you're using rev A2 or A3 already [00:32] it had memory problems before, but at the time you though it might be kernel related [00:32] hm, at least my rev A now works fine [00:33] before even throttling it down to 800Mhz didn't hel[, but that was weeks ago [00:33] course my A board could have the dreaded RAM bug [00:42] yeah, but give the latest image a try and see if it works better === lilstevie|ZNC is now known as lilstevie [04:51] hello [04:51] JakeJBailey: hey, did you try the ubuntu sgx packages for omap3? [04:52] im still installing [04:53] cool [05:01] hoe long is this uspposed to take [05:01] how* [05:12] no serial so idk how im supposed to know its doing anything [05:13] been sitting just blinking as it does when idle [05:25] hasnt done anything in a while [05:36] yea its just sitting, followed these instructions https://wiki.ubuntu.com/ARM/OMAPMaverickInstall [06:05] JakeJBailey: it usually takes around 4, 5 for the first boot [06:05] JakeJBailey: then at your second boot it should display the oem-config after 3, 4 minutes [06:05] then you just finish the installation and you're ok [06:05] uhh [06:06] mines been sitting here 45mins [06:06] ouch, nothing on the screen? [06:06] nope [06:06] JakeJBailey: what board are you using? [06:06] C4 [06:07] oh, that's weird, it should work without any change [06:07] JakeJBailey: could be something got wrong during your progress [06:07] you should be able to see something on your monitor from the first boot [06:07] progress? [06:07] nothing [06:07] it should show you it's resizing the sd card [06:07] i got the uncompressing linux and boot in the serial and that was it [06:08] ok, try writing the image again and then edit the boot.scr file to get the serial working [06:08] any tips on that? the link goes to no page in the tutorial [06:08] JakeJBailey: https://wiki.ubuntu.com/ARM/BeagleEditBootscr [06:09] JakeJBailey: after writing the image with dd, mount the sd card [06:09] at the first partition give: dd if=boot.scr of=boot.script bs=1 skip=72 [06:09] then edit the boot.script file [06:09] https://wiki.ubuntu.com/ARM/BeagleEditBootscr [06:09] will that work? [06:09] oh sry, haha [06:09] add console=ttyS2,115200n8 to the bootargs line [06:10] write the new boot.src file with: mkimage -A arm -T script -C none -n "Ubuntu boot script" -d boot.script boot.scr [06:10] umount the card and boot it on your board [06:10] you should be able to see what's happening at least [06:13] sudo sh -c 'zcat ./ubuntu-netbook-10.10-preinstalled-netbook-armel+.img.gz >/dev/' [06:13] is that equivalent to dd? [06:17] JakeJBailey: yup, just that by giving zcat you don't need to first gunzip it [06:17] in case you want to use dd you first need to gunzip it, then run dd with the img file [06:19] epic fail [06:19] was the monitor [06:19] plugged into a different one and now it works [06:21] JakeJBailey: haha :-) [06:21] cool, ping us later in case you need any help with ubuntu [06:22] I'm out now, quite late already === hrw is now known as hrw-uds === JaMa is now known as JaMa|Off === ogra_ac_ is now known as ogra_ac === lilstevie is now known as lilstevie|ZNC === sumitsemwal is now known as sumits [17:27] hello [17:28] following this wiki page https://wiki.ubuntu.com/ARM/OMAP/Graphics i get that none of the packages are found [17:30] "unable to locate package" [17:30] JakeJBailey: you need to activate the universe and multiverse repo first [17:30] did that [17:31] JakeJBailey: omap3 or omap4? [17:31] omap3 [17:31] beagleboard c4 [17:31] JakeJBailey: ok... so that is for rsalveti then, not me ;-) [17:32] JakeJBailey: after apt-get update you should be able to see it [17:32] try giving apt-cache search sgx [17:32] wait there are two checkboxes now for the repos [17:32] I checked them off in the list style box but there is also a menu where they must be checked\ [17:35] okay while I am waiting can you guys tell me if there is a nice way to handle choosing a wifi connection from within fluxbox or some other light window manager? [17:37] JakeJBailey: you an always try to start nm-applet [17:37] stalonetray [17:37] if you have a window manager with systray, you're ok [17:37] that gives you a floating tray area [17:37] okay thanks for the suggestions [17:41] okay i think i was enabling it in the other software tab instead of the ubuntu software tab [17:43] its working now, thinks for your help guys. Can anyone edit the ubuntu wiki that i linked? if so i will add some clarification to it [18:01] when i get packages from the repo for armel im guessing those are compiled to have support for the most chips so would it be very beneficial to compile for my specific armv7a? [19:44] Do you have sound on your bb with maverick netbook install? I don't, shouldn't I? [19:44] C4 hw === ogra_ac_ is now known as ogra_ac [21:50] is there anyway I can get the ubuntu toolchain used to build for the beagleboard as described here: http://elinux.org/BeagleBoardUbuntu [21:53] cipher: what exactly are you looking for? [21:53] cipher: emdebian.org has cross toolchains. For ubuntu, those were integrated via some ppa, not sure if already on maverick, try to search for gcc-4.4-arm-linux-gnueabi [21:54] zumbi_: cipher: maverick has armel gcc cross compiler. it's even possible to install them in lucid [21:55] ndec: I'd like to be able to build a binary for a beagleboard that is I believe running the maverick build [21:55] for maverick: apt-get install gcc-arm-linux-gnueabi should work [21:56] and to install it on lucid: https://wiki.linaro.org/WorkingGroups/ToolChain/CrossCompilerOnLucid [21:57] ndec: do you know if some work has been done for bare metal toolchains? [21:57] so my host machine isn't an ubuntu box but a debian lenny [21:57] ndec: does that make things a little more challenging? [21:58] cipher: then use emdebian.org (wiki.debian.org/EmdebianToolchain) [21:58] cipher: you could still build in a chroot.. that's what I do even if I run maverick. [21:58] otherwise I don't think there is a bare metal toolchain available. maybe hrw or lool would know. [21:59] ndec: can you elaborate? I know what a chroot is, but would I then have to setup an entire maverick install inside the chroot? [21:59] cipher: yes: just create a maverick buildd chroot, and install the arm cross compiler inside. [22:00] https://wiki.linaro.org/UsingXdeb like this? [22:00] exactly I was going to point you to this ;-) [22:00] excellent, thank you. [22:00] it does not mean that you have to use xdeb, though. [22:00] zumbi_: I will look at what you've mentioned as well.. not ignoring you :-) [22:01] cipher: zumbi_: i don't think embeddian would have support for amrv7, though. [22:02] with the linaro/ubuntu cross compiler you have access to the very same gcc that was used to build the entire ubuntu archive. [22:02] ndec: if you use mabi mcpu options, does not make any difference [22:02] ndec: I'm almost thinking of just trying to build the rootfs of the beagleboard from scratch seeing as I need a very basic functionality... essentially I just want a linux kern with hidraw and some USB support. the rootfs actually doesn't need much at all I just want to be able to cross compile for the target platform. I was handed a beagleboard with an ubuntu install on it and so i thought this might be the fastest way to get going. [22:03] ndec: debian and ubuntu tools are the same [22:03] ndec: not exactly, but those share the same base [22:03] sure [22:04] cipher: so you want to rebuild the rootfs? why exactly? why can't you just use the existing rootfs or build a minimal (console only) rootfs with rootstock for example [22:04] ndec: like I said I'm open to suggestions. I'm just kind of new to this and have kind of a hobby project [22:05] so if you have any pointers to that I am happy to look. I'll check on rootstock [22:05] cipher: np... so you might want to check this: https://wiki.ubuntu.com/ARM/RootfsFromScratch [22:05] everything atm is kind of fragmented in my mind. kind of aware some of the pieces but not sure how to put them all together [22:05] you can create a minimal rootfs with console only + apt-get installed in a few minutes. [22:06] with rootstock you create the ubuntu rootfs that you want, you choose all the packages you need. [22:07] so then I just need to build a kernel myself or does that handle that part as well [22:07] I assume not, so then I jump back to the other link you mentioned about cross compiling and just roll from the vanilla linux with omap support [22:08] or using an ubuntu kernel, i.e. maverick [22:08] i don't recall this exactly. i think you can give it a prebuilt .deb and it would install it, not sure though. otherwise, you can just build your kernel. [22:09] we wrote this a while ago: http://omappedia.org/wiki/Get_started_with_ubuntu_on_omap4. might be a bit outdated, but that could help you understanding the process of building your rootfs [22:10] if you plan on using ubuntu rootfs, i recommend you start using the ubuntu kernel. that's the one we test ubuntu on... so it's safer. === JaMa|Off is now known as JaMa [22:12] cipher: i need to go... out of battery and no plug around... we can catch up later if you need. [22:12] ndec: all right, thanks. === JaMa is now known as JaMa|Zzz