[SOLVED] Samsung q1 ( egalax ) touchscreen not working with Xorg 1.6

I was using egalax touchscreen driver 2.06.2410 in my samsung Q1 :
http://home.eeti.com.tw/web20/eGalaxTou … Driver.htm
With the Xorg update to 1.6 version touchscreen stop working. If you want it back you can use this egalax_drv.so i got from eeti:
http://rapidshare.com/files/228797256/e … rv.so.html
Liquibyte and Kriblom kindly provided alternative (and probably better ) hosting:
http://www.liquibyte.com/driver/egalax_drv.so
http://dont-looze-touch.ovh.org/egalax_drv.so
It do worked for me using the 2.06.2410 driver and overwriting the old egalax_drv.so in /usr/lib/xorg/modules/input. I'm on 32 bit and i don't know if this do work in 64 bit too.
Last edited by ernia (2009-05-04 06:09:27)

Actually I've just gotten it.  I'll just post mine in case it's useful to someone else.
Section "ServerLayout"
InputDevice "EETI" "SendCoreEvents"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
Option "DontZap" "false"
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 "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x600"
EndSubSection
EndSection
### Touch Configuration Beginning ###
Section "InputDevice"
Identifier "EETI"
Driver "egalax"
Option "Device" "usbauto"
Option "Parameters" "/var/lib/eeti.param"
Option "ScreenNo" "0"
EndSection
### Touch Configuration End ###
Editing for brevity.
Last edited by liquibyte (2009-05-03 19:54:42)

