Recording/Monitoring Problems

Hi Fellow Mac'rs!:
I am trying to use Logic Studio to do 2 things
1. Record an electric guitar through an interface into Logic, adjust levels and monitor that performance as I record it via headphones;
2. Record a vocal through the same interface, adjust levels and monitor that performance via headphones.
When I monitor/try to set levels/record guitar or vocals I am using headphones (plugged into MacPro headphone jack) to monitor, but hear nothing
When I playback, I hear recorded performance in headphones fine
Problems I am having
1. I do not hear my guitar or vocal imput and cannot monitor levels, nor adjust levels (vocal levels hardly register and on playback they are a whisper)
2. Guitar: there is response levels showing before recording, but no ability to raise/lower volume/set levels = no response
3. Vocals: there is response (barely) and levels showing before recording, but no ability to raise/lower volume/set levels = no response
Running Logic 9.1.4
Headphones: Sennheiser
Mic: AKG C1000S
Audio Interface: ESI UGM96
This set-up has worked before, now I am having issues described.
Could this be a hardware issue??
I hope I'm explaining myself properly.
Thanks!

Firstly
Software monitoring must be enabled in preferences / audio
You then need to record arm and press the little i button to input monitor
and while you are in there, just make sure that the ESI is still set to be the input inferface, logic can forget, or it can change.
secondly, make sure all of you analouge gain staging is correct
IE things are averaging around 0dbvu on the way in, if you have the metering of course.
the fader makes no diffrence to the file being recorded, all it does is affect the level sent to the output.
and finally also in audio preferences make sure that independent monitor level isn't checked.
i hope that helps,

