Issue with AS2 Adapter monitoring

Hi All,
I am using Seeburger AS2 Adapter in our XI project we are able to post and retrieve
messages through AS2 communication,but we are facing the problem of monitoring the messages if any incoming messages failed in the AS2 adapter only due to some network failure or some other issue we are not able to track which message is failed and what payload it contains as in Adapter Monitoring or communication channel monitoring AS2 Adapter shows the only "Failed Session"
Do we have any application to monitor it in XI.
Regards
Gaurav

Hi Gaurav,
Have you tried Tcode SXMB_MONI . In this by giving some details about your scenario, it will give you the information about all the messages which are successful or not. Here you can see the payload af successful messages and error in failed message by clicking on the perticular message.
hope this will help.
regards
HONEY

Similar Messages

Issue with Apps adapter for Create_Cust_Account API

Hi ,
I need to invoke this package from apps adapter in BPEL(10.1.3.5).
Create Customer: HZ_CUST_ACCOUNT_V2PUB. create_cust_account. This is a Over loaded procedure. Look for the Procedure with these Parameters.
PROCEDURE create_cust_account (
p_init_msg_list IN VARCHAR2:= FND_API.G_FALSE,
p_cust_account_rec IN CUST_ACCOUNT_REC_TYPE,
p_organization_rec IN HZ_PARTY_V2PUB.ORGANIZATION_REC_TY
PE,
p_customer_profile_rec IN HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER
PROFILEREC_TYPE,
p_create_profile_amt IN VARCHAR2:= FND_API.G_TRUE,
x_cust_account_id OUT NUMBER,
x_account_number OUT VARCHAR2,
x_party_id OUT NUMBER,
x_party_number OUT VARCHAR2,
x_profile_id OUT NUMBER,
x_return_status OUT VARCHAR2,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2
But I’m getting the following error,
An error occurred while running Jpublisher.missing method
· I’ve tried with Database adapter. But in the runtime I’m not able to pass oracle apps initialization parameter in spite of using transaction and idempotent property in partnerlink.
· Then I’ve tried to invoke fnd_global.apps_initialize first then call the package from database adapter, but it fails again, apparently its not able to execute both DBadapter in same database session although they are in same BPEL transaction.
When I’m passing the initialization parameters in adapter created wrapper procedure then its working fine and customer got created.
Please let me know where I’m going wrong or issue with apps adapter.
It’s urgent …
Thanks in Advance,
Shreekanta

Thanks for the reply.
I'm able to execute the BPEL flows using DB adapter in same session and customer got created.
But I'm wondering why I cant invoke the API using Apps adapter though its standard one.
wsdl file is not getting generated as the adapter wizard not get completed.
Do u have any idea why its giving ' error occurred while running Jpublisher.missing method' error?should I conclude that apps adapter does not support overloaded procedure.

Problem with CC Receiver with AS2 Adapter Seeburger

Hi,
I try to test the AS2 Adapter with Receiver channel y one server and Sender channel in second server, but in the Receiver channel, I have the error :
"MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2."
I find the error and I found the URL Error in AS2 adapter. Object not found in lookup of as2.. Its urgent..!! with the same problem, but I have the same configuration in the Party of the receiver and the Sender, the same AS2ID name, and try with the solution in the forum respect the Party name in the scenario of the Receiver, but don't work.
My scenario is send an IDOC from R/3 to a partner with the AS2 receiver channel.
Is my fisrt scenario with AS2 adapter. Somebody help me please with any example or with any idea about the solution to my problem?
Greetings,
Hervey

I have resolved this problem, thanks.

Issue with DB Adapter involving multiple tables

Hi,
Am facing an issue with DB Adapter with multiple tables. Here are the details.
I have 4 tables. Header, Details,Products and Devices. The relationship is defined as follows:
Header has 1:M relationship with Details.
Details has 1:M relationship with Products.
Products has 1:M relationship with Devices.
I want to select the details from all the tables for a particular header_id and detail_id. Defined 2 parameters and query is created with parameters.
SELECT DISTINCT t0.FILE_NAME, t0.UNIQUE_SEQUENCE_NUMBER, t0.HEADER_COUNT, t0.TOTAL_DEVICE_COUNT, t0.FILE_DATE, t0.FILE_SEQ_NUMBER, t0.DEVICE_COUNT, t0.PHONE_TYPE, t0.PHONE_OWNERSHIP, t0.TRANSACTION_TYPE, t0.PURCHASE_ORDER_NUMBER, t0.CUSTOMER_ID, t0.CUSTOMER_DEST_SUFFIX, t0.LOCATION_DESTINATION, t0.MASTER_FACTORY_ORDER, t0.MASTER_FACTORY_ORDER_LINE_NUM, t0.ENT_ORDER_NUMBER, t0.DELIVERY_IDENTIFICATION_NUM, t0.UEDF_REVISION_NUM, t0.STATUS, t0.INBOUND_BPEL_INSTANCE_ID, t0.ERROR_DESCRIPTION, t0.INBOUND_FILE_VERSION, t0.CREATED_BY, t0.CREATION_DATE, t0.UPDATED_BY, t0.UPDATE_DATE FROM EDF_HEADER_STG_INT t0, EDF_DETAILS_STG_INT t1 WHERE (((t0.FILE_NAME = #file_name) AND (t1.EDF_SERIAL_TYPE = #prod_type)) AND (t1.UNIQUE_SEQUENCE_NUMBER = t0.UNIQUE_SEQUENCE_NUMBER))
I expect the DB Adapter to retrieve the records for the parameters passed. i.e only those records from details table which matches with the parameter I passes in (t1.EDF_SERIAL_TYPE = #prod_type) . But I see that the DB Adapter retrieves all records from the details table for a particular unique_sequence_number(unique_sequence_number is primary key for headers table and foreign key for details table). Could you pls tell me how can I retrieve only selected records from the details table?
Regards,
Meenu

Yes. When I run this query in DB, I get one record . While defining DB Adapter, I have imported 4 tables and also defined the relationship between the tables. In my case, column unique sequence number is primary key of headers table and foreign key of details table.The above select query is generated by the DB Adapter for the parameters I have passed in.
My data is as follows:
Headers table:
file_name uniq_seq_num
file_1.xml 220
Details table
product_id unique seq num edf_prod_type
111 220 A
112 220 B
113 220
Now, I call DB Adapter with parameters 'file_1.xml' (file_name)and 'A'(prod_type). I expect the DB adapter to retrieve only one record with product_id 111 in the detailscollection. But I see that the adapter retrieves all records from the details table without considering the value of prod_type.
Edited by: user13276819 on Mar 19, 2012 6:32 AM

AS2 software to work with AS2 adapter of B2B Toolkit 1.0

Hi Team,
I am doing scenario on AS2 adapter of B2B ToolKit 1.0 to work with AS2 adapter i need AS2 software and i am thinking to use mendelson AS2 server to work with it does it support it or should i use another AS2 software please suggest me.
Regards,
Avinash

Hi Avinash,
you have this blog, Easy-to-use AS2 software - part I Easy-to-use AS2 software - part I
You can find the part 2 and 3 of it. All the info has been explained very good.
Best regards, i hope it helps you.

Seeburger inbound/outbound mapping options with AS2 adapter

Hi Gurus,
This is the first time that i am handling Seeburger adapters(AS2 adapter).
We have the following issue.
We are using AS2 adapter from Seeburger for communicating with Partners (inbound/outbound).
For some scenarios, the trading partners either sends us a flat/csv file or expects a flat/csv file from PI.
And for these scenarios, we are using the AS2 adapter (for sender or receiver channel configuration) .
Now, the main issue is that we need to convert the flat file to PI-XML format when we receive a flat file from a trading partner or we need to convert from PI-XML format to flat file format when we are sending file to a trading partner.
Since the AS2 adapter does not have a File Content Conversion (Like we have in the File/FTP adapter) mechanism, we need to rely on MessageTransformBean (under AF Modules) to do the conversion for us. However, since this module cannot handle deep structures (nested structures) what other alternatives can we look out for ?
I know we can also go for BIC Mapper which is shipped from Seeburger for EDI to XML and XML to EDI conversions. However in this project, we just need XML to flat file/CSV or Flat File/CSV to XML conversions and hence we want to abstain from buying a license for BIC mapper.
Please let me know what other options can we try in this case.
Does Seeburger has anything specific to do the conversions from XML to flat file or flat file to XML (and not the whole BIC mapper tool).
Regards, Gaurav.

Does Seeburger has anything specific to do the conversions from XML to flat file or flat file to XML (and not the whole BIC mapper tool).
No. Seeburger doesn't provide any such tool/option.
Please let me know what other options can we try in this case.
As per the detail you have provided, you don't have any standard option left. You have to either develop your own adapter module or you can pass the payload directly to mapping and then perform Java mapping on it. You have option of using Conversion Agent but there must be some license cost for it as well.
Regards,
Prateek

Issue with minidisplay adapter and wifi

I'm not sure if anyone else is having this issue, but my gf is having an issue when she connects her 13" macbook pro to her monitor via the minidisplay dvi adapter. When she connects it her wifi disconnects and has no internet access at all, but when she disconnects it the internet comes right back on. She's using a generic adapter but what would that have to with the wifi? She uses a linksys G router and is using 10.6.1

This thread caught my attention - because since switching last week from a late '06 Macbook to the Macbook Pro 13", my Wifi performance at home has gotten slow and unreliable.
I'm using the Apple MiniDP-DVI adapter, connected to a 24" Dell monitor, which has worked great for a few years on my white Macbook. My base station is a Linksys WRTSL54GS, located about 20 feet away from my desk.
So, I tried some speed tests with and without the DVI. Performance with the adapter connected is terrible, disconnected it's perfect. Further testing shows that positioning matters.
When the adapter is turned back 90 degrees, leading the monitor cable towards the back of my desk, Wifi performance is bad. When I turn the adapter so it sticks straight out the left side of the Macbook Pro, performance is normal.
This is a little weird, but an acceptable workaround for me.

W540 and Ultradock Display Port Issue with Monoprice 27" Monitor

Hi,
I have been troubleshooting an issue with my W540 and Ultradock for over a month now.
The issue is that the display port will not recognize my Monoprice 27" monitor. This same monitor was working previously with my W520 and a different dock (ThinkPad Mini Dock Plus Series 3) through the same display adapter. The current monitor will work on the DVI port, but I obviously can't get the full resolution of the monitor without the display port adapter.
So far I have tried:
1) Updating the drivers of the laptop
2) Updating the drivers of the dock itself to 2.22
3) Power cycling the monitor with the PC connected, not connected, etc.
4) Switching between Standard/Advanced mode in the BIOS
5) Nearly every iteration of monitor detection in the screen resolution settings
6) Changing cables, adapters, and display ports
What is different in my scenario (based off of the other issues I've seen with the Ultradock and W540) is that the monitor is never even detected under any circumstance through the display port. Device manager never sees it, nor does the normal monitor detection procedure.
Any help would be greatly appreciated.
Best,
Austin

Any ideas?
I am about to throw this in the trash... It's now defaulting my DVI port monitor to 640x480 without the option to change it.
Moderator comment: Post edited to conform with the Community Rules. Keep it clean.

Classloader issue with resource adapter and webservice

The following applications are planned to be deployed on the server.
1.My-shared-lib.ear (J2EE shared library).
2.My-Service-ear.ear (Service)
3.My-Resource-Adapter.rar
The My-shared-lib.ear contains a war which has 3rd Party jars.
The My-Service-ear.ear contains the service classes and refers to the My-shared-lib.ear using a library relationship. In our case, it refers to spring, Hibernate and related jars.
The My-Resource-Adapter.rar contains the Resources Adapters. In this case it contains the Spring jars.
Points on Setup
1.The configuration does not specify any jars in the classpath.
2.There are no 3rd party jars in the ext folder.
*2.Issue Description*
Issue while starting the Service EAR.*
The development setup has an application server that has My-shared-lib.ear and My-Service-ear.ear deployed. This works fine.
The proposed deployment architecture mandates that these applications be deployed on a server where the My-Resource-Adapter.rar is already running. We can deploy & start My-shared-lib.ear . However, when we try to deploy and start My-Service-ear.ear, it fails to start with the error. The detailed exception is found in Appendix A.
Error Message:
java.lang.NoClassDefFoundError: org/hibernate/ejb/HibernatePersistence
*3.Options tried*
1.Place all the required jars in the .rar.
We placed all the 3rd party jars required for the My-Service-ear.ear in the My-Resource-Adapter.rar file. When we deployed all the 3 applications, all applications including the My-Service-ear.ear were deployed and started as well.
2.Place all the required jars in the Service ear.
We placed all the 3rd party jars required for the My-Service-ear.ear in the My-Service-ear.ear file with the <prefer-web-inf-classes>true</prefer-web-inf-classes>. When we deployed all the 3 applications, all applications including the My-Service-ear.ear were deployed and started as well.
3.Altering deployment order.
The deployment order was altered with a higher preference being given to the My-Service-ear.ear. When we deployed all the 3 applications, the application My-Service-ear.ear was deployed but failed to start giving the same exception.
*4.Analysis*
1.The spring jar though available in the library ear is being loaded from the .rar application by the classloader.
2.The above point means that the library reference being provided in the My-Service-ear.ear does not seem to have any impact.
3.In the 3rd scenario we observed that when the spring is removed from the .rar, it gets loaded from the My-shared-lib.ear. However when it tries to load Hibernate related classes, it fails.
*5.Summary*
Our understanding is that all the applications run within their own Classloaders. If classes are not found within the applications, then they should be looking at the Application Server. But here we see that they are referring to the classes in ‘.rar’ file. Hence we are unable to understand this issue. The above problem has workarounds. However, these options are not allowed as per the requirement. The requirement is that the application should run independent of the’ .rar’. Is there a better approach? Are we missing any configuration?
Edited by: user8575867 on Oct 13, 2010 11:41 PM

This thread caught my attention - because since switching last week from a late '06 Macbook to the Macbook Pro 13", my Wifi performance at home has gotten slow and unreliable.
I'm using the Apple MiniDP-DVI adapter, connected to a 24" Dell monitor, which has worked great for a few years on my white Macbook. My base station is a Linksys WRTSL54GS, located about 20 feet away from my desk.
So, I tried some speed tests with and without the DVI. Performance with the adapter connected is terrible, disconnected it's perfect. Further testing shows that positioning matters.
When the adapter is turned back 90 degrees, leading the monitor cable towards the back of my desk, Wifi performance is bad. When I turn the adapter so it sticks straight out the left side of the Macbook Pro, performance is normal.
This is a little weird, but an acceptable workaround for me.

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

Satellite P300-1AN - Touchpad issue with AC adapter

I've a Satellite P300-1AN notebook and since the beginning (two weeks)
I have a touchpad issue: it is not immediately responsive and the pointer trembles when touching the pad. Very often it freezes for just one or two seconds.
This is VERY annoying. A USB mouse works perfectly.
I tried reinstalling ALPS drivers, tried Synaptics ones, tried just Windows Vista drivers: no way.
Now I have found the reason: this issue is present only when the notebook is powered by AC adapter.
With battery the touchpad is perfect.
I contacted Toshiba Service and thay said that they won't change the AC adapter if I don't try before a complete system restore!
Isn't it simpler just try with a new adapter and only then, if the problem persists, try more drastic procedures?
Has anyone had this same issue?

> I contacted Toshiba Service and thay said that they won't change the AC adapter if I don't try before a complete system restore! Isn't it simpler just try with a new adapter and only then, if the problem persists, try more drastic procedures?
The point is that your notebook should be always checked using the Toshiba factory configuration.
Why? Because the ASP wants to be sure that this issue is not related to a software problem (compatibility issue with 3rd party applications). The software issues are not covered by warranty.
Furthermore the ASP will always recover the notebook before checking any hardware parts for a malfunction. Therefore you should always backup your data from the HDD before you will send the notebook for checking.
I would recommend to reinstall the OS using the Toshiba recover disk and then check if the issue would appears.
If yes then you can contact the ASP again and could provide all details which are necessary for an technician.
Bye

Issue With Apps Adapter JDev 11.1.1.3

Hi ,
We are facing some issue with Oracle Apps Adapter with Jdev 11.1.1.3. The wrappers for PLSql APIs were not properly generated.
If anyone having such issue/solution pls share the same.
Thanks In Adv
Venkata Madhu

Hi Anuj,
I sent email to ur official id with the issue details. 1 query i have here, Can i generate wrapper using 10g Adapter and consume in OSB 11.1.1.3?.
Also some funny issues we are facing with API's. If the API create/modified, immediately we couldn't able to generte the wrapper if generate also, the response is not in xsd defined format.
But if we re-generate the wrapper after sometime, it work with no issues. Don't why.
Regards
Venkata Madhu

Issues with FTP adapter

Hello,
I m facing issues using the FTP adapter. I am using 10.1.3.1 standalone installed in my desktop.
1) The FTP adapter doesnt poll continuously for the files. It dies off as soon the folder is empty. If there are incoming files after sometime, the BPEL process fails to pick them. I created an empty BPEL process that has a recieve activity from an FTP adapter as partner link
2) The files are fetched and deleted but are never archived, despite setting the archive files. Can we not archive those files in another folder of same FTP server ?
3) Sometimes, the files are deleted, but there is no activity or process shown in the BPEL console.
Can you please help me with these issues
Thanks
Harinath Gandhi

