Hi Ash,

1. My board doesn't hang and proc_gpio module is loading and working correctly.  In fact,
everything is working fine for me now ... (after applying the additional changes I will discuss below):

I am still using the original u-boot 1.2.0 (May 2008).

What uboot are you using?

Maybe the proc_gpio issue you have is related to using a newer uboot?

2. The udev-1.51 changed the way firmware gets loaded.

Instead of using the old firmware.sh script, it now builds a binary from C code which it installs in the
libexecs path.  The syntax for invoking the firmware helper is now different as well so affects the
udev rules, in particular the 50-firmware.rules (the new one is conveniently provided in the extras folder by
the kernel driver archive but was missed previously in the bitbake recipes update).
In addition, the new patch in the kernel build for changing the name of ethX to wlan0 in the libertas driver
was supposed to correspond with a change to remove that same functionality from the udev
rules files.

As a result, the previous recipes that were checked in for udev-1.51 needed to
be corrected in order for the wireless (Marvell libertas) to work (i.e. load the firmware correctly). 

I have sent you the new updated udev patches in a separate email.

I have also updated the libertas-firmware bitbake recipes to retrieve the latest firmware binaries
from the official linux-firmware git repository for libertas rather than duplicate it in our git repository.
This will have the effect of bumping up the  libertas-cs driver (cf8385) revision being used to 5.0.20p from
previous 5.0.16.

Note: There is no mesh support in this device/firmware but the latest version of the libertas driver in 2.6.31 added that feature.  
This is apparently why we will now get a message like this during boot:

   libertas: PREP_CMD: command 0x00a3 failed: 2
(The 0x00a3 means CMD_MESH_CONFIG_OLD which our device doesn't support)

From my research, I think the message can be ignored and doesn't affect anything adversely.

3. The rtc issue you encountered seems to be due to some inadvertent changes in the defconfig in the last git check in.
Probably due to that in my board, I use an external I2C based RTC (ds1307)  so need a slightly different defconfig.
In my case the kernel configuration needs to be different because the  related rtc drivers load as modules due to
dependency on i2c.  But in the PXA case, the RTC driver support needs to be integrated into the kernel.  I have sent
you a patch that fixes this for the latter (should be the default) PXA internal RTC case.

4. There were some additional config settings related to external firmware loading etc that were not correct
in the defconfig.  I have also included those changes in my patch.

5. When using the previous etc/network/interfaces file, the cf8535 wireless/wifi would overheat (burn your
finger hot!) and start randomly shutting down (and rebooting) the system.  It is fixed by un-commenting
(this should be mandatory) the line in the  recipes/netbase/gumstix-verdex/interfaces file:

      pre-up/sbin/iwconfig $IFACE txpower auto

This dramatically cuts the power (and heat) consumed by the device by disabling
the transmitters when not in use.

5. What was the reason for removing the cool "penguin-tux" boot up graphic logo
screen?  I included it back in the files I sent you (including the actual binary that
I had painstakingly scaled down from Overo version to work on the verdex-console-vx
lcd screen).


Since the additional patches will only confuse and muddle this thread, and I am also
sending a binary (as mentioned for the nice logo screen) this time I am sending them
in a private email to Ash. 

I have tested today everything mentioned above.

Ash, can you please review and test what I am sending you and check in to git if you concur?


Regards,
    Joseph



From: Ash Charles <ashcharles@gmail.com>
To: General mailing list for gumstix users. <gumstix-users@lists.sourceforge.net>
Sent: Fri, March 5, 2010 6:57:26 PM
Subject: Re: [Gumstix-users] Bitbaking New Kernel 2.6.31 for Verdex

Hi Joseph,
Thanks for the patches.  I've made the appropriate changes and pushes
the changes to the repository. Unfortunately, my board is still
hanging and I wonder if this is due to a failure loading the proc_gpio
module.

Also, I still see errors regarding a missing /dev/misc/rtc even if I
manually create the symlink or whatever I try in udev.  Any ideas?

Specific comments regarding the patches are given inline.

-Ash

On Fri, Mar 5, 2010 at 12:57 AM, Joseph Kortje <jpktech@rogers.com> wrote:
> Hi Ash,
>
> Here is my current additional patch list.  Most of this was sent via Steve
> Sakoman previously in my original files
> from November but I noticed that some things were  missed in the git
> checkin.  Some of it is now also needed to be revised slightly due
> to more recent Git repository differences.
>
> As you indicated, there are apparently some weird/new interactions with
> newer kernel and newer udev going on.
>
> My results are that it is at least booting now without hanging but I am
> still getting problems with libertas (wifi) firmware
> helper loading (and therefore no wlan).  There is no hot-plug event being
> received when toggling GPIO80 so I will try regressing to udev-141
> (which worked for 2.6.30) tomorrow. Also the DEFAULT_PREFERENCE = "-1" isn't
> working in those udev files
> so it is always picking 1.51.
Hmm.  I'm having issues even getting proc_gpio to load at the moment.
The angstrom distro now prefers udev-151.  I'm able to switch back to
udev-141 if I make the change in
conf/distro/include/angstrom-2008-preferred-versions.inc however it
causes some dependencies issues with angstrom-zeroconf-audio.

>
> With the udev1.51, there are some specific rule/syntax changes that you will
> see in the logs as warnings.
> The SYSFS is changed to ATTRS and the "NAME%k" is now deemed redundant.  The
> Overo repository already had those fixed
>  and I have ported those changes over.
Perfect :).  I'd actually pulled those changes from Overo but hadn't
merged them.  They're in there now.

>
> Also, I would prefer the better way to handle the ethX to wlan0 renaming
> issue which is to directly patch the libertas driver as per this
> information I found instead of doing it by messing with the udev rules:
>
> http://lists.infradead.org/pipermail/libertas-dev/2009-August/002661.html
Okay - I've added a libertas-eth-to-wlan patch based on this thread.

>
> (BTW, Overo also changed to use udev-1.51 in last few months ... and doesn't
> have the rule to rename eth* to wlan0 in their udev local
> rules either.  So is the libertas_sd driver working correctly?  I checked
> the kernel driver and it seems it will still create it as
> eth1 (assuming eth0 exists) so if there is a wlan0 in overo when using the
> libertas sdio device, where is that wlan0 name coming from now?)
I'm not sure on this.  Anyone with more Overo experience?

