![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| SUN Solaris The Solaris Operating System, usually known simply as Solaris, is a free Unix-based operating system introduced by Sun Microsystems . |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Connected or not connected ! | !_30 | High Level Programming | 3 | 01-21-2007 06:02 PM |
| Ultra60 and A1000....raid manager needed just to see it? | Yinzer955i | UNIX for Dummies Questions & Answers | 3 | 08-24-2006 06:31 AM |
| solaris boot problem boot error loading interpreter(misc/krtld) | johncy_j | SUN Solaris | 0 | 08-17-2005 05:15 AM |
| New Sparc box wont boot. Keyboard? | Curt | UNIX for Dummies Questions & Answers | 5 | 06-02-2003 04:13 AM |
| How can I map Unix keyboard for PC keyboard | simhab | UNIX for Advanced & Expert Users | 1 | 03-06-2002 08:29 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
HELP! Keyboard connected but Ultra60 doesn't boot :-((
Hi all,
This is my first post here I'm in a predicament - my Ultra 60 worked fine before it was put into storage a year ago ... now, I've set it up in my PC room and I get the following message on startup: Can't open input device. Keyboard not present. Using ttya for input and output. Now, I powered on by pressing the 'power' button on the keyboard! On bootup, all 4 keyboard LED lights flash, along with the beep, but the system just hangs with the above message. I borrowed a Wyse terminal for the night to see whether it could actually bootup, and it did without problem. I borrowed another keyboard to try out - one known to work - and still the same message. What is going on?!? Tearing my hair out on this one ... Any help *much* appreciated. Cheers, Monte. |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
It sounds like the server isn't getting any response back from the keyboard (yet the keyboard is getting info from the server on boot which is why you see the lights). Since you already tried another keyboard you know works, then it's probably the input on the system (a db9 ?) - check the pins and wiring inside the box OR just use a dumb terminal. The input is built in - I don't think it's easily replaced (but I don't have one inf front of me either).
|
|
#3
|
|||
|
|||
|
You should be able to still halt the system and enter the forth monitor (ok prompt). please run test-all to run diagnotics. Please also set your input-device and output-device to ttya. This should bypass the keyboard check that the boot process performs.
|
|
#4
|
|||
|
|||
|
hi,
same thing happened with me once using sunblade150, after trouble shooting i found that one of the ram module get faulty, try working on this line of action |
|||
| Google The UNIX and Linux Forums |