Are you able to upgrade to 10.1.3.3. A lot of issues with adapters are solved in this release.
Marc
http://orasoa.blogspot.com

MDN Issue in AS2 adapter.. Seeburger experts., Need help

Hi All,
Iam doing a scenario EDI-->Idoc for purchase order(ORDERS) by using AS2 adapter.
We are expected to send the technical acknowledgment once we receive the Orders from sender.
I think When we use the MDN (Message disposition notification), i will be getting the system generated acknowledge like below.
 <TransmissionReport>
<from>SAP</from>
<to>BIS</to>
<transmissionMsgID>43cc21a0-f752-11d8-c8ca-00c09f19e074</transmissionMsgID>
<sentAt>2004-08-26T132252+0200</sentAt>
<info/><adapterName>AS2</adapterName>
</TransmissionReport>
But my requirement is to send the ackowledgement with few more details like POnumber along with the standard details like below.
<TransmissionReport>
<from>SAP</from>
<to>BIS</to>
<transmissionMsgID>43cc21a0-f752-11d8-c8ca-00c09f19e074</transmissionMsgID>
<POnumber>6529833</POnumber>
<sentAt>2004-08-26T132252+0200</sentAt>
<info/><adapterName>AS2</adapterName>
</TransmissionReport>
1. Is there any option where i can modify the MDN acknowledgement file by adding few more fields??
2. If not please suggest me how i can proceed with this.
Note: We should not use by creating one more msgtype in SAP and send back the acknowledgement like Orders response(ORDRSP). They just want the file from XI itself.(But not from SAP Side).
Regards
Seema.
Edited by: Mike Pokraka on Jul 24, 2008 1:43 PM

