**** BEGIN LOGGING AT Fri Sep 23 02:59:56 2011 Sep 23 03:12:27 cooloney: hi Sep 23 03:26:28 Graah Sep 23 03:27:04 Looks like my TF101 was somehow on last week, and ran itself out of battery completely -- to the point where I couldn't even turn it on with the power plugged in via the dock, I had to plug the power directly into the tablet part Sep 23 03:36:06 chihchun: hi Sep 23 03:37:18 is omap3 porting also included in ti-oamp4 branch of natty kernel tree (2.6.38) ? Sep 23 03:43:48 lilstevie: I'm looking at u-boot/include/configs/tegra2_common.h:CONFIG_NETBOOT_SETTINGS, and I can't see where it loads the ramdisk. Sep 23 03:44:48 From the CrOS kernel config you're using, it looks like you make everything =y, so I guess you don't HAVE a ramdisk, but I'd kinda like one, if only so I can use it for rescue when root won't mount Sep 23 03:44:54 (yay busybox) Sep 23 03:59:26 Oh, I just realized the FAT version is loading a *u-boot script*, not a kernel directly from FAT Sep 23 04:02:39 Ah, OK, so fatload/ext2load copy a file into RAM at a specified address, and then source/bootm actually DO something with it. Sep 23 04:08:32 lilstevie: stupid question, but when you said that u-boot interactivity wasn't working -- did you try just removing the u-boot line that tells it to set console=ttyS0 ? Sep 23 04:09:11 nm, that would be the kernel, not u-boot. I can see further down that stdin=serial,tegra-kbc and so on Sep 23 05:06:37 15:05 I manually run "kbdrate -d 250 -r 30" and it is still set to 0 Sep 23 06:59:36 lilstevie: can you show me an MBR-based nvflash flash.cfg? Sep 23 07:00:58 when I wake up Sep 23 07:01:04 Sure thing Sep 23 07:01:05 I am out of it :/ Sep 23 07:01:11 Are you about to get up, or go to bed? ;-P Sep 23 07:01:43 I have been napping Sep 23 07:02:04 afk for half an hour, beer Sep 23 07:02:26 kk Sep 23 07:24:33 is Unity3D all OpenGLES ready right now for Oneiric? Sep 23 09:00:04 back Sep 23 09:00:24 lilstevie: ^ Sep 23 09:00:40 lilstevie: I was hoping you'd have made me a pastebin :P Sep 23 09:44:04 hello, i´m using beagleboard xm with an rtc battery and now i want to change the time epoch from 1970 to 2010, but with "sudo hwclock --setepoch --epoch=2010" i get the message "The kernel keeps an epoch value for the hardweare clock only on alpha machine. This copy of hwclock was build for a maschine other than alpha. No action taken." someone can help me to change the epoch ? Sep 23 09:45:54 Why do you want to set the epoch? Sep 23 09:46:13 Everything else on unix uses an epoch of 1970 Sep 23 09:47:08 If you just want to set the hw clock, you want hwclock -w Sep 23 09:47:15 s/unix/known universe Sep 23 09:47:26 im using socketcan and the timestamps are calculated from the time epoch in seconds Sep 23 09:48:39 and now i want to change the time epoch, because the timestamps are to huge Sep 23 09:49:04 too huge for what? Sep 23 09:49:15 They should be <32bit Sep 23 09:49:35 signed, 32-bit time_t goes until 2038, right? Sep 23 09:50:00 Somewhere around then Sep 23 09:50:40 I guess socketcan isn't using time_t then Sep 23 09:50:54 (https://secure.wikimedia.org/wikipedia/en/wiki/SocketCAN) Sep 23 09:53:14 it uses timestamp Sep 23 09:53:17 dsjfbdfkb Sep 23 09:53:19 timeval :D Sep 23 09:53:19 yes but the timestamp i get from the sockets have the format struct timeval with time_t tv_sec and suseconds_t tv_usec Sep 23 09:53:43 and time_t is count from epoch ? Sep 23 09:53:54 sure Sep 23 09:54:04 are you sure the time on your board is set right? Sep 23 09:54:26 because when the rtc dies on some of my arm boxes, the time is 1969 and time_t values have wrapped around... Sep 23 09:54:50 -1 time_t is just the same as 2 billion and it causes trouble.. Sep 23 09:54:50 yes the time i set correct, i^m using init.d script to load the time from rtc with "hwclock -s" Sep 23 09:54:57 lilstevie: ping, did you fall asleep again :-( Sep 23 10:16:05 Should I be worried that file says uImage is a "u-boot legacy image", when I'm AFAIK using this new FIT/dtc stuff? Sep 23 10:35:19 twb, yes.. Sep 23 10:35:32 it should print a bitchload of info too Sep 23 10:35:38 what, file? Sep 23 10:35:50 rootfs/boot/vmlinux.uimg: u-boot legacy uImage, Linux-2.6.38.3+, Linux/ARM, OS Kernel Image (Not compressed), 3135112 bytes, Fri Sep 23 19:17:03 2011, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0x246D6351, Data CRC: 0x94ACEAFB Sep 23 10:36:05 no, u-boot.. it should say something like "detected fit image" and then stuff going from there (lots and lots of lines) Sep 23 10:36:14 I haven't put u-boot in place yet Sep 23 10:36:25 And when I do, it won't have a working keyboard or screen, so I won't see that Sep 23 10:36:31 they are legacy images Sep 23 10:36:31 oh okay.. I wouldn't expect "file" to know the difference right now Sep 23 10:36:37 it has screen Sep 23 10:36:57 it prints out the same info that mkimage does if you tell it to read the information Sep 23 10:36:59 lilstevie: so I'm doing the right thing? Sep 23 10:37:06 yes Sep 23 10:37:24 therefore you're not using the fit/dtc stuff :) Sep 23 10:37:30 yep :) Sep 23 10:37:44 u-boot needs fit/dtc stuff to compile Sep 23 10:37:45 Neko: I sure needed to install dtc to get u-boot to build... Sep 23 10:37:49 Oh, OK Sep 23 10:37:49 kernel isn't using it though Sep 23 10:38:08 twb, yeah, u-boot always wants it to build, but it doesn't necessarily NEED it. Sep 23 10:38:21 lilstevie: is it u-boot.img or u-boot, that I write to the EBT partition? Sep 23 10:38:29 u-boot.bin Sep 23 10:38:39 I will pastie my config soon Sep 23 10:38:51 it took me a bit to get the right location for MBR Sep 23 10:39:05 so probably easier for me just to give that to you p Sep 23 10:39:06 :p Sep 23 10:39:20 I hope so Sep 23 10:40:01 btw is the "no support for micro SD" because it's actually not supported, or just because the script doesn't try to use mmc device 2, but only usb, mmc1, mmc0 Sep 23 10:41:04 because there is no support for it Sep 23 10:41:27 OK, just checking :-) Sep 23 10:42:52 If I make an ext4 filesystem, can u-boot's ext2load read files from it, or will it freak out because of extents or something? Sep 23 10:45:12 BTW, should I be worried that u-boot.bin is like one-sixth the size of the original asus/android bootloader? Sep 23 10:45:50 no Sep 23 10:46:00 ogra_: hi. does banshee work for you? Sep 23 10:46:01 because it is a different bootloader Sep 23 10:46:12 the window opens, but it's all white for me Sep 23 10:46:26 And a substantially less bloated one :-P Sep 23 10:46:35 also I have an ext2 fs for my u-boot partition Sep 23 10:46:47 with a boot.scr kernel and initrd Sep 23 10:48:42 lilstevie: hm, can you also give me your CONFIG_EXTRA_ENV_SETTINGS for u-boot? I wasn't sure what to put for e.g. the ramdisk's load address Sep 23 10:49:06 That is pastebin tegra2-common.h or so Sep 23 10:50:10 ndec, havent tried yet, file a bug :) Sep 23 10:50:27 I read it to a location in my boot.scr Sep 23 10:50:28 :p Sep 23 10:58:41 * twb waits impatiently for MBR flash.cfg and uboot scripts Sep 23 11:16:40 * twb pokes lilstevie Sep 23 11:21:35 ogra_: LP#857299 Sep 23 11:21:51 bug 857299 Sep 23 11:21:52 Launchpad bug 857299 in banshee "banshee window remain white on startup on pandaboard" [Undecided,New] https://launchpad.net/bugs/857299 Sep 23 11:22:03 NCommander will love this :) Sep 23 11:22:58 ogra_: i always forget how to trigger ubot2 ;-) Sep 23 11:23:30 :) Sep 23 11:24:44 ogra_: on my panda, the link vmlinuz and initrd.gz in /boot are wrong. is that normal? Sep 23 11:25:26 they exist but point to non existing kernel Sep 23 11:26:35 upgrade ? Sep 23 11:26:43 or fresh install ? Sep 23 11:26:57 upgrade Sep 23 11:29:04 twb: http://pastebin.com/3SVrZ1PZ Sep 23 11:29:08 Yay Sep 23 11:29:20 ogra_: vmlinuz is in / now? Sep 23 11:29:31 env is because I have env_is_mmc Sep 23 11:29:42 and offset to that specific location Sep 23 11:29:47 ndec, not really, no Sep 23 11:29:53 UIM is my u-boot ext2 part Sep 23 11:30:34 Hm, OK. Sep 23 11:30:35 as for where I load my initrd that is ${loadaddr}+kernel_size+500kb to be safe Sep 23 11:31:14 After the pivot_root, does the ramdisk space get GC'd? Sep 23 11:31:32 Because if so you could just always load it at 8MB or 16MB or something, to allow for huge kernels Sep 23 11:33:07 no idea Sep 23 11:33:17 thats why I do it close :p Sep 23 11:33:54 You set MBR type=data -- does that mean I have to write the MBR myself? Sep 23 11:34:02 no Sep 23 11:34:06 Or does nvflash still do it based on the name or something Sep 23 11:34:30 that is just nvflash being odd Sep 23 11:34:38 k Sep 23 11:41:22 You set allocation_attribute=8 instead of 0x808 -- does that mean "fill to end of disk, with no exceptions" ? Sep 23 11:42:09 lilstevie: also, why doesn't MPT have file_system_attribute=0 ? Sep 23 11:43:23 don't ask me, ask nvidia :p Sep 23 11:43:38 this is based off the ventana flash.cfg in the LDK Sep 23 11:43:54 I bet its because the nvidia engineer forgot Sep 23 11:44:21 none of it is documented Sep 23 11:44:48 And they stripped the executable, so no debugging Sep 23 11:45:21 if you are a hw partner you can get the BSP stuff, which includes the source code for nvflash Sep 23 11:45:51 but even then, there is a lot that are PCHs Sep 23 11:46:03 only under NDA though, I expect, which defeats the purpose of getting it Sep 23 11:46:08 so I hear anyway Sep 23 11:46:14 yeah Sep 23 11:46:20 Well, here we go. Sep 23 11:49:51 Am I right in thinking that nvflash -bl needs to be given the original bootloader, not u-boot? Sep 23 11:50:16 for flashing, yes Sep 23 11:50:41 u-boot does not implement the flashing program Sep 23 11:52:11 Hmm, it didn't like me Sep 23 11:52:54 Maybe it doesn't like four-letter partition names Sep 23 11:53:06 no Sep 23 11:53:08 3 only Sep 23 11:53:14 less ok more not Sep 23 11:57:11 If you pass TERM=dumb, it disables that progress shit Sep 23 11:57:19 I think Sep 23 11:57:42 Never mind, it's still doing its mkfs-type step before copying to actual fs across Sep 23 11:58:25 But passing TERM=dumb did make it generate a lot less output during the upload step I think. Sep 23 11:59:53 Hm, no, it must be *just* screen that doesn't like its output. Probably a funny termcap thing. Sep 23 12:09:15 Nearly done... Sep 23 12:11:46 lilstevie: OK, once I reboot, when I hit the power button do I still get the Nvidia Tegra splash screen? Sep 23 12:12:41 no Sep 23 12:12:52 Hm, screen isn't turning on at all Sep 23 12:12:57 that is in the asus bootloader Sep 23 12:13:57 I probably fucked up the u-boot configuration somehow... I built it this way: Sep 23 12:13:58 make ventana_config DEV_SRC_TREE=tegra-tf101; PATH=/usr/src/dtc:$PATH make -j Sep 23 12:14:13 (I figured before fucking with its config I should make sure it was gonna work at all) Sep 23 12:16:42 I can't get it to turn on at all Sep 23 12:17:21 Now, I did get an error *after* repartitioning and uploading all the images, from "./nvflash -r --sync --go" Sep 23 12:17:21 I build with make ARCH=arm ventana CROSS_COMPILE=arm-linux-gnueabi- DEV_TREE_SRC="tegra2-tf101" Sep 23 12:17:33 what error Sep 23 12:17:35 I was compiling from a native chroot Sep 23 12:17:47 ok so drop CROSS_COMPILE Sep 23 12:18:29 I just realized I did tegra-tf101 and you did tegra2-tf101 Sep 23 12:19:07 Error was: [resume mode] \n failed executing command 25 NvError 0x8 \n command failure: sync failed Sep 23 12:19:16 hm Sep 23 12:19:23 And then I saw the nvidia splash screen, which I think means the --go worked Sep 23 12:19:52 Then I just powered it off by holding to power button, since it was (understandably) not finding anything via the asus bootloader Sep 23 12:21:28 I'm not panicing yet, but this is sure acting like a brick Sep 23 12:22:20 The other thing I probably did different from you, was I was running dtc from git Sep 23 12:22:29 v1.3.0-6-g83df28b Sep 23 12:22:31 yeah well you know you can go back into apx :p Sep 23 12:22:47 Well, that's a nice theory except it's not showing up in lsusb Sep 23 12:23:08 press volup then hold power Sep 23 12:23:19 monitor your lsusb it will show up very soon Sep 23 12:23:32 unless your batt is flat Sep 23 12:23:39 I suppose that's possible Sep 23 12:23:50 The dock's battery is green Sep 23 12:24:27 OK, APX is back Sep 23 12:25:10 So now to work out what went wrong Sep 23 12:25:46 I think the problem is that I forgot the 2 in tegra2-tf101, so I built the wrong dtc Sep 23 12:25:53 Er, dts Sep 23 12:26:05 I'm surprised it didn't give an error at compile-time, though... Sep 23 12:27:57 well personally I am going after serial Sep 23 12:28:22 haha, there is a dropbear.id.au Sep 23 12:28:35 (*.id.au names are supposed to be .au fauna) Sep 23 12:29:06 lol Sep 23 12:31:06 The downside is that recompiling u-boot is gonna take a while, because until the tf boots again I'm doing it via qemu Sep 23 12:31:18 (Cross-compiling is too hard.) Sep 23 12:31:59 just use the linaro compiler Sep 23 12:32:05 cross compiling is easy Sep 23 12:32:24 Then I have to compile that, since its binaries aren't signed by Debian Sep 23 12:33:52 That or trust linaro, I mean. Plus I have no idea what additional stuff is in linaro that isn't in Debian, and part of the goal here is to be as close to stock Debian as possible -- including bootstrapping everything Sep 23 12:40:37 lilstevie: how do I tell nvflash not to rewrite all the other partitions, since I'm only going to be uploading a new u-boot? Sep 23 12:40:47 lilstevie: do I just omit the --create option? Sep 23 12:42:12 ./nvflash --bct BCT.img --setbct --configfile flash.cfg --bl bl.img --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --download 4 u-boot.bin Sep 23 12:43:34 you cant Sep 23 12:43:38 not for bootloader Sep 23 12:44:00 Well that's lame Sep 23 12:44:19 it is nvflash being a pain Sep 23 12:44:28 In that case I guess you run a normal --create command, but on a flash.cfg that has all the file= lines removed? Sep 23 12:44:51 And all the type=ext[23] changed to type=data, to prevent it overwriting the existing filesystem with an empty one Sep 23 12:45:33 nope Sep 23 12:45:48 I'm not gonna like the right answer, am i? Sep 23 12:45:52 because it does format_all Sep 23 12:45:59 well more to the point Sep 23 12:46:05 it deletes all partitions Sep 23 12:46:12 then creates and formats Sep 23 12:46:22 always? Sep 23 12:47:43 yes Sep 23 12:48:28 You'd think with NAND flash they'd want to avoid a big bag of pointless writes Sep 23 12:51:13 So just to be absolutely clear: there's *no* way to upload a new u-boot, without also having to upload the entire root filesystem again? Sep 23 13:05:38 hello all Sep 23 13:12:48 hello Sep 23 13:22:48 * twb uploads a new, hopefully correct, u-boot Sep 23 13:28:03 OK, I uploaded a new u-boot, but skipped uploading the OS.img root filesystem, on the basis that I should at least be able to see u-boot on the screen even if u-boot can't find a kernel Sep 23 13:28:17 But it's still not turning the screen on... Sep 23 13:30:39 :) Sep 23 13:32:30 I can't see what I did wrong Sep 23 13:32:55 you know you can upload it as -bl to test Sep 23 13:33:00 rather than writing every time Sep 23 13:33:20 No I didn't :-/ Sep 23 13:33:29 did you add ARCH=arm in the make command Sep 23 13:33:41 No, because I wasn't cross-compiling Sep 23 13:33:51 http://paste.debian.net/131770/ Sep 23 13:34:05 That's the end of the compile run Sep 23 13:34:41 file u-boot.bin Sep 23 13:34:47 http://paste.debian.net/131771/ managed to get the whole thing Sep 23 13:35:03 lilstevie: /usr/src/u-boot/u-boot.bin: ERROR: vasprintf failed (Invalid or incomplete multibyte or wide character) Sep 23 13:35:31 file u-boot Sep 23 13:35:41 ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, not stripped Sep 23 13:36:07 hm Sep 23 13:36:38 gcc vers? Sep 23 13:37:02 gcc (Debian 4.6.1-11) 4.6.1 Sep 23 13:37:55 hm Sep 23 13:37:57 If I ask Debian about it they will probably tell me to do the whole thing again from the ground up, on armel Sep 23 13:38:12 some of the newer toolchains are broken for tegra Sep 23 13:38:24 some hardware errata bs AFAIK Sep 23 13:38:57 * twb carefully refrains from chucking tf101 through a window Sep 23 13:39:26 lilstevie: do you know which chains, or how I can test if a chain is broken? Sep 23 13:40:08 After all if debian's gcc is broken, then the userland is gonna be screwed even if I build the bootloader and kernel with something else Sep 23 13:40:25 nah kernel works around this stuff Sep 23 13:41:29 So I should try building u-boot using an older gcc? Sep 23 13:41:46 4.4 and 4.5 should be apt-gettable Sep 23 13:43:15 well I use 4.4 Sep 23 13:43:36 okey dokey Sep 23 13:45:30 twb: this is a long shot, but have you tried exporting LC_ALL=C in the environment and rebuilding? Sep 23 13:45:54 Hm, LANG probably doesn't make it through chroot(8), lemme look Sep 23 13:46:13 "multibyte character" sounds like locale-related encoding problems Sep 23 13:46:32 dmart: oh, you mean for file(1) Sep 23 13:47:02 dmart: nice one: /mnt/bar/rootfs/usr/src/u-boot/u-boot.bin: Spectrum .TAP data "\024\237\024\237\024" Sep 23 13:47:35 fuck this board Sep 23 13:47:38 er Sep 23 13:47:42 wrong chan Sep 23 13:47:45 haha Sep 23 13:47:46 and excuse my language Sep 23 13:47:51 We were all thinking it Sep 23 13:47:57 Of course, if the build itself is bad it doesn't solve that problem Sep 23 13:48:07 the uart is burried in the JTAG port :/ Sep 23 13:48:27 well the only one I can trace Sep 23 13:48:40 but don't know much more Sep 23 13:50:48 OK, off we go using gcc-4.4 Sep 23 14:04:47 Donkey balls Sep 23 14:05:01 /usr/src/u-boot/lib/sha1.c: In function ‘sha1_process’: Sep 23 14:05:02 /usr/src/u-boot/lib/sha1.c:228:1: internal compiler error: in maybe_add_or_update_dep_1, at sched-deps.c:845 Sep 23 14:05:45 So qemu won't let me compile u-boot using gcc-4.4 Sep 23 14:07:58 At this point I am thinking instead of using userspace emulation on my netbook, I should just use qemu host emulation on one of the chunky buildds in the office Sep 23 14:22:26 Same problem in gcc-4.5 Sep 23 14:22:42 So until I either get qemu up or reflash this with ubuntu, I'm at an imp-arse. Sep 23 14:23:06 a.k.a. bed time for twb Sep 23 14:40:25 try and fix this golang test failing Sep 23 14:40:48 ok, I've forgotten to install the OMAP4 stuff from TI and I wonder if I should do that to Sep 23 14:40:51 try and fix this golang test failing Sep 23 14:40:52 phew Sep 23 16:15:49 I'm running angstrom, a beagle board version. Should i in theory be able to use an ubuntu beagle board version ? Sep 23 16:17:40 sniperjo: angstrom is more generic, but you may have some luck with the oneiric omap images as thy are more mainstream. Just remember that not all of angstrom's kernel bits are upstream, whereas ubuntu pulls the kernel directly from upstream. Sep 23 16:18:29 GrueMaster: ok thanks, I'm desperate here Sep 23 16:25:35 GrueMaster: ubuntu also patches the upstream kernel. we are always trying to reduce the patches in both Angstrom and Ubuntu by moving more stuff upstream. Sep 23 16:43:45 jkridner: do you know about the pm/smartreflex support at upstream? want to have my xm working at 1ghz :-) Sep 23 16:43:59 have a bug for ubuntu, bug 771537 Sep 23 16:43:59 Launchpad bug 771537 in linux "Beagle XM lacks proper 1Ghz support" [Medium,In progress] https://launchpad.net/bugs/771537 Sep 23 16:44:24 don't know yet if we're already able to have it working with upstream properly, didn't have time to look around for the patches still Sep 23 16:47:29 jkridner: What I meant was that unless a system is in our hands, we only support what the upstream kernel supports. If support for the system that sniperjo is using isn't in the main kernel tree, we really have no way to support it directly. Sep 23 16:48:23 GrueMaster: Texnexion is also on the beagle board website Sep 23 16:48:39 not sure what that has to do with anything… but i just though i would put it out there Sep 23 16:49:46 That doesn't mean I have one here to test with. My hardware budget is semi-limited and I already blew it on multiple pandas (and support hardware) for server testing. Now, if you want to supply me with one... Sep 23 16:50:08 GrueMaster: If you have it up and running for me, consider it done Sep 23 16:50:35 it has been done http://www.youtube.com/watch?v=vWYHk15QOTo Sep 23 16:50:39 Not that I would be able to get to it this cycle. I really am overloaded at the moment. Sep 23 16:51:10 I have a Nook Color that was my pet project to get running. So far, I have barely had time to root it (since May). Sep 23 16:52:37 GrueMaster: I am getting to the stage, where paying for someone to get it working, could be a viable option Sep 23 16:53:51 That video has a link to our RootFromScratch page, which indicates to me they built their own chroot environment (similar to ubuntu-core), which is what I suggested to you twice now. Sep 23 16:55:14 And I know getting Ubuntu running on non-supported hardware can be done. I did it using Natty Alpha on a Tegra 2 development platform using their boot loader & kernel. Sep 23 16:55:19 GrueMaster: i have managed to chroot into a card, but i diddnt have internet connectivity Sep 23 16:55:45 rsalveti mike turquette is supposed to be sending an updated ABB patch. PM patches are rebased on Kevin's branch on Tony's tree, but more work is required before going upstream. We pull in the last patch set into OE. Sep 23 16:55:51 That may be a kernel issue. Make sure the ethernet module for your system is loaded. Sep 23 16:56:22 rsalveti: I believe rcn-ee has an ubuntu-style kernel. I'm sure you must watch it. Sep 23 16:57:06 rsalveti: rcn-ee is pretty good at tracking whatever koen hacks on (and koen follows khilman and tmlind). Sep 23 16:57:09 jcrigby: cool, would like to check that patch set Sep 23 16:57:10 yeah Sep 23 16:57:18 even to enable it properly at linaro Sep 23 16:57:59 * rsalveti updating his oe tree Sep 23 16:58:23 rsalveti I saw khilman sending arnd patches yesterday for PM. I don't think it included the ABB support for 1GHz xM, but you can probably set the 1GHz OPP without it and not have too many headaches. Sep 23 16:58:26 jcrigby: which kernel version are you using as base? Sep 23 16:58:40 jcrigby: yeah, cool Sep 23 16:58:49 GrueMaster: how would i find out what my ethernet module was ? Sep 23 16:59:25 sniperjo: There are a lot of things to check as to why you don't have networking. First, look at dmesg to see if the kernel detects the network device. Second, read the documentation to determine what type of device it is. If it is usb, lsusb should see it. Sep 23 17:00:04 If it is seen, the driver loaded, and dmesg indicates link detected, then maybe you just need to run dhclient eth0. Sep 23 17:01:53 rsalveti: I'd be happy to point you to my 3.0.4 kernel (from koen) that supports 1GHz. Sep 23 17:02:06 i do have libertas: wlan0: Marvell WLAN 802.11 adapter Sep 23 17:02:28 jkridner: cool, want to have a look at that Sep 23 17:03:01 having 1ghz support for our 11.09 would be awesome Sep 23 17:16:31 rsalveti http://gitorious.org/beagleboard-validation/linux/commit/c8f49b6a6cbcb3b2627388cee438096381b41913 Sep 23 17:31:41 jkridner: great Sep 23 17:31:54 jcrigby: which branch is that, still cloning the tree Sep 23 17:34:22 rsalveti, is you tab completion expanding to jcrigby when you mean jkridner ? Sep 23 17:35:03 hahah :-) Sep 23 17:35:10 that was for jkridner :-) Sep 23 17:35:13 jcrigby: sorry ;-) Sep 23 17:35:31 np, my brain is in a fog so I just wanted to make sure Sep 23 17:35:32 * rsalveti needs food, out for lunch Sep 23 17:39:39 rsalveti I think it is ulcd-android-20110917b Sep 23 17:39:57 there actually aren't any android patches on it... Sep 23 17:40:29 but, I was looking at pulling in the Linaro android patches and this tree was at the base point where I was going to apply the patches Sep 23 17:40:38 I got held up on TLS incompatibilities. Sep 23 17:41:24 I was able to cherry-pick a bunch of the Linaro Android patches, but the Android file system I have has an emulated TLS. Sep 23 17:41:28 :( Sep 23 18:03:55 ogra_: tested yesterdays image, installation goes through without a hitch, even with selecting keyboard-layout etc. Sep 23 18:05:00 on the ac100 that is Sep 23 18:05:32 GrueMaster: ping Sep 23 18:05:46 prpplague: pong Sep 23 18:06:54 ogra_: also did it by the wiki with another computer with clean ubuntu install, with installing nvflash from .deb etc. Sep 23 18:07:11 so the installation-guide is also tested to be accurate Sep 23 18:12:03 GrueMaster: hey, we need to look into the ppa stuff for the 10.10 release Sep 23 18:12:23 GrueMaster: i along with about 5 others have been trying with no success on installing them Sep 23 18:12:51 Yep, I'm working on that now. Have to flash a new SD with the image. Should be ready in 20-30 minutes. Sep 23 18:15:16 It may be that universe and multiverse need to be enabled iirc. But I want to verify that first. Sep 23 18:31:59 GrueMaster: yea tried enabling those Sep 23 18:38:31 prpplague: I am booting up now. Will let you know what I find soon. Sep 23 18:38:46 GrueMaster: ok thanks Sep 23 18:46:24 w00t, I had to comment out that one test for go in order to get go installed Sep 23 19:24:35 prpplague: I just finished booting into maverick (I got distracted a little). When I initially tried to install the extras, it failed due to gstreamer & faac packages. Adding universe and multiverse to /etc/apt/sources.list fixes that. Sep 23 19:24:46 Will document on wiki. Sep 23 19:25:10 GrueMaster: which instructions were you using ? Sep 23 19:25:47 GrueMaster: are you adding the univer and multiverse from the gui? Sep 23 19:27:04 I didn't. I just logged into the maverick image and tried the link for the ti extras. When it failed, I opened a terminal and tried "sudp apt-get install ubuntu-omap4-extras-multimedia". Then figured it out from there. Sep 23 19:27:20 No, but I will document it in the release notes. Sep 23 19:27:41 This was a known issue for maverick (missing universe & multiverse). Sep 23 19:27:44 GrueMaster: ok, document what you got and i will try to replicate Sep 23 19:28:07 GrueMaster: the instructions we have on omapedia are for using the GUI Sep 23 19:28:26 HAH! Anyone want to see how fast the pandaboard serves up requests? Sep 23 19:28:38 mind you my BW is limited to 768 outbound Sep 23 19:29:10 http://eutonian.ath.cx Sep 23 23:31:27 hello, I have a beagleboard XM with ubuntu desktop on it. I want to understand how to trigger events from the user button. I thought all I had to do was build a new kernel after modifying the /arch/arm/omap/mach-omap2/board-omap3beagle.c, compile the kernel and copy the vmlinuz into ubuntu's /boot directory and adjusting the symbolic link to run it, but I looked for the events, and inputs within the sysfs director **** ENDING LOGGING AT Sat Sep 24 02:59:57 2011