Bug 121905 - Can't set native mode (1680X1050) for Dell 2005FPW
Summary: Can't set native mode (1680X1050) for Dell 2005FPW
Status: RESOLVED DUPLICATE of bug 215673
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Final
Hardware: i686 SUSE Other
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Egbert Eich
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 02:49 UTC by Constantine Shtabnoy
Modified: 2006-10-27 13:40 UTC (History)
4 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/etc/X11/xorg.conf (4.83 KB, application/octet-stream)
2005-10-13 01:46 UTC, Constantine Shtabnoy
Details
/var/log/Xorg.0.log (40.59 KB, text/x-log)
2005-10-13 01:48 UTC, Constantine Shtabnoy
Details
/etc/init.d/boot.local (595 bytes, application/octet-stream)
2005-10-13 01:50 UTC, Constantine Shtabnoy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Constantine Shtabnoy 2005-10-10 02:49:39 UTC
I had just installed SUSE 10.0 on my PC.
Here is the configuration:
Motherboard: ASUS P5GDC-V Deluxe, Intel 915G chipset.
CPU: P4 2.8GHz. 800MHz FSB.
Video card: integrated Intel 915G.
Monitor: Dell 2005FPW.

This monitor is LCD with native resolution of 1680X1050. I have tried to set
this resolution with no luck. When I go to SaX2 and set this resolution, restart
the computer and it looks like X Windows is just ignoring this settings.
1680X1050 is written on SaX2 screen and in xorg.conf file but X Windows is
operating on 1280X1024 no metter what. When I go to YaST/Hadrware/Hardware
information, under "Framebuffer" (which is I suspect is the list of video modes
supported by the driver) I can't see 1680X1050 there.
I know that my hardware configuration can work in that mode because it works
fine under WinXP.
Comment 1 Stefan Dirsch 2005-10-10 05:08:15 UTC
This is a known problem. Could you try to workaround this with 855resolution? 
The package should be installed by default. 
Consult /usr/share/doc/packages/855resolution/README.txt for configuration 
details.  
  
IIRC with 10.1 (Alpha2) SaX2 will take care of this. 
Comment 2 Matthias Hopf 2005-10-10 10:40:00 UTC
I don't think a hack like 855resolution should be installed by default. Perhaps
a Wiki entry would help here.

Stefan, I though Alan had 855resolution included in his latest driver, or is
this one not yet released upstream?
Comment 3 Stefan Dirsch 2005-10-10 10:51:49 UTC
Hmm ... I thought that you all (Marcus, Seife, Matthias) decided to configure
this by default for 10.1 and this had been already done?!?

It does not look like Alan ahs already included the functionality of 
855resolution for 915G.
Comment 4 Matthias Hopf 2005-10-10 13:45:10 UTC
(In reply to comment #3)
> Hmm ... I thought that you all (Marcus, Seife, Matthias) decided to configure
> this by default for 10.1 and this had been already done?!?

I certainly do not know anything about that :-P
Comment 5 Stefan Dirsch 2005-10-12 13:16:18 UTC
Still waiting for feedback by the reporter.
Comment 6 Constantine Shtabnoy 2005-10-12 15:01:11 UTC
Sorry guys, I didn't get back to you earlier. In fact I fixed it just yesterday.
I promise to write more detailed report when I get home with attached config 
and log files for you consideration.

From the top of my head...
Here is what I did. I have changed one of VBIOS modes into 1680x1050 with 
915resolution which I belive is some later mutation of 855resolution. I choose 
915 one just because I actually have 915G chipset, but 855resolution worked 
fine two though. This thing along didn't help so I had to specify video timing 
explicitly. I don't realy remember this combination right now. Funny thing is 
that couldn't make it set 60Hz. I spend 2 hours playing with those numbers but 
couldn't make it work. It either switched to 1900x1600 or to 1200x1024 or 
1680x1050 but on 56Hz. In that mode monitor's auto adjastment made picture 
compressed from the sides. By adjusting of clock, phase, and position in 
monitor's menu I finally have atcheved acceptable picture. I can't say for sure 
but it looks like "blurry stripe" is still visible.   

Comment 7 Constantine Shtabnoy 2005-10-13 01:46:10 UTC
Created attachment 53903 [details]
/etc/X11/xorg.conf

As I promised
Comment 8 Constantine Shtabnoy 2005-10-13 01:48:29 UTC
Created attachment 53904 [details]
/var/log/Xorg.0.log
Comment 9 Constantine Shtabnoy 2005-10-13 01:50:07 UTC
Created attachment 53905 [details]
/etc/init.d/boot.local
Comment 10 Stefan Dirsch 2005-10-13 05:10:02 UTC
Ok. Thanks. 
Comment 11 Stefan Dirsch 2005-10-17 08:38:44 UTC
> Comments #1-4:

This needs to be discussed!
Comment 12 Stefan Dirsch 2005-10-20 16:57:58 UTC
It has been discussed meanwhile. We'll do this by default for 10.1. Closing as fixed.
Comment 17 Stefan Dirsch 2005-11-24 21:33:27 UTC
Feel free.
Comment 18 Stefan Dirsch 2005-11-29 15:13:07 UTC
IMHO this is no longer critical. Of course it would be better to see a solution inside the driver ... setting to NORMAL.
Comment 19 Egbert Eich 2006-02-16 08:35:44 UTC
Setting to enhancement
Comment 20 Forgotten User waLIv0Y828 2006-10-12 11:03:31 UTC
I have this same issue using SLED and a Thinkpad T60 - the native resolution of 1400 x 1050 cannot be set, and despite SaX2 showing this resolution, the 'text screen' and eventual resolution is set to 1280 x 1024. The chipset is intel 945GM
Comment 21 Stefan Dirsch 2006-10-27 13:40:48 UTC
This issue will be resolved with the new developped Intel driver (modesetting branch in git, still experimental).

*** This bug has been marked as a duplicate of bug 215673 ***