Philip,<br><br>> Can you try with the kernel created by OE?<br><br>So to do that, in gumstix.conf would I replace:<br><br>PREFERRED_PROVIDER_virtual/kernel = "linux-gumstix"<br><br>with<br><br>PREFERRED_PROVIDER_virtual/kernel = "linux"
<br><br>Steve<br><br><div><span class="gmail_quote">On 8/17/07, <b class="gmail_sendername">Philip Balister</b> <<a href="mailto:philip@balister.org">philip@balister.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Can you try with the kernel created by OE? It is also a 2.6.15 kernel,<br>but maybe the kernel config is updated.<br><br>Philip<br><br>Steve Sakoman wrote:<br>> Philip,<br>><br>> Thanks for your help! That yielded a bootable image and gets me to a login
<br>> prompt. See below for the boot messages.<br>><br>> A good start, but still some issues to resolve -- udevd for example, perhaps<br>> a mismatch with the gumstix kernel revision?<br>><br>><br>> Steve
<br>><br>> Instruction Cache is ON<br>> ### JFFS2 loading 'boot/uImage' to 0xa2000000<br>> Scanning JFFS2 FS: ........ done.<br>> ### JFFS2 load complete: 749692 bytes loaded to 0xa2000000<br>> ## Booting image at a2000000 ...
<br>> Image Name: Linux-2.6.15gum<br>> Image Type: ARM Linux Kernel Image (uncompressed)<br>> Data Size: 749628 Bytes = 732.1 kB<br>> Load Address: a0008000<br>> Entry Point: a0008000
<br>> OK<br>><br>> Starting kernel ...<br>><br>> Linux version 2.6.15gum (sakoman@tera) (gcc version 4.1.1) #1 Fri Aug 17<br>> 08:25:11 PDT 2007<br>> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE)
<br>> Machine: The Gumstix Platform<br>> Memory policy: ECC disabled, Data cache writeback<br>> Memory clock: 99.53MHz (*27)<br>> Run Mode clock: 199.07MHz (*2)<br>> Turbo Mode clock: 199.07MHz (*1.0, inactive)
<br>> CPU0: D VIVT undefined 5 cache<br>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets<br>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets<br>> Built 1 zonelists<br>
> Kernel command line: console=ttyS0,115200n8 root=1f01 rootfstype=jffs2<br>> reboot=cold,hard<br>> PID hash table entries: 512 (order: 9, 8192 bytes)<br>> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<br>> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)<br>> Memory: 64MB = 64MB total<br>> Memory: 63256KB available (1249K code, 245K data, 56K init)<br>> Mount-cache hash table entries: 512<br>> CPU: Testing write buffer coherency: ok
<br>> NET: Registered protocol family 16<br>> JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.<br>> Initializing Cryptographic API<br>> io scheduler noop registered<br>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART
<br>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART<br>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART<br>> pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART<br>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth)
<br>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank<br>> Intel/Sharp Extended Query Table at 0x0031<br>> Using buffer write method<br>> cfi_cmdset_0001: Erase suspend on write enabled<br>> Using static partitions on Gumstix Flash ROM
<br>> Creating 2 MTD partitions on "Gumstix Flash ROM":<br>> 0x00000000-0x00040000 : "Bootloader"<br>> 0x00040000-0x01000000 : "RootFS"<br>> NET: Registered protocol family 2<br>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<br>> TCP established hash table entries: 4096 (order: 2, 16384 bytes)<br>> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)<br>> TCP: Hash tables configured (established 4096 bind 4096)<br>> TCP reno registered
<br>> TCP bic registered<br>> NET: Registered protocol family 1<br>> NET: Registered protocol family 17<br>> VFS: Mounted root (jffs2 filesystem).<br>> Freeing init memory: 56K<br>> Starting the hotplug events dispatcher udevd
<br>> Jan 1 00:19:50 udevd[78]: main: the kernel does not support inotify, udevd<br>> can't monitor configuration file changes<br>> Synthesizing the initial hotplug events<br>> modprobe: could not parse modules.dep
<br>> modprobe: could not parse modules.dep<br>> modprobe: could not parse modules.dep<br>> Waiting for /dev to be fully populated<br>> Remounting root file system...<br>> mount: Mounting proc on /proc failed: Device or resource busy
<br>> root: mount: Mounting rootfs on / failed: No such device<br>> root: mount: Mounting usbfs on /proc/bus/usb failed: No such file or<br>> directory<br>> Setting up IP spoofing protection: rp_filter.<br>> Configuring network interfaces... done.
<br>> hwclock: Could not access RTC: No such file or directory<br>> Starting Dropbear SSH server: Will output 1024 bit rsa secret key to<br>> '/etc/dropbear/dropbear_rsa_host_key'<br>> Generating key, this may take a while...
<br>> Public key portion is:<br>> ssh-rsa<br>> AAAAB3NzaC1yc2EAAAADAQABAAAAgwCQiHAfZOhoI+uL7Q1s62SVyuJMcwKMk0hoFJ/nNKOi7XO9mC8MOOmOOBVrypkr80XpgCvH29ykM3Zyk1O3XU6Tx1+8VCXnODdzp4upeePQYkV+X5BZgN7XYC+yyBxBCYTDGwapBpvYaVRu3cr1LFenapsXXMFMJPsDVZox0croXPvr
<br>> root@gumstix<br>> Fingerprint: md5 3a:38:71:21:ef:00:48:ba:c1:80:b9:cf:39:04:5a:5d<br>> dropbear.<br>> Starting syslogd/klogd: done<br>><br>> OpenEmbedded Linux gumstix ttyS0<br>><br>> gumstix 1 gumstix ttyS0
<br>><br>> gumstix login: root<br>> root@gumstix:~$<br>><br>><br>> On 8/17/07, Philip Balister <<a href="mailto:philip@balister.org">philip@balister.org</a>> wrote:<br>>> bitbake angstrom-minimal-image
<br>>><br>>> or for a few more features<br>>><br>>> bitbake angstrom-console-image<br>>><br>>> the tasks are an intermediate product, normally we do not build them<br>>> directly.
<br>>><br>>> Philip<br>>><br>>> Steve Sakoman wrote:<br>>>> Philip,<br>>>><br>>>> I don't have that directory after the build. Only tmp/deploy/ipk<br>>> exists.
<br>>>> Should doing a "bitbake task-boot" create the image? I wanted to start<br>>> out<br>>>> with something minimal, but perhaps that is too minimal!<br>>>><br>>>> Steve
<br>>>><br>>>> On 8/17/07, Philip Balister <<a href="mailto:philip@balister.org">philip@balister.org</a>> wrote:<br>>>>> There should be something that look like this:<br>>>>>
<br>>>>> tmp/deploy/glibc/images/efika<br>>>>><br>>>>> probably gumstix instead of Efika.<br>>>>><br>>>>> Philip<br>>>>><br>>>>> Steve Sakoman wrote:
<br>>>>>> That's where I looked initially, but my tmp/deploy directory only has<br>>> an<br>>>>> ipk<br>>>>>> subdirectory. No likely candidates there!<br>>>>>>
<br>>>>>> Steve<br>>>>>><br>>>>>> On 8/17/07, Hans Henry von Tresckow <<a href="mailto:hvontres@gmail.com">hvontres@gmail.com</a>> wrote:<br>>>>>>> try looking in the tmp/deploy folder in your build directory. for my
<br>>>>> glibc<br>>>>>>> builds for poodle they are in tmp/deploy/glibc/images/poodle<br>>>>>>><br>>>>>>> On 8/17/07, Steve Sakoman <<a href="mailto:sakoman@gmail.com">
sakoman@gmail.com</a>> wrote:<br>>>>>>>> Hmmm . . . another newbie question!<br>>>>>>>><br>>>>>>>> Where does the rootfs image get placed at the end of the
<br>>> build? Can't<br>>>>>>>> seem to find it.<br>>>>>>>><br>>>>>>>> I'm assuming that the following line in the machine conf file is<br>>> what
<br>>>>>>>> builds it:<br>>>>>>>><br>>>>>>>> EXTRA_IMAGECMD_jffs2 = "--little-endian --eraseblock=0x20000<br>>> --squash"<br>>>>>>>> Thanks!
<br>>>>>>>><br>>>>>>>> Steve<br>>>>>>>><br>>>>>>>> On 8/17/07, Philip Balister < <a href="mailto:philip@balister.org">philip@balister.org
</a>> wrote:<br>>>>>>>>> Try again. Thanks for your patience.<br>>>>>>>>><br>>>>>>>>> Philip<br>>>>>>>>><br>>>>>>>>> Steve Sakoman wrote:
<br>>>>>>>>>> Philip,<br>>>>>>>>>><br>>>>>>>>>> No joy on the build:<br>>>>>>>>>><br>>>>>>>>>> Connecting to
prdownloads.sourceforge.net|66.35.250.217|:80...<br>>>>>>>>> connected.<br>>>>>>>>>> HTTP request sent, awaiting response... 301 Moved Permanently<br>>>>>>>>>> Location:
<br>>>>>>>>>><br>>> <a href="http://downloads.sourceforge.net/u-boot/u-boot-1.2.0.tar.bz2?download&failedmirror=superb-east.dl.sourceforge.net[following]">http://downloads.sourceforge.net/u-boot/u-boot-1.2.0.tar.bz2?download&failedmirror=superb-east.dl.sourceforge.net[following]
</a><br>>>>>>>>> <<br>>> <a href="http://downloads.sourceforge.net/u-boot/u-boot-1.2.0.tar.bz2?download&failedmirror=superb-east.dl.sourceforge.net%5Bfollowing%5D">http://downloads.sourceforge.net/u-boot/u-boot-1.2.0.tar.bz2?download&failedmirror=superb-east.dl.sourceforge.net%5Bfollowing%5D
</a><br>>>>>>>>>> 20 redirections exceeded.<br>>>>>>>>>> NOTE: Task failed: Fetch failed:<br>>>>>>>>>> <a href="http://downloads.sourceforge.net/u-boot/u-boot-1.2.0.tar.bz2">
http://downloads.sourceforge.net/u-boot/u-boot-1.2.0.tar.bz2</a><br>>>>>>>>>> NOTE: package uboot-utils-1.2.0-r6: task do_fetch: failed<br>>>>>>>>>><br>>>>>>>>>> According to SourceForce the source for u-boot seems to have
<br>>> moved:<br>>>>>>>>>> The "U-Boot" Universal Bootloader project provides firmware for<br>>> many<br>>>>>>>>> CPU<br>>>>>>>>>> architectures and boards with full source code under GPL. NOTE:
<br>>>>>>>>> current<br>>>>>>>>>> source code is available from DENX git repository and FTP server;<br>>>>>>>>> see<br>>>>>>>>>>
<a href="http://www.denx.de/en/Software/GIT">http://www.denx.de/en/Software/GIT</a><br>>>>>>>>>><br>>>>>>>>>> Steve<br>>>>>>>>>><br>>>>>>>>>> On 8/16/07, Steve Sakoman <
<a href="mailto:sakoman@gmail.com">sakoman@gmail.com</a>> wrote:<br>>>>>>>>>>> Philip,<br>>>>>>>>>>><br>>>>>>>>>>> Thanks! Just did the pull and update.
<br>>>>>>>>>>><br>>>>>>>>>>> Build is underway . . .<br>>>>>>>>>>><br>>>>>>>>>>> Steve<br>>>>>>>>>>>
<br>>>>>>>>>>> On 8/16/07, Philip Balister < <a href="mailto:philip@balister.org">philip@balister.org</a>> wrote:<br>>>>>>>>>>>> OK, if you pull and update, you should be able to build a
<br>>> complete<br>>>>>>>>> image<br>>>>>>>>>>>> for the gumstix. I fixed uboot-utils so it compiles mkimage, and<br>>>>>>>>> added<br>
>>>>>>>>>>> uboot-utils as a dependency to the linux-gumstix bb file.<br>>>>>>>>>>>><br>>>>>>>>>>>> Philip<br>>>>>>>>>>>>
<br>>>>>>>>>>>> Steve Sakoman wrote:<br>>>>>>>>>>>>> Koen,<br>>>>>>>>>>>>><br>>>>>>>>>>>>> Thanks for your response. I'm an Open Embedded beginner, so
<br>>> I'm<br>>>>>>>>> not<br>>>>>>>>>>>> quite<br>>>>>>>>>>>>> sure what to do with your suggestion :-)<br>>>>>>>>>>>>>
<br>>>>>>>>>>>>> Should the "DEPENDS" statement be added to the gumstix machine<br>>>>>>>>>>>> definition?<br>>>>>>>>>>>>> Steve
<br>>>>>>>>>>>>><br>>>>>>>>>>>>> On 8/15/07, Koen Kooi < <a href="mailto:koen@dominion.kabel.utwente.nl">koen@dominion.kabel.utwente.nl</a>> wrote:
<br>>>>>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----<br>>>>>>>>>>>>>> Hash: SHA1<br>>>>>>>>>>>>>><br>>>>>>>>>>>>>> Philip Balister schreef:
<br>>>>>>>>>>>>>>> I can confirm this is a problem building Angstrom for a<br>>> gumstix<br>>>>>>>>> with<br>>>>>>>>>>>> a
<br>>>>>>>>>>>>>>> clean tmp directory. I think the problem is that the kernel<br>>>>>>>>> build<br>>>>>>>>>>>> needs<br>>>>>>>>>>>>>>> mkiamge from u-boot, but the gumstix machine does not build
<br>>>>>>>>> u-boot.<br>>>>>>>>>>>> I<br>>>>>>>>>>>>>>> tried building u-bbot for the gumstix, but u-boot contains no<br>>>>>>>>> config
<br>>>>>>>>>>>> for<br>>>>>>>>>>>>>>> the hardware. Then I tried building uboot-utils and that<br>>> failed<br>>>>>>>>>>>> trying
<br>>>>>>>>>>>>>>> to unpack :<br>>>>>>>>>>>>>>><br>>>>>>>>>>>>>>> org.openembedded.dev /packages/uboot/files/fw_env.config': No
<br>>>>>>>>> such<br>>>>>>>>>>>> file<br>>>>>>>>>>>>>>> or directory<br>>>>>>>>>>>>>>>
<br>>>>>>>>>>>>>>> Any thoughts?<br>>>>>>>>>>>>>> Yes, DEPENDS = "u-boot-mkimage-openmoko-native" for a<br>>> 'generic'
<br>>>>>>>>>>>> mkimage in<br>>>>>>>>>>>>>> STAGING_BINDIR_NATIVE.<br>>>>>>>>>>>>>><br>>>>>>>>>>>>>> regards,
<br>>>>>>>>>>>>>><br>>>>>>>>>>>>>> Koen<br>>>>>>>>>>>>>> -----BEGIN PGP SIGNATURE-----<br>>>>>>>>>>>>>> Version: GnuPG
v1.4.5 (Darwin)<br>>>>>>>>>>>>>><br>>>>>>>>>>>>>><br>>> iD8DBQFGw3UKMkyGM64RGpERAg0wAJ9W1ey+p1fJ9BCj1kngeOTvlSSYKQCgu4kQ<br>>>>>>>>>>>>>> 7e3DquN5wj+Ac/xPMtRmPSE=
<br>>>>>>>>>>>>>> =npCT<br>>>>>>>>>>>>>> -----END PGP SIGNATURE-----<br>>>>>>>>>>>>>><br>>>>>>>>>>>>>> _______________________________________________
<br>>>>>>>>>>>>>> Openembedded-users mailing list<br>>>>>>>>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org
</a><br>>>>>>>>>>>>>><br>>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
</a><br>>>>><br>>> ------------------------------------------------------------------------<br>>>>>>>>>>>>> _______________________________________________<br>>>>>>>>>>>>> Openembedded-users mailing list
<br>>>>>>>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>>>>>>>>>>><br>>>>>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>>>>>>>>>> _______________________________________________
<br>>>>>>>>>>>> Openembedded-users mailing list<br>>>>>>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org
</a><br>>>>>>>>>>>><br>>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
</a><br>>> ------------------------------------------------------------------------<br>>>>>>>>>> _______________________________________________<br>>>>>>>>>> Openembedded-users mailing list
<br>>>>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>>>>>>>><br>>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>>>>>>> _______________________________________________<br>>>>>>>>> Openembedded-users mailing list
<br>>>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>>>>>>><br>>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>>>>>>><br>>>>>>>> _______________________________________________<br>>>>>>>> Openembedded-users mailing list
<br>>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>>>>>><br>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>>>>>><br>>>>>>> _______________________________________________<br>>>>>>> Openembedded-users mailing list
<br>>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>>>>><br>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>>>>><br>>>>>><br>>> ------------------------------------------------------------------------<br>>>>>> _______________________________________________
<br>>>>>> Openembedded-users mailing list<br>>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>>> _______________________________________________<br>>>>> Openembedded-users mailing list<br>>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">
Openembedded-users@lists.openembedded.org</a><br>>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a>
<br>>>>><br>>>>><br>>>>><br>>>><br>>>> ------------------------------------------------------------------------<br>>>><br>>>> _______________________________________________
<br>>>> Openembedded-users mailing list<br>>>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>> _______________________________________________<br>>> Openembedded-users mailing list<br>>> <a href="mailto:Openembedded-users@lists.openembedded.org">
Openembedded-users@lists.openembedded.org</a><br>>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br>>>
<br>>><br>>><br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> Openembedded-users mailing list
<br>> <a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br>> <a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
</a><br><br>_______________________________________________<br>Openembedded-users mailing list<br><a href="mailto:Openembedded-users@lists.openembedded.org">Openembedded-users@lists.openembedded.org</a><br><a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users">
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</a><br><br><br></blockquote></div><br>