From: Michael K. <mfk...@gm...> - 2007-09-05 16:29:47
|
On 9/5/07, Paul Faulstich, SEnnovation <pa...@se...> wrote: > Thanks for the detailed response. I hadn't realized that it was the > shell on the build box that was causing the problem! (and now that you > point it out, I see it in the wiki.) > > setting sh to bash on the build box is certainly easy enough. Just did > it, and will check on the compile when I get home from work.... :) You'll also need to be sure and change it back when/if you upgrade your build system. I decided to simply fix the makefiles so they use '/bin/echo' rather than the shell built-in (I'm not sure '-e' is part of the "Bourne Shell standard" anyway). The patch is attached if anyone else is interested. --Mike > > Thanks! > > Paul > > On 9/4/2007 11:13 PM, Chris McClenaghan wrote: > > Paul, > > > > The problem that dash causes is during the build - but not of busybox, > > but of various configuration files generated by make using /bin/sh. > > Ubuntu has /bin/sh linked to dash. Dash and echo don't get along. If you > > have root priviliges, you can simply relink /bin/sh to /bin/bash. On > > your Ubuntu system if you are up to it and understand the following: > > > > cd /bin > > sudo rm sh > > sudo ln -s bash sh > > > > I haven't looked at the make file close enough, but setting SHELL to > > /bin/bash in your environment doesn't work. > > > > I'd leave busybox alone - I suspect that the various aliases (ash, lash, > > etc) link to the same code (anyone know)? > > > > So how did it happen - rebuilding the root fs in Ubuntu? Somewhere in > > the wiki this problem is documented, I can remember reading it. > > > > If you are wondering why I'm replying, I did the same thing and spent > > waited 4.5 hours to transfer a mangled root fs. Clean build underway and > > an overnight transfer coming. > > > > Good luck, > > > > Chris > > > > Paul Faulstich, SEnnovation wrote: > > > >> okay, so how do I fix it? I see that in the busybox config > >> (package/busybox/busybox.config) I can set the shell to ash, hush, lash, > >> msh or none. Do I want one of these, and if so, which? Or, can I set > >> one of the Ash shell options to make it sh-compliant? Or, is there > >> something completely different I should be doing? (maybe > >> CONFIG_FEATURE_SH_STANDALONE_SHELL?) I haven't found documentation for > >> all the settings on the busybox website yet, so I'm a bit lost. > >> > >> And I'm still puzzled how it happened in the first place, since I > >> thought that the gumstix shipped with the default build, and the > >> ethernet worked before I dropped the new boot image in place. > >> > >> Thanks - Paul > >> > >> On 9/4/2007 10:03 PM, Chris McClenaghan wrote: > >> > >> > >>> Paul, > >>> > >>> Busybox is runtime. The dash and the link to /bin/sh is a build time > >>> issue. You may be able to hand edit all the offending files, but a > >>> rebuild with be the safest way to ensure all is okay. > >>> > >>> Chris > >>> > >>> > >>> Paul Faulstich, SEnnovation wrote: > >>> > >>> > >>> > >>>> Thanks. I have a few followup questions: > >>>> > >>>> 1. How do I fix the problem? Do I need to do a new buildroot? If so, > >>>> what do I need to set in the config to get the right shell? (btw, > >>>> /bin/sh is linked to busybox. Is busybox dash based?) I tried fixing > >>>> the problem by rm'ing /bin/sh and soft linking /bin/sh to /bin/ash, but > >>>> that didn't work. Of course - now that I look - ash just links to > >>>> busybox too. > >>>> > >>>> 2. How did the problem happen? in the first place? Is it something set > >>>> in the buildroot by default? I followed the buildroot instructions on > >>>> the website - I first ran make defconfig, then make, then make > >>>> menuconfig to select the 2 packages I wanted to add. > >>>> > >>>> Thanks, > >>>> > >>>> Paul > >>>> > >>>> > >>>> On 9/4/2007 8:15 PM, Craig Hughes wrote: > >>>> > >>>> > >>>> > >>>> > >>>>> You have /bin/sh linked to dash, which is not sh-compliant in that it > >>>>> doesn't grok the -e flag to the echo command. > >>>>> > >>>>> C > >>>>> > >>>>> On Sep 4, 2007, at 4:00 PM, Paul Faulstich, SEnnovation wrote: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> I'm having problems with the new jffs2 file that I just built and > >>>>>> installed for my connex 400xm (netMMC pack) - my ethernet no longer > >>>>>> works! It looks like maybe there is a problem with the /etc/ > >>>>>> modprobe.conf file? Any advice is much appreciated! TIA - Paul > >>>>>> > >>>>>> Here is the uboot output. A ways down you'll see the modprobe > >>>>>> warnings. > >>>>>> U-Boot 1.1.4 (Nov 6 2006 - 11:20:03) - 400 MHz - 1161 > >>>>>> > >>>>>> *** Welcome to Gumstix *** > >>>>>> > >>>>>> U-Boot code: A3F00000 -> A3F25DE4 BSS: -> A3F5AF00 > >>>>>> RAM Configuration: > >>>>>> Bank #0: a0000000 64 MB > >>>>>> Flash: 16 MB > >>>>>> Using default environment > >>>>>> > >>>>>> SMC91C1111-0 > >>>>>> Net: SMC91C1111-0 > >>>>>> Hit any key to stop autoboot: 0 > >>>>>> Instruction Cache is ON > >>>>>> ### JFFS2 loading 'boot/uImage' to 0xa2000000 > >>>>>> Scanning JFFS2 FS: .................. done. > >>>>>> ### JFFS2 load complete: 763192 bytes loaded to 0xa2000000 > >>>>>> ## Booting image at a2000000 ... > >>>>>> Image Name: uImage > >>>>>> Image Type: ARM Linux Kernel Image (uncompressed) > >>>>>> Data Size: 763128 Bytes = 745.2 kB > >>>>>> Load Address: a0008000 > >>>>>> Entry Point: a0008000 > >>>>>> OK > >>>>>> > >>>>>> Starting kernel ... > >>>>>> > >>>>>> Linux version 2.6.18gum (paul@dell) (gcc version 3.4.5) #1 Mon Sep > >>>>>> 3 12:00:13 EDT 2007 > >>>>>> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f > >>>>>> Machine: The Gumstix Platform > >>>>>> Memory policy: ECC disabled, Data cache writeback > >>>>>> Memory clock: 99.53MHz (*27) > >>>>>> Run Mode clock: 398.13MHz (*4) > >>>>>> Turbo Mode clock: 398.13MHz (*1.0, inactive) > >>>>>> CPU0: D VIVT undefined 5 cache > >>>>>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets > >>>>>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets > >>>>>> Built 1 zonelists. Total pages: 16384 > >>>>>> Kernel command line: console=ttyS0,115200n8 root=1f01 > >>>>>> rootfstype=jffs2 reboot=cold,hard > >>>>>> PID hash table entries: 512 (order: 9, 2048 bytes) > >>>>>> start_kernel(): bug: interrupts were enabled early > >>>>>> 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: 63360KB available (1248K code, 250K data, 60K init) > >>>>>> Mount-cache hash table entries: 512 > >>>>>> CPU: Testing write buffer coherency: ok > >>>>>> NET: Registered protocol family 16 > >>>>>> NET: Registered protocol family 2 > >>>>>> IP route cache hash table entries: 512 (order: -1, 2048 bytes) > >>>>>> TCP established hash table entries: 2048 (order: 1, 8192 bytes) > >>>>>> TCP bind hash table entries: 1024 (order: 0, 4096 bytes) > >>>>>> TCP: Hash tables configured (established 2048 bind 1024) > >>>>>> TCP reno registered > >>>>>> JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. > >>>>>> Initializing Cryptographic API > >>>>>> io scheduler noop registered (default) > >>>>>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART > >>>>>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART > >>>>>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART > >>>>>> pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART > >>>>>> 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 0x0031 > >>>>>> Using buffer write method > >>>>>> cfi_cmdset_0001: Erase suspend on write enabled > >>>>>> Using static partitions on Gumstix Flash ROM > >>>>>> Creating 2 MTD partitions on "Gumstix Flash ROM": > >>>>>> 0x00000000-0x00040000 : "Bootloader" > >>>>>> 0x00040000-0x01000000 : "RootFS" > >>>>>> TCP bic registered > >>>>>> VFS: Mounted root (jffs2 filesystem). > >>>>>> Freeing init memory: 60K > >>>>>> request_module: runaway loop modprobe net-pf-1 > >>>>>> Dec 31 16:00:14 modprobe: WARNING: /etc/modprobe.conf line 39: > >>>>>> ignoring bad line starting with '-e' > >>>>>> > >>>>>> request_module: runaway loop modprobe net-pf-1 > >>>>>> Dec 31 16:00:14 modprobe: WARNING: /etc/modprobe.conf line 42: > >>>>>> ignoring bad line starting with '-e' > >>>>>> > >>>>>> NET: Registered protocol family 1 > >>>>>> Dec 31 16:00:14 modprobe: WARNING: /etc/modprobe.conf line 39: > >>>>>> ignoring bad line starting with '-e' > >>>>>> > >>>>>> Dec 31 16:00:14 modprobe: WARNING: /etc/modprobe.conf line 42: > >>>>>> ignoring bad line starting with '-e' > >>>>>> [... these last two warning lines repeat about 50 times ....] > >>>>>> Initializing random number generator... done. > >>>>>> Starting 32kHz clock...Settled > >>>>>> WARNING: /etc/modprobe.conf line 39: ignoring bad line starting > >>>>>> with '-e' > >>>>>> WARNING: /etc/modprobe.conf line 42: ignoring bad line starting > >>>>>> with '-e' > >>>>>> WARNING: /etc/modprobe.conf line 39: ignoring bad line starting > >>>>>> with '-e' > >>>>>> WARNING: /etc/modprobe.conf line 42: ignoring bad line starting > >>>>>> with '-e' > >>>>>> Set (AF1,out,clear) via /proc/gpio/GPIO12 > >>>>>> Starting Bluetooth subsystem:Trying baud rate 57600... > >>>>>> [... a bunch of the bluetooth messages since I don't have BT ...] > >>>>>> No response from BT module > >>>>>> Can't initialize device: Success > >>>>>> Starting network... > >>>>>> ifup: option with empty value "-e" > >>>>>> Starting Rendezvous: > >>>>>> Starting dropbear sshd: OK > >>>>>> Starting httpd... > >>>>>> > >>>>>> > >>>>>> > >>>>>> Looking at /etc/modprobe.conf, I see the following (starting on > >>>>>> line 37): > >>>>>> options hostap_cs ignore_cis_vcc=1 > >>>>>> options orinoco_cs ignore_cis_vcc=1 > >>>>>> -e > >>>>>> install pcmcia /sbin/modprobe --ignore-install pcmcia && modprobe > >>>>>> pxa2xx-cs > >>>>>> > >>>>>> -e alias mwlan0 cfio > >>>>>> install cfio /sbin/modprobe --ignore-install cfio && /sbin/modprobe > >>>>>> mcf25 > >>>>>> > >>>>>> Potentially useful details: I built the new rootfs.arm_nofpu.jffs2 > >>>>>> file from revision 1161 and added miniperl and python. My build > >>>>>> machine is running Ubuntu 7.04 (fiesty fawn). For yucks, I also > >>>>>> checked out the latest revision from subversion and built it, and I > >>>>>> see the same lines in the /etc/modprobe.conf file, which makes me > >>>>>> wonder if the warnings are red herrings. > >>>>>> ---------------------------------------------------------------------- > >>>>>> --- > >>>>>> This SF.net email is sponsored by: Splunk Inc. > >>>>>> Still grepping through log files to find problems? Stop. > >>>>>> Now Search log events and configuration files using AJAX and a > >>>>>> browser. > >>>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>>>>> _______________________________________________ > >>>>>> gumstix-users mailing list > >>>>>> gum...@li... > >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> ------------------------------------------------------------------------- > >>>>> This SF.net email is sponsored by: Splunk Inc. > >>>>> Still grepping through log files to find problems? Stop. > >>>>> Now Search log events and configuration files using AJAX and a browser. > >>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>>>> _______________________________________________ > >>>>> gumstix-users mailing list > >>>>> gum...@li... > >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> ------------------------------------------------------------------------- > >>>> This SF.net email is sponsored by: Splunk Inc. > >>>> Still grepping through log files to find problems? Stop. > >>>> Now Search log events and configuration files using AJAX and a browser. > >>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>>> _______________________________________________ > >>>> gumstix-users mailing list > >>>> gum...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>>> > >>>> > >>>> > >>>> > >>>> > >>> ------------------------------------------------------------------------- > >>> This SF.net email is sponsored by: Splunk Inc. > >>> Still grepping through log files to find problems? Stop. > >>> Now Search log events and configuration files using AJAX and a browser. > >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>> _______________________________________________ > >>> gumstix-users mailing list > >>> gum...@li... > >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>> > >>> > >>> > >>> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. > >> Still grepping through log files to find problems? Stop. > >> Now Search log events and configuration files using AJAX and a browser. > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > >> > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |