I have try to boot an Indy R5k with netboot. I have installed DHCP and TFTP
Server and the indy can load the Image via bootp. But after loading the image the system is standing still. know somewhere the reason !!
Who has already boot gentoo on an Indy R5K
Message
It is possible you've got the output device configured improperly.
Indy can only be interacted with via two means: Monitor/KB/Mouse or Serial Console. I personally prefer the latter, as it's sometimes easier than moving a monitor setup around alot. However, serial on an Indy (and Indigo2) requires a special cable which is difficult to find.
That said, if you're using serial, you need to make sure of several things:
The kernel should then autodetect and use the serial device, but this sometimes doesn't work either. In that case, try passing console=ttyS0,<baud> on the command line, where <baud> is the selected baud rate.
If you're going the Monitor route, you need to make sure the monitor supports SyncOnGreen, and can support high/odd resolutions. I learned a trick for my Indy, was to plug in the mouse and keyboard, but leave the monitor unplugged for several seconds after bootup, then plug the unit in. This makes the Indy operate at a lower resolution that my monitor will accept. Your results may vary, however.
--Kumba
Indy can only be interacted with via two means: Monitor/KB/Mouse or Serial Console. I personally prefer the latter, as it's sometimes easier than moving a monitor setup around alot. However, serial on an Indy (and Indigo2) requires a special cable which is difficult to find.
That said, if you're using serial, you need to make sure of several things:
- Monitor, Keyboard, and Mouse are all unplugged
- console is set to 'd1' (the serial device) via executing setenv console d1 on the prom command line.
- Setting dbaud correctly, again using the setenv command.
The kernel should then autodetect and use the serial device, but this sometimes doesn't work either. In that case, try passing console=ttyS0,<baud> on the command line, where <baud> is the selected baud rate.
If you're going the Monitor route, you need to make sure the monitor supports SyncOnGreen, and can support high/odd resolutions. I learned a trick for my Indy, was to plug in the mouse and keyboard, but leave the monitor unplugged for several seconds after bootup, then plug the unit in. This makes the Indy operate at a lower resolution that my monitor will accept. Your results may vary, however.
--Kumba
"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
--Emperor Turhan, Centauri Republic