Fujitsu L20T-2 monitor

I bought a Fujitsu L20T-2 to connect to my iMac. I used the mini DVI connector with the VGA connector cable supplied with the monitor.
I get a NO Signal repsonse on the monitor. Has anyone successfully connected one of these monitors and can you hekp me with my problem?

One option is to press F10 to open the Code Inspector and drag that window onto your secondary monitor.

Similar Messages

  • External display acting strange in Lion?

    I'm having a problem i can't work around. I have a mid 2010 macbook pro, i5 2,53ghz running Mac OS X Lion 10.7.2. I have an apple mini display to DVI adapter and a Fujitsu Siemens 27" monitor with a native resolution of 1920x1200 with HDMI, DVI and VGA input. The monitor works just great on VGA and on DVI, no problems at all and at the correct resolution.
    I now bought a DVI to HDMI cable and inserted the HDMI in the monitor and the DVI in de minidisplay port and it ONLY works on 1080i. ALL other resolutions result in a flickering image of the screen filled with pixels in all kinda colors and then a véry short image of the actual desktop in bad quality. I thought it was the cable so i tested it on a windows based laptop and it worked fine.
    !!! The most crazy thing is; when i boot into Windows 7 on Boot Camp, the setup works GREAT at the native resolution of 1920x1200. So the cable isnt broken, the minidisplay to DVI adapter isn't broken and the monitor isn't broken because it just works in bootcamp. As soon as i reboot into mac the same problem occurs... Any ideas?

    To fix your issue is too complicated and lengthy to go into all of it here as it sounds like a hardware issue, it will require the services of person very familiar and experienced with Mac's to first recover your data and then restore OS X back to a functional state which may or may not require new hardware/software installed.
    If your under warranty or AppleCare, take it in for service.
    You can also hire the services of a local Mac computer support technician experienced in these matters.
    Have them look at your Wifi, RAM amount, extra storage and computer backup proceedures in the process.
    Good Luck.

  • Sun MC and PrimePower

    Hi,
    according to this page http://www.sun.com/software/products/sunmanagementcenter/ds/datasheet.xml#10 SunMC 3.6.1 supports PrimePower Machines:
    Hardware platforms
    SPARC and x86 platform-based workstations and servers
    The Solaris Container Manager 3.6.1 addon also supports the Fujitsu-Siemens PRIMEPOWER SPARC processor server line running Solaris.
    Is this a correct reading ? And, if yes, where can I download the necessary modules (including installation instructions)?
    TIA
    Bernd

    Hi Bernd,
    according to this page
    http://www.sun.com/software/products/sunmanagementcent
    er/ds/datasheet.xml#10 SunMC 3.6.1 supports
    PrimePower Machines:<snip>
    Is this a correct reading ? And, if yes, where can I
    download the necessary modules (including
    installation instructions)?What that says is that the Solaris Container Manager (SCM) addon is "supported" on PrimePower, but the rest of SunMC officially isn't. SCM is only a subset of SunMC.
    But both Fujitsu and Sun hardware run the same basic version of Solaris, so almost all of SunMC itself works fine. And there's no special addons or files needed... just download SunMC 3.6.1 and run the regular installer on your PrimePower box. The only thing you'll be missing today is the "Config Reader" line of modules... so while you'll have all the CPU/memory/swap/files/process info you won't have Fujitsu-specific hardware monitoring.
    This is one of those cases where what's "supported" and what "works" are two different things :)
    Note: Halcyon modules also run fine (and you can buy support contracts for them) on these SunMC-on-PrimePower configurations (http://www.halcyoninc.com/products/a-z.php)
    Regards,
    [email protected]

  • Dual monitoring from Macbook pro to Fujitsu laptop

    hi i would like to use an old laptop as a dual monitor for my macbook pro. i have onhand a VGA adaptor that I bought recently. I have tried connecting macbook to a monitor and it worked just fine. but with the laptop, it couldn't work.
    i tried connecting my macbook to the fujitsu laptop. but i wasnt able to extend the desktop to the fujitsu laptop.
    i want to use my macbook as the primary screen for me to work on, but i place other reports on the other laptop.
    can anybody help?
    thanks in advance

    I do this kind of thing quite a bit, and it all depends on what kind of storage options that are available.
    1. I have several pen drives, a few 16gb in storage, that I use to transfer data from one computer to another. If you have 26gb of music, the transfer should't be too long.
    2. I also own a few Seagate portable drives, which are great for transferring data. It's also fairly fast. I use a USB to USB2 cable to do the transfer; my cable came with the drive.
    One easy way to figure out which cable you need would be to visit your Apple Store; they should be able to tell which cable to purchase.

  • Mac Mini using Fujitsu Siemens monitor

    I am using a Fujitsu Siemens monitor with my new Mac Mini. 
    What is displayed on it is too large for the screen and I have to keep moving the bar from left to right and using the up and down arrows.
    Also I can't see the Apple icon so that I can get the Apple menu .
    Any help please?

    Under Display settings u can change the zoom....so u can get in the screen. I'd the same problmen with my TV.

  • [Solved]Synaptics Touchpad not working at all on Fujitsu Siemens UH552

    Hi,
    I have just installed Arch on my Fujitsu Siemens UH552 laptop. Everything works except for the touchpad which seems to get loaded by Xorg, but when in X it doesn't work. I have tried both using /dev/input/event* and /dev/input/mouse0 as device paths, neither works.
    xf86-input-evdev and xf86-input-synaptics are installed.
    I have tried running both with the default 10-evdev.conf, with 10-synaptics.conf, with both, and without both.
    TLDR SOLUTION: https://bbs.archlinux.org/viewtopic.php … 3#p1189603
    My current 10-synaptics.conf:
    Section "InputClass"
    Identifier "Touchpad Catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "synaptics"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    EndSection
    Xorg.0.log
    [ 2275.127]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 2275.130] X Protocol Version 11, Revision 0
    [ 2275.131] Build Operating System: Linux 3.4.8-1-ARCH x86_64
    [ 2275.132] Current Operating System: Linux corvo 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64
    [ 2275.132] Kernel command line: root=/dev/sda2 rootflags=subvol=__active ro initrd=/boot/initramfs-linux.img BOOT_IMAGE=/boot/vmlinuz-linux
    [ 2275.134] Build Date: 27 August 2012 08:04:39AM
    [ 2275.135]
    [ 2275.136] Current version of pixman: 0.26.2
    [ 2275.138] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2275.138] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2275.142] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 1 13:16:01 2012
    [ 2275.143] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2275.144] (==) No Layout section. Using the first Screen section.
    [ 2275.144] (==) No screen section available. Using defaults.
    [ 2275.144] (**) |-->Screen "Default Screen Section" (0)
    [ 2275.144] (**) | |-->Monitor "<default monitor>"
    [ 2275.144] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 2275.144] (**) | |-->Device "Intel Graphics"
    [ 2275.144] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 2275.144] (==) Automatically adding devices
    [ 2275.144] (==) Automatically enabling devices
    [ 2275.144] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 2275.144] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 2275.144] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2275.144] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2275.144] (II) Loader magic: 0x7c8b00
    [ 2275.144] (II) Module ABI versions:
    [ 2275.144] X.Org ANSI C Emulation: 0.4
    [ 2275.144] X.Org Video Driver: 12.1
    [ 2275.144] X.Org XInput driver : 16.0
    [ 2275.144] X.Org Server Extension : 6.0
    [ 2275.144] (--) PCI:*(0:0:2:0) 8086:0166:10cf:16c2 rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00002000/64
    [ 2275.144] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 2275.144] (II) LoadModule: "extmod"
    [ 2275.144] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 2275.145] (II) Module extmod: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] Module class: X.Org Server Extension
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension MIT-SCREEN-SAVER
    [ 2275.145] (II) Loading extension XFree86-VidModeExtension
    [ 2275.145] (II) Loading extension XFree86-DGA
    [ 2275.145] (II) Loading extension DPMS
    [ 2275.145] (II) Loading extension XVideo
    [ 2275.145] (II) Loading extension XVideo-MotionCompensation
    [ 2275.145] (II) Loading extension X-Resource
    [ 2275.145] (II) LoadModule: "dbe"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 2275.145] (II) Module dbe: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] Module class: X.Org Server Extension
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension DOUBLE-BUFFER
    [ 2275.145] (II) LoadModule: "glx"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2275.145] (II) Module glx: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (==) AIGLX enabled
    [ 2275.145] (II) Loading extension GLX
    [ 2275.145] (II) LoadModule: "record"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 2275.145] (II) Module record: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.13.0
    [ 2275.145] Module class: X.Org Server Extension
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension RECORD
    [ 2275.145] (II) LoadModule: "dri"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 2275.145] (II) Module dri: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension XFree86-DRI
    [ 2275.145] (II) LoadModule: "dri2"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2275.145] (II) Module dri2: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.2.0
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension DRI2
    [ 2275.145] (II) LoadModule: "intel"
    [ 2275.146] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 2275.146] (II) Module intel: vendor="X.Org Foundation"
    [ 2275.146] compiled for 1.12.3.901, module version = 2.20.5
    [ 2275.146] Module class: X.Org Video Driver
    [ 2275.146] ABI class: X.Org Video Driver, version 12.1
    [ 2275.146] (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,
    Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
    Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
    Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
    Haswell Server (GT2+), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
    Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
    Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
    Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
    Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
    Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
    Haswell CRW Server (GT2), Haswell CRW Server (GT2+)
    [ 2275.146] (--) using VT number 7
    [ 2275.149] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.149] drmOpenDevice: open result is 7, (OK)
    [ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 2275.150] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.150] drmOpenDevice: open result is 7, (OK)
    [ 2275.150] drmOpenByBusid: drmOpenMinor returns 7
    [ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 2275.150] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.150] drmOpenDevice: open result is 8, (OK)
    [ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 2275.150] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.150] drmOpenDevice: open result is 8, (OK)
    [ 2275.150] drmOpenByBusid: drmOpenMinor returns 8
    [ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 2275.150] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 2275.150] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 2275.150] (==) intel(0): RGB weight 888
    [ 2275.150] (==) intel(0): Default visual is TrueColor
    [ 2275.150] (**) intel(0): Option "AccelMethod" "sna"
    [ 2275.150] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
    [ 2275.151] (**) intel(0): Framebuffer tiled
    [ 2275.151] (**) intel(0): Pixmaps tiled
    [ 2275.151] (**) intel(0): 3D buffers tiled
    [ 2275.151] (**) intel(0): Throttling enabled
    [ 2275.151] (**) intel(0): Delayed flush enabled
    [ 2275.151] (**) intel(0): "Tear free" disabled
    [ 2275.151] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 2275.151] (II) intel(0): Output LVDS1 has no monitor section
    [ 2275.152] (II) intel(0): found backlight control interface acpi_video0 (type 'firmware')
    [ 2275.152] (II) intel(0): Output VGA1 has no monitor section
    [ 2275.153] (II) intel(0): Output HDMI1 has no monitor section
    [ 2275.193] (II) intel(0): Output DP1 has no monitor section
    [ 2275.193] (II) intel(0): EDID for output LVDS1
    [ 2275.193] (II) intel(0): Manufacturer: LGD Model: 371 Serial#: 0
    [ 2275.193] (II) intel(0): Year: 2012 Week: 0
    [ 2275.193] (II) intel(0): EDID Version: 1.3
    [ 2275.193] (II) intel(0): Digital Display Input
    [ 2275.193] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
    [ 2275.193] (II) intel(0): Gamma: 2.20
    [ 2275.193] (II) intel(0): No DPMS capabilities specified
    [ 2275.193] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 2275.193] (II) intel(0): First detailed timing is preferred mode
    [ 2275.193] (II) intel(0): redX: 0.589 redY: 0.347 greenX: 0.343 greenY: 0.555
    [ 2275.193] (II) intel(0): blueX: 0.160 blueY: 0.124 whiteX: 0.313 whiteY: 0.329
    [ 2275.193] (II) intel(0): Manufacturer's mask: 0
    [ 2275.193] (II) intel(0): Supported detailed timing:
    [ 2275.193] (II) intel(0): clock: 70.0 MHz Image Size: 293 x 165 mm
    [ 2275.193] (II) intel(0): h_active: 1366 h_sync: 1402 h_sync_end 1438 h_blank_end 1476 h_border: 0
    [ 2275.193] (II) intel(0): v_active: 768 v_sync: 772 v_sync_end 780 v_blanking: 790 v_border: 0
    [ 2275.193] (II) intel(0): LG Display
    [ 2275.193] (II) intel(0): LP133WH2-TLF1
    [ 2275.193] (II) intel(0): EDID (in hex):
    [ 2275.193] (II) intel(0): 00ffffffffffff0030e4710300000000
    [ 2275.193] (II) intel(0): 00160103801d10780afc359658578e29
    [ 2275.193] (II) intel(0): 1f505400000001010101010101010101
    [ 2275.193] (II) intel(0): 010101010101581b566e500016302424
    [ 2275.194] (II) intel(0): 480025a5100000190000000000000000
    [ 2275.194] (II) intel(0): 00000000000000000000000000fe004c
    [ 2275.194] (II) intel(0): 4720446973706c61790a2020000000fe
    [ 2275.194] (II) intel(0): 004c503133335748322d544c463100ce
    [ 2275.194] (II) intel(0): EDID vendor "LGD", prod id 881
    [ 2275.194] (II) intel(0): Printing DDC gathered Modelines:
    [ 2275.194] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
    [ 2275.194] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Printing probed modes for output LVDS1
    [ 2275.194] (II) intel(0): Modeline "1366x768"x60.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
    [ 2275.194] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
    [ 2275.194] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
    [ 2275.194] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
    [ 2275.194] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
    [ 2275.194] (II) intel(0): EDID for output VGA1
    [ 2275.195] (II) intel(0): EDID for output HDMI1
    [ 2275.236] (II) intel(0): EDID for output DP1
    [ 2275.236] (II) intel(0): Output LVDS1 connected
    [ 2275.236] (II) intel(0): Output VGA1 disconnected
    [ 2275.236] (II) intel(0): Output HDMI1 disconnected
    [ 2275.236] (II) intel(0): Output DP1 disconnected
    [ 2275.236] (II) intel(0): Using exact sizes for initial modes
    [ 2275.236] (II) intel(0): Output LVDS1 using initial mode 1366x768
    [ 2275.236] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 2275.236] (**) intel(0): Display dimensions: (290, 160) mm
    [ 2275.236] (**) intel(0): DPI set to (119, 121)
    [ 2275.236] (II) Loading sub module "dri2"
    [ 2275.236] (II) LoadModule: "dri2"
    [ 2275.237] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2275.237] (II) Module dri2: vendor="X.Org Foundation"
    [ 2275.237] compiled for 1.12.4, module version = 1.2.0
    [ 2275.237] ABI class: X.Org Server Extension, version 6.0
    [ 2275.237] (==) Depth 24 pixmap format is 32 bpp
    [ 2275.237] (II) intel(0): SNA initialized with IvyBridge backend
    [ 2275.237] (==) intel(0): Backing store disabled
    [ 2275.237] (==) intel(0): Silken mouse enabled
    [ 2275.237] (II) intel(0): HW Cursor enabled
    [ 2275.237] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 2275.238] (==) intel(0): DPMS enabled
    [ 2275.239] (II) intel(0): [DRI2] Setup complete
    [ 2275.239] (II) intel(0): [DRI2] DRI driver: i965
    [ 2275.239] (II) intel(0): direct rendering: DRI2 Enabled
    [ 2275.239] (==) intel(0): hotplug detection: "enabled"
    [ 2275.239] (--) RandR disabled
    [ 2275.239] (II) Initializing built-in extension Generic Event Extension
    [ 2275.239] (II) Initializing built-in extension SHAPE
    [ 2275.239] (II) Initializing built-in extension MIT-SHM
    [ 2275.239] (II) Initializing built-in extension XInputExtension
    [ 2275.239] (II) Initializing built-in extension XTEST
    [ 2275.239] (II) Initializing built-in extension BIG-REQUESTS
    [ 2275.239] (II) Initializing built-in extension SYNC
    [ 2275.239] (II) Initializing built-in extension XKEYBOARD
    [ 2275.239] (II) Initializing built-in extension XC-MISC
    [ 2275.239] (II) Initializing built-in extension SECURITY
    [ 2275.239] (II) Initializing built-in extension XINERAMA
    [ 2275.239] (II) Initializing built-in extension XFIXES
    [ 2275.239] (II) Initializing built-in extension RENDER
    [ 2275.239] (II) Initializing built-in extension RANDR
    [ 2275.239] (II) Initializing built-in extension COMPOSITE
    [ 2275.239] (II) Initializing built-in extension DAMAGE
    [ 2275.250] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 2275.250] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 2275.250] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 2275.250] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 2275.250] (II) AIGLX: Loaded and initialized i965
    [ 2275.250] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 2275.251] (II) intel(0): switch to mode 1366x768 on crtc 3 (pipe 0)
    [ 2275.276] (II) intel(0): Setting screen physical size to 361 x 203
    [ 2275.319] (II) config/udev: Adding input device Power Button (/dev/input/event6)
    [ 2275.319] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2275.319] (II) LoadModule: "evdev"
    [ 2275.319] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 2275.320] (II) Module evdev: vendor="X.Org Foundation"
    [ 2275.320] compiled for 1.12.3.901, module version = 2.7.3
    [ 2275.320] Module class: X.Org XInput Driver
    [ 2275.320] ABI class: X.Org XInput driver, version 16.0
    [ 2275.320] (II) Using input driver 'evdev' for 'Power Button'
    [ 2275.320] (**) Power Button: always reports core events
    [ 2275.320] (**) evdev: Power Button: Device: "/dev/input/event6"
    [ 2275.320] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2275.320] (--) evdev: Power Button: Found keys
    [ 2275.320] (II) evdev: Power Button: Configuring as keyboard
    [ 2275.320] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
    [ 2275.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 2275.320] (**) Option "xkb_rules" "evdev"
    [ 2275.320] (**) Option "xkb_model" "evdev"
    [ 2275.320] (**) Option "xkb_layout" "se"
    [ 2275.355] (II) config/udev: Adding input device Fujitsu FUJ02E3 (/dev/input/event3)
    [ 2275.356] (**) Fujitsu FUJ02E3: Applying InputClass "evdev keyboard catchall"
    [ 2275.356] (II) Using input driver 'evdev' for 'Fujitsu FUJ02E3'
    [ 2275.356] (**) Fujitsu FUJ02E3: always reports core events
    [ 2275.356] (**) evdev: Fujitsu FUJ02E3: Device: "/dev/input/event3"
    [ 2275.356] (--) evdev: Fujitsu FUJ02E3: Vendor 0 Product 0x6
    [ 2275.356] (--) evdev: Fujitsu FUJ02E3: Found keys
    [ 2275.356] (II) evdev: Fujitsu FUJ02E3: Configuring as keyboard
    [ 2275.356] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input3/event3"
    [ 2275.356] (II) XINPUT: Adding extended input device "Fujitsu FUJ02E3" (type: KEYBOARD, id 7)
    [ 2275.356] (**) Option "xkb_rules" "evdev"
    [ 2275.356] (**) Option "xkb_model" "evdev"
    [ 2275.356] (**) Option "xkb_layout" "se"
    [ 2275.357] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
    [ 2275.357] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 2275.357] (II) Using input driver 'evdev' for 'Video Bus'
    [ 2275.357] (**) Video Bus: always reports core events
    [ 2275.357] (**) evdev: Video Bus: Device: "/dev/input/event9"
    [ 2275.357] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 2275.357] (--) evdev: Video Bus: Found keys
    [ 2275.357] (II) evdev: Video Bus: Configuring as keyboard
    [ 2275.357] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9/event9"
    [ 2275.357] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 2275.358] (**) Option "xkb_rules" "evdev"
    [ 2275.358] (**) Option "xkb_model" "evdev"
    [ 2275.358] (**) Option "xkb_layout" "se"
    [ 2275.359] (II) config/udev: Adding input device Fujitsu FUJ02B1 (/dev/input/event2)
    [ 2275.359] (**) Fujitsu FUJ02B1: Applying InputClass "evdev keyboard catchall"
    [ 2275.359] (II) Using input driver 'evdev' for 'Fujitsu FUJ02B1'
    [ 2275.359] (**) Fujitsu FUJ02B1: always reports core events
    [ 2275.359] (**) evdev: Fujitsu FUJ02B1: Device: "/dev/input/event2"
    [ 2275.359] (--) evdev: Fujitsu FUJ02B1: Vendor 0 Product 0x6
    [ 2275.359] (--) evdev: Fujitsu FUJ02B1: Found keys
    [ 2275.359] (II) evdev: Fujitsu FUJ02B1: Configuring as keyboard
    [ 2275.359] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/FUJ02B1:00/input/input2/event2"
    [ 2275.359] (II) XINPUT: Adding extended input device "Fujitsu FUJ02B1" (type: KEYBOARD, id 9)
    [ 2275.359] (**) Option "xkb_rules" "evdev"
    [ 2275.359] (**) Option "xkb_model" "evdev"
    [ 2275.359] (**) Option "xkb_layout" "se"
    [ 2275.360] (II) config/udev: Adding input device Power Button (/dev/input/event5)
    [ 2275.360] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2275.360] (II) Using input driver 'evdev' for 'Power Button'
    [ 2275.360] (**) Power Button: always reports core events
    [ 2275.360] (**) evdev: Power Button: Device: "/dev/input/event5"
    [ 2275.360] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2275.360] (--) evdev: Power Button: Found keys
    [ 2275.360] (II) evdev: Power Button: Configuring as keyboard
    [ 2275.361] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5/event5"
    [ 2275.361] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 10)
    [ 2275.361] (**) Option "xkb_rules" "evdev"
    [ 2275.361] (**) Option "xkb_model" "evdev"
    [ 2275.361] (**) Option "xkb_layout" "se"
    [ 2275.362] (II) config/udev: Adding input device Lid Switch (/dev/input/event4)
    [ 2275.362] (II) No input driver specified, ignoring this device.
    [ 2275.362] (II) This device may have been added with another device file.
    [ 2275.362] (II) config/udev: Adding input device FJ Camera (/dev/input/event7)
    [ 2275.362] (**) FJ Camera: Applying InputClass "evdev keyboard catchall"
    [ 2275.362] (II) Using input driver 'evdev' for 'FJ Camera'
    [ 2275.362] (**) FJ Camera: always reports core events
    [ 2275.362] (**) evdev: FJ Camera: Device: "/dev/input/event7"
    [ 2275.363] (--) evdev: FJ Camera: Vendor 0x10f1 Product 0x1a44
    [ 2275.363] (--) evdev: FJ Camera: Found keys
    [ 2275.363] (II) evdev: FJ Camera: Configuring as keyboard
    [ 2275.363] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input7/event7"
    [ 2275.363] (II) XINPUT: Adding extended input device "FJ Camera" (type: KEYBOARD, id 11)
    [ 2275.363] (**) Option "xkb_rules" "evdev"
    [ 2275.363] (**) Option "xkb_model" "evdev"
    [ 2275.363] (**) Option "xkb_layout" "se"
    [ 2275.364] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
    [ 2275.364] (II) No input driver specified, ignoring this device.
    [ 2275.364] (II) This device may have been added with another device file.
    [ 2275.364] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
    [ 2275.364] (II) No input driver specified, ignoring this device.
    [ 2275.364] (II) This device may have been added with another device file.
    [ 2275.365] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
    [ 2275.365] (II) No input driver specified, ignoring this device.
    [ 2275.365] (II) This device may have been added with another device file.
    [ 2275.365] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 2275.365] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2275.365] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 2275.366] (**) AT Translated Set 2 keyboard: always reports core events
    [ 2275.366] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 2275.366] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 2275.366] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 2275.366] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
    [ 2275.366] (**) Option "xkb_rules" "evdev"
    [ 2275.366] (**) Option "xkb_model" "evdev"
    [ 2275.366] (**) Option "xkb_layout" "se"
    [ 2275.366] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
    [ 2275.366] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Touchpad Catchall"
    [ 2275.366] (II) LoadModule: "synaptics"
    [ 2275.366] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 2275.367] (II) Module synaptics: vendor="X.Org Foundation"
    [ 2275.367] compiled for 1.12.2, module version = 1.6.2
    [ 2275.367] Module class: X.Org XInput Driver
    [ 2275.367] ABI class: X.Org XInput driver, version 16.0
    [ 2275.367] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 2275.367] (**) Option "Device" "/dev/input/event8"
    [ 2275.367] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 2275.367] (**) Option "TapButton1" "1"
    [ 2275.367] (**) Option "TapButton2" "2"
    [ 2275.367] (**) Option "TapButton3" "3"
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 2275.367] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input8/event8"
    [ 2275.368] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
    [ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
    [ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.040
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 2275.368] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 2275.368] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 2275.368] (II) No input driver specified, ignoring this device.
    [ 2275.368] (II) This device may have been added with another device file.
    [ 2275.368] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
    [ 2275.368] (II) No input driver specified, ignoring this device.
    [ 2275.368] (II) This device may have been added with another device file.
    xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Fujitsu FUJ02E3 id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Fujitsu FUJ02B1 id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ FJ Camera id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    running
    dmesg | grep -i synaptics
    doesn't show anything. However running
    dmesg | grep -i psmouse
    returns a lot of
    psmouse serio1: bad data from KBC - timeout
    Last edited by flako (2012-11-08 09:44:59)

    I have tried doing that with both linux mint, and now fedora live usb. Neither one loads the touchpad correctly.  So yeah, our problems weren't really related
    Anyway, I tried looking into the
    psmouse serio1: bad data from KBC - timeout
    messages, and tried running psmouse proto (defined in /etc/modprobe.conf/psmouse.conf) as both raw and imps as per https://answers.launchpad.net/ubuntu/+s … ion/206950 Unfortunately, that didn't solve anything. Using the raw setting meant that the touchpad wasn't loaded at all (as in not appearing in the Xorg.log at all).
    The laptop is quite new, but at the same time what i figured from the touchpad vendor & product ID, the touchpad itself isn't. So it should technically work. Before installing arch i booted into windows to see if everything worked, and found no issues with the touchpad. So I have ruled out any hardware errors. Maybe its just the Fn-key that doesn't work yet in Linux? But that doesn't explain the "psmouse serio1: bad data from KBC - timeout" Any pointers to where I should look/ what commands I should run to delve deeper into this issue?
    Last edited by flako (2012-09-09 12:10:51)

  • DVI- HDMI discoloration on HDTV (as second monitor)

    Hello all.
    I have been having some issues when using my Philips CRT 30" 1080i HDTV as a second monitor via a DVI->HDMI cable. There seems to be a discoloration that occurs (my best guess being a "green" discoloration) that occurs in the top left corner of the screen. It is made all the more apparent when you then unplug, and a purple haze is left in the corner of the "blue" video input channel. (i imagine the green discoloration on the blue channel yields purple).
    From what I can tell, this problem does not occur on any other video input (say, a Wii on the composite channel, or an XBOX on the component, etc).
    I had heard rumblings that it could be, in order of bad to worst: a bad HDMI cable, a bad HDMI input on the television, or the television going bad period.
    Wanted to know if any of you have had or heard of similar experiences. Need to decide soon if I'm going to had to just buy a new HDMI cable, or if I need to buy a new television/monitor for a job coming up.
    Thanks in advance!
    Brian
    4/30/10 2:47 PM
    Hardware:
    Hardware Overview:
    Model Name: MacBook Pro
    Model Identifier: MacBookPro3,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.4 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 4 MB
    Memory: 4 GB
    Bus Speed: 800 MHz
    Boot ROM Version: MBP31.0070.B07
    SMC Version (system): 1.16f11
    Sudden Motion Sensor:
    State: Enabled
    Network:
    Bluetooth DUN:
    Type: PPP (PPPSerial)
    Hardware: Modem
    BSD Device Name: Bluetooth-Modem
    Has IP Assigned: No
    Service Order: 0
    Ethernet:
    Type: Ethernet
    Hardware: Ethernet
    BSD Device Name: en0
    Has IP Assigned: No
    Service Order: 1
    FireWire:
    Type: FireWire
    Hardware: FireWire
    BSD Device Name: fw0
    Has IP Assigned: No
    Service Order: 2
    AirPort:
    Type: AirPort
    Hardware: AirPort
    BSD Device Name: en1
    Has IP Assigned: Yes
    Service Order: 3
    Software:
    System Software Overview:
    System Version: Mac OS X 10.6.3 (10D573)
    Kernel Version: Darwin 10.3.0
    64-bit Kernel and Extensions: No
    Time since boot: 12 minutes
    ATA:
    ATA Bus:
    MATSHITADVD-R UJ-857E:
    Model: MATSHITADVD-R UJ-857E
    Revision: ZA0E
    Detachable Drive: No
    Protocol: ATAPI
    Unit Number: 0
    Socket Type: Internal
    Low Power Polling: Yes
    Power Off: Yes
    Audio (Built In):
    Intel High Definition Audio:
    Device ID: 0x106B00A0
    Audio ID: 44
    Available Devices:
    Speaker:
    Connection: Internal
    Headphone:
    Connection: Combo
    Internal Microphone:
    Connection: Internal
    Line In:
    Connection: Combo
    S/P-DIF Out:
    Connection: Combo
    S/P-DIF In:
    Connection: Combo
    Bluetooth:
    Apple Bluetooth Software Version: 2.3.1f4
    Hardware Settings:
    Vendor ID: 0x5ac
    Product ID: 0x8205
    Devices (Paired, Favorites, etc):
    Device:
    Type: Mouse
    Firmware Version: 0x200
    Services: Mighty Mouse
    Manufacturer: Broadcom (0x2, 0x314)
    Vendor ID: 0x5ac
    Product ID: 0x30c
    Diagnostics:
    Power On Self-Test:
    Last Run: 4/30/10 2:35 PM
    Result: Passed
    Disc Burning:
    MATSHITA DVD-R UJ-857E:
    Firmware Revision: ZA0E
    Interconnect: ATAPI
    Burn Support: Yes (Apple Shipping Drive)
    Cache: 2048 KB
    Reads DVD: Yes
    CD-Write: -R, -RW
    DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
    Write Strategies: CD-TAO, CD-SAO, DVD-DAO
    Media: To show the available burn speeds, insert a disc and choose View > Refresh
    Ethernet Cards:
    pci168c,24:
    Type: Other Network Controller
    Bus: PCI
    Slot: PCI Slot 5
    Vendor ID: 0x168c
    Device ID: 0x0024
    Subsystem Vendor ID: 0x106b
    Subsystem ID: 0x0087
    Revision ID: 0x0001
    Link Width: x1
    BSD name: en1
    Kext name: AirPortAtheros.kext
    Location: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros.k ext
    Version: 422.19.10
    Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA:
    Name: ethernet
    Type: Ethernet Controller
    Bus: PCI
    Vendor ID: 0x11ab
    Device ID: 0x436a
    Subsystem Vendor ID: 0x11ab
    Subsystem ID: 0x00ba
    Revision ID: 0x0013
    Link Width: x1
    BSD name: en0
    Kext name: AppleYukon2.kext
    Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleYukon2 .kext
    Version: 3.1.14b1
    FireWire:
    FireWire Bus:
    Maximum Speed: Up to 800 Mb/sec
    G-Drive mini Device 00:
    Manufacturer: G-TECH
    Model: 0x0
    GUID: 0x1C0D02E00B0A3E
    Maximum Speed: Up to 800 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Sub-units:
    G-Drive mini Device 00 Unit:
    Unit Software Version: 0x10483
    Unit Spec ID: 0x609E
    Firmware Revision: 0x103
    Product Revision Level: FBEO
    Sub-units:
    G-Drive mini Device 00 SBP-LUN:
    Capacity: 250.06 GB (250,059,350,016 bytes)
    Removable Media: Yes
    BSD Name: disk1
    Partition Map Type: APM (Apple Partition Map)
    S.M.A.R.T. status: Not Supported
    Volumes:
    disk1s3:
    Capacity: 249.93 GB (249,925,091,328 bytes)
    Available: 21.68 GB (21,684,412,416 bytes)
    Writable: Yes
    File System: Journaled HFS+
    Graphics/Displays:
    NVIDIA GeForce 8600M GT:
    Chipset Model: GeForce 8600M GT
    Type: GPU
    Bus: PCIe
    PCIe Lane Width: x16
    VRAM (Total): 256 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0407
    Revision ID: 0x00a1
    ROM Revision: 3175
    Displays:
    Color LCD:
    Resolution: 1440 x 900
    Pixel Depth: 32-Bit Color (ARGB8888)
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Built-In: Yes
    Display Connector:
    Status: No Display Connected
    Memory:
    Memory Slots:
    ECC: Disabled
    BANK 0/DIMM0:
    Size: 2 GB
    Type: DDR2 SDRAM
    Speed: 667 MHz
    Status: OK
    Manufacturer: 0x7F7F7F7F7F9B0000
    Part Number: 0x4354323536363441433636372E4D31364647
    BANK 1/DIMM1:
    Size: 2 GB
    Type: DDR2 SDRAM
    Speed: 667 MHz
    Status: OK
    Manufacturer: 0x7F7F7F7F7F9B0000
    Part Number: 0x4354323536363441433636372E4D31364647
    PCI Cards:
    pci168c,24:
    Type: Other Network Controller
    Driver Installed: Yes
    Bus: PCI
    Slot: PCI Slot 5
    Vendor ID: 0x168c
    Device ID: 0x0024
    Subsystem Vendor ID: 0x106b
    Subsystem ID: 0x0087
    Revision ID: 0x0001
    Link Width: x1
    Link Speed: 2.5 GT/s
    Serial-ATA:
    Intel ICH8-M AHCI:
    Vendor: Intel
    Product: ICH8-M AHCI
    Link Speed: 1.5 Gigabit
    Negotiated Link Speed: 1.5 Gigabit
    Description: AHCI Version 1.10 Supported
    FUJITSU MHW2160BHPL:
    Capacity: 160.04 GB (160,041,885,696 bytes)
    Model: FUJITSU MHW2160BHPL
    Revision: 0081001C
    Native Command Queuing: Yes
    Queue Depth: 32
    Removable Media: No
    Detachable Drive: No
    BSD Name: disk0
    Partition Map Type: GPT (GUID Partition Table)
    S.M.A.R.T. status: Verified
    Volumes:
    disk0s2:
    Capacity: 131.94 GB (131,936,026,624 bytes)
    Available: 23.73 GB (23,733,391,360 bytes)
    Writable: Yes
    File System: Journaled HFS+
    disk0s3:
    Capacity: 27.63 GB (27,626,639,360 bytes)
    Available: 13.65 GB (13,652,635,648 bytes)
    Writable: Yes
    File System: Journaled HFS+
    USB:
    USB High-Speed Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBEHCI
    PCI Device ID: 0x2836
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0xfd
    Built-in iSight:
    Product ID: 0x8502
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 1.45
    Serial Number: 607F59A99AB2811A (03.00)
    Speed: Up to 480 Mb/sec
    Manufacturer: Apple Inc.
    Location ID: 0xfd400000
    Current Available (mA): 500
    Current Required (mA): 500
    USB High-Speed Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBEHCI
    PCI Device ID: 0x283a
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0xfa
    USB Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x2835
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0x3a
    USB Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x2834
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0x1a
    Bluetooth USB Host Controller:
    Product ID: 0x8205
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 19.65
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Inc.
    Location ID: 0x1a100000
    Current Available (mA): 500
    Current Required (mA): 0
    USB Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x2830
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0x1d
    USB Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x2831
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0x3d
    USB Bus:
    Host Controller Location: Built-in USB
    Host Controller Driver: AppleUSBUHCI
    PCI Device ID: 0x2832
    PCI Revision ID: 0x0003
    PCI Vendor ID: 0x8086
    Bus Number: 0x5d
    Apple Internal Keyboard / Trackpad:
    Product ID: 0x021a
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 0.18
    Speed: Up to 12 Mb/sec
    Manufacturer: Apple Computer
    Location ID: 0x5d200000
    Current Available (mA): 500
    Current Required (mA): 40
    IR Receiver:
    Product ID: 0x8242
    Vendor ID: 0x05ac (Apple Inc.)
    Version: 0.16
    Speed: Up to 1.5 Mb/sec
    Manufacturer: Apple Computer, Inc.
    Location ID: 0x5d100000
    Current Available (mA): 500
    Current Required (mA): 100
    AirPort:
    Software Versions:
    Menu Extra: 6.2.1 (621.1)
    configd plug-in: 6.2 (620.15.1)
    System Profiler: 6.0 (600.9)
    Network Preference: 6.2.1 (621.1)
    AirPort Utility: 5.5.1 (551.19)
    IO80211 Family: 3.1 (310.6)
    Interfaces:
    en1:
    Card Type: AirPort Extreme (0x168C, 0x87)
    Firmware Version: Atheros 5416: 2.0.19.10
    Locale: FCC
    Country Code: US
    Supported PHY Modes: 802.11 a/b/g/n
    Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165
    Status: Connected

    Problems like that are caused by stray magnetism that cause misalignment of the electron beams from landing on the proper phosphor color. The set itself has a demagnetizer, but sometimes the magnetism is too strong for the built-in demagnetizer to overcome. But calling in a TV repair person to do a demagnetization is, I'm afraid, a throw back to bygone days. But that's what your TV needs.

  • ORACLE SERVER AND UNIX TP MONITOR-1

    제품 : ORACLE SERVER
    작성날짜 : 2002-05-17
    ====================================================================
    Subject: Oracle Server and UNIX Transaction Processing Monitors - 1
    =====================================================================
    PURPOSE
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o What is a Transaction Processing Monitor (TPM)?
         o What is the X/Open Distributed Transaction Processing Model?
         o How does the Oracle Server works with TPMs?
         o How should I position TPMs with my customer?
         o What Oracle products must a customer purchase?
         o Where can my customer purchase a TPM?
         o Availability and packaging
    Explanation & Example
    What is a Transaction Processing Monitor?
    =========================================
    Under UNIX, a Transaction Processing Monitor (TPM) is a tool that coordinates
    the flow of transaction requests between front-end client processes that issue
    requests and back-end servers that process them. A TPM is used as
    the "glue" to coordinate transactions that require the services of several
    different types of back-end processes, such as application servers and
    resource managers, possibly distributed over a network.
    In a typical TPM environment, front-end client processes perform screen
    handling and ask for services from back-end server processes via calls to the
    TPM. The TPM then routes the requests to the appropriate back-end server
    process or server processes, wherever they are located on the network. Through
    configuration information, the TPM knows what services are available and where
    they are located. Generally, the back-end server processes are specialized so
    that each one handles one type of requested service. The TPM provides
    location transparency as well and can send messages through the network
    utilizing lower-level transport services such as TCP/IP or OSF DCE.
    The back-end servers process the requests as necessary and
    return the results back to the TP monitor. The TP monitor then routes
    these results back to the original front-end client process.
    A TPM is instrumental in the implementation of truly distributed processing.
    Front-end clients and back-end processes have no knowledge of each
    other. They operate as separate entities, and it is this concept that provides
    flexibility in application development. Front-end and back-end processes are
    developed in the UNIX client-server style, with each side optimized for its
    particular task. Server functionality can be deployed in stages, which makes
    it easy to add functionality as needed later in the product cycle. It also
    makes it easy to distribute both the front-end and back-end processes
    throughout the network on the most appropriate hardware for the job. In
    addition, multiple back-end server processes of the same type might be
    activated to handle increasing numbers of users.
    What is the X/Open Distributed Transaction Processing Model?
    ============================================================
    The X/Open Transaction Processing working group has been working
    for several years to establish a standard architecture to implement
    distributed transaction processing on open systems. In late 1991,
    X/Open published the initial Distributed Transaction Processing (DTP)
    model specification and defined the first of several interfaces that
    exist between the components of the model. Subsequently, other publications
    and a revised model specification have been published.
    An important function of the TPM in the X/Open DTP model is the
    synchronization of any commits and rollbacks that are required to complete
    a distributed transaction request. The Transaction Manager (TM) portion
    of the TPM is the entity responsible for ordering when distributed commits
    and rollbacks will take place. Thus, if a distributed application program
    is written to take advantage of the TM portion of the TPM, then it,
    and not the DBMS, becomes responsible for enabling the two-phase commit
    process. Article 2 has more detail on this model.
    How does the Oracle Server work with TPMs?
    ==========================================
    When a TPM is used without invoking an X/Open TM component to manage the
    transactions, Oracle Server needs no special functionality. The transaction
    will be managed by Oracle itself. However, when the TPM X/Open TM component
    is used to manage the transaction, the Oracle Server, that is the Oracle DBMS,
    acts as a Resource Manager--a type of back-end process. In the case of
    TPM-managed transactions, the TM needs a way to tell the RMs about the stages
    of the transaction. This is done by a standard, X/Open defined interface
    called XA. Article 2 of of this document gives more information about both
    the X/Open model and Oracle7's use of XA.
    Because the XA interface provides a standard interface between the TM and the
    resource manager, it follows that the TM can communicate with any XA-compliant
    resource manager (e.g., RDBMS), and, conversely, that a resource manager can
    communicate with any XA-compliant TM. Thus, the Oracle Server, beginning with
    Oracle7, works with any XA-compliant TM.
    How should I position TPMs with my customer?
    ============================================
    There's been a great deal of confusion about the need for TPM technology. Some
    software suppliers, most notably IBM, will assert that a TPM like CICS is a
    necessary requirement for high volume OLTP. Other vendors will assert that
    there is seldom a need for such technology. And yet others promote TPMs as
    providers of higher transaction throughput.
    From Oracle's standpoint, customers might choose TPM technology under any of
    the following conditions:
    1. For heterogeneous database access, especially for 2PC capability
         This means that a TPM can be used to coordinate 2PC between Oracle
         DBMS and any other XA-compliant database, such as Informix. This
         does NOT provide SQL heterogeneity - SQL calls to Oracle DBMS may be
         different than SQL calls to Informix. The TPM handles the routing,
         communication, and two-phase commit portion of the transaction, but
         does not translate one type of SQL call into another.
    2. For transaction monitoring and workload control
         The leading TPMs supply tools to actively manage the flow of
         transactions between clients and servers and to load balance the work
         load across all available processors on a network, not just on a
         single multi-processor system. Some TPMs also have the ability to
         dynamically bring up additional back-end services during peak work
         hours.
    3. For more flexible application development and installation
         One of the key features of the DTP model is application modularity.
         Modularity, that is, the decomposition of a large program into small,
         easily defined, coded and maintained "mini-programs" makes it easy to
         add new functionality as needed. Modularity also makes it much easier
         to distribute the front-end and back-end processes and the resource
         managers across hardware throughout a network.
    4. For isolating the client from details of the data model
    By using the service oriented programming model, the client program
         is unaware of the data model. The service can be recoded to use a
         different one with no change to the client. To get this advantage,
         the application developer must explicitly code the server and client
         to fit the service model.
    5. For connection of thousands of users
         TP Monitors, because of their three-tier architecture, can be used
         to connect users to an intermediate machine or machines, removing
         the overhead of handling terminal connections from the machine
         actually running the database. See Article 4 for more information.
    There are also several cases where TPM technology is not the right answer.
    These include:
    1. If the customer is simply looking for a performance improvement
         The customer may have heard a theory that "higher performance
         is possible for large scale applications only if they use a
         TP monitor". First, no performance gain can be achieved for
         existing applications; in fact, they won't even run under a TP
         Monitor without recoding. Second, performance improvements have
         only been documented for large numbers of users, and "large"
         means many hundreds or thousands. Without a TP Monitor,
         Oracle Server can handle several hundred users with its normal
         two-task architecture and several times that using the Multi
         Threaded Server. For more on performance, see Article 4.
    2. If the customer has made large investment in his existing Oracle
    applications
         TP monitor applications must be designed from the ground up to take
         advantage of TP monitor technology. Current Oracle customers will find
         it difficult to "retrofit" a TP monitor to their existing applications.
         The Multi Threaded Server, on the other hand, allows the use of
         existing Oracle applications without change.
    3. If the customer is committed to the Oracle tool set
         Currently, none of Oracle's front-end tools (Oracle Forms, etc.) is
         designed to work with TP monitors. It is possible to invoke a
         TP Monitor by using user exits. However, the fact that the TP
         Monitor model hides the data model from the client means that only
         the screen display parts of Forms can be used, not the automatic
         mapping from screen blocks to tables.
    4. If the customer does not have a staff of experienced software engineers
         This is still very young technology for UNIX. There is not a lot of
    knowledge in the industry on how to build TP monitor applications or
    what techniques are most useful and which are not. Furthermore,
         integrating products from different vendors, even with the support
         of standard interfaces, is more complex than deploying an integrated
         all-Oracle solution. Because TP monitor technology is fairly
         complex, we recommend that you let the TP monitor supplier promote
         the virtues of their technology and differentiate themselves from
         their competitors.
    What Oracle products must a customer purchase?
    ==============================================
    If your customer is only interested in building Oracle-managed TP Monitor
    transactions, the only Oracle products required are the Oracle Server
    and the appropriate Oracle precompiler for whatever language the
    application is being written in--most likely C or Cobol. If TPM-managed
    transactions are required, the Oracle7 Server with the distributed option
    is also required. SQL*Net is optional because the TPM takes care of the
    network services. Article 2 describes when you would choose to have the TP
    Monitor manage the transactions.
    Where can my customer purchase a TPM?
    =====================================
    There are many vendors offering the UNIX TPM products. (Oracle does not
    relicense TPMs.) Information on the most well known products is provided
    below:
    The following support XA:
    Product & Vendor     FCS          Known OS/Platform Ports
    "TUXEDO System/T"     1986          UNIX SVR4 & SVR3: Amdahl, AT&T,
    UNIX System Laboratories          Bull, Compaq, Dell, Fujitsu, ICL,
    190 River Road                    Motorola, Olivetti, Pyramid,Sequent,
    Summit, NJ 07901               Sun, Toshiba, Unisys, NCR, Stratus
                             Other: IBM AIX, HP/UX, DEC Ultrix
    "TOP END"      1992          UNIX SVR4: NCR
    NCR Corporation
    1334 S. Patterson Blvd.
    Dayton, OH 45479
    "ENCINA"          1992          IBM AIX, HP, Sun (SunOS and Solaris)
    Transarc Corporation               Other: OS/2, DOS, HP-UX, STRATUS
    707 Grant Street (Depends on DCE)
    Pittsburgh, PA 15219
    "CICS/6000" 1993          AIX: IBM
    IBM Corporation                    (Depends on DCE)
    "CICS 9000" 1994          HP-UX
    HP
    The following do not currently support XA:
    Product & Vendor     FCS          Known OS/Platform Ports
    "VIS/TP"          unknown          unknown
    VISystems, Inc.
    11910 Greenville Avenue
    Dallas, TX 75243
    "UniKix"          1990          UNIX: ARIX, AT&T, NCR, Pyramid,
    UniKix                     Sequent, Sun, Unisys      
    "MicroFocus           1993          SCO Unix, AIX
    Transaction System"
    Micro Focus
    26 West Street
    Newbury RG13 1JT
    UK
    There are also several third parties who are reselling the products listed
    above.
    In addition, Groupe Bull, Digital, Siemens-Nixdorf, and several other hardware
    vendors are planning to redesign their proprietary TPMs to be XA-compliant and
    suitable for use on UNIX systems.
    Availability and Packaging
    ==========================
    On what platforms is the XA Library available?
    Oracle provides the XA interface with Oracle7 Server on all platforms that
    support an XA-compliant TPM. Support for XA is included as part of the
    Oracle7 Server distributed option and has no extra charge in and of itself.
    Which version of XA does Oracle Server support?
    Oracle7 Server supports the Common Application Environment (CAE) version of
    XA, based on the specification published by X/Open in late 1991. It will
    require that the TM also be at that level. This means Tuxedo /T version 4.2,
    for example.
    Oracle Server supports all required XA functions. There are some optional
    features Oracle Server does not support, such as asynchronous operation.
    None of those options affect application programming.
    Page (2/4)
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Oracle Server Working with UNIX TPMs
         o TPM Application Architecture
    The questions answered in part 2 provide additional detail to the information
    provided in part 1.
    Oracle Server Working with UNIX TP Monitors
    ===========================================
    Do I need XA to use Oracle Server with TPMs? If I don't use it, what are
    the consequences?
    There are a number of real applications running today with Oracle Server and
    TPMs but not using XA. To use a TPM with Oracle without using XA, the user
    would write an "application server" program which could handle one or more
    "services". For example, a server program might handle a service called
    "debit_credit". The key requirement is that the entire transaction,
    including the "commit work", must be executed within a single service. This
    is the restriction which XA will remove, as we'll see later. Each
    server process can serially handle requests on behalf of different clients.
    Because a server process can handle many client processes, this can
    reduce the total number of active processes on the server system,
    thereby reducing resource requirements and possibly increasing overall
    throughput.
    When Oracle is used with a TPM in this mode, we call it an Oracle-managed
    transaction since the transaction commit or rollback is done with a SQL
    statement.
    What is XA? How does XA help Oracle7 work with UNIX TPMs?
    XA is an industry standard interface between a Transaction Manager and a
    Resource Manager. A Resource Manager (RM) is an agent which
    controls a shared, recoverable resource; such a resource can be
    returned to a consistent state after a failure. For example, Oracle7 Server
    is an RM and uses its redo log and undo segments to be able to do this.
    A Transaction Manager (TM) manages a transaction including the
    commitment protocol and, when necessary, the recovery after a failure.
    Normally, Oracle Server acts as its own TM and manages its own commitment
    and recovery. However, using a standards-based TM allows Oracle7 to
    cooperate with other heterogeneous RMs in a single transaction.
    The commonly used TPMs include a TM component for this purpose. In order to
    use the TM capability of the TPM rather than Oracle7's own transaction
    management, the application uses a transaction demarcation API (called TX)
    provided by the TPM rather than the SQL transaction control statements (e.g.
    "commit work"). For each TX call, the TM then instructs all RMs, by the
    appropriate XA commands, to follow the two-phase commit protocol. We
    call this a TPM-managed transaction.
    The following picture shows these interfaces within a monolithic application
    program model. This is the model most commonly described in the
    DTP literature. We'll see later what the picture looks like when we add
    Oracle7 and when we switch to a modularized client-server application
    program model.
              | |
              | |
              | Application Program (AP) |
              | |
              | |
                   | | |                    |
    Resource Manager API | | | |
    (e.g. SQL) -----|--|------------- | TX API
              | | v |          |
              --------|-------------     |          |
              | v | | v
         ---------------------- | | --------------------
         | | | | | |
         | Resource | | |<----->| Transaction |
         | Managers | |--- | Manager |
         | (RMs) | |<-------->| (TM) |
         | |--- | |
         | |<----------->| |
         ---------------------- XA --------------------
                        Interface
    The XA interface is an interface between two system components, not
    an application program interface; the application program does
    not write XA calls nor need to know the details of this interface.
    The TM cannot do transaction coordination without the assistance of
    the RM; the XA interface is used to get that assistance.
    How does the DTP Model support client-server?
    The above picture was actually simplified to make it easier to explain
    the role of XA. In a true distributed transaction architecture, there
    are multiple applications, each with an Application Program, a Resource
    Manager, and a Transaction Manager. The applications communicate by
    using a Communication Resource Manager. The CRM is generally provided
    as a component of the TPM. It includes the transaction information when
    it sends messages between applications, so that both applications can
    act of behalf of the same transaction. The following picture
    illustrates this:
    Client Application
    | AP |
    ||| | |
    SQL ||| | TX | CRM
    ||V V | API
    -||-- ----- |
    | |V | | | V
    --|-- |<---| | -----
    | V || | | | |
    ----- |<----| TM |<-->| CRM |
    | || | |XA+ | |
    | RMs |<-----| | -----
    | | XA | | A
    ----- ----- | Server Application
    | -----------------------------
    | | AP |
    | -----------------------------
    | ||| | |
    | SQL ||| | TX | CRM
    | ||V V | API
    | -||-- ----- |
    | | |V | | | V
    | --|-- |<---| | -----
    | | V || | | | |
    | ----- |<----| TM |<-->| CRM |
    | | || | |XA+ | |
    | | RMs |<-----| | -----
    | | | XA | | A
    | ----- ----- |
    | |
    | |
    -------- |
    / |
    / |
    / |
    Most TP Monitor products include both a TM and a CRM, and also provide
    additional functions such as task scheduling and workload monitoring.
    What is XA+? What does Oracle need to do to comply with it?
    XA+ is an interface that lets the X/Open model actually be distributed
    because it allows a communication resource manager to tell a TM on the
    server that a message from a client just came in for a particular
    transaction. Oracle is not currently planning to provide an X/Open
    communication resource manager, so we don't have any plans right now
    to do XA+. Version 2 of the DTP model paper from X/Open describes it.
    The status of the current XA+ specification is "snapshot".
    When would I choose an Oracle-managed transaction vs a TPM-managed
    transaction?
    Oracle Server is very efficient at managing its own transactions. If
    the TPM manages the transaction, in general some additional overhead
    will be incurred.
    The two main reasons a customer might prefer to use a TPM-managed
    transaction are as follows:
    (1) He may need to update RMs from different vendors. Experience so far
    has been that the most common case is wanting to update both Oracle and
    a TP Monitor managed resource such as a transactional queuing service
    in the same transaction (see Article 3).
    (2) He may want to use the model of having several different services in
    a transaction, even to the same database. For example, the
    "debit_credit" service could be split into a "debit" service and a
    "credit" service. This is a very attractive model, but this type of
    modularity does exact a performance penalty (see Article 4).
    Can I get a version of XA to run on Oracle Server version 6?
    No, the XA functionality uses two underlying mechanisms in the Oracle
    Server which are not available in version 6: two-phase commit and
    session switching. The upi calls for these functions do not not exist
    in version 6.
    When would I use XA vs Oracle7 to coordinate all-Oracle distributed
    transactions?
    Generally speaking, Oracle Server should be used to coordinate all-Oracle
    distributed transactions. The main reason for using XA to coordinate
    transactions would be that you want to use the TP Monitor service-oriented
    architecture. That is, you would like to construct an application built of
    services and service requests in order to benefit from the modularity and
    workload control such an environment provides.
    TP Monitor Application Architecture
    ===================================
    What might a TP Monitor application look like?
    Most TPM applications will consist of two more more programs, where
    there are front-end client programs which request services and back-end
    server programs which provide services. In this case, the TPM supplies an
    additional capability which is transactional communication. The client
    describes the boundaries of the transaction, through the use of the TX API,
    and the TPM relays that transaction information to each requested service.
    The overall application structure generally looks like the following in the
    client-server model. The "TP Monitor Services" box is not necessarily a
    process. It could be one or more processes, or just libraries coordinating
    through shared memory. Each client process and server process could be on
    a different machine. Normally, the application server processes would be
    connected to their Oracle Server processes using the IPC driver; the TPM
    would be used to deliver messages between application client processes on
    one machine and application server processes on another. However, the
    application server processes could also be connected with the standard
    Oracle SQL*Net to shadow processes on different machines. This might be
    useful if one of the databases was on a machine which did not support TPMs.
    |Application| |Application| |Application|
    | Client 1 | | Client 2 | | Client 3 |
    | | | | | |
    \ TPM API | TPM API / TPM API
    | |
    | TP Monitor Services |
    | |
         | --------------------- |
    | | Transaction Manager | |
    ---------------|---------------|---------------------
    TPM API | | XA | XA | TPM API
    | | inter- | inter- |
              | | face | face |
              | | | |
    ----------- | | -----------
    |Application| | | |Application|
    | Server 1 |--- ---| Server 2 |
    | (Pro*C) | | | | (Pro*C) |
    | SQL | SQL
    | | | |
    | Resource ----------- ----------- |
    | Manager | | | | |
    | | Oracle7 | | Oracle7 | |
    | | Server | | Server | |
    | | Process | | Process | |
    | | | | | |
    | ----------- ----------- |
    | | | |
    | ----------------------------------------------------- |
    | | | |
    | | SGA | |
    | | | |
    | ----------------------------------------------------- |
    | |
    Application client programs might be written in C and be linked with
    TPM libraries. Alternatively, they could use a screen painter product.
    Application server programs would be written in Pro*C or Pro*COBOL and
    be linked with TPM libraries, the normal Oracle7 user-side libraries
    and libxa.a. The Oracle7 Server process is the regular Oracle7 executable.
    More complicated application architectures can also be constructed. Most of
    the TPMs allow a server to become a client of another service, so you can
    involve additional servers.
    Could I use Oracle7's Multi Threaded Server as the SQL*Net connection in the
    previous picture?
    Yes, but that will not be needed in many cases. For example, both
    application server processes in the previous picture could talk to a
    single Oracle7 Server process through the Multi Threaded Server in the
    previous picture. However, since the TPM architecture typically reduces
    the number of server processes, the reduction in processes using Multi
    Threaded Server may be less significant than in an architecture without
    TPMs. If the application will use database links, however, then MTS will
    be required.
    How do I write an Oracle TP Monitor application?
    The actual API used to talk to the TPM varies between vendors, so you need
    to get the documentation from the vendor. However, all have a way to
    indicate where a transaction begins and ends and a way to send a request
    and receive a response from a client to a server. Some use an RPC model,
    some use a pseudo-RPC model, and some use a send/receive model. The TX API
    described earlier is a subset of the TPM API as defined by each of
    the TPM providers.
    The client program and server program might look something like the
    following examples. We h (such as Tuxedo's
    "tpacall
    Reference Ducumment
    ---------------------

    hello,
    the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
    regards,
    the oracle reports team

  • External Monitor no longer works after 10.5.8 Update

    I just downloaded 10.3.8 update and my Fujitsu external monitor no longer works with my Imac 24". The same thing has happened to a friend who has the same iMAC and similar external monitor. Is this Apples way to get us to use Apple products only or is this a big with the update? Any ideas? Thank you.

    Hello
    Try disconnecting all external peripherals, then shutdown your Mac, pull out all power cord, if it is a portable, take out the battery and leave it as it is for at least 5 minutes... 15 mins best.
    Then power back your mac and see if the FW ports are working
    Cheers

  • Bootcamp 2.0, Win XP 32bit and beamer / external monitor activation

    Hi,
    similar topics have been posted but I could not find any solution yet...
    My system: MacBook (NOT Pro, Core2Duo, with 10.5 Leopard and Bootcamp 2.0 with Win XP Pro 32bit SP2) and Mini-DVI to DVI adapter.
    Working on Leopard connecting my external monitor (Fujitsu-Siemens P19-2) is working perfectly. It is automatically detected and activated.
    When I connect the monitor on Win XP, the desktop and tasbar flicker/are reloaded, i.e. ANYTHING is detected. However, the monitor is black and says "No signal" and i cannot activate it. I considered/tried:
    - the Windows way: FN + F7 => did not work / is deactivated and tools like Input Remapper didnt work (written for Macbook Pro only afaik)
    - the 2nd Windows way: Display Properties, Settings => any changes without effect
    - via Bootcamp / GMA Driver Properties: no possibility to activate 2nd monitor: Note at "Display Devices"-menu: "Two displays must be connected to the computer before you can use this feature. Please connect another display."
    Therefore my questions:
    - any solution i did not consider?
    - is it a bootcamp / driver issue to be solved in bootcamp updates?
    - is there a keyboard tool similar to inputRemapper for Not-Pro-Macbooks? (To activate not only FN+F7 but also Del and PSC)
    Thanks in advance...
    Ben

    Thing is, I am trying this too. However, the only option I get is to clone the display. This is not what I want, I want to use the TV as the primary display. This way games will startup on the big TV and not on my Macbook Pro. Now I don't get the option to use that TV as a primary display.
    So leaves me with the option to clone the display and have same image rendered on both screens... This is NOT what i want. In Leopard everything works great... obviously...
    PLease let me know if you got any solutions for this

  • Connecting DVI Monitor to the ADC port

    I have a G5 with dual video ports. One is an ADC Port and the other is a DVI port. I want to get rid of my Apple display and connect two Dell monitors both of which have a DVI connectors. How do I connect a DVI connector to the ADC port? The DVI to ADC adapter is for connecting a ADC Apple display to a DVI port. Is there an adapter for doing the opposite--a DVI plug to a ADC port?
    Power Mac G5   Mac OS X (10.4.9)  

    The ADC to DVI adapter is for connecting a DVI LCD to the ADC port. It cannot be used with a DVI to VGA adapter to connect a VGA display to an ADC port. For that you need an ADC to VGA adapter, such as:
    <http://www.mac-pro.com/s.nl/it.A/id.230/.f?sc=2&category=128>
    These are becoming scarce as the ADC is no longer being manufactured.
    Your Sun monitor should work from the ADC port using the ADC to DVI adapter, and the Fujitsu from the DVI port using the DVI to VGA adapter.

  • External Monitor bug

    Hi,
    i am working on a Macbook Pro Retina and a Fujitsu Siemens external 21,5" Monitor,
    when i take a window from my Macbook Monitor to the external, it look like this:
    can somebody tell me how to fix this bug?
    its not appearing very often, but sometimes. Or is this an Osx Bug?
    My OS is Mountain Lion.

    I am running the latest up-to-date version of Photoshop.
    Curiously, for some windows it displays fine on the second screen, whereas on others it goes absolutely nuts like the OP's attached image!
    I'm also getting alot of persistent graphics that shouldn't be there (on my primary retina monitor), things like artifacts from the free-transform overlay and existing documents (when tabbing between open psds). I could go into more detail, but I'm starting to think it's a separate issue and warrants it's own post, which I'll try to do shortly.

  • T2000 onboard RAID monitoring in Solaris 10

    hey all,
    i have a new T2000 with the system disks mirrored via the hardware LSI raid controller.
    solaris 10 is installed.
    how do i get alerted as to when one of the 2 drives in the mirror taps out?
    i think ALOM will monitor the hard drives and generate alerts, but not sure if that will trigger if the mirror breaks or if there are problems on the raid controller itself?
    just want to make sure this system is covered.

    Ok, Two more drives in and the order seems a little strange. I suspect the tech who replace dthe MB flipped a pair of the SAS cables? Is this controller 2 channels?
    The 2 - 73GB disks are in the bottom (drive slots 0 and 1)
    The 2 - 146GB disks are in the top (drive slots 2 and 3)
    Here is what I am seeing in OBP
    {0} ok show-children
    MPT Version 1.05, Firmware Version 1.09.00.00
    Target 0
    Unit 0 Disk SEAGATE ST914602SSUN146G0400 286739329 Blocks, 146 GB
    SASAddress 5000c5000672aab1 PhyNum 0
    Target 1
    Unit 0 Disk FUJITSU MBB2073RCSUN72G 0505 143374738 Blocks, 73 GB
    SASAddress 500000e0186212b2 PhyNum 1
    Target 2
    Unit 0 Disk FUJITSU MBB2073RCSUN72G 0505 143374738 Blocks, 73 GB
    SASAddress 500000e017bd0402 PhyNum 2
    Target 3
    Unit 0 Disk SEAGATE ST914602SSUN146G0400 286739329 Blocks, 146 GB
    SASAddress 5000c5000679416d PhyNum 3

  • External monitor is not listed by xrandr

    Hi,
    I have an external monitor (VGA) connected to my laptop. All worked fine until the last nvidia-package update. X would no longer start up and therefore I decided to use the free nv driver instead (xf86-video-nv package). I updated my xorg.conf and everything was fine except that my external monitor isn't recognized.
    I own 2 external Monitors with VGA. When connected, both show the same picture as the internal monitor of my laptop but the picture is "shaking" the whole time. Doesn't look very healthy at all...
    (And I don't want a duplication but an extension of screen space)
    When I invoke xrandr it only lists my internal display. So I suppose the problem lies below all the Xorg.conf stuff. But I have no idea where to look for the cause of the problem.
    Is the kernel responsible of recognizing my monitors? Or is it a differenz component? How can I find out if the kernel(if responsible) has recognized my monitor?
    My system is up to date. No packages are held back. The relevant hardware is:
    Nvidia GeForce 7400
    Fujitsu Siemens (no model specification available)
    Samsung Syncmaster 2243 BW
    the following daemons are running:
    crond  dbus  hal  netfs  network  smartd  syslog-ng
    Last edited by essence-of-foo (2009-08-07 20:13:08)

    Thanks for your replies.
    djszapi wrote:1. You can create an xorg.conf with X -configure or with hwd, or try it without xorg.conf.
    Does that mean that xrandr looks into the xorg.conf to see if there are more monitors?
    I tried both methods.
    X -configure created an xorg.xonf with the instruction to use the nvdia driver. The result was (as expected) that the screen of my monitor stays black and only sysreq could help me to reboot. I edited the file to let the xserver use the nv driver but this changed almost nothing except that I still could use the ctrl+alt+F1... keys to get back to the virtual console (remember: X was all black. No windowmanager ect. )
    Using no xorg.conf has the same results as my current xorg.conf which I will paste later in this post. edit: The xorg.conf generated by X -configure has been attached too
    2. Which version of kernel/driver do you use ?
    As I wrote - everything is up to date.
    That means:
    Name                 : kernel26
    Version              : 2.6.30.4-1
    Name                 : nvidia
    Version              : 185.18.31-1
    Name                 : xf86-video-nv
    Version              : 2.1.14-1
    Name                 : xorg-server
    Version              : 1.6.3-2
    Name                 : hal
    Version              : 0.5.12git20090421.4fc367-2
    3. Is it a 32/64 bit system ?
    32 bits
    4. Maybe you can show some related log files, like xorg.log, error.log, syslog.
    Of couse:
    xorg.conf (written by me):
    Section "ServerLayout"
    Identifier "Builtin Default Layout"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection
    #--- first screen settings
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    Option "TwinView" "0"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nv"
    BoardName "GeForce Go 7400"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    ModelName "Nvidia Default Flat Panel"
    HorizSync 29.0 - 49.0
    VertRefresh 0.0 - 61.0
    EndSection
    #--- second screen settings
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    Option "TwinView" "0"
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nv"
    BoardName "GeForce Go 7400"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    ModelName "Samsung SyncMaster"
    #HorizSync 30.0 - 81.0
    #VertRefresh 56.0 - 75.0
    Option "RandRRotation" "yes"
    EndSection
    errors.log:
    Aug 6 19:09:34 Linuxbox kernel: NOHZ: local_softirq_pending 80
    syslog.log
    Aug 10 18:02:02 Linuxbox syslog-ng[3632]: syslog-ng starting up; version='3.0.3'
    hmm why dont u use the nvidia pakage ? Then you could use nvidia-utils for twinview
    I did. But since the last update I can't use the Xserver any more with the nvidia driver. And nvidia's tools only work when the driver is already working in the background.
    However I'm still wondering which component is responsible for recognizing the monitor. This will probalbly help me to investigate the problem.
    edit: xorg.conf generated by X -configure and edited by me:
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dri"
    Load "record"
    Load "extmod"
    Load "dbe"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nv"
    VendorName "nVidia Corporation"
    BoardName "G72M [GeForce Go 7400]"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    I changed the driver to "nv" and removed the glx module because the xserver was complaining. But this didn't change anything. The error messages are:
    X.Org X Server 1.6.3
    Release Date: 2009-7-31
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.30-ARCH i686
    Current Operating System: Linux Linuxbox 2.6.30-ARCH #1 SMP PREEMPT Fri Jul 31 18:10:38 UTC 2009 i686
    Build Date: 03 August 2009 08:45:00PM
    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: Mon Aug 10 21:03:11 2009
    (++) Using config file: "xorg.conf.new"
    (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    error setting MTRR (base = 0xb0000000, size = 0x04000000, type = 1) Invalid argument (22)
    Last edited by essence-of-foo (2009-08-10 19:10:58)

  • Macbook pro monitor flickers and audio interference

    Hi there,
    I've noticed some strange behavior with my macbook pro lately.  Occasionally the monitor will flicker just once really quickly. It will flicker between black and the regular screen.  Maybe it happens about twice a day.  When I'm surfing, I noticed some interference with the music that is playing in Itunes.  For example, if I click on a link in Google Chrome, the audio signal from whatever is playing in Itunes will get cut for a split second. It's almost like the processor is working too hard to manage both surfing in Chrome and the music playing in Itunes, which is ridiculous.  When I bought my computer (2008 or 2009 model), I upped the RAM to 4gb. My processor is 2.4 ghz.  I have no idea what's going on.  Is it a hard drive problem? Hope you can help.
    Thanks!

    Do you have access to an Apple Store? If so, it may be worth making an appointment at the genius bar and having them run the test for the NVIDIA problem. Since your replacement logic board still has the NVIDIA GeForce 8600 M GT video chip, it could be starting to happen to your replacement logic board.
    I also agree with all of CMCSK's suggestions. Freezing is often associated with hard drive problems. You might also want to run SMART Utility:
    http://www.apple.com/downloads/macosx/systemdiskutilities/smartutility.html
    You can download the demo and run it several times for free. It will give you a very comprehensive view of the physical health of your hard drive. If you still have the original one from 2007, it's getting pretty long in the tooth and may be approaching the end of its average useful life of 3-5 years. I just recently had to replace my original 2007 Fujitsu drive.
    If your drive is headed south, and is also too small, it may be time to upgrade to a larger and faster drive.
    The software update probably didn't cause the problems, but it may have exposed problems that were already in existence.
    Good luck!

Maybe you are looking for

  • Submitting a pdf form to a SharePoint 2010 library

    Hello, I have a pdf form that was created in Adobe LiveCycle. Right now the submit form button it configured to send the form to an email address. I need to be able to submit the form to a SharePoint 2010 document library but I can't get it to work.

  • Problem connecting two storage networks

    Hello, I connect two datacenters with 10GB modules. I'm using single mode fiber, it has 10Km between datacenters. Now I need connect the storage network in both datacenters using the same fiber. The storage networks use FCoE. What solution can I use

  • Can a Numbers worksheet link with iCal?

    I need a weekly update worksheet that has my iCal schedule linked to it. Does anyone know of a way to subscribe to it so that it will post onto a worksheet?

  • Changing the managed account to Admin

    while trying to set the parental controls on my iMac 2006 (OSX Lion), it has changed my current User (only Admin Account) to a managed. It did not ask me for creating a new user account. after restart I realized that my user account is under parental

  • Help about ipod touch plz reply me urgent

    I using ipod touch in us , but i also want to use in india , so can i use without problem or i want unlcok for sim card ?