Monitor LSMW

Hi All,
Can any please let me know how to check/monitor data upload and download that is carried out using LSMW, SM30?
Is there any log file for LSMW and SM30?
With Best Regards,
V.M

Hi,
Please check the following SAP Help Link:
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/frameset.htm
Goto txn LSMW -> Select Project-> Action Log
- Regards, Dibya

Similar Messages

HR data upload using LSMW

Hi All
I am using LSMW to upload the HR master data. The infotype data that is loaded include the basic infotypes like 0000, 0001, 0002, 0007, 0014 and 0019 (monitoring of tasks). I am using recording method. I can record all infotypes till 0014 in single shot and the recording gets saved at the end of 0014 and gets back to LSMW step. I need 0019 infotype recording also. For this what should I do? How should I record it? Can I record this individually and attach to the above recording? Please help.
Thanks
Shakir

Hi,
What we do during data convertion is creating each recording separately. I don't think the customer will provide you one data file with all ITs information. Providing he/she has to extract data from his/her system it is likely that you get separeted files. Pelase ensure it won't be this way.
Moreover this approach is less error-prone. Image that you are missing some configuration for one of the infotype, which is in the middle (lets say 4th in the row out of 10). Everything would load correctly till it reaches this "unlucky" infotype. Then the record has status of not loaded. The rest would be skipped and you have missing data. Now you need to start reloading from this wrong infotype to the end. But how about these already loaded? Would you delete the records to avoid duplicating?
That's why I am really encouraging you to take each IT separately approach. It is better to spend some time preparing data files then loosing your nerves when investingating what's in and what's not yet in the system, in case an error occurs.
Regards
Marcin

Bdc and lsmw

Hi All,
I am presuming that both bdc's and lsmw are being used for data migration. if this is right then when would someone prefer bdc over lsmw or vice versa. if my assumption is wrong then tell me for what specifications we use lsmw and for what specs we use a bdc.

Hi,
"The Data Transfer Workbench (or DX Workbench, transaction SXDA) is an integrated SAP tool that supports data transfer and analysis. It
does not have the built-in features for mapping for source structures to target structures, but it will allow you to integrate Legacy System Migration Workbench (LSMW) objects as processing tasks within a run definition. The DX workbench has many features for creating
test data and performing data migrations - for example, logging of data migration runs.
However, if you need to map or convert data, you should use the LSMW. Or, you can integrate
your LSMW objects as task within a more user-friendly data migration run, in which the LSMW
project steps "Read data", "Convert data," and "Start IDoc processing" are automated
and use the features of both tools. If you donot need logging and automated data migration
runs, you can perform your data migration without the DX Workbench."
The following was taken at this site :
http://www.info-sun.com/docs/wp_sapinter.pdf
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form
of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The
transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP
program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using
Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the
BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and
invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate
fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are
not available for all application areas.
Remote Function Call (RFC) in SAP R/3 is based on UNIXs Remote Procedure Call (RPC). RFC enables the real-time link between different R/3 instances and can connect SAP to Non-SAP systems. With Remote Function Call, both inbound (RFCServer) and outbound (RFCClient) interfaces are possible.
SAP also provides a toolkit called RFC API for non-SAP systems to interact with SAPs Function modules remotely.
RFC is a very powerful tool for interfacing with SAP system in real time. Most other interfacing techniques like ALE, EDI, BAPI etc are
inherently based on the RFC technology.
Electronic Data Interchange (EDI) is the industry standard format for exchanging Business data. SAP uses a neutral format called Intermediate Document
(IDoc) for communicating EDI & ALE messages.
The IDoc interface contains data structures and processing logic for each of the business transaction. These are grouped as Message
Types. The external EDI Server is responsible for receiving the EDI messages sent by the trading partners. These EDI messages are then
mapped onto the IDoc structure fields and stored in the IDoc interface layer by SAP.
EDI/IDoc supports both inbound and outbound interfaces. The IDocs received through the EDI Server can be configured to automatically get
processed, or can be stored in the IDoc interface layer for a future manual or scheduled processing. The IDoc interface layer also has a powerful error
handling, reporting, monitoring and reprocessingmechanism built into it (Transaction WEDI). IDoc is also tightly integrated with the WorkFlow system
of SAP for initiating other business tasks upon receiving/sending EDI messages.
The IDoc interface can be employed for non-SAP applications to load or extract data from SAP system. But typically, EDI / IDoc is engaged when
SAP system is to be integrated with any of its business partners (Customers, Suppliers and other partners) for carrying out standard business
transactions (like Create Sales orders, Sending Purchase orders to Suppliers, etc).
Application Link Enabling (ALE) is a middleware tool, which is part of SAPs Business framework Architecture (BFA). ALE can effectively be used
for loosely coupled Asynchronous communication between SAP systems and with non-SAP systems. ALE is based on the distributed processing
architecture and hence integrates applications with the local database rather than centralized one. ALE messages are based on the Intermediate
Document (IDoc) format, similar to the EDI counterpart. Though ALE can be used to interface with non-SAP systems, usually it is used to
distribute Master & Transactional data between SAP R/3 instances.
The ALE distribution can be based on,
Business APIs
IDoc Message Types"
Business API (BAPI) is the most important component of SAP Business Framework. BAPI enables SAP and third party applications to interact and integrate
with each other at the Business Object / Process level.

LSMW for IP30 possible or not

Hi all,
I am successful in LSMW for all my requirement, but I am trying to have LSMW recording for IP30 (deadline monitoring), i am not successful, as in this case, the Execute button is clicked before the recording. Execute button is not recognising in the recording, I am struck here.
Kindly let us know whether LSMW is possible for IP30 or not. Pl help.
Thanx in advance
regards
srihari

Hi,
IP 30 is it self a Back ground job for Scheduling the Maintenance Plan.Use SM35 Create the Batch job by mantaining the Variant Name,ABap Programme-RISTRA20,Language--EN.Then maintain the Batch Job start date and Time.system automaticaly perform schduling.No NEED FOR LSMW RECORDING for this.
If you want LSMW any how for Schduling of Maintenace Plan Then Create The LSMW Object for Transction Code--IP10 it will work
Regards,
Rakesh
Edited by: RAKESH ASHOK MANE on Sep 3, 2010 1:48 PM

LSMW techniques

Can some one tell me the advantages and disadvantages; and when shall we use
the Direct Input, Batch input recording, BAPI, and IDoc techniques in LSMW workbench...any doumentation will be of great help. eg. why should we choose Direct Input as opposed to Batch Input recording and so on..
Thanks a lot. Will award points
Arianne

