Then your next step would be to establish a console connection from another computer.
Serial port to serial port, null modem cable, and a terminal program for command-line interaction.
That's the only guaranteed way to learn what might be happening.
It could be as simple as the current resolution isn't compatible with the monitor.
It could be as serious as a coincidental failure of something in the system.
--
Oops !
Sudden thought ...
Do you have a UPA frame buffer installed
while you're attempting to connect the monitor to the onboard graphics?
If so, then the default graphics output is now going to the DB13W3 output,
and not to the HD15 connector.Shut it down and remove that graphics card.
Output will automatically revert to the HD15 connector.
ok ive managed to get a signal on my monitor from the ultra 10. i just had to wait a bit it takes about 5 mins to load up. This then reveals the problem. when the 'bios' screen loads it now tells me everything that is connected to the motherboard it constantly says:
Boot device net file and args:
Using onboard transiever
i managed to get it to boot a cd but then when i have to make a selection ie country it wont accept my command it just shows the ok prompt any ideas on this one?
... back to what I mentioned a few days ago:
"Then your next step would be to establish a console connection from another computer.
Serial port to serial port, null modem cable, and a terminal program for command-line interaction.
That's the only guaranteed way to learn what might be happening."
That means you remove your current keyboard and your only connection
would be through that serial console.Expect to start the OS installation all over again.
(Yes, you can install an OS while using that command-line serial console.)
ok so ive managed to get the first cd to go through its loading stuff when it reboots for the first time the screen comes back very quickly however i posed with
boot device net file and args:
using onboard transeiver - timeout waiting for autonegotiation status to be updated
timeout reading link status check cable and try again
This carries on and it wont let me carry on the installation
That suggests you have an issue with the disk drives.
Something is broken or uninstalled or unconnected inside the chassis.
Your OS installation can't find the drive(s), and is attempting to find
a boot device on the network.
While connected via your serial console, get it back to the OBP prompt.
Then do ...
OK setenv auto-boot? false <enter>
OK setenv diag-device disk <enter>
OK setenv diag-level max <enter>
OK setenv diag-switch true <enter>
OK reset-all <enter>
The system will reboot and go into a deep diagnostic POST.
It will scroll too fast for you to read it, so you'll need to capture all console output to a text file for later review.
Once armed with all that info, it's time to go to an OS forum and get guidance from those who haunt such an arena.
Hello,
re-attach the keyboard, power-on the system, wait a few seconds, then press the keys STOP (upper left key below the Help key) and A simultaneously. Then enter (blind)
setenv diag-switch? false
setenv auto-boot? false
power-off the system and remove the keyboard. Power-on, output and input now to/from the serial console. If you know which key combination sends a BREAK, you can try this instead. TeraTerm uses ALT-B.
Use printenv to review the setting (important are: diag-switch? and boot-device).
Check if the boot-device is set with disk as the first item.
probe-ide displays the ide devices, first one is the disk (promary master) and third one (secondary slave) the CD drive.
Your error is probably caused by the setting of diag-switch?. If set to true the boot-device is set to net as the first item.
Good luck, I'm heading for the airport ... I will be back on Monday.
Michael