7332 is not detected in MAX

Hi,
We have a PCI NI7332 motion controller purchased with us. We installed the drivers and softwares  from the cd that comes with the package. The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. When i tried to connect an encoder and read it in MAX nothing is happening.  Do i have to change any setting when using the board for the first time?
With regards,
Jerry

Jerry, 
I don't quite understand this:
" The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. "
I'm assuming that the board just isn't showing up in NI-MAX.  If you are running Windows, I would go to the Device Manager on your machine and make sure the computer is recognizing it first (I'm not familiar with the Mac equivalent of this).  If the computer is not recognizing it as a piece of hardward installed on the motherborrd, there may be a bad connection.  Restarting the computer is also not a bad idea just to make sure everything is operating correctly.
Hope you get it figured out.
Adam

Similar Messages

  • 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

  • CRIO not Detected in MAX

    Hello,
    I'm totally new to NI and LabVIEW, so I may have done many unnecessary steps or missed something obvious, but here's the rundown (what I can remember) of what I tried:
    I'm trying to make a cRIO-9073 (newer revision, IPreset switch does not reset IP to 0.0.0.0) work with LabVIEW 2011 SP1 (includes MAX 5.1.0f0 and NI-VISA 5.1) installed on Windows 7 Professional SP1 using a crossover ethernet cable.  MAX does not recognize the cRIO in the Remote Systems tab.  After initial problems, I was able to locate 2 IP addresses corresponding to the cRIO, but its still does not appear in MAX.  I have tried the following:
    refreshing the list using F5, rebooting the cRIO, and using the IPreset switch
    reinstalling drivers on the computer using September 2011 NI System Driver Set CD
    manually adding the a new remote VISA system in MAX (tells me that a device is already using that IP address)
    manually adjusted the LAN settings in the Windows control panel and disabled DHCP
    edited Internet Protocol Version 4 (TCP/IPv4)
    manually set IP address and local subnet mask to match the cRIO settings
    Added exceptions to the Windows firewall
    NI-RIO RPC Server
    VISA Interactive Control
    I think that the software and/or drivers on either the computer or the cRIO may not be up to date or compatible with the rest, but I'm not too sure on how to install software on the cRIO if I cannot see it in MAX.  Any ideas?
    Thank you!
    Solved!
    Go to Solution.

    Zach-H wrote:
    To add the device manually you need to select "Remote Device (not on the local subnet)" not "Remote VISA System". The cRIO should try and default to a link local IP address (169.254.x.x Range) if it can't communicate with a DHCP server. This will likely be the case with the cRIO connected directly to the computer.
    If your computer isn't on an agreeing IP and subnet mask its likely that the cRIO wouldn't show up unless you add it manually. You don't want to set them up as the same as the cRIO as they need individual IP addresses. I would recommend setting the subnet masks the same and adding one to the last number of the cRIO's IP address, which should allow it to show up in MAX.
    Very useful document for this kind of a situation: http://digital.ni.com/public.nsf/allkb/abe4bc247e8ac9bc8625734e005cab42?OpenDocument 
    When I tried to add it as a "Remote Device (not on the local subnet)," I got the error message "The device at this address is not supported by the drivers installed on this host."  I checked that my version of NI-RIO 4.0 is compatible with the cRIO-9073.
    Also, I ran through the link you provided, and the steps did not remedy the problem.  When I ran the cRIO with the CONSOLE OUT switch ON, I was able to get lots of information from the cRIO in the command prompt in Windows.  This makes me think that there are no problems with the cRIO, but with the software I have installed on Windows.  I'm not sure what else I can try to install, though.

  • Pxi not detected under max

    Hi...
    I have aPXI 1000B chassis with 8156B controller, i am trying to make the pxi get detected under MAX for 1 month now... still no result... i don know what the problem is...

    i am using windows xp. the labview version is 7.1 with a 7.1 real time. the max version is 3.3 and the controller is 8156B with 1000B chassis. the pxi doesnot boot into anything, but when i connect a vga port the boot screen look like the one in photo i have attached.
    Attachments:
    8156B controller.jpg ‏319 KB
    pxi boots to this screen.jpg ‏311 KB

  • CDAQ-9181 not detected in MAX

    I have NI device which I am trying to connect to in NIMAX however it just not getting connected to it or searched. But I see it running in NI Network browser with some random ip address which I can not ping. Hence I can't configure that device in Network browser either. 
    Any Idea what's wrong? or if there is any utility to configure it? Or it's a NI-DAQ version problem. ??
    I tried NI - MAX 5.1, 5.5 & 5.6 but no use, they all failed to detect it. 
    Where I can download just the device drivers but not whole NI suite?

    Hi prabhushrikant-
    Which version of NI-DAQmx are you using currently?  You can download the latest version here, but make sure first that it meets your O/S and LabVIEW (or other NI software) compatibility requirements.
    What 'random ip' do you see in the network browser for the device?  What happens if you try to click on the link in the network browser?  Can you tell us more about the networking setup on your PC and network?  Do you have multiple NICs in the PC?  What are their networking settings set to (DHCP, static IP, etc)?
    Tom W
    National Instruments

  • Board not detected from MAX

    The machine is equipped with NT4.0 sp5, and was using an old PC-TIO-10 with NIDAQ6.1.
    We decided to sobstitute the board with a PCI-6023E, as we needed some analog signal inputs.
    We installed NIDAQ6.8.1 (without first uninstalling 6.1 version), put away the PC-TIO-10, and installed the PCI-6023E.
    Once MAX opened, it showed the PCI-6023E, but also continued to show the PC-TIO-10 board. We manually removed this old board from the list("delete"). But, at successive MAX openings, it was impossible to find the PCI-6023E board, also refreshing or setting the preferences at "every time I launch MAX".
    We tried unistalling and reinstalling NIDAQ6.8.1, reinstalling NIDAQ6.1 so to try to uninstall it, restarting the machine many times, changing slo
    t for the board, but we never more managed to see the PCI-6023E board among the devices.
    Now the system is on, the board is in the PC, NIDAQ6.8.1 is installed, but we have not the way to use the board.
    We cannot reinstall all (NT, applications, etc.) as the PC is on a plant and cannot be stopped for more than a few minutes.
    We are sure that no secondary things may have caused the problems (bios settings, applications, etc.) as the first time after installation the board was correctly recognised.
    Many thanks.

    Moroli
    Here is what I would suggest to do.
    1. Uninstall NI-DAQ
    2. Clean the registry
    -Click on Windows 'Start' Button and goto 'Run'
    -Type in regedit to open the Registry Editor
    -Follow this path: HKEY_LOCAL_MACHINE >> Software >> National Instruments >> NI-DAQ
    -Delete the NI-DAQ folder
    -Shutdown computer and take out PCI-6023 board
    -Reinstall newest version of NI-DAQ
    (NI-DAQ 6.9.1 can be download from ni.com
    -After installation is complete, put PCI-6023 board back in computer
    By going through these steps, you should be able to use your board normally.
    Brian

  • PXIe-1073 not detected

    I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64.  I have the latest version of Labview, NI-DAQmx, etc.  The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge").  The chassis and installed DAQ card are not detected in MAX.
    I am actually transferring this system from an older computer.  I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software".  There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
    After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll".  This proceeded to occur every time I tried to load Windows.  I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601".  I was finally able to load the last known good configuration and uninstall the software.
    When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point.  It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts.  Why is the computer unable to recognize the chassis without it?  What else can I do to solve the problem?

    Hello Bob_mcbob,
    After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
    As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
    Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
    Jim St
    National Instruments
    RF Product Support Engineer

  • SCXI-1102/SCXI-1303 not detected in SCXI-1000 chassis

    I am using a setup with SCXI-1303 module in a SCXI-1102 within a SCXI-1000 chassis to take voltage and thermocouple measurements.
    Until recently, everything was working fine. but it now appears I am unable to communicate with the interface. I have tried two different computers and the hardware is not detected in MAX. The power light and fan on the SCXI-1000 still comes on, there just appears to be no acknowledgment of the connection to the computer.
    A few more specific error codes:
    * When I double-clicked the DAQ Assistant in the block diagram window and clicked "Test" on one of my inputs, I received the following error:
    "Error -88705:The specified device is not present or is not active in the system."
    * I have also gotten the error code "Error -89130: Device not available in NI-DAQmx" in the DAQ Assistant test panel
    * When closing the DAQ Assistant test panel, I see the error "Error -89130: Device not available for routing"
    * In MAX, if I try to "test" the chassis or module, I have seen errors either saying that the device is not detected, or that the device needs to be reset or is in the process of being reset, or that Traditional DAQ drivers need to be reset (I've tried these reset suggestions with no result)
    At this point I'm wondering if the board or the cable is shot. I unfortunately don't have another 68-pin cable to test at the moment.
    Thanks in advance...
    Solved!
    Go to Solution.

    mtd12 wrote:
    Thanks guys, I was able to resolve the problem. For anyone who might come across this,
    * I noticed in Windows Device Manager that two PCI devices were listed as not being installed properly.
    * After trying to update the drivers, I couldn't start the computer; got BSOD after BIOS load.
    * Some research prompted me to pull out the two PCI cards that I was not using, and I also moved my DAQ card to another slot to force a hardware reinstall.
    * Booted up, loaded the drivers automatically, and off I went.
    Doesn't explain why it didn't work in the other computer, but in the words of Spinal Tap, the authorities said it was better left unsolved at this point.
    You should move the DAQ board back and verify whether it still works. Perhaps one of the slots went bad.
    You didn't notice that you had two PCI devices that were not installed properly before?

  • Parallel port not detected in measurement and automation explorer

    I have installed labview 2010 in windows XP.
    The problem what I am facing is I could not find "Serial & Parallel port" option in Measurement and automation explorer.
    After seeing the similar problem in forum I have installed Ni-Daqmx 9.0.2.  But still I can not see the ports in MAX.
    I think i have attached enough document .
    If the parallel port is not detected in MAX can we send digital data to parallel port.
    I have tested parallel port with LED connecting one leg in 1st data line(pin 2) and another in gnd(pin 25).
    And my program is to blink the led for every one second but I cannot see the blinking.
    Can anyone help in this regards
    thank you
    Attachments:
    max.jpg ‏90 KB
    port setting tab1.jpg ‏30 KB
    device manager resource tab.jpg ‏34 KB

    Thank you for ur reply Smercurio
    I have changed the bios setting now 
    but still i cant see the printer port in MAX
    Regarding my vi, now i changed it please see that also 
    I have given values to element of arrays as (1,2&4) 
    Now also it is not blinking instead it is glowing all the time without blinking.
    What i have to do next.
    Attachments:
    device manger.JPG ‏43 KB
    device manger2.JPG ‏165 KB
    port test.vi ‏9 KB

  • MAX not detecting PCI 6259 connected to BNC 2120

    I have the DAQmx driver 9.0.2
    I have the card (PCI 6259) in a windows XP machine
    The breakout box is a BNC 2120
    MAX does not detect any devices and interfaces.
    Thanks for any help,
    Fmiles

    Does your device show up in Device Manager under data acquisition devices?  If not than it is not being recognized by the computer and you should try moving PCI slots on the card.  If it does not show up under data acquisition devices, right click on it and select uninstall, restart the computer and it should install on its own again.
    Was the card installed during the DAQmx install, try reseating the card.
    Make sure the NI Device Loader Service is started in Control panel»Administration»Services.  It should be set to started and automatic.
    Does DAQmx 9.0.2 appear under Software in the Configuration Pane of Measurement and Automation Explorer, if not, it may not have installed correctly.
    Doug Farrell
    Product Manager - Condition Monitoring
    National Instruments
    National Instruments Condition Monitoring

  • PCI-7344 not found in MAX 3.1.1 after installing NI-Motion 7.0

    Hi,
    I updated my PCI-7344 + LabView 7.0 system with the newest NI-Motion 7.0. After the update the card was not anymore detected in MAX. There was a "broken" device PCI-7344 under NI Motion Devices, which status said something like "This device has been removed or could not be detected" and the Reset command said something like "Could not communicate with the device. Power cycle the computer..". I removed the device from the "Devices and interfaces" list and since that, MAX hasn't had a clue about the card. I've tried the "Create new.." function, but it doesn't show any NI Motion Devices or PCI-7344 anywhere else. I've also tried the Tools/Install legacy driver support, but MAX only notifies that the updates are OK. I've also tried removing the physical device, starting the computer and MAX, reinstalling the device and restarting MAX, but nothing changes. The device is recognised by BIOS as "Unknown device"; in Windows 2000 Pro, the device is well recognised as National Instruments PCI-7344.
    One thing that could cause the problem is that I also have LabView 6i installed on the system, although I'm not currently using it for any purpose. Anyway, this seems to prevent the MAX from detecting the correct updates needed when using the "National Instruments Product Updates.." from Tools menu. Perhaps I need some driver software to correct this problem?
    I also tried to uninstall the NI-Motion 7.0 and to install the NI-Motion 6.1.5, but after this, the MAX did not work correctly. For example, none of the branches in the configuration tree would expand and the MAX locked up when trying to use the Create New.. / NI Motion Device. Is there a way to uninstall the NI-Motion 7.0 and to replace it with NI-Motion 6.1.5 without removing all NI software from the system?
    Before the update, with NI-Motion 6.1.5, the PCI-7344 card was correctly found in MAX and well usable in LabView 7.0.

    Jouni,
    A valid serial number is any number > 0. If you have multiple boards in you system, they must each have a unique serial number. This would be the case for any board coming out of manufacturing. The board Jochen had probably came from R&D and was a prototype board.
    Your problem with downgrading from NI-Motion 7.0 to NI-Motion 6.1.5 was most likely due to the data stored in the MAX database. When you uninstall NI-Motion, the data in the MAX database remains. The NI-Motion 6.1.5 driver would not have been able to read the data correctly. The easiest way to "clear" this database is to delete the c:\Program Files\National Instruments\MAX\data folder. The only other way is to uninstall MAX, which requires that you uninstall everything. WARNING, Deleting the MAX data folder will delete all MAX settings and set them back to defaults for all NI hardware (uninstalling everything has this same affect, by the way). Downgrading is never as clean as upgrading.
    The firmware on a Motion board can always be downgraded by forcing the download of firmware files. To do this, select the board in MAX under Devices and Interfaces. Click on the Firmware tab at the bottom on the window. Highlight "PCI-73XX Firmware" by clicking on it once. Right click on one of the items in the "Firmware name" column to the right. Select "Download All Files".
    I do not have a good explaination for why NI-Motion 7.0 did not recognize your board. Do you have a second board you can try in the system? If not, could you ask your local sales representative if they have one you borrow for a quick test? Since the board is recognized by Windows 2000 Device Manager, I don't think there is an issue with the board, but it doesn't hurt verify this.
    My best guess is that there was a confict during the installation process and your system did not get all of the required files. Though we do significant installer testing, there are rare occasions when a system is in such a state that the installation process does not function as expected. It is my experience that these rare instances do not occur on clean machines, but on machines that have had multiple products installed and uninstalled. If you do get a chance to try NI-Motion 7.0 again you may want to use these parameters to get the installer to create a log of the installation: "c:\setup.exe l*v c:\log.txt". This assumes that the setup.exe is in the c:\ directory. Go to start>>run and type this in without the quotes. The log file will be named log.txt in the c:\ directory.
    Finally, you can technically use NI-Motion 7.0 in LabVIEW 6. You just need to copy the C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\Motion folder to the vi.lib folder of LabVIEW 6. Though this is not officially supported, there is no reason it shouldn't work.
    Regards,

  • 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.

  • Change of modes not detected

    I have a yoga 2 13.My laptop does not detect any change of modes i.e it does not activate tent/theatre/tablet.Is there any solution for it or is it a manufacture defect since i was facing the problem from the beginning.Please suggest.  

    Try pressing the rotation lock buttons. 
    Also, install my yoga patch. If it detects slate/laptop mode, it is a software problem, not a hardware problem.
    indest wrote:
    RC8: http://alltechtalk.net/Yoga_Patch.exe
    Just an FYI, this is a RC, not the final product.
    As always, use at your own risk.
    Please report any/all bugs
    Change log:
    RC8.1 Fixed the notification bug, when the screen was resized; ALT + L hotkey activates the Lock.
    RC8: Fixed Lock Password bug, Fixed Lock Siren Bug, Auto max audio upon Lock start, Blocked Muting/Volume down on trigger) when Lock is activated; Added BT Toggle Hotkey Alt+B (thank miru)
    RC7: Added "Yoga Lock" to the program (via tray menu).*****
    RC6:  Removed Battery info to eliminate redundancy with windows app; Refined System Up-time code; Added Estimate Usage Cost (Eco-Friendly initiative)
    RC5: Added Power Plan changer to the trey menu; Added Battery Info, Bug Fixes
    RC4: Update detector/downloader; Fixed "Disable Touchscreen on Boot" bug, cleaned up the Settings app; added quick resolution buttons to the tray menu.
    RC3: Added a Disable Touchscreen on Boot option; Fixed spelling errors.
    RC2: Hopefully fixed the Slate Mode Notification Bug; Auto-Disable Touchscreen, if Touchscreen was disabled before slate mode
    RC1: Notification bug fix; changed the path of the trigger file to AppData; made an installer
    V. 0.5.1 Added DPI support
    V. 0.5: Added a "Close" button disabler (the button next to the volume up button.... this addition prevents accidental program closer); Modified the settings apps; Improved Notification Bar; Removed Tooltips (replaced with Notification Bar) 
    V. 0.4: Added Notification handler for Slate Mode/Laptop Mode; Modified the settings apps; Added tray menu; Removed the Alt + X close hotkey, since try menu was added; Fixed minor bugs
    V. 0.3: Added Power Plan Toggle on Power State change; Added a Settings App; Added switches to the Patch
    V. 0.2: Added Trackpad Fix****
    V. 0.1: Touchscreen Toggle
    ****The trackpad fix only works with generic synaptic drivers. To install the latest driver (17.0.19), please do the following:
    1. Disable signature enforcement: https://www.youtube.com/watch?v=NM1MN8QZhnk
    2. Install the synaptic driver: 17.0.19
    3. Install the aforementioned patch
    Yoga Lock Description:
    Ever wanted to go to the bathroom at Starbuck or in the Library? Afraid to leave your laptop behind? If so, this Lock was made for you.
    Disclaimer: I shall not be held liable for any stolen property!!! As always use at your own risk and please use your brain!
    Once activated the lock has the following potential:
    Covers your entire screen.
    Blocks perpetrators from accessing your desktop.
    Prevents USB drives from being stolen, via Siren Deterrent.
    Helps deter thieves from taking your laptop.
    What can trigger the Lock:
    The slightest mouse movement.
    Removal of a USB drive.
    Attempted power down of the computer (future goal is to suspend all attempts of powering down).
    Change in AC status (i.e. unplugging the computer).
    When triggered, the lock has the following potential:
    Take a picture of the person who triggered the lock and email the picture to you (passwords are encrypted).
    Loud siren is played.
    Activation of any script you write. This essentially opens this feature to endless possibilities. Currently, I utilize this feature to report my computer as stolen to the prey-project's control panel (this script is not fully functional and will not be packaged with this application).

  • NI 9014 is not detect NI network browser and MUX

    Hi,
    I have been dealing with NI cRio 9014.
    Now, I face a problem with detecting the cRio in MUX and NI network browser after upgrading  the new drives and Labview software. Simply it doesn’t detect at all. I have set correct subnet and IP in my machine.
    Currently install configuration in my machine is shown below
    MUX version = 5.3.0f0
    LabVIEW version =  11.0.1f2 (32bit)
    OS = Windows 7
    I could barely detect the device if I right click on the remote systems in MUX, Create New, Remote Device (not on the local subnet) and then enter the IP address. But I am 100% sure that I have set the correct local subnet in my machine. Interesting even if the NI 9014 is force to detect by this way it still be undetected by NI Network browser.
    In the XP machine, in which MUX version 5.0.0f1 and LabVIEW 10.0.f2(32 bit) installed in, detects NI 9014 within a second.
    This problem is a big headache for me. Specially, after format the disk from W7 machine it is not detected whatsoever from the same machine  and have to reformat the disk from xp machine and need to be configured from the xp machine.
     If you guys could help me to fix this it would be really nice.
    Thank you in advance.

    Hello,
    If you still has problems to detect the cRIO-9014 in MAX you can start to have a look at the points suggested in this article:
    http://digital.ni.com/public.nsf/allkb/ABE4BC247E8AC9BC8625734E005CAB42?OpenDocument
    Especially the points about the firewall and compatibility could be of interest. What software is installed on the cRIO?
    Please let us know how it goes.
    Best regards
    Richard

  • Arch does not detect /dev/sdb

    HI everybody,
    Like the title says, Arch does not detect a second SATA hard drive I have installed on my computer.
    I've searched around Google and the forums and I've doesn't found any helpfull tip.
    The Arch installation is fresh, I just made it tonight, and cfdisk (during the installation) had recogniced the drive.
    I've posted this here because I'm new on Arch, coming from Ubuntu and Fedora distros and I feel like a real Newbie
    Here's some outputs that may be useful:
    sudo fdisk -l
    Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Identificador del disco: 0x8370a3d6
    Disposit. Inicio Comienzo Fin Bloques Id Sistema
    /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
    /dev/sda2 206848 1435379711 717586432 7 HPFS/NTFS/exFAT
    /dev/sda3 1435379712 1953525167 259072728 5 Extendida
    /dev/sda5 1435379775 1437339641 979933+ 82 Linux swap / Solaris
    /dev/sda6 * 1437339705 1827960116 195310206 83 Linux
    /dev/sda7 1827960180 1953525167 62782494 83 Linux
    ls -lat /dev/sd*
    brw-rw---- 1 root disk 8, 2 feb 3 03:32 /dev/sda2
    brw-rw---- 1 root disk 8, 7 feb 3 03:32 /dev/sda7
    brw-rw---- 1 root disk 8, 5 feb 3 03:32 /dev/sda5
    brw-rw---- 1 root disk 8, 6 feb 3 03:32 /dev/sda6
    brw-rw---- 1 root disk 8, 1 feb 3 03:32 /dev/sda1
    brw-rw---- 1 root disk 8, 3 feb 3 03:32 /dev/sda3
    brw-rw---- 1 root disk 8, 0 feb 3 03:32 /dev/sda
    lspci -k
    00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
    Subsystem: Intel Corporation Device 0036
    00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
    Kernel driver in use: pcieport
    00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: mei
    00:16.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset PT IDER Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: ata_generic
    00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: serial
    00:19.0 Ethernet controller: Intel Corporation 82578DC Gigabit Network Connection (rev 06)
    Subsystem: Intel Corporation Device 0037
    Kernel driver in use: e1000e
    00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: ehci_hcd
    00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: snd_hda_intel
    00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: ehci_hcd
    00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
    00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: lpc_ich
    00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: pata_acpi
    00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: i801_smbus
    00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
    Subsystem: Intel Corporation Device 0036
    Kernel driver in use: pata_acpi
    01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
    Subsystem: Device 196e:0898
    Kernel driver in use: nvidia
    01:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1)
    Subsystem: Device 196e:0898
    Kernel driver in use: snd_hda_intel
    3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
    Subsystem: Intel Corporation Device 8086
    3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
    Subsystem: Intel Corporation Device 8086
    3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
    Subsystem: Intel Corporation Device 8086
    3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
    Subsystem: Intel Corporation Device 8086
    3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
    Subsystem: Intel Corporation Device 8086
    3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
    Subsystem: Intel Corporation Device 8086
    Thanks for the help!

    I had the drive connected to a eSATA port, but I pluged it to a ordinary SATA port, and the result is the same.
    The configuration on the BIOS:
    ATA/IDE Mode -> Native
    Configure Storage as -> IDE
    It doesn't show more valuable information except for the location of any drive on any SATA port.
    dmesg output, it can be useful for someone:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.7.5-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Jan 28 10:03:32 CET 2013
    [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d40a9225-bd6b-46b0-9e14-54b177499391 ro quiet
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bfff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009c000-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000df451fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000df452000-0x00000000df494fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000df495000-0x00000000df508fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000df509000-0x00000000df50afff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000df50b000-0x00000000df610fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000df611000-0x00000000df611fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000df612000-0x00000000df612fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000df613000-0x00000000df61afff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000df61b000-0x00000000df61bfff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000df61c000-0x00000000df61dfff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000df61e000-0x00000000df625fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000df626000-0x00000000df646fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000df647000-0x00000000df689fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000df68a000-0x00000000df7fffff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001fbffffff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000001fc000000-0x00000001ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000200000000-0x000000021bffffff] usable
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] SMBIOS 2.6 present.
    [ 0.000000] DMI: /DH55HC, BIOS TCIBX10H.86A.0048.2011.1206.1342 12/06/2011
    [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] No AGP bridge found
    [ 0.000000] e820: last_pfn = 0x21c000 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-CFFFF write-protect
    [ 0.000000] D0000-E7FFF uncachable
    [ 0.000000] E8000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000 mask E00000000 write-back
    [ 0.000000] 1 base 200000000 mask FE0000000 write-back
    [ 0.000000] 2 base 0E0000000 mask FE0000000 uncachable
    [ 0.000000] 3 base 1FC000000 mask FFC000000 uncachable
    [ 0.000000] 4 base 21C000000 mask FFC000000 uncachable
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
    [ 0.000000] e820: update [mem 0x1fc000000-0x1ffffffff] usable ==> reserved
    [ 0.000000] e820: last_pfn = 0xdf800 max_arch_pfn = 0x400000000
    [ 0.000000] found SMP MP-table at [mem 0x000fccd0-0x000fccdf] mapped at [ffff8800000fccd0]
    [ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
    [ 0.000000] Base memory trampoline at [ffff880000096000] 96000 size 24576
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0xdf7fffff]
    [ 0.000000] [mem 0x00000000-0xdf7fffff] page 2M
    [ 0.000000] kernel direct mapping tables up to 0xdf7fffff @ [mem 0x1fffb000-0x1fffffff]
    [ 0.000000] init_memory_mapping: [mem 0x100000000-0x1fbffffff]
    [ 0.000000] [mem 0x100000000-0x1fbffffff] page 2M
    [ 0.000000] kernel direct mapping tables up to 0x1fbffffff @ [mem 0xdf7fb000-0xdf7fffff]
    [ 0.000000] init_memory_mapping: [mem 0x200000000-0x21bffffff]
    [ 0.000000] [mem 0x200000000-0x21bffffff] page 2M
    [ 0.000000] kernel direct mapping tables up to 0x21bffffff @ [mem 0x1fbffe000-0x1fbffffff]
    [ 0.000000] RAMDISK: [mem 0x37a76000-0x37d32fff]
    [ 0.000000] ACPI: RSDP 00000000000f0410 00024 (v02 INTEL)
    [ 0.000000] ACPI: XSDT 00000000df61ce18 00054 (v01 INTEL DH55HC 01072009 MSFT 00010013)
    [ 0.000000] ACPI: FACP 00000000df61ad98 000F4 (v04 INTEL DH55HC 01072009 MSFT 00010013)
    [ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20120913/tbfadt-394)
    [ 0.000000] ACPI BIOS Bug: Warning: 32/64X FACS address mismatch in FADT - 0xDF61BF40/0x00000000DF61BE40, using 32 (20120913/tbfadt-521)
    [ 0.000000] ACPI: DSDT 00000000df613018 06B90 (v01 INTEL DH55HC 00000000 INTL 20051117)
    [ 0.000000] ACPI: FACS 00000000df61bf40 00040
    [ 0.000000] ACPI: APIC 00000000df61af18 000CC (v02 INTEL DH55HC 01072009 MSFT 00010013)
    [ 0.000000] ACPI: SSDT 00000000df61ac18 00102 (v01 INTEL DH55HC 00000001 MSFT 03000001)
    [ 0.000000] ACPI: MCFG 00000000df61df18 0003C (v01 INTEL DH55HC 01072009 MSFT 00000097)
    [ 0.000000] ACPI: HPET 00000000df61de98 00038 (v01 INTEL DH55HC 01072009 AMI. 00000003)
    [ 0.000000] ACPI: ASF! 00000000df61cc18 000A0 (v32 INTEL DH55HC 00000001 TFSM 000F4240)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000021bffffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x21bffffff]
    [ 0.000000] NODE_DATA [mem 0x21bffc000-0x21bffffff]
    [ 0.000000] [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880213600000-ffff88021b5fffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00010000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal [mem 0x100000000-0x21bffffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00010000-0x0009bfff]
    [ 0.000000] node 0: [mem 0x00100000-0xdf451fff]
    [ 0.000000] node 0: [mem 0xdf509000-0xdf50afff]
    [ 0.000000] node 0: [mem 0xdf611000-0xdf611fff]
    [ 0.000000] node 0: [mem 0xdf68a000-0xdf7fffff]
    [ 0.000000] node 0: [mem 0x100000000-0x1fbffffff]
    [ 0.000000] node 0: [mem 0x200000000-0x21bffffff]
    [ 0.000000] On node 0 totalpages: 2061655
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 6 pages reserved
    [ 0.000000] DMA zone: 3910 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 16320 pages used for memmap
    [ 0.000000] DMA32 zone: 894475 pages, LIFO batch:31
    [ 0.000000] Normal zone: 18176 pages used for memmap
    [ 0.000000] Normal zone: 1128704 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled)
    [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 16 CPUs, 12 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: 000000000009c000 - 00000000000a0000
    [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    [ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    [ 0.000000] PM: Registered nosave memory: 00000000df452000 - 00000000df495000
    [ 0.000000] PM: Registered nosave memory: 00000000df495000 - 00000000df509000
    [ 0.000000] PM: Registered nosave memory: 00000000df50b000 - 00000000df611000
    [ 0.000000] PM: Registered nosave memory: 00000000df612000 - 00000000df613000
    [ 0.000000] PM: Registered nosave memory: 00000000df613000 - 00000000df61b000
    [ 0.000000] PM: Registered nosave memory: 00000000df61b000 - 00000000df61c000
    [ 0.000000] PM: Registered nosave memory: 00000000df61c000 - 00000000df61e000
    [ 0.000000] PM: Registered nosave memory: 00000000df61e000 - 00000000df626000
    [ 0.000000] PM: Registered nosave memory: 00000000df626000 - 00000000df647000
    [ 0.000000] PM: Registered nosave memory: 00000000df647000 - 00000000df68a000
    [ 0.000000] PM: Registered nosave memory: 00000000df800000 - 00000000e0000000
    [ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000e4000000
    [ 0.000000] PM: Registered nosave memory: 00000000e4000000 - 00000000fed1c000
    [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
    [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000ff000000
    [ 0.000000] PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
    [ 0.000000] PM: Registered nosave memory: 00000001fc000000 - 0000000200000000
    [ 0.000000] e820: [mem 0xe4000000-0xfed1bfff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:16 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88021bc00000 s84608 r8192 d21888 u131072
    [ 0.000000] pcpu-alloc: s84608 r8192 d21888 u131072 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2027089
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d40a9225-bd6b-46b0-9e14-54b177499391 ro quiet
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] __ex_table already sorted, skipping sort
    [ 0.000000] Checking aperture...
    [ 0.000000] No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 8033416k/8847360k available (4883k kernel code, 600740k absent, 213204k reserved, 4030k data, 812k init)
    [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
    [ 0.000000] NR_IRQS:4352 nr_irqs:808 16
    [ 0.000000] Extended CMOS year: 2000
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 33554432 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.003333] tsc: Detected 3324.877 MHz processor
    [ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 6652.82 BogoMIPS (lpj=11082923)
    [ 0.000006] pid_max: default: 32768 minimum: 301
    [ 0.000034] Security Framework initialized
    [ 0.000044] AppArmor: AppArmor disabled by boot time parameter
    [ 0.000483] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    [ 0.002616] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.003590] Mount-cache hash table entries: 256
    [ 0.003783] Initializing cgroup subsys cpuacct
    [ 0.003786] Initializing cgroup subsys memory
    [ 0.003793] Initializing cgroup subsys devices
    [ 0.003794] Initializing cgroup subsys freezer
    [ 0.003796] Initializing cgroup subsys net_cls
    [ 0.003797] Initializing cgroup subsys blkio
    [ 0.003818] CPU: Physical Processor ID: 0
    [ 0.003819] CPU: Processor Core ID: 0
    [ 0.003824] mce: CPU supports 9 MCE banks
    [ 0.003833] CPU0: Thermal monitoring enabled (TM1)
    [ 0.003840] process: using mwait in idle threads
    [ 0.003844] Last level iTLB entries: 4KB 512, 2MB 7, 4MB 7
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
    tlb_flushall_shift: 6
    [ 0.003958] Freeing SMP alternatives: 16k freed
    [ 0.004816] ACPI: Core revision 20120913
    [ 0.007720] ftrace: allocating 18793 entries in 74 pages
    [ 0.015109] Switched APIC routing to physical flat.
    [ 0.015602] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.048500] smpboot: CPU0: Intel(R) Core(TM) i5 CPU 660 @ 3.33GHz (fam: 06, model: 25, stepping: 05)
    [ 0.154172] Performance Events: PEBS fmt1+, 16-deep LBR, Westmere events, Intel PMU driver.
    [ 0.154177] perf_event_intel: CPUID marked event: 'bus cycles' unavailable
    [ 0.154178] ... version: 3
    [ 0.154179] ... bit width: 48
    [ 0.154180] ... generic registers: 4
    [ 0.154181] ... value mask: 0000ffffffffffff
    [ 0.154182] ... max period: 000000007fffffff
    [ 0.154182] ... fixed-purpose events: 3
    [ 0.154183] ... event mask: 000000070000000f
    [ 0.190806] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.177468] smpboot: Booting Node 0, Processors #1 #2 #3
    [ 0.227213] Brought up 4 CPUs
    [ 0.227218] smpboot: Total of 4 processors activated (26609.30 BogoMIPS)
    [ 0.229378] devtmpfs: initialized
    [ 0.230458] PM: Registering ACPI NVS region [mem 0xdf452000-0xdf494fff] (274432 bytes)
    [ 0.230462] PM: Registering ACPI NVS region [mem 0xdf612000-0xdf612fff] (4096 bytes)
    [ 0.230463] PM: Registering ACPI NVS region [mem 0xdf61b000-0xdf61bfff] (4096 bytes)
    [ 0.230464] PM: Registering ACPI NVS region [mem 0xdf61e000-0xdf625fff] (32768 bytes)
    [ 0.230466] PM: Registering ACPI NVS region [mem 0xdf647000-0xdf689fff] (274432 bytes)
    [ 0.231092] RTC time: 21:05:23, date: 02/03/13
    [ 0.231127] NET: Registered protocol family 16
    [ 0.231227] ACPI: bus type pci registered
    [ 0.231289] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000)
    [ 0.231291] PCI: MMCONFIG at [mem 0xe0000000-0xe3ffffff] reserved in E820
    [ 0.236542] PCI: Using configuration type 1 for base access
    [ 0.236958] bio: create slab <bio-0> at 0
    [ 0.237003] ACPI: Added _OSI(Module Device)
    [ 0.237005] ACPI: Added _OSI(Processor Device)
    [ 0.237006] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.237007] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.237812] ACPI: EC: Look up EC in DSDT
    [ 0.238684] ACPI: Executed 1 blocks of module-level executable AML code
    [ 0.240605] ACPI: SSDT 00000000df612c18 0038C (v01 AMI IST 00000001 MSFT 03000001)
    [ 0.240820] ACPI: Dynamic OEM Table Load:
    [ 0.240821] ACPI: SSDT (null) 0038C (v01 AMI IST 00000001 MSFT 03000001)
    [ 0.240837] ACPI BIOS Bug: Warning: Incorrect checksum in table [SSDT] - 0x3F, should be 0x1F (20120913/tbutils-324)
    [ 0.240840] ACPI: SSDT 00000000df61bd18 00084 (v01 AMI CST 00000001 MSFT 03000001)
    [ 0.241020] ACPI: Dynamic OEM Table Load:
    [ 0.241021] ACPI: SSDT (null) 00084 (v01 AMI CST 00000001 MSFT 03000001)
    [ 0.241360] ACPI: Interpreter enabled
    [ 0.241363] ACPI: (supports S0 S1 S3 S4 S5)
    [ 0.241374] ACPI: Using IOAPIC for interrupt routing
    [ 0.241528] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [ 0.244856] ACPI: No dock devices found.
    [ 0.244859] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.244939] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.244985] pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
    [ 0.245005] PCI host bridge to bus 0000:00
    [ 0.245007] pci_bus 0000:00: root bus resource [bus 00-ff]
    [ 0.245009] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.245010] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.245011] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.245012] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xffffffff]
    [ 0.245019] pci 0000:00:00.0: [8086:0040] type 00 class 0x060000
    [ 0.245033] DMAR: BIOS has allocated no shadow GTT; disabling IOMMU for graphics
    [ 0.245049] pci 0000:00:01.0: [8086:0041] type 01 class 0x060400
    [ 0.245073] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    [ 0.245118] pci 0000:00:16.0: [8086:3b64] type 00 class 0x078000
    [ 0.245149] pci 0000:00:16.0: reg 10: [mem 0xfa129000-0xfa12900f 64bit]
    [ 0.245261] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    [ 0.245285] pci 0000:00:16.2: [8086:3b66] type 00 class 0x010185
    [ 0.245304] pci 0000:00:16.2: reg 10: [io 0xf150-0xf157]
    [ 0.245314] pci 0000:00:16.2: reg 14: [io 0xf140-0xf143]
    [ 0.245323] pci 0000:00:16.2: reg 18: [io 0xf130-0xf137]
    [ 0.245334] pci 0000:00:16.2: reg 1c: [io 0xf120-0xf123]
    [ 0.245346] pci 0000:00:16.2: reg 20: [io 0xf110-0xf11f]
    [ 0.245430] pci 0000:00:16.3: [8086:3b67] type 00 class 0x070002
    [ 0.245452] pci 0000:00:16.3: reg 10: [io 0xf100-0xf107]
    [ 0.245463] pci 0000:00:16.3: reg 14: [mem 0xfa128000-0xfa128fff]
    [ 0.245580] pci 0000:00:19.0: [8086:10f0] type 00 class 0x020000
    [ 0.245601] pci 0000:00:19.0: reg 10: [mem 0xfa100000-0xfa11ffff]
    [ 0.245610] pci 0000:00:19.0: reg 14: [mem 0xfa127000-0xfa127fff]
    [ 0.245620] pci 0000:00:19.0: reg 18: [io 0xf020-0xf03f]
    [ 0.245697] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
    [ 0.245723] pci 0000:00:1a.0: [8086:3b3c] type 00 class 0x0c0320
    [ 0.245745] pci 0000:00:1a.0: reg 10: [mem 0xfa126000-0xfa1263ff]
    [ 0.245840] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    [ 0.245870] pci 0000:00:1b.0: [8086:3b56] type 00 class 0x040300
    [ 0.245887] pci 0000:00:1b.0: reg 10: [mem 0xfa120000-0xfa123fff 64bit]
    [ 0.245970] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.246001] pci 0000:00:1d.0: [8086:3b34] type 00 class 0x0c0320
    [ 0.246022] pci 0000:00:1d.0: reg 10: [mem 0xfa125000-0xfa1253ff]
    [ 0.246117] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    [ 0.246141] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    [ 0.246216] pci 0000:00:1f.0: [8086:3b06] type 00 class 0x060100
    [ 0.246328] pci 0000:00:1f.2: [8086:3b20] type 00 class 0x01018f
    [ 0.246347] pci 0000:00:1f.2: reg 10: [io 0xf0f0-0xf0f7]
    [ 0.246357] pci 0000:00:1f.2: reg 14: [io 0xf0e0-0xf0e3]
    [ 0.246366] pci 0000:00:1f.2: reg 18: [io 0xf0d0-0xf0d7]
    [ 0.246376] pci 0000:00:1f.2: reg 1c: [io 0xf0c0-0xf0c3]
    [ 0.246386] pci 0000:00:1f.2: reg 20: [io 0xf0b0-0xf0bf]
    [ 0.246395] pci 0000:00:1f.2: reg 24: [io 0xf0a0-0xf0af]
    [ 0.246454] pci 0000:00:1f.3: [8086:3b30] type 00 class 0x0c0500
    [ 0.246472] pci 0000:00:1f.3: reg 10: [mem 0xfa124000-0xfa1240ff 64bit]
    [ 0.246498] pci 0000:00:1f.3: reg 20: [io 0xf000-0xf01f]
    [ 0.246538] pci 0000:00:1f.5: [8086:3b26] type 00 class 0x010185
    [ 0.246557] pci 0000:00:1f.5: reg 10: [io 0xf090-0xf097]
    [ 0.246567] pci 0000:00:1f.5: reg 14: [io 0xf080-0xf083]
    [ 0.246576] pci 0000:00:1f.5: reg 18: [io 0xf070-0xf077]
    [ 0.246586] pci 0000:00:1f.5: reg 1c: [io 0xf060-0xf063]
    [ 0.246595] pci 0000:00:1f.5: reg 20: [io 0xf050-0xf05f]
    [ 0.246605] pci 0000:00:1f.5: reg 24: [io 0xf040-0xf04f]
    [ 0.246682] pci 0000:01:00.0: [10de:1200] type 00 class 0x030000
    [ 0.246690] pci 0000:01:00.0: reg 10: [mem 0xf8000000-0xf9ffffff]
    [ 0.246698] pci 0000:01:00.0: reg 14: [mem 0xe8000000-0xefffffff 64bit pref]
    [ 0.246706] pci 0000:01:00.0: reg 1c: [mem 0xf0000000-0xf3ffffff 64bit pref]
    [ 0.246711] pci 0000:01:00.0: reg 24: [io 0xe000-0xe07f]
    [ 0.246717] pci 0000:01:00.0: reg 30: [mem 0xfa000000-0xfa07ffff pref]
    [ 0.246758] pci 0000:01:00.1: [10de:0e0c] type 00 class 0x040300
    [ 0.246765] pci 0000:01:00.1: reg 10: [mem 0xfa080000-0xfa083fff]
    [ 0.246835] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.246838] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    [ 0.246839] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfa0fffff]
    [ 0.246842] pci 0000:00:01.0: bridge window [mem 0xe8000000-0xf3ffffff 64bit pref]
    [ 0.246904] pci 0000:00:1e.0: PCI bridge to [bus 02] (subtractive decode)
    [ 0.246915] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    [ 0.246916] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.246917] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.246919] pci 0000:00:1e.0: bridge window [mem 0xe0000000-0xffffffff] (subtractive decode)
    [ 0.246929] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.247023] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR20._PRT]
    [ 0.247107] pci0000:00: Requesting ACPI _OSC control (0x1d)
    [ 0.247197] pci0000:00: ACPI _OSC request failed (AE_SUPPORT), returned control mask: 0x0d
    [ 0.247198] ACPI _OSC control for PCIe not granted, disabling ASPM
    [ 0.250341] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.250370] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.250397] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 10 11 12 14 15)
    [ 0.250425] ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
    [ 0.250454] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 *7 10 11 12 14 15)
    [ 0.250484] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    [ 0.250511] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.250542] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.250605] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.250606] vgaarb: loaded
    [ 0.250607] vgaarb: bridge control possible 0000:01:00.0
    [ 0.250627] PCI: Using ACPI for IRQ routing
    [ 0.252814] PCI: Discovered peer bus 3f
    [ 0.252815] PCI: root bus 3f: using default resources
    [ 0.252815] PCI: Probing PCI hardware (bus 3f)
    [ 0.252831] PCI host bridge to bus 0000:3f
    [ 0.252833] pci_bus 0000:3f: root bus resource [io 0x0000-0xffff]
    [ 0.252834] pci_bus 0000:3f: root bus resource [mem 0x00000000-0xfffffffff]
    [ 0.252836] pci_bus 0000:3f: No busn resource found for root bus, will use [bus 3f-ff]
    [ 0.252840] pci 0000:3f:00.0: [8086:2c61] type 00 class 0x060000
    [ 0.252855] pci 0000:3f:00.1: [8086:2d01] type 00 class 0x060000
    [ 0.252869] pci 0000:3f:02.0: [8086:2d10] type 00 class 0x060000
    [ 0.252882] pci 0000:3f:02.1: [8086:2d11] type 00 class 0x060000
    [ 0.252894] pci 0000:3f:02.2: [8086:2d12] type 00 class 0x060000
    [ 0.252906] pci 0000:3f:02.3: [8086:2d13] type 00 class 0x060000
    [ 0.252926] pci_bus 0000:3f: busn_res: [bus 3f-ff] end is updated to 3f
    [ 0.253005] PCI: pci_cache_line_size set to 64 bytes
    [ 0.253052] e820: reserve RAM buffer [mem 0x0009c000-0x0009ffff]
    [ 0.253053] e820: reserve RAM buffer [mem 0xdf452000-0xdfffffff]
    [ 0.253055] e820: reserve RAM buffer [mem 0xdf50b000-0xdfffffff]
    [ 0.253056] e820: reserve RAM buffer [mem 0xdf612000-0xdfffffff]
    [ 0.253058] e820: reserve RAM buffer [mem 0xdf800000-0xdfffffff]
    [ 0.253125] NetLabel: Initializing
    [ 0.253126] NetLabel: domain hash size = 128
    [ 0.253127] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.253137] NetLabel: unlabeled traffic allowed by default
    [ 0.253153] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    [ 0.253157] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    [ 0.255164] Switching to clocksource hpet
    [ 0.258533] pnp: PnP ACPI init
    [ 0.258548] ACPI: bus type pnp registered
    [ 0.258610] pnp 00:00: [bus 00-ff]
    [ 0.258612] pnp 00:00: [io 0x0cf8-0x0cff]
    [ 0.258614] pnp 00:00: [io 0x0000-0x0cf7 window]
    [ 0.258615] pnp 00:00: [io 0x0d00-0xffff window]
    [ 0.258616] pnp 00:00: [mem 0x000a0000-0x000bffff window]
    [ 0.258618] pnp 00:00: [mem 0x00000000 window]
    [ 0.258619] pnp 00:00: [mem 0xe0000000-0xffffffff window]
    [ 0.258649] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    [ 0.258677] pnp 00:01: [mem 0xfed14000-0xfed19fff]
    [ 0.258678] pnp 00:01: [mem 0xe0000000-0xe3ffffff]
    [ 0.258680] pnp 00:01: [mem 0xfed90000-0xfed93fff]
    [ 0.258681] pnp 00:01: [mem 0xfed20000-0xfed3ffff]
    [ 0.258682] pnp 00:01: [mem 0xfee00000-0xfee0ffff]
    [ 0.258714] system 00:01: [mem 0xfed14000-0xfed19fff] has been reserved
    [ 0.258716] system 00:01: [mem 0xe0000000-0xe3ffffff] has been reserved
    [ 0.258717] system 00:01: [mem 0xfed90000-0xfed93fff] has been reserved
    [ 0.258719] system 00:01: [mem 0xfed20000-0xfed3ffff] has been reserved
    [ 0.258720] system 00:01: [mem 0xfee00000-0xfee0ffff] has been reserved
    [ 0.258723] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.258812] pnp 00:02: [io 0x0000-0xffffffffffffffff disabled]
    [ 0.258814] pnp 00:02: [io 0x0000-0xffffffffffffffff disabled]
    [ 0.258834] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.258995] pnp 00:03: [io 0x03f8-0x03ff]
    [ 0.259007] pnp 00:03: [irq 4]
    [ 0.259008] pnp 00:03: [dma 0 disabled]
    [ 0.259046] pnp 00:03: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.259277] pnp 00:04: [io 0x0378-0x037f]
    [ 0.259279] pnp 00:04: [io 0x0778-0x077f]
    [ 0.259283] pnp 00:04: [irq 5]
    [ 0.259284] pnp 00:04: [dma 3]
    [ 0.259381] pnp 00:04: Plug and Play ACPI device, IDs PNP0401 (active)
    [ 0.259389] pnp 00:05: [dma 4]
    [ 0.259390] pnp 00:05: [io 0x0000-0x000f]
    [ 0.259391] pnp 00:05: [io 0x0081-0x0083]
    [ 0.259392] pnp 00:05: [io 0x0087]
    [ 0.259394] pnp 00:05: [io 0x0089-0x008b]
    [ 0.259395] pnp 00:05: [io 0x008f]
    [ 0.259396] pnp 00:05: [io 0x00c0-0x00df]
    [ 0.259407] pnp 00:05: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.259413] pnp 00:06: [io 0x0070-0x0071]
    [ 0.259418] pnp 00:06: [irq 8]
    [ 0.259431] pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.259437] pnp 00:07: [io 0x0061]
    [ 0.259449] pnp 00:07: Plug and Play ACPI device, IDs PNP0800 (active)
    [ 0.259459] pnp 00:08: [io 0x0010-0x001f]
    [ 0.259460] pnp 00:08: [io 0x0022-0x003f]
    [ 0.259462] pnp 00:08: [io 0x0044-0x005f]
    [ 0.259463] pnp 00:08: [io 0x0062-0x0063]
    [ 0.259464] pnp 00:08: [io 0x0065-0x006f]
    [ 0.259465] pnp 00:08: [io 0x0072-0x007f]
    [ 0.259466] pnp 00:08: [io 0x0080]
    [ 0.259467] pnp 00:08: [io 0x0084-0x0086]
    [ 0.259468] pnp 00:08: [io 0x0088]
    [ 0.259469] pnp 00:08: [io 0x008c-0x008e]
    [ 0.259471] pnp 00:08: [io 0x0090-0x009f]
    [ 0.259472] pnp 00:08: [io 0x00a2-0x00bf]
    [ 0.259473] pnp 00:08: [io 0x00e0-0x00ef]
    [ 0.259474] pnp 00:08: [io 0x04d0-0x04d1]
    [ 0.259500] system 00:08: [io 0x04d0-0x04d1] has been reserved
    [ 0.259503] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.259508] pnp 00:09: [io 0x00f0-0x00ff]
    [ 0.259513] pnp 00:09: [irq 13]
    [ 0.259526] pnp 00:09: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.259621] pnp 00:0a: [io 0x0400-0x047f]
    [ 0.259622] pnp 00:0a: [io 0x1180-0x119f]
    [ 0.259623] pnp 00:0a: [io 0x0500-0x057f]
    [ 0.259625] pnp 00:0a: [mem 0xfed1c000-0xfed1ffff]
    [ 0.259626] pnp 00:0a: [mem 0xfec00000-0xfecfffff]
    [ 0.259627] pnp 00:0a: [mem 0xfed08000-0xfed08fff]
    [ 0.259628] pnp 00:0a: [mem 0xff000000-0xffffffff]
    [ 0.259648] system 00:0a: [io 0x0400-0x047f] has been reserved
    [ 0.259650] system 00:0a: [io 0x1180-0x119f] has been reserved
    [ 0.259651] system 00:0a: [io 0x0500-0x057f] has been reserved
    [ 0.259653] system 00:0a: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 0.259654] system 00:0a: [mem 0xfec00000-0xfecfffff] could not be reserved
    [ 0.259656] system 00:0a: [mem 0xfed08000-0xfed08fff] has been reserved
    [ 0.259658] system 00:0a: [mem 0xff000000-0xffffffff] has been reserved
    [ 0.259660] system 00:0a: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.259783] pnp 00:0b: [mem 0xfed00000-0xfed003ff]
    [ 0.259800] pnp 00:0b: Plug and Play ACPI device, IDs PNP0103 (active)
    [ 0.259892] pnp: PnP ACPI: found 12 devices
    [ 0.259893] ACPI: ACPI bus type pnp unregistered
    [ 0.266408] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.266411] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    [ 0.266413] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfa0fffff]
    [ 0.266415] pci 0000:00:01.0: bridge window [mem 0xe8000000-0xf3ffffff 64bit pref]
    [ 0.266418] pci 0000:00:1e.0: PCI bridge to [bus 02]
    [ 0.266444] pci 0000:00:1e.0: setting latency timer to 64
    [ 0.266448] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.266449] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.266450] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.266452] pci_bus 0000:00: resource 7 [mem 0xe0000000-0xffffffff]
    [ 0.266453] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    [ 0.266454] pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfa0fffff]
    [ 0.266456] pci_bus 0000:01: resource 2 [mem 0xe8000000-0xf3ffffff 64bit pref]
    [ 0.266457] pci_bus 0000:02: resource 4 [io 0x0000-0x0cf7]
    [ 0.266459] pci_bus 0000:02: resource 5 [io 0x0d00-0xffff]
    [ 0.266460] pci_bus 0000:02: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.266461] pci_bus 0000:02: resource 7 [mem 0xe0000000-0xffffffff]
    [ 0.266463] pci_bus 0000:3f: resource 4 [io 0x0000-0xffff]
    [ 0.266464] pci_bus 0000:3f: resource 5 [mem 0x00000000-0xfffffffff]
    [ 0.266492] NET: Registered protocol family 2
    [ 0.266910] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
    [ 0.268783] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.269029] TCP: Hash tables configured (established 524288 bind 65536)
    [ 0.269063] TCP: reno registered
    [ 0.269073] UDP hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.269110] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.269211] NET: Registered protocol family 1
    [ 0.315053] pci 0000:01:00.0: Boot video device
    [ 0.315082] PCI: CLS 64 bytes, default 64
    [ 0.315125] Unpacking initramfs...
    [ 0.353156] Freeing initrd memory: 2804k freed
    [ 0.353546] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    [ 0.353549] software IO TLB [mem 0xdb452000-0xdf451fff] (64MB) mapped at [ffff8800db452000-ffff8800df451fff]
    [ 0.353859] audit: initializing netlink socket (disabled)
    [ 0.353875] type=2000 audit(1359925523.249:1): initialized
    [ 0.363018] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.364275] VFS: Disk quotas dquot_6.5.2
    [ 0.364309] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.364442] msgmni has been set to 15695
    [ 0.364641] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.364676] io scheduler noop registered
    [ 0.364678] io scheduler deadline registered
    [ 0.364713] io scheduler cfq registered (default)
    [ 0.364792] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    [ 0.364908] vesafb: mode is 1280x800x32, linelength=5120, pages=0
    [ 0.364910] vesafb: scrolling: redraw
    [ 0.364911] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 0.365255] vesafb: framebuffer at 0xf1000000, mapped to 0xffffc90005600000, using 4032k, total 4032k
    [ 0.452482] Console: switching to colour frame buffer device 160x50
    [ 0.539642] fb0: VESA VGA frame buffer device
    [ 0.539651] intel_idle: MWAIT substates: 0x1120
    [ 0.539652] intel_idle: v0.4 model 0x25
    [ 0.539653] intel_idle: lapic_timer_reliable_states 0xffffffff
    [ 0.539700] GHES: HEST is not enabled!
    [ 0.539744] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.560441] 00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 0.581146] 0000:00:16.3: ttyS1 at I/O 0xf100 (irq = 17) is a 16550A
    [ 0.581313] Linux agpgart interface v0.103
    [ 0.581361] i8042: PNP: No PS/2 controller found. Probing ports directly.
    [ 0.594604] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 0.594626] serio: i8042 AUX port at 0x60,0x64 irq 12
    [ 0.594726] mousedev: PS/2 mouse device common for all mice
    [ 0.594777] rtc_cmos 00:06: RTC can wake from S4
    [ 0.594939] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
    [ 0.594973] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    [ 0.595018] cpuidle: using governor ladder
    [ 0.595079] cpuidle: using governor menu
    [ 0.595112] drop_monitor: Initializing network drop monitor service
    [ 0.595172] TCP: cubic registered
    [ 0.595242] NET: Registered protocol family 10
    [ 0.595362] NET: Registered protocol family 17
    [ 0.595369] Key type dns_resolver registered
    [ 0.595570] PM: Hibernation image not present or could not be loaded.
    [ 0.595576] registered taskstats version 1
    [ 0.596120] Magic number: 1:939:94
    [ 0.596267] rtc_cmos 00:06: setting system clock to 2013-02-03 21:05:24 UTC (1359925524)
    [ 0.597300] Freeing unused kernel memory: 812k freed
    [ 0.597412] Write protecting the kernel read-only data: 8192k
    [ 0.599884] Freeing unused kernel memory: 1248k freed
    [ 0.601056] Freeing unused kernel memory: 476k freed
    [ 0.606451] systemd-udevd[57]: starting version 197
    [ 0.624469] SCSI subsystem initialized
    [ 0.625159] ACPI: bus type usb registered
    [ 0.625179] usbcore: registered new interface driver usbfs
    [ 0.625187] usbcore: registered new interface driver hub
    [ 0.625823] ACPI: bus type scsi registered
    [ 0.625865] usbcore: registered new device driver usb
    [ 0.625875] libata version 3.00 loaded.
    [ 0.626068] pata_acpi 0000:00:16.2: setting latency timer to 64
    [ 0.626104] pata_acpi 0000:00:1f.2: setting latency timer to 64
    [ 0.626423] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 0.627806] scsi0 : pata_acpi
    [ 0.628229] scsi1 : pata_acpi
    [ 0.628555] ata1: PATA max UDMA/133 cmd 0xf0f0 ctl 0xf0e0 bmdma 0xf0b0 irq 19
    [ 0.628557] ata2: PATA max UDMA/133 cmd 0xf0d0 ctl 0xf0c0 bmdma 0xf0b8 irq 19
    [ 0.628587] pata_acpi 0000:00:1f.5: setting latency timer to 64
    [ 0.633159] scsi2 : pata_acpi
    [ 0.633673] scsi3 : pata_acpi
    [ 0.634669] ata3: PATA max UDMA/133 cmd 0xf090 ctl 0xf080 bmdma 0xf050 irq 19
    [ 0.634672] ata4: PATA max UDMA/133 cmd 0xf070 ctl 0xf060 bmdma 0xf058 irq 19
    [ 0.634727] ehci_hcd 0000:00:1a.0: setting latency timer to 64
    [ 0.634732] ehci_hcd 0000:00:1a.0: EHCI Host Controller
    [ 0.634739] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
    [ 0.634756] ehci_hcd 0000:00:1a.0: debug port 2
    [ 0.638765] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
    [ 0.638798] ehci_hcd 0000:00:1a.0: irq 16, io mem 0xfa126000
    [ 0.647329] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    [ 0.647467] hub 1-0:1.0: USB hub found
    [ 0.647471] hub 1-0:1.0: 2 ports detected
    [ 0.647542] ehci_hcd 0000:00:1d.0: setting latency timer to 64
    [ 0.647545] ehci_hcd 0000:00:1d.0: EHCI Host Controller
    [ 0.647549] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    [ 0.647560] ehci_hcd 0000:00:1d.0: debug port 2
    [ 0.651548] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported
    [ 0.651561] ehci_hcd 0000:00:1d.0: irq 23, io mem 0xfa125000
    [ 0.660694] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [ 0.660928] hub 2-0:1.0: USB hub found
    [ 0.660932] hub 2-0:1.0: 2 ports detected
    [ 0.801747] ata1.00: ATA-8: ST31000528AS, CC38, max UDMA/133
    [ 0.801750] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [ 0.802139] ata1.01: ATA-8: ST1000DL002-9TT153, CC32, max UDMA/133
    [ 0.802144] ata1.01: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [ 0.803079] ata1.01: no PIO support
    [ 0.953074] usb 1-1: new high-speed USB device number 2 using ehci_hcd
    [ 1.076944] hub 1-1:1.0: USB hub found
    [ 1.077141] hub 1-1:1.0: 6 ports detected
    [ 1.182336] usb 2-1: new high-speed USB device number 2 using ehci_hcd
    [ 1.306076] hub 2-1:1.0: USB hub found
    [ 1.306284] hub 2-1:1.0: 8 ports detected
    [ 1.351793] tsc: Refined TSC clocksource calibration: 3325.000 MHz
    [ 1.351799] Switching to clocksource tsc
    [ 1.385166] usb 1-1.2: new low-speed USB device number 3 using ehci_hcd
    [ 1.541306] usb 1-1.4: new low-speed USB device number 4 using ehci_hcd
    [ 5.935629] ata1.01: no PIO support
    [ 5.935631] ata1.01: disabled
    [ 5.951315] ata1.00: configured for UDMA/100
    [ 5.951734] scsi 0:0:0:0: Direct-Access ATA ST31000528AS CC38 PQ: 0 ANSI: 5
    [ 6.120495] ata2.01: ATAPI: TSSTcorp CDDVDW SH-222AB, SB00, max UDMA/100
    [ 6.120503] ata2.01: no PIO support
    [ 11.257635] ata2.01: no PIO support
    [ 11.257639] ata2.01: disabled
    [ 11.421879] ata_generic 0000:00:16.2: setting latency timer to 64
    [ 11.422293] scsi4 : ata_generic
    [ 11.422400] scsi5 : ata_generic
    [ 11.422428] ata5: PATA max UDMA/100 cmd 0xf150 ctl 0xf140 bmdma 0xf110 irq 18
    [ 11.422430] ata6: PATA max UDMA/100 cmd 0xf130 ctl 0xf120 bmdma 0xf118 irq 18
    [ 11.751474] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    [ 11.751521] sd 0:0:0:0: [sda] Write Protect is off
    [ 11.751523] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 11.751538] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 11.775078] usbcore: registered new interface driver usbhid
    [ 11.775081] usbhid: USB HID core driver
    [ 11.812772] sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
    [ 11.813929] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 11.814854] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input0
    [ 11.814908] hid-generic 0003:046D:C31B.0002: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:1a.0-1.4/input0
    [ 11.815047] input: Microsoft Microsoft® Comfort Mouse 4500 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input1
    [ 11.815422] microsoft 0003:045E:076C.0001: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® Comfort Mouse 4500] on usb-0000:00:1a.0-1.2/input0
    [ 11.817407] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input2
    [ 11.817457] hid-generic 0003:046D:C31B.0003: input,hidraw2: USB HID v1.11 Device [Logitech Logitech USB Keyboard] on usb-0000:00:1a.0-1.4/input1
    [ 12.388733] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
    [ 12.938667] systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    [ 12.961471] systemd[1]: Set hostname to <archlinuxPC>.
    [ 13.159056] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    [ 13.159185] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    [ 13.159221] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [ 13.159230] systemd[1]: Starting Remote File Systems.
    [ 13.159238] systemd[1]: Reached target Remote File Systems.
    [ 13.159244] systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
    [ 13.159250] systemd[1]: Starting Delayed Shutdown Socket.
    [ 13.159271] systemd[1]: Listening on Delayed Shutdown Socket.
    [ 13.159277] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    [ 13.159292] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [ 13.159298] systemd[1]: Starting Encrypted Volumes.
    [ 13.159306] systemd[1]: Reached target Encrypted Volumes.
    [ 13.159313] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    [ 13.159334] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    [ 13.159356] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    [ 13.159431] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    [ 13.159472] systemd[1]: Starting udev Kernel Socket.
    [ 13.159488] systemd[1]: Listening on udev Kernel Socket.
    [ 13.159519] systemd[1]: Starting udev Control Socket.
    [ 13.159537] systemd[1]: Listening on udev Control Socket.
    [ 13.159543] systemd[1]: Starting Swap.
    [ 13.159550] systemd[1]: Reached target Swap.
    [ 13.159556] systemd[1]: Starting Journal Socket.
    [ 13.159589] systemd[1]: Listening on Journal Socket.
    [ 13.159600] systemd[1]: Started File System Check on Root Device.
    [ 13.159605] systemd[1]: Mounting Temporary Directory...
    [ 13.191259] systemd[1]: Mounting Huge Pages File System...
    [ 13.194730] systemd[1]: Starting udev Coldplug all Devices...
    [ 13.214643] systemd[1]: Mounting POSIX Message Queue File System...
    [ 13.231452] systemd[1]: Starting Apply Kernel Variables...
    [ 13.240935] systemd[1]: Starting Setup Virtual Console...
    [ 13.252572] systemd[1]: Started Load Kernel Modules.
    [ 13.252592] systemd[1]: Mounted FUSE Control File System.
    [ 13.252605] systemd[1]: Mounting Debug File System...
    [ 13.254667] systemd[1]: Mounting Configuration File System...
    [ 13.274425] systemd[1]: Starting udev Kernel Device Manager...
    [ 13.305170] systemd[1]: Started Set Up Additional Binary Formats.
    [ 13.305183] systemd[1]: Starting Journal Service...
    [ 13.307733] systemd[1]: Started Journal Service.
    [ 13.307763] systemd[1]: Starting Remount Root and Kernel File Systems...
    [ 13.726755] EXT4-fs (sda7): re-mounted. Opts: data=ordered
    [ 13.750053] systemd-udevd[127]: starting version 197
    [ 13.921301] systemd-journald[128]: Received SIGUSR1
    [ 14.418021] systemd-journald[128]: File /var/log/journal/9dcd8569a2b14c4f9f53ce4406e57e79/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 14.792337] snd_hda_intel 0000:00:1b.0: irq 41 for MSI/MSI-X
    [ 14.877515] input: PC Speaker as /devices/platform/pcspkr/input/input3
    [ 14.893383] e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
    [ 14.893385] e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
    [ 14.953180] parport_pc 00:04: reported by Plug and Play ACPI
    [ 5.951986] ACPI: Invalid Power Resource to register!
    [ 14.953337] parport0: PC-style at 0x378
    [ 14.953338] (0x778), irq 5, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
    [ 15.027758] ppdev: user-space parallel port driver
    [ 15.059527] microcode: CPU0 sig=0x20655, pf=0x2, revision=0x3
    [ 15.068458] microcode: CPU1 sig=0x20655, pf=0x2, revision=0x3
    [ 15.068852] microcode: CPU2 sig=0x20655, pf=0x2, revision=0x3
    [ 15.069229] microcode: CPU3 sig=0x20655, pf=0x2, revision=0x3
    [ 15.069558] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 15.124825] ACPI: Requesting acpi_cpufreq
    [ 15.127274] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
    [ 15.127327] ACPI: Power Button [PWRB]
    [ 15.127369] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
    [ 15.127425] ACPI: Power Button [PWRF]
    [ 15.131162] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input6
    [ 15.139560] input: HDA Intel MID Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
    [ 15.139628] input: HDA Intel MID Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
    [ 15.139728] input: HDA Intel MID Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 15.139785] input: HDA Intel MID Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    [ 15.139838] input: HDA Intel MID Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    [ 15.140068] hda_intel: Disabling MSI
    [ 15.140077] hda-intel: 0000:01:00.1: Handle VGA-switcheroo audio client
    [ 15.140087] e1000e 0000:00:19.0: setting latency timer to 64
    [ 15.140156] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [ 15.140194] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
    [ 15.310985] nvidia: module license 'NVIDIA' taints kernel.
    [ 15.310990] Disabling lock debugging due to kernel taint
    [ 15.335816] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) e0:69:95:a2:d5:75
    [ 15.335819] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
    [ 15.335893] e1000e 0000:00:19.0 eth0: MAC: 9, PHY: 9, PBA No: FFFFFF-0FF
    [ 15.335992] mei 0000:00:16.0: setting latency timer to 64
    [ 15.336076] mei 0000:00:16.0: irq 43 for MSI/MSI-X
    [ 15.336761] ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \_SB_.PCI0.SBRG.AY34 1 (20120913/utaddress-251)
    [ 15.336765] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [ 15.342893] gpio_ich: GPIO from 180 to 255 on gpio_ich
    [ 15.384478] iTCO_vendor_support: vendor-support=0
    [ 15.392227] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    [ 15.392289] iTCO_wdt: Found a H55 TCO device (Version=2, TCOBASE=0x0460)
    [ 15.392384] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 15.468027] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
    [ 15.570266] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
    [ 15.570395] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 15.762514] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
    [ 16.022159] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input12
    [ 16.022316] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input13
    [ 16.022456] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
    [ 16.022589] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
    [ 16.023047] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
    [ 16.023288] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 313.18 Wed Jan 9 17:02:09 PST 2013
    [ 18.372541] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
    [ 18.372591] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 34.993202] NVRM: Your system is not currently configured to drive a VGA console
    [ 34.993205] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
    [ 34.993206] NVRM: requires the use of a text-mode VGA console. Use of other console
    [ 34.993207] NVRM: drivers including, but not limited to, vesafb, may result in
    [ 34.993208] NVRM: corruption and stability problems, and is not supported.
    [ 44.447627] EXT4-fs (sda7): re-mounted. Opts: data=ordered,commit=0
    [ 98.242223] fuse init (API version 7.20)
    Thanks everyone for every reply, I'm learning more GNU/Linux in two days than in two years as other Linux distro's user.

Maybe you are looking for

  • IPhone Safari doesn't open links in new page

    Under iPhone Safari Settings, I've got it set to Open Links In New Page, but when I click on links in Safari, that doesn't happen. When I set it to Open Links In Background, that doesn't happen either. Links open in the same page no matter what the s

  • All files in Blackberry folder on Micro SD/USB drive gone!

    how could something like this happen? the minute I plug my micro SD, which contains files in a blackberry folder (this folder works fine when transferring files back and forth between my blackberry and windows PC), into my used macbook pro that i jus

  • Update new iPod 5.0 to new iOS 7

    Just got replacement iPod 5th gen. When I try to back up it says the iOS's are not compatible. How do I up date to new iOS so I can restore?

  • Why resolution will change in After Effect?

    Would you please help me? I have problem with imported files in After Effect, the file resolution in After Effect is different from source file. I am editing an NTSC video file in Edius, the resolution is 720x480-widescreen16:9 and aspect ratio is 1:

  • Document Set and WF 2013

    I have two questions: 1. Can workflow be started on Document Set (using 2013 workflow - Visual Studio) ? 2. Can Document Set be declared as Record from 2013 workflow - Visual Studio? EDIT: 3. Can Document Set be declared as Record programmatically?