Slow seller management in BI

Hi all,
Anybody have idea about How to implement Slow seller Management in SAP Retail in BI?
Any doc which explains how to proceed about the same.
Regards
R@ngzz

Hi ,
Thanks Raja for your clear expalnation...
What I know is Slow seller management is a part of MAP...We need to implement this planning function BI in order to get slow seller management..Please correct me if I am wrong.. But not getting info to implement the same....
Tomer,
I don't have scenario as such..., I am new to this slow seller management..
This is with respect to Retail business...
Please explain me if you have any business scenario in your implementation...
Regards,
Rangzz
Edited by: Ranganath Kodiugane on Feb 4, 2009 6:50 AM

Similar Messages

  • Stock aging + Slow Seller Management

    Hi,
    could anyone give me a tip on how to reproduce Stock Aging ( inside Merchandise & Assortment Planning  ) in order to combine it with Slow Seller Management?
    Thanks in advance
    Fabricio Granja

    Hi Fabrizio,
    What are you trying to achieve with this?
    Reason I ask is that the slow seller analysis transaction in slow seller management checks the sell-throughs of the relevant articles and, based on planed vs. actual sell-through, proposed markdowns (ie. I don't think you need to worry about getting stock aging details into slow seller management - the process is self-contained).
    Thanks,
    Steve

  • Slow seller analysis for generic / variant articles

    Hi all,
    We are having issues getting slow seller analysis to work for generic variant articles.
    We have created a generic with variants of a certain colour and size.  We have attached a markdown profile to one of the variants and transferred this to BI (the profile in BI is assigned to the generic at for a specific colour and size).  We have then loaded sales and goods receipt data for the variant article into the relevant cube in BI.
    When we execute the slow seller query directly in BI (trans RSRT1) it is correctly retrieving the sales and GR data at the generic / size / colour level, however when we execute the slow seller analysis using transaction /n/MAP/SSM2 we get no markdown proposals generate the the log returns a message that no data could be found.
    We have implementation the best practice building block however can't identify why no data is found for our selection criteria.
    Does anyone have any documentation (apart from the best practices documentation) on how this needs to be set up?
    Many thanks,
    Steve

    The problem is also described and answered within OSS Note Nr. 0000561477 for Year: 2009. Name: Slow seller analysis not picking up variant articles
    Bottom line of this problem is:
    I analyzed the data in cube  
    0RMP_MC21. The movement data of seasonal merchandise (generic articles)
    is expected to be stored in this cube on the level generic/color/size.
    This is controlled via MAP foundation. In this case, the slow seller  
    report can evaluate the data and propose markdowns. Unfortunately, the
    data in your cube 0RMP_MC21 is stored on variant level (material      
    number). You can verify this by running the query 0RMP_MC21/          
    0RMP_MC21_Q0020. In contrast to the screenshot you provided as an     
    attachment, this query doesn't give you values for article 400018 on  
    the level color/size, but only for the variants. Therfore, the slow   
    seller report won't find the data.                                    
    If you ensure the update of the cube according to the MAP foundation  
    (0material is filled with generic article), then the slow seller      
    analysis will pick up the variants as expected. 
    Post is answered!
    Regards,
    Markus
    Edited by: Markus Semar on Jun 18, 2009 6:00 PM
    Edited by: Markus Semar on Jun 18, 2009 6:03 PM

  • Slow profile manager

    Hi gurus!
    Got a clean install of server 10.7.4 with all updates done. DNS and Opendirectroy are runnung ok and I have no firewall.
    For some reason, Profile Manager is terribly slow; it takes him up to 10 minutes to update a workstation; is that normal?
    I'm working at night with no traffic on the network, testing 4 machines out of 70.
    I've also seen that the devices can be set to be update manually; is that a good option. If yes, can you force that from the workstation or is it pushed by the slow server?
    I'm still hesitating to implement this in our school, can anybody give me a strong advice, like "don't use it" or "great stuff" ?
    Help and shared experience would be much appreciated.
    Thanks, Guy

    Hi,
    Thanks for your feedback and sorry for the late answer. In facts, doing that operation takes ages…
    Somehow it is as if a firewall (there's none) was blocking something. If you look at the attached screenshot you'll notice that this simple "update info" operation is really slow. I don't know what those values should be or what they are on your server.
    Is there any error log… I don't think so…
    Thanks for your feedback on that, Guy

  • Slow workgroup manager, slow screensharing, slow account management

    Hi,
    At home on my Mac Mini Server, i try to connect to the workgroup manager. It works but it need a lot of time to connect. During this time, i get certain times this error in the log message:
    DirectoryService[29]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database)
    DirectoryService[29]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server ldap/[email protected] not found in Kerberos database)
    Is there something i can do to fix that problem. Because i think this is the reason why it's so slow.
    Greetings Roger

    archiving the ldap directory, demote to standalone, "remote" to OD Master, followed by restoring the LDAP directory did the trick to me.
    I have been mad at WGM for months and stumbled on this tip and it fixed all my problems!
    see here:
    http://discussions.apple.com/thread.jspa?threadID=1520446&tstart=66

  • Extreamly slow container managed persistence

    Hi.
    We perform the following procedure:
    1. We invoke a finder method on a container managed bean
    2. Then we traverse the enumeration of beans returned and invoke a getter
    method to get their properties.
    The finder finishes really fast, but then traversing the enumeration takes
    about 1 second per entity bean.
    Any suggestions?
    Giora Katz-Lichtenstein

    Hi,
    When you're iterating through your collection or enumeration of primary
    keys, each method call is going to the database to retrieve the row
    associated with that primary key. I'll bet the issue is with the calls to
    the db or whatever persistent store you're using.
    Steve...
    Giora <[email protected]> wrote in message
    news:82kolv$192$[email protected]..
    Hi.
    We perform the following procedure:
    1. We invoke a finder method on a container managed bean
    2. Then we traverse the enumeration of beans returned and invoke agetter
    method to get their properties.
    The finder finishes really fast, but then traversing the enumeration takes
    about 1 second per entity bean.
    Any suggestions?
    Giora Katz-Lichtenstein

  • SAP MAP - Merchandise and Assortment Planning

    Hi Everyone,
    I'm responsible for Merchandise and Assortment Planning. It is a new solution, based in SAP BW especially for SAP Retail Fashion Loop.
    I'm looking for people, who were involved in such a project and could help me.
    Does anyone know anything about Relase Workbench in SAP MAP (transaction starts with UPARI*),  BAdI's for Slow Seller Management, Open To Buy, Markdowns Proposals - Template Implementation, their methods and parameters.
    Any help will be appreciated.
    regards
    Krzysztof

    Dear Krzysztof,
    Can you please mail me at [email protected] all MAP Releated document which has been prepared by you during your work?
    I am doing pre-implementation evaluation of SAP MAP for one of my client and need all the documents.
    I want to know first prerequisites details in terms of
    system details such as their vesrion, their EHP, theri Support Package Stake, BI and Retail content if any
    SAP Retail functionalities such as Assortment, Article Hierarchy, Merchandise Distribution, Promotion etc.
    I want to know system landscape such what are systems involved such as SAP Netweaver, SAP ECC, SAP PI/XI, any legacy system.
    prior to implement SAP MAP.
    Thanks,
    Ashish Kumar

  • Satellite C55D-A-149 - Windows 8.1 depressingly SLOW

    Hi, I was asked by Toshiba USA to post this here as my laptop is an European model.
    I recently got this laptop, so it is still new and so is the installation.
    The laptop is TOSHIBA SATELLITE C55D-A-149. I realise that this is a budget laptop and the processor is fairly weak. But still it came pre-installed with Windows 8.1 and afaik isnt Windows 8.1 optimised for slow laptops/tablets but mine is performing really poorly.
    Startup is slow, file manager is slow, minimizing a window takes forever and so on.
    In order to find out where the problem lies I ran a cross platform benchmark on my machine i.e. on Windows and on Ubuntu linux. I used a live CD to run linux without installing it. The benchmark tool used was Geekbench3: http://www.primatelabs.com/geekbench/
    The results of the benchmark can be seen from here: http://browser.primatelabs.com/user/87755
    And it is clear how lagging Windows 8.1 is.
    What is the reason for this very poor performance?
    If Windows 8.1 really is the problem would it be better for me to remove this and install Windows 7? But I dont want to lose my genuine copy of 8.1 as this is what ensures the next free Windows 10 upgrade. Is there any way to partition the hard drive and not lose the recovery partition?
    What are my options now

    Hi
    From my point of few the system is muddled up and i would recommend you to reset the Win 8.1 system to the default settings
    This is not very complicated but before doing this, I recommend you to backup your personal data.
    Microsoft has published short instruction how to do that. Take a look here:
    http://windows.microsoft.com/en-us/windows-8/restore-refresh-reset-pc
    I would recommend you to test the first option without affecting the files. In case this does not solve your issue, check the 2nd option: Recovery.

  • Anyone use nio-memory-manager ?? what's it good for?

    Can someone give me an example of when the nio-memory-manager should be used?
    Thanks,
    Andrew

    If I remember the outcome of my experiments with NIO right the situation is as follows:
    1. Allocating/releasing huge shared memory blocks over and over can lead to OS/JVM issues. To avoid this I allocated the max size I wanted from the start (this is an option when configuring "off-heap" storage I believe). When doing it this way I had no reliability issues with the NIO memory manager in my tests.
    2. Tangosol/Oracle used to claim that the off-heap (NIO memory manager) result in worse performance than on-heap - I could not see any clear indication of this but this may be application dependent. For our app the reduced number of JVM:s per server (reducing network communication, number of threads, risk of any JVM performing GC at a given time etc etc) seemed to more than offset the allegedly slower memory manager resulting in MUCH BETTER performance! A lot of queries etc anyhow (at least for us) mainly work against indexes that always are stored "on-heap"...
    3. There is a limitation to 2Gb per NIO block (at least in 32-bit JVM:s not sure about 64:bit - never seen any point in using them since larger heaps than 2Gb seldom work well anyhow and each pointer consumes double the space in heap and CPU-caches) but this is for each CACHE and separate for PRIMARY and BACKUP I believe! So my understanding is that if you (using 64-bit OS) for instance have two (equally big) caches you could allocate max 2 * 2 * 2 = 8Gb of off-heap memory for folding data per JVM (without ANY impact on GC-pauses!) and in addition to that use as much heap as you can get away with (given GC-pause times) for holding the indexes to that data. This would makes a huge difference in JVM count!- for example we today have to run like 10+ JVM:s per server using "on-heap" while we using "off-heap" storage probably could get that down to one or two JVM:s per server!
    4. There may be both OS and JVM parameter that you need to set (depending on OS and JVM used!) in order to allocate large amounts of shared memory using NIO (the default is rather small).
    As for the question about de-allocation I never saw any sign of memory leaks with the NIO memory manager (i.e. space previously occupied by deleted objects were reused for new objects) but as I mentioned above you better allocating the max size NIO memory block you intend to use up-front and that memory will then remain allocated for this use so if your amount of cache data vary and you would like to use memory for other purposes (like heap!) at some point you may be better of sticking with "on-heap" that is more flexible in that respect.
    As I previously mentioned off-heap is today (until Oracle fixes the improvement request!) really only an option if you do not plan to use "overflow protection" or your objects are fixed size :-(
    And if you are interested in using servers with a lot of memory and would like to use "off-heap" please talk to your Oracle sales rep about it! If enough people do that it may allow the Coherence developers to assign more time for making "off-heap" storage better! With this feature in place Coherence will be even more of a "killer application" than it already is!
    Best Regards
    Magnus

  • Data manager navigation performance

    Hi Gurus,
    I have some issue with slow data manager navigation.  The packages themselves run perfectly fast, but such things as opening the package list or validating a transformation file takes a huge amount of time.  Does anyone have any experience dealing with this and have any ways of improving it?
    Initially I thought it was my laptop but it is being experienced universally.
    Cheers,
    Chris

    Hi Ethan,
    Take a look at one of the allocation script: http://pastebin.com/TA16xCd3
    We are testing RUNLOGIC but we are facing some problems in two situations:
    - passing the DM package variable to the RUNLOGIC script
    - using a passed variable in the called script
    The DM prompts for 3 selections: ENTITY, TIME and CATEGORY.
    The RUNLOGIC script:
    *SELECT(%DIVISIONS%,"[ID]",DIVISION,"[LEVEL]='DIV' AND [STORECOMMON]<>'Y'")
    *SELECT(%BRANCHES%,"[ID]",BRANCH,"[BRANCHTYPE]='STORE'")
    *START_BADI RUNLOGIC
         QUERY=OFF
         WRITE=ON
         LOGIC=ALLOC_DIV_ACTUAL_S.LGF
         DIMENSION ENTITY=C1000
         DIMENSION TIME=FY10.MAY
         DIMENSION CATEGORY=ACTUAL
         DIMENSION DIVISION=%DIVISIONS%
         DIMENSION DIVISION=%BRANCHES%
         CHANGED=ENTITY,TIME,CATEGORY,DIVISION,BRANCH
         DEBUG=ON
    *END_BADI
    In ALLOC_DIV_ACTUAL_S.LGF, we are using a %DIVISION_SET% variable. At the time of validating, we get a message "Member "" does not exist".
    When we run the package, it fails with the same error message:
    An exception with the type CX_UJK_VALIDATION_EXCEPTION occurred, but was neither handled locally, nor declared in a RAISING clause
    Member "" not exist
    Thanks
    Regis

  • Enterprise Iphone Management

    Hello,
    We are new to the group and appreciate any help and advice.
    We are looking for the most stable central operation solution for managing Iphones in an enterprise.
    Is there a native enterprise solution from Apple that does not require third party support?
    The only way we can sell managing mobile devices to our executive management is if we can manage with apple tools only and Not third party.
    We would like to be able to provision Itunes and iOS updates, enforce encryption, enforce profiles, etc.
    Any suggestions are very much appreciated.

    Take a look at http://www.apple.com/iphone/business/resources/
    Good luck.

  • Can anyone tell me where to see OSS notes

    Hi
    Can anyone tell me where to see composite OSS note 586163 (any OSS notes). In which site and in which category i should search.

    www.service.sap.com
    SAP Support Portal
    Quick Lnks :
    Search for OSS notes.
    You need to have a login..its not free.
    After login - Help & Support - Search for SAP notes
    <b>
    Anyws here is the note</b>
    Summary
    Symptom
    You are transferring data from SAP R/3 Inventory Management to the BW system. You get unexpected data or data that differs from the data in the analyses in the R/3 system.
    This note should help you to analyze this problem.
    Other terms
    2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 2LIS_03_S195,
    2LIS_03_S196, 2LIS_03_S197, 2LIS_03_S198, 0IC_C01, 0IC_02, 0IC_C03,
    0IC_MC01, 0IC_MC02, 0IC_MC03, stock analyses, inventory management,
    Non-cumulative InfoCubes, stock key figures, stock, stocks,
    RMCBINIT_BW, RMCBNERP, RMCBNEUA, consistency,
    data consistency, healthcare, health service
    Reason and Prerequisites
    This note provides an overview of the release strategy, sources of information, tips and tricks, and known errors for this subject area.
    Solution
    Contents
    1. Release strategy
    a) General information
    b) Recommended objects for BW Releases 3.0B, 3.1 Content and 3.2 Content
    c) Recommended objects for BW Releases 2.0B and 2.1C
    d) Obsolete objects
    e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
    2. Sources of information
    a) BW technology
    SAP BW online documentation
    "How to" documents
    b) Business Content
    Online documentation for BI Content
    Extraction Documentation:
    "How to" documents
    Plug-In information
    3. Extracting non-cumulative data from R/3
    a) Explanations for the extraction
    b) Known errors
    Stocks (2LIS_40_S278/2LIS_03_BX)
    Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
    Industry-specific notes
    4. Technical information regarding non-cumulative info cubes in BW
    a) Warehouse Management
    b) Queries
    c) Update rules
    d) Known errors
    5. Stock Analyses in BW
    a) Explanations on data flow
    b) Known errors
    c) Tips and tricks
    6. Performance
    1. Release strategy
    Use the following objects depending on your BW and R/3 or plug-in releases:
    a) General information
    The following basic principle applies: The 0IC_C03 InfoCube (material movements) replaces the 0IC_C01 (material movement plant) and 0IC_C02 (material movements storage location) InfoCubes. The 2LIS_03_BX (material stocks) InfoSource or DataSource replaces the 2LIS_40_S278 (transfer BW: stock) 2LIS_03_S197 (material stocks storage location) and 2LIS_03_S198 (material stocks plant) InfoSource or DataSource. The 2LIS_03_BF (material movements) InfoSource or DataSource replaces the 2LIS_03_S195 (material movements storage location) and 2LIS_03_S196 (material movements plant) InfoSource or DataSource.
    We therefore STRONGLY recommend that you use the OIC_C03, 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM objects. We will continue to deliver and support any other objects mentioned in this note, but only for reasons of downward compatibility. These objects will not be enhanced because they are based on obsolete technology.
    For information about the general support for DataSources based on information structures, see also Note 543002.
    As of PI 2002.2, the 2LIS_03_BX DataSource is available for Release 4.0B and higher.
    As of PI 2001.2, the 2LIS_03_BF and 2LIS_03_UM DataSources are available for Release 4.0B and higher.
    The 0IC_C03 InfoCube is available as of Release 3.0B.
    b) Recommended objects for BW Release 3.0B and higher
    InfoCube: 0IC_C03 (Material movements)
    InfoSources and update rules:
    2LIS_03_BX (stocks) - available for Release 3.0B as of Support Package 10
    2LIS_03_BF (movements)
    2LIS_03_UM (revaluations)
    If your Support Package version for Release 3.0B is Support Package 9 or lower, you have the alternative option of using the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons stated above, we recommend that you change to 2LIS_03_BX as of Support Package 10. For more information, see Note 588015.
    c) Recommended objects for BW Releases 2.0B and 2.1C
    InfoSources: 2LIS_03_BX (stocks) - available for Release 2.0B as of Support Package 30
                                    - available for Release 2.1C as ofSupport Package 22
                2LIS_03_BF (movements)
                2LIS_03_UM (revaluations)
    If you are using Release 2.0B Support Package 29 or lower or Release 2.1C Support Package 21 or lower, you can alternatively use the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons given above, we recommend that you change to 2LIS_03_BX as of Support Package 30/Support Package 22. For more information, see Note 588015. Unfortunately, we cannot provide the 0IC_C03 InfoCube and related update rules. If you need to use this InfoCube, we can provide a similar solution to the one provided for Releases 3.0B or higher as part of a consulting project. Note that Note 589024 does not apply in this case.
    d) Obsolete objects
    If you are using R/3 Release 3.1I and do not intend to upgrade to a higher release (regardless of the BW release) in the foreseeable future, use only the 0IC_C01 and 0IC_C02 InfoCubes and the related InfoSources or DataSources 2LIS_03_S195 - 2LIS_03_S198. If you are using the Healthcare industry solution and are interested in using the 0IC_C01_Q0020 and 0IC_C01_Q0021 queries, you can also use the 0IC_C01 InfoCube and related objects. Unfortunately, there is no automatic data migration for the transition from 0IC_C01/2 to 0IC_C03. See also Note 804781 for a complete overview of all key figures in 0IC_C03 that are also possible in 0IC_C01/2.
    e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
    For more information, see Note 591063.
    2. Sources of information
    The main sources of information are located in the BW online documentation in the BW section of the SAP Service Marketplace and in the IMG documentation for the Plug-In. Other useful information is contained in various notes. These notes are listed under headings 3 - 6 below.
    a) BW technology
    This area contains documentation on the technical mapping of stock analyses in SAP BW.
    Online documentation SAP BW (http://help.sap.com)
    -> Documentation -> SAP NetWeaver -> '04
    -> Information Integration -> SAP BW
    i Stocks
        -> BI Platform -> OLAP
        -> Performance Optimization -> Stocks
    ii Validity Table
        -> Data Warehousing
        -> Administrator Workbench -> Modeling -> InfoCube
        -> Additional functions for InfoCube maintenance
        -> Stock Parameter Maintenance
    iii Compression
        -> Data Warehousing
        -> Administrator Workbench -> Data Warehouse Management
        -> Process Management
        -> Managing Data Targets
        -> Managing InfoCubes -> InfoCube Compression
    iv Aggregation
        -> Data Warehousing
        -> Administrator Workbench -> Modeling
        -> InfoObject -> Create InfoObject: Key Figure
        -> Aggregation v Exception Aggregation
        -> BI Platform -> OLAP
        -> Special OLAP Functions and Services
        -> Aggregation
        -> Scenarios for the Use of an Exception Aggregation
    "How to" documents
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> In the information index: N ("Non-cumulatives") ->
    "Non-Cumulative Values 3.x (ppt)"
    b) Business Content
    This area contains the business content representation of stock analyses in SAP BW, based on the SAP R/3 process and object model.
    Online documentation for BI Content (http://help.sap.com)
    -> Documentation -> SAP NetWeaver -> '04
    -> Information Integration: BI Content
    -> BI Content -> Supply Chain Management
    -> Supply Chain Performance Management -> Inventory Management
    Documentation for extraction (OLTP system)
    -> Transaction SBIW
    -> Business Information Warehouse
    -> Settings for application-specific DataSources
    -> Logistics
    Here you will find the relevant documentation for each of the relevant nodes.
    "How to" documents
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> in the information index: N ("Non-cumulatives") ->
    "How to... Handle inventory management scenarios in SAP BW 3.x" (pdf)
    Plug-In information
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW Extractors - Plug-in
    3. Extracting non-cumulative data from R/3
    This section explains the extraction process in the R/3 system and it gives an overview of known errors and their solutions.
    a) Explanations for the extraction
    Determining transaction keys
    Note 492828
    Determining the component
    When stocks are initialized, the 'MM' core application is transferred, regardless of which component you specify in Customizing under 'Specify Industry' (TAC MCB_). You must implement Note 323018 for this purpose.
    In most cases, the 'MM' Core application is also used when you initialize documents and for the delta load. However, 'IS-R' is transferred as the component if Retail is set as the component and you are working with stock transfers or movements for material group articles (MATNR <> MATBF).
    To create the component, the BW enrichment is required during extraction. For more information, see Notes 315880 and 353042.
    The "GETSYSDEF" report provides the system setting.
    Creating non-cumulative relevance
    In general, the non-cumulative relevance is set to '1', meaning 'relevant'. The exceptions are consumption postings (BSTTYP = V and BSTAUS = V) and postings for material group articles (MATNR <> MATBF). Value '2' is assigned in these cases.
    Logistics data extraction: Customizing Cockpit (transaction LBWE)
    You can configure the 2LIS_03_BF und 2LIS_03_UM DataSources in application 03. You cannot configure the 2LIS_03_BX DataSource in the Customizing Cockpit. To activate the 2LIS_03_BX DataSource, see Note 631345.
    Generic extraction of stocks
    This function is available as of PI 2003.1. For lower release levels, a consulting solution can be implemented on request (contact SAP in this case).
    User exit (SAP enhancement RSAP0001)
    Note 413807
    Update methods/extract structures/XPRAs
    i  Update methods (V3 update, DeltaQueue, and so on).
    Notes 380078, 396647, 486784 and 505700.
    For information about the automatic conversion of update methods in the logistics extraction, refer to the release notes for plug-in 2003.1
    DataSources for application 03 are delivered by default with the "Unserialized V3 Update" method.
    A change to "Queued Delta" may occur.
    For performance reasons, you should not select "Direct Delta".
    ii Changes to extract structures/XPRAs
    Notes 328181, 489259, 511657 and 566917.
    If you try to add another field from the pool to the "2LIS_03_BF" DataSource , the system issues error message "D0 322".
    Possible reason:
    XPRA "RMCSBWXP_IM_01" did not run after you imported the plug-in. This XPRA is responsible for comparing customer fields in the extract structure (enhancement) with new default fields in the extract structure (SAP). This error message appears as a result.
    b) Known errors
    Stocks, movements and revaluations are transferred to BW using various extractors. All known errors and proposed solutions of these three extractors are listed below.
    Stocks (2LIS_03_BX/2LIS_40_S278) -> see Note 691228.
    i Rounding error/valuation at company code level
        Notes 663681 and 762219
    ii Project stocks
        Note 535657
    iii Valuated sales order stocks or project stocks
        Notes 487043, 616119, 674351 and 756151
    iv Vendor consignment stocks
        Notes 585619 and 726485
    v Special stocks for customers/vendors
        Note 533682
    vi Valuation class
        Note 684789
    vii Stock in transit
        Notes 767786 and 898231
    Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
    i Delta ability/procedure
        Notes 385703 and 581778
    ii Update methods (V3 update, delta queue, qRFC and so on)
        Notes 339691, 444261, 498484 and 631562
    iii Missing BW derivation (component,
        transaction key, and so on)
        Notes 315880 and 353042
        Caution: You MUST read these notes
        BEFORE you transfer data to the BW system.
    iv Movements (2LIS_03_BF)
        - Returnable packaging with customer
          Notes 512597 and 530730
        - Vendor consignment
          Notes 585139 and 607710
        - Project stocks
          Note 522770
        - Stock transfers
          Notes 399929, 557378 and 628090 (stock in transit/
          valuation type)
        - Purchase orders with account assignment (consumptions)
          Notes 587320 and 629726 (non-valuated materials,
          see also Notes 752607 and 790506)
        - Batches
          Notes 445632 and 685450
        - Incorrect stock type
          Notes 438649 and 451355
        - Customer consignment
          Note 563342
        - Incorrect / missing valuation class
          Notes 735425, 747581 and 770858
        - Returns (movement types 122/123)
          Notes 741396 and 763424
        - Profit center
          Note 769660
        - Subsequent adjustments
    Note 822396
    v Revaluations (2LIS_03_UM)
        - Incorrect update because the
          BSTAUS and BSTTYP fields are missing
          Notes 494288 and 675610
        - Missing BW derivation of characteristics with settlement ofrequests
          Notes 523298 and 747361
        - External display of the WBS element does not exist
          Note 512611
        - Incorrect transaction key during setup
          Note 587241
        - Incorrect sign
          Note 587283
        - Duplicate document for MR22
          Note 587304
        - Incorrect/missing document number
          Notes 489290, 500825, 507958, 521046, 619482,
                  667534, 739050, 839711, 845307, 856669 and
                  864630
        - The BUZEI field is not filled
          Note 599731
        - Currency field not filled
          Note 612131
        - Returns (movement types 122/123)
          Note 715176
        - Reconstruction report RMCBNERP
          Note 735209
        - Missing valuation class
          Note 837052
    vi Master data (0STOCKTYPE/0STOCKCAT)
          Note 766954
        - 0STOCKCAT_TEXT is not filled since the value 'U' has not been added to the BSTTYP domain.
          Note 907195
    Industry-specific notes
    i IS Retail
    - Revaluation at retail (2LIS_40_REVAL)
    Notes 533577 and 600460
    - Miscellaneous
    Note 841878
    ii IS Oil/IS Mine
    - G/L quantity for two-step stock transfer procedure
    Notes 608744, 608975 and 629320
    4. Technical information regarding non-cumulative info cubes in BW
    In addition to the relevant sections in the online documentation, there are a number of explanatory notes that will help you to analyze problems. Section 4 e) deals with known errors and proposed solutions.
    a) Warehouse Management
    Validity table: Notes 360249 and 534865
    Selective deletion: Note 510680
    Aggregates: Note 456359
    ODS capability: Notes 322303, 323811, 385099, 417703, 581778,
    747037, 752492/782314 and 773823
    DataMart/Open Hub capability: Notes 375098, 566145 and 566762
    Compression (updating the stock marker)
    ->>> ESSENTIAL INFORMATION <<<-
    You can see in the log whether or not the stock marker was updated during the compression (as of 3.0B Support Package 13)
    For example:
    "START cond CUBE IC11 at 165446 on 20030514 maxreqid 23282 maxcnsid 0 refpoint update + null elim" ->
    "refpoint update" or "no refpoint update" provides the relevant information.
    See Notes 613701 and 639253 if you are using Oracle 9.
    Also see Notes 643687 and 655798.
    For a BW system with several application servers, see also Note 834829.
    ->>> ESSENTIAL INFORMATION <<<-
    b) Queries
    -> For information about the recommended procedure for analyzing query problems see the following note: Note 370004
    Slow-moving item/slow seller reports: Note 541559
    A How to document is also available:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> in the information index: M ("MultiProviders") -> "MultiProviders (incl. Slow Moving Item Scenario) ..."
    c) Update rules
    The following special features are provided for updating in non-cumulative cubes:
    The non-cumulative key figure has to be included with the relevant cumulative value(s) in the InfoCube definition.
    Only receipt key figures are provided for updating from the InfoSource with the stocks.
    The issue and receipt key figures are provided for updating from the InfoSource with movements.
    Therefore, from a technical point of view, stocks are written to the receipt key figure. The process of differentiating between the stocks and the remaining receipts then takes place in the InfoCube using record type = 1 (InfoObject: 0RECORDTP) in the technical dimension table (this also sets up the connection to the validity table).
    The OLAP processor dynamically calculates non-cumulative key figures in the query (taking into account the issues/receipts and the validity table).
    d) Known errors
    Warehouse Management
    i Loading data
         Notes 534865 and 529610
    ii MultiCube/MultiProvider
        Note 435227
    iii Compression (updating the stock markers)
        Notes 613064, 613701 and 615349
    iv Updating
         Note 574341
    Queries
    i Fiscal year variant characteristic (0FISCVARNT, 0FISCPER
    and 0FISCYEAR)
        Note 490067
    ii Exception aggregations
        Notes 145630 and 607608
    iii No/multiple time restrictions
         Note 388983
    5. Stock Analyses in BW
    This section explains the data flow in BW and provides an overview of known errors and their solutions. This section also explains certain limitations and workarounds for same.
    a) Explanations on data flow
    See the How to paper from Section 2 b)
    "How to... Handle inventory management scenarios in SAP BW 3.x" (PDF).
    Note that the 2LIS_03_UM can also be loaded before the 2LIS_03_BF.
    You will find further information on the SAP Service Marketplace:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW Business Content
    -> SAP Supply Chain Management
    -> Supply Chain Performance Management
    -> In the navigation area on the left: Related Topics
    -> Business Content
    -> Inventory Management.
    b) Known errors
    0IC_C03
    Notes 637927, 655798, 668085 and 710404
    0IC_MC01
    Note 664520
    Queries
    Notes 534429, 630034 and 676960
    c) Tips and tricks
    Analyses in BW with the storage location (0STOR_LOC) and stock characteristic (0STOCKTYPE) characteristics in the drilldown.
    Solution: Note 589024 (see also Notes 201327, 322335, 456106, 506077 and 543188) and the How to document
    -> http://service.sap.com/bw
    -> In the navigation area on the left: Services & Implementation
    -> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
    "How to... Realize summarized display of stock values on storage"
    Stock transfers in the two-step stock transfer procedure/differences between analyses in BW and the R/3 transaction MB5B
    If you notice different results for the issue and receipt quantities of the total stock during the analysis of stock transfers in the two-step procedure, for example, storage location to storage location within a plant (movement types 351 and 101), add the "0STOCKTYPE" characteristic to the drilldown. Where necessary, filter according to the values "A" (unrestricted) and "H" (transit). You will then find the same values under stock type "A" and in transaction MB5B (if you select the storage location stock or the valuated stock).
    Individual analysis of revaluations
    After stock is initialized using the 2LIS_03_BX InfoSource, load revaluations into the 0IC_C03 InfoCube with the 2LIS_03_UM InfoSource. By doing this, you avoid uploading movements with the 2LIS_03_BF InfoSource. If you do so, the non-cumulative values (quantities and values) can no longer be calculated. Reason: When you initialize stocks, DIM IDs are created for 0BASE_UOM and 0LOC_CURRCY. As a result, all stock markers for 0BASE_UOM have an entry other than ' '. With revaluations, only values are updated-all quantities and their units are updated with ' '. This means that you can no longer assign revaluations to the stock markers because the units of measure are inconsistent. Solution: Update the revaluations with quantities also, as you did for the values (the result for the quantities is always RESULT = 0).
    Incorrect results if quantity key figures and value key figures are analyzed together.
    For example, you only displayed quantity key figures in the current drilldown. If you now add value key figures, the quantity key figures are no longer calculated correctly (the reverse also applies). As in the case of individual analyses of revaluations, movements may not be assigned to the stock markers due to missing DIM IDs. As a result, stock cannot be recalculated correctly either. This should not usually occur when the 0IC_C03 InfoCube is filled with the 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM InfoSources (this is also the case with the other relevant Business Content InfoCubes, for example 0CP_IC_C1 or 0RT_C36/37). However, it may occur because of certain loading processes, for example. Solution: Update the quantities (or values) in the same way as the values (or quantities) (RESULT = 0 is always the result for the quantities or values). See Note 643291 for the 0CP_IC_C1 InfoCube.
    Enhancing the 0IC_C03 InfoCube with additional characteristics
    These additional characteristics must be updated from the 2LIS_03_BX InfoSource, as well as from the 2LIS_03_BF and 2LIS_03_UM InfoSources, only then can movements be assigned to stock markers (see the two preceding points).
    The following enhancements are possible:
    1. Valuation type (0VAL_TYPE)
    Source field from 2LIS_03_BX/BF: BWTAR
    2. Company code (0COMP_CODE)
    Source field from 2LIS_03_BF/UM: BUKRS
    3. Valuation area (0ID_VALAREA)
    Source field from 2LIS_03_BX/BF/UM: BWKEY
    4. Vendor (0VENDOR/0GN_VENDOR) - for vendor consignment stocks
    Source field from 2LIS_03_BX/BF/UM: LIFNR
    This is delivered with BI Content 3.3 Add-On (see SRM Business Content Online documentation).
    5. Customer (0CUSTOMER) - for consignment stocks at customer
    Source field from 2LIS_03_BX/BF/UM: KUNNR
    6. Sales order (0DOC_NUMBER/0S_ORD_ITEM) - for sales order stocks
    Source field from 2LIS_03_BX/BF: KDAUF/KDPOS
    7. Project number (0WBS_ELEMT) - for project stocks
    Source field from 2LIS_03_BX/BF: PS_PSP_PNR
    8. Evaluation class (0VAL_CLASS)
    Source field from 2LIS_03_BX/BF/UM: BKLAS (Note 684789)
    Enhancement possibilities for 2LIS_03_BX:
    Note that the 2LIS_03_BX DataSource cannot be extended in the same way as the 2LIS_03_BF DataSource, for example.
    Only SAP can enhance this DataSource (Note 684789).
    Other enhancements are no longer useful since fields, such as the movement type, G/L account or profit center do not in appear in the stock tables (for example, MARC and MARD) but only in the movement tables (for instance, MSEG).
    Evaluation restrictions that occur as a result (similar to the two preceding points) can only be resolved by a data enhancement (for example, reading from a DataStore object with all material movements) subsequent to the extraction or by not using 2LIS_03_BX. In both cases, all material movements must exist in the source system. If this is not the case, you must read from the corresponding archive files for the extraction.
    Changing the exception-aggregation of the stock key figures
    There is a predefined exception aggregation for stock key figures (for example, "last value") in the key figure definition. If you want to override these in the query definition, proceed as follows:
    -> Create a new calculated key figure.
    -> Drag the relevant basic key figure to the formula area.
    -> Choose "OK".
    -> In the next window, choose "Extend >>".
    -> Then, maintain the required exception aggregation and the reference characteristic.
    Mapping FIFO logic
    The data structures in the 0IC_C03 InfoCube allow FIFO logic to be mapped using the relevant query definitions. In this case, contact your SAP consultant.
    Unexpected or negative stock values due to FI document summarization
    If FI document summarization is activated for the MATNR field, revaluations (2LIS_03_UM) are transferred to BW without a material number. As a result, complete analyses are no longer possible at material number level. For more information, see Notes 36353 and 497992.
    Options for the R/3 and BW data verification/consistency check
    TAC MB5B <-> Queries 0IC_C03_Q???
    (Stocks/movements R/3 <-> BW)
    TACs MC.? <-> Queries 0IC_C03_Q???
    (Inventory controlling LIS <-> BW)
    Reports MBQUANT and RM07MMFI
    (verification of the R/3 data)
    Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
    With Note 766622 you can also create a LOG file for the extraction.
    Archiving
    See the corresponding "How to" document about archiving that is available on SAP Service Marketplace:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> in the information index: A ("Archiving")
    MultiProvider and non-cumulative key figures
    Note 690475
    Displaying the contents of the InfoCube with TAC "LISTCUBE"
    Note 629451
    Snapshot scenario
    The "How to" document mentioned in section 2 b) "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)" contains important information about the advantages and disadvantages of mapping stocks using a snapshot procedure.
    Validity period of stocks
    You can use transaction RSDV to determine the time period in which stocks can be calculated. This time period is determined automatically by the oldest and the most recent material movement. If you have a reporting requirement to display further stocks in the past, you can use the RSDG_CUBE_VALT_MODIFY report to manually change the time period.
    Evaluations of cross-company code stock transfers.
    Corresponding reports are currently not possible using the 2LIS_03_BX/BF/UM DataSources. For further information, see the following "How t"o document:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: Services & Implementation
    -> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
    "How to... Report on cross company stock in transit", which allows you to carry out evaluations in BW similar to the ones in R/3 transaction "MB5T".
    0IC_C03 data modeling
    Due to the different characteristic value calculation for stock quantities and values, a MultiCube scenario ("sparse tables") is useful in this case, one InfoCube for quantities and one for values.
    You can then execute common stock quantities, values and evaluations using queries on a MultiCube.
    The 0IC_C03 InfoCube currently uses a key figure model (various specific key figures, such as inspection stock, stock in transit and so on). In this case, an account model is suitable:
    - Three key figures: Stock quantity, stock value and valuated stock quantity (including the movement key figures)
    - Based on stock instance/type, you can then limit the query to the special stock
    - Advantage: Uses less database space
    - Disadvantage: The load for the OLAP processor is higher and there is more work during the query definition, the other approach may also be more transparent for the end user.
    Inventory management and ODS
    ODS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
    In this connection, you should use the ODS technology only for:
    - Document-related reporting or the Enterprise DataWarehouse layer based on the 2LIS_03_BX/BF/UM InfoSources (see Notes 581778 and 747037).
    - The implementation of a snapshot scenario; see the How to document mentioned in section 2 b) for more information:
    "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
    Implement Note 773823 to be able to update the 2LIS_03_BX InfoSource to an ODS.
    If you want to activate another ODS object for the 2LIS_03_BF and 2LIS_03_UM DataSources before the 0IC_C03 InfoCube, we recommend a parallel update.
    However, if you want the InfoCube to be filled by a subsequent update from the ODS, take the following into account:
    Documents that are entered after the stock initialization (CPUDT field > stock initialization key date) and are posted back to a period before the stock initialization (BUDAT field < stock initialization key date),
    must be updated with a delta request in the InfoCube, because only these requests can be compressed with a stock marker update.
    Therefore, mechanisms for which the movements are different before and after the stock initialization (as a result of restrictions on the posting date) are incorrect in this case. However, if you want to work with the requests in question, you must restrict the movements using the date of entry (CPUDT). Otherwise the stock evaluations will be incorrect due to the compression logic used.
    The same problem occurs if documents are posted to the future (CPUDT field > stock initialization key date and BUDAT field > stock initialization key date).
    Posting to a prior period and postings to the future
    If you can post this type of material documents in the system, take note of the documents that caused the initialization run (transaction MCNB, or report RMCBINIT_BW)during the reconstruction in R/3 (transaction OLI1BW, or report RMCBNEUA):
    1. BUDAT < stock initialization key date and CPUDT > stock initialization key date
    You execute the report with a date restriction (for example, upper limit = key date of stock initialization) to avoid a posting block.
    -> Postings to a prior period are selected by mistake.
    -> Solution: You MUST set a posting lock (if this is not possible, it may help to select according to the document number).
    2. BUDAT > stock initialization key date and CPUDT < stock initialization key date
    Here the same applies as described under point 1, however, the documents are then missing in the setup table. You can still make restrictions according to the posting date but you must set a relatively high upper limit.
    Consumption key figures in 0IC_C03 (the same as LIS reports)
    See Note 804781.
    Avoiding data inconsistencies, HASH solution.
    See Note 838050 for more information.
    Connection between transaction keys and reversals. See Note 352344 (and an example in Note 745788).
    Suppressing the display of the previous period in the BEx Web Analyzer.
    See Note 623944.
    6. Performance
    a) General BW/logistics extraction (TSV_TNEW_PAGE_ALLOC_FAILED/ SYSTEM_IMODE_TOO_LARGE)
    Notes 409641, 417307, 419465, 548845 and 589997
    b) Extraction 2LIS_03_BX
    The recommended setting in the RMCBINIT_BW report for 'Number of data records per LUW' is 5000. Higher values may cause the following errors:
    TSV_TNEW_PAGE_ALLOC_FAILED
    TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
    TSV_LIN_ALLOC_FAILED
    You can reduce an extremely long runtime by setting up the stock individually for each plant. For more information, see Note 728360.
    When you run the report, the "Transfer Zero Stocks" option must NOT be active, because this will significantly increase the runtime.
    This is no longer required as of Note 823951 (for more information, see Note 655798).
    c) Extraction 2LIS_03_UM
    Notes 537235 and 585750
    d) Extraction 2LIS_03_BF
    Note 454267
    e) Warehouse
    Due to the stock marker generation technology, it is normal for the E table to be larger than the F table in the non-cumulative InfoCubes.
    As a result of the different updating of stock quantities and values (see Note 589024) required by the R/3 data model, movement data usually generates two entries in the F table.
    To reduce the data volume of the 0IC_C03 InfoCube, you can distribute quantity and value key figures to two InfoCubes. As a result, the key figures have the same characteristic value update again. You can then use MultiCubes to execute common evaluations of quantities and values.
    f) Queries
    Notes 419490 and 784682
    Message was edited by:
            Jr Roberto

  • Error trying to print report to both pdf and network printer

    Hi all,
    When trying to print a report to my network printer or to pdf I get the two errors attached, one right after the other.  The resulting pdf or hard copy has almost everything in it, except for three tables which are completely missing.  When I go back into the report and open the page with the missing table, the table is no longer visible in the report and I get the second error again.  Exiting and restarting diadem brings the tables back.
    I've found several threads about pdf and other print errors and tried the solutions there to no avail; specifically the one posted here.
    I hope there is a fix to this!  These reports are intended to sell management on diadem! Thanks!
    OS Info:
    Windows 7 64 bit SP1
    18GB RAM
    DIAdem Info:
    Version: 11.3.0f4563
    USI:       1.9.1f4681
    DataFinder:  3.0.0f4681
    Script Engine:
    5,5,0,5207
    Debugger: 6,0,0,8424
    CLAD
    Solved!
    Go to Solution.
    Attachments:
    diadem print error 6-7-12.png ‏17 KB
    diadem print error two .6-7-12.png ‏15 KB

    Hello testingHotAir,
    Just to make sure, do you have administrative privileges for this machine?
    Also, you have attempted these exact steps as posted by lerman?
    Make sure that you are logged in as Windows administrator.
    Click the Windows button and click Printers.
    Right-click the Diadem pdf Export and select Properties
    Click the Ports tab, then click the Add Port button.
    Note: If the Ports tab is greyed out, right-click the Diadem Pdf Export icon and select Run as admin.
    Select Local Port and click the New Port button.
    Enter PDF1 for the new port name and click OK. Close the Printer Ports window.
    Put a checkmark in the box next to the PDF1 port if it is not already checked.
    Click on the Advanced tab.
    Select the Spool print documents radio button to make the options below it clickable.
    Clear (uncheck) the box labeled Enable advanced printing features by clicking it.
    Select the Print directly to printer radio button to make the options below not clickable.
    Click the Apply button, then click OK.
    Important: In order for the changes to take effect, you must restart your computer.
    Reboot your computer and then try to print, email, or create a pdf from Diadem.
    Regards,
    Jeff L.
    Applications Engineer | National Instruments

  • Xorg segfault in gnome 3

    This week xorg crashed a couple of times, I am trying to find out why but I do not know where to start looking.
    I am using xorg with gdm and gnome 3.
    It just happened again, so I gathered some data I thought might be usefull.
    The crash:
    Backtrace:
    [ 219.680] 0: /usr/bin/Xorg (xorg_backtrace+0x37) [0x81c00d7]
    [ 219.680] 1: /usr/bin/Xorg (0x8048000+0x17bc1a) [0x81c3c1a]
    [ 219.680] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb784040c]
    [ 219.680] 3: /usr/lib/xorg/modules/extensions/librecord.so (0xb7370000+0x214f) [0xb737214f]
    [ 219.680] 4: /usr/bin/Xorg (_CallCallbacks+0x3c) [0x807afbc]
    [ 219.680] 5: /usr/bin/Xorg (WriteToClient+0x273) [0x81c3353]
    [ 219.680] 6: /usr/lib/xorg/modules/extensions/libdri2.so (ProcDRI2WaitMSCReply+0x70) [0xb7360fa0]
    [ 219.680] 7: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2WaitMSCComplete+0x73) [0xb735f243]
    [ 219.680] 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb72e6000+0x2419b) [0xb730a19b]
    [ 219.680] 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb72e6000+0x8fd3) [0xb72eefd3]
    [ 219.680] 10: /usr/lib/libdrm.so.2 (drmHandleEvent+0xce) [0xb733de6e]
    [ 219.680] 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb72e6000+0x9037) [0xb72ef037]
    [ 219.680] 12: /usr/bin/Xorg (WakeupHandler+0x65) [0x807a805]
    [ 219.680] 13: /usr/bin/Xorg (WaitForSomething+0x1a5) [0x81bd355]
    [ 219.680] 14: /usr/bin/Xorg (0x8048000+0x2e462) [0x8076462]
    [ 219.680] 15: /usr/bin/Xorg (0x8048000+0x1c39a) [0x806439a]
    [ 219.680] 16: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb74f1243]
    [ 219.680] 17: /usr/bin/Xorg (0x8048000+0x1c6c9) [0x80646c9]
    [ 219.680] Segmentation fault at address 0xb4a39008
    [ 219.680]
    Fatal server error:
    [ 219.680] Caught signal 11 (Segmentation fault). Server aborting
    the full Xorg.0.log:
    [ 15.121]
    X.Org X Server 1.11.2
    Release Date: 2011-11-04
    [ 15.121] X Protocol Version 11, Revision 0
    [ 15.121] Build Operating System: Linux 3.1.0-3-ARCH i686
    [ 15.121] Current Operating System: Linux marvin 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 12:14:48 UTC 2011 i686
    [ 15.121] Kernel command line: root=/dev/sda1 ro pcie_aspm=force fastboot i915.modeset=1 i915.semaphores=1
    [ 15.121] Build Date: 07 November 2011 08:54:15AM
    [ 15.121]
    [ 15.121] Current version of pixman: 0.24.0
    [ 15.121] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 15.121] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 15.121] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 17 21:19:48 2011
    [ 15.137] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 15.169] (==) No Layout section. Using the first Screen section.
    [ 15.169] (==) No screen section available. Using defaults.
    [ 15.169] (**) |-->Screen "Default Screen Section" (0)
    [ 15.169] (**) | |-->Monitor "<default monitor>"
    [ 15.179] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 15.179] (==) Automatically adding devices
    [ 15.179] (==) Automatically enabling devices
    [ 15.224] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 15.224] Entry deleted from font path.
    [ 15.304] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 15.304] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 15.304] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 15.316] (II) Loader magic: 0x8228580
    [ 15.316] (II) Module ABI versions:
    [ 15.316] X.Org ANSI C Emulation: 0.4
    [ 15.316] X.Org Video Driver: 11.0
    [ 15.316] X.Org XInput driver : 13.0
    [ 15.316] X.Org Server Extension : 6.0
    [ 15.317] (--) PCI:*(0:0:2:0) 8086:2a42:144d:c059 rev 9, Mem @ 0xfa000000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8
    [ 15.317] (--) PCI: (0:0:2:1) 8086:2a43:144d:c059 rev 9, Mem @ 0xfa400000/1048576
    [ 15.317] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 15.317] (II) LoadModule: "extmod"
    [ 15.325] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 15.331] (II) Module extmod: vendor="X.Org Foundation"
    [ 15.331] compiled for 1.11.2, module version = 1.0.0
    [ 15.331] Module class: X.Org Server Extension
    [ 15.331] ABI class: X.Org Server Extension, version 6.0
    [ 15.331] (II) Loading extension MIT-SCREEN-SAVER
    [ 15.331] (II) Loading extension XFree86-VidModeExtension
    [ 15.331] (II) Loading extension XFree86-DGA
    [ 15.331] (II) Loading extension DPMS
    [ 15.331] (II) Loading extension XVideo
    [ 15.331] (II) Loading extension XVideo-MotionCompensation
    [ 15.331] (II) Loading extension X-Resource
    [ 15.331] (II) LoadModule: "dbe"
    [ 15.332] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 15.337] (II) Module dbe: vendor="X.Org Foundation"
    [ 15.337] compiled for 1.11.2, module version = 1.0.0
    [ 15.337] Module class: X.Org Server Extension
    [ 15.337] ABI class: X.Org Server Extension, version 6.0
    [ 15.337] (II) Loading extension DOUBLE-BUFFER
    [ 15.337] (II) LoadModule: "glx"
    [ 15.337] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 15.354] (II) Module glx: vendor="X.Org Foundation"
    [ 15.354] compiled for 1.11.2, module version = 1.0.0
    [ 15.354] ABI class: X.Org Server Extension, version 6.0
    [ 15.354] (==) AIGLX enabled
    [ 15.354] (II) Loading extension GLX
    [ 15.354] (II) LoadModule: "record"
    [ 15.354] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 15.355] (II) Module record: vendor="X.Org Foundation"
    [ 15.355] compiled for 1.11.2, module version = 1.13.0
    [ 15.355] Module class: X.Org Server Extension
    [ 15.355] ABI class: X.Org Server Extension, version 6.0
    [ 15.355] (II) Loading extension RECORD
    [ 15.355] (II) LoadModule: "dri"
    [ 15.355] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 15.494] (II) Module dri: vendor="X.Org Foundation"
    [ 15.494] compiled for 1.11.2, module version = 1.0.0
    [ 15.494] ABI class: X.Org Server Extension, version 6.0
    [ 15.494] (II) Loading extension XFree86-DRI
    [ 15.494] (II) LoadModule: "dri2"
    [ 15.494] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 15.515] (II) Module dri2: vendor="X.Org Foundation"
    [ 15.515] compiled for 1.11.2, module version = 1.2.0
    [ 15.515] ABI class: X.Org Server Extension, version 6.0
    [ 15.515] (II) Loading extension DRI2
    [ 15.515] (==) Matched intel as autoconfigured driver 0
    [ 15.515] (==) Matched vesa as autoconfigured driver 1
    [ 15.515] (==) Matched fbdev as autoconfigured driver 2
    [ 15.515] (==) Assigned the driver to the xf86ConfigLayout
    [ 15.515] (II) LoadModule: "intel"
    [ 15.525] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 15.582] (II) Module intel: vendor="X.Org Foundation"
    [ 15.582] compiled for 1.10.99.902, module version = 2.16.0
    [ 15.582] Module class: X.Org Video Driver
    [ 15.582] ABI class: X.Org Video Driver, version 11.0
    [ 15.582] (II) LoadModule: "vesa"
    [ 15.605] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 15.728] (II) Module vesa: vendor="X.Org Foundation"
    [ 15.728] compiled for 1.11.1, module version = 2.3.0
    [ 15.728] Module class: X.Org Video Driver
    [ 15.728] ABI class: X.Org Video Driver, version 11.0
    [ 15.728] (II) LoadModule: "fbdev"
    [ 15.729] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 15.740] (II) Module fbdev: vendor="X.Org Foundation"
    [ 15.740] compiled for 1.10.99.902, module version = 0.4.2
    [ 15.740] ABI class: X.Org Video Driver, version 11.0
    [ 15.740] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
    [ 15.740] (II) VESA: driver for VESA chipsets: vesa
    [ 15.740] (II) FBDEV: driver for framebuffer: fbdev
    [ 15.740] (++) using VT number 7
    [ 15.748] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 15.748] (WW) Falling back to old probe method for vesa
    [ 15.748] (WW) Falling back to old probe method for fbdev
    [ 15.885] (II) Loading sub module "fbdevhw"
    [ 15.885] (II) LoadModule: "fbdevhw"
    [ 15.905] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 15.922] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 15.922] compiled for 1.11.2, module version = 0.0.2
    [ 15.922] ABI class: X.Org Video Driver, version 11.0
    [ 15.922] drmOpenDevice: node name is /dev/dri/card0
    [ 15.922] drmOpenDevice: open result is 8, (OK)
    [ 15.922] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 15.922] drmOpenDevice: node name is /dev/dri/card0
    [ 15.922] drmOpenDevice: open result is 8, (OK)
    [ 15.922] drmOpenByBusid: drmOpenMinor returns 8
    [ 15.922] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 15.922] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 15.922] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 15.922] (==) intel(0): RGB weight 888
    [ 15.922] (==) intel(0): Default visual is TrueColor
    [ 15.922] (II) intel(0): Integrated Graphics Chipset: Intel(R) GM45
    [ 15.923] (--) intel(0): Chipset: "GM45"
    [ 15.923] (**) intel(0): Relaxed fencing enabled
    [ 15.923] (**) intel(0): Wait on SwapBuffers? enabled
    [ 15.923] (**) intel(0): Triple buffering? enabled
    [ 15.923] (**) intel(0): Framebuffer tiled
    [ 15.923] (**) intel(0): Pixmaps tiled
    [ 15.923] (**) intel(0): 3D buffers tiled
    [ 15.923] (**) intel(0): SwapBuffers wait enabled
    [ 15.923] (==) intel(0): video overlay key set to 0x101fe
    [ 15.923] (II) intel(0): Output LVDS1 has no monitor section
    [ 15.923] (II) intel(0): found backlight control interface /sys/class/backlight/samsung
    [ 15.936] (II) intel(0): Output VGA1 has no monitor section
    [ 16.470] (II) intel(0): Output HDMI1 has no monitor section
    [ 16.471] (II) intel(0): Output DP1 has no monitor section
    [ 16.472] (II) intel(0): Output DP2 has no monitor section
    [ 16.771] (II) intel(0): Output TV1 has no monitor section
    [ 16.771] (II) intel(0): EDID for output LVDS1
    [ 16.771] (II) intel(0): Manufacturer: CMO Model: 1711 Serial#: 0
    [ 16.771] (II) intel(0): Year: 2009 Week: 5
    [ 16.771] (II) intel(0): EDID Version: 1.3
    [ 16.771] (II) intel(0): Digital Display Input
    [ 16.771] (II) intel(0): Max Image Size [cm]: horiz.: 39 vert.: 22
    [ 16.771] (II) intel(0): Gamma: 2.20
    [ 16.771] (II) intel(0): No DPMS capabilities specified
    [ 16.771] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 16.771] (II) intel(0): First detailed timing is preferred mode
    [ 16.771] (II) intel(0): redX: 0.617 redY: 0.336 greenX: 0.321 greenY: 0.596
    [ 16.771] (II) intel(0): blueX: 0.160 blueY: 0.081 whiteX: 0.313 whiteY: 0.329
    [ 16.771] (II) intel(0): Manufacturer's mask: 0
    [ 16.771] (II) intel(0): Supported detailed timing:
    [ 16.771] (II) intel(0): clock: 97.8 MHz Image Size: 382 x 215 mm
    [ 16.771] (II) intel(0): h_active: 1600 h_sync: 1648 h_sync_end 1680 h_blank_end 1760 h_border: 0
    [ 16.771] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 908 v_blanking: 926 v_border: 0
    [ 16.771] (II) intel(0): N173O6-L02
    [ 16.771] (II) intel(0): CMO
    [ 16.771] (II) intel(0): N173O6-L02
    [ 16.771] (II) intel(0): EDID (in hex):
    [ 16.771] (II) intel(0): 00ffffffffffff000daf111700000000
    [ 16.771] (II) intel(0): 05130103802716780a06359e56529829
    [ 16.771] (II) intel(0): 14505400000001010101010101010101
    [ 16.771] (II) intel(0): 0101010101012f2640a060841a303020
    [ 16.771] (II) intel(0): 35007ed710000018000000fe004e3137
    [ 16.771] (II) intel(0): 334f362d4c30320a2020000000fe0043
    [ 16.771] (II) intel(0): 4d4f0a202020202020202020000000fe
    [ 16.771] (II) intel(0): 004e3137334f362d4c30320a2020002f
    [ 16.771] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 16.771] (II) intel(0): Printing DDC gathered Modelines:
    [ 16.771] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 16.771] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 16.771] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 16.772] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 16.772] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 16.772] (II) intel(0): Printing probed modes for output LVDS1
    [ 16.772] (II) intel(0): Modeline "1600x900"x60.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 16.772] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 16.772] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 16.772] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 16.772] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 16.790] (II) intel(0): EDID for output VGA1
    [ 17.323] (II) intel(0): EDID for output HDMI1
    [ 17.324] (II) intel(0): EDID for output DP1
    [ 17.325] (II) intel(0): EDID for output DP2
    [ 17.624] (II) intel(0): EDID for output TV1
    [ 17.624] (II) intel(0): Output LVDS1 connected
    [ 17.624] (II) intel(0): Output VGA1 disconnected
    [ 17.624] (II) intel(0): Output HDMI1 disconnected
    [ 17.624] (II) intel(0): Output DP1 disconnected
    [ 17.624] (II) intel(0): Output DP2 disconnected
    [ 17.624] (II) intel(0): Output TV1 disconnected
    [ 17.624] (II) intel(0): Using exact sizes for initial modes
    [ 17.624] (II) intel(0): Output LVDS1 using initial mode 1600x900
    [ 17.624] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 17.624] (II) intel(0): Kernel page flipping support detected, enabling
    [ 17.624] (**) intel(0): Display dimensions: (390, 220) mm
    [ 17.624] (**) intel(0): DPI set to (104, 103)
    [ 17.624] (II) Loading sub module "fb"
    [ 17.624] (II) LoadModule: "fb"
    [ 17.625] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 17.652] (II) Module fb: vendor="X.Org Foundation"
    [ 17.652] compiled for 1.11.2, module version = 1.0.0
    [ 17.652] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 17.652] (II) Loading sub module "dri2"
    [ 17.652] (II) LoadModule: "dri2"
    [ 17.652] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 17.652] (II) Module dri2: vendor="X.Org Foundation"
    [ 17.652] compiled for 1.11.2, module version = 1.2.0
    [ 17.652] ABI class: X.Org Server Extension, version 6.0
    [ 17.652] (II) UnloadModule: "vesa"
    [ 17.652] (II) Unloading vesa
    [ 17.652] (II) UnloadModule: "fbdev"
    [ 17.652] (II) Unloading fbdev
    [ 17.652] (II) UnloadModule: "fbdevhw"
    [ 17.652] (II) Unloading fbdevhw
    [ 17.652] (==) Depth 24 pixmap format is 32 bpp
    [ 17.652] (II) intel(0): [DRI2] Setup complete
    [ 17.652] (II) intel(0): [DRI2] DRI driver: i965
    [ 17.652] (II) intel(0): Allocated new frame buffer 1600x900 stride 6656, tiled
    [ 17.694] (II) UXA(0): Driver registered support for the following operations:
    [ 17.694] (II) solid
    [ 17.694] (II) copy
    [ 17.694] (II) composite (RENDER acceleration)
    [ 17.694] (II) put_image
    [ 17.694] (II) get_image
    [ 17.694] (==) intel(0): Backing store disabled
    [ 17.694] (==) intel(0): Silken mouse enabled
    [ 17.694] (II) intel(0): Initializing HW Cursor
    [ 17.710] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 17.710] (==) intel(0): DPMS enabled
    [ 17.710] (==) intel(0): Intel XvMC decoder enabled
    [ 17.710] (II) intel(0): Set up textured video
    [ 17.711] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [ 17.711] (II) intel(0): direct rendering: DRI2 Enabled
    [ 17.711] (==) intel(0): hotplug detection: "enabled"
    [ 17.711] (--) RandR disabled
    [ 17.711] (II) Initializing built-in extension Generic Event Extension
    [ 17.711] (II) Initializing built-in extension SHAPE
    [ 17.711] (II) Initializing built-in extension MIT-SHM
    [ 17.711] (II) Initializing built-in extension XInputExtension
    [ 17.711] (II) Initializing built-in extension XTEST
    [ 17.711] (II) Initializing built-in extension BIG-REQUESTS
    [ 17.711] (II) Initializing built-in extension SYNC
    [ 17.711] (II) Initializing built-in extension XKEYBOARD
    [ 17.711] (II) Initializing built-in extension XC-MISC
    [ 17.711] (II) Initializing built-in extension SECURITY
    [ 17.711] (II) Initializing built-in extension XINERAMA
    [ 17.711] (II) Initializing built-in extension XFIXES
    [ 17.711] (II) Initializing built-in extension RENDER
    [ 17.711] (II) Initializing built-in extension RANDR
    [ 17.711] (II) Initializing built-in extension COMPOSITE
    [ 17.711] (II) Initializing built-in extension DAMAGE
    [ 17.894] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 17.894] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 17.894] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 17.894] (II) AIGLX: enabled GLX_SGI_make_current_read
    [ 17.894] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 17.894] (II) AIGLX: Loaded and initialized i965
    [ 17.894] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 17.894] (II) intel(0): Setting screen physical size to 423 x 238
    [ 18.210] (II) XKB: Reusing cached keymap
    [ 18.213] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 18.213] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 18.213] (II) LoadModule: "evdev"
    [ 18.225] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.233] (II) Module evdev: vendor="X.Org Foundation"
    [ 18.233] compiled for 1.10.99.902, module version = 2.6.0
    [ 18.233] Module class: X.Org XInput Driver
    [ 18.233] ABI class: X.Org XInput driver, version 13.0
    [ 18.233] (II) Using input driver 'evdev' for 'Power Button'
    [ 18.233] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.233] Option "XkbRules" "evdev"
    [ 18.233] Option "XkbModel" "evdev"
    [ 18.233] Option "XkbLayout" "be"
    [ 18.233] Option "_source" "server/udev"
    [ 18.233] Option "name" "Power Button"
    [ 18.233] Option "path" "/dev/input/event3"
    [ 18.233] Option "device" "/dev/input/event3"
    [ 18.233] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 18.233] Option "driver" "evdev"
    [ 18.233] (**) Power Button: always reports core events
    [ 18.233] (**) Power Button: Device: "/dev/input/event3"
    [ 18.233] (--) Power Button: Found keys
    [ 18.233] (II) Power Button: Configuring as keyboard
    [ 18.233] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 18.233] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 18.233] (**) Option "xkb_rules" "evdev"
    [ 18.233] (**) Option "xkb_model" "evdev"
    [ 18.233] (**) Option "xkb_layout" "be"
    [ 18.278] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
    [ 18.278] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 18.278] (II) Using input driver 'evdev' for 'Video Bus'
    [ 18.278] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.278] Option "XkbRules" "evdev"
    [ 18.278] Option "XkbModel" "evdev"
    [ 18.278] Option "XkbLayout" "be"
    [ 18.278] Option "_source" "server/udev"
    [ 18.278] Option "name" "Video Bus"
    [ 18.278] Option "path" "/dev/input/event5"
    [ 18.278] Option "device" "/dev/input/event5"
    [ 18.278] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input5/event5"
    [ 18.278] Option "driver" "evdev"
    [ 18.278] (**) Video Bus: always reports core events
    [ 18.278] (**) Video Bus: Device: "/dev/input/event5"
    [ 18.278] (--) Video Bus: Found keys
    [ 18.278] (II) Video Bus: Configuring as keyboard
    [ 18.278] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input5/event5"
    [ 18.278] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 18.278] (**) Option "xkb_rules" "evdev"
    [ 18.278] (**) Option "xkb_model" "evdev"
    [ 18.278] (**) Option "xkb_layout" "be"
    [ 18.278] (II) XKB: Reusing cached keymap
    [ 18.279] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 18.279] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 18.279] (II) Using input driver 'evdev' for 'Power Button'
    [ 18.279] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.279] Option "XkbRules" "evdev"
    [ 18.279] Option "XkbModel" "evdev"
    [ 18.279] Option "XkbLayout" "be"
    [ 18.279] Option "_source" "server/udev"
    [ 18.279] Option "name" "Power Button"
    [ 18.279] Option "path" "/dev/input/event1"
    [ 18.279] Option "device" "/dev/input/event1"
    [ 18.279] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 18.279] Option "driver" "evdev"
    [ 18.279] (**) Power Button: always reports core events
    [ 18.279] (**) Power Button: Device: "/dev/input/event1"
    [ 18.279] (--) Power Button: Found keys
    [ 18.279] (II) Power Button: Configuring as keyboard
    [ 18.279] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 18.279] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 18.279] (**) Option "xkb_rules" "evdev"
    [ 18.279] (**) Option "xkb_model" "evdev"
    [ 18.279] (**) Option "xkb_layout" "be"
    [ 18.279] (II) XKB: Reusing cached keymap
    [ 18.280] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
    [ 18.280] (II) No input driver/identifier specified (ignoring)
    [ 18.280] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 18.280] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 18.280] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 18.280] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.280] Option "XkbRules" "evdev"
    [ 18.280] Option "XkbModel" "evdev"
    [ 18.280] Option "XkbLayout" "be"
    [ 18.280] Option "_source" "server/udev"
    [ 18.280] Option "name" "Sleep Button"
    [ 18.280] Option "path" "/dev/input/event2"
    [ 18.280] Option "device" "/dev/input/event2"
    [ 18.280] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2"
    [ 18.280] Option "driver" "evdev"
    [ 18.280] (**) Sleep Button: always reports core events
    [ 18.280] (**) Sleep Button: Device: "/dev/input/event2"
    [ 18.280] (--) Sleep Button: Found keys
    [ 18.280] (II) Sleep Button: Configuring as keyboard
    [ 18.280] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2"
    [ 18.280] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 18.280] (**) Option "xkb_rules" "evdev"
    [ 18.280] (**) Option "xkb_model" "evdev"
    [ 18.280] (**) Option "xkb_layout" "be"
    [ 18.280] (II) XKB: Reusing cached keymap
    [ 18.281] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event6)
    [ 18.281] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
    [ 18.281] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
    [ 18.281] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.281] Option "XkbRules" "evdev"
    [ 18.281] Option "XkbModel" "evdev"
    [ 18.281] Option "XkbLayout" "be"
    [ 18.281] Option "_source" "server/udev"
    [ 18.281] Option "name" "Logitech USB Receiver"
    [ 18.281] Option "path" "/dev/input/event6"
    [ 18.281] Option "device" "/dev/input/event6"
    [ 18.281] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input6/event6"
    [ 18.281] Option "driver" "evdev"
    [ 18.281] (**) Logitech USB Receiver: always reports core events
    [ 18.281] (**) Logitech USB Receiver: Device: "/dev/input/event6"
    [ 18.281] (--) Logitech USB Receiver: Found keys
    [ 18.281] (II) Logitech USB Receiver: Configuring as keyboard
    [ 18.281] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input6/event6"
    [ 18.281] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 10)
    [ 18.281] (**) Option "xkb_rules" "evdev"
    [ 18.281] (**) Option "xkb_model" "evdev"
    [ 18.281] (**) Option "xkb_layout" "be"
    [ 18.281] (II) XKB: Reusing cached keymap
    [ 18.282] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event7)
    [ 18.282] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
    [ 18.282] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
    [ 18.282] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
    [ 18.282] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.282] Option "XkbRules" "evdev"
    [ 18.282] Option "XkbModel" "evdev"
    [ 18.282] Option "XkbLayout" "be"
    [ 18.282] Option "_source" "server/udev"
    [ 18.282] Option "name" "Logitech USB Receiver"
    [ 18.282] Option "path" "/dev/input/event7"
    [ 18.282] Option "device" "/dev/input/event7"
    [ 18.282] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/input/input7/event7"
    [ 18.282] Option "driver" "evdev"
    [ 18.282] (**) Logitech USB Receiver: always reports core events
    [ 18.282] (**) Logitech USB Receiver: Device: "/dev/input/event7"
    [ 18.282] (--) Logitech USB Receiver: Found 20 mouse buttons
    [ 18.282] (--) Logitech USB Receiver: Found scroll wheel(s)
    [ 18.282] (--) Logitech USB Receiver: Found relative axes
    [ 18.282] (--) Logitech USB Receiver: Found x and y relative axes
    [ 18.282] (--) Logitech USB Receiver: Found absolute axes
    [ 18.282] (--) Logitech USB Receiver: Found keys
    [ 18.282] (II) Logitech USB Receiver: Configuring as mouse
    [ 18.282] (II) Logitech USB Receiver: Configuring as keyboard
    [ 18.282] (II) Logitech USB Receiver: Adding scrollwheel support
    [ 18.282] (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    [ 18.282] (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 18.283] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/input/input7/event7"
    [ 18.283] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 11)
    [ 18.283] (**) Option "xkb_rules" "evdev"
    [ 18.283] (**) Option "xkb_model" "evdev"
    [ 18.283] (**) Option "xkb_layout" "be"
    [ 18.283] (II) XKB: Reusing cached keymap
    [ 18.283] (II) Logitech USB Receiver: initialized for relative axes.
    [ 18.283] (WW) Logitech USB Receiver: ignoring absolute axes.
    [ 18.283] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    [ 18.283] (**) Logitech USB Receiver: (accel) acceleration profile 0
    [ 18.283] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
    [ 18.283] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
    [ 18.283] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
    [ 18.283] (II) No input driver/identifier specified (ignoring)
    [ 18.284] (II) config/udev: Adding input device WebCam SCB-0320N (/dev/input/event12)
    [ 18.284] (**) WebCam SCB-0320N: Applying InputClass "evdev keyboard catchall"
    [ 18.284] (II) Using input driver 'evdev' for 'WebCam SCB-0320N'
    [ 18.284] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.284] Option "XkbRules" "evdev"
    [ 18.284] Option "XkbModel" "evdev"
    [ 18.284] Option "XkbLayout" "be"
    [ 18.284] Option "_source" "server/udev"
    [ 18.284] Option "name" "WebCam SCB-0320N"
    [ 18.284] Option "path" "/dev/input/event12"
    [ 18.284] Option "device" "/dev/input/event12"
    [ 18.284] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.0/input/input12/event12"
    [ 18.284] Option "driver" "evdev"
    [ 18.284] (**) WebCam SCB-0320N: always reports core events
    [ 18.284] (**) WebCam SCB-0320N: Device: "/dev/input/event12"
    [ 18.284] (--) WebCam SCB-0320N: Found keys
    [ 18.284] (II) WebCam SCB-0320N: Configuring as keyboard
    [ 18.284] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.0/input/input12/event12"
    [ 18.284] (II) XINPUT: Adding extended input device "WebCam SCB-0320N" (type: KEYBOARD, id 12)
    [ 18.284] (**) Option "xkb_rules" "evdev"
    [ 18.284] (**) Option "xkb_model" "evdev"
    [ 18.284] (**) Option "xkb_layout" "be"
    [ 18.284] (II) XKB: Reusing cached keymap
    [ 18.285] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event10)
    [ 18.285] (II) No input driver/identifier specified (ignoring)
    [ 18.285] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event11)
    [ 18.285] (II) No input driver/identifier specified (ignoring)
    [ 18.286] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
    [ 18.286] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 18.286] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 18.286] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 18.286] Option "XkbRules" "evdev"
    [ 18.286] Option "XkbModel" "evdev"
    [ 18.286] Option "XkbLayout" "be"
    [ 18.286] Option "_source" "server/udev"
    [ 18.286] Option "name" "AT Translated Set 2 keyboard"
    [ 18.286] Option "path" "/dev/input/event4"
    [ 18.286] Option "device" "/dev/input/event4"
    [ 18.286] Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
    [ 18.286] Option "driver" "evdev"
    [ 18.286] (**) AT Translated Set 2 keyboard: always reports core events
    [ 18.286] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4"
    [ 18.286] (--) AT Translated Set 2 keyboard: Found keys
    [ 18.286] (II) AT Translated Set 2 keyboard: Configuring as keyboard
    [ 18.286] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
    [ 18.286] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 13)
    [ 18.286] (**) Option "xkb_rules" "evdev"
    [ 18.286] (**) Option "xkb_model" "evdev"
    [ 18.286] (**) Option "xkb_layout" "be"
    [ 18.286] (II) XKB: Reusing cached keymap
    [ 18.286] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
    [ 18.286] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 18.287] (II) LoadModule: "synaptics"
    [ 18.287] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 18.287] (II) Module synaptics: vendor="X.Org Foundation"
    [ 18.288] compiled for 1.11.0, module version = 1.5.0
    [ 18.288] Module class: X.Org XInput Driver
    [ 18.288] ABI class: X.Org XInput driver, version 13.0
    [ 18.288] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 18.288] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 18.288] Option "_source" "server/udev"
    [ 18.288] Option "name" "SynPS/2 Synaptics TouchPad"
    [ 18.288] Option "path" "/dev/input/event9"
    [ 18.288] Option "device" "/dev/input/event9"
    [ 18.288] Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
    [ 18.288] Option "TapButton1" "1"
    [ 18.288] Option "RTCornerButton" "2"
    [ 18.288] Option "RBCornerButton" "3"
    [ 18.288] Option "VertEdgeScroll" "on"
    [ 18.288] Option "HorizEdgeScroll" "on"
    [ 18.288] Option "driver" "synaptics"
    [ 18.288] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 18.288] (**) Option "Device" "/dev/input/event9"
    [ 18.483] (**) Option "Device" "/dev/input/event9"
    [ 18.483] port opened successfully
    [ 18.590] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
    [ 18.590] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
    [ 18.590] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 18.590] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 0
    [ 18.590] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right
    [ 18.590] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 18.590] (**) Option "VertEdgeScroll" "on"
    [ 18.590] (**) Option "HorizEdgeScroll" "on"
    [ 18.590] (**) Option "RTCornerButton" "2"
    [ 18.590] (**) Option "RBCornerButton" "3"
    [ 18.590] (**) Option "TapButton1" "1"
    [ 18.696] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 18.696] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 18.803] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
    [ 18.803] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 14)
    [ 18.803] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 18.803] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
    [ 18.803] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.040
    [ 18.803] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 18.803] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 18.803] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 18.803] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 18.803] (**) Option "Device" "/dev/input/event9"
    [ 18.803] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 18.804] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 18.804] (II) No input driver/identifier specified (ignoring)
    [ 18.804] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
    [ 18.804] (II) No input driver/identifier specified (ignoring)
    [ 18.836] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 18.836] (II) intel(0): Printing DDC gathered Modelines:
    [ 18.836] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 24.907] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 24.907] (II) intel(0): Printing DDC gathered Modelines:
    [ 24.907] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 25.888] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 25.888] (II) intel(0): Printing DDC gathered Modelines:
    [ 25.888] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 27.318] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 27.318] (II) intel(0): Printing DDC gathered Modelines:
    [ 27.318] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 28.181] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 28.181] (II) intel(0): Printing DDC gathered Modelines:
    [ 28.181] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 29.031] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 29.031] (II) intel(0): Printing DDC gathered Modelines:
    [ 29.031] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 35.698] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 35.698] (II) intel(0): Printing DDC gathered Modelines:
    [ 35.698] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 55.995] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 55.995] (II) intel(0): Printing DDC gathered Modelines:
    [ 55.995] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 59.047] (II) intel(0): EDID vendor "CMO", prod id 5905
    [ 59.047] (II) intel(0): Printing DDC gathered Modelines:
    [ 59.047] (II) intel(0): Modeline "1600x900"x0.0 97.75 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.5 kHz)
    [ 219.680]
    Backtrace:
    [ 219.680] 0: /usr/bin/Xorg (xorg_backtrace+0x37) [0x81c00d7]
    [ 219.680] 1: /usr/bin/Xorg (0x8048000+0x17bc1a) [0x81c3c1a]
    [ 219.680] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb784040c]
    [ 219.680] 3: /usr/lib/xorg/modules/extensions/librecord.so (0xb7370000+0x214f) [0xb737214f]
    [ 219.680] 4: /usr/bin/Xorg (_CallCallbacks+0x3c) [0x807afbc]
    [ 219.680] 5: /usr/bin/Xorg (WriteToClient+0x273) [0x81c3353]
    [ 219.680] 6: /usr/lib/xorg/modules/extensions/libdri2.so (ProcDRI2WaitMSCReply+0x70) [0xb7360fa0]
    [ 219.680] 7: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2WaitMSCComplete+0x73) [0xb735f243]
    [ 219.680] 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb72e6000+0x2419b) [0xb730a19b]
    [ 219.680] 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb72e6000+0x8fd3) [0xb72eefd3]
    [ 219.680] 10: /usr/lib/libdrm.so.2 (drmHandleEvent+0xce) [0xb733de6e]
    [ 219.680] 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb72e6000+0x9037) [0xb72ef037]
    [ 219.680] 12: /usr/bin/Xorg (WakeupHandler+0x65) [0x807a805]
    [ 219.680] 13: /usr/bin/Xorg (WaitForSomething+0x1a5) [0x81bd355]
    [ 219.680] 14: /usr/bin/Xorg (0x8048000+0x2e462) [0x8076462]
    [ 219.680] 15: /usr/bin/Xorg (0x8048000+0x1c39a) [0x806439a]
    [ 219.680] 16: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb74f1243]
    [ 219.680] 17: /usr/bin/Xorg (0x8048000+0x1c6c9) [0x80646c9]
    [ 219.680] Segmentation fault at address 0xb4a39008
    [ 219.680]
    Fatal server error:
    [ 219.680] Caught signal 11 (Segmentation fault). Server aborting
    [ 219.680]
    [ 219.680]
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 219.680] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 219.680]
    [ 219.716] (II) Power Button: Close
    [ 219.716] (II) UnloadModule: "evdev"
    [ 219.716] (II) Unloading evdev
    [ 219.743] (II) Video Bus: Close
    [ 219.743] (II) UnloadModule: "evdev"
    [ 219.743] (II) Unloading evdev
    [ 219.763] (II) Power Button: Close
    [ 219.763] (II) UnloadModule: "evdev"
    [ 219.763] (II) Unloading evdev
    [ 219.783] (II) Sleep Button: Close
    [ 219.783] (II) UnloadModule: "evdev"
    [ 219.783] (II) Unloading evdev
    [ 219.803] (II) Logitech USB Receiver: Close
    [ 219.803] (II) UnloadModule: "evdev"
    [ 219.803] (II) Unloading evdev
    [ 219.823] (II) Logitech USB Receiver: Close
    [ 219.823] (II) UnloadModule: "evdev"
    [ 219.823] (II) Unloading evdev
    [ 219.846] (II) WebCam SCB-0320N: Close
    [ 219.846] (II) UnloadModule: "evdev"
    [ 219.846] (II) Unloading evdev
    [ 219.890] (II) AT Translated Set 2 keyboard: Close
    [ 219.890] (II) UnloadModule: "evdev"
    [ 219.890] (II) Unloading evdev
    [ 219.947] (II) UnloadModule: "synaptics"
    [ 219.947] (II) Unloading synaptics
    [ 219.947] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 219.998] Server terminated with error (1). Closing log file.
    some hardware info:
    $ uname -a
    Linux marvin 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 12:14:48 UTC 2011 i686 Pentium(R) Dual-Core CPU T4200 @ 2.00GHz GenuineIntel GNU/Linux
    $ lspci
    00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
    00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
    00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
    00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
    00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
    00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
    00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
    00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
    00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
    00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
    00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
    00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
    00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
    00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
    00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
    00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
    02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
    04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
    software is fully up to date, except for the kernel (I could not control the backlight with the latest version). Got some software from the AUR and 2 custom packages too.
    $ pacman -Q linux linux-headers
    linux 3.0.7-1
    linux-headers 3.0.7
    $ pacman -Qm
    alacarte 0.13.2-6
    aurget 3.4.0-2
    banshee-community-extensions 2.2.0-1
    banshee-custom 20111016-1
    briss 0.0.13-2
    chromium-stable-libpdf 15.0.874.106-1
    cope-git 20110919-1
    docky-stacks-bzr 1576-1
    easy-slow-down-manager-svn 33-1
    font-manager 0.5.7-1
    gedit-latex 3.3.1-1
    gio-sharp-git 20111114-1
    gnome-menus2 3.0.1-1
    gnome-settings-daemon-custom 3.2.0-2
    gnome-shell-extension-mediaplayer-git 20111008-1
    gnome-shell-extension-presentation-mode-git 20111022-1
    gnome-shell-extension-weather-git 20111008-1
    gnome-system-tools 3.0.0-2
    gpaste 1.99-1
    gtg 0.2.4-6
    gtk-engine-unico 1.0.1-2
    hyena-git 20111007-1
    liboobs 3.0.0-1
    nautilus-terminal 1.0-1
    package-query 0.9-1
    pacman-color 3.5.4-1
    pdfmod 0.9.1-1
    perl-env-path 0.18-2
    perl-io-stty 0.30.0-3
    perl-regexp-common 2010010201-1
    phatch 0.2.7.1-4
    python-nautilus 1.1-2
    samsung-tools 1.5-1
    system-tools-backends 2.10.2-1
    ttf-ms-fonts 2.0-8
    ttf-raghu 1.0-1
    ttf-vista-fonts 1-3
    xampp 1.7.4-1
    as for the way Xorg is configurated:
    $ cat /etc/X11/xorg.conf.d/*
    # Catch-all evdev loader for udev-based systems
    # We don't simply match on any device since that also adds accelerometers
    # and other devices that we don't really want to use. The list below
    # matches everything but joysticks.
    Section "InputClass"
    Identifier "evdev pointer catchall"
    MatchIsPointer "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    EndSection
    Section "InputClass"
    Identifier "evdev keyboard catchall"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "XkbLayout" "be"
    EndSection
    #Section "InputClass"
    # Identifier "evdev touchpad catchall"
    # MatchIsTouchpad "on"
    # MatchDevicePath "/dev/input/event*"
    # Driver "evdev"
    #EndSection
    #Section "InputClass"
    # Identifier "evdev tablet catchall"
    # MatchIsTablet "on"
    # MatchDevicePath "/dev/input/event*"
    # Driver "evdev"
    #EndSection
    #Section "InputClass"
    # Identifier "evdev touchscreen catchall"
    # MatchIsTouchscreen "on"
    # MatchDevicePath "/dev/input/event*"
    # Driver "evdev"
    #EndSection
    # Collection of quirks and blacklist/whitelists for specific devices.
    # Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
    # http://bugs.freedesktop.org/show_bug.cgi?id=22442
    Section "InputClass"
    Identifier "ThinkPad HDAPS accelerometer blacklist"
    MatchProduct "ThinkPad HDAPS accelerometer data"
    Option "Ignore" "on"
    EndSection
    # Section "Device"
    # Identifier "old intel stuff"
    # Driver "intel"
    # Option "Shadow" "True"
    # EndSection
    Section "InputClass"
    Identifier "touchpad catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "synaptics"
    Option "TapButton1" "1"
    Option "RTCornerButton" "2"
    Option "RBCornerButton" "3"
    Option "VertEdgeScroll" "on"
    Option "HorizEdgeScroll" "on"
    EndSection
    # Collection of quirks and blacklist/whitelists for specific devices.
    # Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
    # http://bugs.freedesktop.org/show_bug.cgi?id=22442
    #Section "InputClass"
    # Identifier "ThinkPad HDAPS accelerometer blacklist"
    # MatchProduct "ThinkPad HDAPS accelerometer data"
    # Option "Ignore" "on"
    #EndSection
    Last edited by berz_ (2011-11-17 20:58:24)

    I did add testing and community-testing, sorted out the pacman keysigning thing, and upgraded all packages, including  xf86-video-intel.
    I will wait to see if the problem still occurs.
    If it does, I will try upgrading to linux 3.1, but I would prefer not to because it causes easy-slow-down-manager and samsung-tools to fail, and I do not have a lot of time to troubleshoot my system at the moment.
    I need the AUR packages to control my samsung R719 backlight.
    Apparantly there is a new version of samsung-tools out which does not require easy-slow-down-manager, but the AUR package is out of date.

  • How do I adjust print margins in Safari

    Hello
    I am trying to print out multiple forms via Safari for printing onto removable sticky  address labels.  I cant seem to adjust the print setting to align the text with the label.  I need to set margins to do this.  I have tried adjusting the printable area via the manage custom sizes but this doesn't seem to work.  All my efforts still result in the printer printing will very narrow margin and my text doesn't align with the labels.
    I am worried the I might create a world shortage of ink in my attempts to work out what's wrong.  Please help.
    I am printing shipping labels in eBay using the Seller manager pro package .
    I am using an OKI C531 LED Printer
    Many thanks

    I am using Snow Leopard and I don't really see a +shrink to fit+ option.
    Using Safari (This also happens with Firefox and Opera), when I do the ⌘P, I get the following dialog:
    [Print Dialog 1|https://files.me.com/w1jp/udykuc]
    The only option I see to scale is either putting some number in the +Scale box+ or on the +Paper Handling+ dialog:
    [Print Dialog 2|https://files.me.com/w1jp/uwm676]
    Selecting +Scale to fit paper size+ didn't fix the problem either.
    It's like the margins aren't working for this printer when printing web pages. All the other applications (non-browser) print correctly.
    [Example of scanned print|https://files.me.com/w1jp/bg2x8q]
    Tnx,
    w1jp

Maybe you are looking for

  • Remove space in record

    HI all While executing DTP i am getting an error.INVALID CHARACTER.Its because of the space at the end of below mentioned records and also a space between * and (. '7.4*(9.92.53) '7.8*(204.25.1) I can go and correct in PSA.But for every load i need t

  • Can't get Audio or Video chat to work, it keep saying I am being denied

    Date/Time: 2009-01-14 21:50:12.969 -0600 OS Version: 10.4.11 (Build 8S2167) Report Version: 4 iChat Connection Log: AVChat started with ID 0. 0x16413530: State change from AVChatNoState to AVChatStateWaiting. brandonch58: State change from AVChatNoSt

  • From where this runtime is getting populated

    Suppose you create a report and run it. After running the report, you click administration, then session, you will find the generated physical query. +++User_ID:20cc0000:20cc0001:----2011/06/22 21:08:43 i would like to know where this timestamp (2011

  • How to check postal code contains only 0 to 9

    Hi all, How to check postal code contains only 0 to 9 thank you

  • Show new Field from BP in a Service View

    Hi All We need to show 2 fields from the Business Partner in a Service View. We need to show the BP Number because after it is entered is is OK this value is changed by the Name of the BP, and our client need to see the number all the time. An also w