From: Juergen Q. <qu...@hs...> - 2007-05-25 09:32:56
Attachments:
session.log.reflash
|
Hi all, I think I need some help! Reflashing my verdex-xm4-bt failed. I tried it twice, first with r1321, second with 1352. Flashing seemed to work well, but when booting the system it stopped with the following messages: ... Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring bad line starting with '-e' Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring bad line starting with '-e' Gumstix Flash ROM: buffer write error (status 0xd0) Write clean marker to block at 0x00a60000 failed: -22 Newly-erased block contained word 0xffffffef at offset 0x00a41de0 Gumstix Flash ROM: buffer write error (status 0xd0) Write clean marker to block at 0x00a40000 failed: -22 Gumstix Flash ROM: Chip not ready after erase suspended: status = 0x0 I am still using (presinstalled) u-boot 1.1.4. Therefore in case of r1352 I loaded the kernel via zmodem and booted via bootm-command. That seems to work well... gum> loadb a2000000 gum> bootm a2000000 Find attach my Kermit-session.log-file. Any help is appreciated! Juergen. |
From: Juergen Q. <qu...@hs...> - 2007-05-25 10:27:15
|
My gumstix is booting again... For the protocol: I changed two things. 1. I erased the flash with the command >>jerase<< instead of >>erase<<. BTW: What is the difference between "erase" and "jerase"? 2. I exchanged the defect "modprobe.conf" file in the root filesystem. I still do not know what part of the build process is responsible for the defects in the file... Juergen On Fri, May 25, 2007 at 11:36:35AM +0200, Juergen Quade wrote: > Hi all, >=20 > I think I need some help! > Reflashing my verdex-xm4-bt failed. I tried it twice, > first with r1321, second with 1352. >=20 > Flashing seemed to work well, but when booting the > system it stopped with the following messages: >=20 > ... > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: > ignoring bad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: > ignoring bad line starting with '-e' >=20 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00a60000 failed: -22 > Newly-erased block contained word 0xffffffef at offset 0x00a41de0 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00a40000 failed: -22 > Gumstix Flash ROM: Chip not ready after erase suspended: status = =3D > 0x0 >=20 > I am still using (presinstalled) u-boot 1.1.4. Therefore > in case of r1352 I loaded the kernel via zmodem and booted > via bootm-command. That seems to work well... >=20 > gum> loadb a2000000 > gum> bootm a2000000 >=20 > Find attach my Kermit-session.log-file. >=20 > Any help is appreciated! >=20 > Juergen. > ? >=20 >=20 >=20 > U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >=20 >=20 >=20 > *** Welcome to Gumstix *** >=20 >=20 >=20 > U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >=20 > RAM Configuration: >=20 > Bank #0: a0000000 64 MB >=20 > Flash: 16 MB >=20 > Using default environment >=20 >=20 >=20 > SMC91C1111-0 >=20 > Net: SMC91C1111-0 >=20 > Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 > Instruction Cache is ON > ### JFFS2 loading 'boot/uImage' to 0xa2000000 > Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =08= =08/ =08=08. =08=08- =08=08\ =08=08| =08=08. =08=08/ =08=08- =08=08\ =08= =08. =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08. =08= =08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08= =08- =08=08\ =08=08| =08=08/ =08=08. =08=08. =08=08- =08=08. =08=08\ =08= =08. =08=08. =08=08| =08=08/=20 >=20 > U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >=20 > *** Welcome to Gumstix *** >=20 > U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 > RAM Configuration: > Bank #0: a0000000 64 MB > Flash: 16 MB > Using default environment >=20 > SMC91C1111-0 >=20 >=20 > U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz ? >=20 > U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >=20 > *** Welcome to Gumstix *** >=20 > U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 > RAM Configuration: > Bank #0: a0000000 64 MB > Flash: 16 MB > Using default environment >=20 > SMC91C1111-0 > Net: SMC91C1111-0 > Hit any key to stop autoboot: 2 =08=08=08 0=20 > GUM> loadb a2000000 > ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps... > ## Total Size =3D 0x006f7984 =3D 7305604 Bytes > ## Start Addr =3D 0xA2000000 > GUM> crc32 a2000000 ${filesys=08 =08=08 =08ize} > CRC32 for a2000000 ... a26f7983 =3D=3D> 79c08dbc > GUM> protect on 1:0-1 > Protect Flash Sectors 0-1 in Bank # 1 > .. done > GUM> erase all > Erase Flash Bank # 1 - Warning: 2 protected sectors will not be erased! > .........................................................................= =2E....................................................... done > GUM> cp.b a2000000 40000 ${filesize} > Copy to Flash... done > GUM> boot > Instruction Cache is ON > ### JFFS2 loading 'boot/uImage' to 0xa2000000 > Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =08= =08/ =08=08. =08=08- =08=08\ =08=08| =08=08. =08=08/ =08=08- =08=08\ =08= =08. =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- =08= =08. =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08= =08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08= \ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08= =08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08= done. > ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000 > ## Booting image at a2000000 ... > Image Name: uImage > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 858388 Bytes =3D 838.3 kB > Load Address: a0008000 > Entry Point: a0008000 > OK >=20 > Starting kernel ... >=20 > Linux version 2.6.18gum (quade@ezs-mobil) (gcc version 4.1.1) #1 Fri May = 25 09:53:26 CEST 2007 > CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f > Machine: The Gumstix Platform > 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=20 > 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=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djf= fs2 reboot=3Dcold,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 =3D 64MB total > Memory: 63128KB available (1396K code, 285K data, 64K 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) (SUMMARY) (C) 2001-2006 Red Hat, Inc. > Initializing Cryptographic API > io scheduler noop registered > io scheduler cfq registered (default) > pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART > pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART > pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 20) is a STUART > Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidt= h) > 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 > 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: 64K > request_module: runaway loop modprobe net-pf-1 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > request_module: runaway loop modprobe net-pf-1 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > NET: Registered protocol family 1 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00840000 failed: -22 > Newly-erased block contained word 0xfffeffff at offset 0x008202c4 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00820000 failed: -22 > Gumstix Flash ROM: Chip not ready after erase suspended: status =3D 0x0 > ? >=20 > U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >=20 > *** Welcome to Gumstix *** >=20 > U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 > RAM Configuration: > Bank #0: a0000000 64 MB > Flash: 16 MB > Using default environment >=20 > SMC91C1111-0 > Net: SMC91C1111-0 > Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 > Instruction Cache is ON > ### JFFS2 loading 'boot/uImage' to 0xa2000000 > Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =08= =08/ =08=08. =08=08- =08=08\ =08=08| =08=08. =08=08/ =08=08- =08=08\ =08= =08. =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- =08= =08. =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08= =08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08= \ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08= =08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08= done. > ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000 > ## Booting image at a2000000 ... > Image Name: uImage > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 858388 Bytes =3D 838.3 kB > Load Address: a0008000 > Entry Point: a0008000 > OK >=20 > Starting kernel ... >=20 > Linux version 2.6.18gum (quade@ezs-mobil) (gcc version 4.1.1) #1 Fri May = 25 09:53:26 CEST 2007 > CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f > Machine: The Gumstix Platform > 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=20 > 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=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djf= fs2 reboot=3Dcold,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 =3D 64MB total > Memory: 63128KB available (1396K code, 285K data, 64K 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) (SUMMARY) (C) 2001-2006 Red Hat, Inc. > Initializing Cryptographic API > io scheduler noop registered > io scheduler cfq registered (default) > pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART > pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART > pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 20) is a STUART > Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidt= h) > 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 > 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: 64K > request_module: runaway loop modprobe net-pf-1 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > request_module: runaway loop modprobe net-pf-1 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > NET: Registered protocol family 1 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring b= ad line starting with '-e' >=20 > Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring b= ad line starting with '-e' >=20 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00a20000 failed: -22 > Newly-erased block contained word 0xffbfffff at offset 0x00a001f0 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00a00000 failed: -22 > Gumstix Flash ROM: Chip not ready after erase suspended: status =3D 0x0 > ? >=20 > U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >=20 > *** Welcome to Gumstix *** >=20 > U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 > RAM Configuration: > Bank #0: a0000000 64 MB > Flash: 16 MB > Using default environment >=20 > SMC91C1111-0 > Net: SMC91C1111-0 > Hit any key to stop autoboot: 2 =08=08=08 0=20 > GUM> ls > Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =08= =08/ =08=08. =08=08- =08=08\ =08=08| =08=08. =08=08/ =08=08- =08=08\ =08= =08. =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- =08= =08. =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08= =08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08= \ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ = =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08= =08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08= - =08=08 done. > drwxr-xr-x 0 Fri May 25 08:04:06 2007 bin > drwxr-xr-x 0 Fri May 25 07:54:34 2007 boot > drwxr-xr-x 0 Fri May 25 08:04:08 2007 dev > drwxr-xr-x 0 Fri May 25 08:04:08 2007 etc > drwxr-xr-x 0 Mon Nov 22 17:20:58 1999 home > drwxr-xr-x 0 Fri May 25 08:04:06 2007 lib > drwxr-xr-x 0 Fri May 25 07:08:09 2007 mnt > drwxr-xr-x 0 Mon Nov 22 17:21:08 1999 opt > drwxr-xr-x 0 Wed Nov 03 00:54:07 1999 proc > drwxr-xr-x 0 Fri May 25 07:08:09 2007 root > drwxr-xr-x 0 Fri May 25 08:04:07 2007 sbin > drwxr-xr-x 0 Fri May 25 07:08:09 2007 sys > drwxr-xr-x 0 Thu Jun 29 23:20:38 2000 tmp > drwxr-xr-x 0 Fri May 25 08:02:12 2007 usr > drwxr-xr-x 0 Fri May 25 07:42:49 2007 var > GUM>=20 > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@gu...> - 2007-05-25 15:12:15
|
On May 25, 2007, at 3:30 AM, Juergen Quade wrote: > My gumstix is booting again... > For the protocol: I changed two things. > > 1. I erased the flash with the command >>> jerase<< instead of >>erase<<. > > BTW: What is the difference between "erase" and "jerase"? "erase" resets all the bytes in the flash sector to 0xff. jerase first does an erase, and then writes a JFFS2 "clean block" header to the sector. This reduces substantially the time required the first time linux tries to mount the JFFS2 filesystem, since without the clean header in there, JFFS2 will re-erase the (already erased) block, and then write its clean header in. jerase MUST NOT be used to erase anything other than sectors to be used by a JFFS2 filesystem. Use regular "erase" to erase the u-boot sectors, for example. > 2. I exchanged the defect "modprobe.conf" file in the > root filesystem. I still do not know what part of the > build process is responsible for the defects in the > file... The "-e" errors iirc are due to some echo command which does not respect the -e flag and just echos it instead of turning on escape- interpretation. IIRC this happens on some distro which uses ash or sash or something as its default shell. C |
From: Jens C. <jc...@in...> - 2007-05-25 15:56:10
|
Juergen Quade schrieb: >> ... >> The "-e" errors iirc are due to some echo command which does not >> respect the -e flag and just echos it instead of turning on escape- >> interpretation. IIRC this happens on some distro which uses ash or >> sash or something as its default shell. > > I would say my kubuntu uses a bash, at least that is what I have > as default shell... > > Thanks for your explanations! > > Juergen > Not necessarily. I think default in Kubuntu is dash, at least I think I had to symlink it to bash by hand. Hope this helps Jens |
From: Juergen Q. <qu...@hs...> - 2007-05-25 16:08:25
|
On Fri, May 25, 2007 at 05:56:11PM +0200, Jens Carroll wrote: > Juergen Quade schrieb: > >> ... > >> The "-e" errors iirc are due to some echo command which does not > >> respect the -e flag and just echos it instead of turning on escape- > >> interpretation. IIRC this happens on some distro which uses ash or > >> sash or something as its default shell. > > > > I would say my kubuntu uses a bash, at least that is what I have > > as default shell... > > > > Thanks for your explanations! > > > > Juergen > > > Not necessarily. I think default in Kubuntu is dash, at least I think I > had to symlink it to bash by hand. Hmm, in /etc/passwd users and root have a "/bin/bash" as shell; no mentioning of "dash" at all. (And /bin/bash is not a symlink to something like /bin/dash, although a "dash" is installed in the system). Whether another command or buildroot is calling /bin/dash (or whatover shell is doing the mess) internally? Juergen. |
From: Dave H. <dhy...@gm...> - 2007-05-25 16:37:25
|
Hi guys, > Whether another command or buildroot is calling /bin/dash (or whatover > shell is doing the mess) internally? It would be that /bin/sh is symlinked to dash -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: bSib1 <bsi...@co...> - 2007-06-25 20:41:09
|
Juergen, did you ever figure out why you were getting the "-e" in your modprobe.conf file. I switched to a new build maching and am now getting them as well. ...with similiar failures as you described?? Brian Sibilsky Juergen Quade wrote: >=20 > My gumstix is booting again... > For the protocol: I changed two things. >=20 > 1. I erased the flash with the command > >>jerase<< instead of >>erase<<. >=20 > BTW: What is the difference between "erase" and "jerase"? >=20 > 2. I exchanged the defect "modprobe.conf" file in the > root filesystem. I still do not know what part of the > build process is responsible for the defects in the > file... >=20 > Juergen >=20 >=20 > On Fri, May 25, 2007 at 11:36:35AM +0200, Juergen Quade wrote: >> Hi all, >>=20 >> I think I need some help! >> Reflashing my verdex-xm4-bt failed. I tried it twice, >> first with r1321, second with 1352. >>=20 >> Flashing seemed to work well, but when booting the >> system it stopped with the following messages: >>=20 >> ... >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: >> ignoring bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: >> ignoring bad line starting with '-e' >>=20 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a60000 failed: -22 >> Newly-erased block contained word 0xffffffef at offset 0x00a41de= 0 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a40000 failed: -22 >> Gumstix Flash ROM: Chip not ready after erase suspended: status = =3D >> 0x0 >>=20 >> I am still using (presinstalled) u-boot 1.1.4. Therefore >> in case of r1352 I loaded the kernel via zmodem and booted >> via bootm-command. That seems to work well... >>=20 >> gum> loadb a2000000 >> gum> bootm a2000000 >>=20 >> Find attach my Kermit-session.log-file. >>=20 >> Any help is appreciated! >>=20 >> Juergen. >=20 >> ? >>=20 >>=20 >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >>=20 >>=20 >> *** Welcome to Gumstix *** >>=20 >>=20 >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >>=20 >> RAM Configuration: >>=20 >> Bank #0: a0000000 64 MB >>=20 >> Flash: 16 MB >>=20 >> Using default environment >>=20 >>=20 >>=20 >> SMC91C1111-0 >>=20 >> Net: SMC91C1111-0 >>=20 >> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 >> Instruction Cache is ON >> ### JFFS2 loading 'boot/uImage' to 0xa2000000 >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08= \ =08=08| =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08.= =08=08. =08=08- =08=08. =08=08\ =08=08. =08=08. =08=08| =08=08/=20 >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >>=20 >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz ? >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >> Net: SMC91C1111-0 >> Hit any key to stop autoboot: 2 =08=08=08 0=20 >> GUM> loadb a2000000 >> ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps... >> ## Total Size =3D 0x006f7984 =3D 7305604 Bytes >> ## Start Addr =3D 0xA2000000 >> GUM> crc32 a2000000 ${filesys=08 =08=08 =08ize} >> CRC32 for a2000000 ... a26f7983 =3D=3D> 79c08dbc >> GUM> protect on 1:0-1 >> Protect Flash Sectors 0-1 in Bank # 1 >> .. done >> GUM> erase all >> Erase Flash Bank # 1 - Warning: 2 protected sectors will not be erased! >> ........................................................................= ......................................................... >> done >> GUM> cp.b a2000000 40000 ${filesize} >> Copy to Flash... done >> GUM> boot >> Instruction Cache is ON >> ### JFFS2 loading 'boot/uImage' to 0xa2000000 >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08= \ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08-= =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ >> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ >> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done. >> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000 >> ## Booting image at a2000000 ... >> Image Name: uImage >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 858388 Bytes =3D 838.3 kB >> Load Address: a0008000 >> Entry Point: a0008000 >> OK >>=20 >> Starting kernel ... >>=20 >> Linux version 2.6.18gum (quade@ezs-mobil) (gcc version 4.1.1) #1 Fri May >> 25 09:53:26 CEST 2007 >> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f >> Machine: The Gumstix Platform >> 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=20 >> 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=3DttyS0,115200n8 root=3D1f01 rootfstype=3Dj= ffs2 >> reboot=3Dcold,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 =3D 64MB total >> Memory: 63128KB available (1396K code, 285K data, 64K 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) (SUMMARY) (C) 2001-2006 Red Hat, Inc. >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler cfq registered (default) >> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART >> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART >> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 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 >> 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: 64K >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> NET: Registered protocol family 1 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00840000 failed: -22 >> Newly-erased block contained word 0xfffeffff at offset 0x008202c4 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00820000 failed: -22 >> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D 0x0 >> ? >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >> Net: SMC91C1111-0 >> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 >> Instruction Cache is ON >> ### JFFS2 loading 'boot/uImage' to 0xa2000000 >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08= \ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08-= =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ >> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ >> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done. >> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000 >> ## Booting image at a2000000 ... >> Image Name: uImage >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 858388 Bytes =3D 838.3 kB >> Load Address: a0008000 >> Entry Point: a0008000 >> OK >>=20 >> Starting kernel ... >>=20 >> Linux version 2.6.18gum (quade@ezs-mobil) (gcc version 4.1.1) #1 Fri May >> 25 09:53:26 CEST 2007 >> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f >> Machine: The Gumstix Platform >> 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=20 >> 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=3DttyS0,115200n8 root=3D1f01 rootfstype=3Dj= ffs2 >> reboot=3Dcold,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 =3D 64MB total >> Memory: 63128KB available (1396K code, 285K data, 64K 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) (SUMMARY) (C) 2001-2006 Red Hat, Inc. >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler cfq registered (default) >> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART >> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART >> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 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 >> 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: 64K >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> NET: Registered protocol family 1 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring >> bad line starting with '-e' >>=20 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a20000 failed: -22 >> Newly-erased block contained word 0xffbfffff at offset 0x00a001f0 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a00000 failed: -22 >> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D 0x0 >> ? >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >> Net: SMC91C1111-0 >> Hit any key to stop autoboot: 2 =08=08=08 0=20 >> GUM> ls >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08= \ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08-= =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- >> =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ = =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| >> =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done. >> drwxr-xr-x 0 Fri May 25 08:04:06 2007 bin >> drwxr-xr-x 0 Fri May 25 07:54:34 2007 boot >> drwxr-xr-x 0 Fri May 25 08:04:08 2007 dev >> drwxr-xr-x 0 Fri May 25 08:04:08 2007 etc >> drwxr-xr-x 0 Mon Nov 22 17:20:58 1999 home >> drwxr-xr-x 0 Fri May 25 08:04:06 2007 lib >> drwxr-xr-x 0 Fri May 25 07:08:09 2007 mnt >> drwxr-xr-x 0 Mon Nov 22 17:21:08 1999 opt >> drwxr-xr-x 0 Wed Nov 03 00:54:07 1999 proc >> drwxr-xr-x 0 Fri May 25 07:08:09 2007 root >> drwxr-xr-x 0 Fri May 25 08:04:07 2007 sbin >> drwxr-xr-x 0 Fri May 25 07:08:09 2007 sys >> drwxr-xr-x 0 Thu Jun 29 23:20:38 2000 tmp >> drwxr-xr-x 0 Fri May 25 08:02:12 2007 usr >> drwxr-xr-x 0 Fri May 25 07:42:49 2007 var >> GUM>=20 >> ------------------------------------------------------------------------= - >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >=20 >=20 > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users >=20 >=20 --=20 View this message in context: http://www.nabble.com/Need-help%3A-Flash-Prob= lems-tf3815114.html#a11295128 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Sibilsky <bsi...@co...> - 2007-06-25 20:57:17
|
Nevermind, Initially I wasn't able to see the rest of the responses. I = was using the dash shell and have changed it to bash. Hopefully that will = fix things. Brian -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of bSib1 Sent: Monday, June 25, 2007 3:41 PM To: gum...@li... Subject: Re: [Gumstix-users] Need help: Flash-Problems Juergen, did you ever figure out why you were getting the "-e" in your modprobe.conf file. I switched to a new build maching and am now getting them as well. ...with similiar failures as you described?? Brian Sibilsky Juergen Quade wrote: >=20 > My gumstix is booting again... > For the protocol: I changed two things. >=20 > 1. I erased the flash with the command > >>jerase<< instead of >>erase<<. >=20 > BTW: What is the difference between "erase" and "jerase"? >=20 > 2. I exchanged the defect "modprobe.conf" file in the > root filesystem. I still do not know what part of the > build process is responsible for the defects in the > file... >=20 > Juergen >=20 >=20 > On Fri, May 25, 2007 at 11:36:35AM +0200, Juergen Quade wrote: >> Hi all, >>=20 >> I think I need some help! >> Reflashing my verdex-xm4-bt failed. I tried it twice, >> first with r1321, second with 1352. >>=20 >> Flashing seemed to work well, but when booting the >> system it stopped with the following messages: >>=20 >> ... >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line = 39: >> ignoring bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line = 42: >> ignoring bad line starting with '-e' >>=20 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a60000 failed: -22 >> Newly-erased block contained word 0xffffffef at offset = 0x00a41de0 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a40000 failed: -22 >> Gumstix Flash ROM: Chip not ready after erase suspended: = status =3D >> 0x0 >>=20 >> I am still using (presinstalled) u-boot 1.1.4. Therefore >> in case of r1352 I loaded the kernel via zmodem and booted >> via bootm-command. That seems to work well... >>=20 >> gum> loadb a2000000 >> gum> bootm a2000000 >>=20 >> Find attach my Kermit-session.log-file. >>=20 >> Any help is appreciated! >>=20 >> Juergen. >=20 >> ? >>=20 >>=20 >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >>=20 >>=20 >> *** Welcome to Gumstix *** >>=20 >>=20 >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >>=20 >> RAM Configuration: >>=20 >> Bank #0: a0000000 64 MB >>=20 >> Flash: 16 MB >>=20 >> Using default environment >>=20 >>=20 >>=20 >> SMC91C1111-0 >>=20 >> Net: SMC91C1111-0 >>=20 >> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 >> Instruction Cache is ON >> ### JFFS2 loading 'boot/uImage' to 0xa2000000 >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. = =08=08\ =08=08| =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ = =08=08. =08=08. =08=08- =08=08. =08=08\ =08=08. =08=08. =08=08| = =08=08/ >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >>=20 >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz ? >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >> Net: SMC91C1111-0 >> Hit any key to stop autoboot: 2 =08=08=08 0=20 >> GUM> loadb a2000000 >> ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps... >> ## Total Size =3D 0x006f7984 =3D 7305604 Bytes >> ## Start Addr =3D 0xA2000000 >> GUM> crc32 a2000000 ${filesys=08 =08=08 =08ize} >> CRC32 for a2000000 ... a26f7983 =3D=3D> 79c08dbc >> GUM> protect on 1:0-1 >> Protect Flash Sectors 0-1 in Bank # 1 >> .. done >> GUM> erase all >> Erase Flash Bank # 1 - Warning: 2 protected sectors will not be = erased! >> .........................................................................= ... ..................................................... >> done >> GUM> cp.b a2000000 40000 ${filesize} >> Copy to Flash... done >> GUM> boot >> Instruction Cache is ON >> ### JFFS2 loading 'boot/uImage' to 0xa2000000 >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. = =08=08\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ = =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- = =08=08\ >> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ = =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| = =08=08/ >> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done. >> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000 >> ## Booting image at a2000000 ... >> Image Name: uImage >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 858388 Bytes =3D 838.3 kB >> Load Address: a0008000 >> Entry Point: a0008000 >> OK >>=20 >> Starting kernel ... >>=20 >> Linux version 2.6.18gum (quade@ezs-mobil) (gcc version 4.1.1) #1 Fri = May >> 25 09:53:26 CEST 2007 >> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f >> Machine: The Gumstix Platform >> 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=20 >> 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=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2 >> reboot=3Dcold,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 =3D 64MB total >> Memory: 63128KB available (1396K code, 285K data, 64K 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) (SUMMARY) (C) 2001-2006 Red Hat, Inc. >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler cfq registered (default) >> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART >> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART >> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 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 >> 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: 64K >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> NET: Registered protocol family 1 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00840000 failed: -22 >> Newly-erased block contained word 0xfffeffff at offset 0x008202c4 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00820000 failed: -22 >> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D = 0x0 >> ? >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >> Net: SMC91C1111-0 >> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 >> Instruction Cache is ON >> ### JFFS2 loading 'boot/uImage' to 0xa2000000 >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. = =08=08\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ = =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- = =08=08\ >> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ = =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| = =08=08/ >> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done. >> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000 >> ## Booting image at a2000000 ... >> Image Name: uImage >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 858388 Bytes =3D 838.3 kB >> Load Address: a0008000 >> Entry Point: a0008000 >> OK >>=20 >> Starting kernel ... >>=20 >> Linux version 2.6.18gum (quade@ezs-mobil) (gcc version 4.1.1) #1 Fri = May >> 25 09:53:26 CEST 2007 >> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f >> Machine: The Gumstix Platform >> 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=20 >> 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=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2 >> reboot=3Dcold,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 =3D 64MB total >> Memory: 63128KB available (1396K code, 285K data, 64K 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) (SUMMARY) (C) 2001-2006 Red Hat, Inc. >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler cfq registered (default) >> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART >> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART >> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 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 >> 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: 64K >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> request_module: runaway loop modprobe net-pf-1 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> NET: Registered protocol family 1 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: = ignoring >> bad line starting with '-e' >>=20 >> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: = ignoring >> bad line starting with '-e' >>=20 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a20000 failed: -22 >> Newly-erased block contained word 0xffbfffff at offset 0x00a001f0 >> Gumstix Flash ROM: buffer write error (status 0xd0) >> Write clean marker to block at 0x00a00000 failed: -22 >> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D = 0x0 >> ? >>=20 >> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@400 MHz - 1321 >>=20 >> *** Welcome to Gumstix *** >>=20 >> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70 >> RAM Configuration: >> Bank #0: a0000000 64 MB >> Flash: 16 MB >> Using default environment >>=20 >> SMC91C1111-0 >> Net: SMC91C1111-0 >> Hit any key to stop autoboot: 2 =08=08=08 0=20 >> GUM> ls >> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| = =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20 >> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. = =08=08\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08- >> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ = =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ = =08=08- >> =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- = =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ = =08=08| >> =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done. >> drwxr-xr-x 0 Fri May 25 08:04:06 2007 bin >> drwxr-xr-x 0 Fri May 25 07:54:34 2007 boot >> drwxr-xr-x 0 Fri May 25 08:04:08 2007 dev >> drwxr-xr-x 0 Fri May 25 08:04:08 2007 etc >> drwxr-xr-x 0 Mon Nov 22 17:20:58 1999 home >> drwxr-xr-x 0 Fri May 25 08:04:06 2007 lib >> drwxr-xr-x 0 Fri May 25 07:08:09 2007 mnt >> drwxr-xr-x 0 Mon Nov 22 17:21:08 1999 opt >> drwxr-xr-x 0 Wed Nov 03 00:54:07 1999 proc >> drwxr-xr-x 0 Fri May 25 07:08:09 2007 root >> drwxr-xr-x 0 Fri May 25 08:04:07 2007 sbin >> drwxr-xr-x 0 Fri May 25 07:08:09 2007 sys >> drwxr-xr-x 0 Thu Jun 29 23:20:38 2000 tmp >> drwxr-xr-x 0 Fri May 25 08:02:12 2007 usr >> drwxr-xr-x 0 Fri May 25 07:42:49 2007 var >> GUM>=20 >> = -------------------------------------------------------------------------= >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >=20 >=20 > = -------------------------------------------------------------------------= > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users >=20 >=20 --=20 View this message in context: http://www.nabble.com/Need-help%3A-Flash-Problems-tf3815114.html#a1129512= 8 Sent from the Gumstix mailing list archive at Nabble.com. -------------------------------------------------------------------------= This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Juergen Q. <qu...@hs...> - 2007-05-25 15:31:45
|
> ... > The "-e" errors iirc are due to some echo command which does not > respect the -e flag and just echos it instead of turning on escape- > interpretation. IIRC this happens on some distro which uses ash or > sash or something as its default shell. I would say my kubuntu uses a bash, at least that is what I have as default shell... Thanks for your explanations! Juergen |
From: Dave H. <dhy...@gm...> - 2007-05-25 16:36:15
|
HI Juergen, > Flashing seemed to work well, but when booting the > system it stopped with the following messages: > > ... > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: > ignoring bad line starting with '-e' See this page: http://docswiki.gumstix.com/Buildroot_on_Ubuntu#Possible_Problems > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00a60000 failed: -22 > Newly-erased block contained word 0xffffffef at offset 0x00a41de0 > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00a40000 failed: -22 > Gumstix Flash ROM: Chip not ready after erase suspended: status = > 0x0 This looks like a bad flash chip - or possibly marginal timing on u-boot's part. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Philippe N. <pn....@gm...> - 2007-05-25 17:08:41
|
Hi > > Gumstix Flash ROM: buffer write error (status 0xd0) > > Write clean marker to block at 0x00a40000 failed: -22 > > Gumstix Flash ROM: Chip not ready after erase suspended: status = > > 0x0 > > This looks like a bad flash chip - or possibly marginal timing on u-boot's part. > please can you explain more, i have the same problem and it's a recurrent problem > > Gumstix Flash ROM: buffer write error (status 0xd0) > > Write clean marker to block at 0x00a40000 failed: -22 it's a typical message when i write in a file, not all the time i have also re-falshing, but it's recurrent. i don't think that the flash is damaged, but i don't understand, what is it ? thanks , philippe 2007/5/25, Dave Hylands <dhy...@gm...>: > HI Juergen, > > > Flashing seemed to work well, but when booting the > > system it stopped with the following messages: > > > > ... > > Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: > > ignoring bad line starting with '-e' > > See this page: > http://docswiki.gumstix.com/Buildroot_on_Ubuntu#Possible_Problems > > > Gumstix Flash ROM: buffer write error (status 0xd0) > > Write clean marker to block at 0x00a60000 failed: -22 > > Newly-erased block contained word 0xffffffef at offset 0x00a41de0 > > Gumstix Flash ROM: buffer write error (status 0xd0) > > Write clean marker to block at 0x00a40000 failed: -22 > > Gumstix Flash ROM: Chip not ready after erase suspended: status = > > 0x0 > > This looks like a bad flash chip - or possibly marginal timing on u-boot's part. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2007-05-25 18:48:47
|
HI Phillipe, > it's a typical message when i write in a file, not all the time > i have also re-falshing, but it's recurrent. > i don't think that the flash is damaged, but i don't understand, what is it ? I think it depends on when exactly it happens. The fact that you're seeing this error means to that flash block located at 0x00a40000 is in fact not being erased properly. I'm pretty familiar with how things work with NAND chips (cause that's what I use at work). When the kernel is running, if jffs2 encounters this problem, it will pick another block. However, I'm pretty sure that if u-boot encounters a bad block while writing then you're hooped. It's my understanding that you shouldn't be getting bad blocks with NOR flash. Since the gumstix uses NOR flash, the fact that you're seeing this seems to indicate something wrong with the flash chip itself. 0x00a40000 is about 10 Mb into the flash, so it's a region that u-boot normally wouldn't write to (except using the jerase command). At work, we have a temperature chamber, and we do stress tests where we take the device under test through the temperature extremes that it's supposed to be rated for. We've discovered that parts which work properly at room temperature, often need sligthly different timings in order to operate properly over the entire temperature range. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Philippe N. <pn....@gm...> - 2007-05-25 21:41:36
|
Sorry, but 0x00a40000 address it's an exemple. this address is different for each "Gumstix error flash ..." i have try a lot of combinaison and i have re-write completly all programs... but if i use the same program, with connex xm400 bt, r1161 : no problem !!!! and now i have the same error with the different address but my verdex make good. however, if my verdex is out, i must re-flashing because u-boot encounters a bad block while writing. why this error is present on verdex ? on r1352 ? I cannot any more what make ... is it possible to verify flash at each boot and so repare all bad sector ? i use only bluez (sdp) and sqlite ... perhaps the sqlite multi threading ? i don't know thank for your help or idea .. Philippe 2007/5/25, Dave Hylands <dhy...@gm...>: > HI Phillipe, > > > it's a typical message when i write in a file, not all the time > > i have also re-falshing, but it's recurrent. > > i don't think that the flash is damaged, but i don't understand, what is it ? > > I think it depends on when exactly it happens. The fact that you're > seeing this error means to that flash block located at 0x00a40000 is > in fact not being erased properly. > > I'm pretty familiar with how things work with NAND chips (cause that's > what I use at work). When the kernel is running, if jffs2 encounters > this problem, it will pick another block. > > However, I'm pretty sure that if u-boot encounters a bad block while > writing then you're hooped. > > It's my understanding that you shouldn't be getting bad blocks with > NOR flash. Since the gumstix uses NOR flash, the fact that you're > seeing this seems to indicate something wrong with the flash chip > itself. > > 0x00a40000 is about 10 Mb into the flash, so it's a region that > u-boot normally wouldn't write to (except using the jerase command). > > At work, we have a temperature chamber, and we do stress tests where > we take the device under test through the temperature extremes that > it's supposed to be rated for. We've discovered that parts which work > properly at room temperature, often need sligthly different timings in > order to operate properly over the entire temperature range. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Juergen Q. <qu...@hs...> - 2007-05-26 19:33:24
|
> ... > is it possible to verify flash at each boot and so repare all bad sector ? > > i use only bluez (sdp) and sqlite ... > perhaps the sqlite multi threading ? > i don't know > > thank for your help or idea .. Maybe you avoid to "work" with the flash... Has anybody tried to hold the rootfilesystem of the gumstix in a ramdisk instead of using the flash? In this case you have on the flashmemory just some kernel and some ramdisk images, which will be loaded at boottime into memory. Advantages: - Longer live for your flash-memory: You don't write to the flash except for updating the system. - Update is much easier: + Mount the flash. + Copy the new image to the flash. + reboot + boot the kernel with the ramdisk-image + if it fails you can boot the (still existen) old image. - When updating you do not have to write a complete new jffs2-Image; you do not have to write the whole flash. - You can hold configs in the flash; those configs are available after update (because writing a new image to the flash does not mean to overwrite everything else on the flash). Disadvantage: - You need to sacrifice some ram. But (using a 16MByte Ramdisk) are 48 MBytes of RAM not enough for your application? - To change the config of systemfiles (for example in /etc) you have to loop-mount the image on the flash. Has someone worked on this approach? Juergen. |
From: Dave H. <dhy...@gm...> - 2007-05-27 01:05:31
|
Hi Juergen, > Has anybody tried to hold the rootfilesystem of the gumstix in a > ramdisk instead of using the flash? In this case you have on the > flashmemory just some kernel and some ramdisk images, which will be > loaded at boottime into memory. I've used cramfs before (not n the gumstix, but on a similar product). It's a read-only filesystem. I've also seen extfs used to populate a ramdisk. You could also use an NFS filesystem if you had an NFS server. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Philippe N. <pn....@gm...> - 2007-05-29 06:46:51
|
Hi Dave sorry, but i think which stop the verdex by a plug off power, it's not a good solution for a daemon programm with scan bluetooth and update sqlite base. and so i have this error at reboot : > Gumstix Flash ROM: buffer write error (status 0xd0) > Write clean marker to block at 0x00XX0000 failed: -22 how to do to repare this error ? how to do not have this error ? is it possible to protect uboot and kernel with this error ? because il this error is in Kernel address, il must reflashing verdex !!!! thanks for your response and help Philippe 2007/5/25, Dave Hylands <dhy...@gm...>: > HI Phillipe, > > > it's a typical message when i write in a file, not all the time > > i have also re-falshing, but it's recurrent. > > i don't think that the flash is damaged, but i don't understand, what is it ? > > I think it depends on when exactly it happens. The fact that you're > seeing this error means to that flash block located at 0x00a40000 is > in fact not being erased properly. > > I'm pretty familiar with how things work with NAND chips (cause that's > what I use at work). When the kernel is running, if jffs2 encounters > this problem, it will pick another block. > > However, I'm pretty sure that if u-boot encounters a bad block while > writing then you're hooped. > > It's my understanding that you shouldn't be getting bad blocks with > NOR flash. Since the gumstix uses NOR flash, the fact that you're > seeing this seems to indicate something wrong with the flash chip > itself. > > 0x00a40000 is about 10 Mb into the flash, so it's a region that > u-boot normally wouldn't write to (except using the jerase command). > > At work, we have a temperature chamber, and we do stress tests where > we take the device under test through the temperature extremes that > it's supposed to be rated for. We've discovered that parts which work > properly at room temperature, often need sligthly different timings in > order to operate properly over the entire temperature range. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2007-05-29 07:10:36
|
HI Phillipe, > sorry, but i think which stop the verdex by a plug off power, it's not > a good solution for a daemon programm with scan bluetooth and update > sqlite base. > > and so i have this error at reboot : > > > Gumstix Flash ROM: buffer write error (status 0xd0) > > Write clean marker to block at 0x00XX0000 failed: -22 > > how to do to repare this error ? I'm not sure. It seems to be showing up all over the place. I've seen it, my brother has seen it, and several people on the list have seen it. It could be due to bad hardware, or it could be a software problem. Perhaps Craig or Gordon have more insight? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Philippe N. <pn....@gm...> - 2007-05-29 09:02:42
|
Thanks, i am waiting ... for information, do you think that the problem is the multithreading with sqlite I have 2 programs whish use the same database ... thanks for your help. Philippe 2007/5/29, Dave Hylands <dhy...@gm...>: > HI Phillipe, > > > sorry, but i think which stop the verdex by a plug off power, it's not > > a good solution for a daemon programm with scan bluetooth and update > > sqlite base. > > > > and so i have this error at reboot : > > > > > Gumstix Flash ROM: buffer write error (status 0xd0) > > > Write clean marker to block at 0x00XX0000 failed: -22 > > > > how to do to repare this error ? > > I'm not sure. It seems to be showing up all over the place. I've seen > it, my brother has seen it, and several people on the list have seen > it. > > It could be due to bad hardware, or it could be a software problem. > > Perhaps Craig or Gordon have more insight? > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |