2.6.1 Consol out of monitor's frequency range

id10t · 01-27-2004, 02:38 PM

OK So I couldn't see anything in the console. Oh well I came to the lovely LQforums, found the answer that jymbo gave us... And I have success... I know there is something there because my monitor tells me that the signal is the wrong frequency now instead of just nothing...

No problem I know how to fix thir right? I go to XF86Config XF86Config-4 XF86Config-vesa and XF86Config-fbdev and make sure all of the settings for my monitor are correct... And they are... I had to fix them before to make my 2.4.22 show the console.

Help... is there something I am forgetting?

Shade · 01-27-2004, 06:14 PM

Indeed there is

And you are mistaken about editing the XF86Config files for your framebuffer on console.
These are for X configuration. Not the kernel framebuffer.

More than likely, you compiled the wrong framebuffer support into your kernel.
I usually simply select the standard vesa driver, rather than a card-specific.

It's buggy with my trident card, and doesn't work at all with my radeon.
So just recompile the kernel with vesa framebuffer support, and video mode selection support, and you should be fine.

--Shade

id10t · 01-27-2004, 08:29 PM

I did exactly that to get as far as the "Out of Range" error. Before it was just a black screen.

It's strange I know but editing the XF86Config fixed my 2.4.22 kernel.

Shade · 01-27-2004, 09:06 PM

It's not *strange*. It's *wrong*. There's no way editing the xfree86 configuration file
will affect the console.
Just think -- how would you fix this problem if you didn't have X installed at all???

Questions:
What video card do you have?
What resolution does your monitor support?

Suggestions:
What resolution are you trying to run the framebuffer at?
What color depth?
What happens when you use vga=normal instead of say vga=788 in lilo.conf ?

-Shade

Edit: If editing the XF86Config file "fixed" your framebuffer... I give up linux.
Unless a buggy X driver somehow initialized your card right, and then you did a soft reboot and the framebuffer somehow worked, then damn. I dont see how its possible.

id10t · 01-28-2004, 01:46 AM

Quote:

It's not *strange*. It's *wrong*. There's no way editing the xfree86 configuration file
will affect the console.
Just think -- how would you fix this problem if you didn't have X installed at all???

Alright buddy... You don't have to be a jerk about it... It just fixed the problem of going back to console from X. Sigh... maybe I should have explained better

I have a Radeon 9500 (with ATI's fglrx drivers installed)
My Monitor is a 17" LCD that has a native Resolution of 1280X1024
Fh:30~82kHz, fv:50~75 Hz

VGA = normal currently. I had it set higher before. (and of course neither worked)

Quote:

Edit: If editing the XF86Config file "fixed" your framebuffer... I give up linux.
Unless a buggy X driver somehow initialized your card right, and then you did a soft reboot and the framebuffer somehow worked, then damn. I dont see how its possible.

It "fixed" the flippin problem. I'm sorry... I'll try and talk more 1337 nex7 7im3 s0 j00 don't ha\/e to pu7 up w1th my l4m3 w4y 0f t4lking.

If you are going to so anal about this... please... Don't answer my question. There are plenty of people who would be happy to work with someone who isn't as uber elite with linux as they are. I'll find them...they are everywhere.

J.W. · 01-28-2004, 10:24 PM

Dude - mellow. Shade's advice is good. Settings to the XF86Config file apply to X, not the console. I'm running, or at least trying to run, a Radeon 9700Pro on an experimental box, and am running into a variety of hassles including the same out of range problem you describe. (I can only wish I had your success in installing those [bleeping] ATI fglrx drivers). Anyway, modifying the lilo.conf file to use vga=normal (and then running /sbin/lilo to make those changes take effect) solved that particular problem for me, and should fix it for you too. If that doesn't work, then you might want to try setting the specs even lower like vga=771 or even vga=769. At the risk of telling you something you already know, edits you make to the XF86Config file will take effect the next time you "startx" in user mode, but edits you make to lilo.conf won't take effect until you /sbin/lilo as root. Good luck with the monitor -- J.W.

id10t · 01-29-2004, 01:09 AM

Yeah... your right... Sorry for going off. I'm just so sick of this "I'm leet and your not so you piss me off" attitude. I give that a try with lilo.

==============Warning:: Off Topic==========================

Oh... you know what got my fglrx to work... Use the rpm2tgz tool to change the RPM to a tgz package and then use pkgtool to install it...

They don't have manual entries... (at least on my box

) but they are pretty simple.

Code:

bash# rpm2tgz fglrx<blah blah blah>.rpm
bash# installpkg fglrx<blah blah blah>.tgz
bash# fglrxconfig

Then the rest you should be able to do.

J.W. · 01-29-2004, 02:24 AM

id10t - hey man, thanks for the pointers on the ATI stuff. I've tried just about everything else I could find, without success, but will give your suggestions a try tomorrow. All I know is that I've downloaded any number of tutorials, drivers, etc, trying to take advantage of the advanced performance this card offers, but at this stage, my crappy $45 video card I bought a few years ago scores a better FPS rating than this 9700. If it works, I'll post up about it. Thanks for the recommendations.

As for the monitor issue, you'll definitely want to run the lilo program itself anytime you edit the /etc/lilo.conf file itself, in order to apply those changes, running as root:

code:# /sbin/lilo

In order to solve this issue on my rig, I did exactly what Shade recommended, which was to just bump down the vga console setting. Comment out the line that is in effect, and uncomment one at a lower setting. As you'll see, the choices in the file reflect the resolution and color depth, and you should be guaranteed to be safe with any choices that use 256 colors. Edit lilo, then run lilo, and hopefully you should be good to go. As you know, just to play it safe, you should save a copy of lilo.conf prior to making any edits. -- J.W.