| View previous topic :: View next topic |
| Author |
Message |
|Quantum|
Tux's lil' helper
Joined: 24 Jan 2004
Posts: 133
Location: Belgium
|
 Posted: Fri May 25, 2007 6:32 pm Post subject: Cannot get netboot to work in SGI Indy |
 |
|
Hi,
I recently received an SGI Indy. I followed all possible guides and tried to find experiences from other users on the net,
but I *still* can't get it to boot. I emerged net-ftp/tftp-hpa-0.48 and net-misc/dhcp-3.0.3-r9.
First the contents of /etc/dhcp/dhcpd.conf
| Code: |
# dhcpd.conf
ddns-update-style none;
subnet 192.168.0.0 netmask 255.255.255.0 {
pool {
range dynamic-bootp 192.168.0.1 192.168.0.254;
}
authorative;
allow bootp;
}
# Entry for the Indy!
host indy {
hardware ethernet 08:00:69:a0:f3:32;
next-server 192.168.0.1;
fixed-address 192.168.0.3;
option host-name "/tftpboot.img";
}
|
I configured my IP-address using | Code: | | ifconfig eth0 192.168.0.1 |
.
Services are started using :
| Code: |
in.tftpd -l -s /tftpboot
dhcpd
|
and of course I ran
| Code: |
echo 1 >/proc/sys/net/ipv4/ip_no_pmtu_disc
echo "2048 32767" >/proc/sys/net/ipv4/ip_local_port_range
|
The bootimage (renamed to tftpboot.img), is put in /tftpboot.
On the Indy now, I just boot, and give the following commands:
| Code: |
unsetenv netaddr
bootp(): /dev/ram0
|
Now comes the weird part. The indy SHOULD get the IP-address 192.168.0.3, but instead it gets 192.168.0.254.
Then it shouts the message "File not found" or something. There is no logging at all, not even when I supply in.tftpd with
the -v option.
I'm really out of options now, I think I tried every possible combination there is. |
|
| Back to top |
|
 |
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Fri May 25, 2007 10:59 pm Post subject: Re: Cannot get netboot to work in SGI Indy |
|
|
| |Quantum| wrote: | | Now comes the weird part. The indy SHOULD get the IP-address 192.168.0.3, but instead it gets 192.168.0.254. |
The dhcp server doesn't recognize it and it gives it an address from the "generic" pool, rather than the one from its specific entry. Since the generic stuff does not include the TFTP information, it can't find its boot image.
Are you sure about the MAC address (from the prom, run "printenv" and look at the "eaddr" line) ? Some of the SGIs can forget their MAC (it's stored in an RTC chip that has a battery inside... and the battery is maybe dead after so much time). It can be reprogrammed if that's the case, but you will need to replace the RTC chip first. |
|
| Back to top |
|
|
Redhatter
Retired Dev
Joined: 20 Sep 2003
Posts: 548
Location: Brisbane, QLD, Australia
|
| Posted: Sat May 26, 2007 1:05 pm Post subject: |
|
|
Okay... a couple of things...
o What does your syslog on the DHCP server say? It should mention what IP it hands out for the Indy.
o Does the Indy have the netaddr PROM variable set? If so, unset it and try again.
_________________
Stuart Longland (a.k.a Redhatter, VK4MSL)
I haven't lost my mind - it's backed up on a tape somewhere...
Gentoo/MIPS Cobalt developer, Mozilla herd member. |
|
| Back to top |
|
|
|Quantum|
Tux's lil' helper
Joined: 24 Jan 2004
Posts: 133
Location: Belgium
|
| Posted: Mon May 28, 2007 12:23 pm Post subject: |
|
|
The MAC-address was indeed the wrong one. After changing it in the dhcp-config, it retrieved the correct address but I still couldn't boot.
After a while I found that I had to use the following command on the Indy:
| Code: |
bootp()tftpboot.img root=/dev/ram0
|
Yes, I have to specify which bootimage to load on the Indy, en no, there is no colon (':').
Any other combination fails. I find it weird that nobody else had this problem before.
Maybe this should be added to the MIPS-handbook as extra tip in the "when it fails"-section.
I found the hint on this page.
Greetings  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on Alternative Architectures