Hi Reddy,
If ur problem is solved can u plz help me?
I have one question related to the MDN .
My scenario is like AS2 adapter is on the receiver side means its converting XML to EDI format. When the payload along with MDN is sent from the XI side EDI partner , the EDI partner sends back the MDN acknowledgment back to XI.
The problem is that XI is not able to accept the MDN acknowledgment.
Could you please suggest what all steps need to be configured to receive that MDN acknowledgment on XI side.
e.g 1)AS2 Communication channel with message protocol REPORTS
2)Sender agreement for accepting the acknowledgment
3) What type of message interface is to be used which is required in the configuration step for sender agreements(MDN specific format??)
4) Any other configuaration required ??
Please reply as soon as possible.
With regards,
Simran

Color Space Issue with Wide-Gamut monitor

Since getting my new (and carefully calibrated) LaCie 324 monitor, I have noticed that RAW (and maybe other) images exported from Lightroom as
sRGB jpegs look washed out and slightly green when viewed outside of Lightroom (IE8, Firefox, ACDSee, windows 7 viewer). It seems not to matter whether the external application horors embedded color space profiles or not, since the unmanaged ones assume sRGB.
When I bring one of these jpegs into PhotoShop it still looks bad, and not what I see in Lightroom. However, if I Assign the Adobe RGB profile to the image, it immediately looks like the Lightroom version. And if I then Convert that image to sRGB and save it, it looks fine everywhere, even on an uncalibrated standard Dell TN LCD display.
Any ideas what I might be seeing here. A friend with the same monitor has the same problem, which is what is leading me to suspect the monitor.
The first image here is converted from Lightroom with sRGB color space. The second was first assigned the Adobe RGB color profile and then converted and saved out again as a jpeg.
Converted Only

I downloaded and ran the program. My version number appears to be 2.1 if I read the numbers right.
I am still at a loss as to why my sRGB jpegs only look right if I assign the wrong profile to them.
Here are the settings in Windows 7 for color management. The highlighted profile is the one just created for my monitor. Display 2 is my main display. Note the "viewing conditions" setting on the advanced tab. Do you think the rendering intent might be at fault here? In Lightroom, should I use Perceptual over Relative or vice versa?

Issue with AS2 Adapter monitoring

Similar Messages

Maybe you are looking for