HR ABAP: Issue with using 'nocommit' parameter on FM HR_INFOTYPE_OPERATION

Issue with using nocommit parameter on FM HR_INFOTYPE_OPERATION:
My client has a requirement to create the following 4 infotypes in sequence in a LUW, i.e either all are created or none is created.
9045 (custom infotype)
0045
0078
0015
I tried to use the nocommit parameter on FM HR_INFOTYPE_OPERATION to insert the 4 infotypes
in a nocoomit mode and then at the end I have issued
'Commit Work', but to my surprise only I/T 0015 is created in the database and the first three (9045, 0045 and 0078) did not make it to database.
I searched many threads on SDN but could not find a solution.
Please let me know if there could be any solution to implement the LUW.
YOur inputs will be appreciated.

Hi ,
i think u can also try with this FM HR_MAINTAIN_MASTERDATA , see its documentations.
no commit works like a simulation mode , what u can do is ,
call FM for all Infotypes and collect all error msgs if any , then finally call FM for all infotypes again without passing nocommit work ( i.e space).
regards
prabhu

Similar Messages

Performance issue with using out parameter sys_refcursor

Hello,
I'm using Oracle 10g, with ODP.Net in a C# application.
I'm using about 10 stored procedures, each having one out parameter of sys_refcursor type. when I use one function in C# and call these 10 sp's, it takes about 78ms to excute the function.
Now to improve the performance, I created one SP with 10 output parameters of sys_refcursor type. and i just call this one sp. the time taken has increased , not it takes abt 95ms.
is this the right approach or how can we improve the performance by using sys_refcursor.
please suggest, it is urgent, i'm stuck up with this issue.
thanks
shruti

With 78ms and 95ms are you talking about milliseconds or minutes? If it's milliseconds then what's the problem and does it really matter if there is a difference of 17 milliseconds as that could just be caused by network traffic or something. If you're talking minutes, then we would need more information about what you are attempting to do, what tables and processing is going on, what indexes you have etc.
Query optimisation tips can be found on this thread.. When your query takes too long ....
Without more information we can't really tell what's happening.

Any issues with using LDAP on LINUX for GRC 5.2 UME?

Our company is converting our LDAP servers from AIX to LINUX. The DNS name used in our UME connection should not change. Are there any issues with using LDAP on LINUX? We are currently on GRC 5.2 SP9 (in the middle of upgrading to SP12).
Also, I have been trying to connect our test UME system to a test LDAP box that has already been converted to LINUX but keep getting a 'connection failed' error when I try to test it.
Do you have to reboot the server to test changing the LDAP connections? I've been trying it by going into UME, pulling up the LDAP tab, hitting the Modify button, entering the new userid and password for test LDAP, and hitting the Test Connection button. I've verified that this userid and password is correct for test LDAP.
Is there a way to get more information about why the connection failed?
Thanks.

I've been told by our LDAP Support group that none of the other configuration settings should have to be changed. I should only have to change the id and password to connect to a test version of LDAP instead of our regular connection to the production LDAP.
Can you test a connection for a different userid/password without having to reboot/restart the server? Do I need to change these two settings, save then, reboot/restart, and then do the Test Connection button?
Thanks.

Issues with using relative links in Captivate 8

Is anyone else having issues with using relative links in Captivate 8? These links all used to work in the previous version of Captivate. And I could have sworn this was fixed already once in Captivate 8 but it's popping up again for us. Here is the situation... We have courses that are made up of multiple lessons which as separate Captivate files. Within those lessons are buttons to link to external documents (which live in a shared document folder), demonstrations, etc. We use relative links because we post these to our amazon servers and we also sell them to clients where they can post them on their own web servers or in their LMS. SO we can't put in full paths for the links or we'd have to change them constantly. So an example is that the link for a button might be "../Document/nameofdoc.pdf" This would be going to a user guide or something that is posted in the "Document" folder that lives at the same level as the lesson's folder. But now, all of the sudden, none of our bazillion links is working. And I've tried buttons, hyperlinks, and even the old click box. Nothing works with relative links. And I did check the permissions on every file and folder on our Amazon server to verify nothing changed there as well. Any suggestions?

I have the same issue with relative links using Captivate 8. I am trying to load Captivate modules into an LMS using relative links to document files within the LMS. The links work fine during a site page test so not an issue in the LMS, but from the Captivate module they aren't working....
Help?

