dpaulso@relay.nswc.navy.mil (Dave Paulson) (08/27/90)
I finally received my new NeXT last Thursday (well, new to me, anyway -- I picked up one of the used machines that had been offered recently), and I hooked it up that night, hoping that it suffered no damage in transit. Everything worked great, the system booted beautifully, hard drive drove dreamily, the printer printed perfectly, and I was real pleased finally to be able to see with my own eyes all the neat things that you folks have been raving about here... (Sigh) But my reverie was shattered on Saturday when I tried to use the machine for some real work. Since then, whenever I try to access the printer, I get an alert warning me that the printer is "not connected." It clearly is, though. To cut to the chase: I've verified that both of the printer cables (power and data) are OK. The kernel finds the printer at the expected location (0x0200f000) during boot, but does not "power-tickle" it during boot. I've also seen these error messages in the console window: np0: power_on_async failed, error = 19 npd[105] error opening /dev/np0, no such device [two more of these] Inform [136] no reply to status request from npd, -203 error 19 is "ENODEV" (no such device), but again there clearly _is_ a /dev/np0. I've also tried killing and restarting both lpd and npd, and I've also removed and then remade /dev/np0 with MAKEDEV. Any ideas, anyone? Thanks for your help. /dave -- Dave Paulson Synetics / Naval Surface Warfare Center dpaulso@relay.nswc.navy.mil voice: (703) 663-2137