Hi All,

   I set the link to 100MBPS as well as 10mbps and tried its giving me the
same result.

thanks.
Nishanth

Here is the screen shot



U-Boot 2008.10-svn3231 (Jul 15 2010 - 14:58:38)

CPU:   AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133, OPB=66, EBC=66
MHz)
       No Security/Kasumi support
       Bootstrap Option C - Boot ROM Location EBC (16 bits)
       32 kB I-Cache 32 kB D-Cache
Board: Roach
I2C:   ready
DTT:   1 FAILED INIT
DRAM:  (spd v1.2) dram: notice: ecc ignored
 1 GB
FLASH: 64 MB
USB:   Host(int phy) Device(ext phy)
Net:   ppc_4xx_eth0

Roach Information
Serial Number:    040114
Monitor Revision: 8.3.1698
CPLD Revision:    8.0.1588

type run netboot to boot via dhcp+tftp+nfs
type run soloboot to run from flash without network
type run mmcboot to boot using filesystem on mmc/sdcard
type run usbboot to boot using filesystem on usb
type run bit to run tests

Hit any key to stop autoboot:  0
Waiting for PHY auto negotiation to complete.. done
ENET Speed is 10 Mbps - FULL duplex connection (EMAC0)
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 28
DHCP client bound to address 192.168.70.9
Using ppc_4xx_eth0 device
TFTP from server 192.168.70.1; our IP address is 192.168.70.9
Filename 'uImage'.
Load address: 0x400000
Loading: #################################################################
         ##############################
