X -configure -- Segmentation fault at address 0x28

2013-05-10 Thread Stefan Olsson 
Hello,

When I use startx things works quite well with X-windows, but since I want
a multihead config I tried to run X -configure. That configuration doesn't
get very far though, it lists the available graphics drivers and then
chokes and gives Segmentation fault at address 0x28. -The config that is
created is very basic but I note that it has entries for both intel and
vesa. -What can I do to get a more useful xorg.conf? Prevent the
segmentation fault?

xorg.conf.new:
Section ServerLayout
Identifier X.org Configured
Screen  0  Screen0 0 0
Screen  1  Screen1 RightOf Screen0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
EndSection

Section Files
ModulePath   /usr/X11R6/lib/modules
FontPath /usr/X11R6/lib/X11/fonts/misc/
FontPath /usr/X11R6/lib/X11/fonts/TTF/
FontPath /usr/X11R6/lib/X11/fonts/OTF/
FontPath /usr/X11R6/lib/X11/fonts/Type1/
FontPath /usr/X11R6/lib/X11/fonts/100dpi/
FontPath /usr/X11R6/lib/X11/fonts/75dpi/
EndSection

Section Module
Load  dbe
Load  dri
Load  dri2
Load  extmod
Load  glx
Load  record
EndSection

Section InputDevice
Identifier  Keyboard0
Driver  kbd
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
OptionProtocol wsmouse
OptionDevice /dev/wsmouse
OptionZAxisMapping 4 5 6 7
EndSection

Section Monitor
Identifier   Monitor0
VendorName   Monitor Vendor
ModelNameMonitor Model
EndSection

Section Monitor
Identifier   Monitor1
VendorName   Monitor Vendor
ModelNameMonitor 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 NoAccel # [bool]
#Option AccelMethod # str
#Option Backlight   # str
#Option DRI # str
#Option ColorKey   # i
#Option VideoKey   # i
#Option Tiling # [bool]
#Option LinearFramebuffer   # [bool]
#Option SwapbuffersWait # [bool]
#Option TripleBuffer   # [bool]
#Option XvPreferOverlay # [bool]
#Option HotPlug # [bool]
#Option RelaxedFencing # [bool]
#Option XvMC   # [bool]
#Option FallbackDebug   # [bool]
#Option DebugFlushBatches   # [bool]
#Option DebugFlushCaches   # [bool]
#Option DebugWait   # [bool]
#Option BufferCache # [bool]
Identifier  Card0
Driver  intel
BusID   PCI:0:2:0
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 ShadowFB   # [bool]
#Option DefaultRefresh # [bool]
#Option ModeSetClearScreen # [bool]
Identifier  Card1
Driver  vesa
BusID   PCI:0:2:0
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
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

Section Screen
Identifier Screen1
Device Card1
MonitorMonitor1
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

--
dmesg
OpenBSD 5.3-current (GENERIC.MP) #108: Tue Apr 30 11:35:41 MDT 2013
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error
3fconfig_unit,memory_size,fixed_disk,invalid_time
real mem = 8448847872 (8057MB)
avail mem = 8216231936 (7835MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf2210 (102 entries)
bios0: vendor Dell Inc. version A09 date 09/12/2012
bios0: Dell Inc. Latitude XT3
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC TCPA SSDT MCFG HPET BOOT SSDT SSDT SLIC
acpi0: wakeup devices UAR1(S3) HDEF(S4) GLAN(S4) PXSX(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4)
RP07(S4) PXSX(S4) RP08(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEG2(S4) PEG3(S4)
PXSX(S4) RP03(S4) EHC2(S1) EHCI(S1) LID_(S3) PBTN(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT

Re: X -configure -- Segmentation fault at address 0x28

2013-05-10 Thread Zé Loff 
On May 10, 2013, at 9:56 AM, Stefan Olsson stefan.karl.ols...@gmail.com wrote:

 Hello,
 
 When I use startx things works quite well with X-windows, but since I want
 a multihead config I tried to run X -configure. That configuration doesn't
 get very far though, it lists the available graphics drivers and then
 chokes and gives Segmentation fault at address 0x28. -The config that is
 created is very basic but I note that it has entries for both intel and
 vesa. -What can I do to get a more useful xorg.conf? Prevent the
 segmentation fault?


Since you have an intel gpu, and if all you need is simple multihead
(i.e. multiple monitors on one gpu), I'd advise you to forget xorg.conf
and take a look at xrandr. Search the archives, there was a thread on
this, recently.

Re: X -configure -- Segmentation fault at address 0x28

2013-05-10 Thread Janne Johansson 
2013/5/10 Stefan Olsson stefan.karl.ols...@gmail.com

 When I use startx things works quite well with X-windows, but since I want


Long time since I saw one of these knee-jerk reactions:

The X.Org Foundation requests that the following names be used when
referring to this software:

   X
   X Window System
   X Version 11
   X Window System, Version 11
   X11

=)

xrandr crtc [was: X -configure -- Segmentation fault at address 0x28]

2013-05-10 Thread Stefan Olsson 
On 10 May 2013 10:41, Zé Loff zel...@zeloff.org wrote:

 xrandr


-That was good advice to try xrandr instead, however, now I have a problem
with crtc's - I have two crtc, 0 and 1. But I have three monitors - LVDS1,
VGA1 and HDMI1. It seems like I just can not get it to work on all three
monitor at once. My guess is that I would need more crtc's, but is that
even possible?
VGA1 and HDMI1 are identical monitors able for 1680x1050 and should thus be
able to share a crtc, but even if I specify that they both should have crtc
1 and then configure LVDS1 to have crtc 0 I get xrandr: cannot find crtc
for output LVDS1

-Am I fighting a hopless battle? Is it only possible to get to monitors
working at the same time with this graphics card?

Kind Regards

Re: xrandr crtc [was: X -configure -- Segmentation fault at address 0x28]

2013-05-10 Thread Jonathan Gray 
On Fri, May 10, 2013 at 12:46:00PM +0100, Stefan Olsson wrote:
 On 10 May 2013 10:41, Z?? Loff zel...@zeloff.org wrote:
 
  xrandr
 
 
 -That was good advice to try xrandr instead, however, now I have a problem
 with crtc's - I have two crtc, 0 and 1. But I have three monitors - LVDS1,
 VGA1 and HDMI1. It seems like I just can not get it to work on all three
 monitor at once. My guess is that I would need more crtc's, but is that
 even possible?
 VGA1 and HDMI1 are identical monitors able for 1680x1050 and should thus be
 able to share a crtc, but even if I specify that they both should have crtc
 1 and then configure LVDS1 to have crtc 0 I get xrandr: cannot find crtc
 for output LVDS1
 
 -Am I fighting a hopless battle? Is it only possible to get to monitors
 working at the same time with this graphics card?

You can only have two active pipes/outputs on sandy bridge. With
ivy bridge it should be possible to have three active pipes
if two of them share the same resolution/modelines.  There seem
to be some reports of X not quite liking the three pipe setup
with shared clocks though, so it isn't clear if this currently works,
but it won't on your sandy bridge machine as the hardware can't do it.