SNA / 3270 support

Hi Folks,
Does anyone know of a package that will run under 10.4.6 to support an SNA connection to a mainframe using 3270 terminal mode. I found one package but it runs under a combination of Clasic and 10.4
Any help would be appreciated.
Thanks.
PowerBook Mac OS X (10.4.6)

user618976 wrote:
Do we have any document/reference stating the Oracle Linux does not provide SNA protocol support?I have not see the converse - any documentation from Oracle that Oracle Linux (OL) does support SNA. There are no specific SNA download components for OL at Oracle's edelivery site, and not Metalink/Support note found on this subject matter when searching for "Linux" and "SNA protocol".
Oracle itself do (or did) support Gateway products using SNA. From the few support notes on the topic, it seems that these are pretty old and refer to deprecated s/w.
I would be surprised if OL supports SNA. Or even IPX for that matter. IPv4 and IPV6 are the definitive standards. For fabric layers, there are the various Infiniband protocols (SRP, RDMA, RDS, etc). It's hard to see SNA or something like IPX featuring in this.
Best would be to ask this question to Oracle sales/marketing directly. Neither Dude or I work for Oracle and we've only conveyed our opinions in this regard.

Similar Messages

Oracle Linux-SNA Protocol support

Hello,
We have developed the product with client server architecture with client and server has capability to talk with each other
using either TCP/IP or IBM SNA protocol. Our application is an 32 bit application.
We now need to check whether the Oracle Linux has capability to support SNA protocol.
Can you please let us know whether the following the Oracle linux versions (*Oracle 5 64-bit, Oracle 5 32-bit, Oracle 6 64-bit, Oracle 6 32-bit*) has capability to support SNA protocol?
Thanks in advance.
Regards,
Dayakar
Edited by: user618976 on Nov 14, 2011 1:37 AM

user618976 wrote:
Do we have any document/reference stating the Oracle Linux does not provide SNA protocol support?I have not see the converse - any documentation from Oracle that Oracle Linux (OL) does support SNA. There are no specific SNA download components for OL at Oracle's edelivery site, and not Metalink/Support note found on this subject matter when searching for "Linux" and "SNA protocol".
Oracle itself do (or did) support Gateway products using SNA. From the few support notes on the topic, it seems that these are pretty old and refer to deprecated s/w.
I would be surprised if OL supports SNA. Or even IPX for that matter. IPv4 and IPV6 are the definitive standards. For fabric layers, there are the various Infiniband protocols (SRP, RDMA, RDS, etc). It's hard to see SNA or something like IPX featuring in this.
Best would be to ask this question to Oracle sales/marketing directly. Neither Dude or I work for Oracle and we've only conveyed our opinions in this regard.

What Options I can implement for comunication PC ( lan ethernet) with SNA S

What Options I can implement for comunication PC ( lan ethernet) with SNA Server (Lan Token Ring) :
To see file
thanks you,
jj González

What version of SNA server are you using?
SNA server version 3 and higher support tn3270/tn3270e (for mainframe connectivity) and tn5250 (for as/400 connectivity) clients. The ms windoes telnet client does not support those protocols so you need a 3270 and/or 5250 emulator from another vendor, such as NetManage or Hummingbird.
This assumes that you have a routed network between your workstation and the sna server.
If your network is bridged, then you need to use an emulator that works with the native sna protocol, as the sna server supports that as well. The NetManage and Hummingbird emulators will work in this case too.
Try to use the tn3270/tn5250 as the first choice as it does not require a bridged backbone. SNA is not a routeable protcol by default.
Let me know if this helps.

Why the name Reverse Telnet ?

Forgive me for this simple ( and to some, stupid) question. Why is reaching the console ports of devices attached to a terminal server called Reverse Telnet. I am confused about the "Reverse" part.
1. You reach "terminal server" by some suiteable means (telnet, ssh, console) from a device say your computer.
    c:\> telnet 10.10.10.1
    termsrv >
2. You effectivily telnet to localhost (terminal server) on a specific port bound to certain TTY connection
    termsrv > R1                                  ! ip host R1 2001 <<loopback_address_termsrv>>
    R1>
Whats different for this second telnet is, instead of the telnet server (running on terminal server) presenting you with a second command shell it connects the mapped console port to the new telnet session. Effectively you read from or write to console port of R1.
R1 is oblivious about this whole operation. What's so "Reverse" about this second telnet session ?
Thanks.

Ah, this is a good question. Step into my time machine, and travel with me back to late eighties. The 3Com 3C501 PC Ethernet card was released at the bargain basement price of $999 USD and the mighty Interl 386-DX33 was released to great fanfare. Windows ran on top of DOS and all PC IP networking stacks were 3rd-party bolt-ons. When you communicated with a computer, whether DEC, IBM or whomever you did it with a DUMB TERMINAL. A terminal, for thos eof you who have never sern one, was either a keyboard and a printer combo (like a Decwriter 100) or a CRT text screen (Like a VT220, 80 columns by 24 lines) and a keyboard. What you typed went out the serial port to a computer, and the computer sent text and screen drawing back commands through that same serial port. That was the common human-computer interface of that era.
In the bad old days, the terminals were connected directly to the computers by serial interface cards and RS-232 cable. As computers got faster, more and more terminals could be supported. This started to get ridiculous as many serial lines emerged from these computers. The bigger computers looked like a mutant octopus.
Enter the TERMINAL SERVER, one of Cisco's early products. (The ASM)
The Cisco ASM terminal server took up to 96 terminals in an area and provided serial port connections for them. It then multiplexed those terminals over Ethernet in order to reach an Ethernet connected computer (host). The host computers were now freed from the sea of serial cables and could service dozens to hundreds of terminals thorough a single Ethernet port!   As a result, dozens to hundreds of slow, lightly used 9600 bps serial cables were replaced by a single 10 Mbit/sec connection.
The Cisco ASM software provided a telnet client to each serial port so that each terminal could connect to any telnet server (host) on the any network. This allowed users to connect to multiple computers and relieved the load of computers providing telnet client services to directly attached terminals. In this model, connections were initiated from a terminal on the port of the Cisco ASM to some distant computer.
Over time, Cisco noticed that there were computers and other devices (like the IBM 7171) that could not support Ethernet conenctions, but had dozens upon dozens of physical serial ports. To make it so that network based telnet clients all over the Internet could access such an Ethernet-free computer, Cisco implemented a telnet SERVER function in the ASM. Connections from a distant telnet client could now conenct through the ASM telnet server and reach these serial ports which had previously been limited to local terminals or expensive modem connections. Since this activity was the exact reverse of the original use of the ASM, the function became known as "Reverse telnet."
In summary: When a serially attached device CONSUMES service FROM the network, that is TELNET. (The original design!)
When a serially attached device PROVIDES services TO the network, that is REVERSE TELNET. (The opposite of the original design. But useful!)
Now, I will wait for people who have been in the industry longer than I have to go on about SNA, 3270s, paper tape and punch cards.

Mainframe character mode

Is it possible to develop a portlet that could display character
mode screen information from a mainframe? The application is
CICS based running an SNA 3270.
Thanks,
Suzanne

Suzanne,
I don't know much about mainframe character mode data, but you can approach this problem a few ways:
1) Is there any way to write a java program that can access this data? If so, then you can use PDK-Java to easily turn your java component into a portlet.
2) Is there any way to write a program in ANY language that can access this data and render it as HTML content? If so, then you can use PDK-URL services to render this data as a portlet.
James

