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