Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

I made a Boo Boo

Nov 7, 2005 6:49PM PST

I set the wrong monitor type using yast and it shut down because the resolution\refresh was too high. Now I can't see anything to reset it.

Can you help me fix it?

Discussion is locked

- Collapse -
Failsafe?
Nov 7, 2005 9:35PM PST
- Collapse -
run level three
Nov 7, 2005 9:37PM PST

assuming you did not just destroy your monitor, you should be able to boot the computer into a recovery console (or use Knoppix if you have it), then run your xconf tool (or edit the conf file by hand... i am not sure where it is, but a google search for "x configuration file" should do the trick), then you should be good to go.

- Collapse -
See if this works
Nov 7, 2005 10:28PM PST

I'm typing from memory but I think what you need to do is this: When you boot up you should end at a command prompt, at the promt type su then you will be prompted for the root password enter that. Then type int 3 then type sax2. A cursor will spin around for a bit then you should wind up in the GUI to change the monitor. Hope that helps - Gary

- Collapse -
Thanks man, you just saved my penguin's ***!
Nov 8, 2005 3:34AM PST

I know I'm probably not suposed to say that, but I'm happy and it wasnt meant to be offensive.

Failsafe and Sax2 did the trick but typing int3 first only got an error......

This is probably a common problem maybe it should be somewhat common knowledge like safe mode for windows to fix bad settings huh?

- Collapse -
RE: I made a Boo Boo
Nov 8, 2005 1:08AM PST

I made the same mistake once. If I recall clearly, I had a second monitor that could handle the mess I made. I swapped monitors, corrected my settings and all was fine after that

- Collapse -
(NT) (NT) only mon not hurt circuit protection shutdown thanks
Nov 9, 2005 9:38AM PST