IOS support for MPLS QoS as stated in RFC 3270 L-LSP

Hi,
does anybody know something about the degree of implementation of RFC 3270 (Multi-Protocol Label Switching (MPLS) Support of Differentiated Services), particularly on the classification based on Labels (L-LSP)?
From what is detailed on the CCO it seems that only Exp-bits based LSP are supported (configuring all links along the path for the proper data plane behaviour based on the Exp-bits values): E-LSP
Thanx in advance
Francesco

I guess, in PPP and LAN environments, E-LSP is the preferred method and in the ATM only L-LSP is possible. Maybe cisco chose to implement only the E-LSP for the LAN and PPP environments, i am not sure though.
Anyone knows this for sure?
Check out http://www.cisco.com/warp/public/732/Tech/mpls/docs/mpls_qos_jayk.ppt for more details on MPLS-QoS

Does Catalyst 2950 support SNA traffic ?

hello
we are trying to integrate some legacy sna hosts
to switching enviromnent.
we are faced to a strange symptom when legacy hosts
are connected to 2950 switch no traffic sna pass thru
we checked vlan,ports ,STP, but didnt found any hints
removing 2950 from configuration clear out the problem.
so simple diagram
7206 ==wan===7206=ethernet HUB=legacy sna host OK
----DLSW----> -------SNA------>
7206==wab===7206==CAT2950===legacy sna host NO OK
-----DLSW----> ---------SNA----->
are they any issue on 2950 for SNA traffic .
thanks in advance
JYP

Hi,
in general, No. There are no general issues with sna and a cat2950. The switch doesnt care what type of traffic runs through.
Besides the obviouos, the client and the dlsw router
must be in the same vlan.
There are sometimes problems with a switched environment. I.e if you do trunking with dot1q between the switch and the dlsw router and you use the switch in a mode where it tries to autonegotiate the trunk. Dlsw forwards some of the negotiation packets which leaves the switch in a state where the connections dont work.
We have also seen a problem in some situations where a dot1q trunk is used when the switch is configured for PVSTP, per vlan stp. In that case a special type of bpdu's is send which are also get forwarded by dlsw and can cause the switch on the other end to go to blocking ect.
All of those problems can be fixed by either putting a sap filter onto the bridge group on the dlsw router and only allow the sna saps you need or adopt the switch configuration. I.e. turn of autonegotiation of the trunk mode ect.
The issue needs to be looked at individualy and i would advice to open a case with the tac and work on this problem. So that we can understand what the problem is and fix it.
thanks....
Matthias

Does IP Plus support SNA DLSw

I'm not sure which IOS to run on a router. I need IPSec 3DES and DLSw. What IOS do I need for a 3745?
Also, what IOS do I need for a 1720, same requirements?
Thanks

For 3745, IP Plus (i.e. IP PLUS IPSEC 3DES to get DLSw and 3DES) supports DLSw. For 1720, you need IOS with IBM feature (i.e. IP/IPX/AT/IBM/FW PLUS IPSEC 3DES to get 3DES and DLSw) set to support DLSw.

Does my MacBook support HD output?

I am considering buying this monitor - http://accessories.us.dell.com/sna/products/Displays/productdetail.aspx?c=us&l=e n&s=dhs&cs=19&sku=320-7438
I have a MacBook 4,1 which has a mini DVI port for output?
As you may notice from the link, this monitor supports full HD content. My question - is my MacBook capable of HD output? If not, then what kind of compatibility (i.e. screen resolution and picture quality) can I expect between the monitor and my MacBook?
Also, what all connectors/converters would I need to buy to get things working? Which connection would give me a better resolution (DVI or VGA)?

It should work.
The maximum supported resolution is 1920x1200. It should be able to share information with the monitor and adjust the output resolution to match that of the monitor.
You could use the Apple Mini-DVI to DVI adapter, since the monitor seems to come with a DVI cable. You might also try a special mini-DVI to DVI cable like the following:
http://www.svideo.com/minidvi2dvi.html

SNA Server on Ethernet cannot talk to AS/400 on token ring

We have an SNA server on Ethernet and it cannot talk to a token ring device Q159462 from microsoft suggests to disable LLC local Acknowledgement.
Does anyone have any suggestions and how can I disable LLC?

You can do DLSw FST. I do not find an example of FST. The configuration guide for FST is as follows:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm_c/bcfpart2/bcfdlsw.htm#1002472
Basically, it has a very similar configuration as TCP encaupsulation. Just replace "TCP" by "FST" in the dlsw remote-peer statements.
Please note that FST does not offer segmentation/fragmentation. If the LLC2/DLC frames are larger than 1400+ bytes, the router just drops the packets. Make sure that the token ring stations do not send packets larger 1400+ bytes.
For your information, RIF passthrough is another useful option. Please note that RIF pass through DOES NOT support token ring to ethernet, as documented in the following URL:
http://www.cisco.com/warp/public/cc/pd/ibsw/ibdlsw/tech/dls24_rg.htm
One final comment. I have been supporting DLSw and Cisco routers for 4 years. I have worked with a lot of customers setting up MS SNA server and Cisco routers. I have never worked on a case which Cisco routers fail to forward SAMBE. I am working with the development group and find out if this is an IOS bug or not.

SNA and QOS

Subject: SNA/QOS
I AM CURRENTLY RUNNING 12.1(11a) IOS ON A ROUTER BASED NETWORK WITH FOUR
7500 ROUTERS. I AM CURRENTLY RUNNING CUSTOMER QUEUEING AS MY QOS. I AM
NOW LOOKING TO USING LLQ W/ CBWFQ AND DISTRIBUTED MODES, AS WELL. I HAVE
VIP-40 CARDS IN ALL ROUTER. HOWEVER, MY NETWORK IS COMPOSED OF --
TP0 - BATCH TRAFFIC
TP1- INTERACTIVE TRAFFIC
TP2-CONTROLLED TRAFFIC - HIGH AMOUNTS
I HAVE BEEN TOLD THAT CISCO'S QOS WILL SUPPORT TP1 TRAFFIC SO, I AM
CONCERNED ABOUT MY TP2 (CONTROLLED TRAFFIC) AND IF I CAN IMPLEMENT LLQ/CBWFQ
INTO MY NETWORK.
I WOULD LIKE TO IMPLEMENT THIS FOR MY CRITICAL APPS SUCH AS SNA, AND HTTP
WEB BASED APPS. THUS, LIMITING MY SQL, FTP AND TELNET TRAFFIC.
THANKS IN ADVANCE.
ANY PPT FILES WOULD BE APPRECIATED.

Hi Connie,
You open the door to an interesting discussion, by including both SNA and QoS in your question. As you know, a variety of QoS mechanisms have been available for SNA traffic for quite a while. I can't tell from your description what sort of traffic is contained in "TP2-CONTROLLED", so I will assume it is voice and video traffic, and not the "TP2" from OSI Transport Protocols.
The quick answer is that you can definitely support TP1 traffic while protecting the quality of your TP2 traffic. Essentially you decide what percentage of the available bandwidth to allocate to each class of traffic, providing a minimum guaranteed value. In addition, there is a special class, Low Latency Queuing (LLQ), available for delay and jitter sensitive traffic such as voice. Within each traffic class, IOS will then provide Weighted Fair Queuing (WFQ) for each unique flow (session). This becomes a bit more interesting when combined with different WAN types such as frame relay and ATM, you can take advantage of the VIPs that you mention, and there are considerations for low speed circuits. So here are a couple of URLs that provide more information.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/qos_c/qcprt2/qcdconmg.htm
http://www.cisco.com/univercd/cc/td/doc/product/voice/ip_tele/avvidqos/qoswan.htm
Coming back to the SNA traffic, I assume you're currently using custom queuing with DLSw+, using the priority parameter to create four TCP connections, and classifying traffic using one of the three available methods. In moving to a CBWFQ model, you will want to map the existing custom queues into the newly created classes. In other words, you can continue to use the same classification techniques, while changing to the easier to define, and more efficient WFQ for output queue processing.
The absolute best traffic classification comes with using the Enterprise Extender (EE) feature of SNASw. When SNA traffic is sent across an EE link, the precedence bits in the IP packets are automatically marked with the same values that are used in the SNA Class of Service (CoS). Since SNASw is our APPN node implementation, propagating the precedence markings from SNASw to DLSw+ also provides an automatic means of classifying the SNA traffic.
Rgds, Dan

