Ultimate Edition Forum

I am a happy Ultimate Edition 2.3 user and just gathered my resolve to install 2.5 on my machine.

The problem now is that I cant Install UE2.5. Tried to boot both safe graphics and normal boot but monitor still says "Out of Frequency range". Back when I installed Ultimate Edition 2.3, The normal boot has the above problem, but I can still boot to safe graphics mode then install from there, once Ultimate Edition was installed I just edited my xorg.conf file to add the necessary vertrefresh and horizsync values to it and it works so well I got tears in my eyes.
During my stint using Linux Mint, I change "quiet splash --" in the boot options to "break bottom", which boots me to a concole, and from there I would edit my xorg.conf as I said above.
The work-around that worked for me in 9.04 based distros doesnt seem to work anymore T_T
I know this problem is probably due to Ubuntu 9.10 suddenly making xorg.conf disappear :p

Is there anything I can do around this?

Machine Specs:
Pentium D 2.6GHz
2GB DDR2 RAM
2x 80GB SATA Hard Drive
Intel 945G onboard graphics
Generic 17" CRT Monitor

hm... what is displaying the "out of frequency range"?
is it a command line, or a real GUI?

After I chose either choices, Boot Ultimate Edition 2.5 and Boot Ultimate Edition 2.5 in safe graphics mode, both end up in my monitor cringing about monitor out of frequency range... T_T

ctr+alt+"+" doesnt work, in the boot options adding: vga=7xx doesnt work, break=bottom, which in any 9.04 based distro will lead me to a CLI interface where I can edit my xorg.conf, still results to this problem. break=top seems to boot, but stops halfway, I see no errors in this, it just stops...

im only taking a stab in the dark here. but maybe its something to do with kms. try using

Code: Select all

nomodeset

drama wrote:im only taking a stab in the dark here. but maybe its something to do with kms. try using

Code: Select all

nomodeset

YES! this solved my problem!

Before I used it, I ran a search on google about nomodeset, and found a thread at the ubuntuforums on ubuntu 9.10 crappiness on intel graphics. all i had to add on the boot options was:

Code: Select all

nomodeset --xdriver=intel vga=771

and I finally got into the live-dvd desktop!
Thanks a lot!
[SOLVED]

sagittax wrote:

drama wrote:im only taking a stab in the dark here. but maybe its something to do with kms. try using

Code: Select all

nomodeset

YES! this solved my problem!

Before I used it, I ran a search on google about nomodeset, and found a thread at the ubuntuforums on ubuntu 9.10 crappiness on intel graphics. all i had to add on the boot options was:

Code: Select all

nomodeset --xdriver=intel vga=771

and I finally got into the live-dvd desktop!
Thanks a lot!
[SOLVED]

Glad that solved it for you. Kernel mode setting was a mistake in my opinion. It should default to off with the option to turn it on. Instead of the other way around. Its not just an intel issue. Also affects ati but it doesnt affect all ati/intel gpu's (one of my ati boxes are affected and the other isnt x200 works fine but not x1600). And the issues are widespread from the issue you had to hardlocks to screen corruption and in some cases breaking hardware acceleration completly. Plus when its enabled at least on my x200 framerates drop by half. And its going to be enabled for nvidia soon to from what i hear ( coming in kernel 2.6.33) so nvidia users arent gonna be safe for long either.

Also affects ati but it doesnt affect all ati/intel gpu's (one of my ati boxes are affected and the other isnt x200 works fine but not x1600

Mine is cool...I don't remember doing the nomodeset thing,but your right I think it should have been a option.

It affected an Nvidea 7300 GT of mine that I recently set up. My solution was to simply switch from the standard VGA port and cable to the DVI port and cable. Apparently this allowed the kernel to acquire what my monitor's acceptable refresh rates where.

Cell wrote:

Also affects ati but it doesnt affect all ati/intel gpu's (one of my ati boxes are affected and the other isnt x200 works fine but not x1600

Mine is cool...I don't remember doing the nomodeset thing,but your right I think it should have been a option.

My issues werent too serious. I would get a hard lock if i had an uptime of over 5 days. Nothing out of the ordinary in the system logs either around the time of the hardlock. Disabled kms and that solved it. Fps in glxgears almost doubled by disabling it too...the only place its noticable though is in wine when im playing oblivion.

I suspect the actual issue the OP had was that his monitor was sending a bad EIED and since kms tries to set the highest res possible this just caused it to crap out (the eied is where kms actually gets its info from and uses settings according to that). Now most likely the reason why it crapped out now and not when it was set to off is ( i suspect) the monitor doesnt accept the highest refresh rate its capable of at the highest resolution. I have a buddy that has a screwy monitor like this. Accepts 75hz refresh at all resolutions except 1920x1080 which only accepts 70hz. And the eied doesnt totally give all this info just lists up to 1920x1080 resolution and up to 75hz refresh. Its the fault of the manufacture. Faulty eied's cant be saolved but not as early in the process as what kms starts. And only with the nvidia driver as it accepts

Code: Select all

custom-eied

For a custom eied ignoring the one built into the monitor

and

Code: Select all

ignore-eied

To ignore the eied totally

But that doesnt do any good if your not or cant use the nvidia driver.

Disabled kms and that solved it. Fps in glxgears almost doubled by disabling it too

Heck...maybe Ill disable it then.Maybe Ill get even better performance.