LSMW : An SAP system tool that supports one-time and periodic data transfers from external systems to SAP R/3 systems.
The Legacy System Migration Workbench facilitates the conversion of data to the necessary format.
Technologies supported include Batch Input, Call Transaction, Direct Input, BAPIs, and EDI.
Batch Input : A data transfer technology that enables the transfer of large volumes of data to an SAP System using the online transaction.
A batch input session is created for this purpose which you can then process using the Batch Input Monitor.
Call Transaction : A data transfer technology similar to batch input that allows large amounts of data to be transferred to a SAP System using the online transaction.
No batch input folder is generated. Instead, the data is posted directly using the online transaction.
Direct Input :A data transfer technology that uses function modules created for this purpose by SAP to transfer very large volumes of data to an SAP System.
The same consistency checks are performed within the function modules as those performed in the online transaction.
Direct input has definite performance advantages when compared to the batch input and call transaction technologies because no online transaction has been performed here.
Business Application Progarmming Interface(BAPIs) : A standardized programming interface that facilitates external access to business processes and data in the SAP System.
You define Business Application Programming Interfaces (BAPIs) in the Business Object Repository (BOR) as methods of SAP business objects or SAP interface types.
BAPIs offer an object-oriented view of business components in the SAP System. They are implemented and stored as RFC-enabled function modules in the Function Builder of the ABAP Workbench.
Electronic Data Interchange : Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.

LSMW - Very Slow

Hi All
We are using LSMW to update function locations in SAP PM using LSMW and Batch Input Sessions,
When we upload the data using tx LSMW we are updating at approx 3 records per minute.
The file that needs to be uploaded has approx 53 000 records, hence it would take days to upload this and furthermore we have another 9 files of similar size to upload using LSMW.
We have also switched off table logging (rec/client=ALL) and switch off archive logging to enhance performance.
CPU's are 99 -100 % idle, no paging, memory is 20 out 32GB beig used, basically the system is performing the way it is supposed to but the uploads via LSMW are way to slow.
Are there any more Basis Settings that we can probably tweak / change / edit to get more performance on the LSMW uploads to run quicker.
Please help, we are on ERP 6.0, Oracle, and Solaris using LSMW Version 4.0.0
Thanks
Solly

Hello All
Thanks for all the advice, Mark was right, check the stats out and we found that the bottleneck was the database.
The LSMW runs have a V2 update component to as well as using the normal update work processes, additionally we done a db update stats and swtiched to a very heavy batch, update and update2 type operation mode, reducing dialog processes at the same time.
We then ran in parallel alot of lsmw jobs and monitored it closely while extending tablespaces etc,
We are currently processing about +- 175 records a minute which roughly translates up to max 2 records a second.
System idle is averaging around 96% and peaking at 92% idle.
We are already 70% done with the uploads and are predicting to be done in the next 3 days.
We are also running this on the QA instance, the production instance is an M4000 so we are expecting better throughput.
We think this is acceptable for us, do you guys have any similar stats that we could compare against.
I am sure with alot more tweaking especially in the oracle shared mem etc we could better throughput.
Thanks
Suleman

Sample Exercises in LSMW

Hello Everyone,
Can you be so kind to give me sample exercises in IDOC using BAPI, IDOC or Standard Batch Input? I am only familiar with Batch Input Recording in LSMW.
Please help me to learn the other methods in LSMW.
Thanks,
Louisse

Hi,
BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.
BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.
BAPI is a Remote enabled function module.
Just follow this simple procedure or steps to create a BAPI.
1. Defining BAPI Data structures in SE11
2. Program a RFC enabled BAPI function module for each method
3. Create a Business object for the BAPI in the BOR
4. Documentation the BAPI
5. Generate ALE interface for asynchronous BAPIs
6. Generate and release
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
with regards,
sowjanya.gosala.

Logical filename and logical path in lsmw

Hi all,
I am doing a lsmw for purchasing info record . i created a logicalpath and assigned a physical path to that . i created a logical filename and assigned the logical path .but when i assign that to the lsmw it is throwing error as 'LOGICAL PATH DOES NOT POINT TO PHYSICAL DIRECTORY' .
can anybody provide a solution for that .
Thanks & regards
Magesh anandan

hi ,
goto the tcode file then u find the relation between the logical and physical paths ...and their assignment..
hope it will helps u..
regards,
venkat.

Issues with using 3 monitors on 2 external gpu