Tuxedo 12c - Do mainframe adapters support two-phase commit?

With Oracle Tuxedo 12c, do the Tuxedo mainframe adapters support two-phase commit? I see there is support for two-phase commit with Tuxedo COBRA, for relational databases. My customer has a requirement to integrate with their mainframe systems and require two-phase commit (for rollback functionality) with the Tuxedo mainframe adapters.

Hi,
The Tuxedo Mainframe Adapter for SNA supports two phase commit protocol, or in IBM mainframe parlance syncpoint level 2.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Periodic X segfault (Intel graphics SNA bug)

After a recent update, I have been having some major issues with X periodically segfaulting. Unfortunately, the stack trace does not reveal much.
Complete Xorg log:
[ 4.300]
X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 4.300] X Protocol Version 11, Revision 0
[ 4.300] Build Operating System: Linux 3.15.5-2-ARCH x86_64
[ 4.300] Current Operating System: Linux mizuchi 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64
[ 4.300] Kernel command line: initrd=\initramfs-linux.img root=/dev/disk/by-uuid/62bb9e4b-3f83-4271-84e1-3aaf30aea69f rw ipv6.disable=1
[ 4.300] Build Date: 31 July 2014 11:53:19AM
[ 4.300]
[ 4.300] Current version of pixman: 0.32.6
[ 4.300] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4.300] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.300] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 28 19:51:42 2014
[ 4.303] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4.303] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4.305] (==) No Layout section. Using the first Screen section.
[ 4.305] (==) No screen section available. Using defaults.
[ 4.305] (**) |-->Screen "Default Screen Section" (0)
[ 4.305] (**) | |-->Monitor "<default monitor>"
[ 4.305] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 4.305] (==) Automatically adding devices
[ 4.305] (==) Automatically enabling devices
[ 4.305] (==) Automatically adding GPU devices
[ 4.310] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 4.310] Entry deleted from font path.
[ 4.310] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 4.311] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 4.311] Entry deleted from font path.
[ 4.311] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 4.311] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 4.311] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4.311] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4.311] (II) Loader magic: 0x818d80
[ 4.311] (II) Module ABI versions:
[ 4.311] X.Org ANSI C Emulation: 0.4
[ 4.311] X.Org Video Driver: 18.0
[ 4.311] X.Org XInput driver : 21.0
[ 4.311] X.Org Server Extension : 8.0
[ 4.311] (EE) systemd-logind: failed to get session: PID 343 does not belong to any known session
[ 4.311] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4.312] (--) PCI:*(0:0:2:0) 8086:0416:1028:05fe rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 4.312] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4.313] (II) LoadModule: "glx"
[ 4.313] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4.328] (II) Module glx: vendor="X.Org Foundation"
[ 4.328] compiled for 1.16.0, module version = 1.0.0
[ 4.328] ABI class: X.Org Server Extension, version 8.0
[ 4.328] (==) AIGLX enabled
[ 4.328] (==) Matched intel as autoconfigured driver 0
[ 4.328] (==) Matched intel as autoconfigured driver 1
[ 4.328] (==) Matched modesetting as autoconfigured driver 2
[ 4.328] (==) Matched fbdev as autoconfigured driver 3
[ 4.328] (==) Matched vesa as autoconfigured driver 4
[ 4.328] (==) Assigned the driver to the xf86ConfigLayout
[ 4.328] (II) LoadModule: "intel"
[ 4.329] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 4.331] (II) Module intel: vendor="X.Org Foundation"
[ 4.331] compiled for 1.16.0, module version = 2.99.914
[ 4.331] Module class: X.Org Video Driver
[ 4.331] ABI class: X.Org Video Driver, version 18.0
[ 4.331] (II) LoadModule: "modesetting"
[ 4.333] (WW) Warning, couldn't open module modesetting
[ 4.333] (II) UnloadModule: "modesetting"
[ 4.333] (II) Unloading modesetting
[ 4.333] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 4.333] (II) LoadModule: "fbdev"
[ 4.333] (WW) Warning, couldn't open module fbdev
[ 4.333] (II) UnloadModule: "fbdev"
[ 4.333] (II) Unloading fbdev
[ 4.333] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 4.333] (II) LoadModule: "vesa"
[ 4.333] (WW) Warning, couldn't open module vesa
[ 4.333] (II) UnloadModule: "vesa"
[ 4.333] (II) Unloading vesa
[ 4.333] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 4.333] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 4.334] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 4.334] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 4.334] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 4.334] (++) using VT number 1
[ 4.334] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730
[ 4.336] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
[ 4.336] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
[ 4.336] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 4.336] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 4.336] (==) intel(0): RGB weight 888
[ 4.336] (==) intel(0): Default visual is TrueColor
[ 4.336] (II) intel(0): Output eDP1 using monitor section <default monitor>
[ 4.336] (--) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[ 4.336] (II) intel(0): Output VGA1 has no monitor section
[ 4.336] (II) intel(0): Output HDMI1 has no monitor section
[ 4.336] (II) intel(0): Output DP1 has no monitor section
[ 4.336] (II) intel(0): Output HDMI2 has no monitor section
[ 4.336] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 4.336] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 4.336] (--) intel(0): Output eDP1 using initial mode 3200x1800 on pipe 0
[ 4.336] (==) intel(0): TearFree disabled
[ 4.336] (==) intel(0): DPI set to (96, 96)
[ 4.336] (II) Loading sub module "dri2"
[ 4.336] (II) LoadModule: "dri2"
[ 4.336] (II) Module "dri2" already built-in
[ 4.336] (II) Loading sub module "present"
[ 4.336] (II) LoadModule: "present"
[ 4.336] (II) Module "present" already built-in
[ 4.336] (==) Depth 24 pixmap format is 32 bpp
[ 4.340] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[ 4.340] (==) intel(0): Backing store enabled
[ 4.340] (==) intel(0): Silken mouse enabled
[ 4.341] (II) intel(0): HW Cursor enabled
[ 4.341] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 4.341] (==) intel(0): DPMS enabled
[ 4.341] (II) intel(0): [DRI2] Setup complete
[ 4.341] (II) intel(0): [DRI2] DRI driver: i965
[ 4.341] (II) intel(0): [DRI2] VDPAU driver: i965
[ 4.341] (II) intel(0): direct rendering: DRI2 enabled
[ 4.341] (II) intel(0): hardware support for Present enabled
[ 4.341] (==) intel(0): display hotplug detection enabled
[ 4.341] (--) RandR disabled
[ 4.374] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 4.374] (II) AIGLX: enabled GLX_ARB_create_context
[ 4.374] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 4.374] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 4.374] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 4.374] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 4.374] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 4.374] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 4.374] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 4.374] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 4.374] (II) AIGLX: Loaded and initialized i965
[ 4.374] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 4.379] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 4.400] (II) intel(0): Setting screen physical size to 345 x 194
[ 4.540] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 4.540] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4.540] (II) LoadModule: "evdev"
[ 4.541] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 4.542] (II) Module evdev: vendor="X.Org Foundation"
[ 4.542] compiled for 1.16.0, module version = 2.9.0
[ 4.542] Module class: X.Org XInput Driver
[ 4.542] ABI class: X.Org XInput driver, version 21.0
[ 4.542] (II) Using input driver 'evdev' for 'Power Button'
[ 4.542] (**) Power Button: always reports core events
[ 4.542] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 4.542] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 4.542] (--) evdev: Power Button: Found keys
[ 4.542] (II) evdev: Power Button: Configuring as keyboard
[ 4.542] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 4.542] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 4.542] (**) Option "xkb_rules" "evdev"
[ 4.542] (**) Option "xkb_model" "pc104"
[ 4.543] (**) Option "xkb_layout" "us"
[ 4.556] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 4.556] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 4.556] (II) Using input driver 'evdev' for 'Video Bus'
[ 4.556] (**) Video Bus: always reports core events
[ 4.556] (**) evdev: Video Bus: Device: "/dev/input/event4"
[ 4.556] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 4.556] (--) evdev: Video Bus: Found keys
[ 4.556] (II) evdev: Video Bus: Configuring as keyboard
[ 4.556] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input4/event4"
[ 4.556] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 4.556] (**) Option "xkb_rules" "evdev"
[ 4.556] (**) Option "xkb_model" "pc104"
[ 4.556] (**) Option "xkb_layout" "us"
[ 4.556] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[ 4.556] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 4.556] (II) Using input driver 'evdev' for 'Video Bus'
[ 4.556] (**) Video Bus: always reports core events
[ 4.556] (**) evdev: Video Bus: Device: "/dev/input/event3"
[ 4.556] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 4.556] (--) evdev: Video Bus: Found keys
[ 4.556] (II) evdev: Video Bus: Configuring as keyboard
[ 4.556] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4d/LNXVIDEO:00/input/input3/event3"
[ 4.557] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 4.557] (**) Option "xkb_rules" "evdev"
[ 4.557] (**) Option "xkb_model" "pc104"
[ 4.557] (**) Option "xkb_layout" "us"
[ 4.557] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 4.557] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4.557] (II) Using input driver 'evdev' for 'Power Button'
[ 4.557] (**) Power Button: always reports core events
[ 4.557] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 4.557] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 4.557] (--) evdev: Power Button: Found keys
[ 4.557] (II) evdev: Power Button: Configuring as keyboard
[ 4.557] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[ 4.557] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
[ 4.557] (**) Option "xkb_rules" "evdev"
[ 4.557] (**) Option "xkb_model" "pc104"
[ 4.557] (**) Option "xkb_layout" "us"
[ 4.557] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 4.557] (II) No input driver specified, ignoring this device.
[ 4.557] (II) This device may have been added with another device file.
[ 4.557] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event7)
[ 4.557] (II) No input driver specified, ignoring this device.
[ 4.557] (II) This device may have been added with another device file.
[ 4.557] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event8)
[ 4.557] (II) No input driver specified, ignoring this device.
[ 4.557] (II) This device may have been added with another device file.
[ 4.558] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event9)
[ 4.558] (II) No input driver specified, ignoring this device.
[ 4.558] (II) This device may have been added with another device file.
[ 4.558] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[ 4.558] (II) No input driver specified, ignoring this device.
[ 4.558] (II) This device may have been added with another device file.
[ 4.558] (II) config/udev: Adding input device HDA Intel PCH Headphone Mic (/dev/input/event11)
[ 4.558] (II) No input driver specified, ignoring this device.
[ 4.558] (II) This device may have been added with another device file.
[ 4.558] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event5)
[ 4.558] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 4.558] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 4.558] (**) AT Translated Set 2 keyboard: always reports core events
[ 4.558] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event5"
[ 4.558] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 4.558] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 4.558] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 4.558] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input5/event5"
[ 4.558] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[ 4.558] (**) Option "xkb_rules" "evdev"
[ 4.558] (**) Option "xkb_model" "pc104"
[ 4.558] (**) Option "xkb_layout" "us"
[ 4.558] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event6)
[ 4.558] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 4.558] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[ 4.558] (**) Dell WMI hotkeys: always reports core events
[ 4.558] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event6"
[ 4.558] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[ 4.558] (--) evdev: Dell WMI hotkeys: Found keys
[ 4.558] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[ 4.558] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event6"
[ 4.558] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 11)
[ 4.558] (**) Option "xkb_rules" "evdev"
[ 4.558] (**) Option "xkb_model" "pc104"
[ 4.558] (**) Option "xkb_layout" "us"
[ 4.727] (II) config/udev: Adding input device Vendor strings are placed here. Nuforce µDAC (/dev/input/event12)
[ 4.728] (**) Vendor strings are placed here. Nuforce µDAC : Applying InputClass "evdev keyboard catchall"
[ 4.728] (II) Using input driver 'evdev' for 'Vendor strings are placed here. Nuforce µDAC '
[ 4.728] (**) Vendor strings are placed here. Nuforce µDAC : always reports core events
[ 4.728] (**) evdev: Vendor strings are placed here. Nuforce µDAC : Device: "/dev/input/event12"
[ 4.728] (--) evdev: Vendor strings are placed here. Nuforce µDAC : Vendor 0x8bb Product 0xda48
[ 4.728] (--) evdev: Vendor strings are placed here. Nuforce µDAC : Found keys
[ 4.728] (II) evdev: Vendor strings are placed here. Nuforce µDAC : Configuring as keyboard
[ 4.728] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:08BB:DA48.0001/input/input14/event12"
[ 4.728] (II) XINPUT: Adding extended input device "Vendor strings are placed here. Nuforce µDAC " (type: KEYBOARD, id 12)
[ 4.728] (**) Option "xkb_rules" "evdev"
[ 4.728] (**) Option "xkb_model" "pc104"
[ 4.728] (**) Option "xkb_layout" "us"
[ 4.730] (II) config/udev: Adding input device SYNAPTICS Synaptics Large Touch Screen (/dev/input/mouse0)
[ 4.730] (II) No input driver specified, ignoring this device.
[ 4.730] (II) This device may have been added with another device file.
[ 4.730] (II) config/udev: Adding input device SYNAPTICS Synaptics Large Touch Screen (/dev/input/event13)
[ 4.730] (**) SYNAPTICS Synaptics Large Touch Screen: Applying InputClass "evdev touchscreen catchall"
[ 4.730] (II) Using input driver 'evdev' for 'SYNAPTICS Synaptics Large Touch Screen'
[ 4.730] (**) SYNAPTICS Synaptics Large Touch Screen: always reports core events
[ 4.730] (**) evdev: SYNAPTICS Synaptics Large Touch Screen: Device: "/dev/input/event13"
[ 4.730] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Vendor 0x6cb Product 0xac3
[ 4.730] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found absolute axes
[ 4.730] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found absolute multitouch axes
[ 4.730] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: No buttons found, faking one.
[ 4.730] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found x and y absolute axes
[ 4.730] (--) evdev: SYNAPTICS Synaptics Large Touch Screen: Found absolute touchscreen
[ 4.730] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: Configuring as touchscreen
[ 4.730] (**) evdev: SYNAPTICS Synaptics Large Touch Screen: YAxisMapping: buttons 4 and 5
[ 4.730] (**) evdev: SYNAPTICS Synaptics Large Touch Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 4.730] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/0003:06CB:0AC3.0002/input/input15/event13"
[ 4.730] (II) XINPUT: Adding extended input device "SYNAPTICS Synaptics Large Touch Screen" (type: TOUCHSCREEN, id 13)
[ 4.730] (II) evdev: SYNAPTICS Synaptics Large Touch Screen: initialized for absolute axes.
[ 4.730] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) keeping acceleration scheme 1
[ 4.730] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) acceleration profile 0
[ 4.730] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) acceleration factor: 2.000
[ 4.730] (**) SYNAPTICS Synaptics Large Touch Screen: (accel) acceleration threshold: 4
[ 4.749] (II) config/udev: Adding input device Integrated_Webcam_HD (/dev/input/event14)
[ 4.749] (**) Integrated_Webcam_HD: Applying InputClass "evdev keyboard catchall"
[ 4.749] (II) Using input driver 'evdev' for 'Integrated_Webcam_HD'
[ 4.749] (**) Integrated_Webcam_HD: always reports core events
[ 4.749] (**) evdev: Integrated_Webcam_HD: Device: "/dev/input/event14"
[ 4.749] (--) evdev: Integrated_Webcam_HD: Vendor 0xbda Product 0x573c
[ 4.749] (--) evdev: Integrated_Webcam_HD: Found keys
[ 4.749] (II) evdev: Integrated_Webcam_HD: Configuring as keyboard
[ 4.749] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11:1.0/input/input17/event14"
[ 4.749] (II) XINPUT: Adding extended input device "Integrated_Webcam_HD" (type: KEYBOARD, id 14)
[ 4.749] (**) Option "xkb_rules" "evdev"
[ 4.749] (**) Option "xkb_model" "pc104"
[ 4.749] (**) Option "xkb_layout" "us"
[ 5.381] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event15)
[ 5.381] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 5.381] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 5.382] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 5.382] (II) LoadModule: "synaptics"
[ 5.382] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 5.384] (II) Module synaptics: vendor="X.Org Foundation"
[ 5.384] compiled for 1.16.0, module version = 1.8.0
[ 5.384] Module class: X.Org XInput Driver
[ 5.384] ABI class: X.Org XInput driver, version 21.0
[ 5.384] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 5.384] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 5.384] (**) Option "Device" "/dev/input/event15"
[ 5.476] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 5.476] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5660 (res 42)
[ 5.476] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4646 (res 44)
[ 5.476] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 5.476] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 5.476] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 5.476] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 5.476] (**) Option "TapButton1" "1"
[ 5.476] (**) Option "TapButton2" "2"
[ 5.477] (**) Option "TapButton3" "3"
[ 5.477] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 5.477] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 5.477] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 5.523] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event15"
[ 5.523] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 15)
[ 5.523] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 5.523] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 5.523] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
[ 5.523] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 5.523] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 5.523] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 5.523] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 5.523] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 5.524] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 5.524] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 9.203] (II) intel(0): EDID vendor "SHP", prod id 5112
[ 9.203] (II) intel(0): Printing DDC gathered Modelines:
[ 9.203] (II) intel(0): Modeline "3200x1800"x0.0 373.25 3200 3248 3280 3360 1800 1803 1808 1852 -hsync -vsync (111.1 kHz eP)
[ 13856.646] (EE)
[ 13856.646] (EE) Backtrace:
[ 13856.649] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593966]
[ 13856.649] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197b69) [0x597b69]
[ 13856.649] (EE) 2: /usr/lib/libc.so.6 (0x7fda0f504000+0x33df0) [0x7fda0f537df0]
[ 13856.649] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda0a750000+0x10a3f8) [0x7fda0a85a3f8]
[ 13856.649] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda0a750000+0x2f641) [0x7fda0a77f641]
[ 13856.649] (EE) 5: /usr/bin/Xorg.bin (PictureDestroyWindow+0xd1) [0x509131]
[ 13856.649] (EE) 6: /usr/bin/Xorg.bin (0x400000+0x1192e8) [0x5192e8]
[ 13856.649] (EE) 7: /usr/bin/Xorg.bin (0x400000+0xd96d9) [0x4d96d9]
[ 13856.649] (EE) 8: /usr/bin/Xorg.bin (0x400000+0x114add) [0x514add]
[ 13856.649] (EE) 9: /usr/bin/Xorg.bin (0x400000+0xc94d7) [0x4c94d7]
[ 13856.649] (EE) 10: /usr/bin/Xorg.bin (0x400000+0xef030) [0x4ef030]
[ 13856.649] (EE) 11: /usr/bin/Xorg.bin (0x400000+0x6197e) [0x46197e]
[ 13856.649] (EE) 12: /usr/bin/Xorg.bin (DeleteWindow+0x232) [0x4645c2]
[ 13856.649] (EE) 13: /usr/bin/Xorg.bin (0x400000+0x5a622) [0x45a622]
[ 13856.649] (EE) 14: /usr/bin/Xorg.bin (FreeResource+0x9c) [0x45b15c]
[ 13856.649] (EE) 15: /usr/bin/Xorg.bin (0x400000+0x31cbf) [0x431cbf]
[ 13856.649] (EE) 16: /usr/bin/Xorg.bin (0x400000+0x376d7) [0x4376d7]
[ 13856.649] (EE) 17: /usr/bin/Xorg.bin (0x400000+0x3b866) [0x43b866]
[ 13856.649] (EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7fda0f524000]
[ 13856.650] (EE) 19: /usr/bin/Xorg.bin (0x400000+0x25d0e) [0x425d0e]
[ 13856.650] (EE)
[ 13856.650] (EE) Segmentation fault at address 0x0
[ 13856.650] (EE)
Fatal server error:
[ 13856.650] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 13856.650] (EE)
[ 13856.650] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 13856.650] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 13856.650] (EE)
[ 13856.650] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 13857.724] (EE) Server terminated with error (1). Closing log file.
Any ideas on what might be causing this?
Last edited by alex.forencich (2014-08-31 19:08:51)