done
Bytes transferred = 1390149 (153645 hex)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 00400000 ...
   Image Name:   Linux-2.6.25-svn3489
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1390085 Bytes =  1.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
ocp: exit
arch: exit
Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri Aug
12 09:36:28 SAST 2011
AMCC PowerPC 440EPx Roach Platform
Zone PFN ranges:
  DMA             0 ->   262143
  Normal     262143 ->   262143
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   262143
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
Kernel command line: console=ttyS0,115200
mtdparts=physmap-flash.0:1792k(linux),256k@0x1c0000(fdtp
PID hash table entries: 4096 (order: 12, 16384 bytes)
console [ttyS0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1036416k available (2084k kernel code, 720k data, 132k init, 0k
highmem)
Mount-cache hash table entries: 512
BORPH version CVS-$Revision: 1.10 $ Initialized
net_namespace: 152 bytes
NET: Registered protocol family 16

PCI: Probing PCI hardware
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: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
hwrtype_roach version CVS-$Revision: 1.1 $ registered
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A
serial8250: ttyS2 at MMIO 0x0 (irq = 35) is a 16550A
serial8250: ttyS3 at MMIO 0x0 (irq = 36) is a 16550A
brd: module loaded
PPC 4xx OCP EMAC driver, version 3.54
mal0: initialized, 2 TX channels, 2 RX channels
rgmii0: input 0 in RGMII mode
eth0: emac0, MAC 02:00:00:04:01:14
eth0: found Generic MII PHY (0x1e)
rgmii0: input 1 in RGMII mode
emac1: can't find PHY!
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <m...@qualcomm.com>
Driver 'sd' needs updating - please use bus_type methods
physmap platform flash device: 04000000 at fc000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
mtd: bad character after partition (f)
6 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x001c0000 : "linux"
0x001c0000-0x00200000 : "fdt"
0x00200000-0x00a00000 : "root"
0x00a00000-0x03f60000 : "usr"
0x03f60000-0x03fa0000 : "env"
0x03fa0000-0x04000000 : "uboot"
ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller
ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1
ppc-soc-ohci ppc-soc-ohci.0: irq 21, io mem 0xe0000400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
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: USB Host Controller
usb usb1: Manufacturer: Linux 2.6.25-svn3489 ohci_hcd
usb usb1: SerialNumber: PPC-SOC USB
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i2c /dev entries driver
IBM IIC driver v2.1
ibm-iic0: using standard (100 kHz) mode
ibm-iic1: using standard (100 kHz) mode
rmon: found Roach Monitor - Rev 8.3.1698
rmon_sensors: initialized 23 sensors
rmon 0-000f: rtc core: registered rmon as rtc0
roach_mmc: Roach MMC/SD driver
rmmc: initialized mmc
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rmon 0-000f: setting system clock to 2090-01-30 08:58:02 UTC (3789449882)
eth0: interrupt coalescing (RX:count=8 time=1000, TX:count=8 time=1000)
eth0: link is down
eth0: link is up, 10 FDX, pause enabled
Sending DHCP requests .., OK
IP-Config: Got DHCP answer from 192.168.70.1, my address is 192.168.70.9
IP-Config: Complete:
     device=eth0, addr=192.168.70.9, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.70.9, domain=, nis-domain=(none),
     bootserver=192.168.70.1, rootserver=192.168.70.1,
rootpath=/home/nfs/roach1/current,nolock
Looking up port of RPC 100003/2 on 192.168.70.1
Looking up port of RPC 100005/1 on 192.168.70.1
Root-NFS: Server returned error -13 while mounting /home/nfs/roach1/current
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "192.168.70.1:/home/nfs/roach1/current,nolock"
or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available
partitions:
0100       4096 ram0 (driver?)
0101       4096 ram1 (driver?)
0102       4096 ram2 (driver?)
0103       4096 ram3 (driver?)
0104       4096 ram4 (driver?)
0105       4096 ram5 (driver?)
0106       4096 ram6 (driver?)
0107       4096 ram7 (driver?)
0108       4096 ram8 (driver?)
0109       4096 ram9 (driver?)
010a       4096 ram10 (driver?)
010b       4096 ram11 (driver?)
010c       4096 ram12 (driver?)
010d       4096 ram13 (driver?)
010e       4096 ram14 (driver?)
010f       4096 ram15 (driver?)
1f00       1792 mtdblock0 (driver?)
1f01        256 mtdblock1 (driver?)
1f02       8192 mtdblock2 (driver?)
1f03      54656 mtdblock3 (driver?)
1f04        256 mtdblock4 (driver?)
1f05        384 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
Rebooting in 180 seconds..








On Fri, May 8, 2015 at 10:40 PM, 李健@xao <lij...@xao.ac.cn> wrote:

> !?!?
> --
> 这是通过Aico Mail手机客户端发送的邮件。Aico Mail旨在丰富人们的沟通与生活,提供全新的移动办公体验。
>
> John Ford  写到:
>
> Hi.
>>
>> error 13 is permission denied.  Probably your exports file isn't quite
>> right.  Note that you have to allow root permission on the mount.
>> Something like this should be in /etc/exports:
>>
>> /home/nfs/roach1/current 192.168.40.0/24(sync,rw,no_root_squash)
>>
>> John
>>
>>
>> > Hi All,
>> >
>> >    I used the usb wriggler and ito load the bootloader and now I am seeing
>> > data comming out of the serial terminal as before.
>> > But the roach is still not booting properly. I am trying to boot the roach
>> > through nfs boot and I am seeing this at the terminal. Please can any tell
>> > me how to fix this error.
>> >
>> > Thanks
>> > Nishanth
>> >
>> > U-Boot 2008.10-svn3231 (Jul 15 2010 - 14:58:38)
>> >
>> > CPU:   AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133, OPB=66, EBC=66
>> > MHz)
>> >        No Security/Kasumi support
>> >        Bootstrap Option C - Boot ROM Location EBC (16 bits)
>> >        32 kB I-Cache 32 kB D-Cache
>> > Board: Roach
>> > I2C:   ready
>> > DTT:   1 FAILED INIT
>> > DRAM:  (spd v1.2) dram: notice: ecc ignored
>> >  1 GB
>> > FLASH: 64 MB
>> > USB:   Host(int phy) Device(ext phy)
>> > Net:   ppc_4xx_eth0
>> >
>> > Roach Information
>> > Serial Number:    040114
>> > Monitor Revision: 8.3.1698
>> > CPLD Revision:    8.0.1588
>> >
>> > type run netboot to boot via dhcp+tftp+nfs
>> > type run soloboot to run from flash without network
>> > type run mmcboot to boot using filesystem on mmc/sdcard
>> > type run usbboot to boot using filesystem on usb
>> > type run bit to run tests
>> >
>> > Hit any key to stop autoboot:  0
>> > Waiting for PHY auto negotiation to complete.... done
>> > ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
>> > BOOTP broadcast 1
>> > *** Unhandled DHCP Option in OFFER/ACK: 28
>> > *** Unhandled DHCP Option in OFFER/ACK: 28
>> > DHCP client bound to address 192.168.40.8
>> > Using ppc_4xx_eth0 device
>> > TFTP from server 192.168.40.1; our IP address is 192.168.40.8
>> > Filename 'uImage'.
>> > Load address: 0x400000
>> > Loading: #################################################################
>> >          ##############################
>> > done
>> > Bytes transferred = 1390149 (153645 hex)
>> > WARNING: adjusting available memory to 30000000
>> > ## Booting kernel from Legacy Image at 00400000 ...
>> >    Image Name:   Linux-2.6.25-svn3489
>> >    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>> >    Data Size:    1390085 Bytes =  1.3 MB
>> >    Load Address: 00000000
>> >    Entry Point:  00000000
>> >    Verifying Checksum ... OK
>> >    Uncompressing Kernel Image ... OK
>> > id mach(): done
>> > MMU:enter
>> > MMU:hw init
>> > MMU:mapin
>> > MMU:setio
>> > MMU:exit
>> > setup_arch: enter
>> > setup_arch: bootmem
>> > ocp: exit
>> > arch: exit
>> > Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri Aug
>> > 12 09:36:28 SAST 2011
>> > AMCC PowerPC 440EPx Roach Platform
>> > Zone PFN ranges:
>> >   DMA             0 ->   262143
>> >   Normal     262143 ->   262143
>> > Movable zone start PFN for each node
>> > early_node_map[1] active PFN ranges
>> >     0:        0 ->   262143
>> > Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
>> > 260096
>> > Kernel command line: console=ttyS0,115200
>> > mtdparts=physmap-flash.0:1792k(linux),256k@0x1c0000(fdt),8192k@0x200000
>> > (root),p
>> > PID hash table entries: 4096 (order: 12, 16384 bytes)
>> > console [ttyS0] enabled
>> > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>> > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>> > Memory: 1036416k available (2084k kernel code, 720k data, 132k init, 0k
>> > highmem)
>> > Mount-cache hash table entries: 512
>> > BORPH version CVS-$Revision: 1.10 $ Initialized
>> > net_namespace: 152 bytes
>> > NET: Registered protocol family 16
>> >
>> > PCI: Probing PCI hardware
>> > 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: 32768 (order: 5, 131072 bytes)
>> > TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
>> > TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
>> > TCP: Hash tables configured (established 131072 bind 65536)
>> > TCP reno registered
>> > hwrtype_roach version CVS-$Revision: 1.1 $ registered
>> > JFFS2 version 2.2. (NAND) ??????? 2001-2006 Red Hat, Inc.
>> > io scheduler noop registered (default)
>> > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
>> > serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A
>> > serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A
>> > serial8250: ttyS2 at MMIO 0x0 (irq = 35) is a 16550A
>> > serial8250: ttyS3 at MMIO 0x0 (irq = 36) is a 16550A
>> > brd: module loaded
>> > PPC 4xx OCP EMAC driver, version 3.54
>> > mal0: initialized, 2 TX channels, 2 RX channels
>> > rgmii0: input 0 in RGMII mode
>> > eth0: emac0, MAC 02:00:00:04:01:14
>> > eth0: found Generic MII PHY (0x1e)
>> > rgmii0: input 1 in RGMII mode
>> > emac1: can't find PHY!
>> > tun: Universal TUN/TAP device driver, 1.6
>> > tun: (C) 1999-2004 Max Krasnyansky
>>
>> > Driver 'sd' needs updating - please use bus_type methods
>> > physmap platform flash device: 04000000 at fc000000
>> > physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
>> >  Amd/Fujitsu Extended Query Table at 0x0040
>> > physmap-flash.0: CFI does not contain boot bank location. Assuming top.
>> > number of CFI chips: 1
>> > cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
>> > mtd: bad character after partition (f)
>> > 6 cmdlinepart partitions found on MTD device physmap-flash.0
>> > Creating 6 MTD partitions on "physmap-flash.0":
>> > 0x00000000-0x001c0000 : "linux"
>> > 0x001c0000-0x00200000 : "fdt"
>> > 0x00200000-0x00a00000 : "root"
>> > 0x00a00000-0x03f60000 : "usr"
>> > 0x03f60000-0x03fa0000 : "env"
>> > 0x03fa0000-0x04000000 : "uboot"
>> > ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller
>> > ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1
>> > ppc-soc-ohci ppc-soc-ohci.0: irq 21, io mem 0xe0000400
>> > usb usb1: configuration #1 chosen from 1 choice
>> > hub 1-0:1.0: USB hub found
>> > hub 1-0:1.0: 1 port detected
>> > 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: USB Host Controller
>> > usb usb1: Manufacturer: Linux 2.6.25-svn3489 ohci_hcd
>> > usb usb1: SerialNumber: PPC-SOC USB
>> > Initializing USB Mass Storage driver...
>> > usbcore: registered new interface driver usb-storage
>> > USB Mass Storage support registered.
>> > i2c /dev entries driver
>> > IBM IIC driver v2.1
>> > ibm-iic0: using standard (100 kHz) mode
>> > ibm-iic1: using standard (100 kHz) mode
>> > rmon: found Roach Monitor - Rev 8.3.1698
>> > rmon_sensors: initialized 23 sensors
>> > rmon 0-000f: rtc core: registered rmon as rtc0
>> > roach_mmc: Roach MMC/SD driver
>> > rmmc: initialized mmc
>> > TCP cubic registered
>> > NET: Registered protocol family 1
>> > NET: Registered protocol family 17
>> > RPC: Registered udp transport module.
>> > RPC: Registered tcp transport module.
>> > rmon 0-000f: setting system clock to 2090-01-27 17:36:25 UTC (3789221785)
>> > eth0: interrupt coalescing (RX:count=8 time=1000, TX:count=8 time=1000)
>> > eth0: link is down
>> > Sending DHCP requests .<6>eth0: link is up, 1000 FDX, pause enabled
>> > ., OK
>> > IP-Config: Got DHCP answer from 192.168.40.1, my address is 192.168.40.8
>> > IP-Config: Complete:
>> >      device=eth0, addr=192.168.40.8, mask=255.255.255.0,
>> > gw=255.255.255.255,
>> >      host=roach, domain=, nis-domain=(none),
>> >      bootserver=192.168.40.1, rootserver=192.168.40.1,
>> > rootpath=/home/nfs/roach1/current,nolock
>> > Looking up port of RPC 100003/2 on 192.168.40.1
>> > Looking up port of RPC 100005/1 on 192.168.40.1
>> > Root-NFS: Server returned error -13 while mounting
>> > /home/nfs/roach1/current
>> > VFS: Unable to mount root fs via NFS, trying floppy.
>> > VFS: Cannot open root device
>> > "192.168.40.1:/home/nfs/roach1/current,nolock"
>> > or unknown-block(2,0)
>> > Please append a correct "root=" boot option; here are the available
>> > partitions:
>> > 0100       4096 ram0 (driver?)
>> > 0101       4096 ram1 (driver?)
>> > 0102       4096 ram2 (driver?)
>> > 0103       4096 ram3 (driver?)
>> > 0104       4096 ram4 (driver?)
>> > 0105       4096 ram5 (driver?)
>> > 0106       4096 ram6 (driver?)
>> > 0107       4096 ram7 (driver?)
>> > 0108       4096 ram8 (driver?)
>> > 0109       4096 ram9 (driver?)
>> > 010a       4096 ram10 (driver?)
>> > 010b       4096 ram11 (driver?)
>> > 010c       4096 ram12 (driver?)
>> > 010d       4096 ram13 (driver?)
>> > 010e       4096 ram14 (driver?)
>> > 010f       4096 ram15 (driver?)
>> > 1f00       1792 mtdblock0 (driver?)
>> > 1f01        256 mtdblock1 (driver?)
>> > 1f02       8192 mtdblock2 (driver?)
>> > 1f03      54656 mtdblock3 (driver?)
>> > 1f04        256 mtdblock4 (driver?)
>> > 1f05        384 mtdblock5 (driver?)
>> > Kernel panic - not syncing: VFS: Unable to mount root fs on
>> > unknown-block(2,0)
>> > Rebooting in 180 seconds..
>> >
>> >
>> >
>> > On Tue, May 5, 2015 at 7:49 AM, Nishanth Shivashankaran
>>
>> > wrote:
>> >
>> >> HI Marc,
>> >>      Thank you for the reply, I am not seeing anything on the serial
>> >> terminal. I have ordered a macraigor wiggler, I will try using that and
>> >> see
>> >> if the roach starts working.
>> >>
>> >> Thanks and regards,
>> >> Nishanth
>> >>
>> >> On Mon, May 4, 2015 at 12:28 AM, Marc Welz  wrote:
>> >>
>> >>>
>> >>>
>> >>> On Wed, Apr 29, 2015 at 10:49 PM, Nishanth Shivashankaran <
>> >>> nshiv...@asu.edu> wrote:
>> >>>
>> >>>> Hi All,
>> >>>>
>> >>>>     We bought a new desktop and I tried installing nfs boot on to the
>> >>>> new computer to boot the roach1 and  was trying to bring the roach1
>> >>>> up. But
>> >>>> I think I messed up installing something somewhere and the roach 1 is
>> >>>> not
>> >>>> returning anything to the minicom terminal at all.
>> >>>>
>> >>>> I am sure it is connected to the right port because I can see it on
>> >>>> the
>> >>>> terminal using dmesg command.
>> >>>>
>> >>>
>> >>> If you can see serial text output, then chances are very good that your
>> >>> bootloader
>> >>> is still working. Have you tried pressing any key during bootup, to see
>> >>> if you can reach the
>> >>> bootloader prompt - if you can type "printenv" then uboot is still
>> >>> functional, and there is
>> >>> no need to resort to jtag
>> >>>
>> >>> regards
>> >>>
>> >>> marc
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Nishanth Shivashankaran
>> >> Arizona State University
>> >> Phone:-480-246-6866
>>
>> >> Email:nshiv...@asu.edu
>> >>
>> >
>> >
>> >
>> > --
>> > Nishanth Shivashankaran
>> > Arizona State University
>> > Phone:-480-246-6866
>> > Email:nshiv...@asu.edu
>> >
>>
>>
>>
>>
>>
>>


-- 
Nishanth Shivashankaran
Arizona State University
Phone:-480-246-6866
Email:nshiv...@asu.edu

Reply via email to