Data visible via hypertrend missing in ODBC Traces Table

I am trying to pull data from the Citadel database into Access using the ODBC driver from Lookout. I am running Lookout 5.0 on Windows 2000 Advanced Server. When I query the Traces table, not all of the tags that I am currently logging show up. In fact fewer than half are available. How can I retreive the data that I know is there if I can view it with Hypertrend Object?

You might run into a timeout? You should contact National Instruments Support team to get more information about how to tweak the ODBC driver to extend the timeout.
Hope they can help you further
Roland
PS: Mention KnowladgeBase: 2TFEH4Q2

Similar Messages

  • Tab Purchase Order Data not visible via CIC

    Hi All,
    I have a problem with displaying the tab Purchase Order Data via the Customer Interaction Centre. If I create an order via CRMD_ORDER then this tab is visible, only not via the CIC.
    In tcode CRMV_SSC we use the folling for other tabs like Partner, Sales, etc.:
    Screenprofiletype TSAL
    Screen Profile: ZRAP
    Tabstrip Panel: HDTSAL
    Programm: SAP_LCRM_TSALES_UI
    With the combination above the tab Purchase Order Data (function code SALES_PURC) is not visible in the dropdownlist with available functioncodes. The system indicates that this functioncode is not available in programm SAP_LCRM_TSALES_UI.
    Questions i have are:
    Is SALES_PURC the correct functioncode for the tab Purchase Order Data?
    How can i make this tab visible via the CIC?
    Regards, Sander

    Hi Michael,
    SAP is designed to send a XML file from a purchase order or any other document type (delivery, sales order, transportation, etc) with very little effort. This means, that SAP delivers already a solution for that which the customer needs to set up.
    To create a PDF file actually requires quite a lot of custom development, specially to comply to the layout the customer requires. This is usually a task that goes from the testing team to the development team back and forth a few times before it is accepted.
    Regards

  • Role based data visibility is not working in Round manager

    I am looking for role based data visibility in Syclo round manager application where technician will see the data which is assigned to his name only (not all the data)  I have created one custom role in SAP system and it's working fine .It's showing the below message :
    Now I want to implement the same in syclo round manager .So I went to the SAP configuration panel and set the same user role on the security setting in class handler .Z_SYCLO_RM_ROLE is the custom role which I mentioned earlier .I tried with different option in this tab but it's not working .
    Please let me know if I missed something to mention or is there any other process I need to follow .
    Tags edited by: Michael Appleby

    is not working Insufficient information. In what way is it "not working"? The page doesn't render as required? There's an error message? The browser crashes? The server room has been trampled into dust by a herd of buffalo?
    >
    I am unable to make it as page form / report.
    v1 := v1 || ' ' ||'<input inline type =submit style="color:BLUE;background-color:RED" value='||c2.plot_id||'>';
    ...It is not possible to generate form elements in an APEX page in this way. The [APEX_ITEM API|http://download.oracle.com/docs/cd/E14373_01/apirefs.32/e13369/apex_item.htm#CACEEEJE] is the only way to create APEX items in PL/SQL. However it contains no procedures to generate button items, so an alternative design is required in this case, e.g. a report with links.
    (Also what is the intention of "inline" in the above code? [There is no *inline* attribute|http://www.w3.org/TR/1999/REC-html401-19991224/interact/forms.html#h-17.4].)

  • [SOLVED] - Package xf86-video-via is missing from repositories!

    Hi,
    I have a VIA card as follows:
    VGA Compatible Controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)
    My X doesn't work except in VESA mode. But in Vesa mode, when I play videos in mplayer, I can't fullscreen them.
    When I checked the sample xorg.conf files mentioned in the Xorg wiki, I find that I am advised to use the xf86-video-via package.
    But the package xf86-video-via is missing from repositories!
    pacman -Ss xf86-video-via doesn't give results!
    Please help.
    Thanks.
    Last edited by msadiq (2008-12-27 04:18:45)

    Sorry for the long wait, I havent got the time to test but I did uncomment the RenderAccel and that didnt do anything.
    my Xorg.0.log:
    =================================================================
    X.Org X Server 1.5.3
    Release Date: 5 November 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.27-ARCH i686
    Current Operating System: Linux hp-2133 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 25 10:13:11 UTC 2009 i686
    Build Date: 17 December 2008  08:20:05PM
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 27 21:07:16 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Layout0"
    (**) |-->Screen "Screen0" (0)
    (**) |   |-->Monitor "HP LCD"
    (**) |   |-->Device "Via Chrome9"
    (**) |-->Input Device "HP Keyboard"
    (**) |-->Input Device "HP Touchpad"
    (**) Option "AutoAddDevices" "false"
    (**) Not automatically adding devices
    (==) Automatically enabling devices
    (==) No FontPath specified.  Using compiled-in default.
    (==) FontPath set to:
        /usr/share/fonts/misc,
        /usr/share/fonts/100dpi:unscaled,
        /usr/share/fonts/75dpi:unscaled,
        /usr/share/fonts/TTF,
        /usr/share/fonts/Type1
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x81d5fe0
    (II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 4.1
        X.Org XInput driver : 2.1
        X.Org Server Extension : 1.1
        X.Org Font Renderer : 0.6
    (II) Loader running on linux
    (--) using VT number 7
    (--) PCI:*(0@1:0:0) VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] rev 1, Mem @ 0xc0000000/0, 0xfc000000/0, BIOS @ 0x????????/65536
    (II) System resource ranges:
        [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [32] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [33] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [34] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [35] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [48] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [49] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [50] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [51] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [52] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [53] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dri" will be loaded. This was enabled by default and also specified in the config file.
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
        compiled for 1.5.3, module version = 2.1.0
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.6
    (II) Loading font FreeType
    (II) LoadModule: "xtt"
    (WW) Warning, couldn't open module xtt
    (II) UnloadModule: "xtt"
    (EE) Failed to load module "xtt" (module does not exist, 0)
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 1.1
    (==) AIGLX enabled
    (==) Exporting typical set of GLX visuals
    (II) Loading extension GLX
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "record"
    (WW) Warning, couldn't open module record
    (II) UnloadModule: "record"
    (EE) Failed to load module "record" (module does not exist, 0)
    (II) LoadModule: "xtrap"
    (II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
    (II) Module xtrap: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
    (II) Loading extension DEC-XTRAP
    (II) LoadModule: "type1"
    (WW) Warning, couldn't open module type1
    (II) UnloadModule: "type1"
    (EE) Failed to load module "type1" (module does not exist, 0)
    (II) LoadModule: "openchrome"
    (II) Loading /usr/lib/xorg/modules/drivers//openchrome_drv.so
    (II) Module openchrome: vendor="http://openchrome.org/"
        compiled for 1.5.3, module version = 0.2.903
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 4.1
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
        compiled for 1.4.2, module version = 1.3.1
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
        compiled for 1.4.2, module version = 1.3.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.0
    (II) OPENCHROME: Driver for VIA Chrome chipsets: CLE266, KM400/KN400,
        K8M800/K8N800, PM800/PM880/CN400, P4M800Pro/VN800/CN700,
        K8M890/K8N890, P4M900/VN896/CN896, CX700/VX700, P4M890, VX800
    (II) Primary Device is: PCI 01@00:00:0
    (!!) VIA Technologies does not support this driver in any way.
    (!!) For support, please refer to http://www.openchrome.org/.
    (!!) (development build, at svn revision 726)
    (II) resource ranges after probing:
        [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [32] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [33] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [34] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [35] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [48] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [49] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [50] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [51] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [52] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [53] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    (II) CHROME(0): VIAPreInit
    (II) Loading sub module "vgahw"
    (II) LoadModule: "vgahw"
    (II) Loading /usr/lib/xorg/modules//libvgahw.so
    (II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 0.1.0
        ABI class: X.Org Video Driver, version 4.1
    (II) CHROME(0): VIAGetRec
    (**) CHROME(0): Depth 24, (--) framebuffer bpp 32
    (==) CHROME(0): RGB weight 888
    (==) CHROME(0): Default visual is TrueColor
    (--) CHROME(0): Chipset: P4M900/VN896/CN896
    (--) CHROME(0): Chipset revision: 0
    (--) CHROME(0): Probed amount of VideoRAM = 262144 kB
    (II) CHROME(0): Setting up default chipset options.
    (II) CHROME(0): VIASetupDefaultOptions
    (II) CHROME(0): Reading config file...
    (**) CHROME(0): Option "AccelMethod" "XAA"
    (**) CHROME(0): Option "PanelSize" "1024x600"
    (**) CHROME(0): Option "EnableAGPDMA" "False"
    (II) CHROME(0): Starting to parse config file options...
    (==) CHROME(0): Shadow framebuffer is disabled.
    (==) CHROME(0): Hardware acceleration is enabled.
    (**) CHROME(0): Using XAA acceleration architecture.
    (==) CHROME(0): Using hardware two-color cursors and software full-color cursors.
    (==) CHROME(0): GPU virtual command queue will be enabled.
    (==) CHROME(0): DRI IRQ will be enabled if DRI is enabled.
    (**) CHROME(0): AGP DMA will be disabled if DRI is enabled.
    (==) CHROME(0): PCI DMA will not be used for XV image transfer if DRI is enabled.
    (==) CHROME(0): Will not enable VBE modes.
    (==) CHROME(0): VBE VGA register save & restore will not be used
        if VBE modes are enabled.
    (==) CHROME(0): Xv Bandwidth check is enabled.
    (==) CHROME(0): Will not impose a limit on video RAM reserved for DRI.
    (==) CHROME(0): Will try to allocate 32768 kB of AGP memory.
    (==) CHROME(0): Digital output bus width is 12 bits.
    (==) CHROME(0): DVI Center is disabled.
    (II) CHROME(0): ViaPanelGetNativeModeFromOption
    (**) CHROME(0): Panel mode index is 13
    (**) CHROME(0): Selected Panel Size is 1024x600
    (==) CHROME(0): Panel will not be forced.
    (==) CHROME(0): TV dotCrawl is disabled.
    (==) CHROME(0): TV deflicker is set to 0.
    (==) CHROME(0): No default TV type is set.
    (==) CHROME(0): No default TV output signal type is set.
    (II) CHROME(0): VIAMapMMIO
    (--) CHROME(0): mapping MMIO @ 0xfc000000 with size 0x9000
    (--) CHROME(0): mapping BitBlt MMIO @ 0xfc200000 with size 0x200000
    (II) CHROME(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (==) CHROME(0): Will not print VGA registers.
    (==) CHROME(0): Will not scan I2C buses.
    (II) CHROME(0): ...Finished parsing config file options.
    (--) CHROME(0): Detected Hewlett Packard 2133 Mini-Note.
    (II) CHROME(0): Detected MemClk 8
    (II) CHROME(0): ViaGetMemoryBandwidth
    (II) CHROME(0): Detected TV standard: PAL.
    (==) CHROME(0): Using gamma correction (1.0, 1.0, 1.0)
    (II) Loading sub module "i2c"
    (II) LoadModule: "i2c"
    (II) Module "i2c" already built-in
    (II) CHROME(0): ViaI2CInit
    (II) CHROME(0): ViaI2CBus1Init
    (II) CHROME(0): I2C bus "I2C bus 1" initialized.
    (II) CHROME(0): ViaI2cBus2Init
    (II) CHROME(0): I2C bus "I2C bus 2" initialized.
    (II) CHROME(0): ViaI2CBus3Init
    (II) CHROME(0): I2C bus "I2C bus 3" initialized.
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) CHROME(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.
    (II) CHROME(0): I2C device "I2C bus 1:ddc2" removed.
    (II) CHROME(0): ViaOutputsDetect
    (II) CHROME(0): Enabling panel from PCI-subsystem ID information.
    (II) CHROME(0): Will not try to detect TV encoder.
    (II) CHROME(0): ViaOutputsSelect
    (II) CHROME(0): ViaOutputsSelect: X Configuration: 0x00
    (II) CHROME(0): ViaOutputsSelect: BIOS Initialised register: 0x07
    (II) CHROME(0): ViaOutputsSelect: Panel.
    (II) CHROME(0): ViaPanelPreInit
    (II) CHROME(0): ViaPanelGetNativeDisplayMode
    (II) CHROME(0): NativeModeIndex: 13
    (II) CHROME(0): ViaModesAttach
    (II) CHROME(0): ViaModesMonitorFixup - Adjusted HSync.lo to 29.677456
    (II) CHROME(0): ViaModesMonitorFixup - Adjusted HSync.hi to 74.904167
    (II) CHROME(0): HP LCD: Using hsync range of 29.68-74.90 kHz
    (II) CHROME(0): HP LCD: Using vrefresh range of 55.00-90.00 Hz
    (II) CHROME(0): Clock range:  20.00 to 230.00 MHz
    (II) CHROME(0): ViaValidMode: Validating 640x350 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x400 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 720x400 (35500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25175)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (50000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (49500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 800x600 (56300)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (44900)
    (II) CHROME(0): Not using default mode "1024x768" (interlace mode not supported)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (65000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (75000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (78750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (94500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (108000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x960 (108000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x960" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x960 (148500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x960" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (108000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (135000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (157500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (162000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (175500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (189000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (202500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (229500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1792x1344 (204800)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1792x1344" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1856x1392 (218300)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1856x1392" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 832x624 (57284)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "832x624" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (81620)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (96770)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (104990)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (119650)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (121500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (143470)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1360x768 (72000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1360x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "680x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1360x768 (84750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1360x768" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "680x384" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (122000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (145060)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (155800)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (179260)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1440x900 (106500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1440x900" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "720x450" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1600x1024 (103125)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1024" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (119000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (146250)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (174000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (187000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1680x1050 (214750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1680x1050" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1920x1080 (138500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1920x1080" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "960x540" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 1920x1200 (154000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1920x1200" (exceeds panel dimensions)
    (II) CHROME(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25312)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x480 (26591)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x576 (32663)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x480 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (39822)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 848x480 (33750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 856x480 (31704)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x512 (41164)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x576 (46981)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x600 (48960)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x768 (65028)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1024x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1152x864 (81613)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1152x864" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x768 (81135)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x720 (74600)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x720" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x960 (108280)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x960" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1280x1024 (108280)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1280x1024" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1360x768 (85500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1360x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1366x768 (85860)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1366x768" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1400x1050 (122726)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1400x1050" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1440x900 (106470)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1440x900" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1600x1200 (161793)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1600x1200" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1920x1080 (172900)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): Not using default mode "1920x1080" (exceeds panel dimensions)
    (II) CHROME(0): ViaValidMode: Validating 1024x600 (48960)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x576 (46981)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 1024x512 (41164)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (56300)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (49500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (50000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (39822)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x600 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x576 (32663)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 856x480 (31704)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 848x480 (33750)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 800x480 (40000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x480 (26591)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (36000)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25312)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x480 (25175)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 720x400 (35500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x400 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (II) CHROME(0): ViaValidMode: Validating 640x350 (31500)
    (II) CHROME(0): ViaSecondCRTCModeValid
    (--) CHROME(0): Virtual size is 1024x600 (pitch 1024)
    (**) CHROME(0): *Default mode "1024x600": 49.0 MHz (scaled from 0.0 MHz), 37.3 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "1024x600"x60.0   48.96  1024 1064 1168 1312  600 601 604 622 -hsync +vsync (37.3 kHz)
    (**) CHROME(0):  Default mode "1024x576": 47.0 MHz (scaled from -0.0 MHz), 35.8 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "1024x576"x60.0   46.98  1024 1064 1168 1312  576 576 579 597 -hsync +vsync (35.8 kHz)
    (**) CHROME(0):  Default mode "1024x512": 41.2 MHz (scaled from 0.0 MHz), 31.8 kHz, 59.8 Hz
    (II) CHROME(0): Modeline "1024x512"x59.8   41.16  1024 1056 1160 1296  512 512 515 531 -hsync +vsync (31.8 kHz)
    (**) CHROME(0):  Default mode "800x600": 56.3 MHz (scaled from 0.0 MHz), 53.7 kHz, 85.1 Hz
    (II) CHROME(0): Modeline "800x600"x85.1   56.30  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz)
    (**) CHROME(0):  Default mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
    (II) CHROME(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
    (**) CHROME(0):  Default mode "800x600": 50.0 MHz (scaled from -0.0 MHz), 48.1 kHz, 72.2 Hz
    (II) CHROME(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
    (**) CHROME(0):  Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    (II) CHROME(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "800x600": 39.8 MHz (scaled from -0.0 MHz), 37.7 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "800x600"x60.0   39.82  800 840 968 1056  600 600 604 628 +hsync +vsync (37.7 kHz)
    (**) CHROME(0):  Default mode "800x600": 36.0 MHz (scaled from -0.0 MHz), 35.2 kHz, 56.2 Hz
    (II) CHROME(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
    (**) CHROME(0):  Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "720x576"x60.0   32.66  720 744 816 912  576 576 579 597 -hsync +vsync (35.8 kHz)
    (**) CHROME(0):  Default mode "856x480": 31.7 MHz (scaled from -0.0 MHz), 29.8 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "856x480"x60.0   31.70  856 872 960 1064  480 480 483 497 -hsync +vsync (29.8 kHz)
    (**) CHROME(0):  Default mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
    (II) CHROME(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 485 493 517 +hsync +vsync (31.0 kHz)
    (**) CHROME(0):  Default mode "800x480": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
    (II) CHROME(0): Modeline "800x480"x60.3   40.00  800 832 960 1056  480 541 545 628 -hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "720x480": 26.6 MHz (scaled from -0.0 MHz), 29.7 kHz, 59.7 Hz
    (II) CHROME(0): Modeline "720x480"x59.7   26.59  720 736 808 896  480 480 483 497 -hsync +vsync (29.7 kHz)
    (**) CHROME(0):  Default mode "640x480": 36.0 MHz (scaled from -0.0 MHz), 43.3 kHz, 85.0 Hz
    (II) CHROME(0): Modeline "640x480"x85.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz)
    (**) CHROME(0):  Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
    (II) CHROME(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
    (**) CHROME(0):  Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
    (II) CHROME(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "640x480": 25.3 MHz (scaled from -0.0 MHz), 31.6 kHz, 60.3 Hz
    (II) CHROME(0): Modeline "640x480"x60.3   25.31  640 656 752 800  480 489 491 525 -hsync -vsync (31.6 kHz)
    (**) CHROME(0):  Default mode "640x480": 25.2 MHz (scaled from -0.0 MHz), 31.5 kHz, 59.9 Hz
    (II) CHROME(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
    (**) CHROME(0):  Default mode "720x400": 35.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.0 Hz
    (II) CHROME(0): Modeline "720x400"x85.0   35.50  720 756 828 936  400 401 404 446 -hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "640x400": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.1 Hz
    (II) CHROME(0): Modeline "640x400"x85.1   31.50  640 672 736 832  400 401 404 445 -hsync +vsync (37.9 kHz)
    (**) CHROME(0):  Default mode "640x350": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.1 Hz
    (II) CHROME(0): Modeline "640x350"x85.1   31.50  640 672 736 832  350 382 385 445 +hsync -vsync (37.9 kHz)
    (==) CHROME(0): DPI set to (96, 96)
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "xaa"
    (II) LoadModule: "xaa"
    (II) Loading /usr/lib/xorg/modules//libxaa.so
    (II) Module xaa: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.2.1
        ABI class: X.Org Video Driver, version 4.1
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (II) CHROME(0): VIAUnmapMem
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC?  No, I don't.
    (II) resource ranges after preInit:
        [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [32] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
        [33] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
        [34] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
        [35] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [48] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [49] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [50] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [51] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
        [52] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
        [53] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    (II) CHROME(0): VIAScreenInit
    (II) CHROME(0): VIAMapFB
    (--) CHROME(0): mapping framebuffer @ 0xc0000000 with size 0x10000000
    (--) CHROME(0): Frame buffer start: 0xa7771000, free start: 0x258000 end: 0x10000000
    (II) CHROME(0): VIAMapMMIO
    (--) CHROME(0): mapping MMIO @ 0xfc000000 with size 0x9000
    (--) CHROME(0): mapping BitBlt MMIO @ 0xfc200000 with size 0x200000
    (II) CHROME(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (II) CHROME(0): VIASave
    (II) CHROME(0): Primary
    (II) CHROME(0): Crtc...
    (II) CHROME(0): TVSave...
    (II) CHROME(0): VIAWriteMode
    (II) CHROME(0): ViaModeSet
    (II) CHROME(0): Name: 1024x600
    (II) CHROME(0): Clock: 48960
    (II) CHROME(0): VRefresh: 59.995293
    (II) CHROME(0): HSync: 37.317074
    (II) CHROME(0): HDisplay: 1024
    (II) CHROME(0): HSyncStart: 1064
    (II) CHROME(0): HSyncEnd: 1168
    (II) CHROME(0): HTotal: 1312
    (II) CHROME(0): HSkew: 0
    (II) CHROME(0): VDisplay: 600
    (II) CHROME(0): VSyncStart: 601
    (II) CHROME(0): VSyncEnd: 604
    (II) CHROME(0): VTotal: 622
    (II) CHROME(0): VScan: 0
    (II) CHROME(0): Flags: 6
    (II) CHROME(0): CrtcHDisplay: 0x400
    (II) CHROME(0): CrtcHBlankStart: 0x400
    (II) CHROME(0): CrtcHSyncStart: 0x428
    (II) CHROME(0): CrtcHSyncEnd: 0x490
    (II) CHROME(0): CrtcHBlankEnd: 0x520
    (II) CHROME(0): CrtcHTotal: 0x520
    (II) CHROME(0): CrtcHSkew: 0x0
    (II) CHROME(0): CrtcVDisplay: 0x258
    (II) CHROME(0): CrtcVBlankStart: 0x258
    (II) CHROME(0): CrtcVSyncStart: 0x259
    (II) CHROME(0): CrtcVSyncEnd: 0x25c
    (II) CHROME(0): CrtcVBlankEnd: 0x26e
    (II) CHROME(0): CrtcVTotal: 0x26e
    (II) CHROME(0): ViaModeSecondCRTC
    (II) CHROME(0): ViaPanelScale: 1024,600 -> 1024,600
    (II) CHROME(0): mode: 0x8808110
    (II) CHROME(0): mode->name: 0x880a770
    (II) CHROME(0): mode->name: 1024x600
    (II) CHROME(0): ViaSecondCRTCSetMode
    (II) CHROME(0): Setting up 1024x600
    (II) CHROME(0): ViaSetSecondaryFIFO
    (II) CHROME(0): ViaSetSecondaryDotclock to 0x508c01
    (II) CHROME(0): ViaSetUseExternalClock
    (II) CHROME(0): ViaSecondDisplayChannelEnable
    (II) CHROME(0): ViaDisplayDisableCRT
    (II) CHROME(0): ViaDisplayDisableSimultaneous
    (II) CHROME(0): VIAAdjustFrame
    (II) CHROME(0): VIAAdjustFrame
    (II) CHROME(0): - Blanked
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card2
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card3
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card4
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card5
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card6
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card7
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card8
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card9
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card10
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card11
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card12
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card13
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card14
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card2
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card3
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card4
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card5
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card6
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card7
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card8
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card9
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card10
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card11
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card12
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card13
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card14
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    (EE) [drm] drmOpen failed.
    (EE) CHROME(0): [dri] DRIScreenInit failed.  Disabling DRI.
    (II) CHROME(0): - Visuals set up
    (II) CHROME(0): VIAInternalScreenInit
    (II) CHROME(0): - B & W
    (II) CHROME(0): CursorStart: 0xffc0000
    (II) CHROME(0): Using 1800 lines for offscreen memory.
    (II) CHROME(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        8x8 color pattern filled rectangles
        Solid Lines
        Dashed Lines
        Image Writes
        Setting up tile and stipple cache:
            32 128x128 slots
            20 256x256 slots
            32 8x8 color pattern slots
    (==) CHROME(0): Backing store disabled
    (II) CHROME(0): - Backing store set up
    (II) CHROME(0): - SW cursor set up
    (II) CHROME(0): VIAHWCursorInit
    (II) CHROME(0): - Def Color map set up
    (II) CHROME(0): VIALoadPalette
    (II) CHROME(0): VIALoadRgbLut
    (II) CHROME(0): - Palette loaded
    (II) CHROME(0): DPMS enabled
    (II) CHROME(0): - DPMS set up
    (II) CHROME(0): - Color maps etc. set up
    (II) CHROME(0): direct rendering disabled
    (II) CHROME(0): Benchmarking video copy.  Less time is better.
    (--) CHROME(0): Timed   libc YUV420 copy... 1813105. Throughput: 522.2 MiB/s.
    (--) CHROME(0): Timed kernel YUV420 copy... 1789621. Throughput: 529.1 MiB/s.
    (--) CHROME(0): Timed    SSE YUV420 copy... 960929. Throughput: 985.3 MiB/s.
    (--) CHROME(0): Timed    MMX YUV420 copy... 1706519. Throughput: 554.8 MiB/s.
    (--) CHROME(0): Ditching 3DNow! YUV420 copy. Not supported by CPU.
    (--) CHROME(0): Timed   MMX2 YUV420 copy... 1029823. Throughput: 919.4 MiB/s.
    Freed 9834496 (pool 1)
    (--) CHROME(0): Using SSE YUV42X copy for video.
    (WW) CHROME(0): [XvMC] XvMC is not supported on this chipset.
    (WW) CHROME(0): Option "RenderAccel" is not used
    (II) CHROME(0): - Done
    (==) RandR enabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    (II) AIGLX: Screen 0 is not DRI capable
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
    (II) GLX: Initialized DRISWRAST GL provider for screen 0
    (**) Option "CoreKeyboard"
    (**) HP Keyboard: always reports core events
    (**) Option "Protocol" "standard"
    (**) HP Keyboard: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) HP Keyboard: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) HP Keyboard: XkbModel: "pc105"
    (**) Option "XkbLayout" "se"
    (**) HP Keyboard: XkbLayout: "se"
    (**) Option "CustomKeycodes" "off"
    (**) HP Keyboard: CustomKeycodes disabled
    (**) Option "Protocol" "Auto"
    (**) Option "Device" "/dev/input/mice"
    (II) HP Touchpad: Setting mouse protocol to "ExplorerPS/2"
    (**) HP Touchpad: Device: "/dev/input/mice"
    (**) HP Touchpad: Protocol: "Auto"
    (**) Option "CorePointer"
    (**) HP Touchpad: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons"
    (**) HP Touchpad: Emulate3Buttons, Emulate3Timeout: 50
    (**) HP Touchpad: ZAxisMapping: buttons 4 and 5
    (**) HP Touchpad: Buttons: 9
    (**) HP Touchpad: Sensitivity: 1
    (II) evaluating device (HP Keyboard)
    (II) XINPUT: Adding extended input device "HP Keyboard" (type: KEYBOARD)
    (II) evaluating device (HP Touchpad)
    (II) XINPUT: Adding extended input device "HP Touchpad" (type: MOUSE)
    (II) HP Touchpad: Setting mouse protocol to "ExplorerPS/2"
    (II) HP Touchpad: ps2EnableDataReporting: succeeded
    (II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device Video Bus
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (EE) config/hal: NewInputDeviceRequest failed
    (II) config/hal: Adding input device Macintosh mouse button emulation
    (EE) config/hal: NewInputDeviceRequest failed
    ===============================================================
    And my glxinfo:
    ===============================================================
    name of display: :0.0
    display: :0  screen: 0
    direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
    server glx vendor string: SGI
    server glx version string: 1.2
    server glx extensions:
        GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
        GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
        GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
        GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
    client glx vendor string: S3G
    client glx version string: 1.4
    client glx extensions:
        GLX_SGI_make_current_read,  GLX_SGIX_fbconfig,  GLX_SGIX_pbuffer,
         GLX_ARB_get_proc_address, GLX_EXT_texture_from_pixmap,
        GLX_MESA_copy_sub_buffer
    GLX version: 1.2
    GLX extensions:
        GLX_SGI_make_current_read, GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap,
        GLX_MESA_copy_sub_buffer
    OpenGL vendor string: Mesa Project
    OpenGL renderer string: Software Rasterizer
    OpenGL version string: 1.4 (2.1 Mesa 7.2)
    OpenGL extensions:
        GL_EXT_texture_env_add, GL_ARB_multitexture, GL_ARB_transpose_matrix,
        GL_ARB_texture_env_add, GL_ARB_texture_cube_map,
        GL_ARB_texture_compression, GL_ARB_texture_border_clamp,
        GL_ARB_point_parameters, GL_ARB_texture_env_combine,
        GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3,
        GL_ARB_texture_mirrored_repeat, GL_ARB_depth_texture, GL_ARB_shadow,
        GL_ARB_shadow_ambient, GL_ARB_window_pos, GL_ARB_occlusion_query,
        GL_ARB_texture_non_power_of_two, GL_ARB_point_sprite,
        GL_EXT_texture_rectangle, GL_EXT_abgr, GL_EXT_blend_color,
        GL_EXT_texture3D, GL_EXT_packed_pixels, GL_SGIS_texture_lod,
        GL_EXT_rescale_normal, GL_EXT_vertex_array, GL_SGIS_generate_mipmap,
        GL_SGIS_texture_edge_clamp, GL_SGIS_texture_border_clamp,
        GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_point_parameters,
        GL_EXT_draw_range_elements, GL_EXT_bgra, GL_EXT_separate_specular_color,
        GL_EXT_secondary_color, GL_EXT_multi_draw_arrays, GL_EXT_fog_coord,
        GL_EXT_texture_env_combine, GL_EXT_blend_func_separate,
        GL_EXT_stencil_wrap, GL_NV_texgen_reflection, GL_EXT_texture_lod_bias,
        GL_NV_blend_square, GL_NV_texture_rectangle, GL_EXT_shadow_funcs,
        GL_ATI_texture_env_combine3, GL_SGI_color_matrix,
        GL_EXT_texture_edge_clamp
    2 GLX Visuals
       visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
    id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
    0x21 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
    0x3b 32 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
    32 GLXFBConfigs:
       visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
    id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
    0x3c  0 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
    0x3d  0 tc  0 32  0 r  .  .  8  8  8  8  0  0  0 16 16 16 16  0 0 Slow
    0x3e  0 tc  0 32  0 r  y  .  8  8  8  8  0  0  0 

  • Single Sign-On and Data Visibility Rights

    Hello,
    I was wondering whether anyone has any best practices for implementing single sign on and user identification with Excelsius.
    More specifically, I need to interrogate user role, and limit certain data visibility based on that role.
    For example, a sales rep may only see certain data for their own territories, but the regional and national managers can see more.
    With the emphasis in improving enterprise integration with the new version coming up, I'm also wondering if there are any improvements included for this aspect.
    Thanks in advance.
    Derick

    Hi Derick,
    I want to make our discussion into 2 parts
    1) Sign on
    2) Viewing data based on the Heirarchy
    1)Before discussing about the Sign on i want to know which connectivity you are using ? Live offcie or QaaWS.
    2) We can make the second point possible in two ways One is with providing restriction at universe level
    and the other one is through the use of flash variables.
    Using flash variables:
    The main idea of using flash variables is reading the User ID from BO authentication and based on that we fetch the Heirarchy level of that user. Then we use some excel logic to hide the data from Low level heirarchy(Here we use Dynamic Visibility for components).
    I hope this is what you ar looking for....
    If so i have more points to acheive such scenario.
    Please provide the your BO environment details, such that it will be easy to identify the better best wat to acheve it.
    Regards,
    AnjaniKumar C.A.

  • Data visibility problem in PDF file generated from R/3 system

    Hi all,
    We are converting the output of a Smartform into a PDF format. From this smart from, we receive data in OTF format, after which the required data is converted from OTF format to PDF format. Then PDF data is sent through mail using FM SO_NEW_DOCUMENT_ATT_SEND_API1 as an attachment. 
    For the above mentioned Smartform, we have defined Paragraph & Character font type as 'TIMES' in smart style. But when we receive the PDF file (through mail), some data of appears in other fonts:
    1) When PDF file is generated from Development system, the different font types which are used by PDF are Arial and Times-Roman. In this case, we are able to see the PDF output and faced no major problems because both of these fonts are supported by PDF file format.
    2) When PDF file is generated from Testing system, the font types which is used by PDF is Arial. In this case, we are able to see the PDF output because this font is supported by PDF file format.
    3) When PDF file is generated from Production system, the different font types which are used by PDF are Arial, Times-Roman and PBRS. Here, we are able to see the data which is displayed in Arial font and Times-Roman font. But we are not able to see the data which is displayed in PBRS font because this type of font is not supported by PDF file format. If we copy the distorted text from PDF file and paste it in MS-Word then the required data is clearly visible and that is due to the reason that MS-Word supports PBRS font.
    But as per smart style we have used only 'TIMES' font, then why different fonts are appearing in PDF file?
    What settings are required to be done to make this data visible?
    Any pointer to solve this issue will be really appreciable. Thanks in advance for your help.
    Thanks and Regards,
    Dheeraj Tolani

    Hi,
    check the following
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    business content
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    https://websmp203.sap-ag.de/co
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
    (navigate with expand left nodes)
    also co-pa
    http://help.sap.com/saphelp_nw04/helpdata/en/53/c1143c26b8bc00e10000000a114084/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1910ab90-0201-0010-eea3-c4ac84080806
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff61152b-0301-0010-849f-839fec3771f3
    FI-CO 'Data Extraction -Line Item Level-FI-CO'
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
    FI-GL
    http://help.sap.com/saphelp_nw04/helpdata/en/c9/fe943b2bcbd11ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_470/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm
    http://www.sapgenie.com/sapfunc/fi.htm
    Please reward for the same.

  • I'm having trouble scheduling a "repeat" for an appointment that recurs, e.g., "the second Thursday of each month," rather than on a specific date.   It seems that it can only repeat a given date.  Am I missing something??

    For iCalendar:  Is there a way to schedule a repeat for an event that repeats, e.g., "the 2d Thursday of the month."?  All I see are options that will repeat (every day, month, year, etc.) on a given date.  Am I missing something?

    loyev1,
    There should also be a "Custom..." selection in the (every day, month, year, etc.) drop down menu. Select "Custom..."
    Then:

  • Date type-specific Customizing missing for date type ACTActPln

    Hi all.
    I'm using a Web Service obtained by copying the CRM 7.0 built-in WS APPTACTCRTRC.
    I'm using it to create Appointments using an Adobe Interactive Form.
    It goes everything fine (a Date is created in the system, with all the input data properly set) excepted the dates...
    The WS uses two TIMESTAMPS, TIMESTAMP_FROM for StartDateTime and TIMESTAMP_TO for EndDateTime, whereas the GUI transaction to create Dates accepts dates and times in separated fields.
    Going in Debug I can see that the execution ends with the following error, referred to the involved entity (CRM_APPOINTMENT):
    Date type-specific Customizing missing for date type ACTActPln
    CRM_APPOINTMENT uses date profile 0000000001 with three possible date types: ORDERACTUAL, ORDERPLANNED and ORDERPROPOSED and I cannot find anywhere date type ACTActPln (just to add it in customizing).
    Is anyone able to enlight me?
    Thank you in advance!
    Alessandro
    PS I've years of experience in Java programming but I'm quite new to the SAP world. Maybe the problem is not a problem at all, but it seems to me as such. Even if it has a trivial solution, please let me know. Thx!

    Hi,
    Well I was about to write that you should enter date in decimal format. but you already did that as mentioned in How to set a date in a Form where the bound date format is a decimal?
    In response to following from above thread (copied for others to understand my response)
    Hi all.
    I'm successfully using the LiveCycle Designer and I've managed to remotely create Appointments using a CRM Web Service (a mere copy of APPTACTCRTRC).
    The only problem I'm encountering is that I'm not able to set the dates/times (start and end of the appointment).
    Dragging each of the two fields from the WSDL based Data Connection I obtain a Decimal Field limited to 15 digits.
    How can I write a date and time in such a field?
    I've tried with a retroverse date as YYYYMMDDHHmmss (for example, 20100301124500) but it does not work
    (the appointment is indeed created, but with the start date and time fields filled with
    the current date/time and the end date and time fields filled with the current date and time plus 10 minutes).
    The retroverse date above is only 14 digit long, so, maybe, this is the problem.
    But, given the field definition, I'm not able to fill a blank space between the date and the time.
    I'm not able to put a dot either.
    What should I do?
    Any suggestions?
    Thank you in advance.
    Alessandro
    15 digit in UTC time format here is fraction of second so you should enter 201003011245000 (add one more zero).
    14th Oct 2010 16:00 should be written as 201010141600000, so just try it and and see if it works, I guess if you do not supply end time then by default it will be starttime + 10 min but this is just guess.
    Regards,
    Gourav

  • Select Members in Data Forms via UDA or Substitutionvariable

    Hello,
    I want to select members in row or colum dimension of a Planning data form via an UDA. But it is only possible to select members via hierarchy (member, sibling, parent,...).
    Is there a possibility to select members via UDA?
    What I tried is:
    1.) in the definition of the dimension members for the dimension "Period" in the data form I filled in: "@UDA(Period,FC01)".
    I get the error "The member @UDA(Period does not exist or you do not have access to it."
    2.) Instead of the UDA I tried to use a Substitutionvariable "&PER_LIST"
    This works if the Substitutionvariable contains only one member. It doesn't work if it contains more than one member (comma-separated list).
    I get the error: "A substitution variable required for this calculation is undefined. Variable: PER_LIST" (even though the variable exists and I selected it in the member selection dialog)
    Can anyone help? I'm using Hyp. System 9.3.1.
    Thanks in advance,
    Nicole

    I would love to see the ability to select EDA's from Planning Forms, it would definately make life a little easier.
    As CL says, attributes are great at filtering forms and BR's, their only drawback is that you can only use them on sparse dimensional members.
    To get round this problem i've relied on security to filter out the accounts i do not need to see in the forms for the specific users, and kept the form selection on @IDESCENDANTS(Account_Parent).
    If you wish to filter on the Period dimension and this is a dense dimension, can you not get round the problem with rollups and, for example, @DESCENDANTS(Q1) to only return 3 months in the form, it really depends on your outline structure.

  • SPROXY: No connection to Integration Builder (only local data visible)

    ¡Hola!
    When I try to access the transaction SPROXY I get the message "No connection to Integration Builder (only local data visible)".
    I already did the configuration steps described in the XI Configuration Guide, section 8: Connecting Business Systems with an Integration Engine to the Central Integration Server.  I also checked that the parameters in the Exchange Profile were correct.
    Transaction SLDCHECK is working ok.  The TCP/IP connections SAPSLDAPI & LCRSAPRFC work OK when I do Test Connection.
    In transaction SPROXY, when I do Connection Test the first 2 steps work fine, but I get an error on the last two:
    1.  The address of the Integration Builder must be stored in the R/3
         System
         =>Check/maintain with report SPROX_CHECK_IFR_ADDRESS
    Result: OK: Address maintained
    2. The HTTP connection of the R/3 application server must function
    correctly
    =>Check with report SPROX_CHECK_HTTP_COMMUNICATION
    Result: HTTP communication functioning
    The following 2 steps return an error:
    3. The Integration Builder server must be running correctly
    =>Check with report SPROX_CHECK_IFR_RESPONSE
    Result: Integration Builder data not understood
    4. Proxy generation must correctly interpret the data of the
    Integration Builder
    ==>Check with report SPROX_CHECK_IFR_CONNECTION
    Result: Integration Builder data not understood
    I've been looking in the forums and weblogs but haven't been able to figure out what could be wrong with my system.   Can someone please help?
    Thanks and Regards,
    Carlos

    Carlos,
    Check Global Configuration data in R3  using TC : SXMB_ADM.
    You need to set values..Role of Business System : Application System and Corresponding Integration server details.
    Also check your HTTP RFC connection : INTEGRATION_DIRECTORY_HMI
    Nilesh
    Message was edited by:
            Nilesh Kshirsagar

  • Abap ProxiesNoconnection to Integration Builder(only generic data Visible)

    When we are executing SPROXY from R/3(ECC 6.0)
    Getting components ie connected to XI Integration Builder
    But when we are executing SPROXY from XI Server , we are not getting connection to Integration Builder, Getting error message like No connection to Integration Builder (only generic data Visible)

    Hi Satish,
    Make sure that you are having the following RFC's successful from your ECC/BW system towards your XI Integration Builder.
    1) LCRSAPRFC. - type T
    2) SAPSLDAPI  - type T
    3) PI_INTEGRATIONSERVER - type H
    Make sure that settings are done in SLDAPICUST tcode.
    Check whether the ICM is running & HTTP port is active in SMICM.
    please check the below link as well.. it will be more helpful.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50d69314-1be0-2b10-11ab-8045021f0c3a?QuickLink=index&overridelayout=true
    Regards,
    Dino

  • No connection to integration builder (Only local data visible)

    Hi,
    I am created Interface objects in IR but it is not reflected in SPROXY (ECC 5.0). It is showing like this no connection to integration builder (Only local data visible) please can you  help me necessary configuration.
    Regards,
    -Prabakar.A

    HI Prabakar,
    the Business System SM59 destinations LCRSAPRFC & SAPSLDAPI
      should have the Program IDs
    SAPSLDAPI _UNICODE.
    LCRSAPRFC_UNICODE
    See the online help for connecting Biusiness Systems
    [Connecting Unicode Business Systems|http://help.sap.com/saphelp_nwpi71/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm]
    see also
    [Connecting to the Integration Server|http://help.sap.com/saphelp_nwpi71/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm]
    Regards
    Kenny
    Edited by: Kenny Scott on Feb 25, 2010 5:02 PM

  • No connection to Integration Builder (only generic data visible)

    hi,
    I am facing one problem in IDES system when connecting to proxy from my XI system.
    No connection to Integration Builder (only generic data visible)
    For this when I tried to create rfcu2019s type G and H in the IDES system, in that both rfcu2019s when testing it is giving the following msg.
    ICM_HTTP_CONNECTION_FAILED
    Is anything I need to do before connecting to RFCu2019s type G and H.
    thanks in advance.

    Hi,
    Check this URL:
    SAP NetWeaver Troubleshooting Guide:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    Thanks,
    Boopathi

  • No connection to Integration Builder (only generic data visible)(SPROXY)

    Dear All,
    I am Establishing connection between BW and XI.
    I am getting "No connection to Integration Builder (only generic data visible)" error while opening SPROXY T-Code, also it shows user Menu Disable.
    Please suggest me to solve the error.
    thanks,
    RP

    hi RP,
    I too had same problem, below are the things taken care and finally fixed.
    1. SLDAPICUST settings pointing to SLD system & port
    2. Create SAPSLDAPI & LCRSAPRFC RFCs pointing to program ID created with SLD and XI system using VA (JCo RFC provider)
    3. Set the require settings with RZ70 pointing to XI system name & HTTP port
    4.Create ABAP based HTTP RFC pointing to Target system (XI system ) with HTTP port (smicm-goto-services) and path prefix with "/sap/xi/engine?type=entry" (without quotes). Ensure this RFC is existing at both the ends (source & target).
    5. If incase all ready the Technical System & Business existing at SLD for your business system, you may require to remove them and add them back/manually.
    Please let me know if any more info require.
    Thanks
    Chandra

  • No Connection to Integration Builder (only local data visible): from R/3

    Hi,
    I am also facing the same problem. I maintained the RFC destinations in R/3 properly. I did Test Connection and for RFC destination its working fine. I maintained proper values in SLDAPICUST. When I run SLDCHECK I got the following error.
    <b>Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code 4
    => Check whether the SLD is running!
    Summary: Connection to SLD does not work
    => Check SLD function and configurations</b>
    Otherwise access to XI Profile works fine. But then when I run SPROXY I am getting the same message <b>No Connection to Integration Builder (only local data visible)</b>
    I also checked the following report =>Check with report SPROX_CHECK_IFR_RESPONSE (3rd option) its giving informational message <b>Integration Builder data not understood</b>, for the 4th report  ==>Check with report SPROX_CHECK_IFR_CONNECTION, it is also showing the same above information message.
    Looking forward for the response,
    Appreciate your help,
    Thanks and Regards,
    Jagadish

    Hi,
    I had the same problem and I have already solved it.
    You have just to apply the following sap notes :
    1232805 - Saint: Queue calculation for an add-on with CRT´s fail.
    769120 - Support Package for APPINT 200_620
    The first one is to update tha SPAM/SAINT to v 30 and the second one allow you use the pi/xi objects on application system.
    There is another sap note 689847, but you just apply this if the sap notes above described did not work.
    Paulo Correa

Maybe you are looking for