Hi Paul,

I just put up another linux-dist.tgz where the link to the nfs-utils tarball is from our own server - we have a copy.  the only other difference between your tarball and the latest is the addition of a little load-locked store-conditional test benchmark, so alternatively, you could just change the make rules on your installation to point to:

http://www.m5sim.org/dist/m5_benchmarks/nfs-utils-1.0.6-ptx4.tar.gz

however, i'm not positive that's your problem, i remember seeing that error before but i can't remember exactly what caused it - if you still have a problem after you get nfs-utils into your image, write back and attach a copy of your ptxconfig file.

lisa

On 11/9/06, Paul West <[EMAIL PROTECTED]> wrote:
I'm trying to build a image for ALPHA_FS on M5.  I've build a kernel
that boots up fine with the image provided on the M5 website.  When I
build my own image the kernel seems to boot, but then at the end I get this:
...
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear < [EMAIL PROTECTED]>
All bugs added by David S. Miller <[email protected]>
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 160k freed
Warning: unable to open an initial console.

Then the system hangs with no shell.  Now, the only deviation from the
instructions on the website to build the image was that I had to
disabled NFS because 'nfs-utils-1.0.6-ptx4.tar.gz' could not be
downloaded.  When I googled for the file, the only place that I could
find had it at one point, but no longer.  I'm assuming the lack of NFS
is causing the problem.  Does anyone have a copy?

Thanks,

~Paul
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users


_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to