From: jdoutt <jd...@wh...> - 2009-05-06 20:04:51
|
Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)' U-Boot 1.2.0 (May 10 2008 - 21:17:19) - PXA270@400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB Using default environment Hit any key to stop autoboot: 0 Instruction Cache is ON Found gumstix-factory.script on MMC... ## Executing script at a2000000 Booting from mmc/microSD... Detected: 1935360 blocks of 1024 bytes (1890MB) SD card. Vendor: Man 27 OEM PH "SD02G" Date 11/2008 Product: 2086740393 Revision: 2.0 reading uimage 1030128 bytes read ## Booting image at a2000000 ... Image Name: Angstrom/2.6.21/gumstix-custom-v Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1030064 Bytes = 1005.9 kB Load Address: a0008000 Entry Point: a0008000 OK Starting kernel ... Linux version 2.6.21 (jdoutt@kira) (gcc version 4.1.2) #1 Sun Feb 15 16:56:34 EST 2009 CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f 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 CPU0: D VIVT undefined 5 cache ...... ...... pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth) Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled Using static partitions on Gumstix Flash ROM Creating 3 MTD partitions on "Gumstix Flash ROM": 0x00000000-0x00040000 : "Bootloader" 0x00040000-0x00f00000 : "RootFS" 0x00f00000-0x01000000 : "Kernel" TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale iWMMXt coprocessor detected. Waiting 1sec before mounting root device... No filesystem could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) rebooting from flash gives the following filesystems root@gumstix-custom-verdex:~$ df Filesystem 1k-blocks Used Available Use% Mounted on /dev/mtdblock1 15104 9984 5120 66% / /dev/mtdblock1 15104 9984 5120 66% /dev/.static/dev tmpfs 2048 44 2004 2% /dev tmpfs 31460 0 31460 0% /dev/shm tmpfs 31460 52 31408 0% /var/volatile tmpfs 31460 0 31460 0% /media/ram /dev/mmcblk0p1 40034 38514 1520 96% /media/card /dev/mmcblk0p2 1857948 40284 1723284 2% /media/mmcblk0p2 root@gumstix-custom-verdex:~$ The filesystem on the fat32 partition is: root@gumstix-custom-verdex:~$ lr /media/card/ -rwxr-xr-x 1 root root 332 Feb 15 2009 gumstix-factory.script -rwxr-xr-x 1 root root 1030128 Apr 30 2009 uimage root@gumstix-custom-verdex:~$ And that on the ext2 partition is: root@gumstix-custom-verdex:~$ lr /media/mmcblk0p2/ drwx------ 2 root root 16384 Jan 1 00:22 lost+found drwxrwxr-x 2 root root 4096 Jan 1 1970 mnt drwxrwxr-x 10 root root 4096 Jan 1 1970 usr drwxrwxr-x 10 root root 4096 Jan 1 1970 media drwxrwxr-x 2 root root 4096 Jan 1 1970 sbin drwxrwxr-x 2 root root 4096 Jan 1 1970 bin drwxrwxr-x 9 root root 4096 Jan 1 1970 var drwxrwxr-x 3 root root 4096 Jan 1 1970 home drwxr-xr-x 2 root root 4096 Jan 1 1970 boot drwxrwxr-x 28 root root 4096 Jan 1 1970 etc drwxrwxr-x 4 root root 4096 Jan 1 1970 lib drwxr-xr-x 2 root root 4096 Jan 1 1970 dev drwxr-xr-x 2 root root 4096 Feb 15 2009 sys drwxr-xr-x 2 root root 4096 Feb 15 2009 proc drwxrwxrwt 2 root root 4096 Feb 15 2009 tmp root@gumstix-custom-verdex:~$ -- View this message in context: http://www.nabble.com/Trouble-booting-from-mmc-card-on-Verdex-pro-tp23414427p23414427.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chuck R. <shi...@ro...> - 2009-05-06 23:17:09
|
On May 6, 2009, at 1:04 PM, jdoutt wrote: > Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable > to mount > root fs on unknown-block(0,0)' Before you install the uImage and rootfs onto the MMC card, you need to rebuild those 2 images. Specifically, you need to make certain that you have built a kernel that can boot from the MMC card. Otherwise you will encounter the 'unknown-block(0,0)' error upon booting the gumstix from the MMC card. Modify gumstix-custom-verdex.conf to include mmcroot, ext2 and fat. Chuck |
From: Jim D. <jd...@wh...> - 2009-05-06 23:28:36
|
Chuck Randall wrote: > On May 6, 2009, at 1:04 PM, jdoutt wrote: > > >> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >> to mount >> root fs on unknown-block(0,0)' >> > > Before you install the uImage and rootfs onto the MMC card, you need > to rebuild those 2 images. Specifically, you need to make certain that > you have built a kernel that can boot from the MMC card. Otherwise you > will encounter the 'unknown-block(0,0)' error upon booting the gumstix > from the MMC card. Modify gumstix-custom-verdex.conf to include > mmcroot, ext2 and fat. > > Chuck > Thanks so much - ext2 and fat were enabled, but mmcroot was not. I'm rebuilding now! |
From: Jim D. <jd...@wh...> - 2009-05-07 01:05:04
|
Chuck Randall wrote: > On May 6, 2009, at 1:04 PM, jdoutt wrote: > > >> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >> to mount >> root fs on unknown-block(0,0)' >> > > Before you install the uImage and rootfs onto the MMC card, you need > to rebuild those 2 images. Specifically, you need to make certain that > you have built a kernel that can boot from the MMC card. Otherwise you > will encounter the 'unknown-block(0,0)' error upon booting the gumstix > from the MMC card. Modify gumstix-custom-verdex.conf to include > mmcroot, ext2 and fat. > > Chuck > Thanks so much - ext2 and fat were enabled, but mmcroot was not. I'm rebuilding now! I'm using the microSD card (NOT the MMC as stated above!!!!). I understand that mmcroot is used for the microSD also - IS THAT CORRECT? .... BUT, get the same eror: U-Boot 1.2.0 (May 10 2008 - 21:17:19) - PXA270@400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB Using default environment Hit any key to stop autoboot: 0 Instruction Cache is ON Found gumstix-factory.script on MMC... ## Executing script at a2000000 Booting from mmc/microSD... Detected: 1935360 blocks of 1024 bytes (1890MB) SD card. Vendor: Man 27 OEM PH "SD02G" Date 11/2008 Product: 2086740393 Revision: 2.0 reading uimage 1030128 bytes read ## Booting image at a2000000 ... Image Name: Angstrom/2.6.21/gumstix-custom-v Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1030064 Bytes = 1005.9 kB Load Address: a0008000 Entry Point: a0008000 OK Starting kernel ... Linux version 2.6.21 (jdoutt@kira) (gcc version 4.1.2) #1 Sun Feb 15 16:56:34 EST 2009 CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f 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 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: 16256 Kernel command line: console=ttyS0,115200n8 rootdelay=1 root=/dev/mmcblk0p2 PID hash table entries: 256 (order: 8, 1024 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 62720KB available (1808K code, 196K data, 148K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 NET: Registered protocol family 2 Time: pxa_timer clocksource has been installed. IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler cfq registered (default) Console: switching to colour frame buffer device 80x24 pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth) Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled Using static partitions on Gumstix Flash ROM Creating 3 MTD partitions on "Gumstix Flash ROM": 0x00000000-0x00040000 : "Bootloader" 0x00040000-0x00f00000 : "RootFS" 0x00f00000-0x01000000 : "Kernel" TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale iWMMXt coprocessor detected. Waiting 1sec before mounting root device... No filesystem could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) |
From: Chuck R. <shi...@ro...> - 2009-05-07 01:23:58
|
On May 6, 2009, at 6:05 PM, Jim Doutt wrote: > > Chuck Randall wrote: >> On May 6, 2009, at 1:04 PM, jdoutt wrote: >> >>> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >>> to mount root fs on unknown-block(0,0)' >>> >> Before you install the uImage and rootfs onto the MMC card, you need >> to rebuild those 2 images. Specifically, you need to make certain >> that >> you have built a kernel that can boot from the MMC card. Otherwise >> you >> will encounter the 'unknown-block(0,0)' error upon booting the >> gumstix >> from the MMC card. Modify gumstix-custom-verdex.conf to include >> mmcroot, ext2 and fat. >> >> Chuck >> > > Thanks so much - ext2 and fat were enabled, but mmcroot was not. > I'm > rebuilding now! > > I'm using the microSD card (NOT the MMC as stated above!!!!). I > understand that mmcroot is used for the microSD also - IS THAT > CORRECT? > > .... BUT, get the same eror: Don't worry, the 'mmcroot' setting covers both microSD and MMC cards. Note the message in the bootup log: Booting from mmc/microSD... The only times I have received the 'unknown-block(0,0)' error is when I've made the 'mmcroot' setting incorrectly, or I copied the wrong uImage and rootfs to the microSD card. Make sure you edited the file located here and not some other version of it (the changes wouldn't get picked up): ~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix- custom-verdex.conf with the following line (NO whitespace at the beginning of the line): MACHINE_FEATURES += "mmcroot" Now, rebuild the images: bitbake -c rebuild task-base-gumstix bitbake -c rebuild gumstix-kernel bitbake -c rebuild gumstix-basic-image The products of this rebuild will be in this folder: ~/gumstix/gumstix-oe/tmp/deploy/glibc/images/gumstix-custom- verdex/ specifically: a. The uimage that goes into the FAT16 partition (mmcblk0p1) uImage-2.6.21-r1-gumstix-custom-verdex.bin b. The rootfs that goes into the ext2 partition (mmcblk0p2) gumstix-basic-image-gumstix-custom-verdex.rootfs.tar.gz Chuck |
From: Jim D. <jd...@wh...> - 2009-05-07 12:30:32
|
Chuck Randall wrote: > On May 6, 2009, at 6:05 PM, Jim Doutt wrote: > >> Chuck Randall wrote: >> >>> On May 6, 2009, at 1:04 PM, jdoutt wrote: >>> >>> >>>> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >>>> to mount root fs on unknown-block(0,0)' >>>> >>>> >>> Before you install the uImage and rootfs onto the MMC card, you need >>> to rebuild those 2 images. Specifically, you need to make certain >>> that >>> you have built a kernel that can boot from the MMC card. Otherwise >>> you >>> will encounter the 'unknown-block(0,0)' error upon booting the >>> gumstix >>> from the MMC card. Modify gumstix-custom-verdex.conf to include >>> mmcroot, ext2 and fat. >>> >>> Chuck >>> >>> >> Thanks so much - ext2 and fat were enabled, but mmcroot was not. >> I'm >> rebuilding now! >> >> I'm using the microSD card (NOT the MMC as stated above!!!!). I >> understand that mmcroot is used for the microSD also - IS THAT >> CORRECT? >> >> .... BUT, get the same eror: >> > > Don't worry, the 'mmcroot' setting covers both microSD and MMC cards. > Note the message in the bootup log: > Booting from mmc/microSD... > > The only times I have received the 'unknown-block(0,0)' error is when > I've made the 'mmcroot' setting incorrectly, or I copied the wrong > uImage and rootfs to the microSD card. > > Make sure you edited the file located here and not some other version > of it (the changes wouldn't get picked up): > ~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix- > custom-verdex.conf > > with the following line (NO whitespace at the beginning of the line): > MACHINE_FEATURES += "mmcroot" > > Now, rebuild the images: > bitbake -c rebuild task-base-gumstix > bitbake -c rebuild gumstix-kernel > bitbake -c rebuild gumstix-basic-image > > The products of this rebuild will be in this folder: > ~/gumstix/gumstix-oe/tmp/deploy/glibc/images/gumstix-custom- > verdex/ > specifically: > a. The uimage that goes into the FAT16 partition (mmcblk0p1) > uImage-2.6.21-r1-gumstix-custom-verdex.bin > b. The rootfs that goes into the ext2 partition (mmcblk0p2) > gumstix-basic-image-gumstix-custom-verdex.rootfs.tar.gz > > Chuck > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > SUCCESS!! Thank you so much, Chuck. The secret was the THREE bitbake commands you outlined (I had been issuing only 'bitbake gumstix-basic-image') and the edit to '~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix-custom-verdex.conf' (which I had got right after your first email). Now I can move on to code for my project: bringing in data over two serial lines, storing it to the microSD card, and putting the Gumstix into a deep sleep for a set period of time. I'll ask questions about that in a separate topic. Again, many thanks for setting me on the right path .... hope I can contribute back to the group sometime. jim |
From: arm_555 <ar...@pe...> - 2010-09-13 16:32:50
|
Hi guys, I'm a newbie! I follow this page on how to boot a Verdex from microsd (http://www.gumstix.net/User-How-To-s/view/User-How-To-s/Booting-from-microSD/SD/MMC/110.html) I'm trying to download kernel from www.sakoman.net/oe/mmc-boot/kernel-mmc.tar.gz and rootfs from www.sakoman.net/oe/mmc-boot/rootfs-mmc.tar.gz but the link seem to be broken. Anyone know where I can download the kernel and rootfs files from? Thank you, Arm jdoutt wrote: > > > > Chuck Randall wrote: >> On May 6, 2009, at 6:05 PM, Jim Doutt wrote: >> >>> Chuck Randall wrote: >>> >>>> On May 6, 2009, at 1:04 PM, jdoutt wrote: >>>> >>>> >>>>> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >>>>> to mount root fs on unknown-block(0,0)' >>>>> >>>>> >>>> Before you install the uImage and rootfs onto the MMC card, you need >>>> to rebuild those 2 images. Specifically, you need to make certain >>>> that >>>> you have built a kernel that can boot from the MMC card. Otherwise >>>> you >>>> will encounter the 'unknown-block(0,0)' error upon booting the >>>> gumstix >>>> from the MMC card. Modify gumstix-custom-verdex.conf to include >>>> mmcroot, ext2 and fat. >>>> >>>> Chuck >>>> >>>> >>> Thanks so much - ext2 and fat were enabled, but mmcroot was not. >>> I'm >>> rebuilding now! >>> >>> I'm using the microSD card (NOT the MMC as stated above!!!!). I >>> understand that mmcroot is used for the microSD also - IS THAT >>> CORRECT? >>> >>> .... BUT, get the same eror: >>> >> >> Don't worry, the 'mmcroot' setting covers both microSD and MMC cards. >> Note the message in the bootup log: >> Booting from mmc/microSD... >> >> The only times I have received the 'unknown-block(0,0)' error is when >> I've made the 'mmcroot' setting incorrectly, or I copied the wrong >> uImage and rootfs to the microSD card. >> >> Make sure you edited the file located here and not some other version >> of it (the changes wouldn't get picked up): >> ~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix- >> custom-verdex.conf >> >> with the following line (NO whitespace at the beginning of the line): >> MACHINE_FEATURES += "mmcroot" >> >> Now, rebuild the images: >> bitbake -c rebuild task-base-gumstix >> bitbake -c rebuild gumstix-kernel >> bitbake -c rebuild gumstix-basic-image >> >> The products of this rebuild will be in this folder: >> ~/gumstix/gumstix-oe/tmp/deploy/glibc/images/gumstix-custom- >> verdex/ >> specifically: >> a. The uimage that goes into the FAT16 partition (mmcblk0p1) >> uImage-2.6.21-r1-gumstix-custom-verdex.bin >> b. The rootfs that goes into the ext2 partition (mmcblk0p2) >> gumstix-basic-image-gumstix-custom-verdex.rootfs.tar.gz >> >> Chuck >> >> >> ------------------------------------------------------------------------------ >> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >> production scanning environment may not be a perfect world - but thanks >> to >> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >> i700 >> Series Scanner you'll get full speed at 300 dpi even with all image >> processing features enabled. http://p.sf.net/sfu/kodak-com >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > SUCCESS!! Thank you so much, Chuck. > > The secret was the THREE bitbake commands you outlined (I had been > issuing only 'bitbake gumstix-basic-image') and the edit to > '~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix-custom-verdex.conf' > (which I had got right after your first email). > > > Now I can move on to code for my project: bringing in data over two > serial lines, storing it to the microSD card, and putting the Gumstix > into a deep sleep for a set period of time. I'll ask questions about > that in a separate topic. > > > Again, many thanks for setting me on the right path .... hope I can > contribute back to the group sometime. > > jim > > > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Trouble-booting-from-mmc-card-on-Verdex-pro-tp23414427p29700221.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Oswald B. <op...@sd...> - 2010-09-14 15:45:55
|
hi, following these instructions http://www.gumstix.net/wiki/index.php?title=Verdex_Git_Repository works fine for me now, except for the wifi driver issue (wdi), like libertas complaining about watchdog timeouts and refusing to work. so $ bitbake verdex-console-image results in a bootable 2.6.31 system. because of the wdi i'm using 2.6.21 with a default image onto which i installed various newer packages out of my build. uImage and modules are here: http://www2.informatik.hu-berlin.de/~oberthol/QK/gumstix/2.6.21-mmcboot/ filesystem from here: http://www.gumstix.net/feeds/current/glibc/images/gumstix-custom-verdex/Angstrom-gumstix-basic-image-glibc-ipk-2007.9-test-20080512-gumstix-custom-verdex.rootfs.tar.gz i had to modify bootcmd in uboot to issue mmcinit twice. which seems to be a known issue. subversion based gumstix-oe seems to be defunct. maybe that site (http://www.gumstix.net/Setup-and-Programming/view/Getting-started/Setting-up-a-build-environment/111.html) should be taken offline. bst, opt arm_555 <ar...@pe...> writes: > Hi guys, > > I'm a newbie! I follow this page on how to boot a Verdex from microsd > (http://www.gumstix.net/User-How-To-s/view/User-How-To-s/Booting-from-microSD/SD/MMC/110.html) > I'm trying to download kernel from > www.sakoman.net/oe/mmc-boot/kernel-mmc.tar.gz and rootfs from > www.sakoman.net/oe/mmc-boot/rootfs-mmc.tar.gz but the link seem to be > broken. Anyone know where I can download the kernel and rootfs files from? > > Thank you, > > Arm > > jdoutt wrote: >> >> >> >> Chuck Randall wrote: >>> On May 6, 2009, at 6:05 PM, Jim Doutt wrote: >>> >>>> Chuck Randall wrote: >>>> >>>>> On May 6, 2009, at 1:04 PM, jdoutt wrote: >>>>> >>>>> >>>>>> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >>>>>> to mount root fs on unknown-block(0,0)' >>>>>> >>>>>> >>>>> Before you install the uImage and rootfs onto the MMC card, you need >>>>> to rebuild those 2 images. Specifically, you need to make certain >>>>> that >>>>> you have built a kernel that can boot from the MMC card. Otherwise >>>>> you >>>>> will encounter the 'unknown-block(0,0)' error upon booting the >>>>> gumstix >>>>> from the MMC card. Modify gumstix-custom-verdex.conf to include >>>>> mmcroot, ext2 and fat. >>>>> >>>>> Chuck >>>>> >>>>> >>>> Thanks so much - ext2 and fat were enabled, but mmcroot was not. >>>> I'm >>>> rebuilding now! >>>> >>>> I'm using the microSD card (NOT the MMC as stated above!!!!). I >>>> understand that mmcroot is used for the microSD also - IS THAT >>>> CORRECT? >>>> >>>> .... BUT, get the same eror: >>>> >>> >>> Don't worry, the 'mmcroot' setting covers both microSD and MMC cards. >>> Note the message in the bootup log: >>> Booting from mmc/microSD... >>> >>> The only times I have received the 'unknown-block(0,0)' error is when >>> I've made the 'mmcroot' setting incorrectly, or I copied the wrong >>> uImage and rootfs to the microSD card. >>> >>> Make sure you edited the file located here and not some other version >>> of it (the changes wouldn't get picked up): >>> ~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix- >>> custom-verdex.conf >>> >>> with the following line (NO whitespace at the beginning of the line): >>> MACHINE_FEATURES += "mmcroot" >>> >>> Now, rebuild the images: >>> bitbake -c rebuild task-base-gumstix >>> bitbake -c rebuild gumstix-kernel >>> bitbake -c rebuild gumstix-basic-image >>> >>> The products of this rebuild will be in this folder: >>> ~/gumstix/gumstix-oe/tmp/deploy/glibc/images/gumstix-custom- >>> verdex/ >>> specifically: >>> a. The uimage that goes into the FAT16 partition (mmcblk0p1) >>> uImage-2.6.21-r1-gumstix-custom-verdex.bin >>> b. The rootfs that goes into the ext2 partition (mmcblk0p2) >>> gumstix-basic-image-gumstix-custom-verdex.rootfs.tar.gz >>> >>> Chuck >>> >>> >>> ------------------------------------------------------------------------------ >>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >>> production scanning environment may not be a perfect world - but thanks >>> to >>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >>> i700 >>> Series Scanner you'll get full speed at 300 dpi even with all image >>> processing features enabled. http://p.sf.net/sfu/kodak-com >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> >> SUCCESS!! Thank you so much, Chuck. >> >> The secret was the THREE bitbake commands you outlined (I had been >> issuing only 'bitbake gumstix-basic-image') and the edit to >> '~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix-custom-verdex.conf' >> (which I had got right after your first email). >> >> >> Now I can move on to code for my project: bringing in data over two >> serial lines, storing it to the microSD card, and putting the Gumstix >> into a deep sleep for a set period of time. I'll ask questions about >> that in a separate topic. >> >> >> Again, many thanks for setting me on the right path .... hope I can >> contribute back to the group sometime. >> >> jim >> >> >> >> >> ------------------------------------------------------------------------------ >> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >> production scanning environment may not be a perfect world - but thanks to >> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >> i700 >> Series Scanner you'll get full speed at 300 dpi even with all image >> processing features enabled. http://p.sf.net/sfu/kodak-com >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> -- Sent from |
From: arm_555 <ar...@pe...> - 2010-09-15 15:03:03
|
hi Thank you so much for the codes. Look like it takes so long time for me too boot up (It gets stuck at "Configuring update-modules") and when I log in and untar, it take a long time as well. Is that anyway I can make the process faster? Thank you, Arm Oswald Berthold-5 wrote: > > > hi, > > following these instructions > > http://www.gumstix.net/wiki/index.php?title=Verdex_Git_Repository > > works fine for me now, except for the wifi driver issue (wdi), like > libertas complaining about watchdog timeouts and refusing to work. > > so > > $ bitbake verdex-console-image > > results in a bootable 2.6.31 system. > > because of the wdi i'm using 2.6.21 with a default image onto which i > installed various newer packages out of my build. > > uImage and modules are here: > http://www2.informatik.hu-berlin.de/~oberthol/QK/gumstix/2.6.21-mmcboot/ > > filesystem from here: > http://www.gumstix.net/feeds/current/glibc/images/gumstix-custom-verdex/Angstrom-gumstix-basic-image-glibc-ipk-2007.9-test-20080512-gumstix-custom-verdex.rootfs.tar.gz > > > i had to modify bootcmd in uboot to issue mmcinit twice. which seems to > be a known issue. > > subversion based gumstix-oe seems to be defunct. maybe that site > (http://www.gumstix.net/Setup-and-Programming/view/Getting-started/Setting-up-a-build-environment/111.html) > should be taken offline. > > bst, opt > > > arm_555 <ar...@pe...> writes: > >> Hi guys, >> >> I'm a newbie! I follow this page on how to boot a Verdex from microsd >> (http://www.gumstix.net/User-How-To-s/view/User-How-To-s/Booting-from-microSD/SD/MMC/110.html) >> I'm trying to download kernel from >> www.sakoman.net/oe/mmc-boot/kernel-mmc.tar.gz and rootfs from >> www.sakoman.net/oe/mmc-boot/rootfs-mmc.tar.gz but the link seem to be >> broken. Anyone know where I can download the kernel and rootfs files >> from? >> >> Thank you, >> >> Arm >> >> jdoutt wrote: >>> >>> >>> >>> Chuck Randall wrote: >>>> On May 6, 2009, at 6:05 PM, Jim Doutt wrote: >>>> >>>>> Chuck Randall wrote: >>>>> >>>>>> On May 6, 2009, at 1:04 PM, jdoutt wrote: >>>>>> >>>>>> >>>>>>> Boot from mmc card gives: 'Kernel panic - not syncing: VFS: Unable >>>>>>> to mount root fs on unknown-block(0,0)' >>>>>>> >>>>>>> >>>>>> Before you install the uImage and rootfs onto the MMC card, you need >>>>>> to rebuild those 2 images. Specifically, you need to make certain >>>>>> that >>>>>> you have built a kernel that can boot from the MMC card. Otherwise >>>>>> you >>>>>> will encounter the 'unknown-block(0,0)' error upon booting the >>>>>> gumstix >>>>>> from the MMC card. Modify gumstix-custom-verdex.conf to include >>>>>> mmcroot, ext2 and fat. >>>>>> >>>>>> Chuck >>>>>> >>>>>> >>>>> Thanks so much - ext2 and fat were enabled, but mmcroot was not. >>>>> I'm >>>>> rebuilding now! >>>>> >>>>> I'm using the microSD card (NOT the MMC as stated above!!!!). I >>>>> understand that mmcroot is used for the microSD also - IS THAT >>>>> CORRECT? >>>>> >>>>> .... BUT, get the same eror: >>>>> >>>> >>>> Don't worry, the 'mmcroot' setting covers both microSD and MMC cards. >>>> Note the message in the bootup log: >>>> Booting from mmc/microSD... >>>> >>>> The only times I have received the 'unknown-block(0,0)' error is when >>>> I've made the 'mmcroot' setting incorrectly, or I copied the wrong >>>> uImage and rootfs to the microSD card. >>>> >>>> Make sure you edited the file located here and not some other version >>>> of it (the changes wouldn't get picked up): >>>> ~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix- >>>> custom-verdex.conf >>>> >>>> with the following line (NO whitespace at the beginning of the line): >>>> MACHINE_FEATURES += "mmcroot" >>>> >>>> Now, rebuild the images: >>>> bitbake -c rebuild task-base-gumstix >>>> bitbake -c rebuild gumstix-kernel >>>> bitbake -c rebuild gumstix-basic-image >>>> >>>> The products of this rebuild will be in this folder: >>>> ~/gumstix/gumstix-oe/tmp/deploy/glibc/images/gumstix-custom- >>>> verdex/ >>>> specifically: >>>> a. The uimage that goes into the FAT16 partition (mmcblk0p1) >>>> uImage-2.6.21-r1-gumstix-custom-verdex.bin >>>> b. The rootfs that goes into the ext2 partition (mmcblk0p2) >>>> gumstix-basic-image-gumstix-custom-verdex.rootfs.tar.gz >>>> >>>> Chuck >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! >>>> Your >>>> production scanning environment may not be a perfect world - but thanks >>>> to >>>> Kodak, there's a perfect scanner to get the job done! With the NEW >>>> KODAK >>>> i700 >>>> Series Scanner you'll get full speed at 300 dpi even with all image >>>> processing features enabled. http://p.sf.net/sfu/kodak-com >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> >>> SUCCESS!! Thank you so much, Chuck. >>> >>> The secret was the THREE bitbake commands you outlined (I had been >>> issuing only 'bitbake gumstix-basic-image') and the edit to >>> '~/gumstix/gumstix-oe/com.gumstix.collection/conf/machine/gumstix-custom-verdex.conf' >>> (which I had got right after your first email). >>> >>> >>> Now I can move on to code for my project: bringing in data over two >>> serial lines, storing it to the microSD card, and putting the Gumstix >>> into a deep sleep for a set period of time. I'll ask questions about >>> that in a separate topic. >>> >>> >>> Again, many thanks for setting me on the right path .... hope I can >>> contribute back to the group sometime. >>> >>> jim >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >>> production scanning environment may not be a perfect world - but thanks >>> to >>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >>> i700 >>> Series Scanner you'll get full speed at 300 dpi even with all image >>> processing features enabled. http://p.sf.net/sfu/kodak-com >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> > > -- > Sent from > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Trouble-booting-from-mmc-card-on-Verdex-pro-tp23414427p29718996.html Sent from the Gumstix mailing list archive at Nabble.com. |