Come here for help.
% fbserv -S 1024 0 /dev/sgip &
fb_open: no such device "/dev/sgip"
This error occures due because you do not have the display hardware (or supporting drivers) to run this command.
to find the correct devices for your system try running:
% fbhelp
(Warning may give you black screen of death)
I personally used /dev/X as this seems to work well. Interestingly the file /dev/X does not exist in my subdirectory structure.
The framebuffer system looks for a prefix of /dev/ to determine if the framebuffer specified is a file or a device. Back before bit-mapped graphic displays were common, framebuffers were physical devices with entries in /dev. When the SGI and Sun machines came along with bit-mapped graphics, the convention was retained for the physical display. Thus "/dev/X" became the pseudonym for the X11 framebuffer (even though there is no X in /dev).
Fun Fact 1: You can set your framebuffer to be any filename, and it will save your pictures there. For example, if you set the FB_FILE environment variable to "/tmp/my_picture.pix" and then paint something into the framebuffer with a command like "png-fb angleBracket.png" It will show up in the contents of /tmp/my_picture.pix (as raw RGB data).
Fun Fact 2: You can also specify a remote framebuffer. On machine foo.com, start fbserv:
% fbserv 0 /dev/X &
on machine bar.org, run the rt command:
% rt -F foo.com:0 moss.g all
the rt will run locally and display on the remote machine's framebuffer. This can be handy when you have two machines, one with a sad puny display, and the other with a nice, big display.