Hi,
I have some issues with configuring Xorg to use 3 monitors. I have 2 external graphic cards (same model, no SLI). Monitors connected to the first gpu are recognized ok but I can't configure my 3rd monitor conencted to the second gpu via HDMI nor DVI.
1st is recognized as DVI-I-1, 2nd is DP-1 in first card, 3rd monitor is in second card (bus 22:00.0) as DP-1-2 (also tried connecting as DVI-I-2). I can see them in Xorg log but I can't configure my 3rd monitor via kscreen nor xrandr. :-/
lspci |grep VGA:
03:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1)
22:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1)
xrandr:
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
DVI-I-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 297mm
1920x1080 60.0*+
1600x900 60.0
1280x1024 75.0 60.0
1152x864 75.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
DP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 297mm
1920x1080 60.0*+
1600x900 60.0
1280x1024 75.0 60.0
1152x864 75.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
Xorg config (autoconfig enable only 2 monitors, I generated config and tried to edit it with no luck, I noticed there is PCI:34:0:0 generated by Xorg so I also tried to change it to 22:0:0, I also tried to add that option "Monitor-<output>" but same result):
Section "ServerLayout"
Identifier "X.org Configured"
#Screen 0 "Screen0" 0 0
#Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "DELL"
Option "Monitor-DVI-I-1" "DVI-I-1"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "DELL"
Option "Monitor-DP-1" "DP-1"
EndSection
Section "Monitor"
Identifier "Monitor2"
VendorName "DELL"
Option "Monitor-DP-1-2" "DP-1-2"
EndSection
Section "Device"
Identifier "Card0"
Driver "nouveau"
BusID "PCI:3:0:0"
Option "Monitor-DVI-I-1"
Option "Monitor-DP-1"
EndSection
Section "Device"
Identifier "Card1"
Driver "nouveau"
BusID "PCI:34:0:0"
Option "Monitor-DP-1-2"
EndSection
Xorg log (I can see that monitor at time 1767.316):
[ 1766.959]
X.Org X Server 1.14.5
Release Date: 2013-12-12
[ 1766.960] X Protocol Version 11, Revision 0
[ 1766.960] Build Operating System: Linux 3.12.5-1-ARCH x86_64
[ 1766.960] Current Operating System: Linux CZ09DT1XM5002 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64
[ 1766.960] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=e2c593e5-b0f4-4c74-84fd-5a88db345ca4 rw quiet
[ 1766.961] Build Date: 13 December 2013 03:11:42PM
[ 1766.962]
[ 1766.962] Current version of pixman: 0.32.4
[ 1766.963] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 1766.963] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1766.965] (==) Log file: "/var/log/Xorg.1.log", Time: Thu Jan 2 12:43:56 2014
[ 1766.965] (++) Using config file: "/etc/X11/xorg.conf.d/20-multimonitor.conf"
[ 1766.966] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 1766.966] (==) ServerLayout "X.org Configured"
[ 1766.966] (==) No screen section available. Using defaults.
[ 1766.966] (**) |-->Screen "Default Screen Section" (0)
[ 1766.966] (**) | |-->Monitor "<default monitor>"
[ 1766.966] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 1766.966] (**) | |-->Device "Card0"
[ 1766.966] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 1766.966] (**) |-->Input Device "Mouse0"
[ 1766.966] (**) |-->Input Device "Keyboard0"
[ 1766.966] (==) Automatically adding devices
[ 1766.966] (==) Automatically enabling devices
[ 1766.966] (==) Automatically adding GPU devices
[ 1766.966] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1766.966] Entry deleted from font path.
[ 1766.966] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1766.966] Entry deleted from font path.
[ 1766.966] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1766.966] Entry deleted from font path.
[ 1766.966] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 1766.967] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1766.967] Entry deleted from font path.
[ 1766.967] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 1766.967] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1766.967] Entry deleted from font path.
[ 1766.967] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1766.967] Entry deleted from font path.
[ 1766.967] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1766.967] Entry deleted from font path.
[ 1766.967] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 1766.967] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1766.967] Entry deleted from font path.
[ 1766.967] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 1766.967] (**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 1766.967] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 1766.967] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 1766.967] (WW) Disabling Mouse0
[ 1766.967] (WW) Disabling Keyboard0
[ 1766.967] (II) Loader magic: 0x7fec20
[ 1766.967] (II) Module ABI versions:
[ 1766.967] X.Org ANSI C Emulation: 0.4
[ 1766.967] X.Org Video Driver: 14.1
[ 1766.967] X.Org XInput driver : 19.1
[ 1766.967] X.Org Server Extension : 7.0
[ 1766.967] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 1766.967] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 1767.169] (--) PCI:*(0:3:0:0) 10de:0df8:10de:0835 rev 161, Mem @ 0xc6000000/16777216, 0xc8000000/134217728, 0xd0000000/33554432, I/O @ 0x00007000/128, BIOS @ 0x????????/524288
[ 1767.169] (--) PCI: (0:34:0:0) 10de:0df8:10de:0835 rev 161, Mem @ 0xfa000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288
[ 1767.169] Initializing built-in extension Generic Event Extension
[ 1767.170] Initializing built-in extension SHAPE
[ 1767.170] Initializing built-in extension MIT-SHM
[ 1767.170] Initializing built-in extension XInputExtension
[ 1767.171] Initializing built-in extension XTEST
[ 1767.171] Initializing built-in extension BIG-REQUESTS
[ 1767.172] Initializing built-in extension SYNC
[ 1767.172] Initializing built-in extension XKEYBOARD
[ 1767.172] Initializing built-in extension XC-MISC
[ 1767.173] Initializing built-in extension SECURITY
[ 1767.173] Initializing built-in extension XINERAMA
[ 1767.174] Initializing built-in extension XFIXES
[ 1767.174] Initializing built-in extension RENDER
[ 1767.174] Initializing built-in extension RANDR
[ 1767.175] Initializing built-in extension COMPOSITE
[ 1767.175] Initializing built-in extension DAMAGE
[ 1767.175] Initializing built-in extension MIT-SCREEN-SAVER
[ 1767.176] Initializing built-in extension DOUBLE-BUFFER
[ 1767.176] Initializing built-in extension RECORD
[ 1767.176] Initializing built-in extension DPMS
[ 1767.177] Initializing built-in extension X-Resource
[ 1767.177] Initializing built-in extension XVideo
[ 1767.177] Initializing built-in extension XVideo-MotionCompensation
[ 1767.178] Initializing built-in extension XFree86-VidModeExtension
[ 1767.178] Initializing built-in extension XFree86-DGA
[ 1767.178] Initializing built-in extension XFree86-DRI
[ 1767.179] Initializing built-in extension DRI2
[ 1767.179] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 1767.179] (II) LoadModule: "glx"
[ 1767.179] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1767.179] (II) Module glx: vendor="X.Org Foundation"
[ 1767.179] compiled for 1.14.5, module version = 1.0.0
[ 1767.179] ABI class: X.Org Server Extension, version 7.0
[ 1767.179] (==) AIGLX enabled
[ 1767.180] Loading extension GLX
[ 1767.180] (II) LoadModule: "nouveau"
[ 1767.180] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 1767.180] (II) Module nouveau: vendor="X.Org Foundation"
[ 1767.180] compiled for 1.14.4, module version = 1.0.10
[ 1767.180] Module class: X.Org Video Driver
[ 1767.180] ABI class: X.Org Video Driver, version 14.1
[ 1767.180] (II) NOUVEAU driver
[ 1767.180] (II) NOUVEAU driver for NVIDIA chipset families :
[ 1767.180] RIVA TNT (NV04)
[ 1767.180] RIVA TNT2 (NV05)
[ 1767.180] GeForce 256 (NV10)
[ 1767.180] GeForce 2 (NV11, NV15)
[ 1767.180] GeForce 4MX (NV17, NV18)
[ 1767.180] GeForce 3 (NV20)
[ 1767.180] GeForce 4Ti (NV25, NV28)
[ 1767.180] GeForce FX (NV3x)
[ 1767.180] GeForce 6 (NV4x)
[ 1767.180] GeForce 7 (G7x)
[ 1767.180] GeForce 8 (G8x)
[ 1767.180] GeForce GTX 200 (NVA0)
[ 1767.180] GeForce GTX 400 (NVC0)
[ 1767.180] (--) using VT number 3
[ 1767.182] (II) [drm] nouveau interface version: 1.1.1
[ 1767.183] (II) [drm] nouveau interface version: 1.1.1
[ 1767.183] (II) Loading sub module "dri2"
[ 1767.183] (II) LoadModule: "dri2"
[ 1767.183] (II) Module "dri2" already built-in
[ 1767.183] (--) NOUVEAU(0): Chipset: "NVIDIA NVC1"
[ 1767.183] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 1767.183] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 1767.183] (==) NOUVEAU(0): RGB weight 888
[ 1767.183] (==) NOUVEAU(0): Default visual is TrueColor
[ 1767.183] (==) NOUVEAU(0): Using HW cursor
[ 1767.183] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 1767.183] (==) NOUVEAU(0): Page flipping enabled
[ 1767.183] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 1767.222] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[ 1767.230] (II) NOUVEAU(0): Output DP-1 has no monitor section
[ 1767.265] (II) NOUVEAU(0): EDID for output DVI-I-1
[ 1767.265] (II) NOUVEAU(0): Manufacturer: DEL Model: a09b Serial#: 827608652
[ 1767.265] (II) NOUVEAU(0): Year: 2013 Week: 41
[ 1767.265] (II) NOUVEAU(0): EDID Version: 1.3
[ 1767.265] (II) NOUVEAU(0): Digital Display Input
[ 1767.265] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 53 vert.: 30
[ 1767.265] (II) NOUVEAU(0): Gamma: 2.20
[ 1767.265] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off
[ 1767.265] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 1767.265] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 1767.265] (II) NOUVEAU(0): redX: 0.650 redY: 0.338 greenX: 0.320 greenY: 0.613
[ 1767.265] (II) NOUVEAU(0): blueX: 0.154 blueY: 0.061 whiteX: 0.313 whiteY: 0.329
[ 1767.265] (II) NOUVEAU(0): Supported established timings:
[ 1767.265] (II) NOUVEAU(0): 720x400@70Hz
[ 1767.265] (II) NOUVEAU(0): 640x480@60Hz
[ 1767.265] (II) NOUVEAU(0): 640x480@75Hz
[ 1767.265] (II) NOUVEAU(0): 800x600@60Hz
[ 1767.265] (II) NOUVEAU(0): 800x600@75Hz
[ 1767.265] (II) NOUVEAU(0): 1024x768@60Hz
[ 1767.265] (II) NOUVEAU(0): 1024x768@75Hz
[ 1767.265] (II) NOUVEAU(0): 1280x1024@75Hz
[ 1767.265] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 1767.265] (II) NOUVEAU(0): Supported standard timings:
[ 1767.265] (II) NOUVEAU(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 1767.265] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 1767.265] (II) NOUVEAU(0): #2: hsize: 1600 vsize 900 refresh: 60 vid: 49321
[ 1767.265] (II) NOUVEAU(0): #3: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 1767.265] (II) NOUVEAU(0): Supported detailed timing:
[ 1767.265] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 527 x 297 mm
[ 1767.265] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 1767.265] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 1767.265] (II) NOUVEAU(0): Serial No: 36WJX3A91TNL
[ 1767.265] (II) NOUVEAU(0): Monitor name: DELL P2414H
[ 1767.265] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
[ 1767.265] (II) NOUVEAU(0): EDID (in hex):
[ 1767.265] (II) NOUVEAU(0): 00ffffffffffff0010ac9ba04c4e5431
[ 1767.265] (II) NOUVEAU(0): 2917010380351e78eaa0a5a656529d27
[ 1767.265] (II) NOUVEAU(0): 0f5054a54b00714f8180a9c0d1c00101
[ 1767.265] (II) NOUVEAU(0): 010101010101023a801871382d40582c
[ 1767.265] (II) NOUVEAU(0): 45000f292100001e000000ff00333657
[ 1767.265] (II) NOUVEAU(0): 4a5833413931544e4c0a000000fc0044
[ 1767.265] (II) NOUVEAU(0): 454c4c205032343134480a20000000fd
[ 1767.265] (II) NOUVEAU(0): 00384c1e5311000a20202020202000c2
[ 1767.265] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
[ 1767.265] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 1767.265] (II) NOUVEAU(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 1767.265] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1767.265] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 1767.273] (II) NOUVEAU(0): EDID for output DP-1
[ 1767.273] (II) NOUVEAU(0): Manufacturer: DEL Model: a09a Serial#: 844123724
[ 1767.273] (II) NOUVEAU(0): Year: 2013 Week: 41
[ 1767.273] (II) NOUVEAU(0): EDID Version: 1.4
[ 1767.273] (II) NOUVEAU(0): Digital Display Input
[ 1767.273] (II) NOUVEAU(0): 8 bits per channel
[ 1767.273] (II) NOUVEAU(0): Digital interface is DisplayPort
[ 1767.273] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 53 vert.: 30
[ 1767.273] (II) NOUVEAU(0): Gamma: 2.20
[ 1767.273] (II) NOUVEAU(0): DPMS capabilities: Off
[ 1767.273] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
[ 1767.273] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 1767.273] (II) NOUVEAU(0): Preferred mode is native pixel format and refresh rate
[ 1767.273] (II) NOUVEAU(0): redX: 0.650 redY: 0.338 greenX: 0.320 greenY: 0.613
[ 1767.273] (II) NOUVEAU(0): blueX: 0.154 blueY: 0.061 whiteX: 0.313 whiteY: 0.329
[ 1767.273] (II) NOUVEAU(0): Supported established timings:
[ 1767.273] (II) NOUVEAU(0): 720x400@70Hz
[ 1767.273] (II) NOUVEAU(0): 640x480@60Hz
[ 1767.273] (II) NOUVEAU(0): 640x480@75Hz
[ 1767.273] (II) NOUVEAU(0): 800x600@60Hz
[ 1767.273] (II) NOUVEAU(0): 800x600@75Hz
[ 1767.273] (II) NOUVEAU(0): 1024x768@60Hz
[ 1767.273] (II) NOUVEAU(0): 1024x768@75Hz
[ 1767.273] (II) NOUVEAU(0): 1280x1024@75Hz
[ 1767.273] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 1767.273] (II) NOUVEAU(0): Supported standard timings:
[ 1767.273] (II) NOUVEAU(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 1767.273] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 1767.273] (II) NOUVEAU(0): #2: hsize: 1600 vsize 900 refresh: 60 vid: 49321
[ 1767.273] (II) NOUVEAU(0): #3: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 1767.273] (II) NOUVEAU(0): Supported detailed timing:
[ 1767.273] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 527 x 297 mm
[ 1767.273] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 1767.273] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 1767.273] (II) NOUVEAU(0): Serial No: 36WJX3A92PNL
[ 1767.273] (II) NOUVEAU(0): Monitor name: DELL P2414H
[ 1767.273] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
[ 1767.273] (II) NOUVEAU(0): EDID (in hex):
[ 1767.273] (II) NOUVEAU(0): 00ffffffffffff0010ac9aa04c4e5032
[ 1767.273] (II) NOUVEAU(0): 29170104a5351e783aa0a5a656529d27
[ 1767.273] (II) NOUVEAU(0): 0f5054a54b00714f8180a9c0d1c00101
[ 1767.273] (II) NOUVEAU(0): 010101010101023a801871382d40582c
[ 1767.273] (II) NOUVEAU(0): 45000f292100001e000000ff00333657
[ 1767.273] (II) NOUVEAU(0): 4a5833413932504e4c0a000000fc0044
[ 1767.273] (II) NOUVEAU(0): 454c4c205032343134480a20000000fd
[ 1767.273] (II) NOUVEAU(0): 00384c1e5311000a2020202020200053
[ 1767.273] (II) NOUVEAU(0): Printing probed modes for output DP-1
[ 1767.273] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 1767.273] (II) NOUVEAU(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 1767.273] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1767.273] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 1767.273] (II) NOUVEAU(0): Output DVI-I-1 connected
[ 1767.273] (II) NOUVEAU(0): Output DP-1 connected
[ 1767.273] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 1767.273] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1080
[ 1767.273] (II) NOUVEAU(0): Output DP-1 using initial mode 1920x1080
[ 1767.273] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 1767.274] (--) NOUVEAU(0): Virtual size is 1920x1080 (pitch 0)
[ 1767.274] (**) NOUVEAU(0): Driver mode "1920x1080": 148.5 MHz (scaled from 0.0 MHz), 67.5 kHz, 60.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 1767.274] (**) NOUVEAU(0): Mode "1600x900": 119.0 MHz (scaled from 0.0 MHz), 55.9 kHz, 60.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 1767.274] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1767.274] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 1767.274] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 1767.274] (==) NOUVEAU(0): DPI set to (96, 96)
[ 1767.274] (II) Loading sub module "fb"
[ 1767.274] (II) LoadModule: "fb"
[ 1767.274] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1767.274] (II) Module fb: vendor="X.Org Foundation"
[ 1767.274] compiled for 1.14.5, module version = 1.0.0
[ 1767.274] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1767.274] (II) Loading sub module "exa"
[ 1767.274] (II) LoadModule: "exa"
[ 1767.274] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 1767.274] (II) Module exa: vendor="X.Org Foundation"
[ 1767.274] compiled for 1.14.5, module version = 2.6.0
[ 1767.274] ABI class: X.Org Video Driver, version 14.1
[ 1767.274] (II) Loading sub module "shadowfb"
[ 1767.274] (II) LoadModule: "shadowfb"
[ 1767.274] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 1767.274] (II) Module shadowfb: vendor="X.Org Foundation"
[ 1767.274] compiled for 1.14.5, module version = 1.0.0
[ 1767.274] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1767.274] (II) Loading sub module "dri2"
[ 1767.274] (II) LoadModule: "dri2"
[ 1767.274] (II) Module "dri2" already built-in
[ 1767.274] (--) NOUVEAU(G0): Chipset: "NVIDIA NVC1"
[ 1767.275] (==) NOUVEAU(G0): Depth 24, (--) framebuffer bpp 32
[ 1767.275] (==) NOUVEAU(G0): RGB weight 888
[ 1767.275] (==) NOUVEAU(G0): Default visual is TrueColor
[ 1767.275] (==) NOUVEAU(G0): Using HW cursor
[ 1767.275] (==) NOUVEAU(G0): GLX sync to VBlank disabled.
[ 1767.275] (==) NOUVEAU(G0): Page flipping enabled
[ 1767.275] (==) NOUVEAU(G0): Swap limit set to 2 [Max allowed 2]
[ 1767.308] (II) NOUVEAU(G0): Output DVI-I-1-2 has no monitor section
[ 1767.316] (II) NOUVEAU(G0): Output DP-1-2 has no monitor section
[ 1767.339] (II) NOUVEAU(G0): EDID for output DVI-I-1-2
[ 1767.347] (II) NOUVEAU(G0): EDID for output DP-1-2
[ 1767.347] (II) NOUVEAU(G0): Manufacturer: DEL Model: a09a Serial#: 844124236
[ 1767.347] (II) NOUVEAU(G0): Year: 2013 Week: 41
[ 1767.347] (II) NOUVEAU(G0): EDID Version: 1.4
[ 1767.347] (II) NOUVEAU(G0): Digital Display Input
[ 1767.347] (II) NOUVEAU(G0): 8 bits per channel
[ 1767.347] (II) NOUVEAU(G0): Digital interface is DisplayPort
[ 1767.347] (II) NOUVEAU(G0): Max Image Size [cm]: horiz.: 53 vert.: 30
[ 1767.347] (II) NOUVEAU(G0): Gamma: 2.20
[ 1767.347] (II) NOUVEAU(G0): DPMS capabilities: Off
[ 1767.347] (II) NOUVEAU(G0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
[ 1767.347] (II) NOUVEAU(G0): First detailed timing is preferred mode
[ 1767.347] (II) NOUVEAU(G0): Preferred mode is native pixel format and refresh rate
[ 1767.347] (II) NOUVEAU(G0): redX: 0.650 redY: 0.338 greenX: 0.320 greenY: 0.613
[ 1767.347] (II) NOUVEAU(G0): blueX: 0.154 blueY: 0.061 whiteX: 0.313 whiteY: 0.329
[ 1767.347] (II) NOUVEAU(G0): Supported established timings:
[ 1767.347] (II) NOUVEAU(G0): 720x400@70Hz
[ 1767.347] (II) NOUVEAU(G0): 640x480@60Hz
[ 1767.347] (II) NOUVEAU(G0): 640x480@75Hz
[ 1767.347] (II) NOUVEAU(G0): 800x600@60Hz
[ 1767.347] (II) NOUVEAU(G0): 800x600@75Hz
[ 1767.347] (II) NOUVEAU(G0): 1024x768@60Hz
[ 1767.347] (II) NOUVEAU(G0): 1024x768@75Hz
[ 1767.347] (II) NOUVEAU(G0): 1280x1024@75Hz
[ 1767.348] (II) NOUVEAU(G0): Manufacturer's mask: 0
[ 1767.348] (II) NOUVEAU(G0): Supported standard timings:
[ 1767.348] (II) NOUVEAU(G0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 1767.348] (II) NOUVEAU(G0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 1767.348] (II) NOUVEAU(G0): #2: hsize: 1600 vsize 900 refresh: 60 vid: 49321
[ 1767.348] (II) NOUVEAU(G0): #3: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 1767.348] (II) NOUVEAU(G0): Supported detailed timing:
[ 1767.348] (II) NOUVEAU(G0): clock: 148.5 MHz Image Size: 527 x 297 mm
[ 1767.348] (II) NOUVEAU(G0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 1767.348] (II) NOUVEAU(G0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 1767.348] (II) NOUVEAU(G0): Serial No: 36WJX3A92PPL
[ 1767.348] (II) NOUVEAU(G0): Monitor name: DELL P2414H
[ 1767.348] (II) NOUVEAU(G0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
[ 1767.348] (II) NOUVEAU(G0): EDID (in hex):
[ 1767.348] (II) NOUVEAU(G0): 00ffffffffffff0010ac9aa04c505032
[ 1767.348] (II) NOUVEAU(G0): 29170104a5351e783aa0a5a656529d27
[ 1767.348] (II) NOUVEAU(G0): 0f5054a54b00714f8180a9c0d1c00101
[ 1767.348] (II) NOUVEAU(G0): 010101010101023a801871382d40582c
[ 1767.348] (II) NOUVEAU(G0): 45000f292100001e000000ff00333657
[ 1767.348] (II) NOUVEAU(G0): 4a583341393250504c0a000000fc0044
[ 1767.348] (II) NOUVEAU(G0): 454c4c205032343134480a20000000fd
[ 1767.348] (II) NOUVEAU(G0): 00384c1e5311000a202020202020004f
[ 1767.348] (II) NOUVEAU(G0): Printing probed modes for output DP-1-2
[ 1767.348] (II) NOUVEAU(G0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 1767.348] (II) NOUVEAU(G0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
[ 1767.348] (II) NOUVEAU(G0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 1767.348] (II) NOUVEAU(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 1767.348] (--) NOUVEAU(G0): Virtual size is 1024x768 (pitch 0)
[ 1767.348] (**) NOUVEAU(G0): Mode "1920x1080": 173.0 MHz (scaled from 0.0 MHz), 67.2 kHz, 60.0 Hz
[ 1767.348] (II) NOUVEAU(G0): Modeline "1920x1080"x60.0 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync (67.2 kHz)
[ 1767.348] (==) NOUVEAU(G0): DPI set to (96, 96)
[ 1767.348] (II) Loading sub module "fb"
[ 1767.348] (II) LoadModule: "fb"
[ 1767.348] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1767.348] (II) Module fb: vendor="X.Org Foundation"
[ 1767.348] compiled for 1.14.5, module version = 1.0.0
[ 1767.348] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1767.348] (II) Loading sub module "exa"
[ 1767.348] (II) LoadModule: "exa"
[ 1767.348] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 1767.348] (II) Module exa: vendor="X.Org Foundation"
[ 1767.348] compiled for 1.14.5, module version = 2.6.0
[ 1767.348] ABI class: X.Org Video Driver, version 14.1
[ 1767.348] (II) Loading sub module "shadowfb"
[ 1767.348] (II) LoadModule: "shadowfb"
[ 1767.348] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 1767.348] (II) Module shadowfb: vendor="X.Org Foundation"
[ 1767.348] compiled for 1.14.5, module version = 1.0.0
[ 1767.348] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1767.348] (--) Depth 24 pixmap format is 32 bpp
[ 1767.351] (II) NOUVEAU(G0): Opened GPU channel 0
[ 1767.359] (II) NOUVEAU(G0): [DRI2] Setup complete
[ 1767.359] (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
[ 1767.359] (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
[ 1767.360] (II) EXA(256): Driver allocated offscreen pixmaps
[ 1767.360] (II) EXA(256): Driver registered support for the following operations:
[ 1767.360] (II) Solid
[ 1767.360] (II) Copy
[ 1767.360] (II) Composite (RENDER acceleration)
[ 1767.360] (II) UploadToScreen
[ 1767.360] (II) DownloadFromScreen
[ 1767.360] (==) NOUVEAU(G0): Backing store disabled
[ 1767.360] (==) NOUVEAU(G0): Silken mouse enabled
[ 1767.360] (II) NOUVEAU(G0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 1767.360] (II) NOUVEAU(G0): [XvMC] Extension initialized.
[ 1767.360] (==) NOUVEAU(G0): DPMS enabled
[ 1767.360] (II) NOUVEAU(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 1767.360] (WW) NOUVEAU(G0): Option "Monitor-DVI-I-1" is not used
[ 1767.360] (WW) NOUVEAU(G0): Option "Monitor-DP-1" is not used
[ 1767.362] (II) NOUVEAU(0): Opened GPU channel 0
[ 1767.366] (II) NOUVEAU(0): [DRI2] Setup complete
[ 1767.366] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 1767.366] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 1767.366] (II) EXA(0): Driver allocated offscreen pixmaps
[ 1767.366] (II) EXA(0): Driver registered support for the following operations:
[ 1767.366] (II) Solid
[ 1767.366] (II) Copy
[ 1767.366] (II) Composite (RENDER acceleration)
[ 1767.366] (II) UploadToScreen
[ 1767.366] (II) DownloadFromScreen
[ 1767.366] (==) NOUVEAU(0): Backing store disabled
[ 1767.366] (==) NOUVEAU(0): Silken mouse enabled
[ 1767.366] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 1767.366] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 1767.366] (==) NOUVEAU(0): DPMS enabled
[ 1767.366] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 1767.366] (--) RandR disabled
[ 1767.388] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1767.388] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1767.388] (II) AIGLX: enabled GLX_ARB_create_context
[ 1767.388] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1767.388] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 1767.388] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 1767.388] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1767.389] (II) AIGLX: Loaded and initialized nouveau
[ 1767.389] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1767.390] (II) NOUVEAU(G0): NVEnterVT is called.
[ 1767.393] (II) NOUVEAU(0): NVEnterVT is called.
[ 1767.444] (II) NOUVEAU(0): Setting screen physical size to 508 x 285
[ 1767.444] resize called 1920 1080
[ 1767.479] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 1767.479] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 1767.479] (II) LoadModule: "evdev"
[ 1767.479] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1767.479] (II) Module evdev: vendor="X.Org Foundation"
[ 1767.479] compiled for 1.14.3, module version = 2.8.2
[ 1767.479] Module class: X.Org XInput Driver
[ 1767.479] ABI class: X.Org XInput driver, version 19.1
[ 1767.479] (II) Using input driver 'evdev' for 'Power Button'
[ 1767.479] (**) Power Button: always reports core events
[ 1767.479] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 1767.479] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 1767.479] (--) evdev: Power Button: Found keys
[ 1767.479] (II) evdev: Power Button: Configuring as keyboard
[ 1767.479] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event2"
[ 1767.479] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 1767.479] (**) Option "xkb_rules" "evdev"
[ 1767.479] (**) Option "xkb_model" "pc104"
[ 1767.479] (**) Option "xkb_layout" "us"
[ 1767.499] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 1767.499] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 1767.499] (II) Using input driver 'evdev' for 'Power Button'
[ 1767.500] (**) Power Button: always reports core events
[ 1767.500] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 1767.500] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 1767.500] (--) evdev: Power Button: Found keys
[ 1767.500] (II) evdev: Power Button: Configuring as keyboard
[ 1767.500] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event1"
[ 1767.500] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 1767.500] (**) Option "xkb_rules" "evdev"
[ 1767.500] (**) Option "xkb_model" "pc104"
[ 1767.500] (**) Option "xkb_layout" "us"
[ 1767.500] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 1767.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[ 1767.500] (II) No input driver specified, ignoring this device.
[ 1767.500] (II) This device may have been added with another device file.
[ 1767.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
[ 1767.500] (II) No input driver specified, ignoring this device.
[ 1767.500] (II) This device may have been added with another device file.
[ 1767.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12)
[ 1767.501] (II) No input driver specified, ignoring this device.
[ 1767.501] (II) This device may have been added with another device file.
[ 1767.501] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event11)
[ 1767.501] (II) No input driver specified, ignoring this device.
[ 1767.501] (II) This device may have been added with another device file.
[ 1767.501] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 1767.501] (II) No input driver specified, ignoring this device.
[ 1767.501] (II) This device may have been added with another device file.
[ 1767.501] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
[ 1767.501] (II) No input driver specified, ignoring this device.
[ 1767.501] (II) This device may have been added with another device file.
[ 1767.501] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event8)
[ 1767.501] (II) No input driver specified, ignoring this device.
[ 1767.501] (II) This device may have been added with another device file.
[ 1767.501] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event7)
[ 1767.501] (II) No input driver specified, ignoring this device.
[ 1767.501] (II) This device may have been added with another device file.
[ 1767.502] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
[ 1767.502] (II) No input driver specified, ignoring this device.
[ 1767.502] (II) This device may have been added with another device file.
[ 1767.502] (II) config/udev: Adding input device DELL Dell USB Entry Keyboard (/dev/input/event4)
[ 1767.502] (**) DELL Dell USB Entry Keyboard: Applying InputClass "evdev keyboard catchall"
[ 1767.502] (II) Using input driver 'evdev' for 'DELL Dell USB Entry Keyboard'
[ 1767.502] (**) DELL Dell USB Entry Keyboard: always reports core events
[ 1767.502] (**) evdev: DELL Dell USB Entry Keyboard: Device: "/dev/input/event4"
[ 1767.502] (--) evdev: DELL Dell USB Entry Keyboard: Vendor 0x413c Product 0x2107
[ 1767.502] (--) evdev: DELL Dell USB Entry Keyboard: Found keys
[ 1767.502] (II) evdev: DELL Dell USB Entry Keyboard: Configuring as keyboard
[ 1767.502] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.5/4-1.5:1.0/input/input5/event4"
[ 1767.502] (II) XINPUT: Adding extended input device "DELL Dell USB Entry Keyboard" (type: KEYBOARD, id 8)
[ 1767.502] (**) Option "xkb_rules" "evdev"
[ 1767.502] (**) Option "xkb_model" "pc104"
[ 1767.502] (**) Option "xkb_layout" "us"
[ 1767.502] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event5)
[ 1767.502] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 1767.502] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
[ 1767.502] (**) Logitech USB Optical Mouse: always reports core events
[ 1767.502] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event5"
[ 1767.502] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc077
[ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found 12 mouse buttons
[ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
[ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found relative axes
[ 1767.502] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
[ 1767.502] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
[ 1767.502] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
[ 1767.503] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
[ 1767.503] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 1767.503] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.0/input/input6/event5"
[ 1767.503] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 9)
[ 1767.503] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
[ 1767.503] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
[ 1767.503] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
[ 1767.503] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
[ 1767.503] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
[ 1767.503] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
[ 1767.503] (II) No input driver specified, ignoring this device.
[ 1767.503] (II) This device may have been added with another device file.
[ 1767.503] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 1767.503] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 1767.503] (II) No input driver specified, ignoring this device.
[ 1767.503] (II) This device may have been added with another device file.
[ 1767.504] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[ 1767.504] (II) No input driver specified, ignoring this device.
[ 1767.504] (II) This device may have been added with another device file.
[ 1767.504] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
[ 1767.504] (II) No input driver specified, ignoring this device.
[ 1767.504] (II) This device may have been added with another device file.
[ 1767.504] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event15)
[ 1767.504] (II) No input driver specified, ignoring this device.
[ 1767.504] (II) This device may have been added with another device file.
[ 1767.504] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 1767.504] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 1767.504] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 1767.504] (**) AT Translated Set 2 keyboard: always reports core events
[ 1767.504] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 1767.504] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 1767.504] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 1767.504] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 1767.504] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 1767.504] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[ 1767.504] (**) Option "xkb_rules" "evdev"
[ 1767.504] (**) Option "xkb_model" "pc104"
[ 1767.504] (**) Option "xkb_layout" "us"
[ 1767.505] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event19)
[ 1767.505] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[ 1767.505] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
[ 1767.505] (**) PS/2 Generic Mouse: always reports core events
[ 1767.505] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event19"
[ 1767.505] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
[ 1767.505] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
[ 1767.505] (--) evdev: PS/2 Generic Mouse: Found relative axes
[ 1767.505] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
[ 1767.505] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
[ 1767.505] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[ 1767.505] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 1767.505] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event19"
[ 1767.505] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 11)
[ 1767.505] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
[ 1767.505] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
[ 1767.505] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
[ 1767.505] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[ 1767.505] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[ 1767.505] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse1)
[ 1767.505] (II) No input driver specified, ignoring this device.
[ 1767.505] (II) This device may have been added with another device file.
[ 1767.505] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 1767.505] (II) No input driver specified, ignoring this device.
[ 1767.505] (II) This device may have been added with another device file.
[ 1774.230] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1774.230] (II) NOUVEAU(0): NVLeaveVT is called.
[ 1774.230] (II) NOUVEAU(G0): NVLeaveVT is called.
[ 1779.499] (II) evdev: PS/2 Generic Mouse: Close
[ 1779.499] (II) UnloadModule: "evdev"
[ 1779.499] (II) evdev: AT Translated Set 2 keyboard: Close
[ 1779.499] (II) UnloadModule: "evdev"
[ 1779.499] (II) evdev: Logitech USB Optical Mouse: Close
[ 1779.499] (II) UnloadModule: "evdev"
[ 1779.499] (II) evdev: DELL Dell USB Entry Keyboard: Close
[ 1779.499] (II) UnloadModule: "evdev"
[ 1779.499] (II) evdev: Power Button: Close
[ 1779.499] (II) UnloadModule: "evdev"
[ 1779.499] (II) evdev: Power Button: Close
[ 1779.499] (II) UnloadModule: "evdev"
[ 1779.499] (II) NOUVEAU(G0): NVLeaveVT is called.
[ 1780.500] Error dropping master: -22(Invalid argument)
[ 1780.501] (II) NOUVEAU(G0): Closed GPU channel 0
[ 1780.503] (II) NOUVEAU(0): Closed GPU channel 0
[ 1780.503] (EE) Server terminated successfully (0). Closing log file.
Thanks for any help!

