Jason, Thanks for the comments. The 2nd issue has been solved. I thinks that is all because I'm using an old hub which is not functioning properly. Once I changed it with a new switch, the network works fine.
The first issue remains. I didn't mean I was confusing the read-only file system when booting from the flash. Even if I boot from usb stick, I still got a read-only file system. I have to fix it by typing the command: "mount -n -o remount /" I'm using a 2G usb stick. I prepared it using the following command: --------------------------------------------------------------------- fdisk /dev/sda --- to create partition1 mke2fs -t ext2 /dev/sda1 --- format to ext2 file system ---------------------------------------------------------------------- Then I downloaded the file system from http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/filesystem/filesystem_etch_nfs_2009_07_07.tar.gz I unzipped it and copied to my usb stick. I also checked and fixed the file system using: e2fsck -p /dev/sda1 But eventually the root was still mounted read-only file system when booting from usb stick. Any idea? Best Regards, -- Zhiwei Liu On Wed, Jul 15, 2009 at 12:52 PM, Jason Manley <[email protected]>wrote: > Hi Zhiwei > > Congratulations on getting your ROACH and booting it successfully! comments > below... > > 1) when I try to mount /dev/sda1 (the usb stick) as root filesystem, by >> interrupting boot from flash, and "run usbboot". >> The file system is mounted read-only. please see the attached message file >> (read_only_error.log) >> Although I can remount the / to R/W by typing the following command: >> mount -n -o remount / >> But I'm wondering does this affect anything? Is there any way to get >> across this. >> > This is the standard arrangement. The flash filesystem is there basically > for emergencies and basic testing. It is tiny, though there is a separate > partition for user stuff that you can write to. If you want a full install I > highly recommend you mount the Debian Etch filesystem either with a USB > flash stick, or over the network. This way you will have a full, standard > Linux install. There are details here: > http://casper.berkeley.edu/wiki/Roach_getting_started > > > 2) The 2nd problem is about the ethernet port of ROACH. >> First I connected the ROACH board to a ethernet switch. >> I try to assign the IP address through dhcp server by editting the >> /etc/network/interfaces file >> ----------------------------------- >> auto eth0 >> iface eth0 inet dhcp >> ------------------------------------- >> then use the command: >> >> ifdown eth0 >> ifup eth0 >> >> But I got "No DHCPOFFERS received." >> >> Then I altered the /etc/network/interfaces file to assign a fixed IP >> ------------------------------------------------------------ >> auto eth0 >> iface eth0 inet static >> address 128.235.92.250 >> netmask 255.255.255.0 >> network 128.235.92.0 >> broadcast 128.235.92.255 >> ------------------------------------------------------------- >> I got no complain after the ifdown and ifup command. >> But I can't ping to any computers. >> > If the link light is up on the connection, but packets aren't getting > through (which seems to be the case), then there are a number of things that > could be wrong: > * you are on different subnets > * your switch is faulty > * your switch is configured with VLANs > * your switch/router is not forwarding broadcast DHCP requests > etc > This tells me your network connection is not working. It is not a fault of > ROACH. The fact that ROACH works plugged into a NIC (mentioned below) > confirms that its network is working fine. There is a known issue with > ROACH's ethernet at 1Gbps, but I tested your board and the network before it > was shipped, so I can confirm that there is no problem with its network. > > If I connect the ROACH to a computer directly. I can ping that computer >> successfully and I can also ssh to ROACH from that computer, only if the >> ROACH board was connected to the first NIC port (eth0). There are there NIC >> cards in my computer (eth0, eth1, eth2). You can't ping the ROACH board >> using eth1,eth2. >> > Linux/MAC/Windows by default only chooses one NIC for a given network > subnet. You can't have three NICs one the same subnet and expect a single > ping packet to go out over all three simultaneously by default. They > probably have separate IP addresses on different subnets. It will only send > the ping request out of the one card on the subnet to which your ping > request was directed. > > These are standard networking concepts unrelated to ROACH-specific > implementations. I would suggest calling your computer/network administrator > to help you set up your network if you are having such issues. > > Jason >
