Intel 910GL Limited Video Resolution in 4.1.2 [SOLVED]

[ecomoney]

EDIT:

Solved with much help!

Please apply .pet attached

Origional Post...

Hi, I am having problems getting above a 1024x768 screen resolution in puppy 4.1.2, even though I specify 1280x1024 in the xorgwizard. I also get the same problem in xvesa.

This machine is capable of higher resolutions in both ubuntu and puppy 2.15ce (ecopup).

Dont know if its connected...but seamonkey seems to be crashing a lot also with this configuration, even when just browsing the puppy forum (not usual flash shenanigans).

Here is my xorg.conf, can anyone shed some light on this?

Code: Select all

#Special base config file used in Puppy Linux.

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
    Load        "freetype"

# This loads xtrap extension, used by xrandr
    Load       "xtrap"

# This loads the GLX module (if present)
    Load       "glx"

# This loads dri module (if present)
    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath	"/usr/X11R7/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

    FontPath   "/usr/X11R7/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R7/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R7/lib/X11/fonts/TTF/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...

    Option "RandR" "on"

EndSection

#everything past here is auto-generated by Puppy's Xorg Wizard...


Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option      "XkbRules" "xorg"
	Option      "XkbModel" "pc102"
	Option      "XkbLayout" "gb" #xkeymap0
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2" #mouse0protocol
	Option	    "Device" "/dev/mouse"
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	Option      "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
	#DisplaySize	  320   240	# mm
	Identifier   "Monitor0"
	VendorName   "ACR"
	ModelName    "Acer AC713"
	### Comment all HorizSync and VertRefresh values to use DDC:
	Option	    "DPMS"
	HorizSync    30.0-72.0
	VertRefresh  50.0-85.0
	#UseModes     "Modes0" #monitor0usemodes
	Option      "PreferredMode" "1280x1024"
	EndSection
	
Section "Modes"
	Identifier "Modes0"
	#modes0modeline0
EndSection

Section "Device"
	### Available Driver options are:-
	### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
	### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
	### [arg]: arg optional
	#Option     "NoAccel"            	# [<bool>]
	#Option     "SWcursor"           	# [<bool>]
	#Option     "ColorKey"           	# <i>
	#Option     "CacheLines"         	# <i>
	#Option     "Dac6Bit"            	# [<bool>]
	#Option     "DRI"                	# [<bool>]
	#Option     "NoDDC"              	# [<bool>]
	#Option     "ShowCache"          	# [<bool>]
	#Option     "XvMCSurfaces"       	# <i>
	#Option     "PageFlip"           	# [<bool>]
	Identifier  "Card0"
	Driver      "intel" #card0driver
	VendorName  "Intel Corporation"
	BoardName   "82915G/GV/910GL Integrated Graphics Controller"
	BusID       "PCI:0:2:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
    DefaultDepth 24
    Subsection "Display"
        Depth       24
        Modes       "1280x1024"
    EndSubsection
EndSection

#PuppyHardwareProfile=Intel_r_Grantsdale_G_Graphics_ChipAcerAC713

[MU]

I think you need this tool:
http://www.murga-linux.com/puppy/viewtopic.php?t=32462
I think it is in Puppy 412 already, but the thread should explain, how to use it.
Mark

[Aitch]

seamonkey crashing?

try firepup - fast & stable

http://www.murga-linux.com/puppy/viewtopic.php?t=34061

Aitch

[ecomoney]

Hi, I tried the 915resolution package on your link you posted MU, as per instructions, I installed it, then did a ctrl/alt/backspace and type xorgwizard, selected the 1280x1024, but upon restarting x I was again greeted with only a 1024x768 screen. I noticed on the other thread that it relies on a device ID and this must be added tothe source code. Is my chipset included, and how to I find the device ID?

Am trying out you firepup now tuxxx....it does seem remarkably fast!

[tempestuous]

Is my chipset included, and how to I find the device ID?