I have a similar issue except with two ATI cards and four monitors.
I have a working xorg.conf that uses Xinerama and all 4 work but have been trying to get xrandr to work since xinerama is deprecated supposedly.
I would like to switch to xrandr but there is some kind of magic voodoo I have with my current xorg.conf that doesn't even work on an exact same machine and cards that I tried to setup for a co-worker.
lspci:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT]
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT]
My xorg.conf:
Section "Device"
Identifier "ATI0"
Driver "radeon"
BusID "PCI:1:0:0"
Option "ZaphodHeads" "DVI-0"
Screen 0
EndSection
Section "Device"
Identifier "ATI1"
Driver "radeon"
BusID "PCI:1:0:0"
Option "ZaphodHeads" "DVI-1"
Screen 1
EndSection
Section "Device"
Identifier "ATI2"
Driver "radeon"
BusID "PCI:4:0:0"
Option "ZaphodHeads" "DVI-2"
Screen 0
EndSection
Section "Device"
Identifier "ATI3"
Driver "radeon"
BusID "PCI:4:0:0"
Option "ZaphodHeads" "DVI-3"
Screen 1
EndSection
Section "Monitor"
Identifier "DVI-0"
Option "Primary" "On"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
EndSection
Section "Monitor"
Identifier "DVI-1"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
EndSection
Section "Monitor"
Identifier "DVI-2"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
EndSection
Section "Monitor"
Identifier "DVI-3"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI0"
Monitor "DVI-0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "ATI1"
Monitor "DVI-1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "ATI2"
Monitor "DVI-2"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen3"
Device "ATI3"
Monitor "DVI-3"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Screen0" 0 0
Screen "Screen1" RightOf "Screen0"
Screen "Screen2" Above "Screen1"
Screen "Screen3" Above "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection
My Xorg.0.log shows all the DVI connections when I don't use a xorg.conf file but only two are "connected"
I see DVI-0 and DVI-1 connected and in "xrandr -q" but in Xorg.0.log I see DVI-1-2 and DVI-1-3.
xrandr --listproviders show the two cards as well.
Tried "xrandr --setprovideroutputsource 1 0" and they show up in KDE but as clones and then X crashes eventually.
"xrandr --setprovideroutputsource 0 1" just plain crashes X