>
> Anyways, here's my additional patches below to be put on top of current
> verdex branch ....
> I also fixed bluetooth (there is a limit on the speed range for the bt
> device and a specific driver/protocol path called "gumstix" not "csr" that
> is used as a result of my previous bluez4 patch so the blueprobe patch that
> was in git was incompatible (bug).
Patched.

> BTW, the initial hang was due to the missing INSTALL_LINGUAS = "" in
> verdex-console-image.bb
> which I had previously sent a follow up email to Steve about in November.
Patched.

> And I think the fstab (filesystem table) stuff
> should be the same as used for overo (specifically no more /sysfs, not like
> the old one used in older kernel based verdex) so I fixed that as well.
I'm a little confused about what should really be in the fstab.  What
is the motivation for removing /sysfs?  Likewise, I see these errors:
"logger: mount: mount point /dev/pts does not exist
logger: mount: mount point /dev/shm does not exist"
If I remove /dev/pts and /dev/shm from fstab, these errors go away
because a 'mount -a' no longer tries to mount these listings that have
already been created by udev earlier in the init.d sequence.  I'm not
sure if this is the right approach but I've found this:
https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/321927

> The gsm recipe patch for verdex is added to support the verdex audio-gps
> stix add-on card (again, I haven't verified
> it but it is the same as used previously from com.gumstix.collection so
> should be safe).
Patched but not tested.

>
> Note: these patches are temporary, unofficial and subject to change .... Ash
> will need to review this and then make the appropriate changes
> to integrate it into the git repository....
>
> Regards
> Joseph
> --------------------------------------------------------------------------------------------------
> diff --git a/recipes/base-files/base-files/gumstix-verdex/fstab
> b/recipes/base-files/base-files/gumstix-verdex/fstab
> index 9b5f00c..311bad1 100644
> --- a/recipes/base-files/base-files/gumstix-verdex/fstab
> +++ b/recipes/base-files/base-files/gumstix-verdex/fstab
> @@ -2,10 +2,9 @@
>
>  rootfs               /                    auto       defaults
> 1  1
>  proc                 /proc                proc       defaults
> 0  0
> -sysfs                /sys                 sysfs      defaults
> 0  0
> -tmpfs                /dev                 tmpfs      defaults
> 0  0
> -devpts               /dev/pts             devpts     gid=5,mode=620
> 0  0
> +devpts               /dev/pts             devpts     mode=0620,gid=5
> 0  0
> +usbfs                /proc/bus/usb        usbfs      defaults
> 0  0
> +tmpfs                /var/volatile        tmpfs      defaults
> 0  0
>  tmpfs                /dev/shm             tmpfs      mode=0777
> 0  0
> -tmpfs                /var/volatile        tmpfs      mode=0755
> 0  0
>  tmpfs                /media/ram           tmpfs      defaults
> 0  0
>
> diff --git a/recipes/base-passwd/files/gumstix-verdex/README
> b/recipes/base-passwd/files/gumstix-verdex/README
> index e69de29..41ea057 100644
> --- a/recipes/base-passwd/files/gumstix-verdex/README
> +++ b/recipes/base-passwd/files/gumstix-verdex/README
> @@ -0,0 +1,7 @@
> +The patch sets a root password on /etc/passwd, this password is:
> +
> +gumstix
> +
> +This allows ssh (dropbear) login to a gumstix using that
> +password.
> +
> diff --git a/recipes/base-passwd/files/gumstix-verdex/root-home.patch
> b/recipes/base-passwd/files/gumstix-verdex/root-home.patch
> index e69de29..f1b1628 100644
> --- a/recipes/base-passwd/files/gumstix-verdex/root-home.patch
> +++ b/recipes/base-passwd/files/gumstix-verdex/root-home.patch
> @@ -0,0 +1,8 @@
> +--- base-passwd/passwd.master.orig    2005-07-08 06:26:22.000000000 +0200
> ++++ base-passwd/passwd.master    2005-07-08 06:31:58.000000000 +0200
> +@@ -1,4 +1,4 @@
> +-root::0:0:root:/root:/bin/sh
> ++root:hsUZp3u/ivKP2:0:0:root:/home/root:/bin/sh
> + daemon:*:1:1:daemon:/usr/sbin:/bin/sh
> + bin:*:2:2:bin:/bin:/bin/sh
> + sys:*:3:3:sys:/dev:/bin/sh
> diff --git a/recipes/blueprobe/blueprobe-0.18/verdex.patch
> b/recipes/blueprobe/blueprobe-0.18/verdex.patch
> index 074c4e7..04c20fd 100644
> --- a/recipes/blueprobe/blueprobe-0.18/verdex.patch
> +++ b/recipes/blueprobe/blueprobe-0.18/verdex.patch
> @@ -7,8 +7,8 @@
>  +    "Gumstix verdex")
>  +    BLUETOOTH=yes
>  +    PORT=/dev/ttyS1
> -+    SPEED=115200
> -+    PROTO=csr
> ++    SPEED=921600
> ++    PROTO=gumstix
>  +    PROBE=no
>  +    ;;
>
> diff --git a/recipes/gsm/files/gumstix-verdex/default
> b/recipes/gsm/files/gumstix-verdex/default
> index e69de29..94d787b 100644
> --- a/recipes/gsm/files/gumstix-verdex/default
> +++ b/recipes/gsm/files/gumstix-verdex/default
> @@ -0,0 +1,8 @@
> +# gsmd    This shell script configures for the gsmd init script.
> +
> +. /etc/init.d/functions
> +
> +GSM_DEV="/dev/ttyACM1"
> +GSMD_OPTS=""
> +GSM_POW="/proc/gpio/GPIO100"
> +
> diff --git a/recipes/gsm/files/gumstix-verdex/gsmd
> b/recipes/gsm/files/gumstix-verdex/gsmd
> index e69de29..45d9683 100644
> --- a/recipes/gsm/files/gumstix-verdex/gsmd
> +++ b/recipes/gsm/files/gumstix-verdex/gsmd
> @@ -0,0 +1,46 @@
> +#! /bin/sh
> +#
> +# gsmd  This shell script starts and stops gsmd.
> +#
> +# chkconfig: 345 90 40
> +# description: Gsmd manages access to a serial- or USB-connected GSM
> +# processname: gsmd
> +
> +PATH=/bin:/usr/bin:/sbin:/usr/sbin
> +
> +[ -f /etc/default/rcS ] && . /etc/default/rcS
> +[ -f /etc/default/gsmd ] && . /etc/default/gsmd
> +
> +case "$1" in
> +    start)
> +        [ -n "$GSM_DL" ] && ( echo "1" >$GSM_DL; sleep 1 )
> +        [ -n "$GSM_POW" ] && ( echo "GPIO out clear" >$GSM_POW; sleep 1 )
> +        [ -n "$GSM_POW" ] && ( echo "GPIO out set" >$GSM_POW; sleep 1 )
> +
> +        echo -n "Starting GSM daemon: "
> +        start-stop-daemon -S -x /usr/sbin/gsmd -- gsmd -p $GSM_DEV
> $GSMD_OPTS -d -l syslog
> +
> +        if [ $? = 0 ]; then
> +            echo "gsmd."
> +        else
> +            echo "(failed.)"
> +        fi
> +        ;;
> +    stop)
> +        [ -n "$GSM_POW" ] && echo "GPIO out clear" >$GSM_POW
> +
> +        echo -n "Stopping GSM daemon: "
> +        start-stop-daemon -K -x /usr/sbin/gsmd
> +        echo "gsmd."
> +        ;;
> +    restart|force-reload)
> +        $0 stop
> +        $0 start
> +        ;;
> +    *)
> +        echo "Usage: /etc/init.d/gsmd {start|stop|restart|force-reload}"
> +        exit 1
> +        ;;
> +esac
> +
> +exit 0
> diff --git a/recipes/images/verdex-console-image.bb
> b/recipes/images/verdex-console-image.bb
> index 429dc5d..ea38cf7 100644
> --- a/recipes/images/verdex-console-image.bb
> +++ b/recipes/images/verdex-console-image.bb
> @@ -5,6 +5,7 @@ inherit image
>  DEPENDS = "task-base-gumstix"
>
>  IMAGE_EXTRA_INSTALL ?= ""
> +IMAGE_LINGUAS = ""
>
>  AUDIO_INSTALL = " \
>    alsa-utils \
> diff --git a/recipes/pxaregs/pxaregs_1.14.bb
> b/recipes/pxaregs/pxaregs_1.14.bb
> index 30853c3..6cfbc43 100644
> --- a/recipes/pxaregs/pxaregs_1.14.bb
> +++ b/recipes/pxaregs/pxaregs_1.14.bb
> @@ -10,7 +10,7 @@ SRC_URI =
> "http://www.mn-logistik.de/unsupported/pxa250/pxaregs.c \
>             file://munmap.patch;pnum=1;patch=1 \
>             file://serial.patch;pnum=1;patch=1 \
>             file://usb.patch;pnum=1;patch=1 \
> -           file://pxa270.patch;patch=1 \
> +           file://pxa270.patch;pnum=1;patch=1 \
>  "
>
>  S = "${WORKDIR}"
> diff --git a/recipes/udev/udev-124/local.rules
> b/recipes/udev/udev-124/local.rules
> index 3b2bd5e..f472da0 100644
> --- a/recipes/udev/udev-124/local.rules
> +++ b/recipes/udev/udev-124/local.rules
> @@ -22,7 +22,7 @@ SUBSYSTEM=="net", ACTION=="add"
> RUN+="/etc/udev/scripts/network.sh"
>  SUBSYSTEM=="net", ACTION=="remove" RUN+="/etc/udev/scripts/network.sh"
>
>  # The first rtc device is symlinked to /dev/rtc
> -KERNEL=="rtc0", SYMLINK+="rtc"
> +KERNEL=="rtc0", SYMLINK+="rtc misc/rtc"
>
>  # Try and modprobe for drivers for new hardware
>  ACTION=="add", DEVPATH=="/devices/*", ENV{MODALIAS}=="?*",
> RUN+="/sbin/modprobe $env{MODALIAS}"
> diff --git a/recipes/udev/udev-141/local.rules
> b/recipes/udev/udev-141/local.rules
> index 2acdd7c..d55d1e3 100644
> --- a/recipes/udev/udev-141/local.rules
> +++ b/recipes/udev/udev-141/local.rules
> @@ -22,7 +22,7 @@ SUBSYSTEM=="net", ACTION=="add"
> RUN+="/etc/udev/scripts/network.sh"
>  SUBSYSTEM=="net", ACTION=="remove" RUN+="/etc/udev/scripts/network.sh"
>
>  # The first rtc device is symlinked to /dev/rtc
> -KERNEL=="rtc0", SYMLINK+="rtc"
> +KERNEL=="rtc0", SYMLINK+="rtc misc/rtc"
>
>  #The first framebuffer is symlinked to /dev/fb
>  KERNEL=="fb0",  SYMLINK+="fb"
> @@ -34,6 +34,7 @@ ACTION=="add", DEVPATH=="/devices/*", ENV{MODALIAS}=="?*",
> RUN+="/sbin/modprobe
>  SUBSYSTEM=="input", KERNEL=="event[0-9]*",
> SYSFS{modalias}=="input:*-e0*,3,*a0,1,*18,*", SYMLINK+="input/touchscreen0"
>  SUBSYSTEM=="input", KERNEL=="event[0-9]*", SYSFS{modalias}=="ads7846",
> SYMLINK+="input/touchscreen0"
>
> -# Rename wifi module (/class/net/ethX) (libertas_sdio|libertas_cf)
> +# Rename wifi module (/class/net/ethX) (libertas_sdio|libertas_cs)
>  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="libertas_sdio", KERNEL=="eth*",
> NAME="wlan0"
> -SUBSYSTEM=="net", ACTION=="add", DRIVERS=="libertas_cf", KERNEL=="eth*",
> NAME="wlan0"
> +SUBSYSTEM=="net", ACTION=="add", DRIVERS=="libertas_cs", KERNEL=="eth*",
> NAME="wlan0"
> +
> diff --git a/recipes/udev/udev-151/local.rules
> b/recipes/udev/udev-151/local.rules
> index c28b158..cbd764f 100644
> --- a/recipes/udev/udev-151/local.rules
> +++ b/recipes/udev/udev-151/local.rules
> @@ -31,5 +31,10 @@ KERNEL=="fb0",  SYMLINK+="fb"
>  ACTION=="add", DEVPATH=="/devices/*", ENV{MODALIAS}=="?*",
> RUN+="/sbin/modprobe $env{MODALIAS}"
>
>  # Create a symlink to any touchscreen input device
> -SUBSYSTEM=="input", KERNEL=="event[0-9]*",
> SYSFS{modalias}=="input:*-e0*,3,*a0,1,*18,*", SYMLINK+="input/touchscreen0"
> -SUBSYSTEM=="input", KERNEL=="event[0-9]*", SYSFS{modalias}=="ads7846",
> SYMLINK+="input/touchscreen0"
> +SUBSYSTEM=="input", KERNEL=="event[0-9]*",
> ATTRS{modalias}=="input:*-e0*,3,*a0,1,*18,*", SYMLINK+="input/touchscreen0"
> +SUBSYSTEM=="input", KERNEL=="event[0-9]*", ATTRS{modalias}=="ads7846",
> SYMLINK+="input/touchscreen0"
> +
> +# Rename wifi module (/class/net/ethX) (libertas_sdio|libertas_cs)
> +SUBSYSTEM=="net", ACTION=="add", DRIVERS=="libertas_sdio", KERNEL=="eth*",
> NAME="wlan0"
> +SUBSYSTEM=="net", ACTION=="add", DRIVERS=="libertas_cs", KERNEL=="eth*",
> NAME="wlan0"
> +
> diff --git a/recipes/udev/udev-151/udev.rules
> b/recipes/udev/udev-151/udev.rules
> index 117ba90..60288c0 100644
> --- a/recipes/udev/udev-151/udev.rules
> +++ b/recipes/udev/udev-151/udev.rules
> @@ -15,7 +15,7 @@
>
>  # workaround for devices which do not report media changes
>  SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", ATTR{removable}=="1", \
> -    ENV{ID_MODEL}=="IOMEGA_ZIP*", NAME="%k", OPTIONS+="all_partitions"
> +    ENV{ID_MODEL}=="IOMEGA_ZIP*", OPTIONS+="all_partitions"
>  SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", ATTRS{media}=="floppy", \
>      OPTIONS+="all_partitions"
>
> @@ -103,7 +103,7 @@ SUBSYSTEM=="aoe", KERNEL=="revalidate",
> NAME="etherd/%k"
>  KERNEL=="dm-[0-9]*",        OPTIONS+="ignore_device"
>  KERNEL=="device-mapper",    NAME="mapper/control"
>
> -KERNEL=="rfcomm[0-9]*", NAME="%k",GROUP="users", MODE="0660"
> +KERNEL=="rfcomm[0-9]*", GROUP="users", MODE="0660"
>
>  # Firmware Helper
>  ACTION=="add", SUBSYSTEM=="firmware", RUN+="/lib/udev/firmware.sh"
> diff --git a/recipes/udev/udev_151.bb b/recipes/udev/udev_151.bb
> index f11d529..fe02639 100644
> --- a/recipes/udev/udev_151.bb
> +++ b/recipes/udev/udev_151.bb
> @@ -3,6 +3,8 @@ DESCRIPTION = "udev is a daemon which dynamically creates
> and removes device nod
>  the hotplug package and requires a kernel not older than 2.6.12."
>  LICENSE = "GPL"
>
> +PR = "r4"
> +
>  # Untested
>  DEFAULT_PREFERENCE = "-1"
>
> -------------------------------------------------------------------
> #The following patch is optional (for alsa sound support with gumstix verdex
> PXA270)
> #The alsa part of these patches is optional and un-verified. Currently the
> task-base-gumstix.bb recipe isn't pulling this
> #in because there is some conflict with #the common sound modules and the
> PXA27X requirements that still needs to
> #be worked out.
>
> diff --git a/recipes/alsa/alsa-state/gumstix-verdex/alsa-state
> b/recipes/alsa/alsa-state/gumstix-verdex/alsa-state
> index e69de29..1d012ee
> --- a/recipes/alsa/alsa-state/gumstix-verdex/alsa-state
> +++ b/recipes/alsa/alsa-state/gumstix-verdex/alsa-state
> @@ -0,0 +1,34 @@
> +#! /bin/sh
> +#
> +# Copyright Matthias Hentges <devel@hentges.net> (c) 2007
> +# License: GPL (see http://www.gnu.org/licenses/gpl.txt for a copy of the
> license)
> +#
> +# Filename: alsa-state
> +# Date: 20070308 (YMD)
> +
> +
> +asound_restore(){
> +  echo "ALSA: loading sound modules..."
> +  modprobe ucb1400-ts
> +  modprobe snd-soc-gumstix
> +  modprobe snd-pcm-oss
> +  modprobe snd-mixer-oss
> +  echo "ALSA: Restoring mixer settings..."
> +  if test -x /usr/sbin/alsactl -a -e /etc/asound.state
> +  then
> +    /usr/sbin/alsactl -f /etc/asound.state restore
> +  fi
> +}
> +
> +asound_store(){
> +  echo "ALSA: Storing mixer settings..."
> +  if test -x /usr/sbin/alsactl
> +  then
> +    /usr/sbin/alsactl -f /etc/asound.state store
> +  fi
> +}
> +
> +case "$1" in
> +start)        asound_restore ;;
> +stop)        asound_store ;;
> +esac
> diff --git a/recipes/alsa/alsa-state/gumstix-verdex/asound.state
> b/recipes/alsa/alsa-state/gumstix-verdex/asound.state
> index e69de29..2ad4563 100644
> --- a/recipes/alsa/alsa-state/gumstix-verdex/asound.state
> +++ b/recipes/alsa/alsa-state/gumstix-verdex/asound.state
> @@ -0,0 +1,122 @@
> +state.Gumstix {
> +        control.1 {
> +                comment.access 'read write'
> +                comment.type INTEGER
> +                comment.count 1
> +                comment.range '0 - 4'
> +                iface MIXER
> +                name 'Tone Control - Bass'
> +                value 0
> +        }
> +        control.2 {
> +                comment.access 'read write'
> +                comment.type INTEGER
> +                comment.count 1
> +                comment.range '0 - 2'
> +                iface MIXER
> +                name 'Tone Control - Treble'
> +                value 0
> +        }
> +        control.3 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'Headphone Playback Switch'
> +                value true
> +        }
> +        control.4 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name De-emphasis
> +                value false
> +        }
> +        control.5 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'DC Filter'
> +                value true
> +        }
> +        control.6 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'Hi-pass Filter'
> +                value true
> +        }
> +        control.7 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'ADC Filter'
> +                value true
> +        }
> +        control.8 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'Master Playback Switch'
> +                value true
> +        }
> +        control.9 {
> +                comment.access 'read write'
> +                comment.type INTEGER
> +                comment.count 2
> +                comment.range '0 - 63'
> +                iface MIXER
> +                name 'Master Playback Volume'
> +                value.0 63
> +                value.1 63
> +        }
> +        control.10 {
> +                comment.access 'read write'
> +                comment.type ENUMERATED
> +                comment.count 2
> +                comment.item.0 Mic
> +                comment.item.1 CD
> +                comment.item.2 Video
> +                comment.item.3 Aux
> +                comment.item.4 Line
> +                comment.item.5 Mix
> +                comment.item.6 'Mix Mono'
> +                comment.item.7 Phone
> +                iface MIXER
> +                name 'Capture Source'
> +                value.0 Mic
> +                value.1 Mic
> +        }
> +        control.11 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'Capture Switch'
> +                value true
> +        }
> +        control.12 {
> +                comment.access 'read write'
> +                comment.type INTEGER
> +                comment.count 2
> +                comment.range '0 - 15'
> +                iface MIXER
> +                name 'Capture Volume'
> +                value.0 15
> +                value.1 15
> +        }
> +        control.13 {
> +                comment.access 'read write'
> +                comment.type BOOLEAN
> +                comment.count 1
> +                iface MIXER
> +                name 'Loudness (bass boost)'
> +                value false
> +        }
> +}
> +
> --------------------------------------------------------------------
>
>
>
>
>
>
>
>
>
>
>
>
> ________________________________
> From: Ash Charles <ashcharles@gmail.com>
> To: General mailing list for gumstix users.
> <gumstix-users@lists.sourceforge.net>
> Sent: Thu, March 4, 2010 8:47:07 PM
> Subject: Re: [Gumstix-users] Bitbaking New Kernel 2.6.31 for Verdex
>
> Hi,
>
> I can duplicate these hangs---what was booting for me the other day is
> not working now.  I've updated my code and I've been working through
> some of the errors listed in the provided boot logs.  Mostly, these
> seem to be errors in the kernel configuration and udev.
>
> Currently, I'm stumbling up against errors loading the proc_gpio
> module and properly detecting the network interface chip.  The init
> sequence gets to the last entry S99... but isn't giving me a login
> prompt. I'll update the repository as soon as I get something going.
>
> @Joseph: Thanks for your hard work and please let me know what patches
> I missed. For your reference, I thought I'd pulled most of the changes
> from an e-mail from Steve around the time of this thread:
> http://old.nabble.com/verdex-svn-staleness-td22632802.html#a26203601
>
> Thanks again for the feedback.
>
> -Ash
>
>
>
> On Wed, Mar 3, 2010 at 11:32 AM, mlq <mark.l.quilling@lmco.com> wrote:
>>
>> Hey Ash,
>>
>> I re-flashed u-boot and the latest version and still got the same errors
>> as
>> I did on the first boot; here is the output from the second boot:
>>
>> U-Boot 1.2.0 (May 10 2008 - 21:17:19) - PXA270@400 MHz - 1604
>>
>> *** Welcome to Gumstix ***
>>
>> DRAM:  64 MB
>> Flash: 16 MB
>> Using default environment
>>
>> Hit any key to stop autoboot:  0
>> GUM> mmcinit
>> No MMC card found
>> GUM> mmcinit
>> Detected: 1927168 blocks of 1024 bytes (1882MB) SD card.
>> Vendor: Man 02 OEM TM "SA02G" Date 10/2009
>> Product: 2628934609
>> Revision: 0.3
>> GUM> setenv bootargs console=ttyS0,115200n8 rootdelay=1
>> root=/dev/mmcblk0p2
>> GUM> fatload mmc 0 a2000000 uimage
>> reading uimage
>>
>> 1291348 bytes read
>> GUM> bootm a2000000
>> ## Booting image at a2000000 ...
>>   Image Name:   Angstrom/2.6.31/gumstix-verdex
>>   Image Type:   ARM Linux Kernel Image (uncompressed)
>>   Data Size:    1291284 Bytes =  1.2 MB
>>   Load Address: a0008000
>>   Entry Point:  a0008000
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing
>>
>> Linux..................................................................................
>> done, booting the kernel.
>> Linux version 2.6.31 (gcc version 4.3.3 (GCC) ) #1 Fri Feb 26 15:45:41 PST
>> 2010
>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f
>> CPU: VIVT data cache, VIVT instruction cache
>> Machine: Gumstix verdex
>> Memory policy: ECC disabled, Data cache writeback
>> Run Mode clock: 208.00MHz (*16)
>> Turbo Mode clock: 416.00MHz (*2.0, active)
>> Memory clock: 104.00MHz (/2)
>> System bus clock: 104.00MHz
>> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
>> Kernel command line: console=ttyS0,115200n8 rootdelay=1
>> root=/dev/mmcblk0p2
>> PID hash table entries: 256 (order: 8, 1024 bytes)
>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>> Memory: 64MB = 64MB total
>> Memory: 62248KB available (2212K code, 252K data, 88K init, 0K highmem)
>> NR_IRQS:192
>> Console: colour dummy device 80x30
>> Calibrating delay loop... 415.33 BogoMIPS (lpj=2076672)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> NET: Registered protocol family 16
>> Gumstix verdex udc is disabled
>> Initializing Gumstix verdex i2c
>> Initializing Gumstix verdex smsc911x
>> Initializing Gumstix verdex pcmcia
>> Not netCF-vx board: pcmcia using newer GPIO configuration
>> CPLD responded with: ff
>> found 1 CF slots
>> Initializing Gumstix verdex FB info
>> Initializing Gumstix platform_add_devices
>> bio: create slab <bio-0> at 0
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>> TCP established hash table entries: 2048 (order: 2, 16384 bytes)
>> TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
>> TCP: Hash tables configured (established 2048 bind 2048)
>> TCP reno registered
>> NET: Registered protocol family 1
>> msgmni has been set to 121
>> alg: No test for stdrng (krng)
>> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
>> io scheduler noop registered
>> io scheduler cfq registered (default)
>> Console: switching to colour frame buffer device 80x24
>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
>> console [ttyS0] enabled
>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>> bankwidth)
>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>>  Intel/Sharp Extended Query Table at 0x010A
>>  Intel/Sharp Extended Query Table at 0x010A
>>  Intel/Sharp Extended Query Table at 0x010A
>>  Intel/Sharp Extended Query Table at 0x010A
>>  Intel/Sharp Extended Query Table at 0x010A
>> Using buffer write method
>> Using auto-unlock on power-up/resume
>> cfi_cmdset_0001: Erase suspend on write enabled
>> Using static partitions on Gumstix Flash ROM
>> Creating 3 MTD partitions on "Gumstix Flash ROM":
>> 0x000000000000-0x000000040000 : "Bootloader"
>> 0x000000040000-0x000000f00000 : "RootFS"
>> 0x000000f00000-0x000001000000 : "Kernel"
>> pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
>> TCP cubic registered
>> NET: Registered protocol family 17
>> XScale iWMMXt coprocessor detected.
>> pxa-rtc pxa-rtc: setting system clock to 2000-01-01 00:00:51 UTC
>> (946684851)
>> Waiting 1sec before mounting root device...
>> mmc0: host does not support reading read-only switch. assuming
>> write-enable.
>> mmc0: new SD card at address 1234
>> mmcblk0: mmc0:1234 SA02G 1.83 GiB
>>  mmcblk0: p1 p2
>> kjournald starting.  Commit interval 5 seconds
>> EXT3 FS on mmcblk0p2, internal journal
>> EXT3-fs: recovery complete.
>> EXT3-fs: mounted filesystem with writeback data mode.
>> VFS: Mounted root (ext3 filesystem) on device 179:2.
>> Freeing init memory: 88K
>> INIT: version 2.86 booting
>> Please wait: booting...
>> Starting udev
>> udevd[47]: SYSFS{}= will be removed in a future udev version, please use
>> ATTR{}= to match the event device, or ATTRS{}= to match a parent device,
>> in
>> /etc/udev/rules.d/local.rules:34
>>
>> udevd[47]: SYSFS{}= will be removed in a future udev version, please use
>> ATTR{}= to match the event device, or ATTRS{}= to match a parent device,
>> in
>> /etc/udev/rules.d/local.rules:35
>>
>> udevd[47]: NAME="%k" is superfluous and breaudev: starting version 151
>> ks kernel supplied names, please remove it from
>> /etc/udev/rules.d/udev.rules:18
>>
>> udevd[47]: NAME="%k" is superfluous and breaks kernel supplied names,
>> please
>> remove it from /etc/udev/rules.d/udev.rules:106
>>
>> Remounting root file system...
>>
>> udevadm settle - timeout of 3 seconds reached, the event queue contains:
>>  /sys/devices/platform/pxa2xx-mci.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0
>> (193)
>>
>>
>> /sys/devices/platform/pxa2xx-mci.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p1
>> (194)
>>
>>
>> /sys/devices/platform/pxa2xx-mci.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p2
>> (195)
>> Caching udev devnodes
>> Populating dev cachemv: cannot stat `/tmp/uname': No such file or
>> directory
>> Bluetooth: Core ver 2.15
>> FAT: codepage cp437 not found
>> NET: Registered protocol family 31
>> Bluetooth: HCI device and connection manager initialized
>> Bluetooth: HCI socket layer initialized
>> Bluetooth: L2CAP ver 2.13
>> Bluetooth: L2CAP socket layer initialized
>> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>> usbcore: registered new interface driver usbfs
>> usbcore: registered new interface driver hub
>> usbcore: registered new device driver usb
>> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
>> pxa27x-ohci pxa27x-ohci: PXA27x OHCI
>> pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1
>> pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
>> usb usb1: configuration #1 chosen from 1 choice
>> hub 1-0:1.0: USB hub found
>> hub 1-0:1.0: 3 ports detected
>> Registering gumstix PCMCIA interface.
>> Bluetooth: RFCOMM TTY layer initialized
>> Bluetooth: RFCOMM socket layer initialized
>> Bluetooth: RFCOMM ver 1.11
>> smsc911x: Driver version 2008-10-21.
>> eth%d: smsc911x_init: Driver Parameters:
>> eth%d: smsc911x_init: LAN base: 0xC4A00000
>> eth%d: smsc911x_init: IRQ: 163
>> eth%d: smsc911x_init: PHY will be autodetected.
>> eth%d: smsc911x_init: BYTE_TEST: 0x87654321
>> eth%d: smsc911x_init: LAN911x identified, idrev: 0x01170002, generation: 2
>> eth0: smsc911x_drv_probe: Network interface: "eth0"
>> eth0: smsc911x_phy_initialise_external: HW_CFG EXT_PHY_DET clear, using
>> internal PHY
>> smsc911x-mdio: probed
>> eth0: smsc911x_mii_probe: PHY 1: addr 1, phy_id 0x0007C0D1
>> eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01,
>> irq=-1)
>> eth0: smsc911x_phy_check_loopbackpkt: Successfully verified loopback
>> packet
>> eth0: smsc911x_mii_probe: Passed Loop Back Test
>> eth0: smsc911x_mii_probe: phy initialised succesfully
>> eth0: smsc911x_drv_probe: MAC Address is derived from system serial number
>> net eth0: MAC Address: 02:4c:b7:81:b2:d0
>> Unknown HZ value! (47) Assume 100.
>> logger: mount: mount point /dev/pts does not exist
>> logger: mount: mount point /dev/shm does not exist
>> Starting Marvell Wifi CF8385...
>> Configuring network interfaces... eth0: smsc911x_open: irq polarity:
>> active
>> low
>> eth0: smsc911x_open: irq type: push-pull
>> eth0: smsc911x_open: Testing irq handler using IRQ 163
>> eth0: smsc911x_open: IRQ handler passed test using IRQ 163
>> net eth0: SMSC911x/921x identified at 0xc4a00000, IRQ: 163
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000000C, HASHH 0x00000000,
>> HASHL 0x00000000
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000200C, HASHH 0x00000000,
>> HASHL 0x80000000
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000200C, HASHH 0x00000000,
>> HASHL 0x80000000
>> eth0      no wireless extensions.
>>
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000200C, HASHH 0x00000000,
>> HASHL 0x80000000
>> udhcpc (v1.13.2) started
>> run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000200C, HASHH 0x00000000,
>> HASHL 0x80000000
>> Sending discover...
>> eth0: smsc911x_phy_adjust_link: duplex state has changed
>> eth0: smsc911x_phy_adjust_link: configuring for half duplex mode
>> eth0: smsc911x_phy_update_flowcontrol: half duplex
>> eth0: smsc911x_phy_adjust_link: carrier state has changed
>> eth0: smsc911x_phy_adjust_link: configuring for no carrier
>> Sending discover...
>> Sending discover...
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000200C, HASHH 0x00000000,
>> HASHL 0x80000000
>> No lease, failing
>> done.
>> Starting portmap daemon: portmapportmap: fork: No such device.
>> Unknown HZ value! (69) Assume 100.
>> net.ipv4.conf.default.rp_filter = 1
>> net.ipv4.conf.all.rp_filter = 1
>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>> Mon Mar  1 11:18:00 UTC 2010
>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>> Turning echo off on /dev/ttyS1
>> /etc/rcS.d/S97blueprobe: line 5: can't open /dev/ttyS1: no such file
>> eth0: smsc911x_rx_multicast_update: maccr 0x1000200C, HASHH 0x00000000,
>> HASHL 0x80008000
>> tsc2003_probe
>> tsc2003 i2c touch screen controller
>> Bill Gatliff <bgat at billgatliff.com
>> Nicholas Chen <nchen at cs.umd.edu>
>> tsc2003_probe: checking i2c
>> tsc2003_probe: calling kzalloc
>> tsc2003_probe: probing address 0x48
>> i2c: error: exhausted retries
>> i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
>> i2c: ICR: 000087e0 ISR: 00000002
>> tsc2003: probe of 0-0048 failed with error -121
>> I2C: i2c-0: PXA I2C adapter
>> I2C: i2c-1: PXA I2C adapter
>> i2c /dev entries driver
>>
>> Ash Charles wrote:
>>>
>>> Hi mlq,
>>>
>>> I don't see the same behaviour where setenv needs to be called before
>>> fatload.  As these commands do completely different things, it would
>>> seem like a bug to me.  Have you tried using the more recent 1604
>>> version of uboot?
>>>
>>> The U-Boot files are available here:
>>>  http://www.gumstix.net/feeds/u-boot/
>>> The instructions for *carefully* reflashing U-Boot via serial
>>> connection are given here:
>>>
>>> http://www.gumstix.net/User-How-To-s/view/Developer-how-to-s/Reflashing-using-a-serial-connection/110.html
>>>
>>> I'll have to look through the messages you are seeing in detail.  Some
>>> seem to be configuration/installation issues: does it work any better
>>> the second time you try to boot?  Other ones seem to be problems with
>>> how I've set up udev.
>>>
>>> Thanks for your feedback,
>>>
>>> Ash
>>> On Wed, Mar 3, 2010 at 10:03 AM, mlq <mark.l.quilling@lmco.com> wrote:
>>>>
>>>> Ok so I finally got it to boot; looks like the setenv has to be called
>>>> before
>>>> fatload.  However the boot locks up; below is the output.  Here is the
>>>> fdisk
>>>> output on how my sd card is formated.  Note that the FAT partition only
>>>> has
>>>> the uimage on it and the ext3 has the un-tarred rootfs.
>>>>
>>>> Disk /dev/sdb: 1973 MB, 1973420032 bytes
>>>> 255 heads, 63 sectors/track, 239 cylinders
>>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>>> Disk identifier: 0x00000000
>>>>
>>>>   Device Boot      Start         End      Blocks   Id  System
>>>> /dev/sdb1   *           1           5       40131    c  W95 FAT32 (LBA)
>>>> /dev/sdb2               6         239     1879605   83  Linux
>>>>
>>>> U-Boot 1.2.0 (Dec 21 2007 - 13:34:50) - PXA270@400 MHz - 1578M
>>>>
>>>> *** Welcome to Gumstix ***
>>>>
>>>> DRAM:  64 MB
>>>> Flash: 16 MB
>>>> Using default environment
>>>>
>>>> Hit any key to stop autoboot:  0
>>>> GUM> mmcinit
>>>> Detected: 1927168 blocks of 1024 bytes (1882MB) SD card.
>>>> Vendor: Man 02 OEM TM "SA02G" Date 10/2009
>>>> Product: 2628934609
>>>> Revision: 0.3
>>>> GUM> setenv bootargs console=ttyS0,115200n8 rootdelay=1
>>>> root=/dev/mmcblk0p2
>>>> GUM> fatload mmc 0 a2000000 uimage
>>>> reading uimage
>>>>
>>>> 1291348 bytes read
>>>> GUM> bootm a2000000
>>>> ## Booting image at a2000000 ...
>>>>   Image Name:   Angstrom/2.6.31/gumstix-verdex
>>>>   Image Type:   ARM Linux Kernel Image (uncompressed)
>>>>   Data Size:    1291284 Bytes =  1.2 MB
>>>>   Load Address: a0008000
>>>>   Entry Point:  a0008000
>>>> OK
>>>>
>>>> Starting kernel ...
>>>>
>>>> Uncompressing
>>>>
>>>> Linux..................................................................................
>>>> done, booting the kernel.
>>>> Linux version 2.6.31 (gcc version 4.3.3 (GCC) ) #1 Fri Feb 26 15:45:41
>>>> PST
>>>> 2010
>>>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f
>>>> CPU: VIVT data cache, VIVT instruction cache
>>>> Machine: Gumstix verdex
>>>> Memory policy: ECC disabled, Data cache writeback
>>>> Run Mode clock: 208.00MHz (*16)
>>>> Turbo Mode clock: 416.00MHz (*2.0, active)
>>>> Memory clock: 104.00MHz (/2)
>>>> System bus clock: 104.00MHz
>>>> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
>>>> 16256
>>>> Kernel command line: console=ttyS0,115200n8 rootdelay=1
>>>> root=/dev/mmcblk0p2
>>>> PID hash table entries: 256 (order: 8, 1024 bytes)
>>>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>>>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>>>> Memory: 64MB = 64MB total
>>>> Memory: 62248KB available (2212K code, 252K data, 88K init, 0K highmem)
>>>> NR_IRQS:192
>>>> Console: colour dummy device 80x30
>>>> Calibrating delay loop... 415.33 BogoMIPS (lpj=2076672)
>>>> Mount-cache hash table entries: 512
>>>> CPU: Testing write buffer coherency: ok
>>>> NET: Registered protocol family 16
>>>> Gumstix verdex udc is disabled
>>>> Initializing Gumstix verdex i2c
>>>> Initializing Gumstix verdex smsc911x
>>>> Initializing Gumstix verdex pcmcia
>>>> Not netCF-vx board: pcmcia using newer GPIO configuration
>>>> CPLD responded with: ff
>>>> found 1 CF slots
>>>> Initializing Gumstix verdex FB info
>>>> Initializing Gumstix platform_add_devices
>>>> bio: create slab <bio-0> at 0
>>>> NET: Registered protocol family 2
>>>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>>>> TCP established hash table entries: 2048 (order: 2, 16384 bytes)
>>>> TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
>>>> TCP: Hash tables configured (established 2048 bind 2048)
>>>> TCP reno registered
>>>> NET: Registered protocol family 1
>>>> msgmni has been set to 121
>>>> alg: No test for stdrng (krng)
>>>> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
>>>> io scheduler noop registered
>>>> io scheduler cfq registered (default)
>>>> Console: switching to colour frame buffer device 80x24
>>>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
>>>> console [ttyS0] enabled
>>>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
>>>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
>>>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>>>> bankwidth)
>>>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>>>>  Intel/Sharp Extended Query Table at 0x010A
>>>>  Intel/Sharp Extended Query Table at 0x010A
>>>>  Intel/Sharp Extended Query Table at 0x010A
>>>>  Intel/Sharp Extended Query Table at 0x010A
>>>>  Intel/Sharp Extended Query Table at 0x010A
>>>> Using buffer write method
>>>> Using auto-unlock on power-up/resume
>>>> cfi_cmdset_0001: Erase suspend on write enabled
>>>> Using static partitions on Gumstix Flash ROM
>>>> Creating 3 MTD partitions on "Gumstix Flash ROM":
>>>> 0x000000000000-0x000000040000 : "Bootloader"
>>>> 0x000000040000-0x000000f00000 : "RootFS"
>>>> 0x000000f00000-0x000001000000 : "Kernel"
>>>> pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
>>>> TCP cubic registered
>>>> NET: Registered protocol family 17
>>>> XScale iWMMXt coprocessor detected.
>>>> pxa-rtc pxa-rtc: setting system clock to 2000-01-01 00:00:40 UTC
>>>> (946684840)
>>>> Waiting 1sec before mounting root device...
>>>> mmc0: host does not support reading read-only switch. assuming
>>>> write-enable.
>>>> mmc0: new SD card at address 1234
>>>> mmcblk0: mmc0:1234 SA02G 1.83 GiB
>>>>  mmcblk0: p1 p2
>>>> kjournald starting.  Commit interval 5 seconds
>>>> EXT3 FS on mmcblk0p2, internal journal
>>>> EXT3-fs: mounted filesystem with writeback data mode.
>>>> VFS: Mounted root (ext3 filesystem) on device 179:2.
>>>> Freeing init memory: 88K
>>>> INIT: version 2.86 booting
>>>> Please wait: booting...
>>>> Starting udev
>>>> I2C: i2c-0: PXA I2C adapter
>>>> I2C: i2c-1: PXA I2C adapter
>>>> tsc2003_probe
>>>> tsc2003 i2c touch screen controller
>>>> Bill Gatliff <bgat at billgatliff.com
>>>> Nicholas Chen <nchen at cs.umd.edu>
>>>> tsc2003_probe: checking i2c
>>>> tsc2003_probe: calling kzalloc
>>>> tsc2003_probe: probing address 0x48
>>>> i2c: error: exhausted retries
>>>> i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
>>>> i2c: ICR: 000087e0 ISR: 00000002
>>>> tsc2003: probe of 0-0048 failed with error -121
>>>> usbcore: registered new interface driver usbfs
>>>> usbcore: registered new interface driver hub
>>>> usbcore: registered new device driver usb
>>>> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
>>>> pxa27x-ohci pxa27x-ohci: PXA27x OHCI
>>>> pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1
>>>> pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
>>>> usb usb1: configuration #1 chosen from 1 choice
>>>> hub 1-0:1.0: USB hub found
>>>> hub 1-0:1.0: 3 ports detected
>>>> FAT: codepage cp437 not found
>>>> Remounting root file system...
>>>> Caching udev devnodes
>>>> Populating dev cache
>>>> logger: mount: mount point /dev/pts does not exist
>>>> logger: mount: mount point /dev/shm does not exist
>>>> Undefined users:
>>>>> pulse
>>>> Skipping /etc/default/volatiles/04_pulse
>>>> Undefined users:
>>>>> haldaemon
>>>> Skipping /etc/default/volatiles/99_hal
>>>> Starting Marvell Wifi CF8385...
>>>> Configuring network interfaces... eth0: unknown interface: No such
>>>> device
>>>> eth0: unknown interface: No such device
>>>> eth0      No such device
>>>>
>>>> eth0: unknown interface: No such device
>>>> done.
>>>> Starting portmap daemon: portmapportmap: fork: No such device.
>>>> Unknown HZ value! (68) Assume 100.
>>>> net.ipv4.conf.default.rp_filter = 1
>>>> net.ipv4.conf.all.rp_filter = 1
>>>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>>>> Mon Mar  1 11:18:00 UTC 2010
>>>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>>>> Checking for built-in Bluetooth: /etc/rcS.d/S97blueprobe: line 158:
>>>> can't
>>>> open /dev/ttyS1: no such file
>>>> yes
>>>> Configuring ppp-dialin
>>>> Configuring pulseaudio-server
>>>> addgroup: pulse: group already in use
>>>>
>>>> Undefined users:
>>>>> haldaemon
>>>> Skipping /etc/default/volatiles/99_hal
>>>> postinst script returned status 1
>>>> Configuring policykit
>>>> chmod: cannot access `/var/run/PolicyKit': No such file or directory
>>>> Configuring dbus
>>>>  System startup links for /etc/init.d/dbus-1 already exist.
>>>> Configuring hicolor-icon-theme
>>>> //usr/lib/opkg/info/hicolor-icon-theme.postinst: line 7: can't create
>>>> /etc/gtk-2.0/gdk-pixbuf.loaders: nonexistent directory
>>>> //usr/lib/opkg/info/hicolor-icon-theme.postinst: line 7:
>>>> gdk-pixbuf-query-loaders: not found
>>>> //usr/lib/opkg/info/hicolor-icon-theme.postinst: line 13:
>>>> gtk-update-icon-cache: not found
>>>> postinst script returned status 127
>>>> Configuring sudo
>>>> Configuring angstrom-zeroconf-audio
>>>> Configuring ppp
>>>> Configuring hal
>>>> Configuring avahi-autoipd
>>>> Configuring angstrom-libc-fixup-hack
>>>> Configuring avahi-daemon
>>>>  System startup links for /etc/init.d/avahi-daemon already exist.
>>>> Configuring ntpdate
>>>> adding crontab
>>>> Configuring update-modules
>>>> Configuring libnss-mdns
>>>> Bluetooth: Core ver 2.15
>>>> NET: Registered protocol family 31
>>>> Bluetooth: HCI device and connection manager initialized
>>>> Bluetooth: HCI socket layer initialized
>>>> Bluetooth: L2CAP ver 2.13
>>>> Bluetooth: L2CAP socket layer initialized
>>>> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>>>> Registering gumstix PCMCIA interface.
>>>> Bluetooth: RFCOMM TTY layer initialized
>>>> Bluetooth: RFCOMM socket layer initialized
>>>> Bluetooth: RFCOMM ver 1.11
>>>> smsc911x: Driver version 2008-10-21.
>>>> eth%d: smsc911x_init: Driver Parameters:
>>>> eth%d: smsc911x_init: LAN base: 0xC4A00000
>>>> eth%d: smsc911x_init: IRQ: 163
>>>> eth%d: smsc911x_init: PHY will be autodetected.
>>>> eth%d: smsc911x_init: BYTE_TEST: 0x87654321
>>>> eth%d: smsc911x_init: LAN911x identified, idrev: 0x01170002, generation:
>>>> 2
>>>> eth0: smsc911x_drv_probe: Network interface: "eth0"
>>>> eth0: smsc911x_phy_initialise_external: HW_CFG EXT_PHY_DET clear, using
>>>> internal PHY
>>>> smsc911x-mdio: probed
>>>> eth0: smsc911x_mii_probe: PHY 1: addr 1, phy_id 0x0007C0D1
>>>> eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01,
>>>> irq=-1)
>>>> eth0: smsc911x_phy_check_loopbackpkt: Successfully verified loopback
>>>> packet
>>>> eth0: smsc911x_mii_probe: Passed Loop Back Test
>>>> eth0: smsc911x_mii_probe: phy initialised succesfully
>>>> eth0: smsc911x_drv_probe: MAC Address is derived from system serial
>>>> number
>>>> net eth0: MAC Address: ae:f7:51:56:49:d0
>>>> Collected errors:
>>>>  * ERROR: pulseaudio-server.postinst returned 1
>>>>  * ERROR: hicolor-icon-theme.postinst returned 127
>>>> i2c /dev entries driver
>>>>
>>>>
>>>>
>>>>
>>>> Ash Charles-2 wrote:
>>>>>
>>>>> Hi mlq,
>>>>>
>>>>> Good catch...I've changed it to address a2000000 (feel free to correct
>>>>> my idiocy directly in the future ;-) ).
>>>>>
>>>>> There is no reason it shouldn't work on an old XM4--I believe the
>>>>> processor is the same between these boards.
>>>>>
>>>>> Perhaps you can try the kernel found here
>>>>> (http://dl.dropbox.com/u/211887/uimage) to see if that works for you?
>>>>>
>>>>> -Ash
>>>>> P.S. Sorry if this is a double-posting.
>>>>> On Tue, Mar 2, 2010 at 4:09 PM, mlq <mark.l.quilling@lmco.com> wrote:
>>>>>>
>>>>>> Sigh...
>>>>>>
>>>>>> I followed your instructions exactly and the boot sequnce freezes
>>>>>> after
>>>>>> uncompressing linux ........ It does load to correct kernel though.
>>>>>>
>>>>>> I think the step in the wiki "fatload mmc 0 a20000000 uimage" should
>>>>>> be
>>>>>> "fatload mmc 0 a2000000 uimage" (one less 0).
>>>>>>
>>>>>> Anyhow I have no idea why it is locking up, could it be because I have
>>>>>> an
>>>>>> old XM4 on not a verdex-pro?  I was really hoping that it would work
>>>>>> on
>>>>>> the
>>>>>> XM4.
>>>>>>
>>>>>> mlq
>>>>>>
>>>>>>
>>>>>> Ash Charles-2 wrote:
>>>>>>>
>>>>>>> Hi mlq,
>>>>>>>
>>>>>>> I have put together a documentation page on the user wiki:
>>>>>>> http://www.gumstix.net/wiki/index.php?title=Verdex_Git_Repository
>>>>>>>
>>>>>>> Note: MLO is an OMAP3 specific bootstrap loader.  It is not necessary
>>>>>>> for Verdex.
>>>>>>>
>>>>>>> Let me know if you have have any problems.
>>>>>>>
>>>>>>> -Ash
>>>>>>>
>>>>>>> On Mon, Mar 1, 2010 at 1:23 PM, mlq <mark.l.quilling@lmco.com> wrote:
>>>>>>>>
>>>>>>>> Hi Ash,
>>>>>>>>
>>>>>>>> I got everything built, thanks!  I am struggling getting the verdex
>>>>>>>> image
>>>>>>>> to
>>>>>>>> boot.  I tried using the MLO and u-boot that I use with the overo;
>>>>>>>> tried
>>>>>>>> to
>>>>>>>> rebuild them for the verdex (build failed); and I tried using the
>>>>>>>> old
>>>>>>>> gumstix-factory.script - nothing seems to work.  Should the
>>>>>>>> formatting
>>>>>>>> be
>>>>>>>> exactly the same as the overo?
>>>>>>>>
>>>>>>>> Could someone explain the steps I need to take to load the verdex
>>>>>>>> image
>>>>>>>> and
>>>>>>>> kernel on the microSD card and boot it?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> mlq
>>>>>>>>
>>>>>>>>
>>>>>>>> Ash Charles-2 wrote:
>>>>>>>>>
>>>>>>>>> Hey mlq,
>>>>>>>>>
>>>>>>>>> A 'bitbake virtual/kernel' should build the 2.6.31 kernel for
>>>>>>>>> verdex.
>>>>>>>>> Otherwise, the repository uses a 'task-base-gumstix' recipe to do
>>>>>>>>> most
>>>>>>>>> of the work for various other recipes in keeping with the old svn
>>>>>>>>> style.  Note this does not match the current OE style of just
>>>>>>>>> adding
>>>>>>>>> machine-specific stuff conditionally to the task-base recipe---I
>>>>>>>>> tried
>>>>>>>>> and couldn't get this to work properly so if anyone has a fix for
>>>>>>>>> this
>>>>>>>>> I'd love to see it :).
>>>>>>>>> The git repository currently provides four Verdex images (thanks
>>>>>>>>> Joseph):
>>>>>>>>> - verdex-console-image
>>>>>>>>> - verdex-palmtop-image
>>>>>>>>> - verdex-desktop-image
>>>>>>>>> - verdex-gnome-image
>>>>>>>>> I had some problems building the last two because of the problems
>>>>>>>>> reported on the branch with news & gnumeric etc. but I'm confident
>>>>>>>>> these will go away as bugs get fixed upstream.  I'd try the
>>>>>>>>> verdex-console-image for a start.
>>>>>>>>>
>>>>>>>>> For loading the code, essentially follow the instructions for Overo
>>>>>>>>> for booting from a microSD card.
>>>>>>>>>
>>>>>>>>> HTH,
>>>>>>>>>
>>>>>>>>> Ash
>>>>>>>>>
>>>>>>>>> P.S. If you do get those errors related to task-base, please post
>>>>>>>>> them
>>>>>>>>> so I can look through them.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Feb 27, 2010 at 11:10 AM, mlq <mark.l.quilling@lmco.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> I am also trying to build the verdex image and have sucessfully
>>>>>>>>>> built
>>>>>>>>>> the
>>>>>>>>>> minimal-image and kernel; however when I build the console image
>>>>>>>>>> i.e.
>>>>>>>>>> bitbake console-image it dies on building the task-base.
>>>>>>>>>>  Basically
>>>>>>>>>> it
>>>>>>>>>> is
>>>>>>>>>> looking in the task base folder but is missing the extensions for
>>>>>>>>>> the
>>>>>>>>>> particular tasks (task-base-x, missing x; sorry I dont have the
>>>>>>>>>> output
>>>>>>>>>> in
>>>>>>>>>> front of me).  I have 2 questions;
>>>>>>>>>>
>>>>>>>>>> What is the correct recipe to bitbake for the verdex? (i cant seem
>>>>>>>>>> to
>>>>>>>>>> find
>>>>>>>>>> any verdex-specific recipes in the repo)
>>>>>>>>>>
>>>>>>>>>> What procedure should we follow to flash the mmc? (I was able to
>>>>>>>>>> boot
>>>>>>>>>> using
>>>>>>>>>> the FAT16 partition and gumstix-factory.script from the old svn
>>>>>>>>>> repo
>>>>>>>>>> but
>>>>>>>>>> I
>>>>>>>>>> am not sure if we should be using a similar setup to the overo
>>>>>>>>>> with
>>>>>>>>>> xload?)
>>>>>>>>>>
>>>>>>>>>> Another related question which is not critical is when I add
>>>>>>>>>> recipes
>>>>>>>>>> to
>>>>>>>>>> user.collection/recipes bitbake does not see them - is there
>>>>>>>>>> typical
>>>>>>>>>> reason
>>>>>>>>>> for this?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> mlq
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Connie C wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Joseph,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for the help.  I'm definitely using the bash profile.
>>>>>>>>>>> Followed
>>>>>>>>>>> all
>>>>>>>>>>> those steps.  I also followed the second sequence of code to make
>>>>>>>>>>> the
>>>>>>>>>>> verdex-oe directory and I have the bitbake,build, and
>>>>>>>>>>> org.openembedded.dev
>>>>>>>>>>> directories inside.  I think everything looks okay up to there
>>>>>>>>>>> with
>>>>>>>>>>> what
>>>>>>>>>>> you posted.
>>>>>>>>>>>
>>>>>>>>>>> After removing my user.collection and com.gumstix.collection from
>>>>>>>>>>> the
>>>>>>>>>>> verdex-oe directory, I removed the extraneous tmp directory and
>>>>>>>>>>> ran
>>>>>>>>>>> bitbake verdex-console-image and got:
>>>>>>>>>>> ERROR: Nothing PROVIDES 'verdex-console-image' (but '[]' DEPENDS
>>>>>>>>>>> on
>>>>>>>>>>> or
>>>>>>>>>>> otherwise requires it)
>>>>>>>>>>>
>>>>>>>>>>> I had gotten this originally after I changed >>echo 0 >
>>>>>>>>>>> /proc/sys/vm/mmap_min_addr
>>>>>>>>>>> and was trying to access the .bb file directly as a result.
>>>>>>>>>>>
>>>>>>>>>>> Something with how my bitbake is set up?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Connie
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> bionicjoe wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi, I corrected one critical line below ...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ________________________________
>>>>>>>>>>>> From: Joseph Kortje <jpktech@rogers.com>
>>>>>>>>>>>> To: General mailing list for gumstix users.
>>>>>>>>>>>> <gumstix-users@lists.sourceforge.net>
>>>>>>>>>>>> Sent: Fri, February 26, 2010 9:12:35 PM
>>>>>>>>>>>> Subject: Re: [Gumstix-users]  Bitbaking New Kernel 2.6.31 for
>>>>>>>>>>>> Verdex
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Connie
>>>>>>>>>>>>
>>>>>>>>>>>> Most of what Ash checked in for verdex-oe came originally from
>>>>>>>>>>>> myself
>>>>>>>>>>>> and
>>>>>>>>>>>> a few others
>>>>>>>>>>>> so I can help you.
>>>>>>>>>>>>
>>>>>>>>>>>> It builds clean for me.
>>>>>>>>>>>>
>>>>>>>>>>>> So, lets' review ....
>>>>>>>>>>>>
>>>>>>>>>>>> What OS distribution are you building with?
>>>>>>>>>>>> If it's Ubuntu, please confirm that you did the instruction to
>>>>>>>>>>>> not
>>>>>>>>>>>> reconfigure bash as dash.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>First I installed all the files in the new directory
>>>>>>>>>>>>>>verdex-oe.
>>>>>>>>>>>>
>>>>>>>>>>>> These should be the steps to follow:
>>>>>>>>>>>>
>>>>>>>>>>>> $ mkdir -p ~/verdex-oe
>>>>>>>>>>>> $ cd ~/verdex-oe
>>>>>>>>>>>> $ git clone git://gitorious.org/gumstix-oe/mainline.git
>>>>>>>>>>>> org.openembedded.dev
>>>>>>>>>>>> $ cd org.openembedded.dev
>>>>>>>>>>>> $ git checkout --track -b verdex origin/verdex
>>>>>>>>>>>> $ cd ~/verdex-oe
>>>>>>>>>>>> $ git clone git://git.openembedded.net/bitbake bitbake
>>>>>>>>>>>> $ cd bitbake
>>>>>>>>>>>> $ git checkout 1.8.18
>>>>>>>>>>>> $ cd ~/verdex-oe
>>>>>>>>>>>> $ cp -r org.openembedded.dev/contrib/gumstix/build .
>>>>>>>>>>>>
>>>>>>>>>>>>>>sudo -i
>>>>>>>>>>>>>>echo 0 > /proc/sys/vm/mmap_min_addr
>>>>>>>>>>>>
>>>>>>>>>>>> Yes, that should work.
>>>>>>>>>>>>
>>>>>>>>>>>> Alternatively, you could edit /etc/sysctl.conf (For example sudo
>>>>>>>>>>>> gedit
>>>>>>>>>>>> /etc.sysctl.conf&)
>>>>>>>>>>>> and add the line
>>>>>>>>>>>>
>>>>>>>>>>>> vm.mmap_min_addr = 0
>>>>>>>>>>>>
>>>>>>>>>>>> (Save and then reboot).
>>>>>>>>>>>>
>>>>>>>>>>>>>> First the bitbake complained that it could not find user
>>>>>>>>>>>>>>collection in verdex-oe, so I copied user.collection and
>>>>>>>>>>>>>>com.gumstix.collection over into the directory.
>>>>>>>>>>>>
>>>>>>>>>>>> There is no requirement to copy over user.collection from th
>>>>>>>>>>>> older
>>>>>>>>>>>> gumstix-oe build environment path.
>>>>>>>>>>>> The purpose of user.collection is to override the search path
>>>>>>>>>>>> for
>>>>>>>>>>>> bitbake
>>>>>>>>>>>> recipes.  If any bitbake recipes
>>>>>>>>>>>> in the user.collection path have the same base name as the ones
>>>>>>>>>>>> used
>>>>>>>>>>>> in
>>>>>>>>>>>> org.openembedded.dev then they would be used
>>>>>>>>>>>> in place of the official ones.  Unless the developer has a
>>>>>>>>>>>> specific
>>>>>>>>>>>> reason for adding an override or customization
>>>>>>>>>>>> or new bitbake recipe, and understands what he/she is doing with
>>>>>>>>>>>> it
>>>>>>>>>>>> (and
>>>>>>>>>>>> the consequences)
>>>>>>>>>>>> I suggest not putting anything in user.collection folder (or
>>>>>>>>>>>> don't
>>>>>>>>>>>> use
>>>>>>>>>>>> the folder at all).
>>>>>>>>>>>>
>>>>>>>>>>>> Any old user.collection recipes that were used in the old
>>>>>>>>>>>> gumstix-oe
>>>>>>>>>>>> SVN
>>>>>>>>>>>> based projects will not necessarily be compatible
>>>>>>>>>>>> with the newer verdex-oe stuff since we are using a newer
>>>>>>>>>>>> Angstrom
>>>>>>>>>>>> distribution, newer Kernel, newer bitbake,
>>>>>>>>>>>> etc.  Developers that have such recipes would need to revisit
>>>>>>>>>>>> them
>>>>>>>>>>>> to
>>>>>>>>>>>> port them to the new code base.
>>>>>>>>>>>>
>>>>>>>>>>>> The warning about not finding user.collection can therefore
>>>>>>>>>>>> simply
>>>>>>>>>>>> be
>>>>>>>>>>>> ignored since you are (presumably)
>>>>>>>>>>>> not going to be wanting to override any of the standard bitbake
>>>>>>>>>>>> recipes
>>>>>>>>>>>> or add any of your own
>>>>>>>>>>>> customized ones yet.
>>>>>>>>>>>>
>>>>>>>>>>>> The old "com.gumstix.collection" and any files in that folder
>>>>>>>>>>>> should
>>>>>>>>>>>> not
>>>>>>>>>>>> be added to this path and
>>>>>>>>>>>> is not supported anymore in the Git based OE architecture.  Any
>>>>>>>>>>>> of
>>>>>>>>>>>> the
>>>>>>>>>>>> relevant patches or recipes (previously called packages)
>>>>>>>>>>>> from the previous com.gumstix.collection are now already
>>>>>>>>>>>> integrated
>>>>>>>>>>>> into
>>>>>>>>>>>> the git based verdex branch org.openembedded.dev recipes.
>>>>>>>>>>>>
>>>>>>>>>>>> (There are some exceptions such as support for audio, and
>>>>>>>>>>>> robostix
>>>>>>>>>>>> which
>>>>>>>>>>>> are currently not ported to the new verdex-oe branch.  Still
>>>>>>>>>>>> working
>>>>>>>>>>>> on it ....).
>>>>>>>>>>>>
>>>>>>>>>>>> Here is how to fix your build environment:
>>>>>>>>>>>>
>>>>>>>>>>>> First, you need to clean out the incorrect files that were added
>>>>>>>>>>>> to
>>>>>>>>>>>> the
>>>>>>>>>>>> build path ....
>>>>>>>>>>>>
>>>>>>>>>>>> cd ~/verdex-oe
>>>>>>>>>>>> sudo rm -rf com.gumstix.collection
>>>>>>>>>>>> sudo rm -rf user.collection
>>>>>>>>>>>>
>>>>>>>>>>>> In this case, since the build cache is probably messed up, we
>>>>>>>>>>>> need
>>>>>>>>>>>> to
>>>>>>>>>>>> start with a clean build
>>>>>>>>>>>>
>>>>>>>>>>>> sudo rm -rf tmp
>>>>>>>>>>>> bitbake verdex-console-image
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Note: Please don't add ".bb" to the end of the bitbake recipe
>>>>>>>>>>>> names
>>>>>>>>>>>> in
>>>>>>>>>>>> the bitbake command.
>>>>>>>>>>>> Also, you can omit the -b option.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> BTW, please make sure that you have plenty of space in your
>>>>>>>>>>>> /home
>>>>>>>>>>>> partition.
>>>>>>>>>>>> I use a 300GB partition albeit building for several projects for
>>>>>>>>>>>> OpenEmbedded and I still find that
>>>>>>>>>>>> my space gets eaten up really fast ...
>>>>>>>>>>>>
>>>>>>>>>>>> I recommend at least 40-60GB is needed to build verdex-oe (both
>>>>>>>>>>>> verdex-console-image and verdex-palmtop-image).
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Let me know your results ...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>> Joseph
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> PS: Tip for building faster on dual or quad core cpu ....
>>>>>>>>>>>>
>>>>>>>>>>>> In
>>>>>>>>>>>>  ~/verdex-oe/build/conf/site.conf
>>>>>>>>>>>>
>>>>>>>>>>>> # Uncomment these lines to enable parallel make.
>>>>>>>>>>>> # This allows make to spawn mutliple processes to take advantage
>>>>>>>>>>>> of
>>>>>>>>>>>> multiple
>>>>>>>>>>>> # processors. Useful on SMP machines
>>>>>>>>>>>> PARALLEL_MAKE = "-j 4"
>>>>>>>>>>>> BB_NUMBER_THREADS = "4"
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> View this message in context:
>>>>>>>>>>
>>>>>>>>>> http://old.nabble.com/Bitbaking-New-Kernel-2.6.31-for-Verdex-tp27722745p27730217.html
>>>>>>>>>> Sent from the Gumstix mailing list archive at Nabble.com.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>>>>> Try the new software tools for yourself. Speed compiling, find
>>>>>>>>>> bugs
>>>>>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>>>>> _______________________________________________
>>>>>>>>>> gumstix-users mailing list
>>>>>>>>>> gumstix-users@lists.sourceforge.net
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>>>> _______________________________________________
>>>>>>>>> gumstix-users mailing list
>>>>>>>>> gumstix-users@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> View this message in context:
>>>>>>>>
>>>>>>>> http://old.nabble.com/Bitbaking-New-Kernel-2.6.31-for-Verdex-tp27722745p27749237.html
>>>>>>>> Sent from the Gumstix mailing list archive at Nabble.com.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>>> _______________________________________________
>>>>>>>> gumstix-users mailing list
>>>>>>>> gumstix-users@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>> _______________________________________________
>>>>>>> gumstix-users mailing list
>>>>>>> gumstix-users@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>>>>> http://old.nabble.com/Bitbaking-New-Kernel-2.6.31-for-Verdex-tp27722745p27762956.html
>>>>>> Sent from the Gumstix mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download Intel® Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> gumstix-users mailing list
>>>>>> gumstix-users@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> gumstix-users mailing list
>>>>> gumstix-users@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>>>> http://old.nabble.com/Bitbaking-New-Kernel-2.6.31-for-Verdex-tp27722745p27771565.html
>>>> Sent from the Gumstix mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> gumstix-users mailing list
>>>> gumstix-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> gumstix-users mailing list
>>> gumstix-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Bitbaking-New-Kernel-2.6.31-for-Verdex-tp27722745p27772645.html
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users