Similar Messages

  • Buttons under source and record monitors not working

    For some odd reason, the buttons under the source and record monitors are not working in Premiere. This is a new install, and I'm relatively new to Windows so I hope it is something obvious. Buttons in other CC apps work fine. Any ideas out there?
    Windows 7
    2 x 10 core CPU (40 virtual)
    64 GB Ram
    nVidia Titan
    Decklink 4K
    Latest Premiere CC build
    Wacom Tablet

    Yes, actually. I unplugged the Wacom, uninstalled the drivers and restarted. Problem still there. Other ideas?
    Chris
    =========================================
    Edited by moderator to remove personal information

  • Possibly mundane Mini-DVI to VGA into an external monitor problem

    Hi,
    I've had a look over the interwebs regarding my problem and it seems as if it's not unusual to have external monitor problems but I'm not sure if mine is slightly different:
    I had a perfectly working set up with my new Macbook (the white one, '06 model I believe), that was connected to my Hanns-G HU196D monitor via a mini-DVI to VGA adapter, no problems whatsoever. But for a couple of weeks now my Macbook just flickers a light blue colour, with nothing at all on the monitor, and my macbook is unusable until I remove the adapter. I've read about updating firmware but I can't see my desktop once the macbook is connected to the monitor so it's not possible to configure anything. I've read somewhere that my external monitor isn't compatible with this set up, but it was until a couple of weeks ago!
    My Macbook's 4 months old now and since then I've bought a new mini-dvi to vga adapter and a new VGA cable, no connections seem loose on either mini-dvi port or my monitor's vga port.
    Thanks if you can help!
    Jack

    You will need to use a mini Dvi-dvi and a dvi-svideo/rca adapter.
    Joy joy hallelujah.
    Pardon the sarcasm...I just wasted 3 hours of my life trying to sort the issue out.
    Heard a KWORLD PlusTV PCTOTV Converter SA235 USB 2.0 Interface would sort the issue out for under 40$ but it's not Mac.
    Hope that helps.
    ~r

  • Need help: Flex  record webcam problem, how to setting Brightness,Contrast,Saturation and Sharpness

    Hello, dear all
    Please help me!
    Flex  record webcam problem, how to setting Brightness,Contrast,Saturation and Sharpness?
    nsOutGoing=new NetStream(nc);
    nsOutGoing.attachCamera(m_camera);
    nsOutGoing.publish(filename, "record");
    I want to control the Brightness,Contrast,Saturation and Sharpness for the recorded flv file.
    At present, I only can control the videodisplay object, but I can not able to control Camera.
    Thanks very much!!
    kimi
    MSN: [email protected]

    Can I change a Video object to to Camera object, If yes, How do??
    nsOutGoing.attachCamera(video as Camera);// it does not work rightly
    thanks

  • JavaScript error and CATW record locking problem

    Hello,
    We're having two problems with ESS (CATW and Personal Information (PZM3)) in EP 6. We have an ITS-R/3 landscape.
    The JavaScript problem appears intermittently within Personal Data services (Address, Emergency Contact, ...). The actual error reads "object required" and originates from ITS. A user may be able to click through all the ESS services once fine, but on a second click receive the error. Sometimes they can't use the services at all.
    The record locking problem happens in Time Sheet (CATW). Even though a user Saves and Releases the Time Sheet, it remains locked and cannot be approved. Alternatively, some users are experiencing locked records when they try to complete their own time sheets.
    I'm not sure if these are related.
    Has anyone here seen these problems? Any suggestions are most welcome!
    Cheers,
    Colleen

    The best way to nail down the javascript error would be to use the firefox JavaScript debugger extension plugin and put the breakpoints where the problem occurs.
    This will exactly tell you which object it is looking for which is not found. Moreover you might be able to find that when it is working fine as you said. So give that a try and I am sure you will be able to figure out the problem.
    To me this mostly looks like at time some .js file is not coming through to the browser... but this is just a wild guess based on the symptoms.

  • Logic cpu meter spike while recording / monitoring?

    Hey, I just checked Logic's internal CPU meter, and noticed something quite weird is happening.
    I have only ever had one overload message, which I think was caused by changing a BFD2 setting, so the fact Logic believes that it's maxing out one of my cores confuses me a little more.
    Anyway, in a template project (just unused audio tracks), if I click the record (or the monitor) button, my first core tops out in Logic's meter, but in the activity monitor, little changes, and sometimes even shows the load changing between cores, with Logic still insisting the overloading core is doing the work.
    If I deselect the button, the core returns to no/little load. It doesn't seem to affect Logic's performance, but I'm more than curious about this.
    Anyone have the same thing happen to them, or is there a reason for this?
    Screenshots are here:
    http://i4.photobucket.com/albums/y136/Ed91/Picture1.png
    and here:
    http://i4.photobucket.com/albums/y136/Ed91/Picture2.png
    Thanks, Ed
    Message was edited by: Ed Davies
    Message was edited by: Ed Davies

    From another post of mine:
    An observation about lopsided CPU behaviour: a reliable source(an AU and hardware developer) remarked the other day that according to his tests all stuff that is on record enabled/monitored tracks can only run in a single thread using the (small) i/o buffer on one CPU.
    This 'real time' CPU can easily be overloaded, while the rest of the CPU's may be idling.
    You can have loads and loads of CPU hungry stuff on tracks that are in playback mode(and that use a large buffer because logic knows what is coming) on an octocore, but for record/monitor enabled tracks the octocore is just as good as a single core/cpu machine with the same specs(CPU speed/cache/RAM speed etc.)
    Haven't tested this myself yet, but is sounds plausible and it would certainly explain some of the trouble I've seen with CPU overtloads.

  • M93p dual monitor problems; monitor turns off and cannot be turned on again

    Hi,
    we have multiple M93p tiny computers causing problems in dual monitor setup (VGA / Displayport->DVI). Our users (already >5)  keep telling us, they leave their workplace, return, then DVI attached monitor if off and they do not find a way to turn it on. This is true; the only workaround that has been found by our users is to bring Win7/32bit into standby mode and awaking it again.
    Needless to say, we turned all windows energy saving options off (computer standby/hibernate, monitor turn off). Still the problem appears.
    Maybe there is something wrong with DVI power/DVI signal?
    - Monitor independent, as far as I can see
    - Independent from Windows energy saving modes
    - BIOS updates did not help
    [todo]: Try Intel/(AMD?) drivers, let users test.
    I haven't seen exactly when the monitor turns off because it is reported by users. I had a testing machine, but was not able to reproduce.
    http://forums.lenovo.com/t5/A-M-and-Edge-Series-Th​inkCentre/Dual-monitors-problem-VGA-and-Displaypor​... is related.
    Anyone?
    Thx

    Make a "Genius" appointment at an Apple Store to have the machine tested.
    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
    Keeping your confidential data secure during hardware repair
    *An SSD doesn't need to be zeroed.

  • Disable G722 Advertisement for Call Recording/Monitoring

    I'm troublshooting some call recording/monitoring issues and have come across many steps that reference disabling the "Advertise G.722 codec" in Enterprise Parameters for call manager.
    Contact Center itself can only operate in G711 or G729 and I've validated when agents are on a call with their UCCX extension that they are using the G711 codec. Since UCCX cannot operate at G722 and my agents are taking calls are using G711, what is the reason why the G722 codec advertisement needs to be disabled?
    Thanks.

    Hi Paul,
    It's not the G722 to UCCX that you need to worry about, because the IP Phone will negotiate G711 and not G722.  Both parties have to support it in order for it to be used.  An example of this is an IP Phone calling a UCCX trigger and interacting with a script.
    However, it's the internal calls to Agents that you need to worry about.  An example of this is an internal employee calling the Help Desk and speaking to an Agent.  At this point, the two IP Phones will negotiate G722 and when the UCCX system tries to monitor or record that conversation, it cannot.
    UCCX can only mon/rec G729 or G711.  Therefore, if you didn't care about UCCX based mon/rec, then leave G722 enabled.  It doesn't break your UCCX as a whole, it only prevents you from mon/rec those specific calls.  Calls inbound from the PSTN would likely be G711, and would still work for mon/rec.
    Does that make sense?
    Anthony Holloway
    Please use the star ratings to help drive great content to the top of searches.
    EDIT: Added some more clarity.

  • Activity Monitor problems increase CPU and power burn

    Migration Assistant worked very nicely, transferring from a Powerbook G4 with 30GB of files and data in about 45min via Firewire.
    However, after 2 days of usage, the CPU was still running at 80% and applications were incredibly sluggish. My battery calibration at full charge only showed a little over 1 hour. Activity Monitor also would not show any processes -- the list was completely blank.
    The solution was to rename the Preferences folder, allowing programs to create a new Preferences folder. I then selectively populated the new folder with the main old preferences for mail, Safari, etc. This not only solved the Activity Monitor problem, but immediately drove down the CPU usage to about 10% where I'd expect it. Now the battery shows over 2.5 hrs on a full charge with the screen on full brightness (and it's BRIGHT!)
    Also, Microsoft Word/Powerpoint/Excel/Entourage: trial software on the MacBookPro will mess up your migration, so delete the trial software BEFORE MIGRATION ASSISTANT.
    Hope this helps some of you out there!

    Another thing users who run Migration Assistant should know is that many of your background processes and helpers may slow down the Macbook.
    For example, I notice that a bunch of PowerPC menu items running under Rosetta slowed things down. Also, the Microsoft Office Autoupdate background process, which is started from System Preferences > Accounts > Login Items constituted one Rosetta process running all of the time.
    When I remove/disabled these background processes, I noticed a significant difference.

  • Monitoring problem when recording

    Greetings. I have a Presonus Firebox which I'm using in conjunction with a 2.0 GHz MacBook with 2 gigs memory and Logic Express. I've run into a problem when attempting to monitor an audio (mic) input. When recording a mono source, I can only hear my signal in one side of my headphones: left if recording into input 1, right if into input 2. This is, needless to say, very disorienting. I don't have the same problem when playing back the track. While I'm currently using Logic Express, I have the same problem using the Firebox in Garageband. I did not have the problem when using Sonar 6 under Bootcamp on the same machine. I've checked all of the settings in Logic and they seem perfectly normal (proper inputs and outputs selected, mono inputs panned center, etc.).
    Any ideas?
    Thanks,
    Trent

    Hey Trent,
    Since your channel strip is in Mono (logic) right?
    open you Presonus FireBox Mixer, and zero the
    pan (mic1) or Playback to Phones or
    the Mix button to phones.
    regards,
    Jorge

  • Input monitoring problem during recording

    Greetings,
    I recently purchased Logic Pro 9, and am having a problem with input monitoring. I am not able to in any way affect control over my monitor mix during recording. I have tried every combination of options, including software monitoring, auto-input monitoring, etc...but always get the same headphone levels from my inputs (I am actually trying to mute the input signals out completely so that I can play along to only the click.
    I am wondering whether this is some sort of software glitch, because I was able to control the mix perfectly before the latest software update. I wonder if that is the problem, or if I am overlooking some minor detail. Please help!!
    BTW, I have checked, and this is definitely a software, not a hardware issue...
    Thanks much,
    Kevin

    I have a similar problem, although I'm on Logic Pro 8.
    I can't seem to record my guitar track (mic'd cabinet) without having the result monitor back through my studio monitors unless I turn off software monitoring in Preferences/Audio. But then if I want to record keyboards direct and listen to what I'm playing, I have to go back in and turn the option back on.
    In Sonar on the PC, this was much more intuitive. You could arm a track for recording by clicking the "R" button, and separately toggle monitoring on and off by clicking the little speaker button to the right. You didn't have to constantly fiddle with the program preferences.
    I have a FireWire410 interface, and the monitoring only happens when Logic is loaded. I would have thought that the little "I" icon was to turn monitoring on and off, but it's some "pre/post-tape" toggle I can't find a use for.
    Kevin, how did you control your monitor mix before?

  • Having Monitoring Problems with in Adobe Audition using built in outputs No playback while recording?

    I was using Adobe audition to Record Audio and some how the output throught the hardware settings got changed to airplay. Now even if I change the settings to built in output the is no playback through the computer speakers!! aAny Help would be great! I Put this quesion in the Adobe Forums as well. Just thought I might get some help here quicker. Thanks for your time.

    "This program is too expensive to have such an amateur limitation."
    To help you, Eric.. this is a conclusion to the question the precedes it. I never blamed the program for my lack of knowledge. I wouldn't waste my time in a message board asking how to accomplish a task if I felt it was impossible.
    And, Arrogance? The extent of my description was to prevent people from responding with suggestions I've already tried. The second response fixed the problem (not the first, mind you) so it seems my message suited the situation... and no others found the need to tell me I was the problem.
    MY attitude is in response to YOUR arrogance. After asking a friendly question, you respond with the limitation only being mine, but there is also a limitation with the software. Contradictory? I see you have a reputation to uphold, and now understand the driver that came with Audition does have limitation. It's nice to see you have people that give you credit, because your posts merely tell me that (1) I don't know what I'm doing .. and (2) Yeah, Audition has the limitation you need help getting around.
    Well thanks for your help. My first and last point is why you find the need to tell people they don't understand something, when that's clearly why they've come to you and your peers. You'd make a great firefighter -- showin' up with flashing lights, to deliver the news to people that they don't know how to work an oven.

  • [solved] ThinkPad connect with extern Monitor Problem

    Hello community
    I have installed arch on my T420 integrated HD 3000 and i have the Problem that when i start arch and the boot messages comes i can see the deamon starts ok,ok,ok who should be on the right side but on the NEC they was displayed 5 cm inside. Also when iam on the console and i type dmesg all the output scroll down and broke 5 cm from the roof. And when iam on openbox and i will maximize one window it would be maximized on the size from the Laptop LCD.
    I have made an .xinitrc
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    #xrandr --output DP2 --auto --output LVDS --right-of LVDS
    #xrandr --output DP1 --auto --output LVDS --auto --same-as DP1
    xrandr -d DP2 -s 1900x1200
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    # exec gnome-session
    # exec startkde
    # exec startxfce4
    and here is my Xorg.0.log
    [ 81.298]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 81.298] X Protocol Version 11, Revision 0
    [ 81.298] Build Operating System: Linux 3.4.8-1-ARCH x86_64
    [ 81.298] Current Operating System: Linux bullitt 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64
    [ 81.298] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=7b8780ba-278c-4d61-a1ec-ba2a6f96c6ba ro quiet
    [ 81.299] Build Date: 27 August 2012 08:04:39AM
    [ 81.299]
    [ 81.299] Current version of pixman: 0.26.2
    [ 81.299] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 81.299] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 81.306] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 7 16:33:34 2012
    [ 81.307] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 81.308] (==) No Layout section. Using the first Screen section.
    [ 81.308] (==) No screen section available. Using defaults.
    [ 81.308] (**) |-->Screen "Default Screen Section" (0)
    [ 81.308] (**) | |-->Monitor "<default monitor>"
    [ 81.308] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 81.308] (==) Automatically adding devices
    [ 81.308] (==) Automatically enabling devices
    [ 81.308] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 81.308] Entry deleted from font path.
    [ 81.308] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 81.308] Entry deleted from font path.
    [ 81.308] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 81.308] Entry deleted from font path.
    [ 81.308] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 81.308] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 81.308] Entry deleted from font path.
    [ 81.308] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 81.308] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 81.308] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 81.308] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 81.308] (II) Loader magic: 0x7c8b00
    [ 81.308] (II) Module ABI versions:
    [ 81.308] X.Org ANSI C Emulation: 0.4
    [ 81.308] X.Org Video Driver: 12.1
    [ 81.308] X.Org XInput driver : 16.0
    [ 81.308] X.Org Server Extension : 6.0
    [ 81.308] (--) PCI:*(0:0:2:0) 8086:0126:17aa:21ce rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00005000/64
    [ 81.308] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 81.308] (II) LoadModule: "extmod"
    [ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 81.309] (II) Module extmod: vendor="X.Org Foundation"
    [ 81.309] compiled for 1.12.4, module version = 1.0.0
    [ 81.309] Module class: X.Org Server Extension
    [ 81.309] ABI class: X.Org Server Extension, version 6.0
    [ 81.309] (II) Loading extension MIT-SCREEN-SAVER
    [ 81.309] (II) Loading extension XFree86-VidModeExtension
    [ 81.309] (II) Loading extension XFree86-DGA
    [ 81.309] (II) Loading extension DPMS
    [ 81.309] (II) Loading extension XVideo
    [ 81.309] (II) Loading extension XVideo-MotionCompensation
    [ 81.309] (II) Loading extension X-Resource
    [ 81.309] (II) LoadModule: "dbe"
    [ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 81.309] (II) Module dbe: vendor="X.Org Foundation"
    [ 81.309] compiled for 1.12.4, module version = 1.0.0
    [ 81.309] Module class: X.Org Server Extension
    [ 81.309] ABI class: X.Org Server Extension, version 6.0
    [ 81.309] (II) Loading extension DOUBLE-BUFFER
    [ 81.309] (II) LoadModule: "glx"
    [ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 81.309] (II) Module glx: vendor="X.Org Foundation"
    [ 81.309] compiled for 1.12.4, module version = 1.0.0
    [ 81.309] ABI class: X.Org Server Extension, version 6.0
    [ 81.309] (==) AIGLX enabled
    [ 81.309] (II) Loading extension GLX
    [ 81.309] (II) LoadModule: "record"
    [ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 81.309] (II) Module record: vendor="X.Org Foundation"
    [ 81.309] compiled for 1.12.4, module version = 1.13.0
    [ 81.309] Module class: X.Org Server Extension
    [ 81.309] ABI class: X.Org Server Extension, version 6.0
    [ 81.309] (II) Loading extension RECORD
    [ 81.309] (II) LoadModule: "dri"
    [ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 81.309] (II) Module dri: vendor="X.Org Foundation"
    [ 81.309] compiled for 1.12.4, module version = 1.0.0
    [ 81.309] ABI class: X.Org Server Extension, version 6.0
    [ 81.309] (II) Loading extension XFree86-DRI
    [ 81.309] (II) LoadModule: "dri2"
    [ 81.309] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 81.309] (II) Module dri2: vendor="X.Org Foundation"
    [ 81.309] compiled for 1.12.4, module version = 1.2.0
    [ 81.309] ABI class: X.Org Server Extension, version 6.0
    [ 81.309] (II) Loading extension DRI2
    [ 81.309] (==) Matched intel as autoconfigured driver 0
    [ 81.309] (==) Matched vesa as autoconfigured driver 1
    [ 81.309] (==) Matched fbdev as autoconfigured driver 2
    [ 81.309] (==) Assigned the driver to the xf86ConfigLayout
    [ 81.309] (II) LoadModule: "intel"
    [ 81.310] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 81.310] (II) Module intel: vendor="X.Org Foundation"
    [ 81.310] compiled for 1.12.4, module version = 2.20.9
    [ 81.310] Module class: X.Org Video Driver
    [ 81.310] ABI class: X.Org Video Driver, version 12.1
    [ 81.310] (II) LoadModule: "vesa"
    [ 81.310] (WW) Warning, couldn't open module vesa
    [ 81.310] (II) UnloadModule: "vesa"
    [ 81.310] (II) Unloading vesa
    [ 81.310] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 81.310] (II) LoadModule: "fbdev"
    [ 81.310] (WW) Warning, couldn't open module fbdev
    [ 81.310] (II) UnloadModule: "fbdev"
    [ 81.310] (II) Unloading fbdev
    [ 81.310] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 81.310] (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+),
    ValleyView PO board
    [ 81.310] (--) using VT number 7
    [ 81.313] drmOpenDevice: node name is /dev/dri/card0
    [ 81.314] drmOpenDevice: open result is 8, (OK)
    [ 81.314] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 81.314] drmOpenDevice: node name is /dev/dri/card0
    [ 81.314] drmOpenDevice: open result is 8, (OK)
    [ 81.314] drmOpenByBusid: drmOpenMinor returns 8
    [ 81.314] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 81.314] drmOpenDevice: node name is /dev/dri/card0
    [ 81.314] drmOpenDevice: open result is 9, (OK)
    [ 81.314] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 81.314] drmOpenDevice: node name is /dev/dri/card0
    [ 81.314] drmOpenDevice: open result is 9, (OK)
    [ 81.314] drmOpenByBusid: drmOpenMinor returns 9
    [ 81.314] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 81.314] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 81.314] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 81.314] (==) intel(0): RGB weight 888
    [ 81.314] (==) intel(0): Default visual is TrueColor
    [ 81.314] (--) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2+)
    [ 81.314] (**) intel(0): Relaxed fencing enabled
    [ 81.314] (**) intel(0): Wait on SwapBuffers? enabled
    [ 81.314] (**) intel(0): Triple buffering? enabled
    [ 81.314] (**) intel(0): Framebuffer tiled
    [ 81.315] (**) intel(0): Pixmaps tiled
    [ 81.315] (**) intel(0): 3D buffers tiled
    [ 81.315] (**) intel(0): SwapBuffers wait enabled
    [ 81.315] (==) intel(0): video overlay key set to 0x101fe
    [ 81.315] (II) intel(0): Output LVDS1 has no monitor section
    [ 81.315] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
    [ 81.315] (II) intel(0): Output VGA1 has no monitor section
    [ 81.340] (II) intel(0): Output HDMI1 has no monitor section
    [ 81.380] (II) intel(0): Output DP1 has no monitor section
    [ 81.393] (II) intel(0): Output HDMI2 has no monitor section
    [ 81.406] (II) intel(0): Output HDMI3 has no monitor section
    [ 81.464] (II) intel(0): Output DP2 has no monitor section
    [ 81.506] (II) intel(0): Output DP3 has no monitor section
    [ 81.507] (II) intel(0): EDID for output LVDS1
    [ 81.507] (II) intel(0): Manufacturer: AUO Model: 213e Serial#: 0
    [ 81.507] (II) intel(0): Year: 2010 Week: 33
    [ 81.507] (II) intel(0): EDID Version: 1.4
    [ 81.507] (II) intel(0): Digital Display Input
    [ 81.507] (II) intel(0): 6 bits per channel
    [ 81.507] (II) intel(0): Digital interface is undefined
    [ 81.507] (II) intel(0): Max Image Size [cm]: horiz.: 31 vert.: 17
    [ 81.507] (II) intel(0): Gamma: 2.20
    [ 81.507] (II) intel(0): No DPMS capabilities specified
    [ 81.507] (II) intel(0): Supported color encodings: RGB 4:4:4
    [ 81.507] (II) intel(0): First detailed timing is preferred mode
    [ 81.507] (II) intel(0): Preferred mode is native pixel format and refresh rate
    [ 81.507] (II) intel(0): redX: 0.610 redY: 0.350 greenX: 0.320 greenY: 0.560
    [ 81.507] (II) intel(0): blueX: 0.150 blueY: 0.130 whiteX: 0.313 whiteY: 0.329
    [ 81.507] (II) intel(0): Manufacturer's mask: 0
    [ 81.507] (II) intel(0): Supported detailed timing:
    [ 81.507] (II) intel(0): clock: 110.0 MHz Image Size: 309 x 174 mm
    [ 81.507] (II) intel(0): h_active: 1600 h_sync: 1664 h_sync_end 1706 h_blank_end 2010 h_border: 0
    [ 81.507] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 906 v_blanking: 912 v_border: 0
    [ 81.507] (II) intel(0): Supported detailed timing:
    [ 81.507] (II) intel(0): clock: 73.3 MHz Image Size: 309 x 174 mm
    [ 81.507] (II) intel(0): h_active: 1600 h_sync: 1664 h_sync_end 1706 h_blank_end 2010 h_border: 0
    [ 81.507] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 906 v_blanking: 912 v_border: 0
    [ 81.507] (II) intel(0): AUO
    [ 81.507] (II) intel(0): B140RW02 V1
    [ 81.507] (II) intel(0): EDID (in hex):
    [ 81.507] (II) intel(0): 00ffffffffffff0006af3e2100000000
    [ 81.507] (II) intel(0): 21140104901f11780261959c59528f26
    [ 81.507] (II) intel(0): 21505400000001010101010101010101
    [ 81.507] (II) intel(0): 010101010101f82a409a61840c30402a
    [ 81.507] (II) intel(0): 330035ae10000018a51c409a61840c30
    [ 81.507] (II) intel(0): 402a330035ae10000018000000fe0041
    [ 81.507] (II) intel(0): 554f0a202020202020202020000000fe
    [ 81.507] (II) intel(0): 004231343052573032205631200a00d0
    [ 81.507] (II) intel(0): EDID vendor "AUO", prod id 8510
    [ 81.507] (II) intel(0): Printing DDC gathered Modelines:
    [ 81.508] (II) intel(0): Modeline "1600x900"x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
    [ 81.508] (II) intel(0): Modeline "1600x900"x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
    [ 81.508] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 81.508] (II) intel(0): Printing probed modes for output LVDS1
    [ 81.508] (II) intel(0): Modeline "1600x900"x60.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
    [ 81.508] (II) intel(0): Modeline "1600x900"x40.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
    [ 81.508] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
    [ 81.508] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
    [ 81.508] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
    [ 81.508] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
    [ 81.508] (II) intel(0): EDID for output VGA1
    [ 81.533] (II) intel(0): EDID for output HDMI1
    [ 81.573] (II) intel(0): EDID for output DP1
    [ 81.586] (II) intel(0): EDID for output HDMI2
    [ 81.600] (II) intel(0): EDID for output HDMI3
    [ 81.657] (II) intel(0): EDID for output DP2
    [ 81.657] (II) intel(0): Manufacturer: NEC Model: 67d1 Serial#: 0
    [ 81.657] (II) intel(0): Year: 2011 Week: 33
    [ 81.657] (II) intel(0): EDID Version: 1.4
    [ 81.657] (II) intel(0): Digital Display Input
    [ 81.657] (II) intel(0): 10 bits per channel
    [ 81.657] (II) intel(0): Digital interface is DisplayPort
    [ 81.657] (II) intel(0): Max Image Size [cm]: horiz.: 52 vert.: 32
    [ 81.657] (II) intel(0): Gamma: 2.20
    [ 81.657] (II) intel(0): DPMS capabilities: StandBy Suspend Off
    [ 81.657] (II) intel(0): Supported color encodings: RGB 4:4:4
    [ 81.657] (II) intel(0): First detailed timing is preferred mode
    [ 81.657] (II) intel(0): Preferred mode is native pixel format and refresh rate
    [ 81.657] (II) intel(0): redX: 0.679 redY: 0.310 greenX: 0.210 greenY: 0.686
    [ 81.657] (II) intel(0): blueX: 0.149 blueY: 0.047 whiteX: 0.313 whiteY: 0.329
    [ 81.657] (II) intel(0): Supported established timings:
    [ 81.657] (II) intel(0): 720x400@70Hz
    [ 81.657] (II) intel(0): 640x480@60Hz
    [ 81.657] (II) intel(0): 640x480@67Hz
    [ 81.657] (II) intel(0): 640x480@72Hz
    [ 81.657] (II) intel(0): 640x480@75Hz
    [ 81.657] (II) intel(0): 800x600@56Hz
    [ 81.657] (II) intel(0): 800x600@60Hz
    [ 81.657] (II) intel(0): 800x600@72Hz
    [ 81.657] (II) intel(0): 800x600@75Hz
    [ 81.657] (II) intel(0): 832x624@75Hz
    [ 81.657] (II) intel(0): 1024x768@60Hz
    [ 81.657] (II) intel(0): 1024x768@70Hz
    [ 81.657] (II) intel(0): 1024x768@75Hz
    [ 81.657] (II) intel(0): 1280x1024@75Hz
    [ 81.657] (II) intel(0): 1152x864@75Hz
    [ 81.657] (II) intel(0): Manufacturer's mask: 0
    [ 81.657] (II) intel(0): Supported standard timings:
    [ 81.657] (II) intel(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281
    [ 81.657] (II) intel(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 81.657] (II) intel(0): #2: hsize: 1400 vsize 1050 refresh: 60 vid: 16528
    [ 81.657] (II) intel(0): #3: hsize: 1360 vsize 765 refresh: 60 vid: 49291
    [ 81.657] (II) intel(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 81.657] (II) intel(0): #5: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 81.657] (II) intel(0): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 81.657] (II) intel(0): #7: hsize: 1920 vsize 1200 refresh: 60 vid: 209
    [ 81.657] (II) intel(0): Supported detailed timing:
    [ 81.657] (II) intel(0): clock: 154.0 MHz Image Size: 518 x 324 mm
    [ 81.657] (II) intel(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
    [ 81.657] (II) intel(0): v_active: 1200 v_sync: 1203 v_sync_end 1209 v_blanking: 1235 v_border: 0
    [ 81.657] (II) intel(0): Ranges: V min: 50 V max: 85 Hz, H min: 31 H max: 92 kHz, PixClock max 165 MHz
    [ 81.657] (II) intel(0): Monitor name: PA241W
    [ 81.657] (II) intel(0): Serial No: 18107120UB
    [ 81.657] (II) intel(0): EDID (in hex):
    [ 81.657] (II) intel(0): 00ffffffffffff0038a3d16700000000
    [ 81.657] (II) intel(0): 21150104b5342078e2de45ad4f35af26
    [ 81.657] (II) intel(0): 0c5054bfef8081c0818090408bc09500
    [ 81.657] (II) intel(0): a940b300d100283c80a070b023403020
    [ 81.657] (II) intel(0): 360006442100001a000000fd0032551f
    [ 81.657] (II) intel(0): 5c10000a202020202020000000fc0050
    [ 81.657] (II) intel(0): 41323431570a202020202020000000ff
    [ 81.657] (II) intel(0): 00313831303731323055420a2020004b
    [ 81.657] (II) intel(0): Printing probed modes for output DP2
    [ 81.657] (II) intel(0): Modeline "1920x1200"x60.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP)
    [ 81.657] (II) intel(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 81.657] (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 81.657] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
    [ 81.657] (II) intel(0): Modeline "1400x1050"x74.9 156.00 1400 1504 1648 1896 1050 1053 1057 1099 -hsync +vsync (82.3 kHz e)
    [ 81.657] (II) intel(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 81.657] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 81.657] (II) intel(0): Modeline "1280x1024"x85.0 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync (91.1 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 81.657] (II) intel(0): Modeline "1440x900"x84.8 157.00 1440 1544 1696 1952 900 903 909 948 -hsync +vsync (80.4 kHz e)
    [ 81.657] (II) intel(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    [ 81.657] (II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x960"x85.0 148.50 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync (85.9 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 81.657] (II) intel(0): Modeline "1360x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz)
    [ 81.657] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x800"x84.9 122.50 1280 1360 1496 1712 800 803 809 843 -hsync +vsync (71.6 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 81.657] (II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x768"x84.8 117.50 1280 1360 1496 1712 768 771 778 809 -hsync +vsync (68.6 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 81.657] (II) intel(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
    [ 81.658] (II) intel(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz e)
    [ 81.658] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 81.658] (II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 81.658] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 81.658] (II) intel(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 81.658] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 81.658] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 81.658] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 81.658] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 81.658] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 81.658] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 81.658] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 81.658] (II) intel(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (37.9 kHz e)
    [ 81.658] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz e)
    [ 81.658] (II) intel(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz e)
    [ 81.700] (II) intel(0): EDID for output DP3
    [ 81.700] (II) intel(0): Output LVDS1 connected
    [ 81.700] (II) intel(0): Output VGA1 disconnected
    [ 81.700] (II) intel(0): Output HDMI1 disconnected
    [ 81.700] (II) intel(0): Output DP1 disconnected
    [ 81.700] (II) intel(0): Output HDMI2 disconnected
    [ 81.700] (II) intel(0): Output HDMI3 disconnected
    [ 81.700] (II) intel(0): Output DP2 connected
    [ 81.700] (II) intel(0): Output DP3 disconnected
    [ 81.700] (II) intel(0): Using exact sizes for initial modes
    [ 81.700] (II) intel(0): Output LVDS1 using initial mode 1600x900
    [ 81.700] (II) intel(0): Output DP2 using initial mode 1600x900
    [ 81.700] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 81.700] (II) intel(0): Kernel page flipping support detected, enabling
    [ 81.700] (**) intel(0): Display dimensions: (310, 170) mm
    [ 81.700] (**) intel(0): DPI set to (131, 134)
    [ 81.700] (II) Loading sub module "fb"
    [ 81.700] (II) LoadModule: "fb"
    [ 81.701] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 81.701] (II) Module fb: vendor="X.Org Foundation"
    [ 81.701] compiled for 1.12.4, module version = 1.0.0
    [ 81.701] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 81.701] (II) Loading sub module "dri2"
    [ 81.701] (II) LoadModule: "dri2"
    [ 81.701] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 81.701] (II) Module dri2: vendor="X.Org Foundation"
    [ 81.701] compiled for 1.12.4, module version = 1.2.0
    [ 81.701] ABI class: X.Org Server Extension, version 6.0
    [ 81.701] (==) Depth 24 pixmap format is 32 bpp
    [ 81.702] (II) intel(0): [DRI2] Setup complete
    [ 81.702] (II) intel(0): [DRI2] DRI driver: i965
    [ 81.702] (II) intel(0): Allocated new frame buffer 1600x900 stride 6656, tiled
    [ 81.704] (II) UXA(0): Driver registered support for the following operations:
    [ 81.704] (II) solid
    [ 81.704] (II) copy
    [ 81.704] (II) composite (RENDER acceleration)
    [ 81.704] (II) put_image
    [ 81.704] (II) get_image
    [ 81.704] (==) intel(0): Backing store disabled
    [ 81.704] (==) intel(0): Silken mouse enabled
    [ 81.704] (II) intel(0): Initializing HW Cursor
    [ 81.704] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 81.707] (==) intel(0): DPMS enabled
    [ 81.707] (==) intel(0): Intel XvMC decoder enabled
    [ 81.707] (II) intel(0): Set up textured video
    [ 81.707] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [ 81.707] (II) intel(0): direct rendering: DRI2 Enabled
    [ 81.707] (==) intel(0): hotplug detection: "enabled"
    [ 82.106] (--) RandR disabled
    [ 82.107] (II) Initializing built-in extension Generic Event Extension
    [ 82.107] (II) Initializing built-in extension SHAPE
    [ 82.107] (II) Initializing built-in extension MIT-SHM
    [ 82.107] (II) Initializing built-in extension XInputExtension
    [ 82.107] (II) Initializing built-in extension XTEST
    [ 82.107] (II) Initializing built-in extension BIG-REQUESTS
    [ 82.107] (II) Initializing built-in extension SYNC
    [ 82.107] (II) Initializing built-in extension XKEYBOARD
    [ 82.107] (II) Initializing built-in extension XC-MISC
    [ 82.107] (II) Initializing built-in extension SECURITY
    [ 82.107] (II) Initializing built-in extension XINERAMA
    [ 82.107] (II) Initializing built-in extension XFIXES
    [ 82.107] (II) Initializing built-in extension RENDER
    [ 82.107] (II) Initializing built-in extension RANDR
    [ 82.107] (II) Initializing built-in extension COMPOSITE
    [ 82.107] (II) Initializing built-in extension DAMAGE
    [ 82.119] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 82.119] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 82.119] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 82.119] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 82.119] (II) AIGLX: Loaded and initialized i965
    [ 82.119] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 82.119] (II) intel(0): Setting screen physical size to 423 x 238
    [ 82.158] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 82.158] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 82.158] (II) LoadModule: "evdev"
    [ 82.159] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 82.159] (II) Module evdev: vendor="X.Org Foundation"
    [ 82.159] compiled for 1.12.3.901, module version = 2.7.3
    [ 82.159] Module class: X.Org XInput Driver
    [ 82.159] ABI class: X.Org XInput driver, version 16.0
    [ 82.159] (II) Using input driver 'evdev' for 'Power Button'
    [ 82.159] (**) Power Button: always reports core events
    [ 82.159] (**) evdev: Power Button: Device: "/dev/input/event4"
    [ 82.159] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 82.159] (--) evdev: Power Button: Found keys
    [ 82.159] (II) evdev: Power Button: Configuring as keyboard
    [ 82.159] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
    [ 82.160] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 82.160] (**) Option "xkb_rules" "evdev"
    [ 82.160] (**) Option "xkb_model" "evdev"
    [ 82.160] (**) Option "xkb_layout" "de"
    [ 82.160] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.193] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
    [ 82.193] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 82.193] (II) Using input driver 'evdev' for 'Video Bus'
    [ 82.193] (**) Video Bus: always reports core events
    [ 82.193] (**) evdev: Video Bus: Device: "/dev/input/event12"
    [ 82.193] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 82.193] (--) evdev: Video Bus: Found keys
    [ 82.193] (II) evdev: Video Bus: Configuring as keyboard
    [ 82.193] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input12/event12"
    [ 82.193] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 82.193] (**) Option "xkb_rules" "evdev"
    [ 82.193] (**) Option "xkb_model" "evdev"
    [ 82.193] (**) Option "xkb_layout" "de"
    [ 82.193] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.195] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
    [ 82.195] (II) No input driver specified, ignoring this device.
    [ 82.195] (II) This device may have been added with another device file.
    [ 82.195] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
    [ 82.195] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 82.195] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 82.195] (**) Sleep Button: always reports core events
    [ 82.195] (**) evdev: Sleep Button: Device: "/dev/input/event3"
    [ 82.195] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 82.195] (--) evdev: Sleep Button: Found keys
    [ 82.195] (II) evdev: Sleep Button: Configuring as keyboard
    [ 82.195] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event3"
    [ 82.195] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
    [ 82.195] (**) Option "xkb_rules" "evdev"
    [ 82.196] (**) Option "xkb_model" "evdev"
    [ 82.196] (**) Option "xkb_layout" "de"
    [ 82.196] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.197] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event1)
    [ 82.197] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 82.197] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
    [ 82.197] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    [ 82.197] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event1"
    [ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc01e
    [ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
    [ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    [ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
    [ 82.197] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    [ 82.197] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    [ 82.197] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
    [ 82.197] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 82.197] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 82.197] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input1/event1"
    [ 82.197] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 9)
    [ 82.197] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    [ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    [ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    [ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
    [ 82.197] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
    [ 82.197] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [ 82.197] (II) No input driver specified, ignoring this device.
    [ 82.197] (II) This device may have been added with another device file.
    [ 82.197] (II) config/udev: Adding input device Integrated Camera (/dev/input/event10)
    [ 82.197] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
    [ 82.197] (II) Using input driver 'evdev' for 'Integrated Camera'
    [ 82.197] (**) Integrated Camera: always reports core events
    [ 82.197] (**) evdev: Integrated Camera: Device: "/dev/input/event10"
    [ 82.197] (--) evdev: Integrated Camera: Vendor 0x4f2 Product 0xb221
    [ 82.197] (--) evdev: Integrated Camera: Found keys
    [ 82.197] (II) evdev: Integrated Camera: Configuring as keyboard
    [ 82.197] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input10/event10"
    [ 82.197] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
    [ 82.197] (**) Option "xkb_rules" "evdev"
    [ 82.197] (**) Option "xkb_model" "evdev"
    [ 82.197] (**) Option "xkb_layout" "de"
    [ 82.197] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.198] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event13)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event14)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event15)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event16)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event17)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event18)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event19)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.198] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event20)
    [ 82.198] (II) No input driver specified, ignoring this device.
    [ 82.198] (II) This device may have been added with another device file.
    [ 82.199] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/event5)
    [ 82.199] (**) HID 046a:0101: Applying InputClass "evdev keyboard catchall"
    [ 82.199] (II) Using input driver 'evdev' for 'HID 046a:0101'
    [ 82.199] (**) HID 046a:0101: always reports core events
    [ 82.199] (**) evdev: HID 046a:0101: Device: "/dev/input/event5"
    [ 82.199] (--) evdev: HID 046a:0101: Vendor 0x46a Product 0x101
    [ 82.199] (--) evdev: HID 046a:0101: Found keys
    [ 82.199] (II) evdev: HID 046a:0101: Configuring as keyboard
    [ 82.199] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input5/event5"
    [ 82.199] (II) XINPUT: Adding extended input device "HID 046a:0101" (type: KEYBOARD, id 11)
    [ 82.199] (**) Option "xkb_rules" "evdev"
    [ 82.199] (**) Option "xkb_model" "evdev"
    [ 82.199] (**) Option "xkb_layout" "de"
    [ 82.199] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.199] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/event7)
    [ 82.199] (**) HID 046a:0101: Applying InputClass "evdev keyboard catchall"
    [ 82.199] (II) Using input driver 'evdev' for 'HID 046a:0101'
    [ 82.199] (**) HID 046a:0101: always reports core events
    [ 82.199] (**) evdev: HID 046a:0101: Device: "/dev/input/event7"
    [ 82.199] (--) evdev: HID 046a:0101: Vendor 0x46a Product 0x101
    [ 82.199] (--) evdev: HID 046a:0101: Found 1 mouse buttons
    [ 82.199] (--) evdev: HID 046a:0101: Found scroll wheel(s)
    [ 82.199] (--) evdev: HID 046a:0101: Found relative axes
    [ 82.199] (II) evdev: HID 046a:0101: Forcing relative x/y axes to exist.
    [ 82.199] (--) evdev: HID 046a:0101: Found absolute axes
    [ 82.199] (II) evdev: HID 046a:0101: Forcing absolute x/y axes to exist.
    [ 82.199] (--) evdev: HID 046a:0101: Found keys
    [ 82.199] (II) evdev: HID 046a:0101: Configuring as mouse
    [ 82.199] (II) evdev: HID 046a:0101: Configuring as keyboard
    [ 82.199] (II) evdev: HID 046a:0101: Adding scrollwheel support
    [ 82.199] (**) evdev: HID 046a:0101: YAxisMapping: buttons 4 and 5
    [ 82.199] (**) evdev: HID 046a:0101: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 82.199] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input7/event7"
    [ 82.199] (II) XINPUT: Adding extended input device "HID 046a:0101" (type: KEYBOARD, id 12)
    [ 82.199] (**) Option "xkb_rules" "evdev"
    [ 82.199] (**) Option "xkb_model" "evdev"
    [ 82.199] (**) Option "xkb_layout" "de"
    [ 82.199] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.199] (II) evdev: HID 046a:0101: initialized for relative axes.
    [ 82.199] (WW) evdev: HID 046a:0101: ignoring absolute axes.
    [ 82.199] (**) HID 046a:0101: (accel) keeping acceleration scheme 1
    [ 82.199] (**) HID 046a:0101: (accel) acceleration profile 0
    [ 82.199] (**) HID 046a:0101: (accel) acceleration factor: 2.000
    [ 82.199] (**) HID 046a:0101: (accel) acceleration threshold: 4
    [ 82.200] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/event8)
    [ 82.200] (**) HID 046a:0101: Applying InputClass "evdev pointer catchall"
    [ 82.200] (II) Using input driver 'evdev' for 'HID 046a:0101'
    [ 82.200] (**) HID 046a:0101: always reports core events
    [ 82.200] (**) evdev: HID 046a:0101: Device: "/dev/input/event8"
    [ 82.200] (--) evdev: HID 046a:0101: Vendor 0x46a Product 0x101
    [ 82.200] (--) evdev: HID 046a:0101: Found 9 mouse buttons
    [ 82.200] (--) evdev: HID 046a:0101: Found scroll wheel(s)
    [ 82.200] (--) evdev: HID 046a:0101: Found relative axes
    [ 82.200] (--) evdev: HID 046a:0101: Found x and y relative axes
    [ 82.200] (II) evdev: HID 046a:0101: Configuring as mouse
    [ 82.200] (II) evdev: HID 046a:0101: Adding scrollwheel support
    [ 82.200] (**) evdev: HID 046a:0101: YAxisMapping: buttons 4 and 5
    [ 82.200] (**) evdev: HID 046a:0101: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 82.200] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.2/input/input8/event8"
    [ 82.200] (II) XINPUT: Adding extended input device "HID 046a:0101" (type: MOUSE, id 13)
    [ 82.200] (II) evdev: HID 046a:0101: initialized for relative axes.
    [ 82.200] (**) HID 046a:0101: (accel) keeping acceleration scheme 1
    [ 82.200] (**) HID 046a:0101: (accel) acceleration profile 0
    [ 82.200] (**) HID 046a:0101: (accel) acceleration factor: 2.000
    [ 82.200] (**) HID 046a:0101: (accel) acceleration threshold: 4
    [ 82.200] (II) config/udev: Adding input device HID 046a:0101 (/dev/input/mouse1)
    [ 82.200] (II) No input driver specified, ignoring this device.
    [ 82.200] (II) This device may have been added with another device file.
    [ 82.200] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 82.200] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 82.200] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 82.200] (**) AT Translated Set 2 keyboard: always reports core events
    [ 82.200] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 82.200] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 82.200] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 82.200] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 82.200] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 82.200] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
    [ 82.200] (**) Option "xkb_rules" "evdev"
    [ 82.200] (**) Option "xkb_model" "evdev"
    [ 82.200] (**) Option "xkb_layout" "de"
    [ 82.200] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.201] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event11)
    [ 82.201] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 82.201] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 82.201] (II) LoadModule: "synaptics"
    [ 82.201] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 82.201] (II) Module synaptics: vendor="X.Org Foundation"
    [ 82.201] compiled for 1.12.2, module version = 1.6.2
    [ 82.201] Module class: X.Org XInput Driver
    [ 82.201] ABI class: X.Org XInput driver, version 16.0
    [ 82.201] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 82.201] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 82.201] (**) Option "Device" "/dev/input/event11"
    [ 82.203] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5888
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4820
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 82.203] (**) Option "TapButton1" "1"
    [ 82.203] (**) Option "TapButton2" "2"
    [ 82.203] (**) Option "TapButton3" "3"
    [ 82.203] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 82.203] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 82.204] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event11"
    [ 82.204] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 15)
    [ 82.204] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 82.204] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
    [ 82.204] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.036
    [ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 82.204] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 82.204] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 82.204] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse2)
    [ 82.204] (II) No input driver specified, ignoring this device.
    [ 82.204] (II) This device may have been added with another device file.
    [ 82.204] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event21)
    [ 82.204] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
    [ 82.204] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
    [ 82.204] (**) TPPS/2 IBM TrackPoint: always reports core events
    [ 82.204] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event21"
    [ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
    [ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
    [ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
    [ 82.204] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
    [ 82.204] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
    [ 82.204] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
    [ 82.204] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 82.204] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input21/event21"
    [ 82.204] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 16)
    [ 82.205] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
    [ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
    [ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
    [ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
    [ 82.205] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
    [ 82.205] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse3)
    [ 82.205] (II) No input driver specified, ignoring this device.
    [ 82.205] (II) This device may have been added with another device file.
    [ 82.205] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
    [ 82.205] (II) No input driver specified, ignoring this device.
    [ 82.205] (II) This device may have been added with another device file.
    [ 82.205] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event9)
    [ 82.205] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
    [ 82.205] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
    [ 82.205] (**) ThinkPad Extra Buttons: always reports core events
    [ 82.205] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event9"
    [ 82.205] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
    [ 82.205] (--) evdev: ThinkPad Extra Buttons: Found keys
    [ 82.205] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
    [ 82.205] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input9/event9"
    [ 82.205] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 17)
    [ 82.205] (**) Option "xkb_rules" "evdev"
    [ 82.205] (**) Option "xkb_model" "evdev"
    [ 82.205] (**) Option "xkb_layout" "de"
    [ 82.205] (**) Option "xkb_variant" "nodeadkeys"
    [ 82.222] (II) intel(0): EDID vendor "AUO", prod id 8510
    [ 82.222] (II) intel(0): Printing DDC gathered Modelines:
    [ 82.222] (II) intel(0): Modeline "1600x900"x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
    [ 82.222] (II) intel(0): Modeline "1600x900"x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
    [ 82.415] (II) intel(0): Allocated new frame buffer 1920x1200 stride 7680, tiled
    [ 106.807] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 117.740] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 117.740] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 117.767] (II) intel(0): EDID vendor "AUO", prod id 8510
    [ 117.767] (II) intel(0): Printing DDC gathered Modelines:
    [ 117.767] (II) intel(0): Modeline "1600x900"x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
    [ 117.767] (II) intel(0): Modeline "1600x900"x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz e)
    [ 117.959] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    I have connect my ThinkPad per Dockingstation Displayport (I try also DVI) with an NEC PA241W. It seems arch takes the 1600x900 resolution from the Laptop :-(
    I dont know what to do makes the Kernel the Problem?
    On my second PC i have there an Nvidia when i start arch for install all are perfect on my NEC i connected it with DVI
    here is my xrandr
    [frank@bullitt ~]$ xrandr
    Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
    LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
    1600x900 60.0*+ 40.0
    1024x768 60.0
    800x600 60.3 56.2
    640x480 59.9
    VGA1 disconnected (normal left inverted right x axis y axis)
    HDMI1 disconnected (normal left inverted right x axis y axis)
    DP1 disconnected (normal left inverted right x axis y axis)
    HDMI2 disconnected (normal left inverted right x axis y axis)
    HDMI3 disconnected (normal left inverted right x axis y axis)
    DP2 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
    1920x1200 60.0*+
    1600x1200 60.0
    1680x1050 60.0
    1680x945 60.0
    1400x1050 74.9 60.0
    1600x900 60.0
    1280x1024 85.0 75.0 60.0
    1440x900 84.8 75.0 59.9
    1280x960 85.0 60.0
    1360x768 59.8 60.0
    1280x800 84.9 74.9 59.8
    1152x864 75.0
    1280x768 84.8 74.9 59.9
    1280x720 60.0
    1024x768 85.0 75.1 70.1 60.0
    1024x576 60.0
    832x624 74.6
    800x600 85.1 72.2 75.0 60.3 56.2
    848x480 60.0
    640x480 85.0 72.8 75.0 66.7 60.0
    720x400 85.0 70.1
    640x400 85.1
    640x350 85.1
    DP3 disconnected (normal left inverted right x axis y axis)
    Does anybody have the same kind of connected an Laptop with an external Monitor and knows what was the Problem?
    I like arch very much but so it doesnt make fun :-(
    I hope someone can help me
    the picture shows openbox with the Thunar maximized
    Last edited by kerasi (2012-10-12 23:12:12)

    @trilby
    i use my Laptop at home 95% and at work 5%
    so my first choice would be to have the perfect resolution on my NEC external and when i opened a window it would display there and i dont have to open my Laptop to move the screen to see it on my external or is it so that you must have opened the laptop display to move the windows?
    And when i would take it at work it would be perfect if i see it on the laptop with his resolution 1600x900
    i hope i explained it well.
    @anoknusa
    i change your config to this
    xrandr --output LVDS1 --mode 1600x900 --pos 0x900 --rotate normal --output DP2 --mode 1920x1200 --pos 0x0 --rotate normal
    when i start firefox it was displayes well on my external but when i opened xterm or thunar pcman i have to open my laptop and move from it up to the external do i make a mistake?
    anoknusa wrote:I stuck that in a script to run when I start X; if the external monitor isn't plugged in, only the laptop display is used.  This sets each screen to act as a seperate display; I can still drag windows between them if I wish, as well as assign windows to open on one screen or the other through DWM's configuration file.  As mentioned earlier, this is also the only way (I think) to get each screen to display at its native resolution.  Note that I specify the resolution for both my T520 LCD and my external monitor, and specify their positions (my external is mounted to the wall above my desk, directly above my laptop); change those as necessary.
    what has xrandr to look like for my external monitor and laptop?
    and what would the script look like for me?
    external 1920x1200
    T420 1600x900
    and thank you for your patience and have a nice day
    ps: i know iam very close to find a solution for my problem
    Last edited by kerasi (2012-10-11 00:05:55)

  • PRI monitoring problem with SNMP

    Hello
    I'm having some problems with PRI monitoring.
    I'm using cpmDS1ActiveDS0 MIB on a 3800 VoIP gateway with 4 PRI (2x2) (IOS 12.4(4)T1)
    1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0 - I can see PRI 0/0/0 total number of calls
    1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.1 - I can see PRI 0/0/1 total number of calls
    1.3.6.1.4.1.9.10.19.1.1.9.1.3.1.0 - Error
    1.3.6.1.4.1.9.10.19.1.1.9.1.3.1.1 - Error
    1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0.x - Error
    1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.1.x - Error
    The PRIs that we want to see are 0/1/0 e 0/1/1...... (bad luck!)
    Do I need to make some special configuration on the Router?

    Have you had any responses to this issue ?
    I am running into exactly the same issue and have tried everything I can find to get these individual PRI (count of channels/lines in use) statistics.
    Just for the record, here are some of the SNMP OIDs that I have tried (the ISRs do respond to them, only thing is, the data they send back is mostly rubbish...) the output below is from two separate routers, with different versions of IOS running (which is shown in the sysdescr response):
    Note that the query in red in the second router was responded to with a valid response in the FIRST router...
    All of these OIDs have been suggested at various sites online as useable SNMP OIDs for the ISR, but at other sites, they are suggested to be faulty.  I have found no definitive statement for ways to get these stats successfully on the ISR platform (which amazes me.)  Output below is using net-snmp to collect the stats.
    I welcome any suggestions as to how this can be done reliably for the ISR, and what IOS versions WILL work.  (since I am getting way different reponses to the same OIDs on the two versions below).
    You'll see that for the second (DC) router below, the values are always Zero.
    Yet I can guarantee that the ACTUAL stats are NEVER zero during the time period queried.
    Timestamp: 2010-12-27_13:56:31.73
    C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmActiveDS0s.0
    .1.3.6.1.4.1.9.10.19.1.1.4.0
    C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0
    .1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0
    C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0
    .1.3.6.1.4.1.9.10.19.1.1.3.0
    C:\usr\share\snmp\mibs>snmptranslate -On CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0
    .1.3.6.1.4.1.9.9.63.1.3.3.0
    C:\usr\share\snmp\mibs>snmptranslate -On ISDN-MIB::isdnBearerOperStatus.32
    .1.3.6.1.2.1.10.20.1.2.1.1.2.32
    From ROUTER2 - HQ:
    SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software,
    3800 Software (C3825-ADVIPSERVICESK9-M),
    Version 12.4(15)T8, RELEASE SOFTWARE (fc3)
    CISCO-POP-MGMT-MIB::cpmActiveDS0s.0 = Gauge32: 14
    CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0 = Gauge32: 14
    CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0 = Gauge32: 7
    CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0 = Gauge32: 7 interfaces
    ISDN-MIB::isdnBearerOperStatus.32 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.33 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.34 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.35 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.36 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.37 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.38 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.39 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.40 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.41 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.42 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.43 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.44 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.45 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.46 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.47 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.48 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.49 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.50 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.51 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.52 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.53 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.54 = INTEGER: idle(1)
    From ROUTER2 - DC:
    SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software,
    3800 Software (C3825-ADVIPSERVICESK9-M),
    Version 12.4(18), RELEASE SOFTWARE (fc1)
    CISCO-POP-MGMT-MIB::cpmActiveDS0s.0 = Gauge32: 0
    CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0 = Gauge32: 0
    CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0 = Gauge32: 0
    CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0 = No Such Object available on this agent at this OID
    ISDN-MIB::isdnBearerOperStatus.32 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.33 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.34 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.35 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.36 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.37 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.38 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.39 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.40 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.41 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.42 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.43 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.44 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.45 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.46 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.47 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.48 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.49 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.50 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.51 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.52 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.53 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.54 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.81 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.82 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.83 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.84 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.85 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.86 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.87 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.88 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.89 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.90 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.91 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.92 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.93 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.94 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.95 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.96 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.97 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.98 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.99 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.100 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.101 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.102 = INTEGER: idle(1)
    ISDN-MIB::isdnBearerOperStatus.103 = INTEGER: idle(1)
    Timestamp: 2010-12-27_13:56:35.02

  • Hooking up external synth. monitoring problem. HELP!!!

    so...i had been using garageband without a problem. i am having a problem with logic. i want to record the sounds off my alesis micron. i have 1/4 inch cables running through a tascam us 122. that is hooked up to my macbook pro via usb cable (just trying to be specific here as to how i have things hooked up and my settings). computer input is the us-122, the output is the headphones built in output (instead of the output on t he tascam).
    heres what i have been trying:
    i have the driver on the tascam within logic. clicked on an audio track...enable recording. when i play my keyboard i can see that its picking up a signal...but i can't hear anything. even when playing one of the tutorial tracks that come with logic i cannot hear anything. so i experiment...i record, play my synth a little (even though i can't hear it) and stop. it records the waveform. when i try to play back, i can't hear it. when i switch the driver to direct line...only then can i hear what i records (i cannot hear my synth when the driver is set to direct line, no signal comes through obviously). my initial thought was that there is a monitor play thru button somewhere like garage band. the software monitoring was clicked the whole time. i have no idea what i'm doing wrong. can anyone help me?
    sorry for being longwinded here but im trying to give as much information as possible.

    With no offense intended: your questions seem to indicate confusion on an extremely basic level that's probably quite beyond the scope of this forum.
    It sounds like you need an introduction to basic MIDI, and the differences between MIDI and audio.
    http://www.tweakheadz.com/howto_get_started_withmidi.html
    Basically, MIDI is the equivalent of sheet music - it tells the performing instrument which note(s) to play at what time. What the actual audio generated sounds like is of no concern to MIDI - that depends on the instrument used.
    The audio is the equivalent of a CD recording of the sheet music being performed. It's a completely different medium, as it were.
    Where it gets confusing is in devices that do both, such as the Kaoss pad: you can use it as a MIDI controller to influence the parameters of the synthesizer, AND you can use it to mangle the audio that comes out of the synthesizer (or anywhere else).
    You're going to want to hook the Kaoss pad up via MIDI and audio; the trick is using the Presonus Firebox's mixer/routing application to route the incoming/outgoing audio to your monitor system and into the Kaoss pad at the same time (so as to be able to add FX from the Kaoss pad).
    The audio routing will probably be easier to setup for an inexperienced user/better to control with an external mixer, though the Presonus is certainly potent enough to get it all done in software. But how to set that up really depends on what exactly you're looking to be doing.
    It's easier to fiddle around with cables and a hardware mixer if you're just learning.

Maybe you are looking for

  • 4th generation ipod nano not working

    All of the sudden my 4th generation, 8GB ipod nano isn't working. I had a 2004 G4 aluminum Powerbook that started to go so I bought a refurbished Macbook Pro a couple weeks ago. On my Powerbook, the screen all of the sudden went dark. I researched wh

  • Usage of FM TMS_MGR_READ_TRANSPORT_QUEUE

    Hi there, i want to use the function module TMS_MGR_READ_TRANSPORT_QUEUE but unfortunately it has no documentation and i do not want to change any data. do i change any data if i keep the parameters IV_CLEAR_LOCKS and IV_UPDATE_CACHE at their default

  • Organization level control on Role

    Dear security gurus. I have 2 business roles in company and 2 subsidiaries under HQ. Each company have - Accout clerk - Account manager HQ's clerk&manager: be able to check all company's data. Subsidiary's clerk&manager: be able to check ONLY their o

  • Deployment with minimal user interaction

    We are interested in deploying iPads to users in our company, but we want to do so with minimal user interaction. From what I can tell the best way to do this would be to sync our iPads with one computer and have that computer's iTunes manage the app

  • [kde-unstable] - ... exists in both 'kdeaccessibility-iconthemes' and

    Hi, I've just tried to install the kde-meta package, and I'm getting errors about files existing in both kdeaccessibility-iconthemes and kdeartwork-iconthemes: /usr/share/icons/mono/scalable/status/dialog-warning.svgz exists in both 'kdeaccessibility