Issues with using the output redirection character with newer NXOS versions?

Has anyone seen any issues with using the output redirection character with newer NXOS versions?
Am receiving "Error 0x40870004 while copying."
Simply copying a file from bootflash to tftp is ok.
This occurs for both 3CDaemon and Tftpd32 softwares.
Have tried it on multiple switches - same issue.
Any known bugs?
thanks!
The following is an example of bad (NXOS4.1.1b) and good (SANOS3.2.1a)
MDS2# sho ver | inc system
system:    version 4.1(1b)
system image file is:    bootflash:///m9200-s2ek9-mz.4.1.1b.bin
system compile time:     10/7/2008 13:00:00 [10/11/2008 09:52:55]
MDS2# sh int br > tftp://10.73.54.194
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
TFTP put operation failed:Access violation
Error 0x40870004 while copying tftp://10.73.54.194/
MDS2# copy bootflash:cpu_logfile tftp://10.73.54.194
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
|
TFTP put operation was successful
MDS2#
ck-ci9216-001# sho ver | inc system
system:    version 3.2(1a)
system image file is:    bootflash:/m9200-ek9-mz.3.2.1a.bin
system compile time:     9/25/2007 18:00:00 [10/06/2007 06:46:51]
ck-ci9216-001# sh int br > tftp://10.73.54.194
Trying to connect to tftp server......
|
TFTP put operation was successful

Please check with new version of TFTPD 32 server. The error may be due to older version of TFPT server, the new version available solved this error. Files are getting uploaded with no issues.
1. Download tftpd32b.zip from:
http://tftpd32.jounin.net/tftpd32_download.html
2. Copy the tftpd32b.zip file into an empty directory and extract it.
3. Copy the file you want to transver into the directory containing tftpd32.exe.
4. Run tftpd32.exe from that directory. The "Base Directory" field should show the path to the directory containing the file you want to transfer.
At this point, the tftpserver is ready to begin serving files. As devices request files, the main tftpd32 window will log the requests.
Best Regards...

Performance issue with using buffering in a APPL0 or APPL1 Table

Hi,
Can anyone please tell me whether there's any serious performace issue with using buffering for a Master or Transaction table? I'm asking this because when I run code inspector for my transp table I'm getting information message:
Message Code 0011 ==> Buffereing is Activated but Delivery Class Is "A" and Message Code 0014 ==> Buffereing is Activated but Data Class Is "APPL1".
So what's other way round for improving performance.
Thanks,
Mahesh M.S.

Hi,
have you read the documentation?
Let me paste it here for you:
Buffering is switched on for the examined table and it has data type 'APPL0' or 'APPL1'.
Tables with data type 'APPL0' or 'APPL1' should contain master or transaction data, so these tables should either contain a large amount of data or their content should change frequently. Therefore buffering the table is unfavourable. Very large tables suppress other tables in the buffer memory and hence slow done any access to them. Transaction data should not be buffered because the synchronization of the changes on the various application servers is very time consuming.
In exceptional cases, small master data tables ('APPL0', size category 0) can be buffered.
The solution depends on the table content. If it is master or transaction data, the table should not be buffered. If the table content does not consist of master or transaction data, the data type should be corrected accordingly.
This should answer your questions...
Kind regards,
Hermann

HI. ... Anyone know of any issues with using Logic Pro music software with Mountain lion OS.. I have heard rumours in the past is that all sorted now?

HI. ...
Anyone know of any issues with using Logic Pro music software with Mountain lion OS..
I have heard rumours in the past is that all sorted now?

At least Logic Pro 9 and Logic Pro X work correctly in Mountain Lion. Furthermore, Logic Pro X requires the latest OS X Mountain Lion version

Are there any issues with using OS X Mavericks and Premiere CC?

Are there any issues with using OS X Mavericks and Premiere CC?

Official statement: http://blogs.adobe.com/premierepro/2013/10/premiere-pro-and-mac-os-x-10-9-mavericks.html
Peter Garaway
Adobe
Premiere Pro

Are there any know issues with using multiple (2) apple tv's in the same household??

I'm thinking of getting a second Apple TV. Are there any known issues with using multiple (2) apple tv's in the same household? Thank you in advance.

