**** BEGIN LOGGING AT Mon Dec 12 02:59:56 2011
Dec 12 09:25:27 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r4436208675 10testlab/beaglebone/eglibc/systemd-image/build-id: beaglebone: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 11:04:28 <CIA-54> angstrom: 03Koen Kooi <koen@dominion.thruhere.net> 07master * rf6a7e8655e 10meta-angstrom/recipes-angstrom/angstrom/ (e-wm-config-angstrom.bb exquisite-theme-angstrom.bb): 
Dec 12 11:04:28 <CIA-54> angstrom: e-wm-config-angstrom: fix LICENSE to match upstream
Dec 12 11:04:28 <CIA-54> angstrom: exquisite-theme-angstrom: ditto
Dec 12 11:04:28 <CIA-54> angstrom: Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Dec 12 11:06:36 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * rf1f735db96 10testlab/beaglebone/eglibc/Cloud9-IDE/build-id: beaglebone: Cloud9-IDE configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 11:27:06 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * rf564e5c8e1 10testlab/beagleboard/eglibc/systemd-image/build-id: beagleboard: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 11:47:29 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * rfc1cf2bcbb 10testlab/beagleboard/eglibc/systemd-GNOME-image/build-id: beagleboard: systemd-GNOME-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 11:47:31 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r411baf6040 10testlab/beagleboard/eglibc/efl-nodm-image/ (4 files): beagleboard: efl-nodm-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 12:07:49 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r6294236f01 10testlab/beagleboard/eglibc/XFCE-NetworkManager-image/build-id: beagleboard: XFCE-NetworkManager-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 13:08:26 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r431949fa12 10testlab/beaglebone/eglibc/systemd-image/build-id: beaglebone: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 13:51:53 <thijsnl> goodafternoon
Dec 12 13:58:05 <thijsnl> iam having difficulties with the dpms setting on angstrom
Dec 12 13:59:08 <thijsnl> i can temporarily force it to on by doing 'xset dpms force on -display ":0.0"'  but i want to have it forced permanently! how can i set this?
Dec 12 13:59:41 <thijsnl> i dont want my screen to go into standby mode
Dec 12 14:48:16 <thijsnl> please.. anyone?
Dec 12 14:49:35 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r9290697dc5 10testlab/beaglebone/eglibc/Cloud9-IDE/build-id: beaglebone: Cloud9-IDE configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 15:30:15 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r804d16af9a 10testlab/beagleboard/eglibc/systemd-image/build-id: beagleboard: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 15:50:41 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r6c5fd17e6d 10testlab/beagleboard/eglibc/XFCE-NetworkManager-image/build-id: beagleboard: XFCE-NetworkManager-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 15:50:41 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r9198b93d68 10testlab/beagleboard/eglibc/systemd-GNOME-image/build-id: beagleboard: systemd-GNOME-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 15:50:41 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * ra43df09e8b 10testlab/beagleboard/eglibc/efl-nodm-image/ (4 files): beagleboard: efl-nodm-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d2d11471cff5f3088264d8edff4c4700e819624a
Dec 12 17:51:58 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r3822de4d63 10testlab/beaglebone/eglibc/systemd-image/build-id: beaglebone: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d74271bd336ba5d65068a1f1403f1b1fa46fa1a0
Dec 12 18:52:39 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r616af8a23f 10testlab/beaglebone/eglibc/systemd-image/ (5 files): beaglebone: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision d74271bd336ba5d65068a1f1403f1b1fa46fa1a0
Dec 12 20:54:01 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * rcacdd380e0 10testlab/beaglebone/eglibc/Cloud9-IDE/ (5 files): beaglebone: Cloud9-IDE configured for angstrom v2011.12-core using branch angstrom-staging and revision d74271bd336ba5d65068a1f1403f1b1fa46fa1a0
Dec 12 21:00:40 <Guest96097> can anyone point me at a document that describes setting up angstrom on the sheevaplug? right now I'm just trying to boot from either USB thumb drive or mmc
Dec 12 21:00:57 <Guest96097> I used narcissus to build a rootfs, etc..
Dec 12 21:01:35 <Guest96097> so I have the uImage file and I'm at the u-boot prompt. I do usb start and fatload usb 0:1 0x6400000 uImage
Dec 12 21:01:40 <Guest96097> but now I don't know what to do
Dec 12 21:02:09 <Guest96097> I don't think the angstrom image canme with a ramdisk image
Dec 12 21:06:57 <Guest96097> if I wanted to boot from the thumb drive would I be using /dev/sda1 as the root=?
Dec 12 21:34:19 <XorA> yes
Dec 12 21:34:39 <XorA> actually probably /dev/sda2
Dec 12 21:34:50 <XorA> as Im assuming sda1 is FAT formatted
Dec 12 21:37:46 <Guest96097> yeah it is
Dec 12 21:38:16 <Guest96097> so I haven't flashed a new u-boot to the device yet. I'm using the one that came on it
Dec 12 21:39:28 <Guest96097> I set my bootargs as follows:
Dec 12 21:39:29 <Guest96097> bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/sda2 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
Dec 12 21:39:47 <Guest96097> basically took what was in bootargs already (printenv) and adjusted the root= bit
Dec 12 21:39:53 <XorA> you want a rootwait in there
Dec 12 21:40:12 <Guest96097> anything else?
Dec 12 21:40:21 <XorA> looks good to me
Dec 12 21:40:29 <Guest96097> I figured the mtdparts was just declaring some info, even if I wasn't using it
Dec 12 21:40:31 <XorA> rootwait as USB devices are slow to initialise but thats all
Dec 12 21:40:45 <Guest96097> so I thought I could leave it there, is that true?
Dec 12 21:40:50 <XorA> yes
Dec 12 21:41:07 <Guest96097> now there's nothing in there about a ramdisk
Dec 12 21:41:22 <XorA> no need for a initrd
Dec 12 21:41:26 <Guest96097> from here do I just do 'boot' or 'bootm' or?
Dec 12 21:41:36 <XorA> boot
Dec 12 21:41:58 <Guest96097> it still seems to be booting the kernel from NAND
Dec 12 21:42:34 <Guest96097> right after I did boot it started reading NAND and then I saw the kernel version as being the original one and not what came with my angstrom /boot
Dec 12 21:43:04 <XorA> did you replace the original NAND loading with this "I do usb start and fatload usb 0:1 0x6400000 uImage" from what you said earlier?
Dec 12 21:43:17 <Guest96097> I did
Dec 12 21:43:28 <Guest96097> before doing the setenv bootargs to above, I did the fatload usb bit
Dec 12 21:43:39 <Guest96097> (I'm doing all this interactively till I fully understand it)
Dec 12 21:43:48 <XorA> but when you run boot it runs bootcmd
Dec 12 21:43:56 <Guest96097> ooooh
Dec 12 21:44:05 <Guest96097> so I should be adjusting bootcmd as well?
Dec 12 21:44:08 <XorA> bootm 0x6400000 will do what you want if your manually typing it
Dec 12 21:44:26 <Guest96097> ahhh ok. I think I understand
Dec 12 21:45:05 <XorA> now you can nip round my house and reboot my sheeva for me
Dec 12 21:45:13 <XorA> its annoying me that a powercut took it out
Dec 12 21:45:58 <Guest96097> let me just confirm this works. exicted ;-)
Dec 12 21:46:37 <Guest96097> woot <3
Dec 12 21:46:39 <Guest96097> it's booting
Dec 12 21:47:27 <Guest96097> after it said done, booting kernel I get no feedback. I noticed there was a console variable in there too. does that need adjusting?
Dec 12 21:47:51 <Guest96097> I can't tell if it's frozen or if I'm not getting anything from the console
Dec 12 21:48:37 <XorA> did you get kernel boot messages then no login prompt?
Dec 12 21:48:48 <Guest96097> no. Starting kernel ...
Dec 12 21:48:49 <Guest96097> Uncompressing Linux... done, booting the kernel.
Dec 12 21:48:52 <Guest96097> nothing else
Dec 12 21:49:15 <XorA> either console= is wrong which is unlikely or kernel crashed early in boot
Dec 12 21:49:29 <Guest96097> let me reset and look at console=
Dec 12 21:50:05 <Guest96097> console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
Dec 12 21:50:24 <XorA> console=console=ttyS0,115200 ??
Dec 12 21:50:33 <Guest96097> that's what it says when I did printenv console
Dec 12 21:50:35 <XorA> seems to be too many console= there :-D
Dec 12 21:50:54 <XorA> setenv console 'console=ttyS0,115200'
Dec 12 21:52:48 <Guest96097> does this need adjusting: 
Dec 12 21:52:49 <Guest96097> setenv 'bootargs' bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/sda2 rootwait rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
Dec 12 21:53:50 <XorA> setenv bootargs 'console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/sda2 rootwait rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none'
Dec 12 21:53:54 <XorA> looks more correct to me
Dec 12 21:56:00 <Guest96097> still no output
Dec 12 21:56:34 <XorA> well Im currentl 6K miles from my sheeva
Dec 12 21:56:36 <Guest96097> I seem to remember some change to the name of serial port with newer linux kernels, or something silly?
Dec 12 21:56:44 <XorA> so I think Ive reached my limit to help
Dec 12 21:56:57 <XorA> omap changed I not sure if PXA did
Dec 12 21:56:59 <Guest96097> ok, thanks
Dec 12 21:57:12 <Guest96097> what was it changed to for omap?
Dec 12 21:57:13 <Guest96097> I'll try it
Dec 12 21:57:34 <Guest96097> ttyO0 right?
Dec 12 21:58:01 <XorA> O is for Omap :-D
Dec 12 21:58:10 <Guest96097> ah, duh
Dec 12 21:58:12 <Guest96097> woops
Dec 12 22:02:43 <Guest96097> do you think mainlineLinux should be set to yes?
Dec 12 22:05:03 <XorA> I never knew what that did :-D
Dec 12 22:13:00 <Guest96097> still nothing, hr
Dec 12 22:13:01 <Guest96097> m
Dec 12 22:13:54 <XorA> sorry not sure what to suggest
Dec 12 22:14:01 <XorA> I run debian on my sheeva
Dec 12 22:14:08 <Guest96097> it's ok
Dec 12 22:14:55 <Guest96097> I just wish I had more to work with, an error or something.
Dec 12 22:16:32 <XorA> are you building kernel yourself if so enable early printk
Dec 12 22:16:53 <Guest96097> I wasn't building it; was using the one supplied with the narcissus builder
Dec 12 22:17:02 <Guest96097> maybe I could try building one
Dec 12 22:19:05 <Guest96097> this guy wrote:
Dec 12 22:19:07 <Guest96097> "I have finally solved the problem. I had upgraded U-Boot, but it didn't work until I upgraded again with flip-flip's version. I configured it to boot from MMC and now I have angstrom working flawlessly. And for my purposes it works a lot better than Debian."
Dec 12 22:19:40 <Guest96097> so I suppose I should try this "flipflip" guy's uboot
Dec 12 22:22:17 <Guest96097> I will see what his patch does
Dec 12 22:27:59 <Guest96097> the patch: https://gist.github.com/1469416
Dec 12 22:29:07 <Guest96097> the only thing that's really noticeable really is the setting of CONFIG_ENV_ADDR and CONFIG_ENV_OFFSET
Dec 12 22:29:47 <Guest96097> and unsetting CONFIG_BOOTCOMMAND and CONFIG_EXTRA_ENV_SETTINGS
Dec 12 22:30:23 <Guest96097> and this is also for a guruplug, which is basically same hardware as sheevaplug, isn't it?
Dec 12 22:41:15 <XorA> basically yes
Dec 12 22:56:49 <Guest96097> welp, I've run out of ideas
Dec 12 22:57:11 <Guest96097> surely someone else here must be running angstrom on a sheeva. I'll wait till they can chime in.
**** ENDING LOGGING AT Tue Dec 13 01:20:13 2011

**** BEGIN LOGGING AT Tue Dec 13 01:22:14 2011
**** ENDING LOGGING AT Tue Dec 13 01:30:04 2011

**** BEGIN LOGGING AT Tue Dec 13 01:32:14 2011
Dec 13 01:36:17 <CIA-54> angstrom: 03testlab <testlab@angstrom> 07yocto * r235b675cd9 10testlab/beaglebone/eglibc/systemd-image/ (build-id installed-package-sizes.txt installed-packages.txt): beaglebone: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 089ac81925b7b00f9006d55343d80300ccf785d4
**** ENDING LOGGING AT Tue Dec 13 02:59:57 2011