Bug 152336

Created attachment 69402 [details]
The specs of the Hyunday L50S

Created attachment 69403 [details]
The xorg.conf as generated on beta 4 with nvidia 6100

I'm sorry but I cannot find a mistake in the config file:

1) Monitor:

   HorizSync    30-60  #Khz
   VertRefresh  43-75  #Hz

This is correct according to the given specs. The lower bounding is
not of great relevance because the modelines are selected according to
the upper bounding. The lower bounding is adapted because all modes should
fit into a 60Hz mode which sometimes decreases the lower hsync bounding
which is not critical.

2) The calculated modes:

   Modeline  "1024x768" 79.52 1024 1080 1192 1360 768 769 772 801

The highest 1024x768 mode is using:
 
   58.47 Khz
   72.99 Hz

according to the specs this is valid. So your monitor is out of
sync with these values ?
 

Created attachment 69643 [details]
This is screen i get "Video mode not supported"

Yes the momitor is out of sync with these values. So maybe a tollerance problem? Of the mainboard or Monitor?

If you don't mind send me the information from

   hwinfo --monitor

you told me removing the modelines will solve your problem. Could
you tell me at which hsync/vsync level your monitor works in that case ?
I think you can obtain that information directly from the monitor (menue)

Thanks

Created attachment 69852 [details]
output of hwinfo --monitor

Thanks, monitor has been added with respect to the sync ranges

The problem was solved in beta 6. But appeared again in beta 8.

Hmm, sounds weird... If you don't mind create a backup copy of your
current xorg.conf and call sax2 as user root in runlevel 3

   sax2 -r -a

after this remove all X logs:

   rm -f /var/log/X*

and start a plain X server calling:

   X

kill the X-Server with:

   Ctrl-Alt-BackSpace

--> send the file /etc/X11/xorg.conf
--> send the file /var/log/Xorg*.log

Thanks

In beta9 i had the same problem. These are files for beta9. By the way. for beta9 i couldn't even use the nvidia ie sax2 -m 0=nvidia it was already out of sync. With beta 8 this was possible.

Created attachment 76115 [details]
beta9 log files

IOf needed i can also do the requested. Later on.

sorry it's very confusing what you told me. In your initial comment you
said it works if no modelines are present. The xorg.conf you sent me
didn't contain any modelines (intentionally because the binary nvidia driver
is in use) The driver told me:

   (II) NVIDIA(0): Monitor[0]: Using hsync range of 31.00-60.00 kHz
   (II) NVIDIA(0): Monitor[0]: Using vrefresh range of 56.00-75.00 Hz
   (**) NVIDIA(0): Validated modes for display device CRT-0:
   (**) NVIDIA(0):      Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz
   (**) NVIDIA(0):      Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
   (**) NVIDIA(0):      Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
   (II) NVIDIA(0): Setting mode "1024x768"

This looks pretty good to me, what is wrong ? By the way nvidia is binary
only we cannot fix anything here if it's a driver issue

Sorry but I assume things are really mixed up. The initial bug report
concerns a problem with the specs of your monitor which has been fixed
referring to the written monitor section:

Section "Monitor"
  Option       "CalcAlgorithm" "XServerPool"
  DisplaySize  300 220
  HorizSync    31-50
  Identifier   "Monitor[0]"
  ModelName    "L50S"
  Option       "DPMS"
  VendorName   "HYUNDAI"
  VertRefresh  56-65
  UseModes     "Modes[0]"
EndSection

we are using stricter values because you said it's a problem driving
the monitor at its limit. The nvidia driver doesn't care and use the 
EDID values of: 31.00-60.00 kHz and 56.00-75.00 Hz which looks good to me
as well.

The open source nv driver will use the suggested range and will calculate
modelines within this range.

what exactly is the problem ? If you have a working config what did you
change ? and wich driver did you use. It's not a good idea to mix up things
in such reports it makes me feeling clueless what the problem is. Your
monitor seems to be rather old, a CRT doing a maximum of 75Hz ? Are you sure
your monitor doesn't require specific sync values for specific modes ?
Please consult your monitor manual to check that. Are the sync ranges checked
by the driver the same as included into the manual ?

you see lots of questions no answers...

According to the logs it seems you didn't follow the needinfo
workflow I asked for in comment #10. This workflow would provide exactly
one xorg.conf and the appropriate Xorg.0.log file nothing else