ecomoney,
please run this command

Code: Select all

lspci -n

and post the results.

[ecomoney]

Code: Select all

00:00.0 Class 0600: 8086:2580 (rev 04)
00:01.0 Class 0604: 8086:2581 (rev 04)
00:02.0 Class 0300: 8086:2582 (rev 04)
00:1b.0 Class 0403: 8086:2668 (rev 03)
00:1c.0 Class 0604: 8086:2660 (rev 03)
00:1c.1 Class 0604: 8086:2662 (rev 03)
00:1c.2 Class 0604: 8086:2664 (rev 03)
00:1c.3 Class 0604: 8086:2666 (rev 03)
00:1d.0 Class 0c03: 8086:2658 (rev 03)
00:1d.1 Class 0c03: 8086:2659 (rev 03)
00:1d.2 Class 0c03: 8086:265a (rev 03)
00:1d.3 Class 0c03: 8086:265b (rev 03)
00:1d.7 Class 0c03: 8086:265c (rev 03)
00:1e.0 Class 0604: 8086:244e (rev d3)
00:1f.0 Class 0601: 8086:2640 (rev 03)
00:1f.1 Class 0101: 8086:266f (rev 03)
00:1f.2 Class 0101: 8086:2651 (rev 03)
00:1f.3 Class 0c05: 8086:266a (rev 03)
06:01.0 Class 0200: 1113:1211 (rev 10)
06:05.0 Class 0c00: 11c1:5811 (rev 61)
06:08.0 Class 0200: 8086:1064 (rev 03)

I actually did "lspci -n >> pci.txt" which sends the results to a text file, which I opened and copied and pasted the results. A little trick I learnt.

[tempestuous]

Well 8086:2580 is already a recognised pci id in 915resolution, so it may be a problem with how 915resolution is run from /usr/X11R7/bin/xwin. If you open this file in Geany, at line 110 you will see this -

Code: Select all

915resolution 38 $MYXRES $MYYRES

and maybe "38" is not a valid mode number for your graphics chip. Run this command to find out -

Code: Select all

915resolution -l

and if necessary, change "38" to a valid value.

[ecomoney]

Here are my results from running "915resolution -l"

Code: Select all

Intel 800/900 Series VBIOS Hack : version 0.5.3

Chipset: 915G
BIOS: TYPE 1
Mode Table Offset: $C0000 + $269
Mode Table Entries: 27

Mode 30 : 640x480, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
[u]Mode 38 : 1280x1024, 8 bits/pixel[/u]
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1440, 8 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4b : 1600x1200, 16 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 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1440, 32 bits/pixel

and here is the relevant section around line 110 of my xwin file

Code: Select all

   #v2.21 code to handle widescreen with intel video chips...
   if [ ! -f /etc/resolutionfix ];then
    if grep -F 'oem:' /tmp/ddcprobe.txt | grep -F -q 'Intel' ;then
     MISSINGXY=""
     for ONECUTXY in $MONCUTXY #ex: each field 1024x768
     do
      OPATTERN=" ${ONECUTXY}x"
      [ "`echo "$VESAMODES" | grep "$ONECUTXY"`" = "" ] && MISSINGXY="$ONECUTXY"
     done
     if [ "$MISSINGXY" != "" ];then
      MYXRES="`echo -n "$MISSINGXY" | cut -f 1 -d 'x'`" 
      MYYRES="`echo -n "$MISSINGXY" | cut -f 2 -d 'x'`" 
      915resolution 38 $MYXRES $MYYRES
      #...replaces mode 38 (1024x768).
      #create something for /etc/profile to execute at bootup...
      echo "915resolution 38 $MYXRES $MYYRES" > /etc/resolutionfix
      VESAMODES="`Xvesa -listmodes 2>&1 | grep '^0x' | tr ':' ' ' | tr -s ' ' | cut -f 1,2 -d ' '`"
      PPATTERN=" ${MYXRES}x${MYYRES}x"
      #BASEMOD is res that we are going to start X with...
      BASEMODE="`echo "$VESAMODES" | grep "$PPATTERN" | grep -E 'x16$|x24$|x32$' | head -n 1`"
     fi
    fi
   fi

