Stupid Intel Extreme Graphics not giving me full resolution!

Ian_Hawdon · 08-31-2006, 08:47 AM

Hi there,

As the school time is about to start again, i have acquired a laptop for use at school. The first thing i did was, get rid of the Operating System that seems to have infected the world (you know the one! :wink: ) and put SUSE 10.1 on.

Everything is working (even the WiFi card!) but the graphics card wont give me the full 1400x1050 resolution!

xorg.conf has the mode line in (SUSE's YaST even says 1400x1050)

I did read that the VBIOS may not have the resolution programmed into it, (that would explain why I had to use the Intel program to get the full size screen in wimbloz!)

when i use 855resolution i get this:

Code:

linux-ian-2704:/home/ian/downloads # 855resolution -l
855resolution version 0.4, by Alain Poirier

Chipset: Unknown (id=0x35758086)
VBIOS type: 3
VBIOS Version: 2501

Mode 30 : 640x480, 8 bits/pixel
Mode 31 : 640x400, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 36 : 1024x600, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1440, 8 bits/pixel
Mode 40 : 640x480, 15 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 42 : 800x600, 15 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 44 : 1024x768, 15 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 46 : 1024x600, 15 bits/pixel
Mode 47 : 1024x600, 16 bits/pixel
Mode 48 : 1280x1024, 15 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4a : 1600x1200, 15 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4c : 1920x1440, 15 bits/pixel
Mode 4d : 1920x1440, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 56 : 1024x600, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1440, 32 bits/pixel

So it is not there, OK I'll type this:

855resolution 5c 1400 1050

Code:

linux-ian-2704:/home/ian/downloads # 855resolution 5c 1400 1050
855resolution version 0.4, by Alain Poirier

Chipset: Unknown (id=0x35758086)
VBIOS type: 3
VBIOS Version: 2501

** Patch mode 5c to resolution 1400x1050 complete

YAY, it worked... erm no it didn't

Code:

linux-ian-2704:/home/ian/downloads # 855resolution -l
855resolution version 0.4, by Alain Poirier

Chipset: Unknown (id=0x35758086)
VBIOS type: 3
VBIOS Version: 2501

Mode 30 : 640x480, 8 bits/pixel
Mode 31 : 640x400, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 36 : 1024x600, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1440, 8 bits/pixel
Mode 40 : 640x480, 15 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 42 : 800x600, 15 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 44 : 1024x768, 15 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 46 : 1024x600, 15 bits/pixel
Mode 47 : 1024x600, 16 bits/pixel
Mode 48 : 1280x1024, 15 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4a : 1600x1200, 15 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4c : 1920x1440, 15 bits/pixel
Mode 4d : 1920x1440, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 56 : 1024x600, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1440, 32 bits/pixel <-- What is up with this?

WTF why is it STILL 1920x1440 ?

And why is 1400x1050 not there!

Please help, this is driving me nuts!

crashsystems · 08-31-2006, 12:01 PM

I was having a problem a a few months ago that sounds a lot like what you are dealing with (check out http://www.linuxquestions.org/questi...d.php?t=465994). Basically, how I solved it was by running "sudo dpkg-reconfigure xserver-xorg" in the terminal, and going through the xserver reconfiguration. When I got to the part for selecting available resolutions, I only selected the one I wanted my screen to use. Once I rebooted, everything was working fine. I hope this helps, so be sure to tell me how it goes.

crashsystems

Ian_Hawdon · 08-31-2006, 01:12 PM

The problem does not lie in X, the mode line is in there, if i remove all the other resolutions the VBIOS takes over and sets my screen to 1280x1024

The problem is that neither 855resolution nor 915resolution will change my VBIOS modes, 855resolution says it has but when told to list the modes, it has not changed them! 915resolution says because it is an unknown chipset (it knows it is intel but that's about it!) it wont change anything!

Back to the drawing board!

Ian_Hawdon · 09-02-2006, 11:48 AM

bumping up

Ian_Hawdon · 09-03-2006, 10:15 AM

anyone? please!

Ian_Hawdon · 09-04-2006, 10:27 AM

bump, bump ...

Ian_Hawdon · 09-06-2006, 03:19 PM

come on, someone must have had the same problem :-(

Ian_Hawdon · 09-09-2006, 04:26 PM

lost cause?

ColonelPanic · 09-09-2006, 05:14 PM

Quote:

Originally Posted by Ian_Hawdon

lost cause?

Not quite for 1400x1050 I suppose.
I'm having the same problem but further aggravated by my monitor's native res being 1680x1050. I got the 915resolution hack installed and running at boot time but I also have no real joy with it UNLESS I switch to the VESA driver (which is providing a quite limited performance to say the least). VESA is the only way for me to get 1680x1050 (so it states in the monitor's own hardware settings). However it seems like this is only a virtual resolution - acc to xorg.conf -and the GMA950 is really running at 1400x1050 which is blown up to 1680x1050. I DO get 1400x1050 though with the Intel 945 driver. It obviously doesn't do me any good but perhaps this gives you some new hope.

I'm still an absolute noob in Linux so I can't really give you clear instructions on how I did it. The important point seems to be that 915resolution starts up before everything else. From then on you should be able to just select your res in the hardware settings without any fiddling with xorg.conf.

good luck

btw can I assume you patched the 915resolution as root...?

russh · 10-12-2006, 07:07 AM

Quote:

Originally Posted by Ian_Hawdon

lost cause?

Yep, I have the same problem - T60 / Intel 945 chipset & SLED - 1400 x 1050 is shown in SaX2, but never applied. I've commented to this effect in an open bug report over at the Novell Bugzilla (bug 121905). I'll have a play in a bit to see if I can find any workarounds. I'll update the thread with anything I find.

Russ.

russh · 10-12-2006, 07:23 AM

A quick google gives this possible solution - not tried it yet;
http://linuxmint.com/content/view/212/29/

Ian_Hawdon · 10-12-2006, 11:51 AM

Like i said earlier, it does not update when i use the 855resolution command!

russh · 10-12-2006, 04:20 PM

Quote:

Originally Posted by Ian_Hawdon

lost cause?

Okay, I know it's not a genuine cure - but the first thing I tried worked - I killed the X server - dropped to a command line using INIT 3, logged in as root, and ran SaX2 from the command line - seems to run a different version of it(?). Luckily this seems to have allowed me to run at the 1400 x 1050 resolution!

Russ.

Electro · 10-12-2006, 04:55 PM

I do not recomend SUSE. It is pathetic and you can not edit its config files. I recommend using other distributions besides SUSE. SUSE is not Linux. It is another name for Windows.

BTW, do not even ask about getting 3D rendering to work. It only works with 16-bit color and it has limited instructions.

Ian_Hawdon · 10-12-2006, 05:36 PM

Quote:

Originally Posted by Electro

I do not recomend SUSE. It is pathetic and you can not edit its config files. I recommend using other distributions besides SUSE. SUSE is not Linux. It is another name for Windows.

BTW, do not even ask about getting 3D rendering to work. It only works with 16-bit color and it has limited instructions.

I had SUSE on it and it didn't work either, you can edit the config files in SUSE (it just wont let you open SAX ever again!)

I have given up on that laptop and have put windows on it and donated it to my mum, (she wouldn't care what OS is on it [although i think Micro$oft is upto something strange! {im not parinoid, they really are out to get me!}])

Thanks for all your help but I dont think that Graphics chip was ever ment to be!