Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On Wed, Feb 12, 2014 at 02:37:30AM -0500, RD Thrush wrote: On 02/11/14 19:45, Jonathan Gray wrote: On Mon, Feb 10, 2014 at 01:20:46PM -0500, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Haswell graphics should work since a few months now. It does work; however, only @ vesa 1024x768 resolution. That same hardware yields 1920x1200 w/ win7. Is 1024x768 the upper limit for -current w/ vga and this graphics hardware? 1024x768 is the mode chosen if the monitor does not send a mode when probed. If you want to make all of this a lot easier to debug remove the radeon card. X segfaulting at a low address normally means the framebuffer could not be mmap'd due to the /dev/drm* permissions not being set correctly. Here's what I have: a8v2:home/rd 2181ls -l /dev/drm* crw--- 1 root wheel 87, 0 Jan 24 02:58 /dev/drm0 crw--- 1 root wheel 87, 1 Jan 24 02:58 /dev/drm1 crw--- 1 root wheel 87, 2 Jan 24 02:58 /dev/drm2 crw--- 1 root wheel 87, 3 Jan 24 02:58 /dev/drm3 I didn't expect those perms to matter w/ Xorg -configure -keepPriv. In any case, I added /dev/drm[123] to /etc/fbtab as you suggested in the other post but observed the same segfault. Xorg -configure is known to be broken for quite a while http://lists.freedesktop.org/pipermail/xorg/2013-June/055813.html avoid it.
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 02/12/14 03:01, Jonathan Gray wrote: On Wed, Feb 12, 2014 at 02:37:30AM -0500, RD Thrush wrote: On 02/11/14 19:45, Jonathan Gray wrote: On Mon, Feb 10, 2014 at 01:20:46PM -0500, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Haswell graphics should work since a few months now. It does work; however, only @ vesa 1024x768 resolution. That same hardware yields 1920x1200 w/ win7. Is 1024x768 the upper limit for -current w/ vga and this graphics hardware? 1024x768 is the mode chosen if the monitor does not send a mode when probed. If you want to make all of this a lot easier to debug remove the radeon card. This i7 only has onboard graphics. The other i7 has both graphics hardware. I only brought it up to corroborate the resolution and segfault problems seen in the initial report. X segfaulting at a low address normally means the framebuffer could not be mmap'd due to the /dev/drm* permissions not being set correctly. Here's what I have: a8v2:home/rd 2181ls -l /dev/drm* crw--- 1 root wheel 87, 0 Jan 24 02:58 /dev/drm0 crw--- 1 root wheel 87, 1 Jan 24 02:58 /dev/drm1 crw--- 1 root wheel 87, 2 Jan 24 02:58 /dev/drm2 crw--- 1 root wheel 87, 3 Jan 24 02:58 /dev/drm3 I didn't expect those perms to matter w/ Xorg -configure -keepPriv. In any case, I added /dev/drm[123] to /etc/fbtab as you suggested in the other post but observed the same segfault. Xorg -configure is known to be broken for quite a while http://lists.freedesktop.org/pipermail/xorg/2013-June/055813.html avoid it. Amending the faq[1] might help avoid this unproductive path... [1]http://www.openbsd.org/faq/faq11.html#amd64i386example
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 02/11/14 19:53, Jonathan Gray wrote: On Tue, Feb 11, 2014 at 10:32:25AM -0500, RD Thrush wrote: On 02/10/14 13:20, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Ken Thanks for the feedback. Apparently, Intel HD Graphics 4000 is similarly not yet supported... Ivy bridge works fine, what you didn't point out is that you have both radeondrm and inteldrm in that machine. Setups with multiple cards may have been broken by the fbtab changes Try adjust your /etc/fbtab along these lines and restart your xorg server. --- fbtab.prevWed Feb 12 11:46:14 2014 +++ fbtab Wed Feb 12 11:47:15 2014 @@ -2,6 +2,6 @@ # login(1) reads this file to determine which devices should be chown'd to # the new user. Format is: # login-tty permdevice:[device]:... -/dev/ttyC0 0600 /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0 +/dev/ttyC0 0600 /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0:/dev/drm1:/dev/drm2:/dev/drm3 # samples #/dev/ttyC0 0600/dev/fd0 I will make that change in the next few days and report back. Further info: Both the onboard vga and the radeon display port interface are connected to the same monitor (Dell U2412M). The machine is usually running win8 w/ the monitor in display port mode. When running OpenBSD, I have the monitor in vga mode.
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 02/12/14 02:53, Philip Guenther wrote: On Tue, Feb 11, 2014 at 11:37 PM, RD Thrush openbsd-m...@thrush.com wrote: ... I didn't expect those perms to matter w/ Xorg -configure -keepPriv. With the perms on /dev/drm[0-3] set so that you own them, what happens when you don't use the -configure and -keepPriv options? Thanks. I see the root screen. Cursor tracks mouse. ctl-alt-backspace transitions cleanly to text mode. I've appended the typescript, associated Xorg.0.log and dmesg. (You don't say why you use -configure, so I'll just quote Matthieu I was expecting better than 1024x768 resolution and the X11 section of the faq http://www.openbsd.org/faq/faq11.html#amd64i386example suggested Xorg -configure. Herb from July 2012(!): Also forget about X -configure. It's known to be more or less broken and nowadays you don't need an xorg.conf file to run X in most cases. ) I'll stop using X -configure. Other recommendations for getting better resolution? ### typescript ### Script started on Wed Feb 12 07:06:58 2014 a8v2:home/rd 384export DISPLAY= a8v2:home/rd 385Xorg X.Org X Server 1.14.5 Release Date: 2013-12-12 X Protocol Version 11, Revision 0 Build Operating System: OpenBSD 5.5 amd64 Current Operating System: OpenBSD a8v2.thrush.com 5.5 GENERIC.MP#287 amd64 Build Date: 10 February 2014 11:19:30AM Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Feb 12 07:07:20 2014 (==) Using system config directory /usr/X11R6/share/X11/xorg.conf.d Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension XFree86-VidModeExtension Initializing built-in extension XFree86-DGA Initializing built-in extension XFree86-DRI Initializing built-in extension DRI2 Loading extension GLX (EE) Server terminated successfully (0). Closing log file. a8v2:home/rd 386exit Script done on Wed Feb 12 07:07:50 2014 # Xorg.0.log ### [250360.398] (--) checkDevMem: using aperture driver /dev/xf86 [250360.421] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [250361.450] X.Org X Server 1.14.5 Release Date: 2013-12-12 [250361.450] X Protocol Version 11, Revision 0 [250361.450] Build Operating System: OpenBSD 5.5 amd64 [250361.450] Current Operating System: OpenBSD a8v2.thrush.com 5.5 GENERIC.MP#287 amd64 [250361.451] Build Date: 10 February 2014 11:19:30AM [250361.451] [250361.451] Current version of pixman: 0.32.4 [250361.451]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [250361.451] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [250361.451] (==) Log file: /var/log/Xorg.0.log, Time: Wed Feb 12 07:07:20 2014 [250361.452] (==) Using system config directory /usr/X11R6/share/X11/xorg.conf.d [250361.452] (==) No Layout section. Using the first Screen section. [250361.452] (==) No screen section available. Using defaults. [250361.452] (**) |--Screen Default Screen Section (0) [250361.452] (**) | |--Monitor default monitor [250361.453] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [250361.453] (==) Disabling SIGIO handlers for input devices [250361.453] (==) Automatically adding devices [250361.453] (==) Automatically enabling devices [250361.453] (==) Not automatically adding GPU devices [250361.453] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/,
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 02/12/14 12:32, RD Thrush wrote: On 02/12/14 02:53, Philip Guenther wrote: On Tue, Feb 11, 2014 at 11:37 PM, RD Thrush openbsd-m...@thrush.com wrote: ... I didn't expect those perms to matter w/ Xorg -configure -keepPriv. With the perms on /dev/drm[0-3] set so that you own them, what happens when you don't use the -configure and -keepPriv options? Thanks. I see the root screen. Cursor tracks mouse. ctl-alt-backspace transitions cleanly to text mode. I've appended the typescript, associated Xorg.0.log and dmesg. (You don't say why you use -configure, so I'll just quote Matthieu I was expecting better than 1024x768 resolution and the X11 section of the faq http://www.openbsd.org/faq/faq11.html#amd64i386example suggested Xorg -configure. Herb from July 2012(!): Also forget about X -configure. It's known to be more or less broken and nowadays you don't need an xorg.conf file to run X in most cases. ) I'll stop using X -configure. Other recommendations for getting better resolution? xrandr(1) and mode lines from cvt(1) or gtf(1) might give you better resolution. cvt has solved resolution issues for me where gtf failed. hth Fred PS in theory you can just put the mode lines in xorg.conf - but I didn't have much luck trying that approach...
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 02/10/14 13:20, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Ken Thanks for the feedback. Apparently, Intel HD Graphics 4000 is similarly not yet supported... An older (~Nov 2012) i7 system has similar behavior, ie. vesa @1024x768 and segfault w/ Xorg -configure. I have appended dmesg, Xorg.0.log for segfault as well as for vesa startx. dmesg # OpenBSD 5.5-beta (GENERIC.MP) #287: Fri Feb 7 11:45:09 MST 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17051402240 (16261MB) avail mem = 16589279232 (15820MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeba40 (112 entries) bios0: vendor American Megatrends Inc. version 1204 date 11/26/2013 bios0: ASUSTeK COMPUTER INC. P8Q77-M acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT ASF! SSDT SSDT DMAR acpi0: wakeup devices PS2K(S4) PS2M(S4) UAR1(S4) P0P1(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3400.43 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3400.02 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3400.02 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3400.02 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3400.02 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3400.02 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 1, core 1, package 0 cpu6 at mainbus0: apid 5 (application processor)
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On Mon, Feb 10, 2014 at 01:20:46PM -0500, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Ken 4400 works fine for me. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On Mon, Feb 10, 2014 at 01:20:46PM -0500, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Haswell graphics should work since a few months now. X segfaulting at a low address normally means the framebuffer could not be mmap'd due to the /dev/drm* permissions not being set correctly.
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On Tue, Feb 11, 2014 at 10:32:25AM -0500, RD Thrush wrote: On 02/10/14 13:20, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Ken Thanks for the feedback. Apparently, Intel HD Graphics 4000 is similarly not yet supported... Ivy bridge works fine, what you didn't point out is that you have both radeondrm and inteldrm in that machine. Setups with multiple cards may have been broken by the fbtab changes Try adjust your /etc/fbtab along these lines and restart your xorg server. --- fbtab.prev Wed Feb 12 11:46:14 2014 +++ fbtab Wed Feb 12 11:47:15 2014 @@ -2,6 +2,6 @@ # login(1) reads this file to determine which devices should be chown'd to # the new user. Format is: # login-ttypermdevice:[device]:... -/dev/ttyC0 0600 /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0 +/dev/ttyC0 0600 /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0:/dev/drm1:/dev/drm2:/dev/drm3 # samples #/dev/ttyC00600/dev/fd0
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 02/11/14 19:45, Jonathan Gray wrote: On Mon, Feb 10, 2014 at 01:20:46PM -0500, Kenneth Westerback wrote: On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Haswell graphics should work since a few months now. It does work; however, only @ vesa 1024x768 resolution. That same hardware yields 1920x1200 w/ win7. Is 1024x768 the upper limit for -current w/ vga and this graphics hardware? X segfaulting at a low address normally means the framebuffer could not be mmap'd due to the /dev/drm* permissions not being set correctly. Here's what I have: a8v2:home/rd 2181ls -l /dev/drm* crw--- 1 root wheel 87, 0 Jan 24 02:58 /dev/drm0 crw--- 1 root wheel 87, 1 Jan 24 02:58 /dev/drm1 crw--- 1 root wheel 87, 2 Jan 24 02:58 /dev/drm2 crw--- 1 root wheel 87, 3 Jan 24 02:58 /dev/drm3 I didn't expect those perms to matter w/ Xorg -configure -keepPriv. In any case, I added /dev/drm[123] to /etc/fbtab as you suggested in the other post but observed the same segfault. I had compiled xenocara w/ debug and included the gdb backtrace in the original message[1]. How may I provide more info about this segfault? [1]http://marc.info/?l=openbsd-miscm=139205596505418w=2
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On Tue, Feb 11, 2014 at 11:37 PM, RD Thrush openbsd-m...@thrush.com wrote: ... I didn't expect those perms to matter w/ Xorg -configure -keepPriv. With the perms on /dev/drm[0-3] set so that you own them, what happens when you don't use the -configure and -keepPriv options? (You don't say why you use -configure, so I'll just quote Matthieu Herb from July 2012(!): Also forget about X -configure. It's known to be more or less broken and nowadays you don't need an xorg.conf file to run X in most cases. ) Philip Guenther
Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. After the segfault, I built xenocara w/ DEBUG=-g with -current xenocara src to gather more debug info. I've appended the gdb backtrace from the segfault, dmesg, Xorg.0.log from startx as well as Xorg.0.log from the segfault. ## gdb bt ## a8v2:home/rd 402sudo gdb $(which Xorg) /var/crash/Xorg.core GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-unknown-openbsd5.5... Core was generated by `Xorg'. Program terminated with signal 6, Aborted. Reading symbols from /usr/lib/libpthread.so.18.0...done. Loaded symbols for /usr/lib/libpthread.so.18.0 Loaded symbols for /usr/X11R6/bin/X Symbols already loaded for /usr/lib/libpthread.so.18.0 Reading symbols from /usr/X11R6/lib/libpciaccess.so.2.0...done. Loaded symbols for /usr/X11R6/lib/libpciaccess.so.2.0 Reading symbols from /usr/X11R6/lib/libdrm.so.4.1...done. Loaded symbols for /usr/X11R6/lib/libdrm.so.4.1 Reading symbols from /usr/X11R6/lib/libpixman-1.so.32.4...done. Loaded symbols for /usr/X11R6/lib/libpixman-1.so.32.4 Reading symbols from /usr/X11R6/lib/libpthread-stubs.so.2.0...done. Loaded symbols for /usr/X11R6/lib/libpthread-stubs.so.2.0 Reading symbols from /usr/X11R6/lib/libXfont.so.11.0...done. Loaded symbols for /usr/X11R6/lib/libXfont.so.11.0 Reading symbols from /usr/X11R6/lib/libfreetype.so.22.0...done. Loaded symbols for /usr/X11R6/lib/libfreetype.so.22.0 Reading symbols from /usr/X11R6/lib/libfontenc.so.4.0...done. Loaded symbols for /usr/X11R6/lib/libfontenc.so.4.0 Reading symbols from /usr/lib/libz.so.5.0...done. Loaded symbols for /usr/lib/libz.so.5.0 Reading symbols from /usr/X11R6/lib/libXau.so.10.0...done. Loaded symbols for /usr/X11R6/lib/libXau.so.10.0 Reading symbols from /usr/X11R6/lib/libXdmcp.so.11.0...done. Loaded symbols for /usr/X11R6/lib/libXdmcp.so.11.0 Reading symbols from /usr/lib/libkvm.so.16.0...done. Loaded symbols for /usr/lib/libkvm.so.16.0 Reading symbols from /usr/lib/libm.so.9.0...done. Loaded symbols for /usr/lib/libm.so.9.0 Reading symbols from /usr/lib/libc.so.73.1...done. Loaded symbols for /usr/lib/libc.so.73.1 Reading symbols from /usr/libexec/ld.so...done. Loaded symbols for /usr/libexec/ld.so Reading symbols from /usr/X11R6/lib/modules/drivers/apm_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/apm_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/ark_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/ark_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/ati_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/ati_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/chips_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/chips_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/cirrus_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/cirrus_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/dummy_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/dummy_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/glint_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/glint_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/i128_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/i128_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/intel_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/intel_drv.so Reading symbols from /usr/X11R6/lib/libX11.so.16.0...done. Loaded symbols for /usr/X11R6/lib/libX11.so.16.0 Reading symbols from /usr/X11R6/lib/libxcb.so.3.0...done. Loaded symbols for /usr/X11R6/lib/libxcb.so.3.0 Reading symbols from /usr/X11R6/lib/libdrm_intel.so.3.1...done. Loaded symbols for /usr/X11R6/lib/libdrm_intel.so.3.1 Reading symbols from /usr/X11R6/lib/modules/drivers/mach64_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/mach64_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/mga_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/mga_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/neomagic_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/neomagic_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/nv_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/drivers/nv_drv.so Reading symbols from /usr/X11R6/lib/modules/drivers/openchrome_drv.so...done.
Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600
On 10 February 2014 13:11, RD Thrush openbsd-m...@thrush.com wrote: With a somewhat recent i7 desktop, using startx, X seems to run ok; however, at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or - have no effect on resolution. ctl-alt-backspace correctly reverts to text mode. I then tried Xorg -configure to look for hints to improve resolution; however, that resulted in a segfault almost immediately. I'm pretty sure vga1 at pci0 dev 2 function 0 Intel HD Graphics 4600 rev 0x06 is not supported in the sense of working as opposed to being recognized. i.e. 1024x768 is likely as good as it gets until support is added. Even 4400 is problematic at the moment. But I'm willing to be corrected by people more in the know. :-) Ken
