Hi John, Thanks for the reply. My uImage checksum for uImage-r2borph3 agrees with yours. I do not have any uImage-current, and do not understand why there would be two uImages. I will assume you are running two different ROACH2 versions and that I should be using only the uImage-r2borph3 one, but please correct me if not.
I have the u-boot.bin (with the same checksum), but am not using it. I am confused about what steps I need to take, and thought I could just follow the same procedure for ROACH-1, but do I first have to update the u-boot as in these instructions? http://www.mail-archive.com/casper@lists.berkeley.edu/msg03351.html I actually tried it, but our network seems to be down at the moment. What about romfs? Is this only needed for soloboot? Thanks, Dale On Thu, Jun 6, 2013 at 4:44 AM, John Ford <jf...@nrao.edu> wrote: > In our R2 systems, we have the following kernel: > > root@vegasr2-2:~# uname -a > Linux vegasr2-2 3.7.0-rc2+ #20 Fri Jan 4 18:04:26 SAST 2013 ppc GNU/Linux > > I'm pretty sure the Roach-2 kernels are all 3.x. > > Can you get a checksum (md5sum) of the uimage? I think you have the right > one, but it may be too old. > > Yes, Master<1017> md5sum uImage-current > 300753db387044c3cb8f5f9d92c4fb37 uImage-current > > We also used the following: > Yes, Master<1018> md5sum uImage-r2borph3 > ac6feb36b96c410a336fb3103fafb82c uImage-r2borph3 > > Our uboot is: > > Yes, Master<1022> md5sum u-boot.bin > e396454ffa9d1e2dcbf87abf9eafccba u-boot.bin > > Hope this helps! > > John > > > Posting on behalf of Dale. Please see the message below. > > > > Thanks, > > > > Nimish > > > > > > ---------- Forwarded message ---------- > > From: "Gary, Dale E." <dale.e.g...@njit.edu> > > To: casper list <casper@lists.berkeley.edu> > > Cc: > > Date: Thu, 6 Jun 2013 00:40:25 +0000 > > Subject: netbooting ROACH2 > > Hi Casperites, > > > > I am setting up a ROACH2 rev2 for netbooting, and I think I am almost > > there, but the ROACH hangs during the boot process, which suggests either > > a > > setup problem or the wrong Image or filesystem. The uImage is > > uImage-r2borph3, and the filesystem is > > roach2-debian-fs-snapshot-24-10-2012.tar.gz. According to the output > > during the boot process (see below), I appear to have bootp and tftp set > > up > > correctly. Can anyone spot the problem based on this information, or > > suggest a way to get more information on what might have gone wrong? > > Perhaps something to do with the USB device? > > > > Thanks, > > Dale > > > > =======Output of boot process======== > > Waiting for PHY auto negotiation to complete.... done > > ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0) > > BOOTP broadcast 1 > > DHCP client bound to address 192.168.24.121 > > Using ppc_4xx_eth0 device > > TFTP from server 192.100.16.206; our IP address is 192.168.24.121; > sending > > through gateway 192.168.24.1 > > Filename 'uImage'. > > Load address: 0x4000000 > > Loading: > ################################################################# > > > ################################################################# > > > ################################################################# > > > ################################################################# > > ############ > > done > > Bytes transferred = 1390149 (153645 hex) > > ## Booting kernel from Legacy Image at 04000000 ... > > Image Name: Linux-2.6.25-svn3489 > > Image Type: PowerPC Linux Kernel Image (gzip compressed) > > Data Size: 1390085 Bytes = 1.3 MiB > > 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 -> 131071 > > Normal 131071 -> 131071 > > Movable zone start PFN for each node > > early_node_map[1] active PFN ranges > > 0: 0 -> 131071 > > Built 1 zonelists in Zone order, mobility grouping on. Total pages: > > 130048 > > Kernel command line: console=ttyS0,115200 root=/dev/nfs > > rootpath=192.100.16.206:/srv/roach2_boot/etch ip=dhcp > > PID hash table entries: 2048 (order: 11, 8192 bytes) > > console [ttyS0] enabled > > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > > Memory: 516608k 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: 4096 (order: 2, 16384 bytes) > > TCP established hash table entries: 16384 (order: 5, 131072 bytes) > > TCP bind hash table entries: 16384 (order: 4, 65536 bytes) > > TCP: Hash tables configured (established 16384 bind 16384) > > 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:44:01:02:05:06 > > eth0: found Marvell 88E1111 Ethernet PHY (0x01) > > rgmii0: input 1 in RGMII mode > > eth1: emac1, MAC 00:00:03:f9:40:ab > > eth1: found Marvell 88E1111 Ethernet PHY (0x07) > > 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: 08000000 at f8000000 > > 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. > > RedBoot partition parsing not available > > Using physmap partition information > > Creating 5 MTD partitions on "physmap-flash.0": > > 0x00000000-0x00180000 : "kernel" > > 0x00180000-0x00400000 : "root" > > 0x00400000-0x07f60000 : "user" > > 0x07f60000-0x07fa0000 : "env" > > 0x07fa0000-0x08000000 : "u-boot" > > 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 > > > > >
