Hi -
--- In , Xiang Lu <> wrote:
>
> Dear Charles,
>
> I found a file, called as "ts7250_nand-new-partition-table.patch". Do you mean
> this patch? Should I patch this file after the default path script? Thank you.
>
> Best Regards,
> Xiang
Yes that sounds right. Just apply that patch after you apply Matthieu's patch set. If you have trouble, just apply it by hand, it is small.
To be clear, this is not related to your NFS booting problems. More information about the kernel parameter 'nfsroot= ...' are in the linux kernel source tree ./linux-2.6.xx/Documentation/filesystems/nfsroot.txt. You may have to add things like default gateway, netmask, etc. for the client.
regards, .......... Charlie
>
>
>
> ________________________________
> From: Xiang Lu <>
> To:
> Sent: Fri, July 16, 2010 1:11:15 AM
> Subject: Re: [ts-7000] Re: problem about mount nfsroot
>
>
> Dear Charles,
>
> Thank you for your suggestions. I am not sure about the way to get the nand
> partition patch. I am using Matthieu's patch for 2.6.32.3. You mean I should use
> an old version patch? My objective is to cross compile 2.6.32.3. Can I choose
> 2.6.34 patch for my 2.6.32 kernel to fix the nand partition patch? Or, should I
> abstract the partition related patch file in the 2.6.32 patch? Thank you for
> your further explanation.
>
> Best Regards,
> Xiang
>
>
>
> ________________________________
> From: Charles <charliem_1216@ yahoo.com>
> To: .com
> Sent: Fri, July 16, 2010 12:38:32 AM
> Subject: [ts-7000] Re: problem about mount nfsroot
>
>
>
> Hi --
>
> --- In .com, Xiang Lu <xlu_ncsu@> wrote:
> >
> > 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.embedded arm.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
>
> > 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
>
> You will need the nand partition patch later, to fix this. I think Matt has it
> now again, or you may have to get it from an old version of his patch set.
>
> > 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
>
> You are getting Err -13, which means 'permission denied'. Check that you have
> read access and write access to your nfsroot location. Probably even read
> access is missing; otherwise I believe it would mount and then get an error when
> trying to write to the rootfs.
>
> If you fix the permission issue, this rootfs should work OK, I think. No need
> to rebuild the rootfs for the permission issue.
>
> regards, ......... Charlie
>
> > 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)
> >
>