No, shouldn't have any problems

Issue with using GET n SET Parameter in module pool programming.

Hello Friends,
                     I am using SET n GET Parameter to access input values from a screen. But when I use it, the values are not transfered back n forth. Getting initial values.
Your expertise would be appreciated.
Cheers,
Senthil

Hi,
check this
Filling an Initial Screen using SPA/GPA Parameters
To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.
To fill the initial screen of a program using SPA/GPA parameters, you normally only need the SET PARAMETER statement.
The relevant fields must each be linked to an SPA/GPA parameter.
On a selection screen, you link fields to parameters using the MEMORY ID addition in the PARAMETERS or SELECT-OPTIONS statement. If you specify an SPA/GPA parameter ID when you declare a parameter or selection option, the corresponding input field is linked to that input field.
On a screen, you link fields to parameters in the Screen Painter. When you define the field attributes of an input field, you can enter the name of an SPA/GPA parameter in the Parameter ID field in the screen attributes. The SET parameter and GET parameter checkboxes allow you to specify whether the field should be filled from the corresponding SPA/GPA parameter in the PBO event, and whether the SPA/GPA parameter should be filled with the value from the screen in the PAI event.
When an input field is linked to an SPA/GPA parameter, it is initialized with the current value of the parameter each time the screen is displayed. This is the reason why fields on screens in the R/3 System often already contain values when you call them more than once.
When you call programs, you can use SPA/GPA parameters with no additional programming overhead if, for example, you need to fill obligatory fields on the initial screen of the called program. The system simply transfers the values from the parameters into the input fields of the called program.
However, you can control the contents of the parameters from your program by using the SET PARAMETER statement before the actual program call. This technique is particularly useful if you want to skip the initial screen of the called program and that screen contains obligatory fields.
If you want to set SPA/GPA parameters before a program call, you need to know which parameters are linked to which fields on the initial screen. A simple way of doing this is to start the program that you want to call, place the cursor on the input fields, and choose F1 followed by Technical info. The Parameter ID field contains the name of the corresponding SPA/GPA parameter. Alternatively, you can look at the screen definition in the Screen Painter.
The technical information for the first input field of the booking transaction TCG2 looks like this:
The SPA/GPA parameter for the input field Company has the ID CAR. Use this method to find the IDs CON, DAY, and BOK for the other input fields.
The following executable program is connected to the logical database F1S and calls an update transaction:
REPORT BOOKINGS NO STANDARD PAGE HEADING.
TABLES SBOOK.
START-OF-SELECTION.
WRITE: 'Select a booking',
SKIP.
GET SBOOK.
WRITE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
HIDE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
AT LINE-SELECTION.
SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,
                    'CON' FIELD SBOOK-CONNID,
                    'DAY' FIELD SBOOK-FLDATE,
                    'BOK' FIELD SBOOK-BOOKID.
CALL TRANSACTION 'BOOK'.
The basic list of the program shows fields from the database table SBOOK according to the user entries on the selection screen. These data are also stored in the HIDE areas of each line.
If the user selects a line of booking data by double-clicking, the system triggers the AT LINE-SELECTION event and takes the data stored in the HIDE area to fill them into the SPA/GPA parameters of the initial screen of the transaction. Then it calls the transaction. Since you do not suppress the initial screen using AND SKIP FIRST SCREEN, the initial screen may appear as follows:
If you would use the AND SKIP FIRST SCREEN option with the CALL TRANSACTION statement, the second screen would appear immediately, since all obligatory fields of the first screen are filled.
Regards
Edited by: K.P.N on Jan 9, 2008 5:21 AM

Issue with Custom data parameter in Excel Data Connection

