|
Dear all, I am trying to load a NFS Root file system from a NFS server after loading a new 2.6.32.3 kernel. But when I input the following command, I get the error information about "Unable to mount root fs via NFS". I googled the related messages. But I am not sure about the reasons of this problem. Now, I am using the root file system downloaded from the website of TS, http://www.embeddedarm.com/software/arm-linux-26-ts72xx.php. Should I manufacture my own root file system using busybox? Or, it is fine if I use the offered root file for 2.6.21 kernel? I posted the error information during my load process. I am a newbie for the embedded system. If my question is too naive, I am sorry for that. I really appreciate any comments, suggestions and instructions about the kernel update issue. Thank you so much. Best, Xiang RedBoot> exec -c "console=ttyAM0,115200 ip=dhcp nfsroot=152.14.97.29:/tftpboot/tmp Unbalanced string! Using base address 0x00218000 and length 0x001e4170 Uncompressing Linux..................................................................................... Linux version 2.6.32.3-m (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #1 P0 CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=40007177 CPU: VIVT data cache, VIVT instruction cache Machine: Technologic Systems TS-72xx SBC Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 9040 Kernel command line: console=ttyAM0,115200 ip=dhcp nfsroot=152.14.97.29:/tftpboot/tmp PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 8MB 8MB 8MB 8MB 8MB 8MB 8MB 8MB = 64MB total Memory: 60748KB available (3552K code, 298K data, 112K init, 0K highmem) Hierarchical RCU implementation. NR_IRQS:120 VIC @fefb0000: id 0x00041190, vendor 0x41 VIC @fefc0000: id 0x00041190, vendor 0x41 Console: colour dummy device 80x30 Calibrating delay loop... 99.73 BogoMIPS (lpj=498688) Security Framework initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 ep93xx: PLL1 running at 400 MHz, PLL2 at 192 MHz ep93xx: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz M2P DMA subsystem initialized bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 118 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: AMBA driver apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA console [ttyAM0] enabled apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA Searching for NAND flash... NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 0 at 0x000000000000 Bad eraseblock 13 at 0x0000001a0000 Bad eraseblock 1001 at 0x000007d20000 Bad eraseblock 1002 at 0x000007d40000 cmdlinepart partition parsing not available Using static partition definition Creating 3 MTD partitions on "ts7250-nand": 0x000000000000-0x000000004000 : "TS-BOOTROM" mtd: partition "TS-BOOTROM" doesn't end on an erase block -- force read-only 0x000000004000-0x000007d04000 : "Linux" mtd: partition "Linux" doesn't start on an erase block boundary -- force read-only 0x000007d04000-0x000008000000 : "RedBoot" mtd: partition "RedBoot" doesn't start on an erase block boundary -- force read-only ep93xx-eth version 0.12 loading eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:41:89:85. ep93xx_mii_bus: probed Generic PHY 0:01: PHY supports MII frame preamble suppression net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1) net eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:41:89:85 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ep93xx-ohci ep93xx-ohci: EP93xx OHCI ep93xx-ohci ep93xx-ohci: new USB bus registered, assigned bus number 1 ep93xx-ohci ep93xx-ohci: irq 56, io mem 0x80020000 usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EP93xx OHCI usb usb1: Manufacturer: Linux 2.6.32.3-m ohci_hcd usb usb1: SerialNumber: ep93xx usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc0 rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1 rtc-m48t86 rtc-m48t86: battery exhausted i2c-gpio i2c-gpio.0: using pins 14 (SDA) and 15 (SCL) cpuidle: using governor ladder Registered led device: platform:grled Registered led device: platform:rdled usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 17 rtc-m48t86 rtc-m48t86: hctosys: invalid date/time usb 1-3: new full speed USB device using ep93xx-ohci and address 2 usb 1-3: New USB device found, idVendor=0ace, idProduct=1215 usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=0 usb 1-3: Product: USB2.0 WLAN usb 1-3: Manufacturer: ZyDAS usb 1-3: configuration #1 chosen from 1 choice Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 152.14.97.47 IP-Config: Complete: device=eth0, addr=152.14.97.47, mask=255.255.254.0, gw=152.14.96.1, host=ts7250-eb2-3042-1, domain=ece.ncsu.edu, nis-domain=(none), bootserver=0.0.0.0, rootserver=152.14.97.29, rootpath= Looking up port of RPC 100003/2 on 152.14.97.29 Looking up port of RPC 100005/1 on 152.14.97.29 Root-NFS: Server returned error -13 while mounting /tftpboot/tmp VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "<NULL>" or unknown-block(2,0) Please append a correct "root=" boot option; here are the available partitions: 1f00 16 mtdblock0 (driver?) 1f01 128000 mtdblock1 (driver?) 1f02 3056 mtdblock2 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) __._,_.___
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe __,_._,___ |