Upate to 2.6.14-gentoo-r2 Monitor: Sync Out of Range[SOLVED]

lyoo · n00b Joined: 08 Oct 2005 Posts: 4

After I updated to 2.6.14-gentoo-r2, some strange problem appeared:

1. I do not change any kernel configure and grub boot configure, all of them can work perfectly on linux-2.6.13-gentoo-r5;
2. I compiled 2.6.14-gentoo-r2 and recompiled nvidia-kernel, reboot my computer, everything is ok, it can load frambuffer in console environment;
3. run startx, X window runs correctly, but, when I use ctrl+alt+Fn switch to console environment, monitor says: Sync Out of Range.
4. Then, I exit X window, monitor also says: Sync Out of Range, and can't works.

Motion: LG L1715S LCD
Graphics Card: nVidia Gf4200 8X

vesafb-tng:
(1024x768@60) VESA default mode

grub.conf

sonicbhoc · Posted: Sun Nov 20, 2005 5:13 am Post subject:

Same problem I'm having! Do you think that we need to downgrade kernels? because that would suck. I'm going to see if I can submit a bug report.

EDIT: Reports filed. Let's see what happens.

lyoo · n00b Joined: 08 Oct 2005 Posts: 4

yea, I'v downgraded kernels

I have another gentoo workstation, it updated to x86-2.6.14-gentoo-r2, works fine.

Motion: 17" CRT
Graphics Card: nVidia Gf4 MX440

dispossessed · n00b Joined: 31 Mar 2005 Posts: 9

Any progress on this? I'm having exactly the same problem with an LG 15" CRT and nVidia GeForce. The drivers (nVidia and vesafb-tng) seem to be working fine, presumably it's a bug in 2.6.14-gentoo-r2?

RandomAccess · n00b Joined: 26 May 2005 Posts: 28

I have an Intel i915G motherboard with the Intel GMA900 integrated graphics card, and I'm having the same problem. It only started happening after I upgraded my kernel to 2.6.14-gentoo-r2. So, I guess we can rule out it being a nVidia-only problem?

RandomAccess · n00b Joined: 26 May 2005 Posts: 28

OK, I noticed something just now. When I boot 2.6.14-gentoo-r2, just before the INIT Version 2.8 booting message, vesafb outputs something about "mtrr" being an unknown option. If you hit F2 to see verbose output during boot, you can catch it. You can also do:

dmesg | grep mtrr

When I boot under 2.6.13-gentoo-r5, I do not get the message about "mtrr" being an unknown option. My grub.conf looks like this:

default 0
timeout 10
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.14-r2
root (hd0,0)
kernel /kernel-2.6.14-gentoo-r2 root=/dev/sda3 video=vesafb:mtrr,ywrap,1024x768-32@75 splash=silent CONSOLE=/dev/tty1
title=Gentoo Linux 2.6.13-r5
root (hd0,0)
kernel /kernel-2.6.13-gentoo-r5 root=/dev/sda3 video=vesafb:mtrr,ywrap,1024x768-32@75 splash=silent CONSOLE=/dev/tty1

Could it be that the mtrr option has something to do with it? I'm not exactly sure what it does, but it doesn't make sense to me that it would suddenly become an unknown option in the new kernel.

dispossessed · n00b Joined: 31 Mar 2005 Posts: 9

I'm seeing that too.. I removed mtrr from the boot options and the error disappeared, but the problem remained. Seems unrelated.

j-m · Retired Dev Joined: 31 Oct 2004 Posts: 975

Erm, I don't know if anyone noticed yet, but the problem is solved - your kernel is misconfigured... :!:

That's why cross-posting about the same problem is bad. :idea:

UncleMeat · n00b Joined: 27 Jan 2004 Posts: 2 Location: down in france

Same problem here.
It's a new installation so I don't have X yet, when I reboot, my monitor says "out of range" (H=29.2Khz, V=70.0hz) and the specs fot it are H=30-95Khz V=50-150hz

My monitor is a Hyundaï Q995 with a Nvidia Geforce Ti 4200 (vesafb-tng)

My grub.conf:

dispossessed · n00b Joined: 31 Mar 2005 Posts: 9

Pretty sure that thread is about a different problem. I don't have any drivers other than vesafb-tng checked in the kernel config. Plus this problem occurs after running and exiting X, not initially or during the X session.

RandomAccess · n00b Joined: 26 May 2005 Posts: 28

sonicbhoc · Posted: Wed Nov 23, 2005 1:21 am Post subject:

I'd go out on a limb here and say that this is a little more than a few people misconfiguring their kernels. Any ideas?

sevo · Tux's lil' helper Joined: 12 Mar 2005 Posts: 79

That must be a different problem. vesafb-tng IS loading here, but does only offer low or wrong resolutions on 2.6.14. Which it emphatically did not with older kernels. Probably vesafb-tng is broken in 2.6.14. I am switching back to vesafb.

Sevo

j-m · Retired Dev Joined: 31 Oct 2004 Posts: 975

Someone please file a new bug, seems like a different issue than the other thread.

ribx · Posted: Wed Nov 23, 2005 5:18 pm Post subject:

i accidently started a new [url=https://forums.gentoo.org/viewtopic.php?p=2900176#2900176
]thread[/url] about the same problem.

i want to add that, when i started with my old vseafb settings:

hielvc · Posted: Wed Nov 23, 2005 6:45 pm Post subject:

Well I have two boxs, 1 is a sis, via c2 itx and a via chipset, sempron with geforce 440. The sis box works fine with 2.6.14 @1200x1024. The geforce box will only run at 1024x768 when running 2.6.14. Ive tried both vesa and vesa-tng, and the console and X at stuck at 1024. When I boot with 2.6.13 ever thing is fine. I think has to do with

RandomAccess · n00b Joined: 26 May 2005 Posts: 28

OK, so you are limited to lower resolutions, but what about the original monitor signal out of range problem? I've never run my fbconsole higher than 1024x768 (call me old fashioned), so my problem doesn't happen to be the resolution. Rather, after X loads, I am unable to return to my fbconsole because my monitor complains about the signal being out of range, just as others have described in this thread. Should we open up a separate bug for this specific case?

hielvc · Posted: Wed Nov 23, 2005 8:07 pm Post subject:

Yes I would recommend opening a new bug for it. One thing you might try is look i your /etc/rc.conf and if UNICODE="yes" set the coment it out and reboot. This is a wild shot, but what the hay its your computer not mine :wink:

If it does work, definitly file a bug umm and mention me in big print

_________________
An A-Z Index of the Linux BASH command line

RandomAccess · n00b Joined: 26 May 2005 Posts: 28

Yep, I checked my /etc/rc.conf and I did have UNICODE="yes" for some reason. When I put it to "no" it solved the problem. Obviously it should still work even with UNICODE="yes" so I have filed a new bug:

https://bugs.gentoo.org/show_bug.cgi?id=113408

Thanks for the tip! Hopefully this isn't a tough bug to fix.

dispossessed · n00b Joined: 31 Mar 2005 Posts: 9

Sorry to report that my UNICODE was already set to "no", but I'm still experiencing the problem..

lyoo · n00b Joined: 08 Oct 2005 Posts: 4

hielvc · Posted: Thu Nov 24, 2005 7:02 am Post subject:

Damn he did

_________________
An A-Z Index of the Linux BASH command line

RandomAccess · n00b Joined: 26 May 2005 Posts: 28

olger901 · l33t Joined: 17 Mar 2005 Posts: 625

Try using vesafb instead of vesafb-tng, and see if that solves your problem.

lyoo · n00b Joined: 08 Oct 2005 Posts: 4