Hello,
We are querying a OLAP (SSAS 2008) cube using Excel 2007 by creating a data connection to SSAS server with an extended parameter “Custom Data”. We are using custom data parameter to apply our application’s user security to filter dimension
members in Excel’s pivot table report. We have created a pivot table in Excel and the excel is including this custom data parameter along with each request that excel is submitting to SSAS.
However, when the user selects “Show Properties in Report” option for a dimension which is selected in Row-axis of pivot table, Excel is not including custom data parameter . Why this “Custom Data” parameter is not being included in
the request only for this specific case?
1. The Request which sent from Excel to SSAS when user clicks on “Show Properties in Report” option
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Session xmlns="urn:schemas-microsoft-com:xml-analysis" SessionId="AE6B294B-4983-4010-BC5F-E0896A49ECD9"/></soap:Header><soap:Body><Discover
xmlns="urn:schemas-microsoft-com:xml-analysis"><RequestType>DISCOVER_LITERALS</RequestType><Restrictions/><Properties><PropertyList><Content>SchemaData</Content><Format>Tabular</Format></PropertyList></Properties></Discover></soap:Body></soap:Envelope>
2. The sample Request which sent from Excel to SSAS for all other requests
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Session xmlns="urn:schemas-microsoft-com:xml-analysis" SessionId="74165AD6-C240-4634-92A1-61A400A3FC97"/></soap:Header><soap:Body><Discover
xmlns="urn:schemas-microsoft-com:xml-analysis"><RequestType>MDSCHEMA_CUBES</RequestType><Restrictions><RestrictionList><CUBE_NAME>RepCube</CUBE_NAME></RestrictionList></Restrictions><Properties><PropertyList><Catalog>QAV10_12thMay2010</Catalog><Timeout>5000</Timeout><SafetyOptions>2</SafetyOptions><MdxMissingMemberMode>Error</MdxMissingMemberMode><LocaleIdentifier>1033</LocaleIdentifier><DbpropMsmdMDXCompatibility>1</DbpropMsmdMDXCompatibility><CustomData>xxxxxx</CustomData></PropertyList></Properties></Discover></soap:Body></soap:Envelope>
As the Custom Data parameter is missing in 1st request our application logic is throwing a custom exception to Excel and Excel is not able to understand the exception message. Excel is sending the same request repeatedly (going into infinite loop) and the excel
window is freezed. Not able to work with excel until restarting the Excel.
Can anyone help me to resolve the above? quick help is much appriciated!
Thanks,
Venkat

Venkat,
We have a very similar issue, but there is almost no material to help us. If this gets to you, please let me know if you progressed it or whether I need to go to Microsoft for a solution
THanks
David

Issue with using crystal 8.5 and crystal 13 simultanously in dependent apps

Hello All,
I am facing some issue with different crystal versions used in applications. My application(let's say X13) is using crystal 13.0.10.1385 dotnet API and another application (let's say Y85) is using crystal 8.5 dotnet API version. My application X13 has a module which is dependent on application Y85 module and exchange information between them.
As both applications use crystal, CRPE32.dll is loaded in memory once for both the applications. The issue derives from the fact that the application X13 brings the crpe32.dll (version 13.0.10.1385) located in folder “C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86” into memory. If the application X13 is not loaded into memory first then the version of crpe32.dll (i.e. 8.5.0.461) located in the application Y85 install folder will be used.
As we know that CR 13 and CR 8.5 are two entirely different API's now without any compatibility with each other. Now if my application X13 is initialized first and crpe32.dll (version 13.0.10.1385) is loaded in memory, on accessing the module dependent on application Y85, Y85 tries to make crystal calls.
It tries to call to PEOpenEngine, PEOpenPrintJob, PEGetNTables, PEGetNthTableLocation, crPEGetNthTableLogOnInfo and PEGetNDatabaseFields which executes fine but It is only the call to PEGetNthDatabaseFieldInfo that fails, with a return value of 0. Below is the sequence order of calls:
A 2013 .NET Crystal Engine is initialized first using ReportDocument.Load method or CrystalEngine.CRPE.InitCrpe.Also note that calling CrystalEngine.CRPE.CloseCrpe has no positive effect of eliminating the issue.
Subsequent calls to PEOpenEngine, PEOpenPrintJob, PEGetNTables, PEGetNthTableLocation, crPEGetNthTableLogOnInfo and PEGetNDatabaseFields all execute just fine.
It is only the call to PEGetNthDatabaseFieldInfo that fails, with a return value of 0.
Question arises here is how to get PEGetNthDatabaseFieldInfo working when the .NET Crystal Engine has already been initialized.
Is there a separate declare we can add to our VB6 code that will be compatible with crpe32.dll version 13.0.10.1385?
Or can we load both crpe32.dll (version 13.0.10.1385 and 8.5.0.461) in parallel and instruct .NET crystal to use version 13 and other one to use version 8.5 dll?
I have attached a sample code demonstrating same too. It will be great if anyone can help me on this.
Crystal versions involved : 13.0.10.1385 and 8.5.0.461
Visual Studio 2012
VB.net
WIN APP
Thanks
Saurabh

