I've been trying to help someone out now with linux. I don't really know much about linux so maybe i could get some help with this problem he is having here, what he explained to me was.....

..... been trying out some of the live linux distros such as PHLACK, Knoppix-STD, **** Small Linux, etc..... The problem I've been having is that after booting, when it should hit the desktop the screen goes blank then the monitor reads "Frequency out of range" or "Frequency not in range" (can't remember the exact wording, but something along those lines anyhow) This isn't software produced text it's the text that the monitor throws up there when your unplug it from the computer or turn the computer off so that the monitor isn't getting any signal input from anywhere. But in my case the computer is still on and running strong as ever. I was just wondering what is causing this and/or if there is anyway to fix it. Also I know it's not just a corrupt file because I can run it on one of my computers.
_________________________
ZMA Sports Betting

The problem is caused by misconfiguration of the graphics card settings and is usually solved by running the graphics configuration tool supplied by your distribution. Since these are live discs, they could be a bit annoying to fix, because you would need to start each distro in text only mode, reconfigure the card and then manually start the GUI.

What is maximum resolution you have ever got from this monitor? Looks like system tries to set resolution you hardware doesn't support.

Is there some reason that these live cds are security testing tools. A regular Knoppix LiveCD (or DVD), currently version 5+ will almost certainly boot fine without any such errors.

When I have such a problem I would press ctrl+alt+backspace to drop into the terminal mode. I then proceed to do either

(1) edit /etc/X11/xorg.conf and alter the "Horizsync" and "VertRefres" statements so that the frequencies match the ones of my monitor.

or

(2) Run the terminal program "xorgconfig" to select the scanning frequencies manually (also has choices to specify your own frequencies).

After save the configuration file xorg.conf I will try the terminal command "startx" to get back to GUI.

I could repeat the above process several times if needed to get the system working.

So far that seems to work for me in all Linux and I have tried the same on BSD systems too.

Since I never feed a Linux with a driver I see it fair that I should get my hand dirty by amending the configuration file to get the system off the ground.