MXI-3 interface not detected?

Hello to you all,
I was using PXI/PCI 8335 with PXI 1000B chassis. Everytime I run the MXI-3 optimization it says MXI-interface not detected.
I checked the LEDs.
For PXI-8335, the PWR and RX were both solid on, one green and the other orange. For PCI-8335, the PWR and TX (nor sure it's TX or RX, just the one in the same row with PWR) were both solid on, one green and the other orange.
No LINK light.
The whole system was powered in proper sequence and the fibre optic cable was fine.
So there seems to be something wrong with the cards.
I was wondering is there any way to know particularly which one of PXI-8335 and PCI-8335 doesn't work well without replacing them one by one, since I don't have any extras?
Like, does the LED tell other information except they are not linked?
Thank you in advance.
Yaqiong

Yaqiong,
In general you can't differentiate between a bad transmitter on one side or a bad receiver on the other, so it's often hard to tell which side is bad.
In your case, it sounds like one side or the other has a broken transceiver.  Power and RX on both sides means the boards aren't communicating at all, meaning a transceiver is bad, or a cable is bad in both directions, or a cable is not plugged in or is plugged in backwards.  If you power it up without a cable you should get the same LED behavior -- PWR and RX, the two LEDs next to each other.
If that's the case (same LEDs without a cable as with a cable), you should be able to tell which card is bad if you connect both ends of a half cable to one card (a loopback).  On a working card connecting RX to TX will "link" to itself according to the LEDs (at least it did for me on both the PCI and PXI card).  On a broken card you'll get something else.
- Robert

Similar Messages

  • VXI-MXI-2 is not detected in VIC / VISA panel

    Hello,
    I have a VXI work station (VXI-MXI-2)  with Windows XP (PCI-MXI-2). I had installed the nivxi 3.1.1.
    The VXI-MXI-2 card is not detected / showing in the VIC panel. Only the PCI-MXI-2 is detected as VXI0 (PCI-MXI-2).
    No error occoured while running the Resman. It was completed successfully.
    Regards,
    Perumal.V

    My Friend.
                I understood your frustration totally. I got the same problem. There is not much you can do about it. Probably you won’t like my solution either. It is very painful experiences. Are you ready? Here is the solution.
                            Reinstall all of your software.
                            Yes, Reinstall it. The whole thing, LabVIEW, Drivers, and etc. But you must uninstall first.
                            If it does not work, change the computer.
                            The system should run and found the device. It may takes you a couple of days to do it. But it should work.
                            I ran into this issue a few times. Every time I end it up uninstall and reinstall every thing. And it runs without any problems.

  • Bug: Startup Parameter not detected on Interface scenario generation

    Hi,
    I'd like to report a bug in ODI when generating a scenario from an Interface.
    When a variable is used in the Diagram tab there is no problem, so this can be the work around.
    However when one uses a variable on the flow tab in one of the KM options, you'll find that variable is not detected when generating a scenario from this interface.
    The KM I'm using is: IKM SQL to Hyperion Essbase (DATA)
    Here the RULE_FILE option is set to: #vDataLoadRule -- (Also tried '#{project_name}.vDataLoadRule' )
    Hope this can be solved in new release, so one is not forced to make non sense where clauses in the interface.
    How to use the work around?
    If you do not yet have a filter on your source, then:
    Create a Filter on your source data store, by dragging and dropping a field.
    in the filter set something like this:
    {DataStore}.{DataField} = {DataStore}.{DataField}
    and #{myVariable} = #{myVariable}
    Otherwise, just add the following to an existing source filter:
    and #{myVariable} = #{myVariable}
    This will create an where clause on your source, which is always true.
    Hope this helps!
    Rudy

    Hi John, thanks for your quick reply.
    Doing it dynamicaly is my way to build stuff.
    So I've the situation where need to load data to several cubes (more are coming).
    I want my life to be easy (as there is more to life...) and so I've created a package that does the following:
    Get details of the cube that needs to be processed and process it. The benefit is, that I only need to create a new interface (not a whole package) and register it in my essbase metadata table when a new cube is built.
    Of course I can drag the Interface into that package, but then that package is only capable of running that interface, since there is no way to set a variable Interface name.
    Hence, I need the interface as an scenario, so that I can make it dynamic.
    I have a package that initializes the variables e.g. #vDataLoadRule, #vDataLoadName, #vDataLoadVersion, Which I get from my sql table that holds my Essbase Database metadata ( Server, Application, DatabaseName, DataLoadName, DataLoadVersion, DataLoadRule) and then runs the scenario. The DataLoadName and DataLoadVersion are name and version of the Scenario (Interface) that needs to be processed.
    So with that as a background, I'd like to have dynamic Interfaces.
    The problem is that when you use a variable in the diagram tab of the interface it's perfectly detected when you generate a scenario of the interface, however when you use the variable in the flow tab, it's not detected on scenario generation.
    To me that's a bug.
    Cheers!

  • OVM Server 2.2.1 in a ProLiant BL680c G7 did not detect networks interfaces

    Hello everybody
    I just installed OVM Server in a HP ProLiant BL680c G7 and the installation finish. But the network interfaces was not detected. (The installation skip the network steps)
    The Server have 24 network interfaces (FlexFabric Embedded Ethernet)
    Any idea in order to recognize network interfaces??
    greetings

    Hi,
    try using OVM 2.2.2 which was released a week ago. (edelivery.oracle.com/linux)
    A lot of drivers were updated, maybe now your network cards are also detected.
    Regards
    Sebastian

  • TS1521 Garageband not detecting my microphone/usb audio interface

    Hello all.
         This is what i have here: an old but barely used Tascam US-122L USB 2.0 Audio/MIDI Interface with a Tascam LD-74 phantom mic, which both of them work. The problem is garageband is not detecting them. My interface is plugged into the usb port is telling me my mic is picking up sound.
         But when i go to system preferences, then sound, input,  it only has Internal microphone and Line in with the type being microphone port and audio line-in port respectively. The input volume for the Line in is in the middle but is showing no signs of sound being picked up.
         When i go to garageband, preferences, Audio/MIDI, it only gives me for microphone built-in mic and built-in input. Of course on the track info pane where you select mono 1 built-in input, mono 2 built-in input, Stereo 1/2 built-in input, there is no sign of my mic or interface. I've searched this question over and over and still can't find the answer. Help please.

    I tried that once and the mac told me that they weren't recognized, couldn't be unzipped or whatever. But I just downloaded the most recent driver and it worked.

  • MXi-3 card is not detecting

    hello,
    when i run mxi-3 optimization code, dialog box indicate that mxi ink is not proper. But, in PXI-MXI3 controller and pci-MXi controller, link led is glowing continousuly.total 3 led's are glowing continously named them as, power,link,Tx.plz provie the solution.
    regrads
    chandu

    Hey Chandhuu,
    I found a great KB Article: MXI-3 and MXI-4 Troubleshooting Guide. It seems like they cover the issue you're mentioning exactly under problem 3. A good test would be to try another computer if possible, or try to update the BIOS of the computer.
    Regards,
    Nick D.

  • Communicating with modules in PXI-1042 via MXI-3 interface, all I get is PXI0::MEMACC appearing in MAX. I have OEM modules in the chassis, should these be displayed?

    I have a PXI-1042 with PXI-MXI-3 interface kit. In the chassis I have inserted an OEM PXI module. When I run MAX, all I see is PXI System->PXI Bus 0->PXI0::MEMACC. Is this correct? How do I see the other modules?

    Darren,
    The only PXI modules that show up under the PXI System option in MAX are those cards that are registered with NI-PAL or NI-VISA. For 3rd party cards, it depends on how their particular driver functions. If the vendor creates their drivers based on NI-VISA, then the device will show up in MAX.
    If the vendor created a Windows-specific driver, then there is no way that NI-VISA can find any information on the device, nor can it communicate with it. An example of this is a CompactPCI SCSI or Ethernet card, which is supported by a driver that is native to Windows. NI-VISA does not detect such devices.
    It is important that you contact the manufacturer of your 3rd party modules and find out if they are NI-VISA complient devices.
    Regards,
    Andrew Mier
    au
    Applications Engineer
    National Instruments

  • Ipod touch 5th gen not detected in mac os 10.8.2

    Hi
    My ipod touch 5 gen with ios 6.0.2 is not detected in mac mini with 10.8.2. It is working with all other PCs and mac except my mac. I tried all the posible trobleshootings found in the internet, still it is not working.

    Hi Bruce, and a warm welcome to the forums!
    I can't find the PCI card, just the PCIe card...
    http://www.sonnettech.com/support/kb/kb.php?cat=164&expand=a3_a2b405&action=b490#b490
    http://www.amazon.com/Presto-Gigabit-Ethernet-PCIe-Card/dp/B0017K6BR8
    But on a hunch, System Preferences>Network, unlock the Lock if need be, see if you get New Port Detected, or click the little + icon and see if you can add Ethernet.
    If it works & that is the Interface used for Internet, click on the little Gear icon>Set Service Order, drag Ethernet to the top.

  • HP installer will not detect networked LaserJet MFP M1536dnf just on some PCs

    Hello,
    this printer/scanner was working fine (printer still works fine via a Windows print server). Then scanning (via network) stopped working on one PC (Windows 7).
    Tried to uninstall drivers / HP software and reboot. Then tried to install again - HP Installer will not detect printer on the network no matter what. I can ping the IP of this printer, access its web interface without any issues on the same PC. Tried specifying IP address in the installer - does not detect, the same issue with MAC address. 
    Had a Windows 8 machine with drivers / software installed on it, tested - scanning still worked fine on that PC. Tried to remove HP software to see if problem will appear. And it did! I cannot install the same software package which I still had in downloads - it will NOT detect the printer on network.
    Upgraded printer firmware - no change, even though I don't expect this to be a printer issue as it worked fine until I have uninstalled software on this W8 machine.
    Tried using HP Scan & Print doctor. That thing doesn't see printer/scanner installed and only suggest to download and install software which is not helpfull at all.
    I also tried extracting HP installation files and finding *.inf files which could be used to add scanner via Windows directly, but haven't succeded with that (I would also be not sure how to specify network IP address in such a case anyway).
    Any help is MUCH appreciated. We are kind of stuck...
    Thanks!

    Hi,
    Run some diagnostics and see if any issues are discovered.
    There have been reported issues with the NVIDIA 650 with some of the HP PCs. Additionally, most models of the NVIDIA 650 require a 400 watt power supply as the minimum and some models require a PCI six (6) pin power connector which the 300 watt power supply in your PC is not provisioned.
    There is a BIOS update posted for your PC so you might want to consider installing that update.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • PXI-8532 DNET card is not detected in MAX

    Hi all,
    I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
    Slot 1= PXI-8106 Controller
    Slot 2= PXI-6259 card(AI)
    Slot 3= PXI-6509 card(DI,DO)
    Slot 4= PXI-8532 Card(DNET)
    In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
    PXI-6259 (PXI1 Slot2)
    PXI-6509 (PXI1 Slot3)
    The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
    In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
    Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
    DNET driver version - 1.6.4
    Thanks,
    Raja
    Solved!
    Go to Solution.

    Dirk,
    Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
    New driver - NI-Industrial Communications for DeviceNet 2.1
    But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
    By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
    After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
    Old DNET function palette - Instrument IO>>DNET
    New DNET function palette - Industrial Communications
    My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
    With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
    Error Code ="-1074388957" - The Interface is invalid or unknown.  Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
    With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
    1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
    2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
    Thanks,
    Raja
    LV 2009, Windows XP

  • External monitor not detected on Thinkpad W530 intel-virtual-output

    I'm having problems with connecting my ThinkPad W530 to external monitors since a few months. I'm using NVIDIA Optimus and bumblebee/optirun since the VGA and Mini DisplayPort connectors are only wired to the NVIDIA card om this laptop. For a long time I have executed:
    $ optirun true
    $ intel-virtual-output
    Then I have started the Screens GUI tool in Gnome to setup the placement of the external screen but now the external screen is not present in the GUI tool and xrandr gives me:
    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
    LVDS1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
    1920x1080 60.00*+ 50.00
    1400x1050 59.98
    1280x1024 60.02
    1280x960 60.00
    1024x768 60.00
    800x600 60.32 56.25
    640x480 59.94
    VGA1 disconnected (normal left inverted right x axis y axis)
    VIRTUAL1 disconnected (normal left inverted right x axis y axis)
    If I select "Discrete mode" and select startup screen as VGA in the BIOS the BIOS and the Grub screens shows on the external monitor but the screen locks on the screen that shows that the system is booting with the linux-ck kernel. This has never worked for me in Arch Linux so that is no surprise. In Ubuntu everything everything worked fine the last time I tried.
    How can I debug this? Why is the external screen not detected any more?

    Thanks, I am not sure exactly how to read the logs but I cannot find anything that is obviously wrong
    Below is my log with an external screen connected via Mini DisplayPort and after running:
    $ optirun true
    $ intel-virtual-output
    a few times, no more logs seem to be added when I connect/disconnect the monitor or when I run the above two commands more times.
    ╰─➤ cat /var/log/Xorg.0.log 1 ↵
    [ 2.616]
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 2.616] X Protocol Version 11, Revision 0
    [ 2.616] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 2.616] Current Operating System: Linux ethuil 3.13.9-1-ck #1 SMP PREEMPT Fri Apr 4 15:50:10 EDT 2014 x86_64
    [ 2.616] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-ck root=UUID=25086a9b-a542-4018-9f71-4f492f09be91 rw quiet rcutree.rcu_idle_gp_delay=1
    [ 2.616] Build Date: 09 January 2014 08:47:24AM
    [ 2.616]
    [ 2.616] Current version of pixman: 0.32.4
    [ 2.616] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2.616] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2.616] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 14 22:09:08 2014
    [ 2.624] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2.624] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 2.627] (==) No Layout section. Using the first Screen section.
    [ 2.627] (==) No screen section available. Using defaults.
    [ 2.627] (**) |-->Screen "Default Screen Section" (0)
    [ 2.627] (**) | |-->Monitor "<default monitor>"
    [ 2.628] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 2.628] (==) Automatically adding devices
    [ 2.628] (==) Automatically enabling devices
    [ 2.628] (==) Automatically adding GPU devices
    [ 2.638] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 2.638] Entry deleted from font path.
    [ 2.638] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 2.638] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 2.638] Entry deleted from font path.
    [ 2.638] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 2.638] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/
    [ 2.638] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2.638] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2.638] (II) Loader magic: 0x804c80
    [ 2.638] (II) Module ABI versions:
    [ 2.638] X.Org ANSI C Emulation: 0.4
    [ 2.638] X.Org Video Driver: 15.0
    [ 2.638] X.Org XInput driver : 20.0
    [ 2.638] X.Org Server Extension : 8.0
    [ 2.639] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 3.588] (--) PCI:*(0:0:2:0) 8086:0166:17aa:21f5 rev 9, Mem @ 0xf1400000/4194304, 0xe0000000/268435456, I/O @ 0x00006000/64
    [ 3.588] (--) PCI: (0:1:0:0) 10de:0ffb:17aa:21f5 rev 161, Mem @ 0xf0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
    [ 3.588] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 3.589] Initializing built-in extension Generic Event Extension
    [ 3.589] Initializing built-in extension SHAPE
    [ 3.589] Initializing built-in extension MIT-SHM
    [ 3.589] Initializing built-in extension XInputExtension
    [ 3.589] Initializing built-in extension XTEST
    [ 3.589] Initializing built-in extension BIG-REQUESTS
    [ 3.589] Initializing built-in extension SYNC
    [ 3.589] Initializing built-in extension XKEYBOARD
    [ 3.589] Initializing built-in extension XC-MISC
    [ 3.589] Initializing built-in extension SECURITY
    [ 3.589] Initializing built-in extension XINERAMA
    [ 3.589] Initializing built-in extension XFIXES
    [ 3.589] Initializing built-in extension RENDER
    [ 3.589] Initializing built-in extension RANDR
    [ 3.589] Initializing built-in extension COMPOSITE
    [ 3.589] Initializing built-in extension DAMAGE
    [ 3.589] Initializing built-in extension MIT-SCREEN-SAVER
    [ 3.589] Initializing built-in extension DOUBLE-BUFFER
    [ 3.589] Initializing built-in extension RECORD
    [ 3.589] Initializing built-in extension DPMS
    [ 3.589] Initializing built-in extension Present
    [ 3.590] Initializing built-in extension DRI3
    [ 3.590] Initializing built-in extension X-Resource
    [ 3.590] Initializing built-in extension XVideo
    [ 3.590] Initializing built-in extension XVideo-MotionCompensation
    [ 3.590] Initializing built-in extension XFree86-VidModeExtension
    [ 3.590] Initializing built-in extension XFree86-DGA
    [ 3.590] Initializing built-in extension XFree86-DRI
    [ 3.590] Initializing built-in extension DRI2
    [ 3.590] (II) "glx" will be loaded by default.
    [ 3.590] (II) LoadModule: "dri2"
    [ 3.590] (II) Module "dri2" already built-in
    [ 3.590] (II) LoadModule: "glamoregl"
    [ 3.593] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 3.615] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 3.615] compiled for 1.15.0, module version = 0.6.0
    [ 3.615] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 3.615] (II) LoadModule: "glx"
    [ 3.617] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 3.618] (II) Module glx: vendor="X.Org Foundation"
    [ 3.618] compiled for 1.15.0, module version = 1.0.0
    [ 3.618] ABI class: X.Org Server Extension, version 8.0
    [ 3.618] (==) AIGLX enabled
    [ 3.618] Loading extension GLX
    [ 3.618] (==) Matched intel as autoconfigured driver 0
    [ 3.618] (==) Matched intel as autoconfigured driver 1
    [ 3.618] (==) Matched modesetting as autoconfigured driver 2
    [ 3.618] (==) Matched fbdev as autoconfigured driver 3
    [ 3.618] (==) Matched vesa as autoconfigured driver 4
    [ 3.618] (==) Assigned the driver to the xf86ConfigLayout
    [ 3.618] (II) LoadModule: "intel"
    [ 3.618] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 3.623] (II) Module intel: vendor="X.Org Foundation"
    [ 3.623] compiled for 1.15.0, module version = 2.99.911
    [ 3.623] Module class: X.Org Video Driver
    [ 3.623] ABI class: X.Org Video Driver, version 15.0
    [ 3.623] (II) LoadModule: "modesetting"
    [ 3.624] (WW) Warning, couldn't open module modesetting
    [ 3.624] (II) UnloadModule: "modesetting"
    [ 3.624] (II) Unloading modesetting
    [ 3.624] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 3.624] (II) LoadModule: "fbdev"
    [ 3.624] (WW) Warning, couldn't open module fbdev
    [ 3.624] (II) UnloadModule: "fbdev"
    [ 3.624] (II) Unloading fbdev
    [ 3.624] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 3.624] (II) LoadModule: "vesa"
    [ 3.624] (WW) Warning, couldn't open module vesa
    [ 3.624] (II) UnloadModule: "vesa"
    [ 3.624] (II) Unloading vesa
    [ 3.624] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 3.624] (II) intel: Driver for Intel(R) 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
    [ 3.624] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
    [ 3.624] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
    [ 3.624] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
    [ 3.624] (++) using VT number 1
    [ 3.625] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000
    [ 3.625] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 3.625] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 3.625] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 3.625] (==) intel(0): RGB weight 888
    [ 3.625] (==) intel(0): Default visual is TrueColor
    [ 3.625] (**) intel(0): Framebuffer tiled
    [ 3.625] (**) intel(0): Pixmaps tiled
    [ 3.625] (**) intel(0): "Tear free" disabled
    [ 3.625] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 3.625] (II) intel(0): Output LVDS1 has no monitor section
    [ 3.625] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
    [ 3.625] (II) intel(0): Output VGA1 has no monitor section
    [ 3.625] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 3.625] (--) intel(0): Output LVDS1 using initial mode 1920x1080 on pipe 0
    [ 3.625] (==) intel(0): DPI set to (96, 96)
    [ 3.625] (II) Loading sub module "dri2"
    [ 3.625] (II) LoadModule: "dri2"
    [ 3.625] (II) Module "dri2" already built-in
    [ 3.625] (==) Depth 24 pixmap format is 32 bpp
    [ 3.627] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend
    [ 3.627] (==) intel(0): Backing store enabled
    [ 3.627] (==) intel(0): Silken mouse enabled
    [ 3.628] (II) intel(0): HW Cursor enabled
    [ 3.628] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 3.628] (==) intel(0): DPMS enabled
    [ 3.628] (II) intel(0): [DRI2] Setup complete
    [ 3.628] (II) intel(0): [DRI2] DRI driver: i965
    [ 3.628] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 3.628] (II) intel(0): direct rendering: DRI2 Enabled
    [ 3.628] (==) intel(0): hotplug detection: "enabled"
    [ 3.628] (--) RandR disabled
    [ 3.650] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 3.650] (II) AIGLX: enabled GLX_ARB_create_context
    [ 3.650] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 3.650] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 3.650] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 3.650] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 3.650] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 3.650] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 3.650] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 3.650] (II) AIGLX: Loaded and initialized i965
    [ 3.650] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 3.652] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 3.665] (II) intel(0): Setting screen physical size to 508 x 285
    [ 3.732] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 3.732] (**) Power Button: Applying InputClass "system-keyboard"
    [ 3.732] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 3.732] (II) LoadModule: "evdev"
    [ 3.732] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 3.734] (II) Module evdev: vendor="X.Org Foundation"
    [ 3.734] compiled for 1.15.0, module version = 2.8.2
    [ 3.734] Module class: X.Org XInput Driver
    [ 3.734] ABI class: X.Org XInput driver, version 20.0
    [ 3.734] (II) Using input driver 'evdev' for 'Power Button'
    [ 3.734] (**) Power Button: always reports core events
    [ 3.734] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 3.734] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 3.734] (--) evdev: Power Button: Found keys
    [ 3.734] (II) evdev: Power Button: Configuring as keyboard
    [ 3.734] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
    [ 3.734] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 3.734] (**) Option "xkb_rules" "evdev"
    [ 3.734] (**) Option "xkb_model" "pc104"
    [ 3.734] (**) Option "xkb_layout" "se"
    [ 3.754] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
    [ 3.754] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.754] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.754] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.754] (**) Video Bus: always reports core events
    [ 3.754] (**) evdev: Video Bus: Device: "/dev/input/event13"
    [ 3.754] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.754] (--) evdev: Video Bus: Found keys
    [ 3.754] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input15/event13"
    [ 3.754] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 3.754] (**) Option "xkb_rules" "evdev"
    [ 3.754] (**) Option "xkb_model" "pc104"
    [ 3.754] (**) Option "xkb_layout" "se"
    [ 3.754] (II) config/udev: Adding input device Video Bus (/dev/input/event14)
    [ 3.754] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.754] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.754] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.754] (**) Video Bus: always reports core events
    [ 3.754] (**) evdev: Video Bus: Device: "/dev/input/event14"
    [ 3.754] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.754] (--) evdev: Video Bus: Found keys
    [ 3.754] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input16/event14"
    [ 3.754] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 3.754] (**) Option "xkb_rules" "evdev"
    [ 3.754] (**) Option "xkb_model" "pc104"
    [ 3.754] (**) Option "xkb_layout" "se"
    [ 3.755] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
    [ 3.755] (II) No input driver specified, ignoring this device.
    [ 3.755] (II) This device may have been added with another device file.
    [ 3.755] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 3.755] (**) Sleep Button: Applying InputClass "system-keyboard"
    [ 3.755] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 3.755] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 3.755] (**) Sleep Button: always reports core events
    [ 3.755] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 3.755] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 3.755] (--) evdev: Sleep Button: Found keys
    [ 3.755] (II) evdev: Sleep Button: Configuring as keyboard
    [ 3.755] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event2"
    [ 3.755] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 3.755] (**) Option "xkb_rules" "evdev"
    [ 3.755] (**) Option "xkb_model" "pc104"
    [ 3.755] (**) Option "xkb_layout" "se"
    [ 3.755] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 3.755] (II) config/udev: Adding input device Integrated Camera (/dev/input/event6)
    [ 3.756] (**) Integrated Camera: Applying InputClass "system-keyboard"
    [ 3.756] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
    [ 3.756] (II) Using input driver 'evdev' for 'Integrated Camera'
    [ 3.756] (**) Integrated Camera: always reports core events
    [ 3.756] (**) evdev: Integrated Camera: Device: "/dev/input/event6"
    [ 3.756] (--) evdev: Integrated Camera: Vendor 0x4f2 Product 0xb2eb
    [ 3.756] (--) evdev: Integrated Camera: Found keys
    [ 3.756] (II) evdev: Integrated Camera: Configuring as keyboard
    [ 3.756] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input8/event6"
    [ 3.756] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
    [ 3.756] (**) Option "xkb_rules" "evdev"
    [ 3.756] (**) Option "xkb_model" "pc104"
    [ 3.756] (**) Option "xkb_layout" "se"
    [ 3.756] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.756] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.756] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event10)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.756] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event9)
    [ 3.756] (II) No input driver specified, ignoring this device.
    [ 3.756] (II) This device may have been added with another device file.
    [ 3.757] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event8)
    [ 3.757] (II) No input driver specified, ignoring this device.
    [ 3.757] (II) This device may have been added with another device file.
    [ 3.757] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 3.757] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
    [ 3.757] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 3.757] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 3.757] (**) AT Translated Set 2 keyboard: always reports core events
    [ 3.757] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 3.757] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 3.757] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 3.757] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 3.757] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 3.757] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
    [ 3.757] (**) Option "xkb_rules" "evdev"
    [ 3.757] (**) Option "xkb_model" "pc104"
    [ 3.757] (**) Option "xkb_layout" "se"
    [ 3.757] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
    [ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 3.757] (II) LoadModule: "synaptics"
    [ 3.757] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 3.758] (II) Module synaptics: vendor="X.Org Foundation"
    [ 3.758] compiled for 1.15.0, module version = 1.7.4
    [ 3.758] Module class: X.Org XInput Driver
    [ 3.758] ABI class: X.Org XInput driver, version 20.0
    [ 3.758] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 3.758] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.758] (**) Option "Device" "/dev/input/event12"
    [ 3.783] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 3.783] (**) Option "TapButton1" "1"
    [ 3.783] (**) Option "TapButton2" "2"
    [ 3.783] (**) Option "TapButton3" "3"
    [ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.783] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.793] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event12"
    [ 3.793] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 3.793] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.793] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 3.793] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 3.794] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [ 3.794] (II) No input driver specified, ignoring this device.
    [ 3.794] (II) This device may have been added with another device file.
    [ 3.794] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event4)
    [ 3.794] (**) ThinkPad Extra Buttons: Applying InputClass "system-keyboard"
    [ 3.794] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
    [ 3.794] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
    [ 3.794] (**) ThinkPad Extra Buttons: always reports core events
    [ 3.794] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event4"
    [ 3.794] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
    [ 3.794] (--) evdev: ThinkPad Extra Buttons: Found keys
    [ 3.795] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
    [ 3.795] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input5/event4"
    [ 3.795] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
    [ 3.795] (**) Option "xkb_rules" "evdev"
    [ 3.795] (**) Option "xkb_model" "pc104"
    [ 3.795] (**) Option "xkb_layout" "se"
    [ 3.799] (II) config/udev: removing device SynPS/2 Synaptics TouchPad
    [ 3.824] (II) UnloadModule: "synaptics"
    [ 3.824] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 3.824] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 3.824] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.824] (**) Option "Device" "/dev/input/event12"
    [ 3.844] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 3.844] (**) Option "TapButton1" "1"
    [ 3.844] (**) Option "TapButton2" "2"
    [ 3.844] (**) Option "TapButton3" "3"
    [ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.844] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 3.854] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event12"
    [ 3.854] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 3.854] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 3.854] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 3.854] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 3.855] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 /dev/dri/card0
    [ 3.855] xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    [ 3.855] failed to find screen to remove
    [ 3.855] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 3.855] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (null)
    [ 3.855] (II) config/udev: removing device Video Bus
    [ 3.863] (II) evdev: Video Bus: Close
    [ 3.863] (II) UnloadModule: "evdev"
    [ 3.863] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
    [ 3.863] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.863] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.863] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.863] (**) Video Bus: always reports core events
    [ 3.863] (**) evdev: Video Bus: Device: "/dev/input/event13"
    [ 3.863] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.863] (--) evdev: Video Bus: Found keys
    [ 3.863] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.863] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input15/event13"
    [ 3.863] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 3.863] (**) Option "xkb_rules" "evdev"
    [ 3.863] (**) Option "xkb_model" "pc104"
    [ 3.863] (**) Option "xkb_layout" "se"
    [ 3.863] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (null)
    [ 3.863] (II) config/udev: removing device Video Bus
    [ 3.870] (II) evdev: Video Bus: Close
    [ 3.870] (II) UnloadModule: "evdev"
    [ 3.870] (II) config/udev: Adding input device Video Bus (/dev/input/event14)
    [ 3.870] (**) Video Bus: Applying InputClass "system-keyboard"
    [ 3.870] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 3.870] (II) Using input driver 'evdev' for 'Video Bus'
    [ 3.870] (**) Video Bus: always reports core events
    [ 3.870] (**) evdev: Video Bus: Device: "/dev/input/event14"
    [ 3.870] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 3.870] (--) evdev: Video Bus: Found keys
    [ 3.870] (II) evdev: Video Bus: Configuring as keyboard
    [ 3.870] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input16/event14"
    [ 3.870] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 3.870] (**) Option "xkb_rules" "evdev"
    [ 3.870] (**) Option "xkb_model" "pc104"
    [ 3.870] (**) Option "xkb_layout" "se"
    [ 4.540] (II) intel(0): EDID vendor "LEN", prod id 16562
    [ 4.540] (II) intel(0): Printing DDC gathered Modelines:
    [ 4.540] (II) intel(0): Modeline "1920x1080"x0.0 139.00 1920 1980 2028 2050 1080 1090 1100 1130 -hsync -vsync (67.8 kHz eP)
    [ 4.540] (II) intel(0): Modeline "1920x1080"x0.0 115.83 1920 1980 2028 2050 1080 1090 1100 1130 -hsync -vsync (56.5 kHz e)
    [ 7.358] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event15)
    [ 7.358] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
    [ 7.358] (**) TPPS/2 IBM TrackPoint: Applying InputClass "Trackpoint Wheel Emulation"
    [ 7.358] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
    [ 7.358] (**) TPPS/2 IBM TrackPoint: always reports core events
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event15"
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
    [ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
    [ 7.358] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
    [ 7.358] (**) Option "Emulate3Buttons" "false"
    [ 7.358] (**) Option "EmulateWheel" "true"
    [ 7.358] (**) Option "EmulateWheelButton" "2"
    [ 7.358] (**) Option "YAxisMapping" "4 5"
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
    [ 7.358] (**) Option "XAxisMapping" "6 7"
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: XAxisMapping: buttons 6 and 7
    [ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 7.358] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input14/event15"
    [ 7.358] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 14)
    [ 7.358] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
    [ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
    [ 7.359] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
    [ 7.359] (II) No input driver specified, ignoring this device.
    [ 7.359] (II) This device may have been added with another device file.
    [ 20245.335] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 21030.923] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 21196.939] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 21209.255] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 24416.533] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 26177.657] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none

  • Saitek PS1000 gamepad not working (buttons not detected)

    I'm having an issue with a Saitek PS1000 gamepad which is correctly detected as /dev/input/js0, however only the joysticks are recognized, the buttons are not detected.
    cat /dev/input/js0 outputs garbage whenever I move one of the joysticks, but nothing when I press any button.
    The same with jstest or with the configuration panel under kde (both joystick work, but no output when pressing any button).
    Kernel logging when pluggin in the gamepad (from /var/log/message) :
    Aug 22 17:28:59 antoine kernel: usbcore: registered new interface driver hiddev
    Aug 22 17:28:59 antoine kernel: input: Jess Technology Co., Ltd. PS1000 Dual AnaloguePad as /devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.0/input/input5
    Aug 22 17:28:59 antoine kernel: generic-usb 0003:06A3:0621.0001: input,hidraw0: USB HID v1.11 Gamepad [Jess Technology Co., Ltd. PS1000 Dual AnaloguePad] on usb-0000:00:02.0-7/input0
    Aug 22 17:28:59 antoine kernel: usbcore: registered new interface driver usbhid
    Aug 22 17:28:59 antoine kernel: usbhid: USB HID core driver

    I'm having an issue with a Saitek PS1000 gamepad which is correctly detected as /dev/input/js0, however only the joysticks are recognized, the buttons are not detected.
    cat /dev/input/js0 outputs garbage whenever I move one of the joysticks, but nothing when I press any button.
    The same with jstest or with the configuration panel under kde (both joystick work, but no output when pressing any button).
    Kernel logging when pluggin in the gamepad (from /var/log/message) :
    Aug 22 17:28:59 antoine kernel: usbcore: registered new interface driver hiddev
    Aug 22 17:28:59 antoine kernel: input: Jess Technology Co., Ltd. PS1000 Dual AnaloguePad as /devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.0/input/input5
    Aug 22 17:28:59 antoine kernel: generic-usb 0003:06A3:0621.0001: input,hidraw0: USB HID v1.11 Gamepad [Jess Technology Co., Ltd. PS1000 Dual AnaloguePad] on usb-0000:00:02.0-7/input0
    Aug 22 17:28:59 antoine kernel: usbcore: registered new interface driver usbhid
    Aug 22 17:28:59 antoine kernel: usbhid: USB HID core driver

  • Faxing - Modem Does Not Detect Dial Tone

    Hello Everyone,
    I suddenly have a need to send and receive a Fax. I have a phone line plugged into the modem port on my G4 and on trying to send a text fax, not much happens. Error message to the effect that the modem is not detecting a dial tone. Same cable that works fine on the phone itself.
    Can someone either help with an answer or direct me to a page with more detailed instructions than the "Help" file is providing?
    John

    I have the same problem. I thought I would begin to use my several years old Powerbook to send a simple fax. As it is I have to use my old G3 to fax. Even with Faxstf pro on I still can't get it to work. Fax STF says that the modem is only set to receive and I just cannot change it in the settings. I've trashed the preferences and the program. I am at a loss after having spent a day trying to figure this out. I am on a dedicated phone line that works just fine. I would really like to just simply fax from my powerbook G4. The modem is as follows:
    Modem Model: LastDash
    Interface Type: USB
    Modulation: V.92
    SKU Name: UCJ
    Hardware Version: 4.0
    Firmware Version: APPLE VERSION 2.6.6
    Driver: InternalUSBModem.kext (v2.6.6)
    Country: B5 (United States, Latin America)

  • Cisco prime infrastructure not detect IP address of clients

    hi all,
    I have Cisco Prime infrastructure 1.2 and when move to monitor >> clients tab it lists me all the clients in my network but their IP address list estates "not detected" ?
    please any advice?
    I appreciate your kindly support.

    Just an update that while this appears to have worked fairly well (as far as Cisco Management Planes go), there was one small 'gotcha' I've noticed so far:
    After the services came back up, the entries for our RADIUS servers did not function.  No, not because I didn't update the clients address record on the RADIUS server itself, but because the RADIUS server record(s) within CPI have a field called 'Local Interface IP' that still reflects the previous IP assigned to CPI.  A quick edit/save with the new interface fixes up the issue however.
    Cheers!

  • Docsis 2.0 and 1.1 cable modems are not detected via UBR-MC20X20V-5D line card

    Hi All,
    We have uBR10K series CMTS and recently installed UBR-MC20X20V-5D line card, requirement is to configure this line card to support docsis 1.1 and 2.0. Problem is after finished the configurations modems (Hitron and Motorola) are not detected by the system. means no modem mac address listing under "Show cable modem" command. 
    Our CMTS has the following components
    ESR-PRE2: x1
    ESR-PRE-MEM-FD128: x1
    UBR10-DTCC:  x2
    UBR-MC20X20V-5D: x1
    iOS version:     12.2(33)SCE3
    Part of running-config as follows
    cable spectrum-group 13 band 22800000 26600000
    controller Integrated-Cable 8/0/0
     rf-channel 0 cable downstream channel-id 145
     rf-channel 0 frequency 501012500 annex B modulation 256qam interleave 32
     rf-channel 0 rf-power 59.0
     no rf-channel 0 rf-shutdown
    interface Cable8/0/0
     no cable packet-cache
     cable bundle 1
     cable upstream max-ports 4
     cable upstream 0 connector 0
     cable upstream 0 spectrum-group 13
     cable upstream 0 channel-width 3200000 3200000
     cable upstream 0 docsis-mode tdma
     cable upstream 0 minislot-size 2
     cable upstream 0 range-backoff 3 6
     cable upstream 0 modulation-profile 21
     no cable upstream 0 shutdown
    diag output attached herewith. Please any one advice on how to resolve this issue.
    Thanks in advance.

    Hi All,
    We have uBR10K series CMTS and recently installed UBR-MC20X20V-5D line card, requirement is to configure this line card to support docsis 1.1 and 2.0. Problem is after finished the configurations modems (Hitron and Motorola) are not detected by the system. means no modem mac address listing under "Show cable modem" command. 
    Our CMTS has the following components
    ESR-PRE2: x1
    ESR-PRE-MEM-FD128: x1
    UBR10-DTCC:  x2
    UBR-MC20X20V-5D: x1
    iOS version:     12.2(33)SCE3
    Part of running-config as follows
    cable spectrum-group 13 band 22800000 26600000
    controller Integrated-Cable 8/0/0
     rf-channel 0 cable downstream channel-id 145
     rf-channel 0 frequency 501012500 annex B modulation 256qam interleave 32
     rf-channel 0 rf-power 59.0
     no rf-channel 0 rf-shutdown
    interface Cable8/0/0
     no cable packet-cache
     cable bundle 1
     cable upstream max-ports 4
     cable upstream 0 connector 0
     cable upstream 0 spectrum-group 13
     cable upstream 0 channel-width 3200000 3200000
     cable upstream 0 docsis-mode tdma
     cable upstream 0 minislot-size 2
     cable upstream 0 range-backoff 3 6
     cable upstream 0 modulation-profile 21
     no cable upstream 0 shutdown
    diag output attached herewith. Please any one advice on how to resolve this issue.
    Thanks in advance.

Maybe you are looking for