Often lose wireless connection when using HDTV as monitor

I have an unusual wireless networking problem when using my Samsung HDTV in my living room as a monitor for my MacBook (when watching Internet TV shows, for example). Frequently when I switch URLs, networking freezes, even though the connection appears strong, with the Airport symbol at the top of my screen showing all bars. To re-establish the wireless connection, I have to go through the process of re-joining my network through the “Join Other Network" option. The signal holds as long as I don’t try to change it, as in selecting another URL.
I connect to my HDTV via HDMI cable, using a mini-DVI to HDMI adapter from my Macbook’s video-out port. The audio connection is a mini-plug from the Mac’s headphone out jack to stereo RCA plugs associated with the TV’s HDMI port.
The wireless connection is through a Lynksys Wireless-G 2.4 Ghz, 54 Mpbs Broadband router.
I’d appreciate any solutions the Apple user community has to offer.

I'd say this has nothing to do with your display. The problem will likely lie in either your router settings, network settings or a simple signal strength issue. Try first changing the broadcast channel on your router, and make sure all settings are correct for your desired network.

TV Apple TV MacBook Air:How to connect my computer's monitor and TV as multiple monitors (NOT mirroring)

I have an insignia TV, an apple TV I just bought less than a month ago, and a Macbook Air (mountain Lion) and a MacBook pro (mountain lion).
I am able to connectboth of my computers with the TV to mirror my screen/monitor, but I have not been able to figure out how to use the apple TV to use my TV as a second monitor, like I was able to do with my HDMI cable.
when I bought the Apple TV the person who I talked to at the store told me I would be able to do it, but I havent been able to do it through system preferences and the options for display only show as mirroring through Airplay. I dislike mirroring because while I play something on my computer (or somebody else does) I'd like to still be able to use my computer for browsing or doing homework.
Please help me find a way in which I can make my TV as a second monitor tu my computer without having to have an HDMI cord across the room. I have a puppy and I have had problems with that. That is actually the reason why I considered buying the Apple TV device.
NOTE: In case you know a way to connect my TV to my Macs I have a time capsule and my TV has a DVI, two HDMI, and a USB ports.
thank you!
Lydia

