[07:22] <steev> Chipaca: last i knew, because arm devices tend to be lower... power, and take longer, they don't tend to extend them to users
[08:06] <lilstevie> steev: I think it is more to do with the security side of things, they don't have the same virtualization thing going on that the x86 and x86_64 machines do
[08:06] <lilstevie> or a combination
[08:07] <steev> lilstevie: could be a combination, i just know i was told there wasn't enough hardware to support giving users access to it (wouldn't get stuff built in time)
[08:07] <steev> maybe with all these quadcore machines coming down the pipe (and armv8 (drool)) that will change
[08:07] <lilstevie> yeah
[08:08] <lilstevie> It is just annoying that we can't build a package and upload it to a PPA either
[08:29] <ppisati> ndec: with latest tilt-tracking (44fef05d56961d0f34178e3c7ca4e362948e3107), during boot i get a lot of
[08:29] <ppisati> ndec: wl1271_sdio mmc1:0001:2: sdio read failed (-110)
[08:29] <ndec> ppisati: is it 3.4 or 3.5?
[08:29] <ppisati> ndec: wl12xx: ERROR command complete timeout
[08:29] <ppisati> ndec: 3.4
[08:29] <ppisati> ndec: tilt is still on 3.4 if i'm not mistaken
[08:30] <ndec> well, i am asking because latest tilt-tracking is on 3.5
[08:30] <ndec> and it's probably not in a good shape atm.
[08:30] <ppisati> ndec: really? couldn't find the 3.5 part
[08:30] <ppisati> ndec: anyway, still 3.4 here
[08:30] <ppisati> ndec: let me paste the entire boot logs
[08:31] <ndec> ppisati: well, we don't use tracking atm, but tilt-3.4.
[08:31] <ndec> ok. you're right, it is still 3.4.
[08:34] <ppisati> ndec: http://people.canonical.com/~ppisati/3.4.0-202-wifi/
[08:34] <ppisati> ndec: dmesg and config
[08:34] <ppisati> ndec: it's just an annoyance by now since it resets later in the boot process
[08:34] <ppisati> ndec: and it seems to work (get the ip via dhcp and so on)
[08:34] <ndec> ppisati: well, not sure if i can help atm. can you ping andy, or send an email to linaro-dev?
[08:35] <ppisati> ndec: i'll do, just wanted to check out if it was a known issue
[08:35]  * ndec checks quickly
[08:35] <ndec> ppisati: if you want a 3.4, you should use tilt-3.4 branch instead. it is supposed to be better branch.
[08:36] <ndec> -tracking will get some support for 3.5 later.
[08:36] <ppisati> ndec: i see
[08:36] <ppisati> ndec: i'll check tilt-3.4 then
[10:23] <ogra_> ppisati, your kernel looks good, i get a lot of wireless errors in dmesg though (they were there before but less noisy)
[10:24] <ogra_> (ah, the same errors you described above)
[10:27] <ppisati> ogra_: yeah
[10:28] <ppisati> ogra_: working on that and "INFO: task kinteractiveup:55 blocked for more than 120 seconds." crap
[10:30] <ogra_> i cant really notice any issues that causes
[10:30] <ogra_> i have it too though
[10:32] <ppisati> ogra_: it's harmless but still an annoyance
[10:32] <ogra_> yup, the wlan is more intresting
[10:32] <ppisati> ogra_: hopefully i'll have both them fixed for this afternoon and then i'll pull request
[10:32] <ppisati> ogra_: thanks for testing
[10:32] <ogra_> so thats the latest TILT ?
[10:32] <ppisati> yep
[10:32] <ppisati> bleeding edge
[10:33] <ogra_> do we know if the audio device names will stay like that ?
[10:33] <ogra_> they changed again vs precise so i need to update alsa
[10:33] <ogra_> and wouldnt like to do that twice
[10:33]  * ogra_ wonders why one cant just stay with one name)
[10:34] <ppisati> ogra_: you better ask TI about the name changes
[10:34] <ppisati> ogra_: but if needed i can revert the modification
[10:34] <ogra_> PandaBoardES now ... was PandaBoard and the version before it was just Panda
[10:35] <ogra_> well, it would be cool if upstream could just decide on a proper and persistant name :P
[10:36] <ppisati> persistance is the past, we are heading for the future! :)
[10:36] <ogra_> haha
[10:36]  * ppisati reminds of a Gamma Ray song/album
[10:36] <ppisati> and with that said, i'm out for laundry + lunch
[10:36] <ppisati> back later
[10:36] <ogra_> have fun
[10:39]  * ogra_ just notices that HDMI sound works OOTB
[10:39] <ogra_> nice !
[12:06] <janimo> lilstevie, do you know if the tf101 supports USB console over it's dock cable?
[12:11] <lilstevie> janimo: look at the acm usb gadget
[12:11] <lilstevie> requires a bit of fiddling to get working
[12:11] <janimo> lilstevie, thanks. should it work with kernel boot messages too?
[12:12] <lilstevie> once the gadget driver has initialized
[12:13] <lilstevie> before that no
[12:13] <lilstevie> I have no idea what or even if there is a UART pinout on the connector
[12:13] <lilstevie> in probing I cannot find one
[12:14] <janimo> lilstevie, do you know the easiest way to get kernel boot messages when the screen/fbdev are not working?
[12:14] <janimo> as is the case with 2.6.39
[12:16] <lilstevie> ramconsole
[14:59]  * ogra_ would so love to know why the ac100 kernel explodes in his face with the recent images
[15:03] <hrw> ogra_: kernel itself before initramfs?
[15:09] <ppisati> ndec: what's BCMDHD?
[15:22] <ogra_> hrw, pretty hard to say, no serial ... i end up with an oops and it looks like the kernel couldt use the initrd ...
[15:22] <ogra_> *couldnt
[15:24] <hrw> ogra_: use PRINTK_DELAY option in kernel?
[15:24] <ogra_> that would mean i need to recompile ...
[15:24] <ogra_> nah, thanks
[15:38] <ppisati> ogra_: i've a new kernel that fixes wifi sdio and interactive governor log spam
[15:38] <ppisati> ogra_: willing to give it a test?
[15:38] <ogra_> sure !
[15:40] <ppisati> ogra_: http://people.canonical.com/~ppisati/linux-image-3.4.0-203-omap4_3.4.0-203.8_armhf.deb
[15:40] <ppisati> ogra_: enjoy
[15:54] <ogra_> ppisati, so i see the wlan device in dmesg, but network-manager doesnt, something is still missing it seems
[15:54] <ogra_> beyond that, the oopses are gone
[15:57] <ogra_> hmm, disabling wlan in NM and re-renabling it fixes it ... odd ...
[15:57]  * ogra_ tries a reboot, lets see, probably just a hiccup
[15:58] <GrueMaster> Disabling/reenabling probably reset NM's config.  I've seen that before in Natty iirc.
[15:58] <ogra_> well, lets see i boot with unplugged wired now ...
[15:59]  * ogra_ would love to know what the system does so long in the initrd
[15:59] <ogra_> seems to take minutes until it moves on
[16:01] <ogra_> k, works
[16:01]  * ogra_ puts that one in the hiccup category
[16:04] <ppisati> good
[16:13] <angs> I am searching the package for ralink rt2870 chipset on http://packages.ubuntu.com/ for beagleboard-xm (ubuntu-desktop 12.04) but it does not show any output for "rt2870" or "rt2800" keywords. am I checking it on the wrong webpage?
[16:14] <GrueMaster> angs: Just check /boot/config-<kernel version>.
[16:14] <GrueMaster> That will tell you if it is built or not.
[16:15] <ogra_> thats shipped in teh kernel as rt2x00.ko
[16:18] <ogra_> and its firmware comes as /lib/firmware/rt2870.bin in the linux-firmware package
[16:18] <ogra_> both should be installed by default
[16:21] <angs> I can see the rt2870.bin in the directory that you said. but the led of the usb dongle does not work, also iwconfig, ifconfig -a does not show the wireless interface. however, I can see the usb stick on lsusb
[16:21] <angs> does the stick suppose to work as I plug it to the board?
[16:22] <ogra_> do you apply enough power to the board ? USBV wlan adapters draw a lot
[16:23] <angs> I use 5V, 2.5A power supply
[16:23] <angs> I plugged the usb stick on my laptop, it does not work
[16:25] <GrueMaster> If it doesn't work on your laptop either, that could indicate a bad dongle.
[16:27] <angs> most probably
[16:27] <ogra_> either that or it needs a special initialization ...
[16:28] <ogra_> i had such dongles in the past, they had a mini HDD on them that carries the windows driver and you needed to tweak the device in sysfs to make it switch from HDD mode into wlan
[16:29] <ogra_> anyway ...
[16:30]  * ogra_ is off to mow the lawn
[16:33] <angs> thank you, I saw some threads on google that this d-link product has some problem, I will try to find a solution
[19:48] <janrinze2> lilstevie: which 3.x kernel do you recommend for the tf101?
[19:50]  * janrinze2 runs ubuntu and pidgin on a tf101