Similar Messages

  • [semi-solved] dell xps 12 touchscreen not working (2013, 12-9Q33)

    does anyone know how to get the touch screen working the dell xps 12?
    ran windows on it for a few days and there did not appear to be any hardware issues with touchscreen (or anything else).
    deleted all windows partitions and installed arch + kde with no issues, boots and runs great. but no response from the touch screen.
    have tried to cat every /dev/input/event* but get nothing when tapping touch screen.
    beleve it uses an atmel maxtouch digitizer... which i think should be picked up by udev... but dont think udev even sees the device, it just detetcs boring old mouse.
    this looks like a simmilar issue with ubuntu https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 but on my system there is no indication that it is an i2c device.
    tried atmel kernel but still no action https://git.kernel.org/cgit/linux/kerne … mel-mxt-ts
    lsusb
    Bus 003 Device 002: ID 8087:8000 Intel Corp.
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 8087:09fa Intel Corp.
    Bus 001 Device 003: ID 0bda:5716 Realtek Semiconductor Corp.
    Bus 001 Device 002: ID 8087:07dc Intel Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    input
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [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)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Integrated Webcam id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=12 [slave keyboard (3)]
    sudo cat /proc/bus/input/devices
    I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
    N: Name="AT Translated Set 2 keyboard"
    P: Phys=isa0060/serio0/input0
    S: Sysfs=/devices/platform/i8042/serio0/input/input0
    U: Uniq=
    H: Handlers=sysrq kbd event0
    B: PROP=0
    B: EV=120013
    B: KEY=1100f02902000 8380307cf910f001 feffffdfffefffff fffffffffffffffe
    B: MSC=10
    B: LED=7
    I: Bus=0019 Vendor=0000 Product=0001 Version=0000
    N: Name="Power Button"
    P: Phys=PNP0C0C/button/input0
    S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
    U: Uniq=
    H: Handlers=kbd event1
    B: PROP=0
    B: EV=3
    B: KEY=10000000000000 0
    I: Bus=0019 Vendor=0000 Product=0005 Version=0000
    N: Name="Lid Switch"
    P: Phys=PNP0C0D/button/input0
    S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
    U: Uniq=
    H: Handlers=event2
    B: PROP=0
    B: EV=21
    B: SW=1
    I: Bus=0019 Vendor=0000 Product=0001 Version=0000
    N: Name="Power Button"
    P: Phys=LNXPWRBN/button/input0
    S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    U: Uniq=
    H: Handlers=kbd event3
    B: PROP=0
    B: EV=3
    B: KEY=10000000000000 0
    I: Bus=0001 Vendor=10ec Product=0668 Version=0001
    N: Name="HDA Digital PCBeep"
    P: Phys=card1/codec#0/beep0
    S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input4
    U: Uniq=
    H: Handlers=kbd event4
    B: PROP=0
    B: EV=40001
    B: SND=6
    I: Bus=0000 Vendor=0000 Product=0000 Version=0000
    N: Name="HDA Intel PCH Headphone"
    P: Phys=ALSA
    S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input5
    U: Uniq=
    H: Handlers=event5
    B: PROP=0
    B: EV=21
    B: SW=4
    I: Bus=0010 Vendor=001f Product=0001 Version=0100
    N: Name="PC Speaker"
    P: Phys=isa0061/input0
    S: Sysfs=/devices/platform/pcspkr/input/input6
    U: Uniq=
    H: Handlers=kbd event6
    B: PROP=0
    B: EV=40001
    B: SND=6
    I: Bus=0019 Vendor=0000 Product=0000 Version=0000
    N: Name="Dell WMI hotkeys"
    P: Phys=wmi/input0
    S: Sysfs=/devices/virtual/input/input7
    U: Uniq=
    H: Handlers=kbd rfkill event7
    B: PROP=0
    B: EV=13
    B: KEY=1500b00000000 200300000 0 0
    B: MSC=10
    I: Bus=0003 Vendor=0bda Product=5716 Version=3204
    N: Name="Integrated Webcam"
    P: Phys=usb-0000:00:14.0-5/button
    S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8
    U: Uniq=
    H: Handlers=kbd event8
    B: PROP=0
    B: EV=3
    B: KEY=100000 0 0 0
    I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
    N: Name="SynPS/2 Synaptics TouchPad"
    P: Phys=isa0060/serio1/input0
    S: Sysfs=/devices/platform/i8042/serio1/input/input9
    U: Uniq=
    H: Handlers=mouse0 event9
    B: PROP=5
    B: EV=b
    B: KEY=e520 610000 0 0 0 0
    B: ABS=660800011000003
    I: Bus=0019 Vendor=0000 Product=0006 Version=0000
    N: Name="Video Bus"
    P: Phys=LNXVIDEO/video/input0
    S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
    U: Uniq=
    H: Handlers=kbd event10
    B: PROP=0
    B: EV=3
    B: KEY=3e000b00000000 0 0 0
    I: Bus=0000 Vendor=0000 Product=0000 Version=0000
    N: Name="HDA Intel MID HDMI/DP,pcm=8"
    P: Phys=ALSA
    S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input11
    U: Uniq=
    H: Handlers=event11
    B: PROP=0
    B: EV=21
    B: SW=140
    I: Bus=0000 Vendor=0000 Product=0000 Version=0000
    N: Name="HDA Intel MID HDMI/DP,pcm=7"
    P: Phys=ALSA
    S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input12
    U: Uniq=
    H: Handlers=event12
    B: PROP=0
    B: EV=21
    B: SW=140
    I: Bus=0000 Vendor=0000 Product=0000 Version=0000
    N: Name="HDA Intel MID HDMI/DP,pcm=3"
    P: Phys=ALSA
    S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input13
    U: Uniq=
    H: Handlers=event13
    B: PROP=0
    B: EV=21
    B: SW=140
    sudo dmidecode
    [sudo] password for gamera:
    # dmidecode 2.12
    # SMBIOS entry point at 0x000f04c0
    SMBIOS 2.7 present.
    56 structures occupying 2720 bytes.
    Table at 0x000EBA70.
    Handle 0xDA00, DMI type 218, 251 bytes
    OEM-specific Type
    Header and Data:
    DA FB 00 DA B2 00 0D 5F 0F 37 40 7D 00 00 00 00
    00 7E 00 01 00 00 00 75 01 01 80 01 00 76 01 02
    80 01 00 4F 02 05 80 01 00 50 02 06 80 00 00 A5
    02 02 00 00 00 A6 02 02 00 01 00 9C 00 03 00 01
    00 9B 00 03 00 00 00 8A 01 04 00 01 00 89 01 04
    00 00 00 7F 01 05 00 00 00 80 01 05 00 01 00 53
    01 06 00 00 00 52 01 06 00 01 00 7B 01 07 00 00
    00 7C 01 07 00 01 00 94 01 08 00 00 00 93 01 08
    00 01 00 7D 00 09 00 00 00 2D 00 0A 00 01 00 2E
    00 0A 00 00 00 6E 00 0B 00 00 00 95 00 0C 00 01
    00 96 00 0C 00 00 00 2F 02 0D 00 01 00 30 02 0D
    00 00 00 50 02 0E 00 00 00 51 02 0E 00 01 00 52
    02 0E 00 02 00 53 02 0E 00 03 00 54 02 0E 00 04
    00 56 02 0E 00 05 00 F0 00 5D 80 01 00 ED 00 5E
    80 01 00 4B 01 5F 80 01 00 4A 01 60 80 01 00 EA
    00 0F 00 01 00 FF FF 00 00 00 00
    Handle 0xDA01, DMI type 218, 251 bytes
    OEM-specific Type
    Header and Data:
    DA FB 01 DA B2 00 0D 5F 0F 37 40 EB 00 0F 00 00
    00 37 01 61 80 01 00 38 01 62 80 01 00 39 01 63
    80 01 00 3D 03 66 80 01 00 3E 03 67 80 01 00 2E
    02 07 80 01 00 2D 02 08 80 01 00 4F 03 09 80 01
    00 50 03 0A 80 01 00 0E 01 64 80 01 00 0F 01 65
    80 01 00 47 01 68 80 01 00 46 01 69 80 01 00 36
    02 17 80 01 00 35 02 18 80 01 00 36 03 19 80 01
    00 37 03 1A 80 01 00 3A 03 1B 80 01 00 3B 03 1C
    80 01 00 41 03 1D 80 01 00 42 03 1E 80 01 00 43
    03 1F 80 01 00 44 03 20 80 01 00 45 03 21 80 01
    00 46 03 22 80 01 00 47 03 23 80 01 00 4B 03 24
    80 01 00 4C 03 25 80 01 00 4A 02 0B 80 01 00 26
    03 0C 80 01 00 5B 03 0D 80 01 00 5C 03 0E 80 01
    00 5D 03 0F 80 01 00 5E 03 10 80 01 00 5F 03 11
    80 01 00 60 03 12 80 01 00 0C 80 13 80 01 00 04
    A0 14 80 01 00 FF FF 00 00 00 00
    Handle 0xDA02, DMI type 218, 29 bytes
    OEM-specific Type
    Header and Data:
    DA 1D 02 DA B2 00 0D 5F 0F 37 40 44 01 15 80 01
    00 45 01 16 80 01 00 FF FF 00 00 00 00
    Handle 0x0000, DMI type 0, 24 bytes
    BIOS Information
    Vendor: Dell Inc.
    Version: A02
    Release Date: 07/26/2013
    Address: 0xF0000
    Runtime Size: 64 kB
    ROM Size: 2048 kB
    Characteristics:
    MCA is supported
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    ESCD support is available
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    CGA/mono video services are supported (int 10h)
    ACPI is supported
    USB legacy is supported
    ATAPI Zip drive boot is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
    BIOS Revision: 0.2
    Firmware Revision: 0.2
    Handle 0x0001, DMI type 1, 27 bytes
    System Information
    Manufacturer: Dell Inc.
    Product Name: XPS 12-9Q33
    Version: A02
    Serial Number: FZS4SY1
    UUID: 4C4C4544-005A-5310-8034-C6C04F535931
    Wake-up Type: Power Switch
    SKU Number: XPS 12-9Q33
    Family:
    Handle 0x0002, DMI type 2, 15 bytes
    Base Board Information
    Manufacturer: Dell Inc.
    Product Name: XPS 12-9Q33
    Version: A02
    Serial Number: .FZS4SY1.CN1296139P0049.
    Asset Tag: Not Specified
    Features:
    Board is a hosting board
    Board is replaceable
    Location In Chassis: To Be Filled By O.E.M.
    Chassis Handle: 0x0003
    Type: Motherboard
    Contained Object Handles: 0
    Handle 0x0003, DMI type 3, 22 bytes
    Chassis Information
    Manufacturer: Dell Inc.
    Type: Portable
    Lock: Not Present
    Version: Not Specified
    Serial Number: FZS4SY1
    Asset Tag: Not Specified
    Boot-up State: Safe
    Power Supply State: Safe
    Thermal State: Safe
    Security Status: None
    OEM Information: 0x00000000
    Height: Unspecified
    Number Of Power Cords: 1
    Contained Elements: 0
    SKU Number: To be filled by O.E.M.
    Handle 0x0008, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J1A1
    Internal Connector Type: None
    External Reference Designator: PS2Mouse
    External Connector Type: PS/2
    Port Type: Mouse Port
    Handle 0x0009, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J1A1
    Internal Connector Type: None
    External Reference Designator: Keyboard
    External Connector Type: PS/2
    Port Type: Keyboard Port
    Handle 0x000A, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J2A1
    Internal Connector Type: None
    External Reference Designator: TV Out
    External Connector Type: Mini Centronics Type-14
    Port Type: Other
    Handle 0x000B, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J2A2A
    Internal Connector Type: None
    External Reference Designator: COM A
    External Connector Type: DB-9 male
    Port Type: Serial Port 16550A Compatible
    Handle 0x000C, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J2A2B
    Internal Connector Type: None
    External Reference Designator: Video
    External Connector Type: DB-15 female
    Port Type: Video Port
    Handle 0x000D, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J3A1
    Internal Connector Type: None
    External Reference Designator: USB1
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x000E, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J3A1
    Internal Connector Type: None
    External Reference Designator: USB2
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x000F, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J3A1
    Internal Connector Type: None
    External Reference Designator: USB3
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x0010, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J9A1 - TPM HDR
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0011, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J9C1 - PCIE DOCKING CONN
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0012, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J2B3 - CPU FAN
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0013, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J6C2 - EXT HDMI
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0014, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J3C1 - GMCH FAN
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0015, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J1D1 - ITP
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0016, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J9E2 - MDC INTPSR
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0017, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: J9E4 - MDC INTPSR
    Internal Connector Type: Other
    External Reference Designator: Not Specified
    External Connector Type: None
    Port Type: Other
    Handle 0x0018, DMI type 9, 17 bytes
    System Slot Information
    Designation: J6B2
    Type: x16 PCI Express
    Current Usage: In Use
    Length: Long
    ID: 0
    Characteristics:
    3.3 V is provided
    Opening is shared
    PME signal is supported
    Bus Address: 0000:00:01.0
    Handle 0x0019, DMI type 9, 17 bytes
    System Slot Information
    Designation: J6B1
    Type: x1 PCI Express
    Current Usage: In Use
    Length: Short
    ID: 1
    Characteristics:
    3.3 V is provided
    Opening is shared
    PME signal is supported
    Bus Address: 0000:00:1c.3
    Handle 0x001A, DMI type 10, 6 bytes
    On Board Device Information
    Type: Video
    Status: Enabled
    Description: Mobile Intel HD Graphics
    Handle 0x001B, DMI type 11, 5 bytes
    OEM Strings
    String 1: Dell System
    String 2: 1[05E3h]
    String 3: 3[1.0]
    String 4: 4[0001]
    String 5: 5[0000]
    String 6: 6[D0, D4, D8, DA, DE]
    String 7: 7[]
    String 8: 8[]
    String 9: 9[]
    String 10: 10[A02]
    String 11: 11[]
    String 12: 12[]
    String 13: 13[P20S]
    String 14: 14[0]
    String 15: 15[0]
    Handle 0x001C, DMI type 12, 5 bytes
    System Configuration Options
    Option 1: To Be Filled By O.E.M.
    Handle 0x001D, DMI type 21, 7 bytes
    Built-in Pointing Device
    Type: Touch Pad
    Interface: Bus Mouse
    Buttons: 2
    Handle 0x001E, DMI type 22, 26 bytes
    Portable Battery
    Location: System Battery
    Manufacturer: SDI
    Manufacture Date: Not Specified
    Serial Number: Not Specified
    Name: DELL 7YM0739
    Chemistry: Lithium Ion
    Design Capacity: 51060 mWh
    Design Voltage: 7400 mV
    SBDS Version: 1.0
    Maximum Error: 100%
    OEM-specific Information: 0x00000001
    Handle 0x001F, DMI type 32, 20 bytes
    System Boot Information
    Status: No errors detected
    Handle 0x0021, DMI type 27, 12 bytes
    Cooling Device
    Type: Fan
    Status: OK
    OEM-specific Information: 0x00000000
    Handle 0x0022, DMI type 28, 20 bytes
    Temperature Probe
    Description: CPU Internal Temperature
    Location: Processor
    Status: OK
    Maximum Value: 127.0 deg C
    Minimum Value: 0.0 deg C
    Resolution: 1.000 deg C
    Tolerance: 0.5 deg C
    Accuracy: Unknown
    OEM-specific Information: 0x00000000
    Handle 0xB000, DMI type 176, 10 bytes
    OEM-specific Type
    Header and Data:
    B0 0A 00 B0 00 00 00 00 E3 05
    Handle 0xB100, DMI type 177, 12 bytes
    OEM-specific Type
    Header and Data:
    B1 0C 00 B1 1A 06 00 00 00 00 00 00
    Handle 0x0025, DMI type 208, 12 bytes
    OEM-specific Type
    Header and Data:
    D0 0C 25 00 02 05 FE 00 E3 05 01 02
    Strings:
    20130614
    20130924
    Handle 0x0026, DMI type 212, 57 bytes
    OEM-specific Type
    Header and Data:
    D4 39 26 00 70 00 71 00 01 49 50 48 9C 00 49 FC
    01 9B 00 49 FC 00 7F 01 4A FB 04 80 01 4A FB 00
    53 01 4A F7 08 52 01 4A F7 08 7B 01 4A EF 10 7C
    01 4A EF 10 FF FF 00 00 00
    Handle 0x0027, DMI type 216, 9 bytes
    OEM-specific Type
    Header and Data:
    D8 09 27 00 01 02 01 00 00
    Strings:
    INTEL
    0000
    Handle 0x0028, DMI type 217, 8 bytes
    OEM-specific Type
    Header and Data:
    D9 08 28 00 01 02 00 00
    Strings:
    Handle 0x0029, DMI type 219, 11 bytes
    OEM-specific Type
    Header and Data:
    DB 0B 29 00 00 01 02 03 00 04 05
    Strings:
    Handle 0x002A, DMI type 220, 22 bytes
    OEM-specific Type
    Header and Data:
    DC 16 2A 00 01 F0 00 00 02 F0 00 00 00 00 03 F0
    04 F0 00 00 00 00
    Handle 0x002B, DMI type 221, 19 bytes
    OEM-specific Type
    Header and Data:
    DD 13 2B 00 00 00 00 00 00 03 00 00 00 00 00 00
    00 00 00
    Handle 0x002C, DMI type 222, 16 bytes
    OEM-specific Type
    Header and Data:
    DE 10 2C 00 01 08 FF FF 00 00 00 00 00 00 00 00
    Handle 0x002D, DMI type 4, 42 bytes
    Processor Information
    Socket Designation: SOCKET 0
    Type: Central Processor
    Family: Core i5
    Manufacturer: Intel
    ID: 51 06 04 00 FF FB EB BF
    Signature: Type 0, Family 6, Model 69, Stepping 1
    Flags:
    FPU (Floating-point unit on-chip)
    VME (Virtual mode extension)
    DE (Debugging extension)
    PSE (Page size extension)
    TSC (Time stamp counter)
    MSR (Model specific registers)
    PAE (Physical address extension)
    MCE (Machine check exception)
    CX8 (CMPXCHG8 instruction supported)
    APIC (On-chip APIC hardware supported)
    SEP (Fast system call)
    MTRR (Memory type range registers)
    PGE (Page global enable)
    MCA (Machine check architecture)
    CMOV (Conditional move instruction supported)
    PAT (Page attribute table)
    PSE-36 (36-bit page size extension)
    CLFSH (CLFLUSH instruction supported)
    DS (Debug store)
    ACPI (ACPI supported)
    MMX (MMX technology supported)
    FXSR (FXSAVE and FXSTOR instructions supported)
    SSE (Streaming SIMD extensions)
    SSE2 (Streaming SIMD extensions 2)
    SS (Self-snoop)
    HTT (Multi-threading)
    TM (Thermal monitor supported)
    PBE (Pending break enabled)
    Version: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
    Voltage: 1.2 V
    External Clock: 100 MHz
    Max Speed: 3800 MHz
    Current Speed: 1600 MHz
    Status: Populated, Enabled
    Upgrade: Socket rPGA988B
    L1 Cache Handle: 0x0004
    L2 Cache Handle: 0x0005
    L3 Cache Handle: 0x0006
    Serial Number: Not Specified
    Asset Tag: Fill By OEM
    Part Number: Fill By OEM
    Core Count: 2
    Core Enabled: 2
    Thread Count: 4
    Characteristics:
    64-bit capable
    Handle 0x0004, DMI type 7, 19 bytes
    Cache Information
    Socket Designation: CPU Internal L1
    Configuration: Enabled, Not Socketed, Level 1
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 128 kB
    Maximum Size: 128 kB
    Supported SRAM Types:
    Unknown
    Installed SRAM Type: Unknown
    Speed: Unknown
    Error Correction Type: Single-bit ECC
    System Type: Other
    Associativity: 8-way Set-associative
    Handle 0x0005, DMI type 7, 19 bytes
    Cache Information
    Socket Designation: CPU Internal L2
    Configuration: Enabled, Not Socketed, Level 2
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 512 kB
    Maximum Size: 512 kB
    Supported SRAM Types:
    Unknown
    Installed SRAM Type: Unknown
    Speed: Unknown
    Error Correction Type: Single-bit ECC
    System Type: Unified
    Associativity: 8-way Set-associative
    Handle 0x0006, DMI type 7, 19 bytes
    Cache Information
    Socket Designation: CPU Internal L3
    Configuration: Enabled, Not Socketed, Level 3
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 3072 kB
    Maximum Size: 3072 kB
    Supported SRAM Types:
    Unknown
    Installed SRAM Type: Unknown
    Speed: Unknown
    Error Correction Type: Single-bit ECC
    System Type: Unified
    Associativity: 12-way Set-associative
    Handle 0x0007, DMI type 16, 23 bytes
    Physical Memory Array
    Location: System Board Or Motherboard
    Use: System Memory
    Error Correction Type: None
    Maximum Capacity: 16 GB
    Error Information Handle: Not Provided
    Number Of Devices: 2
    Handle 0x0020, DMI type 17, 34 bytes
    Memory Device
    Array Handle: 0x0007
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 2048 MB
    Form Factor: SODIMM
    Set: None
    Locator: ChannelA-DIMM0
    Bank Locator: BANK 0
    Type: DDR3
    Type Detail: Synchronous
    Speed: 1600 MHz
    Manufacturer: Hynix/Hyundai
    Serial Number: 00000001
    Asset Tag: 0987654321
    Part Number:
    Rank: 1
    Configured Clock Speed: 1600 MHz
    Handle 0x0023, DMI type 20, 35 bytes
    Memory Device Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x0007FFFFFFF
    Range Size: 2 GB
    Physical Device Handle: 0x0020
    Memory Array Mapped Address Handle: 0x002F
    Partition Row Position: 2
    Interleave Position: 1
    Interleaved Data Depth: 1
    Handle 0x0024, DMI type 17, 34 bytes
    Memory Device
    Array Handle: 0x0007
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 2048 MB
    Form Factor: SODIMM
    Set: None
    Locator: ChannelB-DIMM0
    Bank Locator: BANK 2
    Type: DDR3
    Type Detail: Synchronous
    Speed: 1600 MHz
    Manufacturer: Hynix/Hyundai
    Serial Number: 00000002
    Asset Tag: 0987654321
    Part Number:
    Rank: 1
    Configured Clock Speed: 1600 MHz
    Handle 0x002E, DMI type 20, 35 bytes
    Memory Device Mapped Address
    Starting Address: 0x00080000000
    Ending Address: 0x000FFFFFFFF
    Range Size: 2 GB
    Physical Device Handle: 0x0024
    Memory Array Mapped Address Handle: 0x002F
    Partition Row Position: 2
    Interleave Position: 1
    Interleaved Data Depth: 1
    Handle 0x002F, DMI type 19, 31 bytes
    Memory Array Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x000FFFFFFFF
    Range Size: 4 GB
    Physical Array Handle: 0x0007
    Partition Width: 2
    Handle 0x0037, DMI type 131, 64 bytes
    OEM-specific Type
    Header and Data:
    83 40 37 00 31 00 00 00 00 00 00 00 00 00 00 00
    F8 00 43 9C 00 00 00 00 01 20 00 00 05 00 09 00
    D1 05 02 00 00 00 00 00 C8 00 FF FF 00 00 00 00
    00 00 00 00 26 00 00 00 76 50 72 6F 00 00 00 00
    Handle 0x0038, DMI type 13, 22 bytes
    BIOS Language Information
    Language Description Format: Long
    Installable Languages: 1
    en|US|iso8859-1
    Currently Installed Language: en|US|iso8859-1
    Handle 0x0039, DMI type 127, 4 bytes
    End Of Table
    Last edited by fungi (2013-10-13 10:31:45)

    Semi solved the problem by building a kernel with an ubuntu .config from http://kernel.ubuntu.com/~kernel-ppa/ma … y/current/
    I think i have multi touch working on the touchscreen, but this has resulted in breakage of the synapic touchpad which is now operating in a very simple mode (no scrolling or multitouch).
    Probably best to follow https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 and http://thread.gmane.org/gmane.linux.kernel.input/32207 for a real solution

  • [SOLVED] DPMS screen off not working with xorg 1.16.0, gnome 3

    After the update of xorg into 1.16.0-2, screen is not turned off by DPMS in GNOME.
    I also tried an manual command:
    $ xset dpms force off
    but it's not working.
    In other WM, this command is working.
    With xorg 1.15.2 and gnome 3, there is not this problem.
    When I entered the command, the screen turned off for a couple of seconds and turned back on.
    Last edited by esrevinu (2014-07-22 23:35:07)

    Updating xf86-video-intel to 2.99.912-4 solved the problem.
    Thanks.

  • [SOLVED} Suspend to ram does not work (with sleep, s2ram, pm-utils)

    Hi.
    I would like to ask for one thing: i can't suspend to ram or resume from suspend to ram.
    I treid to check over www in order to find some help, some solutions, and how to fix that. Unfortunately, i found these:
    https://forums.opensuse.org/showthread. … 13-2/page2
    https://bugzilla.opensuse.org/show_bug.cgi?id=913105
    https://forums.opensuse.org/showthread. … S-13-1-x64
    Bug 91921 - WD 2TB Caviar black causes hard lock on resume S2RAM
    https://bugzilla.kernel.org/show_bug.cgi?id=91921
    In fact, when i was researching of this problem i wanted to check if my graphic card and memory are failing so a did few changes (removed memory stick and so one) but in doing this i removed almost all of my hard disk drives because i didn't want to hurt them with many reboots or resets.
    What did i find? It is strange, kernel version is not important because i checked most of them.
    I removed 2x2TB Seagate F14 series along with 4x3TB WD Green. Then i checked s2ram, it went to suspend, and resumes correctly. Everything works. I put it to sleep with s2ram -f -a 1. Works
    I attached my 4x3TB WD Green drives. I put computer to sleep with s2ram...it causes hard lock, black screen, i could do only poweroff by powerbutton. s2ram -f -a 1 causes freez. Sometimes, but not constantly, s2ram -f -a 3 -p is being able to suspend...(mostly it does a freez, hard lock computer) but sometimes it is able to put it to a sleep, but resume just freezes everyting - no blinking cursor, no blinking num lock led and so on.
    I know that you would suggest me to check logs - this is the main problem. Logs for pm-suspend works when i suspend or resume without WD drives attached. When i have them connected, i'm not able to check pm-logs because computer hangs, freezes and logs are not being stored/writed to pm-suspend.log and pm-powersave.log.
    Could somebody help? Point me to a solution? I can't check logs because there are not any when freezing occurs. I checked openSuse thread and many others and for other systems there were some kernel fixex, patches.
    They wrote that WD blacks are at fault because they don't have APM. Well, in fact my WD Green have APM with very aggresive factory settings: they park heads over 8 seconds not being used. I disabled it in firmware but disabling it is not the point and not the problem. People have the same problem even with APM and parking heads on other WD drives, i found it that some have it with WD Red's drives and even with very old 320GB WD Blue series - what is more funny, i have 640GB AAKS blue from WD and with this drive i can suspend or resume - APM on this drive is also unavilable, like in Green series because i changed it with wdidle with prebootable cd. I can't  supend or resume with 3TB WD Greens.
    BTW - suspend to disk, with pm-utils and uswsusp works ok, in 100% every time. (i had to add "shutdown method = shutdown" to /etc/suspend.conf from uswsusp package).
    On Windows machine it works. Can suspend, can resume, can hibernate.
    Last edited by firekage (2015-03-07 03:27:28)

    Hm, sometimes i found myself astonished because some things just does not work at all on one machine, while the other one has no problem at all. I was trying to find why suspend to ram won't work at all...and while i was searching i found one topic that was leading to upower dbus. Similar problem with upower i found, by coincidence, on Manjaro forum.
    dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
    this command above returns all the time:
    Error org.freedesktop.DBus.Error.UnknownMethod: Method "Suspend" with signature "" on interface "org.freedesktop.UPower" doesn't exist
    I tried this:
    sudo systemctl enable acpid.service
    sudo systemctl --system daemon-reload
    sudo systemctl restart systemd-logind
    As soon as i enabled and started acpid.service...my supend to ram, from kde, works like a charm, without graphic problem, or freezing.
    There is few question: why on my desktop suspend doesen't work out of the box, when even archwiki says it should? Why on my netbook machine (Acer AOD270) that has the same package installed it works out of the box? Why on my desktop machine acpid.service was not enabled, was not started and was not running while on the notebook it does?
    Anyway...i fixed it by a big coincidence because on Fedora forum somebody has problem with suspend to ram with nvidia GTX750 and this card was new like my card (GTX660). He posted the same problem with upower that i posted in quotes and because of this i found another thing on Manjaro forum and that was it!
    BTW - this problem, i now think, is not related to my WD drives because it works with them. I think that there was another one ugly thing that broke my suspend to ram ability - bios of my motherboard (so called uefi bios with support for old one) has no option for S1-S5 stated (like the previous motherboards had) and only have ASPM...and ASPM is in my opinion broken but i will try to veryfi it one again later.
    Last edited by firekage (2015-03-07 03:29:20)

  • Edit: Touchscreen not working with photoshop cs5

    When using photoshop cs5, I am unable to use any tool properly when using the touch screen.
    Using the touchscreen, I am able to select the tool and other buttons, but when i attempt to draw with the brush tool, dragging a stylus across the screen does not create a line, and only visual feedback is seen. Dots can be drawn, ad the only way a line can be created is to double-click and drag which does not always work and is irritating to use.
    Please help, I have tried searching for a long while and even contacted computer support but they directed me here. I am unable to find a suitable driver, as suggested on the troubleshooting page or any other solution. Any advice is greatly appreciated, thanks.
    Computer: Asus Vivobook S550CM
    System: Windows 8

    This have been touch on many times here.  There are two api use to support touch type devices like tablets and touch screens. The API that many touch screen tablet and computers use lack features Adobe Pen support uses example the API does not support things like pen tilt. Therefore Adobe does not support this API.  You need a device driver for you touch screen that user the API Adobe uses for tablet support.

  • Samsung LED Monitor TA950 not working with Macbook pro

    I bought a Samsung TA950 Full HD LED 3D 27 inch monitor and trying to connect my MBP (early-mid 2009, does not support, MiniPort Audio). Connecting using MDP-DVI to HDMI to connect and MBP detects the monitor, I can see and change Display preferences. The monitor only flashes "no signal" when I disconnect the cables so something is happening...every so often my macbook pro display "flashes" momentarily as if it is recognizing a connection but a)nothing shows up in the display prefs after clicking "detect display" and b) nothing shows up on the external monitor. The monitor did worked and showed the MBP screen when I disconnect the cable, set the MBP display resolution to 1152 by 720, than connect the Miniport cable, the monitors flickers and shows the screen, and after a minute or 2, it goes black and goes in the loop of flickering and trying to detect the monitor

    Hi, I got the same monitor the other day and there should be no problem getting it to work.
    Use the DP to mini-DP cable supplied with the monitor.
    Make sure this cable is plugged into the correct input DP port in the back of the monitor (not the DP port for daisychaining).
    Make sure the DP input is selected in the inputs menu on screen.
    Plug mini-DP end of the cable into Mac
    Should work ...

  • Touchscreen not working with windows 8

    I just upgraded my touchsmart laptop to windows 8 and now the touchscreen doesn't work. Any suggestions?

    When requesting assistance, please provide the full HP model name and/or product number of the computer in question.
    Is the "TouchScreen" listed as known device in the Windows device manager??? Or is there an unknown input device listed??? You may wish to try this NextWindow Windows 8 Driver and see if that helps. Another thing that may work, is to set Windows update to look for optional udpates.
    Please send KUDOs
    Frank
    {------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
    Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
    This is a user supported forum. I am a volunteer and I don't work for HP.
    HP 15t-j100 (on loan from HP)
    HP 13 Split x2 (on loan from HP)
    HP Slate8 Pro (on loan from HP)
    HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
    HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
    HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
    HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
    HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

  • Toshiba Touchscreen Not Working with Echo Sign

    I bought a brand new Toshiba Satellite Radius 2 in 1 and the touch screen won't register to sign via "draw my signature" feature with EchoSign/Adobe Reader.  I have Reader XI installed.  Is that a known issue?  How do I fix this?  This is the whole reason why I bought the touch screen in the first place to sign Adobe Documents with EchoSign.

    Hello DarrenLindquist,
    How exactly are you trying to sign the document? Did you receive an EchoSign email to open the document link to esign or are you trying to open the PDF in Adobe Reader and then placing signature in it? Also, if you can let us know if there is any error encountered or what exactly happens when you try to place signature?
    Regards,
    -Rijul

  • Keyboard not working with xorg-server 1.6.1-1 or xkeyboard 1.5-1

    Hello!
    I have a problem with a no working keyboard. It seems like this is a problem related to some of the latest xkeyboard-config or xorg-server versions. This have been a problem some time, but it have been solved by downgrading xkeyboard-config to v1.5-1 and xorg-server to v1.6.1-1.
    I'm booting into runlevel 3. Keyboard is working in the terminal, but when I run startx, the keyboard stops working. The mouse works fine.
    Have tested with an empty xorg.conf file. Then I get a 'no screen found' error. And I have tryed to enable the keyboard entry in xorg.conf. X starts, but no keyboard. Hal is running.
    Any ideas?
    The xorg.conf and rc.conf
    # Copyright 2004 The X.Org Foundation
    Section "ServerLayout"
    Identifier "Laptop"
    Screen 0 "Default" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    # InputDevice "EvdevMouse" "CorePointer"
    # Inputdevice "Trackpoint" "SendCoreEvents"
    EndSection
    Section "ServerFlags"
    Option "AutoAddDevices" "True"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    EndSection
    Section "Monitor"
    Identifier "LCD"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "radeon_hd"
    Driver "fglrx"
    EndSection
    Section "Screen"
    Identifier "Default"
    Device "radeon_hd"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1440x900" "1024x768"
    Virtual 2720 1024
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    # /etc/rc.conf - Main Configuration for Arch Linux
    LOCALE="en_US.utf8"
    HARDWARECLOCK="UTC"
    USEDIRECTISA="no"
    TIMEZONE="Europe/Oslo"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    MOD_AUTOLOAD="yes"
    MODULES=(fglrx vboxdrv vboxnetadp acpi_cpufreq cpufreq_ondemand !pcspkr)
    USELVM="no"
    HOSTNAME="ArchT400"
    eth0="dhcp"
    INTERFACES=(!eth0)
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    DAEMONS=(syslog-ng network netfs hal laptop-mode cpufreq crond oss @autowifi @cups @openntpd @hddtemp)
    Last edited by orjanp (2009-08-11 13:07:41)

    Her er Xorg.0.log
    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 x86_64
    Current Operating System: Linux ArchT400 2.6.30-ARCH #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009 x86_64
    Build Date: 03 August 2009 08:17:16PM
    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: Wed Aug 12 10:39:18 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Laptop"
    (**) |-->Screen "Default" (0)
    (**) | |-->Monitor "<default monitor>"
    (**) | |-->Device "radeon_hd"
    (==) No monitor specified for screen "Default".
    Using a default monitor configuration.
    (**) Option "AutoAddDevices" "True"
    (**) Automatically adding devices
    (==) Automatically enabling devices
    (==) 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,
    built-ins
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) Cannot locate a core pointer device.
    (II) Cannot locate a core keyboard device.
    (II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AllowEmptyInput.
    (II) Loader magic: 0x7540
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 5.0
    X.Org XInput driver : 4.0
    X.Org Server Extension : 2.0
    (II) Loader running on linux
    (--) using VT number 7
    (--) PCI:*(0:1:0:0) 1002:95c4:17aa:210e ATI Technologies Inc Mobility Radeon HD 3400 Series rev 0, Mem @ 0xd0000000/268435456, 0xcfff0000/65536, I/O @ 0x00002000/256, BIOS @ 0x????????/131072
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (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 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="FireGL - ATI Technologies Inc."
    compiled for 7.4.0, module version = 1.0.0
    (II) Loading extension GLX
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension RECORD
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 7.4.0, module version = 1.0.0
    (II) Loading extension XFree86-DRI
    (II) Loading sub module "fglrxdrm"
    (II) LoadModule: "fglrxdrm"
    (II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
    (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
    compiled for 1.4.99.906, module version = 8.63.2
    (II) LoadModule: "dri2"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
    (II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DRI2
    (II) LoadModule: "fglrx"
    (II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
    (II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
    compiled for 1.4.99.906, module version = 8.63.2
    Module class: X.Org Video Driver
    (II) Primary Device is: PCI 01@00:00:0
    (WW) Falling back to old probe method for fglrx
    (II) ATI Proprietary Linux Driver Version Identifier:8.63.2
    (II) ATI Proprietary Linux Driver Release Identifier: 8.632
    (II) ATI Proprietary Linux Driver Build Date: Jul 2 2009 12:25:51
    (II) Loading PCS database from /etc/ati/amdpcsdb
    (WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
    (WW) Video driver ABI version of the X server is 5.0
    (--) Assigning device section with no busID to primary device
    (--) Chipset Supported AMD Graphics Processor (0x95C4) found
    (II) AMD Video driver is running on a device belonging to a group targeted for this release
    (II) AMD Video driver is signed
    (II) resource ranges after xf86ClaimFixedResources() call:
    [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 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) fglrx(0): pEnt->device->identifier=0x154b6d0
    (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] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (II) fglrx(0): === [atiddxPreInit] === begin
    (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.6.3, module version = 0.1.0
    ABI class: X.Org Video Driver, version 5.0
    (II) fglrx(0): PCI bus 1 card 0 func 0
    (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
    (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    (==) fglrx(0): Default visual is TrueColor
    (II) fglrx(0): 10BitPixelFormat disabled by default
    (==) fglrx(0): RGB weight 888
    (II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
    (==) fglrx(0): Gamma Correction for I is 0x06419064
    (==) fglrx(0): Gamma Correction for II is 0x06419064
    (==) fglrx(0): Buffer Tiling is ON
    (II) Loading sub module "fglrxdrm"
    (II) LoadModule: "fglrxdrm"
    (II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: drmOpenMinor returns 8
    drmOpenByBusid: drmGetBusid reports PCI:1:0:0
    (--) fglrx(0): Chipset: "ATI Mobility Radeon HD 3400 Series" (Chipset = 0x95c4)
    (--) fglrx(0): (PciSubVendor = 0x17aa, PciSubDevice = 0x210e)
    (--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
    (--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
    (--) fglrx(0): MMIO registers at 0xcfff0000
    (--) fglrx(0): I/O port at 0x00002000
    (==) fglrx(0): ROM-BIOS at 0x000c0000
    (II) fglrx(0): Battery is used
    (II) fglrx(0): Primary V_BIOS segment is: 0xc000
    (II) Loading sub module "vbe"
    (II) LoadModule: "vbe"
    (II) Loading /usr/lib/xorg/modules//libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.1.0
    ABI class: X.Org Video Driver, version 5.0
    (II) fglrx(0): VESA BIOS detected
    (II) fglrx(0): VESA VBE Version 3.0
    (II) fglrx(0): VESA VBE Total Mem: 16384 kB
    (II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
    (II) fglrx(0): VESA VBE OEM Software Rev: 10.88
    (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
    (II) fglrx(0): VESA VBE OEM Product: M82
    (II) fglrx(0): VESA VBE OEM Product Rev: 01.00
    (II) fglrx(0): ATI Video BIOS revision 9 or later detected
    (--) fglrx(0): Video RAM: 262144 kByte, Type: DDR3
    (II) fglrx(0): PCIE card detected
    (--) fglrx(0): Using per-process page tables (PPPT) as GART.
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (II) fglrx(0): Using adapter: 1:0.0.
    (II) fglrx(0): [FB] MC range(MCFBBase = 0xc0000000, MCFBSize = 0x10000000)
    (II) fglrx(0): [pcie] 1986048 kB allocated
    (II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
    (II) fglrx(0): Interrupt handler installed at IRQ 32.
    (II) fglrx(0): IRQ 32 Enabled.
    (II) fglrx(0): RandR 1.2 support is enabled!
    (II) fglrx(0): RandR 1.2 rotation support is enabled!
    (==) fglrx(0): Center Mode is disabled
    (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.6.3, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) Loading sub module "ddc"
    (II) LoadModule: "ddc"
    (II) Module "ddc" already built-in
    (II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000002, disabled=0x00000000
    (II) fglrx(0): Connected Display1: LCD on internal LVDS [lvds]
    (II) fglrx(0): Display1 EDID data ---------------------------
    (II) fglrx(0): Manufacturer: LEN Model: 4036 Serial#: 0
    (II) fglrx(0): Year: 2008 Week: 0
    (II) fglrx(0): EDID Version: 1.3
    (II) fglrx(0): Digital Display Input
    (II) fglrx(0): Max Image Size [cm]: horiz.: 30 vert.: 19
    (II) fglrx(0): Gamma: 2.20
    (II) fglrx(0): DPMS capabilities: StandBy Suspend Off
    (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    (II) fglrx(0): First detailed timing is preferred mode
    (II) fglrx(0): redX: 0.571 redY: 0.340 greenX: 0.338 greenY: 0.542
    (II) fglrx(0): blueX: 0.158 blueY: 0.125 whiteX: 0.313 whiteY: 0.329
    (II) fglrx(0): Manufacturer's mask: 0
    (II) fglrx(0): Supported detailed timing:
    (II) fglrx(0): clock: 101.6 MHz Image Size: 304 x 190 mm
    (II) fglrx(0): h_active: 1440 h_sync: 1488 h_sync_end 1520 h_blank_end 1824 h_border: 0
    (II) fglrx(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 926 v_border: 0
    (II) fglrx(0): Supported detailed timing:
    (II) fglrx(0): clock: 85.6 MHz Image Size: 304 x 190 mm
    (II) fglrx(0): h_active: 1440 h_sync: 1488 h_sync_end 1520 h_blank_end 1848 h_border: 0
    (II) fglrx(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 926 v_border: 0
    (WW) fglrx(0): Unknown vendor-specific block f
    (II) fglrx(0): LP141WP2-TLB1
    (II) fglrx(0): EDID (in hex):
    (II) fglrx(0): 00ffffffffffff0030ae364000000000
    (II) fglrx(0): 00120103801e1378ea4b859257568a28
    (II) fglrx(0): 20505400000001010101010101010101
    (II) fglrx(0): 010101010101b027a08051841a303020
    (II) fglrx(0): 360030be100000197021a09851841a30
    (II) fglrx(0): 3020360030be100000190000000f0095
    (II) fglrx(0): 0a32950a28191900320c3c01000000fe
    (II) fglrx(0): 004c503134315750322d544c4231001f
    (II) fglrx(0): End of Display1 EDID data --------------------
    (II) fglrx(0): Output LCD using monitor section LCD
    (II) fglrx(0): Output DFP1 has no monitor section
    (II) fglrx(0): Output CRT1 has no monitor section
    (II) fglrx(0): EDID vendor "LEN", prod id 16438
    (II) fglrx(0): Printing DDC gathered Modelines:
    (II) fglrx(0): Modeline "1440x900"x0.0 101.60 1440 1488 1520 1824 900 903 909 926 -hsync -vsync (55.7 kHz)
    (II) fglrx(0): Modeline "1440x900"x0.0 85.60 1440 1488 1520 1848 900 903 909 926 -hsync -vsync (46.3 kHz)
    (II) fglrx(0): Output LCD connected
    (II) fglrx(0): Output DFP1 disconnected
    (II) fglrx(0): Output CRT1 disconnected
    (II) fglrx(0): Using user preference for initial modes
    (II) fglrx(0): Output LCD using initial mode 1440x900
    (++) fglrx(0): DPI set to (96, 96)
    (==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) fglrx(0): QBS disabled
    (==) fglrx(0): FAST_SWAP disabled
    (==) fglrx(0): PseudoColor visuals disabled
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (==) fglrx(0): NoAccel = NO
    (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.6.3, module version = 1.2.1
    ABI class: X.Org Video Driver, version 5.0
    (==) fglrx(0): NoDRI = NO
    (==) fglrx(0): Capabilities: 0x00000000
    (==) fglrx(0): CapabilitiesEx: 0x00000000
    (==) fglrx(0): cpuFlags: 0x8000001d
    (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    (==) fglrx(0): UseFastTLS=0
    (==) fglrx(0): BlockSignalsOnLock=1
    (II) fglrx(0): Finished Initialize PPLIB!
    (--) 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] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
    (II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
    (WW) fglrx(0): could not detect X server version (query_status=-1)
    (II) Loading extension ATIFGLRXDRI
    (II) fglrx(0): doing DRIScreenInit
    (II) fglrx(0): DRIScreenInit for fglrx driver
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 11, (OK)
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 11, (OK)
    drmOpenByBusid: Searching for BusID PCI:1:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 11, (OK)
    drmOpenByBusid: drmOpenMinor returns 11
    drmOpenByBusid: drmGetBusid reports PCI:1:0:0
    (II) fglrx(0): [drm] DRM interface version 1.0
    (II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
    (II) fglrx(0): [drm] added 8192 byte SAREA at 0xcd000
    (II) fglrx(0): [drm] mapped SAREA 0xcd000 to 0x7f3e01f4b000
    (II) fglrx(0): [drm] framebuffer handle = 0xce000
    (II) fglrx(0): [drm] added 1 reserved context for kernel
    (II) fglrx(0): DRIScreenInit done
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0): Name: fglrx
    (II) fglrx(0): Version: 8.63.2
    (II) fglrx(0): Date: Jul 2 2009
    (II) fglrx(0): Desc: ATI FireGL DRM kernel module
    (II) fglrx(0): Kernel Module version matches driver.
    (II) fglrx(0): Kernel Module Build Time Information:
    (II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.30-ARCH
    (II) fglrx(0): Build-Kernel MODVERSIONS: no
    (II) fglrx(0): Build-Kernel __SMP__: yes
    (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
    (II) fglrx(0): [drm] register handle = 0x000cf000
    (II) fglrx(0): Display width adjusted to to 2816 due to alignment constraints
    (II) fglrx(0): DRI initialization successfull!
    (II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x0106a000
    (II) fglrx(0): FBMM initialized for area (0,0)-(2816,1528)
    (II) fglrx(0): FBMM auto alloc for area (0,0)-(2816,1024) (front color buffer - assumption)
    (II) fglrx(0): Largest offscreen area available: 2816 x 504
    (==) fglrx(0): Backing store disabled
    (II) Loading extension FGLRXEXTENSION
    (II) Loading extension ATITVOUT
    (II) fglrx(0): DPMS enabled
    (**) fglrx(0): Textured Video is enabled.
    (II) LoadModule: "glesx"
    (II) Loading /usr/lib/xorg/modules//glesx.so
    (II) Module glesx: vendor="X.Org Foundation"
    compiled for 1.4.99.906, module version = 1.0.0
    (II) Loading extension GLESX
    (II) fglrx(0): GLESX enableFlags = 94
    (II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
    Screen to screen bit blits
    Solid filled rectangles
    Solid Horizontal and Vertical Lines
    Driver provided ScreenToScreenBitBlt replacement
    Driver provided FillSolidRects replacement
    (II) fglrx(0): GLESX is enabled
    (II) LoadModule: "amdxmm"
    (II) Loading /usr/lib/xorg/modules//amdxmm.so
    (II) Module amdxmm: vendor="X.Org Foundation"
    compiled for 1.4.99.906, module version = 1.0.0
    (II) Loading extension AMDXVOPL
    (II) fglrx(0): UVD2 feature is available
    (II) fglrx(0): Enable composite support successfully
    (II) fglrx(0): X context handle = 0x1
    (II) fglrx(0): [DRI] installation complete
    (==) fglrx(0): Silken mouse enabled
    (==) fglrx(0): Using HW cursor of display infrastructure!
    (==) fglrx(0): Using software cursor
    (II) fglrx(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (--) RandR disabled
    (II) Initializing built-in extension Generic Event Extension
    (II) Initializing built-in extension SHAPE
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension BIG-REQUESTS
    (II) Initializing built-in extension SYNC
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-MISC
    (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
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (WW) AIGLX: 3D driver claims to not support visual 0x33
    (WW) AIGLX: 3D driver claims to not support visual 0x34
    (WW) AIGLX: 3D driver claims to not support visual 0x35
    (WW) AIGLX: 3D driver claims to not support visual 0x36
    (WW) AIGLX: 3D driver claims to not support visual 0x37
    (WW) AIGLX: 3D driver claims to not support visual 0x38
    (WW) AIGLX: 3D driver claims to not support visual 0x39
    (WW) AIGLX: 3D driver claims to not support visual 0x3a
    (WW) AIGLX: 3D driver claims to not support visual 0x3b
    (WW) AIGLX: 3D driver claims to not support visual 0x3c
    (WW) AIGLX: 3D driver claims to not support visual 0x3d
    (WW) AIGLX: 3D driver claims to not support visual 0x3e
    (WW) AIGLX: 3D driver claims to not support visual 0x3f
    (WW) AIGLX: 3D driver claims to not support visual 0x40
    (WW) AIGLX: 3D driver claims to not support visual 0x41
    (WW) AIGLX: 3D driver claims to not support visual 0x42
    (WW) AIGLX: 3D driver claims to not support visual 0x43
    (WW) AIGLX: 3D driver claims to not support visual 0x44
    (WW) AIGLX: 3D driver claims to not support visual 0x45
    (WW) AIGLX: 3D driver claims to not support visual 0x46
    (WW) AIGLX: 3D driver claims to not support visual 0x47
    (WW) AIGLX: 3D driver claims to not support visual 0x48
    (WW) AIGLX: 3D driver claims to not support visual 0x49
    (WW) AIGLX: 3D driver claims to not support visual 0x4a
    (WW) AIGLX: 3D driver claims to not support visual 0x4b
    (WW) AIGLX: 3D driver claims to not support visual 0x4c
    (WW) AIGLX: 3D driver claims to not support visual 0x4d
    (WW) AIGLX: 3D driver claims to not support visual 0x4e
    (WW) AIGLX: 3D driver claims to not support visual 0x4f
    (WW) AIGLX: 3D driver claims to not support visual 0x50
    (WW) AIGLX: 3D driver claims to not support visual 0x51
    (WW) AIGLX: 3D driver claims to not support visual 0x52
    (WW) AIGLX: 3D driver claims to not support visual 0x53
    (WW) AIGLX: 3D driver claims to not support visual 0x54
    (WW) AIGLX: 3D driver claims to not support visual 0x55
    (WW) AIGLX: 3D driver claims to not support visual 0x56
    (WW) AIGLX: 3D driver claims to not support visual 0x57
    (WW) AIGLX: 3D driver claims to not support visual 0x58
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72
    (II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so
    (II) GLX: Initialized DRI GL provider for screen 0
    (II) fglrx(0): Enable the clock gating!
    (II) fglrx(0): Setting screen physical size to 381 x 238
    (II) config/hal: Adding input device ThinkPad Extra Buttons
    (II) LoadModule: "evdev"
    (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 2.2.3
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
    (**) ThinkPad Extra Buttons: always reports core events
    (**) ThinkPad Extra Buttons: Device: "/dev/input/event6"
    (II) ThinkPad Extra Buttons: Found keys
    (II) ThinkPad Extra Buttons: Configuring as keyboard
    (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us,no"
    (**) Option "xkb_options" "grp:alt_shift_toggle"
    (II) config/hal: Adding input device Macintosh mouse button emulation
    (**) Macintosh mouse button emulation: always reports core events
    (**) Macintosh mouse button emulation: Device: "/dev/input/event0"
    (II) Macintosh mouse button emulation: Found 3 mouse buttons
    (II) Macintosh mouse button emulation: Found x and y relative axes
    (II) Macintosh mouse button emulation: Configuring as mouse
    (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
    (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
    (**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
    (**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
    (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
    (**) Macintosh mouse button emulation: (accel) set acceleration profile 0
    (II) config/hal: Adding input device TPPS/2 IBM TrackPoint
    (**) TPPS/2 IBM TrackPoint: always reports core events
    (**) TPPS/2 IBM TrackPoint: Device: "/dev/input/event8"
    (II) TPPS/2 IBM TrackPoint: Found 3 mouse buttons
    (II) TPPS/2 IBM TrackPoint: Found x and y relative axes
    (II) TPPS/2 IBM TrackPoint: Configuring as mouse
    (**) TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
    (**) TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE)
    (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
    (**) TPPS/2 IBM TrackPoint: (accel) filter chain progression: 2.00
    (**) TPPS/2 IBM TrackPoint: (accel) filter stage 0: 20.00 ms
    (**) TPPS/2 IBM TrackPoint: (accel) set acceleration profile 0
    (II) config/hal: Adding input device Logitech USB Receiver
    (**) Logitech USB Receiver: always reports core events
    (**) Logitech USB Receiver: Device: "/dev/input/event9"
    (II) Logitech USB Receiver: Found 20 mouse buttons
    (II) Logitech USB Receiver: Found x and y relative axes
    (II) Logitech USB Receiver: Found scroll wheel(s)
    (II) Logitech USB Receiver: Configuring as mouse
    (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
    (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    (**) Logitech USB Receiver: (accel) filter chain progression: 2.00
    (**) Logitech USB Receiver: (accel) filter stage 0: 20.00 ms
    (**) Logitech USB Receiver: (accel) set acceleration profile 0
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (**) AT Translated Set 2 keyboard: always reports core events
    (**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
    (II) AT Translated Set 2 keyboard: Found keys
    (II) AT Translated Set 2 keyboard: Configuring as keyboard
    (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us,no"
    (**) Option "xkb_options" "grp:alt_shift_toggle"
    (II) config/hal: Adding input device Logitech USB Receiver
    (**) Logitech USB Receiver: always reports core events
    (**) Logitech USB Receiver: Device: "/dev/input/event10"
    (II) Logitech USB Receiver: Found 1 mouse buttons
    (II) Logitech USB Receiver: Found scroll wheel(s)
    (II) Logitech USB Receiver: Found keys
    (II) Logitech USB Receiver: Configuring as keyboard
    (II) Logitech USB Receiver: Adding scrollwheel support
    (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us,no"
    (**) Option "xkb_options" "grp:alt_shift_toggle"
    (II) config/hal: Adding input device Video Bus
    (**) Video Bus: always reports core events
    (**) Video Bus: Device: "/dev/input/event5"
    (II) Video Bus: Found keys
    (II) Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us,no"
    (**) Option "xkb_options" "grp:alt_shift_toggle"
    (II) fglrx(0): EDID vendor "LEN", prod id 16438
    (II) fglrx(0): Printing DDC gathered Modelines:
    (II) fglrx(0): Modeline "1440x900"x0.0 101.60 1440 1488 1520 1824 900 903 909 926 -hsync -vsync (55.7 kHz)
    (II) fglrx(0): Modeline "1440x900"x0.0 85.60 1440 1488 1520 1848 900 903 909 926 -hsync -vsync (46.3 kHz)
    (II) fglrx(0): EDID vendor "LEN", prod id 16438
    (II) fglrx(0): Printing DDC gathered Modelines:
    (II) fglrx(0): Modeline "1440x900"x0.0 101.60 1440 1488 1520 1824 900 903 909 926 -hsync -vsync (55.7 kHz)
    (II) fglrx(0): Modeline "1440x900"x0.0 85.60 1440 1488 1520 1848 900 903 909 926 -hsync -vsync (46.3 kHz)
    Last edited by orjanp (2009-08-12 08:43:13)

  • Fire FTP does not work with Firesfox 4. It worked OK with version 3. How can I get a New Fire FTP? Last version of FTP does not solve the problem

    Fire FTP does not work with Firesfox 4. It worked OK with version 3. How can I get a New Fire FTP? Last version of FTP does not solve the problem

    I need to know if it's 64-bit or 32-bit.
    If it's 64-bit, try copying the mms.cfg file from C:\WINDOWS\syswow64\Macromed\Flash to C:\WINDOWS\system32\Macromed\Flash

  • I upgraded Safari in my Mac (10.6.8 Leopard) but the new version does not work with my system so that I now have not a working browser. How can I solve the problem and/or install back my previous Safari version?

    I have upgraded Safari in my Mac, but the new Safari does not work with my system. So I find myself without any working browser. How can I solve this problem and/or install my previous Safari version?

    Reinstall Safari 5.1.10 for OS X 10.6.8: http://support.apple.com/kb/dl1569. Might do the trick.
    But, frankly, I don't think that simply reinstalling the old Safari will work because of all the peripheral, under the hood changes that happen when you upgrade from one version of Safari to another. Reinstalling 5.1.10 may be insufficient to turn back the clock. (This is the moment where a Time Machine or another form of full backup would save your bacon.)
    While you're getting a copy of Safari 5.1.10, get a copy of Firefox (https://www.mozilla.org/en-US/firefox/desktop/), too, so that you have an alternate browser to use as you're sorting matters.

  • Hi, on a new MBPR 13, I transferred pics from my Samsung Tracfone smartphone using AndroidTransferFile app worked good. My Samsung Galaxy Tab will not transfer with ATF, tried Samsung Kies also no luck, any ideas? Thanks...

    Hi, on a new MBPR 13, I transferred pics from my Samsung Tracfone smartphone using AndroidTransferFile app, worked good. My Samsung Galaxy Tab will not transfer with ATF, tried Samsung Kies also no luck, any ideas? Thanks...

    Today I downloaded a new version of Kies, 3.1.0.15042_6, and it seemed to work fine.  I was able to backup my Note 3 running Lollipop with no hesitation.  Files transferred to my Mac running Yosemite, OS X 10.10.3, easily.  The download is available at http://www.samsung.com/us/kies/

  • [rxvt-unicode]pseudo-transparency not working with Awesome WM (solved)

    Hi all,
    first of all, let me tell you that I googled about this problem, I read the Archwiki, the rxvt FAQ and several threads in multiple forums but nothing that I found actually worked.
    I'm using Awesome WM and OpenBox and my rxvt is the standard rxvt-unicode from the repos.
    Since an update, rxvt is not transparent anymore (I was using pseudo-transparency). Actually, transparency works with OpenBox but it does not work with Awesome WM. I find it very weird.
    I tried increasing the shading value in .Xdefaults as suggested in an other thread in this form but it did not help at all. I thought the problem was that I needed libafterimage so I installed it but then, how to use it?
    Does someone have any idea about this? I'd be very thankfull!
    Last edited by Sherwood51 (2011-01-18 17:04:37)

    And how exactly did you get it to work with feh ? I keep failing to get pseudo-transparency.
    My theme.lua has this:
    awsetbg -f -u feh path/to/wallpaper
    and I also tried this:
    feh --bg-scale path/to/wallpaper
    and in Xdefaults:
    URxvt*background 0
    URxvt*depth 24 ( doesn't work with 32 either )
    URxvt*inheritPixmap true
    URxvt*transparent true
    EDIT:
    I got cairo working ( finally ), so I have true transparency, so don't mind my post.
    Last edited by Varg (2011-01-19 21:08:33)

  • HP Pavilion x360 touchscreen stops working with Win 8.1 pro

    I currently have a HP Pavilion x360 2in1 convertible laptop.  The model # is 11-n010dx.  My issue is the touchscreen was working just fine with Win 8 on it, however, I need to be able to connect to my work network and that requires Win 8.1 pro.  I did the upgrade to Win 8.1 pro 64-bit and the touchscreen is not even recognized by the OS.  It states "No pen or Touch input is available for this display."  I have installed all of the drivers, nothing is missing from the device manager.  I try to install SP57846 but get an error that states that my computer does not meet the minimum requirememnt for this update.  I just need drivers to run my touchscreen in Win 8.1 pro 64-bit.
    Thanks

    Hi @ThundarTheOrk ,
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion 11-n010dx x360 and the Touchscreen not working correctly after a Windows 8.1 update. Here is a link to a document on troubleshooting the Touchscreen.
    Here is a fix I found from Microsoft.
    The touchscreen shouldn’t need recalibration, but if you or another user has recalibrated it, it may affect the performance of the touchscreen.
    Here’s how to check or restore the factory default calibration using a keyboard or mouse:
    Press the Windows logo key Type Control Panel, then use the arrow keys to highlight Control Panel, and press Enter.
    In Control Panel, use the arrow keys to highlight Hardware and Sound and press Enter.
    Under Tablet PC Settings use the arrow keys to highlight Calibrate the screen for pen or touch input, and press Enter.
    Use the Tab key to select the Reset button, and press Enter.
    If the Reset button is grayed out, your Surface touch calibration is still at factory settings and nothing further required.
    Use the Tab key to select Yes, press Enter, and then follow the instructions on the screen.
    Hope this works for you.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • HP Pavilion 14z-n200 Touchsmart CTO Notebook touchscreen not working after update

    More than a month ago I updated my HP Pavilion 14z-n200 Touchsmart CTO Notebook and after the required restart I noticed that the touchscreen had stopped responding. I have searched the forums and found that other members of the HP Pavilion Touchsmart family had the same issues, but their solutions have not solved the problem with my specific PC. Any help would be great! Thanks

    Hi @Cbird22 ,
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion 14z-n200 TouchSmart CTO Notebook  and the Touchscreen not working correctly. If you follow this document it will show you how to correct this issue.
    You can do a system restore. System restore will help if something automatically updated and did not go well on the Notebook.
    When performing a System restore please note remove any and all USB devices. Disconnect all non-essential devices as they can cause issues.
    Hope this helps.
    Thanks
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Maybe you are looking for