DLSW - SNA issue
My client was using IBM router at remote and connecting to IBM router at HQ with WAN line speed of 64kbps. Running OSPF. The application is running on SNA protocol.Remote branch will access the "HOST - Mainframe" at HQ.
After the migration to Cisco routers the customer complain the accessing to the "HOST' became slower.
Iniatially when on IBM platform the network design was very straight forward. The remote branch directly connected to Frame-relay cloud to HQ with one PVC.
Now there is 2 units of 7206 Cisco routers at HQ for redundancy purpose.
Branch remain with frame-relay 64 kbps but using 2 logical sub interface with different PVC to connect to the 2 units of 7206 routers at HQ.
Since running on OSPF routing protocol, IP packets can loadbalance via the both PVC but how about the SNA protocol?
Will there be any issue on the amount of bandwidth being use for SNA application after the migration since the remote branch will only connect to one of the router at one point of time using DLSW to access the HOST.
Below is my remote config. Is there any issue with this config?
dlsw local-peer peer-id x.x.x.1
dlsw remote-peer 0 tcp 141.x.x.1 <hq router 7206_1 token ring interface>
dlsw remote-peer 0 tcp 141.1.243.3 backup-peer 141.1.243.1 linger 3
dlsw icanreach sap 0 4 8 C
dlsw bridge-group 1
interface FastEthernet0/0
ip address 141.x.x.x.255.255.0
no ip redirects
ip route-cache flow
ip ospf authentication-key xxxxx
speed 100
full-duplex
bridge-group 1
interface Serial0/0
no ip address
encapsulation frame-relay IETF
no ip mroute-cache
no fair-queue
cdp enable
frame-relay lmi-type ansi
interface Serial0/0.899 point-to-point
description PVC to HQ 7206_2
bandwidth 64
ip address 10.x.x.x.x.255.252
ip ospf authentication-key xxxx
ip ospf network point-to-point
frame-relay interface-dlci 899
interface Serial0/0.900 point-to-point
description PVC to HQ 7206_1
bandwidth 64
ip address 10.x.x.x.x.255.252
ip ospf authentication-key xxx
ip ospf network point-to-point
frame-relay interface-dlci 900
Hi,
Thanks for the information. Here show tcp command
sh tcp
Stand-alone TCP connection from host 141.1.243.1
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 141.1.209.1, Local port: 2065
Foreign host: 141.1.243.1, Foreign port: 22452
Enqueued packets for retransmit: 0, input: 0 mis-ordered: -1 (0 bytes)
TCP driver queue size 0, flow controlled FALSE
Event Timers (current time is 0x32FEC44):
Timer Starts Wakeups Next
Retrans 9338 380 0x0
TimeWait 0 0 0x0
AckHold 10783 0 0x0
SendWnd 0 0 0x0
KeepAlive 1407 0 0x0
GiveUp 8957 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
iss: 3135737176 snduna: 3139076055 sndnxt: 3139076055 sndwnd: 20342
irs: 3287893903 rcvnxt: 3290222475 rcvwnd: 20022 delrcvwnd: 458
SRTT: 960 ms, RTTO: 4265 ms, RTV: 3305 ms, KRTT: 0 ms
minRTT: 20 ms, maxRTT: 3244 ms, ACK hold: 200 ms
Flags: passive open, higher precedence, retransmission timeout
Datagrams (max data segment is 536 bytes):
Rcvd: 22679 (out of order: 1258), with data: 11790, total data bytes: 2328571
Sent: 22348 (retransmit: 380, fastretransmit: 17), with data: 9722, total data b
ytes: 3347990
tty66, virtual tty from host 10.6.1.9
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 141.1.209.1, Local port: 23
Foreign host: 10.6.1.9, Foreign port: 54786
Enqueued packets for retransmit: 1, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x32FF01C):
Timer Starts Wakeups Next
Retrans 43 3 0x32FF21E
TimeWait 0 0 0x0
AckHold 34 5 0x0
SendWnd 0 0 0x0
KeepAlive 15 0 0x330D368
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
iss: 556178450 snduna: 556185105 sndnxt: 556185105 sndwnd: 4114
irs: 28892121 rcvnxt: 28892229 rcvwnd: 4021 delrcvwnd: 107
SRTT: 330 ms, RTTO: 503 ms, RTV: 173 ms, KRTT: 1006 ms
minRTT: 88 ms, maxRTT: 860 ms, ACK hold: 200 ms
Flags: passive open, higher precedence, retransmission timeout
Datagrams (max data segment is 536 bytes):
Rcvd: 82 (out of order: 15), with data: 47, total data bytes: 107
Sent: 82 (retransmit: 4, fastretransmit: 0), with data: 60, total data bytes: 7190
Similar Messages
-
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
JYPHi,
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 -
Problem establishing SNA session over DLSw link
We are experiencing sporadic problems establishing an SNA session over a DLSw tunnel. The session is between a Tandem host and a CICS region on OS/390. A Cisco 7500 router performs one end of the DLSw link; that same router is channel-attached to the OS/390 mainframe using CIP and uses CSNA for SNA traffic.
The connection is initiated by the SNA software on the Tandem box, but it rarely works on the first attempt. The session goes into a pending state and has to be cancelled and re-tried. This has to be repeated until such time it is successful. Once the session is started it works without problem.
At the point of attempting to start the session all the components are in the 'correct' state, i.e.
-DLSw tunnel is connected
-Host PU is in 'connectable' (CONCT) state
-Host XCA defining CIP SNA and virtual lines are active
No action needs to be taken on the OS/390 end of the link (or anywhere else for that matter) between start attempts on Tandem.
From device traces on OS/390 my suspicion is that the session requests are not actually getting to VTAM on OS/390 for some reason. DLSw traces on 7500 appear the same in both case of success or fail of session start.
Has anyone experienced this, or know of problems in this area that may explain what we are seeing?
Thanks.
KeithMary,
thanks for the extra information.
I would advice at this point the following:
Open a case with the Tac. Provide the information you have at that point and agree on a action plan, i.e. what to look at what trace to take, when you are able to recreate the problem.
What i can see from the documents you attaches is the following:
I only see sna circuits in the dlsw circuit history.
In you show dlsw reach there are quite some netbios names aswell and a large number of mac addresses learned from the remote peer.
You may want to discuss some filter options with the tac to make sure we cut down on the size of the reach cache and to make sure we advertise only those mac addresses which are really needed.
From the show version, 12.1(17) should be fine for dlsw in the way you described it.
From the show dlsw circuit history detail we have a couple of times that circuits are disconnecting.
Most of the time these circuits are up for a long time and they get the following sequence before terminating:
Index local addr(lsap) remote addr(dsap) remote peer
1157627904 4000.0410.0001(08) 0800.8e00.9708(08) 10.19.2.124
Created at : 12:02:55.115 GMT Mon Nov 29 2004
Connected at : 12:02:55.447 GMT Mon Nov 29 2004
Destroyed at : 22:04:01.158 GMT Wed Dec 1 2004
Local Corr : 1157627904 Remote Corr: 3321888773
Bytes: 140092/145133 Info-frames: 1748/2327
XID-frames: 1/2 UInfo-frames: 0/0
Flags: Remote created, Local connected
Last events:
Current State Event Add. Info Next State
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED ADM WanFailure 0x0 HALT_NOACK_PEND
HALT_NOACK_PEND DLC DiscCnf 0x0 CLOSE_PEND
CLOSE_PEND DLC CloseStnCnf 0x0 DISCONNECTED
this circuit was up for more than a month and the reason for disconnection was ADM WAN failure which means the dlsw peer went away at some point.
Some other circuits get these sequence:
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN halt-dl 0x0 HALT_PENDING
WAN halt-dl means the other end tells us to disconnect. No information on this end why. Most of the time it is a legitimate disconnect. but you would need to look at the dlsw peer to get information who terminated the session.
I dont see anything specific in a sense that a circuit did not go to connect at all. In the information you supplied.
Again my advice open a case with the tac and then you can work the issue to completion.
thanks...
Matthias -
Hi all,
this is related to discussion:
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=LAN%2C%20Switching%20and%20Routing&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd82da4
I opened this new one since my question was answered.
Our Topology:
Server---L2 switch---L3 Dist switch---Firewall---L3 switch(Core)--Firewall--CLOUD--IBM host
The server would generate both IP and SNA traffic (port LU6.2). All media are ethernet. The L3 switches are DLSw+ capable. I don't know much about the firewalls and I don't have control in the cloud because its under a different administrator.
Questions:
1. if I would use DLSw+, I need to bridge the ethernet port of the L3 Dist switch connecting the Server side. But, the server's connection is part of a VLAN, so, in the config of L3 Dist Switch, I would need to bridge the VLAN to DLSw. Would this setup impact the original behaviour of my VLAN? The VLAN is a Switched VLAN interface routed to another VLANs also.
2. Is it possible to control the port that would be used where the DLSW+ would pass through? I think I would have problems w/ our Firewall which requires source-destination ports and IPs to pass traffic.
Any suggestions/opinions are very much welcome... thanks!!!
rodneyHi,
if you are using vlan interfaces already than your configuration would look similar to this:
dlsw local-peer peer-id 10.10.10.1
dlsw remote-peer tcp 0 20.20.20.1
dlsw bridge-group 10
interface loopback 0
ip address 10.10.10.1 255.255.255.0
interface vlan 234
ip address ...
bridge-group 10
bridge 10 protocol vlan-bridge
that would allow you to bridge sna traffic into dlsw.
It assumes that 20.20.20.1 is the local peer configured on the partner router in front of the host.
The local peer tied to the loopback interface is just an example.
If you have i.e. more than one vlan you want to bridge than you can create multiple bridge-groups and you can configure multiple dlsw bridge-group statements. This way you bridge multiple vlans into dlsw but you dont bridge them together.
If you know the sap's you are using for sna, default is 4 as far as i know. Most commonly known are 4,8,12 than you can create an access list like this:
access-list 200 permit 0x0000 0x0d0d
and apply it to the bridge-group command on the interface.
interface vlan 234
bridge-group 10
bridge-group 10 input-sap-list 200
that allows only sap's 0,4,8,12 with and without the response bit set into the bridge group and effectively blocks all other traffic.
In respect to the tcp ports that dlsw is using over the WAN. Dlsw version 1, RFC1795, that is what cisco is using, opens always two tcp sessions at startup.
This router starts the connection, it opens a tcp connection on the destination port 2065, source port is a random port above 11000.
Now the receiving end is also opening a tcp session back to the first router. Destination port 2065, local, source port is a random port above 11000.
Next the dlsw capabilities exchange happens and the two peers exchange their information. Once they detected that they both are cisco devices and that they both support the usage of only one tcp session in both directions the one with the "numerically higher ip address" will drop its connection on the local tcp port 2065.
The remaining tcp connection is used for dlsw traffic in both directions.
this is described in detail in RFC1795, section 7.6.7.
thanks...
Matthias -
Will or can DLSW talk SNA over DIX/EthernetII?
Hi. I have a device that can talk SNA only over the DIX/Ethernet2 frame format. For this reason, it cannot communicate via Ethernet transparent bridging with our mainframe OSA Express, which requires SNA to ride the 802.3/802.2 Ethernet frame format.
My intention has been to try to resolve this by configuring DLSW (Ethernet-to-Ethernet) between two routers placed between these non-communicating devices. The hope is that DLSW will use the required 802.3 frame format to communicate on one side with the mainframe (which of course does work) and use the DIX Ethernet frame format to communicate on the other side (separate router) with the device that requires SNA to use DIX.
There is a command for this purpose, source-bridge enable-80d5, but I don't know if that command has any effect Ethernet-to-Ethernet, transparent bridging only. Without it, over Ethernet, is DLSW "smart enough" to use the frame format required by the end host?
Thank you.source-bridge enable-80d5 is local significant. It does not know the interface type of the remote dlsw router. In other words, the router with source-bridge enable-80d5 configured (say Router_a) understands DIX frames. The Router_a converts the DIX frames into information required by DLSw SSP protocol (i.e. SSAP, DSAP, MAC addresses and so on). Router_a has no idea how the remote DLSw router use the information.
Similarly, Router_a converts a DLSw frame into DIX frames. The remote DLSw router has no idea that Router_a is using DIX frame format. -
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?
ThanksFor 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.
-
Hi,
We are having a problem with SNA eWay.
In our project, with an single interface, the invoking program TP (Transaction Program) in mainframe will invoke program TP (Transaction Programs) in SeeBeyond. This is fine and running well when only one interface is deployed and tested.
The problem is when we deploy more than one interface in logical host, the TP to TP communication is mismatching. The actual invoked TP by SNA gateway server is not starting in SeeBeyond. It is actually running randomly the TPs (jcds) deployed and active in the logical host.
Can any one please show some light on this.
Thanks In Advance.did you check feature set of both old and new version?
Maybe there are some DLSW issues.
Ivan -
Hi, my name is fabio and i´ve a problem with dlsw.
When i´ve configured de dlsw in a router 3600 the router 7206 that has the conection with mainframe, the same lost the comunication e appears the messagem in 3600 router, look at below:
Note: A random Spanning Tree Bridge Identifier address of 0000.0cfe.6628
has been chosen for Bridge Group 50 since there is no mac address
associated with the selected interface.
I´am putting the scheme in .ppt.
Can i sending configurations of 3600 and 7200 to help you.
thanksFabio
I'm not sure what the issue is here. The mac-address of the end-stations will not be visible in the 4948 as the SNA traffic is encaps'd in ip. Can you supply sh vers, sh runn, sh dlsw pe, sh dls reach, sh dls circuit, sh bri from the 3640 and the 7206. What is the mac-address of the end-station to which mac-address is it trying to connect ?
Matthew -
DLSw over WAN to Ethernet to Token Ring
Currently, a 3745 in Portland is token ring attached and SNA traffic travels that ring to an IBM 2210 router.
That IBM router connects to a second token ring, which a Cisco 2613 is also connected to. From there
the traffic travels DLSw over the WAN (3 T1s, Multilink PPP bundle) to a 7507 in Cincinnati where a 3745
is connected via serial.
3745-TIC<->TR<->2210<->TR<->2613(DLSw)<->WAN<->(DLSw)7507<->LIC-3745
The 7507 serial port is configured as follows:
interface Serial4/3
description 3745 LIC connection for Fred Meyer DLSW
mtu 4400
no ip address
encapsulation sdlc
no ip mroute-cache
no keepalive
serial restart-delay 0
clockrate 125000
sdlc vmac 4000.3745.0000
sdlc N1 35200
sdlc address 29 seconly
sdlc partner 4000.0910.0008 29
sdlc dlsw 29
The 2613 has an ethernet. The folks in Portland want to move off of the TR and on to Ethernet.
They will replace the IBM router with one that has both TR and ENET.
If we move to the ethernet, the result will be:
3745-TIC<->TR<->2210<->ENET<->2613(DLSw)<->WAN<->(DLSw)7507<->LIC-3745
Should I change the MTU size on the serial port to 1500 (Ethernet)?
Are there any changes that should occur on the 3745/Mainframe side?
Do you see any other issues?You cannot increase the MTU for ethernet larger than 1500 bytes because 802.3 (the standard for ethernet) does not allow that.
You may see issues. The problem is that both 3745 does not know the existance of the ethernet. If either 3745 sends a packet larger than 1500 bytes, the 2613 will drop the packet. (I am not an expert on 2210, I do not know if the 2210 is smart enough to segment the SNA packet into 2. I doubt it does, but please confirm it with IBM.) This causes the remote FEP detects a gap in SDLC, LLC2, or TH sequence number. No matter which layer detects the problem. The end result is still the same. The DLSw circuit will be disconnected.
There are several suggestions to your problem:
1. Make sure the both FEP will not send any PIU larger than 1500 bytes. This can be done either on the NCP gen or modtab. Checking the modtab is tough because your system programmers have to know all application running over the link. Then, they have to check the corresponding modtab entry for the applications.
2. run DLSw between 7507 to IBM 2210
3. directly connect the 2613 to the TIC (3745) -
Hello:
i have a issue about load balancing adn redundance in Routers working with SNA DLsw.
in one router i have a master and the other is slave.
MASTER:
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
SLAVE:
dlsw transparent redundancy-enable 9999.9999.9999
If i want to make redundance in the master, do i have to put the redundancy-enable command in the second port? for example
MASTER:
int e0
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
int e1
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
is this configuration right, does anybody knows something about this?
RegardsAnswer to my question: http://ieoc.com/forums/p/26385/218976.aspx#218976
-
DLSW peers causing congestions
I noticed lately that my peers to the datacentre is causing congestions issues. Once I remove the peer or redirect it to another router performance on the WAN to the remote site improves.
This doesn't sound like a new issue can anyone relate?1. Cisco implements DLSw version 2 in 11.3. DLSw version 2 uses UDP for non-llc2 traffic. If one of the DLSw peers router use 11.2 software, you will not see UDP traffic on the DLSw pipe.
2. DLSw icanreach 00 04 f0 specifies SAP (service access point) transported by DLSw. 04 is the default SAP for SNA traffic. I have seen a couple of companies use other SAP value for SNA. F0 is the default SAP value for NETBIOS. In short, DLSW icanreach command is a filter to filter out all traffic, but SNA and NETBIOS, from DLSw. Very powerful command. Please go to the following URL for details:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm_r1/br1fprt2/br1fdlsw.htm#xtocid15
3. As per above URL, DLSw icanreach is introduced in IOS 11.0. If you do not get the global command, you may run a pre 11.0 software. This is a big problem for you because any IOS version before 11.2 is not Y2K compliant. (Does anyone still care on Y2K?) Please verify the IOS version by using show version. -
Migrate network segment to vlan routing with dlsw+
Currently, the dlsw are terminated on the core router which has token ring interface. The rest of the network are segmented using ethernet interface on the core router.
I need to migrate the network segment on the core router to cat6509 which will run inter-vlan routing.
My concern is when I move down the bridge group from the router ethernet, any issue will arise?
core router core router
| |
cat6509--------cat6509Hi,
My HQ router running SRB/TB to allow ethernet segment at HQ router to access IBM host. There is an active dlsw peer to BR1 and backup peer to BR2.
L1 and L2 are links between gigabit interface to routed port at core switch which running bridge group 1.
CS2 will be the root for vlan 20,40,200. CS1 will be the root for vlan 10,30,100.
L3 and L4 are trunk link to CS1 and CS2. AS1 is connected to DS1 on a port assigned to VLAN200. SNA client is on vlan 200.
Vlan 20,40,200 are assigned to bridge group 1.
For normal operation, SNA client establish circuit to the host. From CS1, I can see host mac address learn through bridge which is from gigabit interface connected to BR1. From CS2, I can see the host mac address learn through port channel.
When L4 link down, the circuit still maintain with interruption. This time CS2 does not display any host mac address due DS1 will forward vlan 200 to CS1. The SNA traffic will go direct to BR1.
During L4 recover ( meaning reconnect back the lost connection), I can see host mac address learn through vlan 20,40,200.
After the mac aging, all mac address disappear and I cant establish any SNA session. What could be the problem for this? -
DLSW - Transparent Bridging via FE Subinterfaces?
Hi. I have a 7206 router connected with FE to a Catalyst 6509, via 802.1Q trunking. Two VLANs. The router supports DLSW to remote sites, and the switch transports SNA traffic to the router with transparent bridging through one of the FE subinterfaces.
What I'd like to do is establish DLSW peering between the router and another device on the local LAN -- in other words, also through the FE interface connected to the 6509. I don't have another physical FE interface on the router. Two questions:
1) Is there any reason I would run into difficulty setting up another VLAN on the switch and another FE subinterface in the router, and using the new VLAN/subinterface for DLSW, while keeping the other subinterface configured to use transparent bridging?
2) In that configuration, might there be any issue transporting SNA into and out of the router via the one FE subinterface configured with a bridge group and the other FE subinterface being used for the DLSW path? That is, I will need the router to decapsulate the SNA coming in via DSLW on one subinterface, and bridge it out the other subinterface, and vice-versa.
Thanks for any guidance.I'm not sure how well I managed to explain the scenario in the previous post. An attempt to clarify:
VLAN1 -\ FE.Subinterface1
[6509] VLAN2 --> <=-802.1Q-=> FE.Subinterface2 [7206]
VLAN3 -/ FE.Subinterface3
6509
VLAN 1: bridge group 1
VLAN 2: bridge group 1
VLAN 3: L2-only VLAN (no definition in the MSFC). Used only to transport DLSW (and other IP) traffic to and from a router also running DLSW to FE.Subinterface3 on the 7206 through the 802.1Q trunk.
7206
FE.Subinterface1: bridge-group 1
FE.Subinterface2: bridge-group 1 (blocked by STP)
FE.Subinterface3: not in a bridge group. The interface through which the 7206 communicates with an internal router running DLSW (transporting SNA for a device directly connected to that internal router).
Traffic path
SNA must travel between the device the 7206 is DLSW peering with through FE.Subinterface3, and a device (a mainframe OSA Express interface) the 7206's SNA traffic can reach via transparent bridging through FE.Subinterface1.
The "steps": the 7206 uses FE.Subinterface3 to receive DLSW TCP/IP-encapsulated SNA traffic from the other DLSW router. The SNA traffic gets decapsulated in the 7206, and is bridged to the mainframe OSA Express interface via FE.Subinterface1. And of course the reverse, from the mainframe, transparently bridged into the 7206 through FE.Subinterface1 and sent via DLSW through FE.Subinterface3.
Do-able? Thanks! -
Street View (google maps) not working on Firefox with SNA
I have a problem with Firefox when trying to use Street View in Google Maps. It basically kills the browser by being extremely slow. Now, this happens only when using SNA acceleration (default), but not with UXA or GLAMOR (just removed on latest update or xf86-video-intel). Everything else works fast and good with SNA, including WebGL in Firefox. Moreover, with Chromium I don't have this issue: Street View works fine with SNA.
This is an Intel based laptop with Gen5 Intel graphics (and in case it matters, I use KDE desktop):
# cat /var/log/Xorg.0.log | grep SNA
[455944.801] (II) intel(0): SNA initialized with Ironlake (gen5) backend
Anyone else noticed this? Any idea of what can be the problem?I have a problem with Firefox when trying to use Street View in Google Maps. It basically kills the browser by being extremely slow. Now, this happens only when using SNA acceleration (default), but not with UXA or GLAMOR (just removed on latest update or xf86-video-intel). Everything else works fast and good with SNA, including WebGL in Firefox. Moreover, with Chromium I don't have this issue: Street View works fine with SNA.
This is an Intel based laptop with Gen5 Intel graphics (and in case it matters, I use KDE desktop):
# cat /var/log/Xorg.0.log | grep SNA
[455944.801] (II) intel(0): SNA initialized with Ironlake (gen5) backend
Anyone else noticed this? Any idea of what can be the problem? -
[solved] XFCE Dual monitor causes theme & icon, xconf issues
Hey all,
Here is the issue:
I have sony svz13114gxx laptop with xfce4 DE, i just tried to hook up external vga monitor to laptop and everything configures right (no mirroring) with this run in normal session:
xrandr --output eDP1 --mode 1920x1080
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode VGA1 1920x1200_60.00
xrandr --output VGA1 --mode 1920x1200_60.00
xrandr --output VGA1 --left-of eDP1
Obviously when i reboot this is not persistent, so then i put this stuff in my /etc/X11/xorg.conf.d/20-intel.conf:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "monitor-eDP1" "eDP1"
Option "monitor-VGA1" "VGA1"
EndSection
Section "Monitor"
Identifier "VGA1"
Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -HSync +VSync
Option "PreferredMode" "1920x1200_60.00"
EndSection
Section "Monitor"
Identifier "eDP1"
Option "PreferredMode" "1920x1080"
Option "Primary" "true"
Option "Position" "1920 0"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Intel Graphics"
Monitor "eDP1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
This is where the problems start. On reboot Slim desktop manager seems to be stretched properly across the two monitors, but the I login and the display switches back to being mirrored, my xfce gtk2 theme is disabled in favor of somee default looking one, my icons are back to default, and none of my custom keyboard shorcuts work.
I can then use xrandr to get the displays in extended mode again, but the themes and icons etc do not revert. And on reboot, i have the same issue.
I have tried the sourcing ~/.xprofile, ~/.xinitrc, and ~/.config.xfce4/xinitrc routes, putting the xrandr cammands above the exec lines and that doesn't even enable VGA1.
I have been to all these places
https://wiki.ubuntu.com/X/Config/Resolution#Xrandr_Graphical_Front_End_GUI
http://ilkinbalkanay.blogspot.com/2008/01/extended-desktop-configuration-with.html
https://bbs.archlinux.org/viewtopic.php?id=98747
https://www.google.com/search?q=arch%20xrandr&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&source=hp&channel=np
https://wiki.archlinux.org/index.php/Execute_commands_after_X_start
http://intellinuxgraphics.org/dualhead.html
http://mac.linux.be/content/setting-xorgconf-manually-xrandr#3
https://www.google.com/search?q=arch%20dual%20monitors%20The%20last%20active%20output%20must%20not%20be%20disabled%2C%20the%20system%20would%20be%20unusable.&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&source=hp&channel=np#hl=en&safe=off&client=firefox-a&tbo=d&rls=org.mozilla:en-US%3Aofficial&channel=np&sclient=psy-ab&q=xfce+%22Selected+output+not+disabled%22&oq=xfce+%22Selected+output+not+disabled%22&gs_l=serp.3...1694.1694.3.2205.1.1.0.0.0.0.97.97.1.1.0.les%3Bcrnk_timediscounta..0.0...1c.1.O4EDj7DaWlA&pbx=1&fp=1&bpcl=39468505&biw=984&bih=936&cad=b&sei=aKC_UIKvJ6GA0AGTg4HwBg&sei=FKS_UMuwJdPU0gHorICQBA&bav=on.2,or.r_gc.r_pw.r_qf.&sei=2MK_UOaAJ5Ph0wGbsoHICg
https://wiki.archlinux.org/index.php/Xfce#Customizing_Startup_Applications
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html
https://wiki.archlinux.org/index.php/Xorg#Monitor_settings
Even after much research, still no luck.
this might be useful:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631225
Anyone have any ideas?
here is my Xorg0.log
[ 3.490]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 3.490] X Protocol Version 11, Revision 0
[ 3.490] Build Operating System: Linux 3.6.3-1-ARCH x86_64
[ 3.490] Current Operating System: Linux tcz 3.6.8-1-ARCH #1 SMP PREEMPT Mon Nov 26 22:10:40 CET 2012 x86_64
[ 3.490] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d23251af-35fa-426b-a7d5-5aa2f0a5b87d ro quiet pcie_aspm=force i915.i915_enable_rc6=1
[ 3.490] Build Date: 08 November 2012 07:09:29PM
[ 3.490]
[ 3.490] Current version of pixman: 0.28.0
[ 3.490] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.490] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.490] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 5 16:25:21 2012
[ 3.492] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3.494] (==) No Layout section. Using the first Screen section.
[ 3.494] (**) |-->Screen "Default Screen" (0)
[ 3.494] (**) | |-->Monitor "eDP1"
[ 3.494] (**) | |-->Device "Intel Graphics"
[ 3.494] (==) Automatically adding devices
[ 3.494] (==) Automatically enabling devices
[ 3.494] (==) Automatically adding GPU devices
[ 3.504] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.504] Entry deleted from font path.
[ 3.504] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.504] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.504] Entry deleted from font path.
[ 3.504] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.504] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 3.504] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.504] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.504] (II) Loader magic: 0x7fcc40
[ 3.504] (II) Module ABI versions:
[ 3.504] X.Org ANSI C Emulation: 0.4
[ 3.504] X.Org Video Driver: 13.1
[ 3.504] X.Org XInput driver : 18.0
[ 3.504] X.Org Server Extension : 7.0
[ 3.505] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 6.276] (--) PCI:*(0:0:2:0) 8086:0166:104d:90a5 rev 9, Mem @ 0xd7000000/4194304, 0xc0000000/268435456, I/O @ 0x00009000/64
[ 6.276] (II) Open ACPI successful (/var/run/acpid.socket)
[ 6.276] Initializing built-in extension Generic Event Extension
[ 6.276] Initializing built-in extension SHAPE
[ 6.276] Initializing built-in extension MIT-SHM
[ 6.276] Initializing built-in extension XInputExtension
[ 6.276] Initializing built-in extension XTEST
[ 6.276] Initializing built-in extension BIG-REQUESTS
[ 6.276] Initializing built-in extension SYNC
[ 6.276] Initializing built-in extension XKEYBOARD
[ 6.276] Initializing built-in extension XC-MISC
[ 6.276] Initializing built-in extension SECURITY
[ 6.276] Initializing built-in extension XINERAMA
[ 6.276] Initializing built-in extension XFIXES
[ 6.276] Initializing built-in extension RENDER
[ 6.276] Initializing built-in extension RANDR
[ 6.276] Initializing built-in extension COMPOSITE
[ 6.276] Initializing built-in extension DAMAGE
[ 6.276] Initializing built-in extension MIT-SCREEN-SAVER
[ 6.276] Initializing built-in extension DOUBLE-BUFFER
[ 6.276] Initializing built-in extension RECORD
[ 6.276] Initializing built-in extension DPMS
[ 6.276] Initializing built-in extension X-Resource
[ 6.276] Initializing built-in extension XVideo
[ 6.276] Initializing built-in extension XVideo-MotionCompensation
[ 6.276] Initializing built-in extension XFree86-VidModeExtension
[ 6.276] Initializing built-in extension XFree86-DGA
[ 6.276] Initializing built-in extension XFree86-DRI
[ 6.276] Initializing built-in extension DRI2
[ 6.276] (II) LoadModule: "glx"
[ 6.278] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.281] (II) Module glx: vendor="X.Org Foundation"
[ 6.281] compiled for 1.13.0, module version = 1.0.0
[ 6.281] ABI class: X.Org Server Extension, version 7.0
[ 6.281] (==) AIGLX enabled
[ 6.281] Loading extension GLX
[ 6.281] (II) LoadModule: "intel"
[ 6.281] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 6.285] (II) Module intel: vendor="X.Org Foundation"
[ 6.285] compiled for 1.13.0.901, module version = 2.20.14
[ 6.285] Module class: X.Org Video Driver
[ 6.285] ABI class: X.Org Video Driver, version 13.1
[ 6.285] (II) intel: Driver for Intel 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, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
ValleyView PO board
[ 6.286] (++) using VT number 7
[ 6.288] (II) intel(0): using device path '/dev/dri/card0'
[ 6.288] (**) intel(0): Depth 24, (--) framebuffer bpp 32
[ 6.288] (==) intel(0): RGB weight 888
[ 6.288] (==) intel(0): Default visual is TrueColor
[ 6.288] (**) intel(0): Option "AccelMethod" "sna"
[ 6.288] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 6.289] (**) intel(0): Framebuffer tiled
[ 6.289] (**) intel(0): Pixmaps tiled
[ 6.289] (**) intel(0): 3D buffers tiled
[ 6.289] (**) intel(0): Throttling enabled
[ 6.289] (**) intel(0): Delayed flush enabled
[ 6.289] (**) intel(0): "Tear free" disabled
[ 6.289] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 6.289] (II) intel(0): Output eDP1 using monitor section eDP1
[ 6.289] (**) intel(0): Option "PreferredMode" "1920x1080"
[ 6.289] (**) intel(0): Option "Position" "1920 0"
[ 6.289] (**) intel(0): Option "Primary" "true"
[ 6.289] (--) intel(0): found backlight control interface acpi_video0 (type 'firmware')
[ 6.293] (II) intel(0): Output VGA1 using monitor section VGA1
[ 6.293] (**) intel(0): Option "PreferredMode" "1920x1200_60.00"
[ 6.294] (II) intel(0): Output HDMI1 has no monitor section
[ 6.336] (II) intel(0): Output DP1 has no monitor section
[ 6.337] (II) intel(0): EDID for output eDP1
[ 6.337] (II) intel(0): Manufacturer: MS_ Model: 25 Serial#: 16843009
[ 6.337] (II) intel(0): Year: 2012 Week: 24
[ 6.337] (II) intel(0): EDID Version: 1.4
[ 6.337] (II) intel(0): Digital Display Input
[ 6.337] (II) intel(0): 8 bits per channel
[ 6.337] (II) intel(0): Digital interface is DisplayPort
[ 6.337] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
[ 6.337] (II) intel(0): Gamma: 2.20
[ 6.337] (II) intel(0): No DPMS capabilities specified
[ 6.337] (II) intel(0): Supported color encodings: RGB 4:4:4
[ 6.337] (II) intel(0): First detailed timing is preferred mode
[ 6.337] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 6.337] (II) intel(0): redX: 0.602 redY: 0.336 greenX: 0.296 greenY: 0.546
[ 6.337] (II) intel(0): blueX: 0.148 blueY: 0.126 whiteX: 0.313 whiteY: 0.329
[ 6.337] (II) intel(0): Manufacturer's mask: 0
[ 6.337] (II) intel(0): Supported standard timings:
[ 6.337] (II) intel(0): #0: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 6.337] (II) intel(0): Supported detailed timing:
[ 6.337] (II) intel(0): clock: 162.8 MHz Image Size: 291 x 164 mm
[ 6.337] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1984 h_blank_end 2481 h_border: 0
[ 6.337] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1086 v_blanking: 1095 v_border: 0
[ 6.337] (II) intel(0): Supported detailed timing:
[ 6.337] (II) intel(0): clock: 99.9 MHz Image Size: 291 x 164 mm
[ 6.337] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1984 h_blank_end 2281 h_border: 0
[ 6.337] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1086 v_blanking: 1095 v_border: 0
[ 6.337] (II) intel(0): Monitor name: Sony LCD
[ 6.337] (II) intel(0): Ranges: V min: 39 V max: 61 Hz, H min: 43 H max: 66 kHz, PixClock max 175 MHz
[ 6.337] (II) intel(0): EDID (in hex):
[ 6.337] (II) intel(0): 00ffffffffffff00367f250001010101
[ 6.337] (II) intel(0): 18160104a51d1078020f159a564b8b26
[ 6.337] (II) intel(0): 205054000000d1c00101010101010101
[ 6.337] (II) intel(0): 0101010101019c3f803172380f402020
[ 6.337] (II) intel(0): 330023a4100000180727806971380f40
[ 6.337] (II) intel(0): 2020330023a410000018000000fc0053
[ 6.337] (II) intel(0): 6f6e79204c43440a20202020000000fd
[ 6.337] (II) intel(0): 00273d2b4211000a2020202020200013
[ 6.337] (II) intel(0): EDID vendor "MS_", prod id 37
[ 6.337] (II) intel(0): Using EDID range info for horizontal sync
[ 6.337] (II) intel(0): Using EDID range info for vertical refresh
[ 6.337] (II) intel(0): Printing DDC gathered Modelines:
[ 6.337] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 6.337] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 6.337] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 6.337] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 6.337] (II) intel(0): Printing probed modes for output eDP1
[ 6.337] (II) intel(0): Modeline "1920x1080"x59.9 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz UeP)
[ 6.337] (II) intel(0): Modeline "1920x1080"x40.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 6.338] (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 6.338] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
[ 6.338] (II) intel(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 6.338] (II) intel(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 6.338] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 6.338] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 6.338] (II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 6.338] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 6.338] (II) intel(0): Modeline "1366x768"x60.0 85.89 1366 1439 1583 1800 768 769 772 795 -hsync +vsync (47.7 kHz)
[ 6.338] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 6.338] (II) intel(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 6.338] (II) intel(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 6.338] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 6.338] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 6.338] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 6.338] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 6.343] (II) intel(0): EDID for output VGA1
[ 6.343] (II) intel(0): Printing probed modes for output VGA1
[ 6.343] (II) intel(0): Modeline "1920x1200_60.00"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz UP)
[ 6.343] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 6.344] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 6.344] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 6.344] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 6.344] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 6.344] (II) intel(0): EDID for output HDMI1
[ 6.386] (II) intel(0): EDID for output DP1
[ 6.386] (II) intel(0): Output eDP1 connected
[ 6.386] (II) intel(0): Output VGA1 connected
[ 6.386] (II) intel(0): Output HDMI1 disconnected
[ 6.386] (II) intel(0): Output DP1 disconnected
[ 6.386] (II) intel(0): Using user preference for initial modes
[ 6.386] (II) intel(0): Output eDP1 using initial mode 1920x1080
[ 6.386] (II) intel(0): Output VGA1 using initial mode 1920x1200_60.00
[ 6.386] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 6.386] (**) intel(0): Display dimensions: (290, 160) mm
[ 6.386] (**) intel(0): DPI set to (336, 190)
[ 6.386] (II) Loading sub module "dri2"
[ 6.386] (II) LoadModule: "dri2"
[ 6.387] (II) Module "dri2" already built-in
[ 6.387] (==) Depth 24 pixmap format is 32 bpp
[ 6.387] (II) intel(0): SNA initialized with IvyBridge backend
[ 6.387] (==) intel(0): Backing store disabled
[ 6.387] (==) intel(0): Silken mouse enabled
[ 6.387] (II) intel(0): HW Cursor enabled
[ 6.387] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 6.388] (==) intel(0): DPMS enabled
[ 6.388] (II) intel(0): [DRI2] Setup complete
[ 6.388] (II) intel(0): [DRI2] DRI driver: i965
[ 6.388] (II) intel(0): direct rendering: DRI2 Enabled
[ 6.388] (WW) intel(0): Option "PreferredMode" is not used
[ 6.388] (WW) intel(0): Option "Primary" is not used
[ 6.388] (WW) intel(0): Option "Position" is not used
[ 6.388] (==) intel(0): hotplug detection: "enabled"
[ 6.388] (--) RandR disabled
[ 6.410] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 6.410] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 6.410] (II) AIGLX: enabled GLX_ARB_create_context
[ 6.410] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 6.410] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 6.410] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 6.410] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 6.410] (II) AIGLX: Loaded and initialized i965
[ 6.410] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 6.411] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
[ 6.500] (II) intel(0): switch to mode 1920x1200 on crtc 5 (pipe 1)
[ 6.663] (II) intel(0): Setting screen physical size to 1016 x 317
[ 6.703] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[ 6.703] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6.703] (II) LoadModule: "evdev"
[ 6.704] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.706] (II) Module evdev: vendor="X.Org Foundation"
[ 6.706] compiled for 1.13.0, module version = 2.7.3
[ 6.706] Module class: X.Org XInput Driver
[ 6.706] ABI class: X.Org XInput driver, version 18.0
[ 6.706] (II) Using input driver 'evdev' for 'Video Bus'
[ 6.706] (**) Video Bus: always reports core events
[ 6.706] (**) evdev: Video Bus: Device: "/dev/input/event10"
[ 6.706] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6.706] (--) evdev: Video Bus: Found keys
[ 6.706] (II) evdev: Video Bus: Configuring as keyboard
[ 6.706] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:09/input/input10/event10"
[ 6.706] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 6.706] (**) Option "xkb_rules" "evdev"
[ 6.706] (**) Option "xkb_model" "evdev"
[ 6.706] (**) Option "xkb_layout" "us"
[ 6.732] (II) config/udev: Adding input device Sony Vaio Keys (/dev/input/event3)
[ 6.732] (**) Sony Vaio Keys: Applying InputClass "evdev keyboard catchall"
[ 6.732] (II) Using input driver 'evdev' for 'Sony Vaio Keys'
[ 6.732] (**) Sony Vaio Keys: always reports core events
[ 6.732] (**) evdev: Sony Vaio Keys: Device: "/dev/input/event3"
[ 6.732] (--) evdev: Sony Vaio Keys: Vendor 0x104d Product 0
[ 6.732] (--) evdev: Sony Vaio Keys: Found keys
[ 6.732] (II) evdev: Sony Vaio Keys: Configuring as keyboard
[ 6.732] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/SNY5001:00/input/input3/event3"
[ 6.732] (II) XINPUT: Adding extended input device "Sony Vaio Keys" (type: KEYBOARD, id 7)
[ 6.732] (**) Option "xkb_rules" "evdev"
[ 6.732] (**) Option "xkb_model" "evdev"
[ 6.732] (**) Option "xkb_layout" "us"
[ 6.732] (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/event4)
[ 6.732] (II) No input driver specified, ignoring this device.
[ 6.732] (II) This device may have been added with another device file.
[ 6.733] (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/mouse0)
[ 6.733] (II) No input driver specified, ignoring this device.
[ 6.733] (II) This device may have been added with another device file.
[ 6.733] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 6.733] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.733] (II) Using input driver 'evdev' for 'Power Button'
[ 6.733] (**) Power Button: always reports core events
[ 6.733] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 6.733] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.733] (--) evdev: Power Button: Found keys
[ 6.733] (II) evdev: Power Button: Configuring as keyboard
[ 6.733] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[ 6.733] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 6.733] (**) Option "xkb_rules" "evdev"
[ 6.733] (**) Option "xkb_model" "evdev"
[ 6.733] (**) Option "xkb_layout" "us"
[ 6.733] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 6.733] (II) No input driver specified, ignoring this device.
[ 6.733] (II) This device may have been added with another device file.
[ 6.733] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 6.734] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 6.734] (II) No input driver specified, ignoring this device.
[ 6.734] (II) This device may have been added with another device file.
[ 6.734] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event7)
[ 6.734] (II) No input driver specified, ignoring this device.
[ 6.734] (II) This device may have been added with another device file.
[ 6.735] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event8)
[ 6.735] (II) No input driver specified, ignoring this device.
[ 6.735] (II) This device may have been added with another device file.
[ 6.735] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6.735] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 6.735] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 6.735] (**) AT Translated Set 2 keyboard: always reports core events
[ 6.735] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 6.735] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 6.735] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 6.735] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 6.735] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6.735] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 6.735] (**) Option "xkb_rules" "evdev"
[ 6.735] (**) Option "xkb_model" "evdev"
[ 6.735] (**) Option "xkb_layout" "us"
[ 6.736] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
[ 6.736] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 6.736] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 6.736] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 6.736] (II) LoadModule: "synaptics"
[ 6.737] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 6.738] (II) Module synaptics: vendor="X.Org Foundation"
[ 6.738] compiled for 1.13.0, module version = 1.6.2
[ 6.738] Module class: X.Org XInput Driver
[ 6.738] ABI class: X.Org XInput driver, version 18.0
[ 6.738] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 6.738] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6.738] (**) Option "Device" "/dev/input/event9"
[ 6.740] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5768
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4758
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 6.740] (**) Option "FingerLow" "35"
[ 6.740] (**) Option "FingerHigh" "45"
[ 6.740] (**) Option "ClickPad" "true"
[ 6.740] (**) Option "EmulateMidButtonTime" "0"
[ 6.740] (**) Option "HorizTwoFingerScroll" "on"
[ 6.740] (**) Option "TapButton1" "1"
[ 6.740] (**) Option "TapButton2" "2"
[ 6.740] (**) Option "TapButton3" "3"
[ 6.740] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 6.740] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6.740] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 6.740] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
[ 6.740] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
[ 6.741] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 6.741] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[ 6.741] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.037
[ 6.741] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 6.741] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 6.741] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 6.741] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 6.741] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6.742] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 6.742] (II) No input driver specified, ignoring this device.
[ 6.742] (II) This device may have been added with another device file.
[ 6.742] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 6.742] (II) No input driver specified, ignoring this device.
[ 6.742] (II) This device may have been added with another device file.
[ 6.747] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 21764432
[ 6.747] xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[ 6.747] failed to find screen to remove
[ 6.747] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 6.747] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1 0
[ 6.747] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 0
[ 6.747] (II) config/udev: removing device Video Bus
[ 6.773] (II) evdev: Video Bus: Close
[ 6.773] (II) UnloadModule: "evdev"
[ 6.773] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[ 6.773] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6.773] (II) Using input driver 'evdev' for 'Video Bus'
[ 6.773] (**) Video Bus: always reports core events
[ 6.773] (**) evdev: Video Bus: Device: "/dev/input/event10"
[ 6.773] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6.773] (--) evdev: Video Bus: Found keys
[ 6.773] (II) evdev: Video Bus: Configuring as keyboard
[ 6.773] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:09/input/input10/event10"
[ 6.773] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 6.773] (**) Option "xkb_rules" "evdev"
[ 6.773] (**) Option "xkb_model" "evdev"
[ 6.773] (**) Option "xkb_layout" "us"
[ 6.774] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1 0
[ 6.774] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1 0
[ 7.569] (II) config/udev: Adding input device USB2.0 Camera (/dev/input/event11)
[ 7.569] (**) USB2.0 Camera: Applying InputClass "evdev keyboard catchall"
[ 7.569] (II) Using input driver 'evdev' for 'USB2.0 Camera'
[ 7.569] (**) USB2.0 Camera: always reports core events
[ 7.569] (**) evdev: USB2.0 Camera: Device: "/dev/input/event11"
[ 7.569] (--) evdev: USB2.0 Camera: Vendor 0x5ca Product 0x18c6
[ 7.569] (--) evdev: USB2.0 Camera: Found keys
[ 7.569] (II) evdev: USB2.0 Camera: Configuring as keyboard
[ 7.569] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input11/event11"
[ 7.569] (II) XINPUT: Adding extended input device "USB2.0 Camera" (type: KEYBOARD, id 11)
[ 7.569] (**) Option "xkb_rules" "evdev"
[ 7.569] (**) Option "xkb_model" "evdev"
[ 7.569] (**) Option "xkb_layout" "us"
[ 24.939] (II) intel(0): EDID vendor "MS_", prod id 37
[ 24.939] (II) intel(0): Using hsync ranges from config file
[ 24.939] (II) intel(0): Using vrefresh ranges from config file
[ 24.939] (II) intel(0): Printing DDC gathered Modelines:
[ 24.939] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 24.939] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 24.939] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 24.989] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
[ 25.055] (II) intel(0): EDID vendor "MS_", prod id 37
[ 25.055] (II) intel(0): Using hsync ranges from config file
[ 25.055] (II) intel(0): Using vrefresh ranges from config file
[ 25.055] (II) intel(0): Printing DDC gathered Modelines:
[ 25.055] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 25.055] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 25.055] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 25.150] (II) intel(0): EDID vendor "MS_", prod id 37
[ 25.150] (II) intel(0): Using hsync ranges from config file
[ 25.150] (II) intel(0): Using vrefresh ranges from config file
[ 25.150] (II) intel(0): Printing DDC gathered Modelines:
[ 25.150] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 25.150] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 25.150] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 25.274] (II) intel(0): EDID vendor "MS_", prod id 37
[ 25.274] (II) intel(0): Using hsync ranges from config file
[ 25.274] (II) intel(0): Using vrefresh ranges from config file
[ 25.274] (II) intel(0): Printing DDC gathered Modelines:
[ 25.274] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 25.274] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 25.274] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 25.387] (II) intel(0): EDID vendor "MS_", prod id 37
[ 25.387] (II) intel(0): Using hsync ranges from config file
[ 25.387] (II) intel(0): Using vrefresh ranges from config file
[ 25.387] (II) intel(0): Printing DDC gathered Modelines:
[ 25.387] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 25.387] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 25.387] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 25.518] (II) intel(0): EDID vendor "MS_", prod id 37
[ 25.518] (II) intel(0): Using hsync ranges from config file
[ 25.518] (II) intel(0): Using vrefresh ranges from config file
[ 25.518] (II) intel(0): Printing DDC gathered Modelines:
[ 25.518] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 25.518] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 25.518] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 25.676] (II) intel(0): EDID vendor "MS_", prod id 37
[ 25.676] (II) intel(0): Using hsync ranges from config file
[ 25.676] (II) intel(0): Using vrefresh ranges from config file
[ 25.676] (II) intel(0): Printing DDC gathered Modelines:
[ 25.676] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 25.676] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 25.676] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 29.373] (II) config/udev: Adding input device Bluetooth Laser Travel Mouse (/dev/input/mouse2)
[ 29.373] (II) No input driver specified, ignoring this device.
[ 29.373] (II) This device may have been added with another device file.
[ 29.373] (II) config/udev: Adding input device Bluetooth Laser Travel Mouse (/dev/input/event12)
[ 29.373] (**) Bluetooth Laser Travel Mouse: Applying InputClass "evdev pointer catchall"
[ 29.373] (II) Using input driver 'evdev' for 'Bluetooth Laser Travel Mouse'
[ 29.373] (**) Bluetooth Laser Travel Mouse: always reports core events
[ 29.373] (**) evdev: Bluetooth Laser Travel Mouse: Device: "/dev/input/event12"
[ 29.373] (--) evdev: Bluetooth Laser Travel Mouse: Vendor 0x46d Product 0xb008
[ 29.373] (--) evdev: Bluetooth Laser Travel Mouse: Found 12 mouse buttons
[ 29.373] (--) evdev: Bluetooth Laser Travel Mouse: Found scroll wheel(s)
[ 29.373] (--) evdev: Bluetooth Laser Travel Mouse: Found relative axes
[ 29.373] (--) evdev: Bluetooth Laser Travel Mouse: Found x and y relative axes
[ 29.374] (II) evdev: Bluetooth Laser Travel Mouse: Configuring as mouse
[ 29.374] (II) evdev: Bluetooth Laser Travel Mouse: Adding scrollwheel support
[ 29.374] (**) evdev: Bluetooth Laser Travel Mouse: YAxisMapping: buttons 4 and 5
[ 29.374] (**) evdev: Bluetooth Laser Travel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 29.374] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/bluetooth/hci0/hci0:33/input12/event12"
[ 29.374] (II) XINPUT: Adding extended input device "Bluetooth Laser Travel Mouse" (type: MOUSE, id 12)
[ 29.374] (II) evdev: Bluetooth Laser Travel Mouse: initialized for relative axes.
[ 29.374] (**) Bluetooth Laser Travel Mouse: (accel) keeping acceleration scheme 1
[ 29.374] (**) Bluetooth Laser Travel Mouse: (accel) acceleration profile 0
[ 29.374] (**) Bluetooth Laser Travel Mouse: (accel) acceleration factor: 2.000
[ 29.374] (**) Bluetooth Laser Travel Mouse: (accel) acceleration threshold: 4
[ 589.381] (II) intel(0): EDID vendor "MS_", prod id 37
[ 589.381] (II) intel(0): Using hsync ranges from config file
[ 589.381] (II) intel(0): Using vrefresh ranges from config file
[ 589.381] (II) intel(0): Printing DDC gathered Modelines:
[ 589.381] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 589.381] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 589.381] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 589.433] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
[ 1442.644] (II) intel(0): EDID vendor "MS_", prod id 37
[ 1442.644] (II) intel(0): Using hsync ranges from config file
[ 1442.644] (II) intel(0): Using vrefresh ranges from config file
[ 1442.644] (II) intel(0): Printing DDC gathered Modelines:
[ 1442.644]Hey all,
Here is the issue:
I have sony svz13114gxx laptop with xfce4 DE, i just tried to hook up external vga monitor to laptop and everything configures right with this run in normal session:
[code]
xrandr --output eDP1 --mode 1920x1080
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode VGA1 1920x1200_60.00
xrandr --output VGA1 --mode 1920x1200_60.00
xrandr --output VGA1 --left-of eDP1
[/code]
Obviously when i reboot this is not persistent, so then i put this stuff in my /etc/X11/xorg.conf.d/20-intel.conf:
[code]
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "monitor-eDP1" "eDP1"
Option "monitor-VGA1" "VGA1"
EndSection
Section "Monitor"
Identifier "VGA1"
Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -HSync +VSync
Option "PreferredMode" "1920x1200_60.00"
EndSection
Section "Monitor"
Identifier "eDP1"
Option "PreferredMode" "1920x1080"
Option "Primary" "true"
Option "Position" "1920 0"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Intel Graphics"
Monitor "eDP1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection[/code]
This is where the problems start. On reboot Slim desktop manager seems to be stretched properly across the two monitors, but the I login and the display switches back to being mirrored, my xfce gtk2 theme is disabled in favor of somee default looking one, my icons are back to default, and none of my custom keyboard shorcuts work.
I can then use xrandr to get the displays in extended mode again, but the themes and icons etc do not revert. And on reboot, i have the same issue.
I have tried the sourcing ~/.xprofile, ~/.xinitrc, and ~/.config.xfce4/xinitrc routes, putting the xrandr cammands above the exec lines and that doesn't even enable VGA1.
I have been to all these places
[code]
https://wiki.ubuntu.com/X/Config/Resolution#Xrandr_Graphical_Front_End_GUI
http://ilkinbalkanay.blogspot.com/2008/01/extended-desktop-configuration-with.html
https://bbs.archlinux.org/viewtopic.php?id=98747
https://www.google.com/search?q=arch%20xrandr&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&source=hp&channel=np
https://wiki.archlinux.org/index.php/Execute_commands_after_X_start
http://intellinuxgraphics.org/dualhead.html
http://mac.linux.be/content/setting-xorgconf-manually-xrandr#3
https://www.google.com/search?q=arch%20dual%20monitors%20The%20last%20active%20output%20must%20not%20be%20disabled%2C%20the%20system%20would%20be%20unusable.&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&source=hp&channel=np#hl=en&safe=off&client=firefox-a&tbo=d&rls=org.mozilla:en-US%3Aofficial&channel=np&sclient=psy-ab&q=xfce+%22Selected+output+not+disabled%22&oq=xfce+%22Selected+output+not+disabled%22&gs_l=serp.3...1694.1694.3.2205.1.1.0.0.0.0.97.97.1.1.0.les%3Bcrnk_timediscounta..0.0...1c.1.O4EDj7DaWlA&pbx=1&fp=1&bpcl=39468505&biw=984&bih=936&cad=b&sei=aKC_UIKvJ6GA0AGTg4HwBg&sei=FKS_UMuwJdPU0gHorICQBA&bav=on.2,or.r_gc.r_pw.r_qf.&sei=2MK_UOaAJ5Ph0wGbsoHICg
https://wiki.archlinux.org/index.php/Xfce#Customizing_Startup_Applications
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html
https://wiki.archlinux.org/index.php/Xorg#Monitor_settings
[/code]
Even after much research, still no luck.
this might be useful:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631225
Anyone have any ideas?
here is my Xorg0.log
[code]
[ 3.490]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 3.490] X Protocol Version 11, Revision 0
[ 3.490] Build Operating System: Linux 3.6.3-1-ARCH x86_64
[ 3.490] Current Operating System: Linux tcz 3.6.8-1-ARCH #1 SMP PREEMPT Mon Nov 26 22:10:40 CET 2012 x86_64
[ 3.490] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d23251af-35fa-426b-a7d5-5aa2f0a5b87d ro quiet pcie_aspm=force i915.i915_enable_rc6=1
[ 3.490] Build Date: 08 November 2012 07:09:29PM
[ 3.490]
[ 3.490] Current version of pixman: 0.28.0
[ 3.490] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3.490] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.490] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 5 16:25:21 2012
[ 3.492] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3.494] (==) No Layout section. Using the first Screen section.
[ 3.494] (**) |-->Screen "Default Screen" (0)
[ 3.494] (**) | |-->Monitor "eDP1"
[ 3.494] (**) | |-->Device "Intel Graphics"
[ 3.494] (==) Automatically adding devices
[ 3.494] (==) Automatically enabling devices
[ 3.494] (==) Automatically adding GPU devices
[ 3.504] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3.504] Entry deleted from font path.
[ 3.504] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3.504] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3.504] Entry deleted from font path.
[ 3.504] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3.504] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 3.504] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3.504] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.504] (II) Loader magic: 0x7fcc40
[ 3.504] (II) Module ABI versions:
[ 3.504] X.Org ANSI C Emulation: 0.4
[ 3.504] X.Org Video Driver: 13.1
[ 3.504] X.Org XInput driver : 18.0
[ 3.504] X.Org Server Extension : 7.0
[ 3.505] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 6.276] (--) PCI:*(0:0:2:0) 8086:0166:104d:90a5 rev 9, Mem @ 0xd7000000/4194304, 0xc0000000/268435456, I/O @ 0x00009000/64
[ 6.276] (II) Open ACPI successful (/var/run/acpid.socket)
[ 6.276] Initializing built-in extension Generic Event Extension
[ 6.276] Initializing built-in extension SHAPE
[ 6.276] Initializing built-in extension MIT-SHM
[ 6.276] Initializing built-in extension XInputExtension
[ 6.276] Initializing built-in extension XTEST
[ 6.276] Initializing built-in extension BIG-REQUESTS
[ 6.276] Initializing built-in extension SYNC
[ 6.276] Initializing built-in extension XKEYBOARD
[ 6.276] Initializing built-in extension XC-MISC
[ 6.276] Initializing built-in extension SECURITY
[ 6.276] Initializing built-in extension XINERAMA
[ 6.276] Initializing built-in extension XFIXES
[ 6.276] Initializing built-in extension RENDER
[ 6.276] Initializing built-in extension RANDR
[ 6.276] Initializing built-in extension COMPOSITE
[ 6.276] Initializing built-in extension DAMAGE
[ 6.276] Initializing built-in extension MIT-SCREEN-SAVER
[ 6.276] Initializing built-in extension DOUBLE-BUFFER
[ 6.276] Initializing built-in extension RECORD
[ 6.276] Initializing built-in extension DPMS
[ 6.276] Initializing built-in extension X-Resource
[ 6.276] Initializing built-in extension XVideo
[ 6.276] Initializing built-in extension XVideo-MotionCompensation
[ 6.276] Initializing built-in extension XFree86-VidModeExtension
[ 6.276] Initializing built-in extension XFree86-DGA
[ 6.276] Initializing built-in extension XFree86-DRI
[ 6.276] Initializing built-in extension DRI2
[ 6.276] (II) LoadModule: "glx"
[ 6.278] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.281] (II) Module glx: vendor="X.Org Foundation"
[ 6.281] compiled for 1.13.0, module version = 1.0.0
[ 6.281] ABI class: X.Org Server Extension, version 7.0
[ 6.281] (==) AIGLX enabled
[ 6.281] Loading extension GLX
[ 6.281] (II) LoadModule: "intel"
[ 6.281] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 6.285] (II) Module intel: vendor="X.Org Foundation"
[ 6.285] compiled for 1.13.0.901, module version = 2.20.14
[ 6.285] Module class: X.Org Video Driver
[ 6.285] ABI class: X.Org Video Driver, version 13.1
[ 6.285] (II) intel: Driver for Intel 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, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
ValleyView PO board
[ 6.286] (++) using VT number 7
[ 6.288] (II) intel(0): using device path '/dev/dri/card0'
[ 6.288] (**) intel(0): Depth 24, (--) framebuffer bpp 32
[ 6.288] (==) intel(0): RGB weight 888
[ 6.288] (==) intel(0): Default visual is TrueColor
[ 6.288] (**) intel(0): Option "AccelMethod" "sna"
[ 6.288] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 6.289] (**) intel(0): Framebuffer tiled
[ 6.289] (**) intel(0): Pixmaps tiled
[ 6.289] (**) intel(0): 3D buffers tiled
[ 6.289] (**) intel(0): Throttling enabled
[ 6.289] (**) intel(0): Delayed flush enabled
[ 6.289] (**) intel(0): "Tear free" disabled
[ 6.289] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 6.289] (II) intel(0): Output eDP1 using monitor section eDP1
[ 6.289] (**) intel(0): Option "PreferredMode" "1920x1080"
[ 6.289] (**) intel(0): Option "Position" "1920 0"
[ 6.289] (**) intel(0): Option "Primary" "true"
[ 6.289] (--) intel(0): found backlight control interface acpi_video0 (type 'firmware')
[ 6.293] (II) intel(0): Output VGA1 using monitor section VGA1
[ 6.293] (**) intel(0): Option "PreferredMode" "1920x1200_60.00"
[ 6.294] (II) intel(0): Output HDMI1 has no monitor section
[ 6.336] (II) intel(0): Output DP1 has no monitor section
[ 6.337] (II) intel(0): EDID for output eDP1
[ 6.337] (II) intel(0): Manufacturer: MS_ Model: 25 Serial#: 16843009
[ 6.337] (II) intel(0): Year: 2012 Week: 24
[ 6.337] (II) intel(0): EDID Version: 1.4
[ 6.337] (II) intel(0): Digital Display Input
[ 6.337] (II) intel(0): 8 bits per channel
[ 6.337] (II) intel(0): Digital interface is DisplayPort
[ 6.337] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
[ 6.337] (II) intel(0): Gamma: 2.20
[ 6.337] (II) intel(0): No DPMS capabilities specified
[ 6.337] (II) intel(0): Supported color encodings: RGB 4:4:4
[ 6.337] (II) intel(0): First detailed timing is preferred mode
[ 6.337] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 6.337] (II) intel(0): redX: 0.602 redY: 0.336 greenX: 0.296 greenY: 0.546
[ 6.337] (II) intel(0): blueX: 0.148 blueY: 0.126 whiteX: 0.313 whiteY: 0.329
[ 6.337] (II) intel(0): Manufacturer's mask: 0
[ 6.337] (II) intel(0): Supported standard timings:
[ 6.337] (II) intel(0): #0: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 6.337] (II) intel(0): Supported detailed timing:
[ 6.337] (II) intel(0): clock: 162.8 MHz Image Size: 291 x 164 mm
[ 6.337] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1984 h_blank_end 2481 h_border: 0
[ 6.337] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1086 v_blanking: 1095 v_border: 0
[ 6.337] (II) intel(0): Supported detailed timing:
[ 6.337] (II) intel(0): clock: 99.9 MHz Image Size: 291 x 164 mm
[ 6.337] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1984 h_blank_end 2281 h_border: 0
[ 6.337] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1086 v_blanking: 1095 v_border: 0
[ 6.337] (II) intel(0): Monitor name: Sony LCD
[ 6.337] (II) intel(0): Ranges: V min: 39 V max: 61 Hz, H min: 43 H max: 66 kHz, PixClock max 175 MHz
[ 6.337] (II) intel(0): EDID (in hex):
[ 6.337] (II) intel(0): 00ffffffffffff00367f250001010101
[ 6.337] (II) intel(0): 18160104a51d1078020f159a564b8b26
[ 6.337] (II) intel(0): 205054000000d1c00101010101010101
[ 6.337] (II) intel(0): 0101010101019c3f803172380f402020
[ 6.337] (II) intel(0): 330023a4100000180727806971380f40
[ 6.337] (II) intel(0): 2020330023a410000018000000fc0053
[ 6.337] (II) intel(0): 6f6e79204c43440a20202020000000fd
[ 6.337] (II) intel(0): 00273d2b4211000a2020202020200013
[ 6.337] (II) intel(0): EDID vendor "MS_", prod id 37
[ 6.337] (II) intel(0): Using EDID range info for horizontal sync
[ 6.337] (II) intel(0): Using EDID range info for vertical refresh
[ 6.337] (II) intel(0): Printing DDC gathered Modelines:
[ 6.337] (II) intel(0): Modeline "1920x1080"x0.0 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz eP)
[ 6.337] (II) intel(0): Modeline "1920x1080"x0.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 6.337] (II) intel(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 6.337] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 6.337] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 6.337] (II) intel(0): Printing probed modes for output eDP1
[ 6.337] (II) intel(0): Modeline "1920x1080"x59.9 162.84 1920 1952 1984 2481 1080 1083 1086 1095 -hsync -vsync (65.6 kHz UeP)
[ 6.337] (II) intel(0): Modeline "1920x1080"x40.0 99.91 1920 1952 1984 2281 1080 1083 1086 1095 -hsync -vsync (43.8 kHz e)
[ 6.338] (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 6.338] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
[ 6.338] (II) intel(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 6.338] (II) intel(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 6.338] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 6.338] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 6.338] (II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 6.338] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 6.338] (II) intel(0): Modeline "1366x768"x60.0 85.89 1366 1439 1583 1800 768 769 772 795 -hsync +vsync (47.7 kHz)
[ 6.338] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 6.338] (II) intel(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 6.338] (II) intel(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 6.338] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 6.338] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 6.338] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 6.338] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 6.343] (II) intel(0): EDID for output VGA1
[ 6.343] (II) intel(0): Printing probed modes for output VGA1
[ 6.343] (II) intel(0): Modeline "1920x1200_60.00"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz UP)
[ 6.343] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 6.344] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 6.344] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 6.344] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 6.344] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 6.344] (II) intel(0): EDID for output HDMI1
[ 6.386] (II) intel(0): EDID for output DP1
[ 6.386] (II) intel(0): Output eDP1 connected
[ 6.386] (II) intel(0): Output VGA1 connected
[ 6.386] (II) intel(0): Output HDMI1 disconnected
[ 6.386] (II) intel(0): Output DP1 disconnected
[ 6.386] (II) intel(0): Using user preference for initial modes
[ 6.386] (II) intel(0): Output eDP1 using initial mode 1920x1080
[ 6.386] (II) intel(0): Output VGA1 using initial mode 1920x1200_60.00
[ 6.386] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 6.386] (**) intel(0): Display dimensions: (290, 160) mm
[ 6.386] (**) intel(0): DPI set to (336, 190)
[ 6.386] (II) Loading sub module "dri2"
[ 6.386] (II) LoadModule: "dri2"
[ 6.387] (II) Module "dri2" already built-in
[ 6.387] (==) Depth 24 pixmap format is 32 bpp
[ 6.387] (II) intel(0): SNA initialized with IvyBridge backend
[ 6.387] (==) intel(0): Backing store disabled
[ 6.387] (==) intel(0): Silken mouse enabled
[ 6.387] (II) intel(0): HW Cursor enabled
[ 6.387] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 6.388] (==) intel(0): DPMS enabled
[ 6.388] (II) intel(0): [DRI2] Setup complete
[ 6.388] (II) intel(0): [DRI2] DRI driver: i965
[ 6.388] (II) intel(0): direct rendering: DRI2 Enabled
[ 6.388] (WW) intel(0): Option "PreferredMode" is not used
[ 6.388] (WW) intel(0): Option "Primary" is not used
[ 6.388] (WW) intel(0): Option "Position" is not used
[ 6.388] (==) intel(0): hotplug detection: "enabled"
[ 6.388] (--) RandR disabled
[ 6.410] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 6.410] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 6.410] (II) AIGLX: enabled GLX_ARB_create_context
[ 6.410] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 6.410] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 6.410] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 6.410] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 6.410] (II) AIGLX: Loaded and initialized i965
[ 6.410] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 6.411] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
[ 6.500] (II) intel(0): switch to mode 1920x1200 on crtc 5 (pipe 1)
[ 6.663] (II) intel(0): Setting screen physical size to 1016 x 317
[ 6.703] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[ 6.703] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 6.703] (II) LoadModule: "evdev"
[ 6.704] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.706] (II) Module evdev: vendor="X.Org Foundation"
[ 6.706] compiled for 1.13.0, module version = 2.7.3
[ 6.706] Module class: X.Org XInput Driver
[ 6.706] ABI class: X.Org XInput driver, version 18.0
[ 6.706] (II) Using input driver 'evdev' for 'Video Bus'
[ 6.706] (**) Video Bus: always reports core events
[ 6.706] (**) evdev: Video Bus: Device: "/dev/input/event10"
[ 6.706] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 6.706] (--) evdev: Video Bus: Found keys
[ 6.706] (II) evdev: Video Bus: Configuring as keyboard
[ 6.706] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:09/input/input10/event10"
[ 6.706] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 6.706] (**) Option "xkb_rules" "evdev"
[ 6.706] (**) Option "xkb_model" "evdev"
[ 6.706] (**) Option "xkb_layout" "us"
[ 6.732] (II) config/udev: Adding input device Sony Vaio Keys (/dev/input/event3)
[ 6.732] (**) Sony Vaio Keys: Applying InputClass "evdev keyboard catchall"
[ 6.732] (II) Using input driver 'evdev' for 'Sony Vaio Keys'
[ 6.732] (**) Sony Vaio Keys: always reports core events
[ 6.732] (**) evdev: Sony Vaio Keys: Device: "/dev/input/event3"
[ 6.732] (--) evdev: Sony Vaio Keys: Vendor 0x104d Product 0
[ 6.732] (--) evdev: Sony Vaio Keys: Found keys
[ 6.732] (II) evdev: Sony Vaio Keys: Configuring as keyboard
[ 6.732] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/SNY5001:00/input/input3/event3"
[ 6.732] (II) XINPUT: Adding extended input device "Sony Vaio Keys" (type: KEYBOARD, id 7)
[ 6.732] (**) Option "xkb_rules" "evdev"
[ 6.732] (**) Option "xkb_model" "evdev"
[ 6.732] (**) Option "xkb_layout" "us"
[ 6.732] (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/event4)
[ 6.732] (II) No input driver specified, ignoring this device.
[ 6.732] (II) This device may have been added with another device file.
[ 6.733] (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/mouse0)
[ 6.733] (II) No input driver specified, ignoring this device.
[ 6.733] (II) This device may have been added with another device file.
[ 6.733] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 6.733] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.733] (II) Using input driver 'evdev' for 'Power Button'
[ 6.733] (**) Power Button: always reports core events
[ 6.733] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 6.733] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.733] (--) evdev: PowerHave you ever tried 'arandr'? It's a GUI for xrandr; it could be useful.
I used this config with nouveau, now I've successfully created my xorg.conf with nvidia blobs, but this one worked~
Section "Device"
Identifier "NVIDIA GeForce GT320"
Driver "nouveau"
Option "Monitor-DVI-I-1" "BENQ G2450"
Option "Monitor-HDMI-1" "LG W2442PA"
EndSection
Section "Monitor"
Identifier "BENQ G2450"
Option "Primary" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
Option "Position" "1080 612"
EndSection
Section "Monitor"
Identifier "LG W2442PA"
Option "LeftOf" "BENQ G2450"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "59.9"
Option "Position" "0 0"
Option "Rotate" "Left"
EndSection
Section "Screen"
Identifier "Primary Screen"
Device "NVIDIA GeForce GT320"
Monitor "BENQ G2450"
DefaultDepth 24
SubSection "Display"
Depth 24
Virtual 3000 1920
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Primary Screen"
EndSection
I'm using XFCE as well, 2 monitors, the left one rotated 90º. The main difference it's that I've the 'Virtual' option inside 'SubSection'; not sure if it's relevant.
Maybe you are looking for
-
Multiple Software Versions Question
Rookie question here. My organization recently purchased a new copy of InDesign CS6 for me and one other employee. We did NOT purchase Creative Cloud subscriptions, but hard copy licenses. The software is working great and we love your product. T
-
Itunes was not installed correctly please reinstall. :(
After upgrading itunes it says ' itunes was not installed corectly please reinstall so i uninstalled everything apple : bonjour apple application support , quicktime ....., than installed itunes again nothing ! same message i'v tried dowload microsof
-
Hi, so I was recently thinking about purchasing an Ipad Mini for like an entertainment movie luxury for my mother instead of using my Macbook. I know that you can purchase an lightning to VGA adapter so we could use this capability but the real quest
-
Problem in background session processing
Hi Experts, I am performing BDC by batch input session method. I acheved BDC by traditional recording method and able to create batch input session in SM35. Whenever I process batch input session in FOREGROUND it processes successfully.But whenever I
-
[solved] funcsave command fails in fish shell
When I define a function in fish like this: function heythere echo hey there from fish! end and issue the funcsave command, I get this error: troff: fatal error: can't open `/usr/share/fish/man/save_function.1': No such file or directory This de