string
string
string
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
failed to initialize adapter after the probe has correctly identified the<br />
card. There are a variety of reasons for this error, but in all cases the error is because<br />
of misconfiguring the card.<br />
Action<br />
To correct the problem, press Ctrl-a during boot of the computer to enter the 154x<br />
BIOS configuration utility. Choose the<br />
Configure/View Host Adapter Settings option, then press the F6 key to<br />
return the adapter to its factory default settings.<br />
After doing this, reconfigure the adapter per the instructions contained in the x86<br />
Device Configuration Guide or Driver Update Guide if applicable. It is especially<br />
important that the adapter be configured to use DMA 6. Note that it defaults to<br />
DMA 5 and must be changed.<br />
fbconsole: ioctl SRIOCSREDIR: Device<br />
Busy.<br />
Cause<br />
When starting Openwindows from the command line, the following error message is<br />
echoed on the Solaris "Welcome" screen:<br />
fbconsole: ioctl SRIOCSREDIR: Device Busy<br />
Once inside Openwindows, The following message is displayed in the background<br />
windows and when starting cmdtool -C:<br />
SYSTEM WARNING: Object 0x340f8, Device busy, ioctl SRIOCSREDIR<br />
returned -1, attempt to make tty the console failed (Tty package)<br />
Action<br />
Openwindows was probably started in the background (using the "&"). Exit<br />
Openwindows, and run the command in foreground:<br />
/usr/openwin/bin/openwin<br />
If this doesn’t help, then perhaps some daemon or process is "holding" the console.<br />
Type the command: fuser /dev/console.<br />
A list of process id’s is returned. Examine these processes to determine if an<br />
application has hold of the console (using the ps(1) command, will help).<br />
Alphabetical Message Listing 67