Mode 38 seems to be valid according to the "915resolution -l" command, so I have not changed my xwin file. I dont know if its relevant, but I also do not have a file called /etc/resolutionfix , which I think the xwin script above should create?

Still the same problem then, I hope I have identified a bug in the code and it can be fixed for the next versions of puppy.

Thank you for your continued assistance tempestious. Let me know what other information I can provide.

[Aitch]

ecomoney, thanks

Your tip just became a basis for a new thread, TIPS & TRICKS

http://www.murga-linux.com/puppy/viewto ... 564#264564

good luck with your video problem

Aitch

[ecomoney]

Hi Aitch, WOW! Ive replied on the above thread

[ecomoney]

[BUMP]

Any news? not being able to run at higher resolutions would be a complete pain as many of our customers have this common chipset. How come it "broke" from previous puppies that would work with 915's?

[ICPUG]

ecomoney,

I had this problem with an Intel810 video card, although I wanted a lower rather than higher resolution. The problem was caused by the intel 810 driver being removed from Puppy 4 and beyond.

I filched the necessary driver from Puppy 3.01 and modified Puppy 4 to call it. The HowTo is here:

http://www.murga-linux.com/puppy/viewtopic.php?t=29144

I see from your xorg.conf that you are using the bog standard intel driver so maybe the 810 driver will help you. I know it works on the Intel 845 video cards but whether it works on 915 cards is anybody's guess.

Another alternative is to look at the xorg.conf file of one of those previous puppies that work. See what driver it is using. if different to intel810 then copy that one to Puppy 4 in a similar manner as I did with the intel 810.

Hope that helps

[ecomoney]

ICPUG thank you, that solution worked like a charm, am now running at a proper resolution. I think this is a case where "trimming the fat" went to far and cut out some of the flesh. Im going to report this as a bug, and point it out to the puppy 4.2 community edition team so hopefully it will be fixed for when it is released. I remember there was a similar bug in puppies pre-2.14 that meant that intel graphics cards would not run xorg at more than 800x600x16 which caused us loads of trouble.

For the sake of making this fix easier in the meantime for i915, i810 and possible other intel chipset users, Ive hosted the i810_drv.so file on our servers.

Quick fix

1. Download the i810_drv.so file from here. save it in /usr/X11R7/lib/xorg/modules/drivers saying that you wish to overwrite the existing file

2. Open up /etc/X11/xorg.conf and find the line where it says

Code: Select all

Driver "intel" #card0driver 

its under the section "device"

3. change the word "intel" inside the quotes to "i810", so it looks like this

Code: Select all

Driver "i810" #card0driver 

4. Save the xorg.conf file (ctrl-s is the shortcut for this)

5. from the start menu select "Restart X Server" from the shutdown menu

Resolutions should now work properly. Remember that to adjust the resolution of the screen you can press [ctrl]+[alt]+[bkspace] and type "xwin" to re-run the puppy setup wizards.

[ICPUG]

Glad that worked.

I think it is a bug too. I hope the 4.2 team are more ameniable than Barry.

He originally said he was going to incorporate the driver. See:

http://puppylinux.com/blog/?viewDetailed=00359


But later he decided not to! See:

http://puppylinux.com/blog/?viewDetailed=00362

Thank you for hosting the driver file and simplifying the HowTo instructions.

[HairyWill]

I would be interested see if this works after installing the full xorg pet from the ibiblio repository. It might be helpful to see any errors that are reported in /var/log/Xorg.0.log

[ecomoney]

Im sorry, the computer that I was testing this on overheated and blew...could be something to do with the cooler being held on with a piece of string...hmmmm I would test otherwise.