Hi Saurabh,
CR 8.5 never was side-by-side compatible with any other version of CR runtime.
And as of CR 9 you no longer are licensed to be able to use crpe32 as the reporting engine. R&D can change it at anytime so absolutely no support for it in that respect either. After CR 9 crpe32 was completely rewritten and a lot of parts were removed into their own dll's. The major parts were the DB drivers were renamed and the Parameter API's were also updated and old one's are no longer recognized, or may not work the same way.
So why not simply completely drop 8.5 since it is over 12 years old now... There is no reason you need to still be supporting it. We dropped support for it a long long time ago.
Don

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

Issues with using utl_http with Oracle Wallet

Hello Everyone,
We are experimenting with Oracle wallet and utl_http and are attempting to do an https transfer and we are facing some problems. I will appreciate your help greatly if you can advise on what could be wrong. We are on db version 10.2.0.1 and Unix HP-UX. The intention ping an https url and get a simple 200 response. Future development would include get/post XML documents from that url and other interesting stuff. I understand that utl_http with Oracle wallet can be used for this purpose.
The wallet has been created and the ewallet.p12 exists. We downloaded the SSL certificate from the url's website and uploaded into the wallet.
Everything works if I put in a url with plain http. However, it does not work with an HTTP*S* url.
With HTTPS when I run the below code I get the following error. Again, greatly appreciate your time and help because this is the first time we are using Oracle wallet manager and do not know where to go from here.
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1029
ORA-29268: HTTP client error
declare
url varchar2(225);
req utl_http.req;
resp utl_http.resp;
my_proxy BOOLEAN;
name varchar2(2000);
value varchar2(2000);
V_proxy VARCHAR2(2000);
v_n_proxy varchar2(2000);
v_msg varchar2(100);
v_len PLS_INTEGER := 1000;
BEGIN
-- Turn off checking of status code.
utl_http.set_response_error_check(FALSE);
--Set proxy server
utl_http.set_proxy('my-proxy');
utl_http.set_wallet('file:<full Unix path to the wallet on DB server>','wallet998');
req := utl_http.begin_request('https://service.ariba.com/service/transaction/cxml.asp');
--Set proxy authentication
utl_http.set_authentication(req, 'myproxyid', 'myproxypswd','Basic',TRUE); -- Use HTTP Basic
resp := utl_http.get_response(req);
FOR i IN 1..utl_http.get_header_count(resp) LOOP
utl_http.get_header(resp, i, name, value);
dbms_output.put_line(name || ': ' || value);
END LOOP;
utl_http.end_response(resp);
exception
when others then
dbms_output.put_line(sqlerrm);
END;

I tried this using plsql ...
declare
SOAP_URL constant varchar2(1000) := 'http://125.21.166.27/cordys/com.eibus.web.soap.Gateway.wcp?organization=o=WIPRO,cn=cordys,o=itgi.co.in';
request UTL_HTTP.req;
begin
dbms_output.put_line('Begin Request');
request := UTL_HTTP.begin_request(SOAP_URL,'POST',UTL_HTTP.HTTP_VERSION_1_1);
dbms_output.put_line('After Request');
exception
when others then
dbms_output.put_line('Error : '||sqlerrm);
end;The output was ...
Begin Request
Error : ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1029
ORA-12535: TNS:operation timed outIt seems to be an issue with the webservice, plz check if its available & allowing requests.

Issue with use of Function Module GUI_UPLOAD

Hi Experts,
I have an issue in using the Function Module GUI_UPLOAD for uploading the contents of an Excel file on the Presentation Server to an internal table in an ABAP Program.
My file consists of around 300 records but the FM succeeds in uploading only the first 6 lines to the Internal Table specified while calling the FM.
I dont have any idea why this happens. Any pointers in this direction will be helpful.
Thanks in advance.
Regards,
Keerthi

Hi,
Kindly go through this link below:
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=60655105
Hope it helps you
Regards
Mansi

HR ABAP: Issue with using 'nocommit' parameter on FM HR_INFOTYPE_OPERATION

Similar Messages

Maybe you are looking for