I booted my Sparc IPC with out any problems. I followed the instructions to the letter ( sparc_release_note.txt ) With the exception of one thing, which I think you mentioned you have done. On the linux Slak box I was using as the TFTP server, I noticed that "RARP" alone isn't good enuf. ARP must be done also. The instructions only say to do RARP, so that needs to be changed in this case. I found there were connections and such from the IPC in the logs on the TFTP server, so that was a good indication for me that an address had in fact been assigned to the IPC. So watch your logs for one thing. Messages and Syslog etc.
Once I got the Sparc online and was grinning from ear to ear as I saw the bootup of Debian I ended up moving thru the installation menu's without too much trouble, but I did things a little different. First I changed to another console ( alt-f2 ) and setup the Ethernet interface using " ifconfig " etc. And of course added the necessary route's so the Sparc could ping and be pinged by my Linux PC. After exporting the isntall source from my Linux system, I then mounted the partition to a point on the Sparc, and selected " already mounted location " etc for my install. I hope some of that is a little helpful. The only thing I am stuck on, and haven't had much time to look at is installing X. Anyone out there got X working on a Sparc IPC or Sparc of any sort ?? Cheers. Richard Parkinson Ph. 64 7 8399090 Systems Consultant Fax. 64 7 8389333 Encomium Retail Systems E-Mail. [EMAIL PROTECTED] 1139 Victoria St. -----Original Message----- From: Scott Omar Burch [SMTP:[EMAIL PROTECTED] Sent: Wednesday, July 08, 1998 5:21 AM To: [email protected] Subject: Remote Booting Question/Problem on IPC I recently decided to take an old IPC I had that was running Solaris 2.5 and convert it to Linux. I tried to do a remote boot using the tftpboot.img, but after I type boot net and wait for about five minutes the IPC tells me that the file does not appear to be bootable. I tried to do this same procedure with Red Hat's 5.1 tftpboot.img file, but I get the same results. Here are some more details of what I did: I setup tftp on another Linux box and added rarp and arp entries for the IPC. I copied the tftpboot.img file to the tftp directory I specified in the init scritpt and created a symbolic link to the file named with the machines hex hardware address and a .SUN4C extension. Details on the IPC: I believe the prom is version 2.09. When I halt the boot process I have to type n or new to get the new openboot prompt. The machine has 32 MB of RAM and a 1.2 GB Disk. I suspect I am doing something wrong. Can anyone offer me any suggestions? If I get the remote boot to work what methods can I use to access the base.tgz file? Thanks, Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] n.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