I will close this now because it's too confusing. If you don't mind
file a new bug report for the nv driver (because for nvidia you have to
use the bugzilla of nvidia) and include the information I asked for
in comment #10

Thanks

I don't know if you want to have this problem fixed. If not it's also ok with me.

The current problem is the following, it's even worse than the one that existed in beta4. sax2 gives an out of sync with the xorg and the nvidia driver.

with the xorg driver i don't get it to work at all. With the nvidia i do. When i choose 800x600 as screen resolution and in adjust the xorg settings while running xorg, via yast. I needed to change them to: 
Section "Monitor"
  Option       "CalcAlgorithm" "XServerPool"
  DisplaySize  300 220
  HorizSync    31-50
  Identifier   "Monitor[0]"
  ModelName    "L50S"
  Option       "DPMS"
  VendorName   "HYUNDAI"
  VertRefresh  56-65
  UseModes     "Modes[0]"
EndSection

The orginal value was: 
Section "Monitor"
  DisplaySize  300 220
  HorizSync    31-55
  Identifier   "Monitor[0]"
  ModelName    "L50S"
  Option       "DPMS"
  VendorName   "HYUNDAI"
  VertRefresh  56-72
  UseModes     "Modes[0]"
EndSection

By the way deleting the modlines didn't work at all this time!!

By the way might there be a calculation error in sax2 and/or isax2?

I will provide te info as told in the workflow. Do i need to do a new install because i have the nvidia driver installed.

Or should i create a new bug report?

If I wouldn't be interested in fixing a bug I would close it as wontfix
This bug has been fixed as worksforme because the original problem with
wrong detected monitor has been fixed.

- As I already said the nvidia driver is binary we cannot fix it
  AS I already said the nvidia driver doesn't care for your monitor
  settings it use the EDID data from your monitor, your manual change
  couldn't have any influence on that behaviour
  As I already said the log of the nvidia driver tells me the 1024x768
  resolution IS active... blame nvidia if it does not work for you

- As I already said yes I would wish you open a new bugreport IF and only
  if you found a problem while checking the workflow mentioned in
  comment #10 

Thanks

Created attachment 76273 [details]
The requested info according to #10

I added the info accoring to #10. If needed i can create a new bug report. I had to install SuSE 10.1 beta 9 from cratch as i couldn't disable the nvidia driver.

nvidia-installer --uninstall

Thank you, i'll remember if or the next time. in #18 i created the attachment after a new install. According to #10. By the way with beta 9 as this one had the same problem.

Thanks for the information. The tarball you sent contains multiple
directories with multiple files in it *seufz* I assume the directory
sax2-r-a/ and the file Xorg.0.log and xorg.conf are the requested files
and I will ignore the rest.

1) The log file told me:
   (**) NV(0): *Mode "1024x768": 72.7 MHz, 53.5 kHz, 67.0 Hz 
   (II) NV(0): Modeline "1024x768"   72.71  1024 1080 1192 1360  768 769 772 798

2) The xorg.conf includes:
   Modeline  "1024x768" 72.71 1024 1080 1192 1360 768 769 772 798

So this is the correct Modeline and the X-Server accepts it, it fits into
the range of the monitor but you cannot see a picture on your monitor ?
you kidding me right ?

I'm sorry there is nothing I can do because if I trust the logs everything
is just fine. Are you sure there isn't any ghost in your machine ;)
I don't have such a monitor, I'm sorry
   
   

I think what we see here is a general driver problem for GeForce 6100 cards and is not related to the monitor (detection) at all. Joop, can you create any configuration, which works for you and attach this according /etc/X11/xorg.conf and /var/log/Xorg.0.log?

Created attachment 76796 [details]
This is the only config i got to work (only 800x600 was possible not 1024x768)

This is the only config 1 got to work (800x600 by lowering the VertRefresh by 2 Hz). I didn't get 1024x768 to work at all. 

This is really strange. I don't understand this.

according to the logs the 1024x768 are accepted by the driver but
didn't lead to a viewable picture, very strange

Ok. We need to use the "fbdev" driver for your gfx card. Could you add the output of "hwinfo --gfxcard"? Thanks.

Created attachment 76951 [details]
Output of hwinfo --gfxcard

Added the output of: hwinfo --gfxcard

fixed (by using fbdev driver) for RC1.