| View previous topic :: View next topic |
| Author |
Message |
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
 Posted: Tue Mar 27, 2007 12:22 am Post subject: I810 855GM doubble buffer & DRI |
 |
|
Need some advice on getting a big wide desktop. 
I apologize if this was posted in 100 other places. I have not found anything thet works with this exact setup.
I have a | Code: | 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
|
On my Toshiba Laptop I have a VGA out .
I use the i810 driver.
Last edited by turtles on Thu Dec 27, 2007 11:59 am; edited 5 times in total |
|
| Back to top |
|
 |
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Fri Aug 24, 2007 8:53 pm Post subject: MergedFB |
|
|
Revelant log info: | Code: | grep '(EE)' xlog.txt
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) I810(0): Monitor 1 and 2 cannot be type NONE
(EE) I810(1): Monitor 1 or Monitor 2 cannot be type NONE in DualHead, Clone or MergedFB setup.
(EE) Screen(s) found, but none have a usable configuration.
|
EDIT: | Code: | # MY X Server Configuration file
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "First" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Screen 1 "Second" RightOf "First"
EndSection
Section "ServerFlags"
Option "DefaultServerLayout" "X.org Configured"
EndSection
Section "Files"
(EDIT out fonts)
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "dbe"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "type1"
Load "xtrap"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Device"
Identifier "Inta0"
Driver "i810"
VendorName "Intel Corporation"
BusID "PCI:0:2:0"
Option "MonitorLayout" "AUTO, AUTO"
Screen 0
EndSection
Section "Device"
Identifier "Inta1"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "LVDS, AUTO"
Option "MergedFB" "true"
Screen 1
EndSection
Section "Monitor"
Identifier "First"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Second"
DisplaySize 270 203
VendorName "Hewlett-Packard"
ModelName "hp pavilion f1503"
HorizSync 30.0 - 63.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection
Section "Screen"
Identifier "First"
Device "Inta0"
Monitor "First"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1024x768"
Virtual 2048 768
Viewport 0 0
EndSubsection
EndSection
#Laptop
Section "Screen"
Identifier "Second"
Device "Inta1"
Monitor "Second"
DefaultDepth 24
SubSection "Display"
### 1024x768-1024x768
Modes "1024x768"
Virtual 2048 768
EndSubSection
### 1024x768
SubSection "Display"
Modes "1024x768"
Virtual 1024 768
EndSubsection
EndSection
|
|
|
| Back to top |
|
|
fuzzythebear
Guru
Joined: 28 Nov 2004
Posts: 317
|
| Posted: Sat Aug 25, 2007 7:48 pm Post subject: |
|
|
Im not 100 % sure but i beleive i see what's wrong .. i can be wrong though
happened to me once when i was thinking i'd done a mistake ; )
This is my working mergedFB config , i left the irrelevant
parts out , they are top secret and the FBI would hunt you down
and eliminate you if you were to see it ... ( yeah .. right ; )
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
DisplaySize 347 260
Option "VendorName" "ATI open source driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Gamma 0.00 0.00 0.00 # created by KGamma
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "radeon"
BusID "PCI:1:0:0"
Screen 0 Option "EnablePageFlip" "on"
Option "UseFastTLS" "0"
Option "MergedFB" "true"
option "MetaModes" "1024x768-1024x768"
Option "CRT2Position" "RightOf"
Option "ForceCRT2Type" "VGA"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Depth 24
Virtual 2048 768
Modes "1024x768"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "aticonfig-Screen[0]"
InputDevice "Keyboard1"
InputDevice "Mouse1"
EndSection
Section "DRI"
Mode 0666
EndSection
I got 1700+ fps with a radeon 9250 for the whole
screen left and right.it's great but also leads to problems
with apps that put their full screen right in the middle between
the screens 
Fuzzy |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Mon Aug 27, 2007 2:38 am Post subject: |
|
|
I think pci pci@0000:00:02.1 should be the external vga out connector but if I boot with the monitor plugged in pci@0000:00:02.0 is assigned to it and the laptops monitor is off.
EDIT Removed old file
Last edited by turtles on Sun Sep 02, 2007 5:37 pm; edited 3 times in total |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Tue Aug 28, 2007 7:22 am Post subject: |
|
|
Edit removed un needed
Last edited by turtles on Sun Sep 02, 2007 5:38 pm; edited 1 time in total |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Sat Sep 01, 2007 8:44 pm Post subject: |
|
|
The question seems to be do I need the i915 module? I have support for the 855GM compiled in to the kernel.
Hardware support > graffics support> | Code: | | <*> Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL) |
and | Code: | | [*] DDC/I2C for Intel framebuffer support |
and under
Device drivers > character devices > | Code: | <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) │ │
│ │ < > 3dfx Banshee/Voodoo3+ │ │
│ │ < > ATI Rage 128 │ │
│ │ < > ATI Radeon │ │
│ │ <M> Intel I810 │ │
│ │ <M> Intel 830M, 845G, 852GM, 855GM, 865G │ │
│ │ <M> i830 driver │ │
│ │ <M> i915 driver |
I guess I could try compiling in the 855GM charactor device and see if that works.
But it has the choice to use it or not and it chooses the i915.
Edit: atempted vesa driver got one big wide display on pipe B but 1/2 screen and kind of repeating.
Reading: http://linux.die.net/man/4/i810
Last edited by turtles on Sun Sep 02, 2007 7:29 pm; edited 1 time in total |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Sun Sep 02, 2007 6:07 pm Post subject: |
|
|
Now with this config I get no errors and no monitors so I may be close.
EDIT: Running X -config /path/to/test-file lets me use cntrl -c to abort instead of hard locking kernel like before..
Here are some revealing parts of LOG:
| Code: | grep '(WW)\ ' lapcat/xlog-better
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
(WW) The directory "/usr/share/fonts/fonts.cache-1" does not exist.
(WW) The directory "/usr/share/fonts/ttf-bitstream-verals" does not exist.
(WW) The directory "/usr/share/fonts/unfont" does not exist.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) I810(0): Invalid Monitor type specified for Pipe B
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Failed to set display devices to 0x8.
(WW) I810(0): Enabling LVDS directly. Pipe A.
(WW) I810(0): Disabling ADPA directly.
(WW) I810(0): Writing config directly to SWF0.
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Failed to set display devices to 0x8.
(WW) I810(0): Enabling LVDS directly. Pipe A.
(WW) I810(0): Disabling ADPA directly.
(WW) I810(0): Writing config directly to SWF0.
(WW) I810(0): Option "Screen" is not used
(WW) Option "XkbLayout" requires an string value
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(WW) I810(0): Successfully set original devices (2)
|
I messed with the bios settings and did not get different results.
This seems to be out of date but interesting http://www.xfree86.org/~dawes/845driver.html
Edit:
Well I see | Code: | lspci | grep '855GM'
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics D evice (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device ( rev 02)
|
I tryed 0:2:0 as the VGA out and 0:2:1 as the local display. Not much difference.
According to this email archive they need to be the same to indicate a shared device.
I am looking into the bios errors. Looks like a package i915resoloution does some custome bios stuff now what to do with it??
| Quote: | *
* 915resolution alters your video BIOS in a non-permanent way, this means
* that there is no risk of permanent damage to your video card, but
* it also means that it must be run at every boot. To set it up,
* edit /etc/conf.d/915resolution to add your configuration and type the
* following command to add it the your defautl runlevel:
*
* "rc-update add 915resolution default" |
This does not seem to be a resolution problem skipping this.
More interesting kernel messages:
Sep 2 11:16:05 lapcat ACPI: Video Device [VGA] (multi-head: yes rom: yes post: no)
Sep 2 11:16:05 lapcat Using specific hotkey driver
Sep 2 11:16:05 lapcat ACPI: CPU0 (power states: C1[C1] C2[C2])
Sep 2 11:16:05 lapcat ACPI: Thermal Zone [THRM] (53 C)
Sep 2 11:16:05 lapcat toshiba_acpi: Toshiba Laptop ACPI Extras version 0.18
Sep 2 11:16:05 lapcat toshiba_acpi: HCI method: \_SB_.VALZ.GHCI
Sep 2 11:16:05 lapcat intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
Sep 2 11:16:05 lapcat intelfb: Version 0.9.4
Sep 2 11:16:05 lapcat ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
Sep 2 11:16:05 lapcat intelfb: 00:02.0: Intel(R) 852GME, aperture size 128MB, stolen memory 16252kB
Sep 2 11:16:05 lapcat intelfb: Mode is interlaced.
Sep 2 11:16:05 lapcat intelfb: Initial video mode is 1024x768-32@70.
Sep 2 11:16:05 lapcat Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Sep 2 11:16:05 lapcat ACPI: PCI Interrupt 0000:00:1f.6[B] -> GSI 17 (level, low) -> IRQ 18
Last edited by turtles on Thu Dec 27, 2007 5:55 am; edited 2 times in total |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Mon Sep 03, 2007 4:32 pm Post subject: |
|
|
Well the video RAM on this Toshiba A45-S120 is "shared memory" So I will go back to the bios to see if there is a setting.
EDIT no bios setting available. I am using BIOS version 1.30
I am getting the error | Code: | grep '(WW)' /var/log/Xorg.0.log.old
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Failed to set display devices to 0x80.
(WW) I810(0): Disabling LVDS directly.
(WW) I810(0): Disabling ADPA directly.
(WW) I810(0): Writing config directly to SWF0.
turtle@lapcat ~ $ grep '(EE)' /var/log/Xorg.0.log.old
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) I810(0): No Video BIOS modes for chosen depth.
(EE) Screen(s) found, but none have a usable configuration.
|
With external monitor pluged in:
| Code: | grep 'Pipe' /var/log/Xorg.0.log.old
(II) I810(0): Currently active displays on Pipe A:
(II) I810(0): No active displays on Pipe B.
(==) I810(0): Display is using Pipe A |
Booting without external monitor:
| Code: | grep 'Pipe' /var/log/Xorg.0.log
(II) I810(0): No active displays on Pipe A.
(II) I810(0): Currently active displays on Pipe B:
(==) I810(0): Display is using Pipe B
(II) I810(0): Display plane A is disabled and connected to Pipe A.
(II) I810(0): Display plane B is enabled and connected to Pipe B.
(II) I810(0): Display plane A is now disabled and connected to Pipe A.
(II) I810(0): Display plane B is now enabled and connected to Pipe B |
So note that the internal display is pipe B.
This is how I have it set up:
| Code: | (**) I810(0): Option "MonitorLayout" "LFP2,LFP"
(II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1024,768)
(II) I810(0): Display Info: LFP2 (second local flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Size of device LFP (local flat panel) is 1024 x 768
(II) I810(0): LFP (local flat panel)
|
I could change "MonitorLayout" "LFP2,LFP" to "MonitorLayout" "LFP,LVDS"
EDIT: Tried this and the system hard locks.
Any other ideas would be great.
I have emerged 915resolution but not sure what to do with it or if it will help.
Note emerging acpid got rid of some errors in my logfile.
Edit2: ADDED 32MB video ram enabled
| Code: | grep -e WW -e EE e-Viedo e-Memory /var/log/Xorg.0.log
grep: e-Viedo: No such file or directory
grep: e-Memory: No such file or directory
/var/log/Xorg.0.log: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
/var/log/Xorg.0.log:(II) Loading extension MIT-SCREEN-SAVER
/var/log/Xorg.0.log:(WW) I810(0): Extended BIOS function 0x5f05 failed.
/var/log/Xorg.0.log:(EE) AIGLX: Screen 0 is not DRI capable
lapcat ~ # grep -e WW -e EE -e'Video' -e'Memory' -e'Pipe' /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
X.Org Video Driver: 1.1
ABI class: X.Org Video Driver, version 1.1
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.1
ABI class: X.Org Video Driver, version 1.1
ABI class: X.Org Video Driver, version 1.1
ABI class: X.Org Video Driver, version 1.1
(**) I810(0): Option "XVideo" "on"
(II) I810(0): I830CheckAvailableMemory: 1198076 kB available
(--) I810(0): Pre-allocated VideoRAM: 16252 kByte
(**) I810(0): VideoRAM: 32768 kByte
(II) I810(0): No active displays on Pipe A.
(II) I810(0): Currently active displays on Pipe B:
(==) I810(0): Display is using Pipe B
ABI class: X.Org Video Driver, version 1.1
(II) I810(0): Supported VESA Video Modes:
(II) I810(0): Supported additional Video Mode:
MemoryModel: 4
MemoryModel: 4
MemoryModel: 4
MemoryModel: 4
MemoryModel: 4
MemoryModel: 4
MemoryModel: 4
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
MemoryModel: 6
ABI class: X.Org Video Driver, version 1.1
(II) I810(0): 0x81f2780: Memory at offset 0x00020000, size 18432 kBytes
(II) I810(0): 0x81f3280: Memory at offset 0x00000000, size 0 kBytes
(II) I810(0): 0x81f32a8: Memory at offset 0x00000000, size 0 kBytes
(II) I810(0): 0x81f32d4: Memory at offset 0x00000000, size 128 kBytes
(II) I810(0): 0x81f27c0: Memory at offset 0x07fef000, size 64 kBytes
(II) I810(0): 0x81f3988: Memory at offset 0x07fff000, size 4 kBytes
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(II) I810(0): xf86BindGARTMemory: bind key 2 at 0x00fdf000 (pgoffset 4063)
(II) I810(0): xf86BindGARTMemory: bind key 1 at 0x07fef000 (pgoffset 32751)
(II) I810(0): xf86BindGARTMemory: bind key 0 at 0x07fff000 (pgoffset 32767)
(II) I810(0): Display plane A is disabled and connected to Pipe A.
(II) I810(0): Display plane B is enabled and connected to Pipe B.
(II) I810(0): Display plane A is now disabled and connected to Pipe A.
(II) I810(0): Display plane B is now enabled and connected to Pipe B.
(EE) AIGLX: Screen 0 is not DRI capable
|
_________________
Donate to Gentoo |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1670
|
| Posted: Thu Dec 27, 2007 12:37 pm Post subject: Alive and well... still working on i810 & doubble buffer |
|
|
Well I am trying all this again with latest versions of stuff and am getting along.
Hopefully I can get a pair of eyes to look at what is going on in my log file
I have posted my xorg.conf here
I have been looking at the i810 info here.
I added there comments to my config.
What I get from all this research is: 1) i810 and other drivers like nvidia have very different setups in xorg.conf so if you do somthing to get i810 happy dont think it will help you with a different driver. The kernel module for acceleration is related but different and necessary for DRI. 3) I have a theory that Graffix/video chips PCI device numbers kind of walk thru themselves pci device 0:2:0 and 0:2:1 are the same device where as 0:1:0 and 0:2:0 are different. Some further explanation would be helpful here. 4) I have no Idea what VESA or frame buffer stuff is other than old and do not know if I need it. 5) I do not know what it the best in make.conf | Code: | | VIDEO_CARDS="i810 i830 i915" |
or
| Code: | | VIDEO_CARDS="intel i810" |
among other things.
DRM works produces nice spinning gears.
My probelm now is that I cannot get a "mode line" for my LVDS monitor when the flat screen is pluged in.
Both are detected and running but I can only see one.
The LVDS is the laptops monitor and the VGA is the VGA out.
| Code: | xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2048 x 1024
VGA connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 75.1 70.1 60.0*
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
LVDS connected (normal left inverted right)
822x229 1319.1 +
|
I do get a few errors still:
| Code: |
grep '(EE) ' Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) intel(0): detecting sil164
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
(EE) intel(0): Unable to read from DVOI2C_E Slave 236.
(EE) intel(0): ivch: Unable to read register 0x00 from DVOI2C_B:04.
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
(EE) intel(0): tfp410 not detected got VID FFFFFFFF: from DVOI2C_E Slave 112.
grep '(WW) ' Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
(WW) intel(0): Failed to allocate texture space.
(WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
(WW) intel(0): Option "MetaModes" is not used
(WW) intel(0): Option "FixedPipe" is not used
(WW) intel(0): Option "MonitorLayout" is not used
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
|
AIGLX: 3D driver errors are discussed here
EDIT:
xdm.log also gives me (EE) intel(0): I830 Vblank Pipe Setup Failed 0
I wonder why it refers to I830 when I have: | Code: | <*> Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver) --->( ) i830 driver │ │
│ │ (X) i915 driver |
compiled into my kernel (not modular).
I also have <*> Intel 440LX/BX/GX, I8xx and E7x05 chipset support
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
Enabled in the Kernel
So any ideas would be great.
_________________
Donate to Gentoo |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