I have a similar issue using the same graphics driver (i965) and I've been unable to track the issue down. I have little more than the stacktrace that X11 spits out. What are your hardware specs or the model of your laptop?
I'm on a Thinkpad W520. The Xorg logs are the only source of information on this issue that I've been able to find. If there's any further requests for information, do ask.
pastee (for those who prefer)
[ 6015.269]
X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 6015.269] X Protocol Version 11, Revision 0
[ 6015.269] Build Operating System: Linux 3.15.5-2-ARCH x86_64
[ 6015.269] Current Operating System: Linux T3-M4 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64
[ 6015.269] Kernel command line: root=/dev/sda6 ro init=/usr/lib/systemd/systemd resume=/dev/sda8
[ 6015.269] Build Date: 31 July 2014 11:53:19AM
[ 6015.269]
[ 6015.269] Current version of pixman: 0.32.6
[ 6015.269] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6015.269] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6015.269] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 29 18:11:43 2014
[ 6015.269] (==) Using config file: "/etc/X11/xorg.conf"
[ 6015.269] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 6015.269] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6015.270] (==) ServerLayout "X.org Configured"
[ 6015.270] (**) |-->Screen "Screen0" (0)
[ 6015.270] (**) | |-->Monitor "Monitor0"
[ 6015.270] (**) | |-->Device "Card0"
[ 6015.270] (**) |-->Input Device "Mouse0"
[ 6015.270] (**) |-->Input Device "Keyboard0"
[ 6015.270] (==) Automatically adding devices
[ 6015.270] (==) Automatically enabling devices
[ 6015.270] (==) Automatically adding GPU devices
[ 6015.270] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 6015.270] Entry deleted from font path.
[ 6015.270] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 6015.270] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 6015.270] Entry deleted from font path.
[ 6015.270] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 6015.270] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 6015.270] Entry deleted from font path.
[ 6015.270] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 6015.270] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 6015.270] Entry deleted from font path.
[ 6015.270] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 6015.270] (**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 6015.270] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 6015.270] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 6015.270] (WW) Disabling Mouse0
[ 6015.270] (WW) Disabling Keyboard0
[ 6015.270] (II) Loader magic: 0x818d80
[ 6015.270] (II) Module ABI versions:
[ 6015.270] X.Org ANSI C Emulation: 0.4
[ 6015.270] X.Org Video Driver: 18.0
[ 6015.270] X.Org XInput driver : 21.0
[ 6015.270] X.Org Server Extension : 8.0
[ 6015.271] (EE) systemd-logind: failed to get session: PID 25610 does not belong to any known session
[ 6015.271] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6015.683] (--) PCI:*(0:0:2:0) 8086:0126:17aa:21d1 rev 9, Mem @ 0xf1400000/4194304, 0xe0000000/268435456, I/O @ 0x00006000/64
[ 6015.683] (II) Open ACPI successful (/var/run/acpid.socket)
[ 6015.683] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 6015.683] (II) LoadModule: "record"
[ 6015.683] (II) Module "record" already built-in
[ 6015.683] (II) LoadModule: "extmod"
[ 6015.683] (II) Module "extmod" already built-in
[ 6015.683] (II) LoadModule: "dri2"
[ 6015.683] (II) Module "dri2" already built-in
[ 6015.683] (II) LoadModule: "dri"
[ 6015.683] (II) Module "dri" already built-in
[ 6015.683] (II) LoadModule: "glx"
[ 6015.683] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6015.684] (II) Module glx: vendor="X.Org Foundation"
[ 6015.684] compiled for 1.16.0, module version = 1.0.0
[ 6015.684] ABI class: X.Org Server Extension, version 8.0
[ 6015.684] (==) AIGLX enabled
[ 6015.684] (II) LoadModule: "dbe"
[ 6015.684] (II) Module "dbe" already built-in
[ 6015.684] (II) LoadModule: "intel"
[ 6015.684] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 6015.684] (II) Module intel: vendor="X.Org Foundation"
[ 6015.684] compiled for 1.16.0, module version = 2.99.914
[ 6015.684] Module class: X.Org Video Driver
[ 6015.684] ABI class: X.Org Video Driver, version 18.0
[ 6015.684] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 6015.684] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 6015.684] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 6015.684] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 6015.684] (++) using VT number 7
[ 6015.689] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730
[ 6015.689] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000
[ 6015.689] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
[ 6015.689] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 6015.689] (==) intel(0): RGB weight 888
[ 6015.689] (==) intel(0): Default visual is TrueColor
[ 6015.689] (II) intel(0): Output LVDS1 using monitor section Monitor0
[ 6015.689] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
[ 6015.689] (II) intel(0): Output VGA1 has no monitor section
[ 6015.689] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 6015.689] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 6015.689] (--) intel(0): Output LVDS1 using initial mode 1920x1080 on pipe 0
[ 6015.689] (==) intel(0): TearFree disabled
[ 6015.689] (==) intel(0): DPI set to (96, 96)
[ 6015.689] (II) Loading sub module "dri2"
[ 6015.689] (II) LoadModule: "dri2"
[ 6015.689] (II) Module "dri2" already built-in
[ 6015.689] (II) Loading sub module "present"
[ 6015.689] (II) LoadModule: "present"
[ 6015.689] (II) Module "present" already built-in
[ 6015.690] (==) Depth 24 pixmap format is 32 bpp
[ 6015.690] (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend
[ 6015.690] (==) intel(0): Backing store enabled
[ 6015.690] (==) intel(0): Silken mouse enabled
[ 6015.690] (II) intel(0): HW Cursor enabled
[ 6015.690] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 6015.690] (==) intel(0): DPMS enabled
[ 6015.690] (II) intel(0): [DRI2] Setup complete
[ 6015.690] (II) intel(0): [DRI2] DRI driver: i965
[ 6015.690] (II) intel(0): [DRI2] VDPAU driver: i965
[ 6015.690] (II) intel(0): direct rendering: DRI2 enabled
[ 6015.690] (II) intel(0): hardware support for Present enabled
[ 6015.690] (==) intel(0): display hotplug detection enabled
[ 6015.690] (--) RandR disabled
[ 6015.697] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 6015.697] (II) AIGLX: enabled GLX_ARB_create_context
[ 6015.697] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 6015.697] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 6015.697] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 6015.697] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 6015.697] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 6015.697] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 6015.697] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 6015.697] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 6015.697] (II) AIGLX: Loaded and initialized i965
[ 6015.697] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 6015.699] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 6015.706] (II) intel(0): Setting screen physical size to 508 x 285
[ 6015.736] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 6015.736] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6015.736] (II) LoadModule: "evdev"
[ 6015.736] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6015.736] (II) Module evdev: vendor="X.Org Foundation"
[ 6015.736] compiled for 1.16.0, module version = 2.9.0
[ 6015.736] Module class: X.Org XInput Driver
[ 6015.736] ABI class: X.Org XInput driver, version 21.0
[ 6015.736] (II) Using input driver 'evdev' for 'Power Button'
[ 6015.736] (**) Power Button: always reports core events
[ 6015.736] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 6015.736] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6015.736] (--) evdev: Power Button: Found keys
[ 6015.736] (II) evdev: Power Button: Configuring as keyboard
[ 6015.736] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4"
[ 6015.736] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 6015.737] (**) Option "xkb_rules" "evdev"
[ 6015.737] (**) Option "xkb_model" "pc104"
[ 6015.737] (**) Option "xkb_layout" "us"
[ 6015.751] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
[ 6015.751] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6015.751] (II) Using input driver 'evdev' for 'Video Bus'
[ 6015.751] (**) Video Bus: always reports core events
[ 6015.751] (**) evdev: Video Bus: Device: "/dev/input/event12"
[ 6015.751] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6015.751] (--) evdev: Video Bus: Found keys
[ 6015.751] (II) evdev: Video Bus: Configuring as keyboard
[ 6015.751] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14/event12"
[ 6015.751] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 6015.751] (**) Option "xkb_rules" "evdev"
[ 6015.751] (**) Option "xkb_model" "pc104"
[ 6015.751] (**) Option "xkb_layout" "us"
[ 6015.752] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
[ 6015.752] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6015.752] (II) Using input driver 'evdev' for 'Video Bus'
[ 6015.752] (**) Video Bus: always reports core events
[ 6015.752] (**) evdev: Video Bus: Device: "/dev/input/event13"
[ 6015.752] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6015.752] (--) evdev: Video Bus: Found keys
[ 6015.752] (II) evdev: Video Bus: Configuring as keyboard
[ 6015.752] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/LNXVIDEO:01/input/input15/event13"
[ 6015.752] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 6015.752] (**) Option "xkb_rules" "evdev"
[ 6015.752] (**) Option "xkb_model" "pc104"
[ 6015.752] (**) Option "xkb_layout" "us"
[ 6015.752] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 6015.752] (II) No input driver specified, ignoring this device.
[ 6015.752] (II) This device may have been added with another device file.
[ 6015.752] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 6015.752] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 6015.752] (II) Using input driver 'evdev' for 'Sleep Button'
[ 6015.752] (**) Sleep Button: always reports core events
[ 6015.752] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 6015.752] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 6015.752] (--) evdev: Sleep Button: Found keys
[ 6015.752] (II) evdev: Sleep Button: Configuring as keyboard
[ 6015.752] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event3"
[ 6015.752] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 6015.752] (**) Option "xkb_rules" "evdev"
[ 6015.752] (**) Option "xkb_model" "pc104"
[ 6015.752] (**) Option "xkb_layout" "us"
[ 6015.753] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 6015.753] (II) No input driver specified, ignoring this device.
[ 6015.753] (II) This device may have been added with another device file.
[ 6015.753] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event8)
[ 6015.753] (II) No input driver specified, ignoring this device.
[ 6015.753] (II) This device may have been added with another device file.
[ 6015.753] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event9)
[ 6015.753] (II) No input driver specified, ignoring this device.
[ 6015.753] (II) This device may have been added with another device file.
[ 6015.753] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 6015.753] (II) No input driver specified, ignoring this device.
[ 6015.753] (II) This device may have been added with another device file.
[ 6015.753] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 6015.753] (II) No input driver specified, ignoring this device.
[ 6015.753] (II) This device may have been added with another device file.
[ 6015.753] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6015.753] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 6015.753] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 6015.753] (**) AT Translated Set 2 keyboard: always reports core events
[ 6015.753] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 6015.753] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 6015.753] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 6015.753] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 6015.753] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6015.753] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[ 6015.753] (**) Option "xkb_rules" "evdev"
[ 6015.753] (**) Option "xkb_model" "pc104"
[ 6015.753] (**) Option "xkb_layout" "us"
[ 6015.754] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event11)
[ 6015.754] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 6015.754] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 6015.754] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 6015.754] (II) LoadModule: "synaptics"
[ 6015.754] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 6015.754] (II) Module synaptics: vendor="X.Org Foundation"
[ 6015.754] compiled for 1.16.0, module version = 1.8.0
[ 6015.754] Module class: X.Org XInput Driver
[ 6015.754] ABI class: X.Org XInput driver, version 21.0
[ 6015.754] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 6015.754] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6015.754] (**) Option "Device" "/dev/input/event11"
[ 6015.849] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 6015.849] (**) Option "TapButton1" "1"
[ 6015.849] (**) Option "TapButton2" "2"
[ 6015.849] (**) Option "TapButton3" "3"
[ 6015.849] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6015.849] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6015.916] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event11"
[ 6015.916] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11)
[ 6015.916] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 6015.916] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 6015.916] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
[ 6015.916] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 6015.916] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 6015.916] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 6015.916] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 6015.916] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6015.916] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 6015.916] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 6015.916] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event16)
[ 6015.916] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 6015.916] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
[ 6015.916] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 6015.916] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event16"
[ 6015.916] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
[ 6015.916] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 6015.916] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
[ 6015.916] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 6015.916] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
[ 6015.916] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 6015.916] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 6015.916] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input13/event16"
[ 6015.916] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 12)
[ 6015.916] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
[ 6015.916] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[ 6015.916] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[ 6015.916] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 6015.916] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 6015.917] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
[ 6015.917] (II) No input driver specified, ignoring this device.
[ 6015.917] (II) This device may have been added with another device file.
[ 6015.917] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 6015.917] (II) No input driver specified, ignoring this device.
[ 6015.917] (II) This device may have been added with another device file.
[ 6015.917] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event1)
[ 6015.917] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 6015.917] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
[ 6015.917] (**) ThinkPad Extra Buttons: always reports core events
[ 6015.917] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event1"
[ 6015.917] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
[ 6015.917] (--) evdev: ThinkPad Extra Buttons: Found keys
[ 6015.917] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
[ 6015.917] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input2/event1"
[ 6015.917] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
[ 6015.917] (**) Option "xkb_rules" "evdev"
[ 6015.917] (**) Option "xkb_model" "pc104"
[ 6015.917] (**) Option "xkb_layout" "us"
[ 6015.917] (II) config/udev: Adding input device ThinkPad HDAPS joystick emulation (/dev/input/event14)
[ 6015.917] (II) No input driver specified, ignoring this device.
[ 6015.917] (II) This device may have been added with another device file.
[ 6015.917] (II) config/udev: Adding input device ThinkPad HDAPS joystick emulation (/dev/input/js0)
[ 6015.917] (II) No input driver specified, ignoring this device.
[ 6015.917] (II) This device may have been added with another device file.
[ 6015.918] (II) config/udev: Adding input device ThinkPad HDAPS accelerometer data (/dev/input/event15)
[ 6015.918] (**) ThinkPad HDAPS accelerometer data: Ignoring device from InputClass "ThinkPad HDAPS accelerometer blacklist"
[ 6015.918] (II) config/udev: Adding input device ThinkPad HDAPS accelerometer data (/dev/input/js1)
[ 6015.918] (**) ThinkPad HDAPS accelerometer data: Ignoring device from InputClass "ThinkPad HDAPS accelerometer blacklist"
[ 6028.324] (II) intel(0): EDID vendor "AUO", prod id 4589
[ 6028.324] (II) intel(0): Printing DDC gathered Modelines:
[ 6028.324] (II) intel(0): Modeline "1920x1080"x0.0 139.00 1920 1950 1970 2014 1080 1090 1100 1150 -hsync -vsync (69.0 kHz eP)
[ 6599.333] removing GPU device /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1 /dev/dri/card1
[ 6599.333] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 6599.333] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 6599.333] (II) LoadModule: "modesetting"
[ 6599.334] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 6599.347] (II) Module modesetting: vendor="X.Org Foundation"
[ 6599.347] compiled for 1.16.0, module version = 0.9.0
[ 6599.347] Module class: X.Org Video Driver
[ 6599.347] ABI class: X.Org Video Driver, version 18.0
[ 6599.347] xf86: found device 1
[ 54835.017] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 54838.612] (II) Open ACPI successful (/var/run/acpid.socket)
[ 54838.612] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 54838.612] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 54840.952] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 84307.169] (EE)
[ 84307.169] (EE) Backtrace:
[ 84307.208] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593966]
[ 84307.209] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197b69) [0x597b69]
[ 84307.209] (EE) 2: /usr/lib/libc.so.6 (0x7f752ed68000+0x33df0) [0x7f752ed9bdf0]
[ 84307.209] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f752abdc000+0x106b05) [0x7f752ace2b05]
[ 84307.209] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f752abdc000+0x106c2a) [0x7f752ace2c2a]
[ 84307.209] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f752abdc000+0x10a423) [0x7f752ace6423]
[ 84307.209] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f752abdc000+0x2f641) [0x7f752ac0b641]
[ 84307.209] (EE) 7: /usr/bin/Xorg.bin (PictureDestroyWindow+0xd1) [0x509131]
[ 84307.209] (EE) 8: /usr/bin/Xorg.bin (0x400000+0x1192e8) [0x5192e8]
[ 84307.209] (EE) 9: /usr/bin/Xorg.bin (0x400000+0xd96d9) [0x4d96d9]
[ 84307.209] (EE) 10: /usr/bin/Xorg.bin (0x400000+0x114add) [0x514add]
[ 84307.210] (EE) 11: /usr/bin/Xorg.bin (0x400000+0xc94d7) [0x4c94d7]
[ 84307.210] (EE) 12: /usr/bin/Xorg.bin (0x400000+0xef030) [0x4ef030]
[ 84307.210] (EE) 13: /usr/bin/Xorg.bin (0x400000+0x6197e) [0x46197e]
[ 84307.210] (EE) 14: /usr/bin/Xorg.bin (DeleteWindow+0x232) [0x4645c2]
[ 84307.210] (EE) 15: /usr/bin/Xorg.bin (0x400000+0x5a622) [0x45a622]
[ 84307.210] (EE) 16: /usr/bin/Xorg.bin (FreeResource+0x9c) [0x45b15c]
[ 84307.210] (EE) 17: /usr/bin/Xorg.bin (0x400000+0x31cbf) [0x431cbf]
[ 84307.210] (EE) 18: /usr/bin/Xorg.bin (0x400000+0x376d7) [0x4376d7]
[ 84307.210] (EE) 19: /usr/bin/Xorg.bin (0x400000+0x3b866) [0x43b866]
[ 84307.210] (EE) 20: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f752ed88000]
[ 84307.210] (EE) 21: /usr/bin/Xorg.bin (0x400000+0x25d0e) [0x425d0e]
[ 84307.211] (EE)
[ 84307.211] (EE) Segmentation fault at address 0x29a070
[ 84307.211] (EE)
Fatal server error:
[ 84307.211] (EE) Caught signal 11 (Segmentation fault). Server aborting
Last edited by Kaymeerah (2014-08-30 12:25:13)