Morning jotref,
Thanks for using Apple Support Communities.
For more information on this, take a look at this article:
About AirPlay Mirroring in OS X Mountain Lion
http://support.apple.com/kb/ht5404
Best of luck,
Mario

How to connect my Cinema Display as a second monitor

I just purchased a new 27-inch iMac, and I explained to the Apple folks that I had a 17-inch cinema display (silver clad model) that I wanted to connect, for a dual monitor set up. They told me just to get the Mini DisplayPort to DVI Adapter, but I was surprised to realize that's not going to work.
Can anyone tell me how to do this, and what connector is actually needed? I have the big old white power brick that I bought to daisy chain my old 17 and 23 inch displays with my old configuration (Mac Pro).
Or can you not have a second monitor with an iMac?
Thanks in advance.

Hi Cathy,
What connector is on that Cinema? ADC, VGA, or DVI?
Video Card:
GeForce GTX 675MX
VRAM Type:
GDDR5
Details:
This model has a NVIDIA GeForce GTX 675MX graphics processor with 1 GB of dedicated GDDR5 memory. At the time of purchase, it can be custom configured with a NVIDIA GeForce GTX 680MX with 2 GB of dedicated GDDR5 memory for an extra US$150.
Standard VRAM:
1 GB
Maximum VRAM:
1 GB*
Built-in Display:
27" 16:9 Widescreen
Native Resolution:
2560x1440
Details:
This model has a 27" LED-backlit 16:9 widescreen TFT active matrix display with IPS technology and a native resolution of 2560x1440. Apple also reports that the "cover glass is fully laminated to the LCD and an anti-reflective coating is applied." Previous Aluminum iMac models have the LCD covered by glass. The company no longer reports viewing angle or contrast ratio, however. Site sponsor Mission Repair offers free diagnosis of iMac hardware problems and a 24-hour repair service for this iMac. Display replacement, keyboard replacement, a hard drive upgrade service, and more are provided.
2nd Display Support:
Dual/Mirroring*
2nd Max. Resolution:
2560x1600 (x2)
Details:
*This model can simultaneously support two external displays up to 2560x1600 via Thunderbolt.
http://www.everymac.com/systems/apple/imac/specs/imac-core-i7-3.4-27-inch-alumin um-late-2012-specs.html

