[quote]
Opus wrote:
...
Nothing happened :). As these are kernel mode drivers, so if i try this package [b]xorg-x11-drv-intel-2.18.0-1.fc17.x86_64.rpm[/b] then what would be the consequences? Fatal? If not fatal to corrupt the installation then may I try those? I know that the drivers shipped with [u]kernel 2.6.35[/u] were fine. [/quote]
Installing Fedora packages on EL is a [i][b]Very Bad Idea [TM][/b][/i]!
The [url=http://elrepo.org/tiki/tiki-index.php]ELRepo[/url] packages are based on the same upstream sources, but built for EL6 and not Fedora.
intel 965 display options
-
pschaff
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: intel 965 display options
[quote]
Opus wrote:
...
OK here is the complete output of the file, though EPEL repo is already enabled.[/quote]
EPEL != ELRepo
[quote]
...
== BEGIN rpm -qa \*-release\* ==
rpmforge-release-0.5.2-2.el6.rf.x86_64
epel-release-6-5.noarch
centos-release-6-2.el6.centos.7.x86_64
adobe-release-x86_64-1.0-1.noarch
== END rpm -qa \*-release\* ==
...
== BEGIN ls /etc/yum.repos.d ==
adobe-linux-x86_64.repo
atrpms-bleeding.repo
atrpms.repo
atrpms.repo~
atrpms-testing.repo
CentOS-Base.repo
CentOS-Base.repo~
CentOS-Debuginfo.repo
CentOS-Media.repo
CentOS-Media.repo~
epel.repo
epel.repo~
epel-testing.repo
google-chrome.repo
google.repo
linuxtech.repo
linuxtech.repo~
mirrors-rpmforge
mirrors-rpmforge-extras
mirrors-rpmforge-testing
rpmforge.repo
rpmforge.repo~
== END ls /etc/yum.repos.d ==
...
== BEGIN sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==
priority = 3 [atrpms]
priority = 3 [epel]
== END sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==
[/quote]
Your repo configs are a rather large mess. :-)
ATrpms, EPEL, RPMforge, and linuxtech are all mutually incompatible to some degree. You have the yum priorities plugin enabled but have priorities defined only for [atrpms] and [epel] which means those will override all the rest, including core repos, as the default is priority 99 - the lowest. Core packages may already have been overwritten, but fortunately ATrpms and EPEL are pretty good about not doing that, at least unless [atrpms-testing] is enabled.
As a first cut, I'd define "priority=1" for CentOS repos, and insert "enabled=0" in the repo configs for all 3rd party repos.
It is still unclear if the [url=http://elrepo.org/tiki/tiki-index.php]ELRepo[/url] package for [url=http://elrepo.org/tiki/xorg-x11-drv-intel]xorg-x11-drv-intel[/url] will help, but if you want to try it you need to install elrepo-release and[code]yum --noplugins --enablerepo elrepo-extras update xorg-x11-drv-intel[/code]or if feeling more adventurous[code]yum --noplugins --enablerepo elrepo-testing update xorg-x11-drv-intel[/code]
If you want to use [elrepo-extras] packages with yum-plugin-priorities enabled you must give that repo priority=1 and/or excluded needed packages from the CentOS repo configs as it contains packages that replace core packages. Using it as above is probably preferable unless you are very comfortable with the content there and with your (hopefully improved) repo configs.
Opus wrote:
...
OK here is the complete output of the file, though EPEL repo is already enabled.[/quote]
EPEL != ELRepo
[quote]
...
== BEGIN rpm -qa \*-release\* ==
rpmforge-release-0.5.2-2.el6.rf.x86_64
epel-release-6-5.noarch
centos-release-6-2.el6.centos.7.x86_64
adobe-release-x86_64-1.0-1.noarch
== END rpm -qa \*-release\* ==
...
== BEGIN ls /etc/yum.repos.d ==
adobe-linux-x86_64.repo
atrpms-bleeding.repo
atrpms.repo
atrpms.repo~
atrpms-testing.repo
CentOS-Base.repo
CentOS-Base.repo~
CentOS-Debuginfo.repo
CentOS-Media.repo
CentOS-Media.repo~
epel.repo
epel.repo~
epel-testing.repo
google-chrome.repo
google.repo
linuxtech.repo
linuxtech.repo~
mirrors-rpmforge
mirrors-rpmforge-extras
mirrors-rpmforge-testing
rpmforge.repo
rpmforge.repo~
== END ls /etc/yum.repos.d ==
...
== BEGIN sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==
priority = 3 [atrpms]
priority = 3 [epel]
== END sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==
[/quote]
Your repo configs are a rather large mess. :-)
ATrpms, EPEL, RPMforge, and linuxtech are all mutually incompatible to some degree. You have the yum priorities plugin enabled but have priorities defined only for [atrpms] and [epel] which means those will override all the rest, including core repos, as the default is priority 99 - the lowest. Core packages may already have been overwritten, but fortunately ATrpms and EPEL are pretty good about not doing that, at least unless [atrpms-testing] is enabled.
As a first cut, I'd define "priority=1" for CentOS repos, and insert "enabled=0" in the repo configs for all 3rd party repos.
It is still unclear if the [url=http://elrepo.org/tiki/tiki-index.php]ELRepo[/url] package for [url=http://elrepo.org/tiki/xorg-x11-drv-intel]xorg-x11-drv-intel[/url] will help, but if you want to try it you need to install elrepo-release and[code]yum --noplugins --enablerepo elrepo-extras update xorg-x11-drv-intel[/code]or if feeling more adventurous[code]yum --noplugins --enablerepo elrepo-testing update xorg-x11-drv-intel[/code]
If you want to use [elrepo-extras] packages with yum-plugin-priorities enabled you must give that repo priority=1 and/or excluded needed packages from the CentOS repo configs as it contains packages that replace core packages. Using it as above is probably preferable unless you are very comfortable with the content there and with your (hopefully improved) repo configs.
Re: intel 965 display options
thanks Phil for pointing out the repo mess. My mistake!!! I'll set the proper priority of these. Let's see the testing el repo. I'll post soon enough. Thanks once again
-
pschaff
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: intel 965 display options
You are welcome. Please ask if you have and additional questions, and let us know how it goes.
Re: intel 965 display options
Looks good now. All disabled except base and updates. Though, nothing new happened, so this is my guess that I gotta be happy with current config as nothing more I may be able to do till a RHEL 7.0 based CentOS 7.0 gets released with new kernel and latest xorg drivers. I don't wanna go back to Gnome 3.x or Unity (Damn slow) as I love Gnome 2.x.
However, if there is still a solution to driver problem then, I'll appreciate to become aware about that. Thanks
[quote]== BEGIN sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==
priority = 1 [base]
priority = 1 [centosplus]
priority = 1 [contrib]
priority = 1 [extras]
priority = 1 [updates]
priority = 2 [adobe-linux-x86_64]
priority = 2 [google-chrome]
priority = 3 [epel]
priority = 3 [epel-debuginfo]
priority = 3 [epel-source]
priority = 3 [rpmforge]
priority = 3 [rpmforge-extras]
priority = 3 [rpmforge-testing]
priority = 4 [atrpms]
priority = 4 [atrpms-debuginfo]
priority = 4 [atrpms-source]
== END sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==[/quote]
However, if there is still a solution to driver problem then, I'll appreciate to become aware about that. Thanks
[quote]== BEGIN sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==
priority = 1 [base]
priority = 1 [centosplus]
priority = 1 [contrib]
priority = 1 [extras]
priority = 1 [updates]
priority = 2 [adobe-linux-x86_64]
priority = 2 [google-chrome]
priority = 3 [epel]
priority = 3 [epel-debuginfo]
priority = 3 [epel-source]
priority = 3 [rpmforge]
priority = 3 [rpmforge-extras]
priority = 3 [rpmforge-testing]
priority = 4 [atrpms]
priority = 4 [atrpms-debuginfo]
priority = 4 [atrpms-source]
== END sed -n -e "/^\[/h; /priority *=/{ G; s/\n/ /; s/ity=/ity = /; p }" /etc/yum.repos.d/*.repo | sort -k3n ==[/quote]
-
pschaff
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: intel 965 display options
If I were you I'd try the [elrepo-extras] or -testing drivers, but then if you look at the Packager, you may suspect that I'm somewhat prejudiced. :-D
-
AlanBartlett
- Forum Moderator
- Posts: 9345
- Joined: 2007/10/22 11:30:09
- Location: ~/Earth/UK/England/Suffolk
- Contact:
Re: intel 965 display options
Hmm [img]http://www.centos.toracat.org/ajb/tmp/hmmm.gif[/img]
Having seen the previous mess that the repositories' configuration were in, it might be an idea to first perform a [i]yum[/i] controlled re-install of the packages --
[code]
[b]yum reinstall \*[/b]
[/code]
Assuming that completes without error, then re-boot the system.
Once it is back running, now install the configuration file to be able to access the [url=http://elrepo.org]ELRepo Project[/url] repositories. Then you should be good to [i]yum[/i] update the relevant [b]xorg-x11-drv-intel[/b] package . . .
Having seen the previous mess that the repositories' configuration were in, it might be an idea to first perform a [i]yum[/i] controlled re-install of the packages --
[code]
[b]yum reinstall \*[/b]
[/code]
Assuming that completes without error, then re-boot the system.
Once it is back running, now install the configuration file to be able to access the [url=http://elrepo.org]ELRepo Project[/url] repositories. Then you should be good to [i]yum[/i] update the relevant [b]xorg-x11-drv-intel[/b] package . . .
Re: intel 965 display options
If you no longer have an /etc/X11/xorg.conf and your log file still says that it's loading the 'vesa' driver then I think you need to force it to use the intel driver. The 965 is so old that it really ought to be supported by the current xorg-x11-drv-intel package without needing to use newer ones. You might try running `X -configure` and then using the resulting config file that that generates or you could try hand crafting your own, perhaps mine from a 945 based system might help...
[code]
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "catalogue:/etc/X11/fontpath.d"
FontPath "built-ins"
EndSection
Section "Module"
Load "dri2"
Load "glx"
Load "extmod"
Load "dri"
Load "record"
Load "dbe"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "DRI" # [<bool>]
#Option "ColorKey" # <i>
#Option "VideoKey" # <i>
#Option "FallbackDebug" # [<bool>]
#Option "Tiling" # [<bool>]
#Option "LinearFramebuffer" # [<bool>]
#Option "Shadow" # [<bool>]
#Option "SwapbuffersWait" # [<bool>]
#Option "TripleBuffer" # [<bool>]
#Option "XvMC" # [<bool>]
#Option "XvPreferOverlay" # [<bool>]
#Option "DebugFlushBatches" # [<bool>]
#Option "DebugFlushCaches" # [<bool>]
#Option "DebugWait" # [<bool>]
#Option "HotPlug" # [<bool>]
#Option "RelaxedFencing" # [<bool>]
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
[/code]
[code]
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "catalogue:/etc/X11/fontpath.d"
FontPath "built-ins"
EndSection
Section "Module"
Load "dri2"
Load "glx"
Load "extmod"
Load "dri"
Load "record"
Load "dbe"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "DRI" # [<bool>]
#Option "ColorKey" # <i>
#Option "VideoKey" # <i>
#Option "FallbackDebug" # [<bool>]
#Option "Tiling" # [<bool>]
#Option "LinearFramebuffer" # [<bool>]
#Option "Shadow" # [<bool>]
#Option "SwapbuffersWait" # [<bool>]
#Option "TripleBuffer" # [<bool>]
#Option "XvMC" # [<bool>]
#Option "XvPreferOverlay" # [<bool>]
#Option "DebugFlushBatches" # [<bool>]
#Option "DebugFlushCaches" # [<bool>]
#Option "DebugWait" # [<bool>]
#Option "HotPlug" # [<bool>]
#Option "RelaxedFencing" # [<bool>]
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
[/code]
Re: intel 965 display options
OK X -configure failed to create new file as the number of displays reported and detected were not the same (Though I am just using the laptop display ONLY).
So far I have reached at the conclusion that the CentOS is using the VESA while OpenSUSE is using the Intel Driver.
I did few things as under:
[quote]xrandr --newmode "1280x800"x60.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync
[root@xenon home]# xrandr -q
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1280 x 800
default connected 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0
1280x800_60.00 59.8
1280x800x60.0 (0x12b) 69.3MHz
h: width 1280 start 1296 end 1344 total 1416 skew 0 clock 48.9KHz
v: height 800 start 801 end 804 total 816 clock 60.0Hz
[root@xenon home]# xrandr --addmode default 1280x800x60.0
[root@xenon home]# xrandr --output default --mode 1280x800x60.0
xrandr: Configure crtc 0 failed [/quote]
Then I turned to OpenSUSE 12.1 LiveCD and checked the xorg.log file. My current file is here
[quote][ 143.801] (II) VESA(0): Unknown vendor-specific block f
[ 143.801] (II) VESA(0): SAMSUNG
[ 143.801] (II) VESA(0): LTN154X3-L01
[ 143.801] (II) VESA(0): EDID (in hex):
[ 143.801] (II) VESA(0): 00ffffffffffff004ca3454d00000000
[ 143.801] (II) VESA(0): 00110103802115780a87f594574f8c27
[ 143.801] (II) VESA(0): 27505400000001010101010101010101
[ 143.802] (II) VESA(0): 010101010101121b0088502010301030
[ 143.802] (II) VESA(0): 13004bcf100000190000000f00000000
[ 143.802] (II) VESA(0): 00000000002387026404000000fe0053
[ 143.802] (II) VESA(0): 414d53554e470a2020202020000000fe
[ 143.802] (II) VESA(0): 004c544e31353458332d4c30310a001b
[ 143.802] (II) VESA(0): EDID vendor "SEC", prod id 19781
[ 143.802] (II) VESA(0): Printing DDC gathered Modelines:
[ 143.802] (II) VESA(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 143.802] (II) VESA(0): Searching for matching VESA mode(s):
[ 143.802] Mode: 160 (0x0)[/quote]
While the OpenSUSE 12.1 LiveCD file is here where I can clearly watch LVDS1 being detected.
[quote][ 186.978] (II) intel(0): Unknown vendor-specific block f
[ 186.978] (II) intel(0): SAMSUNG
[ 186.978] (II) intel(0): LTN154X3-L01
[ 186.978] (II) intel(0): EDID (in hex):
[ 186.978] (II) intel(0): 00ffffffffffff004ca3454d00000000
[ 186.978] (II) intel(0): 00110103802115780a87f594574f8c27
[ 186.978] (II) intel(0): 27505400000001010101010101010101
[ 186.978] (II) intel(0): 010101010101121b0088502010301030
[ 186.978] (II) intel(0): 13004bcf100000190000000f00000000
[ 186.978] (II) intel(0): 00000000002387026404000000fe0053
[ 186.978] (II) intel(0): 414d53554e470a2020202020000000fe
[ 186.978] (II) intel(0): 004c544e31353458332d4c30310a001b
[ 186.978] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 186.978] (II) intel(0): Printing DDC gathered Modelines:
[ 186.978] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 186.979] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 186.979] (II) intel(0): Printing probed modes for output LVDS1
[ 186.979] (II) intel(0): Modeline "1280x800"x60.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 186.979] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 186.979] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 186.979] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 186.979] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 186.995] (II) intel(0): EDID for output VGA1
[ 187.248] (II) intel(0): EDID for output TV1
[ 187.248] (II) intel(0): Output LVDS1 connected
[189.039] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 189.039] (II) intel(0): Printing DDC gathered Modelines:
[ 189.039] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 192.710] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 192.710] (II) intel(0): Printing DDC gathered Modelines:
[ 192.710] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 194.496] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 194.496] (II) intel(0): Printing DDC gathered Modelines:
[ 194.496] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 194.862] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 194.862] (II) intel(0): Printing DDC gathered Modelines:
[ 194.862] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 195.135] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 195.135] (II) intel(0): Printing DDC gathered Modelines:
[ 195.135] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 195.426] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 195.426] (II) intel(0): Printing DDC gathered Modelines:
[ 195.426] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 195.733] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 195.733] (II) intel(0): Printing DDC gathered Modelines:
[ 195.733] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 206.459] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 206.764] (II) intel(0): Printing DDC gathered Modelines:
[ 206.764] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)[/quote]
Both the xorg.log files and the new xorg.conf.new are here
[url=http://www.box.com/s/9036de0ddde7d7c55d16]xorg.conf.new[/url]
[url=http://www.box.com/s/dd4667bc793e9618bbb6]Xorg-OpenSUSE.log[/url]
[url=http://www.box.com/s/159bfa134ca65f34a13f]Xorg-CentOS.log[/url]
So far I have reached at the conclusion that the CentOS is using the VESA while OpenSUSE is using the Intel Driver.
I did few things as under:
[quote]xrandr --newmode "1280x800"x60.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync
[root@xenon home]# xrandr -q
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1280 x 800
default connected 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0
1280x800_60.00 59.8
1280x800x60.0 (0x12b) 69.3MHz
h: width 1280 start 1296 end 1344 total 1416 skew 0 clock 48.9KHz
v: height 800 start 801 end 804 total 816 clock 60.0Hz
[root@xenon home]# xrandr --addmode default 1280x800x60.0
[root@xenon home]# xrandr --output default --mode 1280x800x60.0
xrandr: Configure crtc 0 failed [/quote]
Then I turned to OpenSUSE 12.1 LiveCD and checked the xorg.log file. My current file is here
[quote][ 143.801] (II) VESA(0): Unknown vendor-specific block f
[ 143.801] (II) VESA(0): SAMSUNG
[ 143.801] (II) VESA(0): LTN154X3-L01
[ 143.801] (II) VESA(0): EDID (in hex):
[ 143.801] (II) VESA(0): 00ffffffffffff004ca3454d00000000
[ 143.801] (II) VESA(0): 00110103802115780a87f594574f8c27
[ 143.801] (II) VESA(0): 27505400000001010101010101010101
[ 143.802] (II) VESA(0): 010101010101121b0088502010301030
[ 143.802] (II) VESA(0): 13004bcf100000190000000f00000000
[ 143.802] (II) VESA(0): 00000000002387026404000000fe0053
[ 143.802] (II) VESA(0): 414d53554e470a2020202020000000fe
[ 143.802] (II) VESA(0): 004c544e31353458332d4c30310a001b
[ 143.802] (II) VESA(0): EDID vendor "SEC", prod id 19781
[ 143.802] (II) VESA(0): Printing DDC gathered Modelines:
[ 143.802] (II) VESA(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 143.802] (II) VESA(0): Searching for matching VESA mode(s):
[ 143.802] Mode: 160 (0x0)[/quote]
While the OpenSUSE 12.1 LiveCD file is here where I can clearly watch LVDS1 being detected.
[quote][ 186.978] (II) intel(0): Unknown vendor-specific block f
[ 186.978] (II) intel(0): SAMSUNG
[ 186.978] (II) intel(0): LTN154X3-L01
[ 186.978] (II) intel(0): EDID (in hex):
[ 186.978] (II) intel(0): 00ffffffffffff004ca3454d00000000
[ 186.978] (II) intel(0): 00110103802115780a87f594574f8c27
[ 186.978] (II) intel(0): 27505400000001010101010101010101
[ 186.978] (II) intel(0): 010101010101121b0088502010301030
[ 186.978] (II) intel(0): 13004bcf100000190000000f00000000
[ 186.978] (II) intel(0): 00000000002387026404000000fe0053
[ 186.978] (II) intel(0): 414d53554e470a2020202020000000fe
[ 186.978] (II) intel(0): 004c544e31353458332d4c30310a001b
[ 186.978] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 186.978] (II) intel(0): Printing DDC gathered Modelines:
[ 186.978] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 186.979] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 186.979] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 186.979] (II) intel(0): Printing probed modes for output LVDS1
[ 186.979] (II) intel(0): Modeline "1280x800"x60.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 186.979] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 186.979] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 186.979] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 186.979] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 186.995] (II) intel(0): EDID for output VGA1
[ 187.248] (II) intel(0): EDID for output TV1
[ 187.248] (II) intel(0): Output LVDS1 connected
[189.039] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 189.039] (II) intel(0): Printing DDC gathered Modelines:
[ 189.039] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 192.710] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 192.710] (II) intel(0): Printing DDC gathered Modelines:
[ 192.710] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 194.496] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 194.496] (II) intel(0): Printing DDC gathered Modelines:
[ 194.496] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 194.862] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 194.862] (II) intel(0): Printing DDC gathered Modelines:
[ 194.862] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 195.135] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 195.135] (II) intel(0): Printing DDC gathered Modelines:
[ 195.135] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 195.426] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 195.426] (II) intel(0): Printing DDC gathered Modelines:
[ 195.426] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 195.733] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 195.733] (II) intel(0): Printing DDC gathered Modelines:
[ 195.733] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)
[ 206.459] (II) intel(0): EDID vendor "SEC", prod id 19781
[ 206.764] (II) intel(0): Printing DDC gathered Modelines:
[ 206.764] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1296 1344 1416 800 801 804 816 -hsync -vsync (48.9 kHz)[/quote]
Both the xorg.log files and the new xorg.conf.new are here
[url=http://www.box.com/s/9036de0ddde7d7c55d16]xorg.conf.new[/url]
[url=http://www.box.com/s/dd4667bc793e9618bbb6]Xorg-OpenSUSE.log[/url]
[url=http://www.box.com/s/159bfa134ca65f34a13f]Xorg-CentOS.log[/url]
Re: intel 965 display options
I really dislike your choice of paste host - they suck :-(
The CentOS log clearly shows that it's still using the vesa driver and not the intel one. I'm afraid I'm confused about which file is which and what you did. Why not just try the Suse xorg.conf on CentOS?
The CentOS log clearly shows that it's still using the vesa driver and not the intel one. I'm afraid I'm confused about which file is which and what you did. Why not just try the Suse xorg.conf on CentOS?