Can my Early-2011 Macbook Pro support dual DisplayPort monitors?

I have an Early-2011 Macbook Pro that Apple states can support two Apple Thunderbolt displays in series (http://support.apple.com/kb/ht5219) but I can't find any information on running two DisplayPort displays in series. I assume that Thunderbolt uses DisplayPort 1.2 which includes the link capabilities but I am not sure as I don't really understand the difference between DP and TB that well.
The displays I would be looking at using are the Dell U2414H (http://accessories.ap.dell.com/sna/productdetail.aspx?c=au&cs=aubsd1&l=en&s=bsd& sku=391-BBNC&redirect=1) which have DP in and out options.
Does anyone know if this will be possible? I don't really have a way to test this myself unfortunately.
Cheers.

I'm curious if you got this configuration working as I'd like to use the same setup (early 2011 MacBook Pro 17" + dual Dell U2414H through daisy chaining the MacBook Pro Thunderbolt port through the monitor displayports).
Apple says you can only have a DisplayPort monitor (Mini Display Port in this case), at the end of the chain, with a Thunderbolt device in between. I'm hoping this is either outdated or just not fully supported but still works.
http://support.apple.com/kb/ht5219
23. How do I connect my Mini DisplayPort monitor or monitor using a Mini DisplayPort adapter to my Thunderbolt-equipped Mac when I have other Thunderbolt devices connected?
When connecting a Mini DisplayPort display or a display using a Mini DisplayPort adapter to a Thunderbolt peripheral (except as described in question 24), make sure the display is connected at the end of the Thunderbolt chain. You can use only one Mini DisplayPort device in the Thunderbolt chain.
Note: Systems with more than one Thunderbolt port, like an iMac, can have more than one Mini DisplayPort monitor or monitor connected with a Mini DisplayPort adapter connected as each Thunderbolt port can support one Mini DisplayPort display.

SNA over the Internet

I am tasked with finding cheaper broadband solutions for connecting remote facilities back to corporate. I need to set up IPSEC tunnels from the remote to corporate that allow me to not have to change my current private addressing. This I believe I should have no problems accomplishing. The tricky part is I also have to run SNA over the Internet. Has any one tried to run a DLSW type connection over a DSL or Cable modem IPSEC tunnel. If so did, did it work or was the latency of the Internet too large to keep the dlsw peers active?
Any suggestions are appreciated.

Hi,
if you want to run dlsw over a vpn/nat solution you need to look at the following:
http://www.cisco.com/en/US/partner/tech/tk331/tk336/technologies_tech_note09186a0080093db6.shtml
this discusses problems with dlsw version 1, RFC1795, this is the default for cisco routers. The point is that the dlsw peer establishment is defined as a bringup of two single tcp connections until the capabilities exchange is done. Each router opens his own write pipe and recieves the read pipe from the other one. So each of them has two tcp pipes open at that point. Then the router with the "numerical" higher ip address drops his pipe on the local tcp port 2065.
This can cause quite some trouble if you dont control the ip nat translation inbetween. So both sides either think they have the numericaly higher ip address on its local peer and both drop the connection or both think they have the lower one and the connection times out.
Additional we commited a change to dlsw with CSCeb47150 which allows the remote device to bring up a dlsw version 2, RFC2166, peer to head end system, and in that case the peer bringup is defined with only one tcp pipe and the whole problem with who has the numericaly higher or lower ip address does not exist anymore. I copy the release note for CSCeb47150 right below here:
Symptom: Customer has DLSW defined at two locations. The locations are connected together over a
VPN tunnel. The peers start to establish and drop after capabilities excahnge.
Conditions: NAT is being used but outside the customer's point of control.
Problem: DLSw Version 1, RFC1795, defines the dlsw peer with tcp encapsulation to use 2 tcp pipes
for the peer bringup. A Write and a Read pipe. Both routers establish their respective Write pipe.
That means that if router A opens a dlsw peer to router B router A establishes his Write pipe to
router B and router B than establishes his Write Pipe back to router A. Next the capabilities
exchange happens and during this exchange the two routers decide if they can drop one tcp
connection and use the resulting tcp session for traffic in both directions. This decision is
based on the numericaly order of the local peer ip addresses. The peer with the numericaly higher
ip address is supposed to drop his tcp pipe. This is defined in RFC 1795 section 7.6.7.
If ip NAT is used inbetween the two dlsw peer routers and the NAT is changing the order of numericaly
higher or lower local peer ip address the peer may fail to establish. Both routers may think that they
are the higher ip address and both drop their tcp session or both think they are the lower ip address
and wait for the other end to take action.
Workaround: The user must preserve the numericaly order of the dlsw local peer ip addresses through
ip NAT. This is not always possible and in any case it is not an easy task.
Solution:
This ddts added a new configuration option to the dlsw peer statements:
v2-single-tcp
This is intended to do the following:
DLSw Version 2, RFC2166, defines the dlsw tcp peer bringup with a single tcp session. So above Problem
does not exist anymore since there is only one tcp session and it makes no difference which end has the
numericaly higher or lower ip address.
The v2-single-tcp keyword will instruct this router to bring up a dlsw Version 2 peer and thus both routers
will automatically only use 1 tcp session to establish the peer.
The usage of the new keyword should be like this:
Branch router A tries to establish a dlsw peer to data center router B.
Data center router B is running ios 12.0 or higher and thus already supporting dlsw version 2.
The dlsw local peer configuration on data center router B is either promiscous, to allow any incoming
peer connection, or if you have to configure each connection individual the peer to branch router A is
configured to be passive.
Branch router A is configured on his dlsw remote-peer statement with the new keyword v2-single-tcp and thus
it starts a version 2 peer to the central data center router A.
Caveats:
DLSw version 2 does not support priority peers.
thanks...
Matthias

SNA / 3270 support

Similar Messages

Maybe you are looking for