**** BEGIN LOGGING AT Sat Feb 11 02:59:57 2012
Feb 11 03:09:40 <CanyonMan> #beaglebone is pretty dead most of the time :(
Feb 11 03:14:43 <scromp> i didn't realize there was one
Feb 11 03:14:55 <scromp> that's the only beagle* i have :)
Feb 11 03:23:10 <CanyonMan> oh haha
Feb 11 03:23:20 <CanyonMan> I'm wondering... where is the code that reads cape EEPROMs and sets the pinmux?  
Feb 11 03:23:29 <CanyonMan> Is that in u-boot?  or in the kernel?  or userspace?
Feb 11 08:13:36 <aholler> /
Feb 11 08:25:33 <ka6sox> .
Feb 11 09:31:29 <champ_> hey
Feb 11 09:31:34 <champ_> anyone der?
Feb 11 09:38:57 <champ_> hi
Feb 11 09:59:17 <_av500_> no
Feb 11 11:42:56 <sgpu> Hi all.  I'm trying to build a systemd-image with OE bit it's failing on gtk+-2.24.8-r2, gtk+-2.24.8/gdk. Is there a stable branch/layers to use so this doesnt happen?
Feb 11 17:45:36 <mouser> I can't seem to get my resolution to change using Angstrom. I created the boot.scr based off this link, but it doesn't change anything when I reboot my xM
Feb 11 17:45:38 <mouser> http://guillaume.segu.in/blog/hackens/337/getting-started-with-your-brand-new-beagleboard-xm/
Feb 11 20:11:37 <staif> hey guys 
Feb 11 20:11:43 <staif> I have a question please 
Feb 11 20:11:44 <xlq> Hello.
Feb 11 20:11:53 <staif> Hello 
Feb 11 20:12:15 <staif> anyone has an experience with beagleboard xm running angstrom ?
Feb 11 20:14:03 <staif> anyone here?!
Feb 11 20:14:38 <jay6981> might get a better response if you just asked a specific question
Feb 11 20:16:06 <staif> I just need the uEnv.txt file to boot angstrom 
Feb 11 20:17:02 <staif> i have a problem in booting angstrom on beagleboard xm which needs the uEnv.txt 
Feb 11 20:17:22 <jay6981> i thought it works even without the file
Feb 11 20:17:53 <thurbad> it works without it, if your monitor supports the default res
Feb 11 20:18:32 <staif> no it doesn't,, it keeps trying to boot 
Feb 11 20:18:43 <jay6981> might be a different problem though
Feb 11 20:19:21 <thurbad> probably not a uEnv.txt problem then, do you have a bootlog?
Feb 11 20:19:48 <staif> [   11.768096] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode [   11.779205] VFS: Mounted root (ext3 filesystem) on device 179:2.
Feb 11 20:20:04 <staif> this is the last thing I get
Feb 11 20:20:18 <staif> and then, it tries to boot again 
Feb 11 20:20:26 <jay6981> doesn't sound like a uboot/uenv problem
Feb 11 20:21:10 <staif> it gives me this warning : *** Warning - readenv() failed, using default environment
Feb 11 20:21:20 <thurbad> sounds like a root file system problem perhaps
Feb 11 20:21:50 <jay6981> staif: you can probably safely ignore it
Feb 11 20:21:57 <jay6981> agree with thurbad… rootfs issue
Feb 11 20:22:01 <thurbad> or power perhaps
Feb 11 20:22:25 <staif> the power is sufficient 
Feb 11 20:22:55 <staif> I got the rootfs from the angstrom website and extracted it on the ext3 partition
Feb 11 20:23:02 <staif> that's it
Feb 11 20:23:53 <thurbad> how is your sd card partitioned?
Feb 11 20:23:59 <jay6981> try md5sum to make sure it's valid and recreate fs, re-extract
Feb 11 20:25:34 <staif> there's a FAT partition for booting, which has MLO and u-boot files 
Feb 11 20:25:50 <staif> and the other one has the rootfs 
Feb 11 20:26:29 <thurbad> you used tar to extract?
Feb 11 20:26:35 <staif> yes
Feb 11 20:26:57 <staif> tar -zxvf
Feb 11 20:28:04 <jay6981> also try another sd card
Feb 11 20:28:41 <staif> ok,, now, how the bootargs of the beagleboard xm are set?
Feb 11 20:28:55 <staif> because it doesn't have a NAND flash 
Feb 11 20:29:08 <staif> so I'm not able to change the bootargs and save them 
Feb 11 20:29:35 <thurbad> uEnv.txt is just a simple text file with variable assignments
Feb 11 20:29:43 <staif> what I understood is that there has to be either a boot.src or uEnv.txt file?
Feb 11 20:29:52 <staif> is that correct?
Feb 11 20:30:33 <thurbad> such as dvimode=1280x720MR-24@60
Feb 11 20:31:00 <jay6981> there doesn't have to be a file. uboot has (usually) sane defaults compiled in 
Feb 11 20:31:16 <staif> okk
Feb 11 20:31:20 <jay6981> you can override them with the file
Feb 11 20:31:21 <thurbad> it's one or the other,which one depends on your u-boot version
Feb 11 20:31:39 <staif> ok,, got it 
Feb 11 20:34:41 <thurbad> dang is it really going to take half a year for panda suppliers to get the pandaboard es back in stock?
Feb 11 20:35:04 <thurbad> saw lead times of 26 weeks
Feb 11 20:36:32 <thurbad> is that because of omap4 supply?
Feb 11 21:09:18 <_av500_> dont trust lead times
Feb 11 21:09:47 <woglinde> dont trust time at all
Feb 11 21:14:35 <jay6981> time sucks
Feb 11 21:36:17 <TonyWatertown> hi folks.  im having an ethernet problem with my brand new beaglebone (revA4).  im running the 12.04 hard float image from eelinux.  i get the following errors when trying to establish a link:     5.561841] CPSW phy found : id is : 0x7c0f1
Feb 11 21:36:18 <TonyWatertown> [    5.568658] PHY 0:01 not found
Feb 11 21:37:02 <TonyWatertown> ive read something on the mailing list (and found a video) for removing R219 from the board.  is this the only fix?
Feb 11 21:58:52 <TonyWatertown> well, i just removed R219 and my ethernet is working.
Feb 11 21:59:29 <koen> good morning all!
Feb 11 22:10:16 <Maxz> que tal las playas de uruguay?
Feb 11 22:15:20 <rlrosa> Maxz, excelentes
Feb 11 22:21:39 <Maxz> :)
Feb 12 00:29:10 <kmansfie> Trying to build an SD Card to boot a beagleboard.  I have tried mkcard.txt and it has toasted a couple of SD cards.  What does everyone do here to build an SD Card from scratch?
Feb 12 00:29:20 <kmansfie> Actually it is a beaglebone.
Feb 12 00:30:39 <thurbad> how did mkcard toast sd cards?
Feb 12 00:32:01 <kmansfie> I'm not able to mount the SD card after running mkcard.txt.
Feb 12 00:32:41 <kmansfie> I ran mkcard.txt on a Ubuntu 10.04 machine if that makes any difference.
Feb 12 00:33:24 <thurbad> that shouln't be a problem
Feb 12 00:33:49 <thurbad> have you looked at the card with gparted or any other partition tools?
Feb 12 00:34:11 <kmansfie> no, haven't tried that.
Feb 12 00:34:47 <kmansfie> The problem is it doesn't come up with a device in /dev to look at.
Feb 12 00:34:57 <kmansfie> or associate with a device in /dev
Feb 12 00:35:48 <kmansfie> When I do a "df" it doesn't show up.
Feb 12 00:36:33 <thurbad> df only shows mounted stuff
Feb 12 00:37:09 <thurbad> was it under /dev before
Feb 12 00:37:17 <kmansfie> yes
Feb 12 00:37:36 <thurbad> have you removed it and plugged it back in?
Feb 12 00:38:06 <kmansfie> yes, several times.
Feb 12 00:38:45 <thurbad> was it mounted when you ran mkcard.txt?
Feb 12 00:39:10 <kmansfie> yes, is that a problem?
Feb 12 00:39:16 <thurbad> also have you rebooted your machine?
Feb 12 00:39:23 <kmansfie> yes
Feb 12 00:39:38 <thurbad> yeah generally you don't want to repartition mounted drives
Feb 12 00:39:49 <kmansfie> good to know
Feb 12 00:40:08 <kmansfie> Is there any way to recover the sd card?
Feb 12 00:40:11 <thurbad> but it shouldn't make it not show up in the /dev file system
Feb 12 00:40:16 <kmansfie> (s)
Feb 12 00:40:44 <thurbad> do you have any external sd card readers?
Feb 12 00:41:56 <kmansfie> I have a USB sd card reader combo device.  Is that what you are talking about?
Feb 12 00:42:12 <thurbad> yeah
Feb 12 00:43:10 <kmansfie> let me try yhat
Feb 12 00:43:45 <kmansfie> s/yhat/that/
Feb 12 00:44:27 <thurbad> if that works I'd say turn off your machine briefly and then power it up again, I've seen sd readers stop working until hard rebooted
Feb 12 00:48:09 <kmansfie> No, that didn't work, still can't see it.
**** ENDING LOGGING AT Sun Feb 12 02:59:56 2012