I have a MBPro mid 2013 with 1 Thunderbolt port. Just bought a Mac monitor and want to daisy chain a PC monitor to it. Use a Mini DVI to VGA adapter from MBP to PC monitor. How do I daisy chain the 2 monitors?

I have a MBPro mid 2013 with 1 Thunderbolt port. Just bought a Mac monitor and want to daisy chain a PC monitor to it. Use a Mini DVI to VGA adapter from MBP to PC monitor. How do I daisy chain the 2 monitors?

Hall Palm Desert,
if your Mac monitor has Thunderbolt ports, and the PC monitor is on the end of the daisy chain, then you might be able to do it by connecting your PC monitor’s VGA cable to a Mini DisplayPort-to-VGA adapter (e.g. Apple, NewerTech), connecting that cable’s Mini DisplayPort end to one of the Mac monitor’s Thunderbolt ports, and then connecting a Thunderbolt cable between the other port on the Mac monitor and your MacBook Pro.

I cannot get both monitors to work when connecting my MacBook Pro to a VGA monitor using Mini DisplayPort to VGA Adapter

Need help with 2 monitor set up on MacBook Pro.

I am sorry for the confusion. The reason I asked about the speaker bar is that I can't find any information that shows built-in speakers on your monitor. I have looked everywhere, including in the HP specifications.
Here is the Back I/O panel (Input / Output) for your computer:
Figure 2: Back I/O panel
1 - Video Graphics Adapter port
2 - USB 2.0: 4
3 - RJ45 Network (LAN)
4 - Audio: Line in
5 - Audio: Front speaker/Line out
6 - Audio: Microphone in
The way that I have always connected speakers is to the port labeled # 5 (Audio: Front speaker/Line Out). This port allows sound to be sent to speakers. The VGA port is for video only. There is no audio capability. The only connection that sends Audio and Video is the HDMI (High-Definition Multimedia Interface) connectors.
This is the type of connector that I would expect to see coming from your speakers:
The male one at the bottom of the picture.
Please check the monitor carefully to assure that there are actually speakers built-in. I just don't want us to continue fighting a problem that doesn't exist. There may have been some incorrect information in the advertisement that you read.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Mini Displayport to vga adapter on MacBook pro 13" late 2011. No signal on external monitor

Hi
Connecting a Late 2011 MacBook Pro 13" to an external monitor, trough mini Dispalyport to vga adapter, i see "no signal" messagge on external monitor, even if i get it as secondary monitor on Preferences > Monitor of my MacBook it's visible (i can change resolution, position, clone screen, ecc.).
Any suggestion? somebody found the same problem?

Hi
i did what you said and tried with other resolution/refresh rate combinations, also with anoter external monitor (and vga cable) but its still the same: monitor is detected but there's no signal.
Now I will try to chek if the adapter works on other pc and monitor.
Thanks
(anyway it was the firs time i connect this mac to an external monitor)

Monitor LSMW

Similar Messages

Maybe you are looking for