[01:02] <heathkid> my Raspberry Pi arrived today.  :)  Anyone running ubuntu on one yet?
[01:05] <twb> heathkid: /topic says don't do that
[01:05] <infinity> s/don't/can't/
[01:05] <heathkid> sorry
[01:06] <heathkid> back to my beagle-bone then...
[08:49] <ppisati> ogra_: what was your problem with panda's led?
[10:01] <ppisati> ogra_: what was your problem with panda's led?
[10:02] <ogra_> ppisati, they arent in the initrd we build for resizing, so if the screen is broken you dont really see that the board is doing something apart from the NIC LEDs
[10:03] <ppisati> ogra_: why they aren't in installer initrd?
[10:03] <ogra_> (rootfs only gets mounted after the next reboot)
[10:04] <ogra_> good question, i bet because the initramfs-tools scripts dont have any clue about led_gpio
[10:05] <ogra_> but beyond that i dont understand why we dont build all driver for HW the board has into the kernel anyway
[10:05] <ogra_> *drivers
[10:05] <ppisati> ogra_: actually that was compiled in in P
[10:06] <ogra_> its a single purpose kernel, all pandas should have the same HW so we could save the boot time to load modules
[10:06] <ogra_> i see led_gpio with lsmod ...
[10:06] <ppisati> yep
[10:06] <ogra_> oh, in P
[10:07] <ppisati> updateconfigs turned it =m i guess
[10:07] <ogra_> well, its not overly important, its just showing explicitly due to the monitor issue
[10:07] <ppisati> yeah
[10:07] <ogra_> otherwise i wouldnt even have noticed
[10:07] <ppisati> anyway
[10:07] <ppisati> let's compile it in
[10:07] <ppisati> actually
[10:07] <ogra_> yeah
[10:08] <ppisati> i would like to know how our initramfs are populated
[10:08] <ppisati> what if, for example, i want to add module xyz?
[10:08] <twb> ppisati: initramfs-tools has pretty extensive docs
[10:08] <twb> You add a build-time hook that says something like 'require_mod xyz'.  I forget the exact details
[10:09] <ogra_> take a look at /usr/share/initramfs-tools/hook-functions
[10:09] <ogra_> that has the functions that loop over modules
[10:09] <ogra_> and decide if they need to be pulled in or not
[10:10] <ogra_> (with a lot of hardcoding in "auto_add_modules")
[10:11] <ogra_> i assume we should add an auto_add_modules gpio function for gpio drivers
[10:12] <ogra_> (initramfs-tools defaults to MODULES=most which in turn uses the auto_add_modules function)
[10:14] <twb> IIRC you can even just list extra modules you want in /etc/initramfs-tools/modules or so
[10:15] <ogra_> twb, we are talking about the default behavior ...
[10:15] <ogra_> the configs are just overrides
[10:15] <ogra_> we usually never use them in official images
[10:36] <_william_> hi all
[10:37] <_william_> I would like to know if there exist a flashplayer (free or nonfree) for ARM architecture ?
[10:41] <ogra_> yes, but only for companies that sign contracts with adobe (i.e. most android phones come with flash)
[10:42] <_william_> ok thanks
[10:42] <ogra_> there are free alternatives ... some of them work so so ... some are totally unusable ... (look for gnash or lightspark)
[10:43] <_william_> i'm first going to ask my hardware manufacturer if they have a player they can ship with the terminal
[11:34] <angs> I am trying to create an adhoc wlan and typed the following commands but I can not see my embedded board on "iwlist wlan0 scan" in my laptop. Does anyone have any suggestion?
[11:34] <angs> ifconfig wlan0 down
[11:34] <angs> iwconfig wlan0 mode ad-hoc essid beagleboard-xm channel 1 key abcdef1234
[11:34] <angs> ifconfig -a wlan0 10.42.43.1 netmask 255.255.255.0
[11:34] <angs> ifconfig wlan0 up
[11:39] <angs> ping 255.255.255.255?
[11:39] <angs> anyone?
[12:01] <marvin24> [22:40:54] <janimo> marvin24, here is hangs after Freeing init memory: 336K
[12:01] <marvin24> yes, there is a known problem with the console
[12:01] <marvin24> but I don't know how to solve it
[12:02] <ogra_> make plymouthd unexecutable
[12:02] <marvin24> I mean solve it in the kernel
[12:02] <marvin24> not back userspace hack
[12:02] <janimo> marvin24, so how come only mine does not boot if it is aknown problem?
[12:02]  * ogra_ hasnt opened a bug for that yet but plans to look into it before final release
[12:02] <janimo> ogra_, so you have 3.1 booting, did you need some hack around it?
[12:03] <ogra_> janimo, i forgot about telling you :) mine wouldnt boot either if i hadnt changed that months ago
[12:03] <marvin24> dito
[12:03] <janimo> sigh, I could have used this info in the ml thread :)
[12:03] <ogra_> sorry
[12:03] <janimo> I thought 3.1 was ready to upload from all points of view
[12:03] <janimo> np, dealing with these things sucks and prone to forgetting stuff :)
[12:04] <janimo> so there is no point trying to upload now since it would not boot on stock ubuntu
[12:04] <ogra_> well, by all means upload it, i can work around in the ac100 installer for the time being
[12:04] <janimo> ah, so upload but not make it default yet ?Fine
[12:05] <ogra_> i'm also not sure its necessarily a kernel issue, might actually be plymouth
[12:05] <janimo> ogra_, btw do you know about arm chroots via qemu-static on x86? Any way to tell it to use many CPUs for use in cross building?
[12:05] <ogra_> i dont think anyone has debugged it deeply yet
[12:05] <janimo> I do such a build now but it seems the default is single CPU, and slooow kernel build
[12:05] <ogra_> hmm, i never tried multiple build threads
[12:06] <marvin24> ogra_: event the android device people (for android 4.0) see this problem
[12:06] <marvin24> but android doesn't care
[12:06] <ogra_> ah
[12:07] <janimo> marvin24, so making plymouthd executable is the workaround?
[12:08] <ogra_> unexecutable ...
[12:08] <janimo> ah
[12:08] <marvin24> I somehow did it different I think
[12:08] <marvin24> dpkg -r plymouth also worked ...
[12:08] <ogra_> i moved mine to .orig and linked the actual plymouthd to /dev/null
[12:08] <ogra_> err
[12:08] <ogra_> /bin/true, sorry
[12:10] <janimo> is there some command line arg to deactivate plymouth?
[12:11] <janimo> kernel cmdline that is
[12:11] <ogra_> nope
[12:11] <ogra_> you could try dropping splash but i think that still fires off plymouthd from mountall
[12:11] <ogra_> once the rootfs is mounted
[12:11] <ogra_> since plymouth acts as UI to mountall
[12:16] <janimo> yes, I boot without splash to see the error messages
[12:42] <angs> does anyone else have problem with ssh to the embedded board, most of the time ubuntu-arm refuses the ssh connection
[12:46] <lilstevie> janimo: ogra_ yeah I had to move plymouthd to .orig and link to /bin/true also for the transformer prime on 3.1
[12:46] <lilstevie> nvidia broke something
[12:47] <janimo> lilstevie, thanks, good to have another confirmation
[12:47] <janimo> is this true for later kernels too?
[12:47] <lilstevie> janimo: 3.1 is the latest we have running on the tf201\
[12:48] <lilstevie> tf201*
[12:48] <janimo> what about tf101 ?
[12:48] <janimo> so it is not a tegra2 only thing even
[12:49] <lilstevie> no it is a tegra thing in general
[12:50] <lilstevie> and we (androidroot) haven't applied the technique to update kernel yet to the tf101
[12:50] <lilstevie> the only 3.1 ports are by people who have sketchy reps at best
[13:13] <ogra_> ndec, one more for your collection http://v.youku.com/v_show/id_XNDA4ODAzODMy.html :)
[14:45] <ogra_> ndec, is there any way we can tell 4460 and 4470 pandas apart by looking at the board ?
[14:45] <ogra_> (we just got a new chunk and i'm not sure which they are )
[15:47] <GrueMaster> ndec: Did you ever get my Blaze?  I wanted to confirm it was received.
[16:31] <angs> I have 5 embedded board that runs ubuntu, none of them gets IP when I plug the ethernet cable. Ethernet led is always red although the cable is plugged. I checked the cable and connection, it works. if I use another linux distribution (e.g. angstroms dist.), eth0 interface gets IP. what should I do?
[16:32] <GrueMaster> angs: First, what board (there are a few out there). second is this an Ubuntu kernel?
[16:34] <angs> I use beaglebone and loaded images according to the instruction here: http://elinux.org/BeagleBoardUbuntu#Precise_12.04_armhf
[16:34] <angs> I can not connect to the board now, it should be 3.2.0 kernel
[16:36] <angs> I was connected one of them after hundred attempts, ubuntu was working fine
[16:38] <GrueMaster> Well, I know the beaglebone doesn't use an Ubuntu kernel, so you won't get much support here (sorry).  Try asking on #beagle.
[16:39] <GrueMaster> The only other suggestion would be to see what ethtool reports when the cable is plugged in.
[16:40] <angs> #beagle people use angstroms dist which sucks and very problematic.
[16:40] <ogra_> well, rcn-ee is often here, i guess its his kernel you use
[16:40] <angs> how can I access ethtool?
[16:40] <ogra_> he should be able to help you with issues
[16:40] <angs> yes what is his nick?
[16:40] <angs> thanks ogra_ it is good to know
[16:41] <ogra_> his nick is rcn-ee
[16:41] <ogra_> he is usually also in #beagle though
[16:41] <angs> thank you
[17:39] <muriani> anyone else have issues with wxgtk-based programs working one time, and then all segfaulting when run any time after that?
[17:40] <Neko> muriani, YO DUDE!
[17:40] <Neko> <-- Matt from Genesi
[17:40]  * ogra_ doesnt think anyone tests wxgtk :/
[17:40] <muriani> in 11.10 specifically, haven't tried 11.04, and 12.04's armhf doesn't play well what I'm doing
[17:40] <muriani> Neko: DUDE!
[17:40] <muriani> :D
[17:40] <Neko> you know if you asked nicely I could have sent you an Efika :)
[17:40] <muriani> hahahaha
[17:41] <muriani> I have one!
[17:41] <Neko> the PPC one, I'm sure?
[17:41] <Neko> I meant the ARM one
[17:41] <muriani> oh wait, you mean an MX :P
[18:06] <muriani> anyhoo, anyone had experience with trying to run gnuradio stuff in ubuntu recently?
[18:06] <muriani> other than me.
[20:18] <angs> I have followed the all methods on http://elinux.org/BeagleBoardUbuntu to install ubuntu to my board(beagleboard). I get "unable to open a folder for boot" error each time as it is seen here http://i47.tinypic.com/33wr0k1.png Is it a something that I should be worry or is it an unimportant error?
[21:59] <scientes> whaaaaa
[22:00] <scientes> why is it using xdg-utils
[22:05] <lilstevie> janrinze: sure, just submit a pull request, I will evaluate, and if it gets rejected I will also give you a comment on why