Shunt Calibration Failed

Hello! I'm pretty new to LabVIEW so I apoligize if I am confusing.
I'm trying to put together a VI that will take the strain measurements from four gauges, initially based off of the example provided through the "Strain - Continuous Input.vi". I'm using a cDAQ-9147 equiped with a NI 9237 and a NI 9944. Since our system won't be changing I wanted to set the Shunt resistor value and location as constants (100,000 ohm and R3, respectively). Unfortunately when I then try to run the VI with "Enable Shunt Cal" on I get an error::
"Error -201493 occurred at DAQmx Perform Shunt Calibration (Strain).vi:5630001
Possible reason(s):
Shunt calibration failed. The calculated gain adjust is out of range. Ensure that the shunt calibration terminals are connected properly and that the shunt resistance and shunt element location settings match how the hardware is wired.
Property: AI.Bridge.ShuntCal.ShuntCalAResistance
Corresponding Value: 100.0e3
Simulated Value with Shunt: 1.750000e-3
Measured Value with Shunt: 603.757856e-6
Property: AI.Bridge.ShuntCal.GainAdjust
Requested Value: 2.898513
Possible Values: 500.0e-3 to 1.500000
Channel Name: Axial 2
Task Name: _unnamedTask<A>"
I should note that the original example works on all gauges, so I know it's a mistake I've made somewhere. I've included the VI if that will help.
Thank you!
Attachments:
Strain_HELP.vi ‏98 KB

Hi Sunkistist,
This error can be caused by one of 3 things:
Your 9237 is so far out of calibration that the gain adjustment it would take to correct it is higher than the maximum supported by shunt calibration. Since the shipping example works, and your confident with the readings, we can assume this is not the case.
Improper physical connections. Again, we can rule this out for the same reasons as #1.
Improper configuration. Check to ensure the all the bridge resistance and strain gauge information is correct.
Here are some links you might find helpful:
Shunt Calibration with NI-DAQmx
Connecting Strain Gauges and Shunt Resistors to the NI 9237
NI 9945 or NI 9944 with an NI 9237 Connection Guide
Jeff Munn
Applications Engineer
National Instruments

Similar Messages

  • Does the cRIO Scan Engine Support Offset and Shunt Calibration on the 9237 module

    Thanks.

    Sachsm,
    The documentation for the Set Shunt Calibration (Scan Interface).vi should have been in the VI help but it looks like it didn't make it so I'll make sure it gets updated.  I'll double check my understanding tomorrow morning but the documentation should be the following for the inputs of this VI:
    slot -  Specifies the chassis slot of the strain module (9237, 9235, 9236 ). Valid values are 1 through N, where N is the number of slots in the chassis.
    channel - Specifies the channel to be affected.  Valid values are 0-N where N is the channel for shunt calibration.
    value - Turns Shunt calibration on or off. Valid values are 0 or 1 where a value of 1 will turn shunt calibration on for the given slot and channel.
    Now, for your orginal question about offsets on the AI inputs, here are my addtional thoughts:
    Unlike our SCXI products, the NI 9237 does not have an internal hardware nulling circuitry because its input range is sufficiently wide so that the inputs will not saturate even with a very large initial bridge offset.  Since the 9237 does not have any hardware nulling circuitry, you have to perform offset nulling with software compenstation, and save the value to use later in the application as you mentioned.  For example, when an offset null is performed in DAQmx, the entire offset is stored in the Initial Bridge Voltage property and is stored in software.  You should see the same offset if you used the module from DAQmx, FPGA Interface, or in the Scan Interface.  With that being said, I believe what your seeing is really just the resting measurement of the module and transducer together and you should be able to zero out your measurement by performing Software Compensation.
    Regarding, Offset Calibration, I think its important to make clear exactly what it is providing as the name is a little misleading.  The Offset Cal feature of the 9237 is really more like an Auto Zero used for eliminating offsets generated by an amplifier stage and doesn't provide the same behavior as offset nulling. In Auto Zero Mode, the 9237 shorts the input channel to ground and subtracts the obtained measurement from all subsequent samples. Performing an auto zero is a quick calibration technique that takes place at the beginning of a scan.  A typical use of the Offset calibration feature would be to set it true at the begining of acquiring data and then leaving it on indefinitely.
    Personally, I do not bother enabling offset cal in my FPGA applications because the measurement of the sensor at rest takes into account all sensor and module offsets.
    And finally, if your looking for some information on how to perform shunt calibration, I like to refer to the example VI located here:
    C:\Program Files\National Instruments\LabVIEW 8.6\examples\CompactRIO\Module Specific\NI 9235\NI 9235 Getting Started
    As it has walks through the programming steps of setting up Shunt cal and applying the Gain Factors.  Its written for LabVIEW FPGA but it should be easy to use with Scan Interface.
    Hope that helps a little bit,
    Let me know if you have questions and I'll help where I can or bug the right engineer.
    Basset Hound

  • Gain error with shunt calibration

    Hello,
    I have a problem with shunt calibration of bridge based displacement transducers. The shunt calibration routine sets gain factors that give errors around 2% in the measured displacement. I have also found that the shunt calibration gain factors run out of bounds without a preceding offset null.
    The hardware is a cDAQ-9188 with 9237 modules. The gauges have four wires, two input wires that I have connected to EX+ with jumper to RS+ and EX- with jumper to RS-/SC-, and two output wires that I have connected to AI+ with jumper to SC+ and AI-. LabVIEW is used with a VI shown in the attached figure.
    Does anyone know why the shunt calibration behaves like that or what I do wrong?
    /Emil
    Attachments:
    labview.png ‏19 KB

    Hi Anton,
    Setting the gain manually from a known displacement is not an option as some of the transducers are mounted so that they cannot be tested with gauge blocks.
    Setting the DAQ Assistant Express VI or Create Channel VI to strain mode gives the same shunt factors as the general bridge mode.
    I have done additional measurements to outrule any chance of coincidence with the sensing wires. With jumpers from EX+ to RS+ and from EX- to RS- on the first four of ten transducers the shunt factors are:
    1.0046; 1.0246; 1.0347; 1.0246; 0.9649; 0.9811; 0.9600; 0.9720; 0.9591; 0.9793
    with jumpers only on the first two transducers the shunt factors are:
    1.0044; 1.0247; 0.9867; 0.9729; 0.9648; 0.9811; 0.9599; 0.9721; 0.9589; 0.9791
    and finally for all transducers without jumpers the factors are:
    0.9624; 0.9715; 0.9868; 0.9728; 0.9647; 0.9809; 0.9600; 0.9721; 0.9592; 0.9792
    The conclusion is that the shunt factors are wrong but stable if the wiring is unchanged. Jumpers between EX and RS terminals effects the shunt factors. The shunt factors are between 0.04 and 0.06 larger with jumpers.
    Should the RS terminals be connected for gauges without an extra sensing wire? Should there be a difference with and without the jumpers? Do you suggest anything special to look into regarding the EX wiring?
    /Emil

  • Output gain adjustment factor from DAQmx Perform Shunt Calibration (strain).vi

    Hi
    We are using the DAQmx Perform Shunt Calibration (strain).vi to apply a gain adjustment to the output of our strain gauges. We would like to view the Gain Adjustment applied by the DAQmx Perform Shunt Calibration (strain).vi, and we have tried to do this using a property node.
    I have attached screenshots of the property node we included before the DAQmx Perform Shunt Calibration (strain).vi (which seems to work fine), and the property node we have included after the DAQmx Perform Shunt Calibration (strain).vi (which doesn't output anything).
    Could someone please advise of what I am doing wrong, or if ouputting the Gain Adjustment applied by the DAQmx Perform Shunt Calibration (strain).vi is even possible?
    Cheers
    Bart Scicchitano
    (using his supervisors NI account with her permission)
    Attachments:
    ShuntCal_GainAdjustFactor_Before.PNG ‏29 KB
    ShuntCal_GainAdjustFactor_After.PNG ‏45 KB

    Hello, thank you for your response.
    Sorry I wasn't clear. We get 0 from the property node when using multiple gauges in series. We have since found that the property node works when outputting the gain adjustment factor from only a single gauge, but we still cannot get it to work for multiple gauges in series.
    I have posed the question in a more clear fashion (I hope) in the Labview forum (link below)
    http://forums.ni.com/t5/LabVIEW/How-to-get-gain-adjust-from-multiple-strain-gauges/m-p/2304956/highl...
    Thank you again for your response
    Bart

  • Shunt calibration NI 9235

    How do I wire strain gage for shunt calibration (is it different wiring than normally without shunt calibration?) and programmically set up shunt calibration at DAQmx level (not DAQ assistant)?  I've got 50 feet of lead wire that's going to be added to 10 foot lead wire on 120 ohm resistance strain gages, and I need to be able to calibrate properly to take the resistance added into consideration so that we get the correct strain readings.  I've looked at http://zone.ni.com/reference/en-XX/help/370466W-01/measfunds/quarter1/#GUID-F34636DC-B311-4257-BDD0-... and http://www.ni.com/pdf/manuals/374645a.pdf#page=11 strain gage and NI 9235 related manuals, but they don't completely outline how to do this.
    I'd greatly appreciate any help anyone can offer.
    Thanks!

    Hi, here is an article that clarifies your doubt but with a different module. Now, in your case, in figure 5 from the 9235 manual states that there is a 50 kΩ internal Shunt Resistor. In summary, for the acquisition you just need to configure a strain task and input the sensor data that comes with the calibration certificate. I hope this helps
    Alejandro | Academic Program Engineer | National Instruments

  • Expected Shunt Calibration Factors

    I am trying to shunt calibrate (using a SCC-SG11) a rectangular rosette strain gage wired to an SCC-SG01 module. I'm using an SC-2345 hooked up to a laptop with a DAQCard-6036E. I am reading in an analog voltage with the SG11 engaged and subtracting the value w/o it engaged. The expected value of Vexpected=(R3*Vex*(Rshunt+R4))/(R4+Rshunt+R3*(Rshunt+R4)) is then divided by this difference to obtain the correction factor. For the Vexpected, R3=R4 correct? I am getting a correction factor value of less than 1 (~.97), which to me doesn't make sense, as the shunt calibration is supposed to correct for the wire resistance. Am I understanding this correctly that the correction factor should be >1?
    Thank you in advance for your assistance
    Solved!
    Go to Solution.

    Hi William,
    If we look at what's going on internally in the SCC-SG11 by looking at pg 17-18 in the manual, it shows a diagram and a sample equation. Set all values to 120 to calculate your expected measurement and then vary it from 119 to 121 and divide by the expected value. If the resistance is higher than 120, you will get a lower measured voltage and a ratio >1. If the resistance is lower than 120, you will get a higher measured voltage and a ratio of <1. 
    Jake H | Applications Engineer | National Instruments

  • Shunt calibration CDAQ

    Hi:
      I’m using C-DAQ NI 9237 module with Signal Express and I have the following doubts: 1)      How can I perform a shunt calibration using a ¼ Wheatstone bridge? I’m using module NI 9945 and I don’t have any way to perform the shunt.2)      Concerning the half and full Wheatstone bridge the shunt calibration is possible using module NI 9949. Is the precision resistor of 100kOhm internal to the module? Can I connect an external precision resistor to pins 1 and 10 of the module? 3)      If the precision resistor is internal how can I activate the resistor? I suppose that is just short-cut pin 1 to pin 10. Is that right?  Regards, Diogo Ribeiro.

    Hi Diogo,
    Thanks for posting!   To answer your questions:
    The
    100 kOhm shunt resistor is internal on the 9237 (connected to a switch across pins 1 and
    10).  The 9945 accessory performs the 1/4 bridge completion and the
    circuit containing the shunt resistor is wired across R3 internally. 
    Running the calibration in Signal Express will automatically
    connect/disconnect the shunt as necessary.
    To perform the shunt
    calibration on the 9949, you would use jumper cables to connect the Shunt Calibration
    pins (1 and 10) across the desired resistor (you can specify the resistor used in software).
    Again, the driver will automatically connect and disconnect the shunt resistor during the calibration process.  You can provide
    your own external shunt resistor on the 9949, but you would have to
    make the measurements and scale the data yourself in software.  I would recommend that you let the driver handle this.
    I hope this answers your questions, if you have any others please let me know.
    -John 
    John Passiak

  • Stereo vision calibration failed

    Hi guys,
    I'm using the Calibrate stereo vision.vi (NI Vision development module 2013) to calibrate my stereo vision system but I failed and I don't know why. My experimental setup is as follows:
    2 aviator 1600gc cameras, with 16mm focal lenses and a baseline of 1 cm;
    a calibration grid of 16*16 dots (dx=dy=4 cm), at a distance of 2 meters;
    2 light projector of 500 W.
    I followed the VI instructions and made a lot of trials for 2 days, but i never succedeed in calibration. More specific, in the grid coverage control i always obtain NaN %, as showed in the picture in the attachment.
    In continued to acquire images as long as all gride coverage control below are all to 100% but the VI doesn't proceed into grid vertex calibration.
    Can someone help me?
    Thanks in advance

    Hi there,
    I got exactly the same problem! I hope it's okay posting in this topic.
    I followed the instructions on http://zone.ni.com/reference/en-XX/help/370281U-01/imaqvision/stereo_vision_example/ but my top grid coverage just won't show any values.
    The grid is from the NI folder, so actually it should  be okay.
    cams: 2x DMK 23F618 from ImagingSource
    lenses: 2x 8mm F1.2
    Furthermore, at most attempts I won't even get any values at all.
    Even if all points are detected it won't show any values. This mostly happens when I use external light sources (tried it with infrared and a common 20W halogen lamp running on DC)
    I hope you can help me out here! Thanks

  • Apple Studio Display 21inch - calibration fails

    G'day all, I've reviewed the topics on this display and none seem to fit my problem. Further, I'm convinced that it's not a display problem but an OS Tiger 10.4.11 problem but I reckon that this is the forum that will be best suited to answer.
    In essence, the problem is that a get an overly white screen with very bold colours - as if the contrast and brightness is on steroids and I cannot get past the first page of the ColorSync Assistant. This condition occurred as a result of allowing a service technician to use my Mac to set up a satellite modem - you'd hope that technicians would be more responsible . . . . .
    Anyhow, as I said, I'm convinced that the problem has more to do with OS 10.4.11 than the display as this works perfectly with another user. Specifically, the technician was logged in as PowerMacUser (isn't that original?) and that is the user which gets a problem display. If I log in as another user (i.e. PowerCenterUser - yes! there's one of these on the network) then the screen is normal and I can calibrate the display. So ColorSynch and the Studio Display are working.
    But when I log in again as PowerMacUser nothing has changed. I did make sure that the color profiles in the Computer/Library/ColorSync/Profiles/Display were the same as those used for PowerCenterUser even though they are global, but that didn't make any difference. And I have tried to find out where user-specific data is used to modify display profiles but without success.
    I have a suspicion that it may have something to do with a file named <boot> but I won't pursue this unless I have a prod to so do.

    This is an update. I'm a bit impatient so I got up at 02:30 and did some more research.
    I found that the file boot.efi was still in my trash (OldUsers . .System>Library>CoreServicesboot.efi) and followed BDAqua's excellent advice in regard to this (see http://discussions.apple.com/thread.jspa?messageID=11661635&#11661635).
    Thus I verified both discs in the PowerMac,did a Safe boot - which failed to correct the colour problem. I then reinstalled Mac OS 10.4 - which failed to correct the colour problem and I'm now in the process of bringing this up to OS 10.4.11.
    The only approach that I can think of now is to create a new user since users other than PowerMacUser (see previous post) do not experience the colour problem.
    Any, more creative, ideas would be welcome.

  • [SOLVED] calibre fails to start (python2-six: No module named moves )

    i have same problem with last calibre (2.28.0-1):
    $ calibre
    Traceback (most recent call last):
    File "/usr/lib/calibre/calibre/gui2/ui.py", line 226, in initialize
    ac.do_genesis()
    File "/usr/lib/calibre/calibre/gui2/actions/__init__.py", line 143, in do_genesis
    self.genesis()
    File "/usr/lib/calibre/calibre/gui2/actions/add.py", line 82, in genesis
    from calibre.ebooks.oeb.polish.create import valid_empty_formats
    File "/usr/lib/calibre/calibre/ebooks/oeb/polish/create.py", line 18, in <module>
    from calibre.ebooks.oeb.polish.parsing import parse
    File "/usr/lib/calibre/calibre/ebooks/oeb/polish/parsing.py", line 15, in <module>
    from html5lib.constants import namespaces, tableInsertModeElements, EOF
    File "/usr/lib/python2.7/site-packages/html5lib/__init__.py", line 16, in <module>
    from .html5parser import HTMLParser, parse, parseFragment
    File "/usr/lib/python2.7/site-packages/html5lib/html5parser.py", line 6, in <module>
    from . import inputstream
    File "/usr/lib/python2.7/site-packages/html5lib/inputstream.py", line 3, in <module>
    from six.moves import http_client
    ImportError: No module named moves
    $ calibre-debug -g
    calibre 2.28 isfrozen: False is64bit: False
    Linux-4.0.1-1-ARCH-i686-with-glibc2.0 Linux ('32bit', 'ELF')
    ('Linux', '4.0.1-1-ARCH', '#1 SMP PREEMPT Wed Apr 29 12:15:20 CEST 2015')
    Python 2.7.9
    Linux: ('', '', '')
    Starting up...
    Traceback (most recent call last):
    File "/usr/lib/calibre/calibre/gui2/ui.py", line 226, in initialize
    ac.do_genesis()
    File "/usr/lib/calibre/calibre/gui2/actions/__init__.py", line 143, in do_genesis
    self.genesis()
    File "/usr/lib/calibre/calibre/gui2/actions/add.py", line 82, in genesis
    from calibre.ebooks.oeb.polish.create import valid_empty_formats
    File "/usr/lib/calibre/calibre/ebooks/oeb/polish/create.py", line 18, in <module>
    from calibre.ebooks.oeb.polish.parsing import parse
    File "/usr/lib/calibre/calibre/ebooks/oeb/polish/parsing.py", line 15, in <module>
    from html5lib.constants import namespaces, tableInsertModeElements, EOF
    File "/usr/lib/python2.7/site-packages/html5lib/__init__.py", line 16, in <module>
    from .html5parser import HTMLParser, parse, parseFragment
    File "/usr/lib/python2.7/site-packages/html5lib/html5parser.py", line 6, in <module>
    from . import inputstream
    File "/usr/lib/python2.7/site-packages/html5lib/inputstream.py", line 3, in <module>
    from six.moves import http_client
    ImportError: No module named moves
    $ ebook-edit
    Traceback (most recent call last):
    File "/usr/bin/ebook-edit", line 20, in <module>
    sys.exit(ebook_edit())
    File "/usr/lib/calibre/calibre/gui_launch.py", line 83, in ebook_edit
    main(args)
    File "/usr/lib/calibre/calibre/gui2/tweak_book/main.py", line 76, in main
    _run(args)
    File "/usr/lib/calibre/calibre/gui2/tweak_book/main.py", line 51, in _run
    from calibre.gui2.tweak_book.ui import Main
    File "/usr/lib/calibre/calibre/gui2/tweak_book/ui.py", line 28, in <module>
    from calibre.gui2.tweak_book.file_list import FileListWidget
    File "/usr/lib/calibre/calibre/gui2/tweak_book/file_list.py", line 23, in <module>
    from calibre.ebooks.oeb.polish.container import guess_type, OEB_FONTS
    File "/usr/lib/calibre/calibre/ebooks/oeb/polish/container.py", line 32, in <module>
    from calibre.ebooks.oeb.polish.parsing import parse as parse_html_tweak
    File "/usr/lib/calibre/calibre/ebooks/oeb/polish/parsing.py", line 15, in <module>
    from html5lib.constants import namespaces, tableInsertModeElements, EOF
    File "/usr/lib/python2.7/site-packages/html5lib/__init__.py", line 16, in <module>
    from .html5parser import HTMLParser, parse, parseFragment
    File "/usr/lib/python2.7/site-packages/html5lib/html5parser.py", line 6, in <module>
    from . import inputstream
    File "/usr/lib/python2.7/site-packages/html5lib/inputstream.py", line 3, in <module>
    from six.moves import http_client
    ImportError: No module named moves
    $ pacman -Q|grep calibre
    calibre 2.28.0-1
    [topo@linux ~]$ pacman -Q|grep python
    python 3.4.3-2
    python-cairo 1.10.0-5
    python-dbus 1.2.0-4
    python-dbus-common 1.2.0-4
    python-gobject 3.16.1-1
    python-gobject2 2.28.6-11
    python-html2text 2015.4.14-1
    python-lhafile 0.1.0fs4-1
    python-pycups 1.9.72-2
    python-pycurl 7.19.5.1-2
    python-pyqt4 4.11.3-4
    python-requests 2.6.2-1
    python-setuptools 1:15.2-1
    python-sip 4.16.7-1
    python-xdg 0.25-2
    python2 2.7.9-1
    python2-apsw 3.8.9-1
    python2-beaker 1.7.0-1
    python2-beautifulsoup3 3.2.1-3
    python2-cairo 1.10.0-2
    python2-cffi 0.9.2-2
    python2-chardet 2.3.0-1
    python2-cherrypy 3.6.0-1
    python2-crypto 2.6.1-2
    python2-cryptography 0.8.2-1
    python2-cssselect 0.9.1-2
    python2-cssutils 1.0-2
    python2-dateutil 2.4.2-1
    python2-dbus 1.2.0-4
    python2-dnspython 1.12.0-1
    python2-enum34 1.0.4-1
    python2-fuse 0.2.1-5
    python2-gobject 3.16.1-1
    python2-gobject2 2.28.6-11
    python2-html5lib 0.999-5
    python2-lxml 3.4.4-1
    python2-mako 1.0.1-1
    python2-markupsafe 0.23-2
    python2-mechanize 0.2.5-4
    python2-netifaces 0.10.4-1
    python2-numpy 1.9.2-2
    python2-pillow 2.8.1-1
    python2-ply 3.6-1
    python2-psutil 2.2.1-2
    python2-pyasn1 0.1.7-2
    python2-pycparser 2.12-1
    python2-pyenchant 1.6.6-1
    python2-pygments 2.0.2-2
    python2-pyopenssl 0.14-3
    python2-pyqt4 4.11.3-4
    python2-pyqt5 5.4.1-2
    python2-reportlab 3.1.44-2
    python2-setuptools 1:15.2-1
    python2-sip 4.16.7-1
    python2-six 1.9.0-1
    python2-twisted 15.1.0-1
    python2-xdg 0.25-2
    python2-zope-interface 4.1.2-2
    only ebook-viewer works.
    if I install it from official site, it works.
    Last edited by quellen (2015-05-17 16:28:49)

    $ pacman -Qkk python2-six python2 calibre
    python2-six: 12 file totali, 0 file alterati
    python2: 4716 file totali, 0 file alterati
    calibre: 4881 file totali, 0 file alterati
    $ python2
    Python 2.7.9 (default, Dec 11 2014, 05:36:55)
    [GCC 4.9.2] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import six
    >>> six.__file__
    '/usr/lib/python2.7/site-packages/six/__init__.pyc'
    >>>
    $ ls -l /usr/lib/python2.7/site-packages/six/
    totale 84
    -rw-r--r-- 1 root root 58 22 mar 2014 __init__.py
    -rw-r--r-- 1 root root 236 28 nov 21.06 __init__.pyc
    -rw-r--r-- 1 root root 236 28 nov 21.06 __init__.pyo
    -rw-r--r-- 1 root root 20588 22 mar 2014 six.py
    -rw-r--r-- 1 root root 20739 28 nov 21.06 six.pyc
    -rw-r--r-- 1 root root 20739 28 nov 21.06 six.pyo
    Last edited by quellen (2015-05-17 12:28:15)

  • MSE RF Calibration - Failed to initiate data collection

    Hi guys.
    As you know, in order to improve Wi-Fi location accuracy, we can apply our RF calibration model. I have a problem here, it is impossible to calibrate.
    I'm using:
    WLC 7.6.100.0;
    MSE 7.6.100.0;
    PI-VA-1.4.0.45-small.
    I have a client with Intel(R) Centrino(R) Advanced-N 6205 wireless card. This card is CCX capable and here is my client info on WLC:
    However, when I go to Cisco Prime infrastructure, create a new RF calibration model, select the floor and click “Next”:
    In the new page I see this error (but I already enabled S60 setting on the WLC via CLI):
    Ok... let say we click "OK" here. Next, on this page I choose “Collection Method – Point” and click “Go” on the selected Calibration Point. The new error message appears:
    So in this situation, I am not able to collect any calibration data in order to improve location accuracy.
    Maybe I am missing something? Has anyone of you tested this?

    Hi,
    I have solved this problem. The problem was incorrect SNMP configuration between WLC and Cisco Prime Infrastructure. Please check Your SNMP configuration.

  • Problems performing offset null and shunt calibration in NI PXI-4220

    I am using a 350 ohm strain gage for the measurements, i have already create a task in MAX, when i want to perform offset null in the task, the program shows a waiting bar and the leds in the 4220 board start to tilting, but when the waiting bar stops, MAX gets blocked. it has been impossible to me to perform the offset null, what can i try?.
    which will be the correct values for the parameters beside the gage parameters for the strain measures?

    Hello,
    Thank you for contacting National Instruments.
    Usually when this problem occurs, it is do to incorrect task configuration or incorrectly matched quarter bridge completion resistor. Ensure that you have the correct Strain Configuration chosen. The default is Full Bridge I. If you only have a single strain gauge in your configuration, you will need to change your configuration. Also ensure that if your are using a quarter bridge completion resistor make sure that it is 350Ohm not 120Ohm. If the resistor if 120Ohm you will more thank likely not be able to null your bridge.
    Please see the PXI-4220 User Manual for more information about your configuration and signal connections: http://digital.ni.com/manuals.nsf/websearch/F93CCA9A0B4BA19B86256D60
    0066CD03?OpenDocument&node=132100_US
    Also, you can download and install the latest NI-DAQ 7.2 driver: http://digital.ni.com/softlib.nsf/websearch/50F76C287F531AA786256E7500634BE3?opendocument&node=132070_US
    This 7.2 driver has a signal connections tab displayed when configuring your DAQmx Task which show you how to correctly connect your signals.
    Regards,
    Bill B
    Applications Engineer
    National Instruments

  • Grub-BIOS UUID-base Arch/LXDE fails to boot completly 2/3 of times

    Hi,
    I have a GRUB-BIOS systemd based Arch/LXDE fresh installation (latest 2/2013 image).
    About 2 out of 3 times I boot the system freezes after  displaying that the  /dev/sda2 (my root) is clean.
    Yet, about 1 out of 3 trials, boot completes without problems.
    In either case I don't add any parameters, and just wait for Grub's timeout.
    The same happen with the Linux fallback as well.
    This is a single drive (sda) netbook installation.
    From the journalctl (see below) it seems to me that the alleged stuck boot almost completed!
    I'd appreciate any help!
    Below please find:
    1. Output of journalctl relating to the last two boots: the 17:33 boot got stuck, whereas I'm writing now after successfully rebooting at 17:36
    2. Copy of my fstab
    3. Copy of grub.cfg
    Thanks a lot!
    ----------copy of journalctl of last 2 boots (sorry, it's long)--------------------
    -- Logs begin at Sat 2013-02-16 11:47:04 IST, end at Sat 2013-02-23 17:36:36 IST. --
    [1;39m-- Reboot --[0m
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Allowing runtime journal files to grow to 100.3M.
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpuset
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpu
    Feb 23 17:33:34 miki_netbook kernel: Linux version 3.7.9-1-ARCH (nobody@foutrelis) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Feb 18 02:27:20 EET 2013
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: e820: BIOS-provided physical RAM map:
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007f375fff] usable
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f376000-0x000000007f3befff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f3bf000-0x000000007f46cfff] ACPI data
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f46d000-0x000000007f4befff] ACPI NVS
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f4bf000-0x000000007f4fffff] ACPI data
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f500000-0x000000007fffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: Notice: NX (Execute Disable) protection missing in CPU!
    Feb 23 17:33:34 miki_netbook kernel: SMBIOS 2.4 present.
    Feb 23 17:33:34 miki_netbook kernel: DMI: Quanta UW1/Base Board Product Name, BIOS Q3A51 2/05/2009
    Feb 23 17:33:34 miki_netbook kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Feb 23 17:33:34 miki_netbook kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Feb 23 17:33:34 miki_netbook kernel: e820: last_pfn = 0x7f376 max_arch_pfn = 0x100000
    Feb 23 17:33:34 miki_netbook kernel: MTRR default type: uncachable
    Feb 23 17:33:34 miki_netbook kernel: MTRR fixed ranges enabled:
    Feb 23 17:33:34 miki_netbook kernel: 00000-9FFFF write-back
    Feb 23 17:33:34 miki_netbook kernel: A0000-BFFFF uncachable
    Feb 23 17:33:34 miki_netbook kernel: C0000-C7FFF write-protect
    Feb 23 17:33:34 miki_netbook kernel: C8000-EFFFF uncachable
    Feb 23 17:33:34 miki_netbook kernel: F0000-FFFFF write-protect
    Feb 23 17:33:34 miki_netbook kernel: MTRR variable ranges enabled:
    Feb 23 17:33:34 miki_netbook kernel: 0 base 0FFFE0000 mask 0FFFE0000 write-protect
    Feb 23 17:33:34 miki_netbook kernel: 1 base 0FFFC0000 mask 0FFFE0000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 2 base 000000000 mask 0C0000000 write-back
    Feb 23 17:33:34 miki_netbook kernel: 3 base 040000000 mask 0C0000000 write-back
    Feb 23 17:33:34 miki_netbook kernel: 4 base 07F800000 mask 0FF800000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 5 base 07F600000 mask 0FFE00000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 6 base 07F500000 mask 0FFF00000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 7 base 000000000 mask 0FFFE0000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Feb 23 17:33:34 miki_netbook kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
    Feb 23 17:33:34 miki_netbook kernel: Base memory trampoline at [c009b000] 9b000 size 16384
    Feb 23 17:33:34 miki_netbook kernel: init_memory_mapping: [mem 0x00000000-0x377fdfff]
    Feb 23 17:33:34 miki_netbook kernel: [mem 0x00000000-0x377fdfff] page 4k
    Feb 23 17:33:34 miki_netbook kernel: kernel direct mapping tables up to 0x377fdfff @ [mem 0x01b1f000-0x01bfffff]
    Feb 23 17:33:34 miki_netbook kernel: RAMDISK: [mem 0x37a72000-0x37d30fff]
    Feb 23 17:33:34 miki_netbook kernel: Allocated new RAMDISK: [mem 0x3753f000-0x377fd99b]
    Feb 23 17:33:34 miki_netbook kernel: Move RAMDISK from [mem 0x37a72000-0x37d3099b] to [mem 0x3753f000-0x377fd99b]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: RSDP 000fe020 00024 (v02 haier)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: XSDT 7f4fe120 00064 (v01 haier computer 00000001 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: FACP 7f4fc000 000F4 (v04 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: DSDT 7f4f3000 04DDE (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: FACS 7f488000 00040
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f4fd000 004C4 (v02 PmRef CpuPm 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: HPET 7f4fb000 00038 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: APIC 7f4fa000 00068 (v02 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: MCFG 7f4f9000 0003C (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: ASF! 7f4f8000 000A5 (v32 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SLIC 7f4f2000 00180 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: BOOT 7f4f1000 00028 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Local APIC address 0xfee00000
    Feb 23 17:33:34 miki_netbook kernel: 1147MB HIGHMEM available.
    Feb 23 17:33:34 miki_netbook kernel: 887MB LOWMEM available.
    Feb 23 17:33:34 miki_netbook kernel: mapped low ram: 0 - 377fe000
    Feb 23 17:33:34 miki_netbook kernel: low ram: 0 - 377fe000
    Feb 23 17:33:34 miki_netbook kernel: Zone ranges:
    Feb 23 17:33:34 miki_netbook kernel: DMA [mem 0x00010000-0x00ffffff]
    Feb 23 17:33:34 miki_netbook kernel: Normal [mem 0x01000000-0x377fdfff]
    Feb 23 17:33:34 miki_netbook kernel: HighMem [mem 0x377fe000-0x7f375fff]
    Feb 23 17:33:34 miki_netbook kernel: Movable zone start for each node
    Feb 23 17:33:34 miki_netbook kernel: Early memory node ranges
    Feb 23 17:33:34 miki_netbook kernel: node 0: [mem 0x00010000-0x0009efff]
    Feb 23 17:33:34 miki_netbook kernel: node 0: [mem 0x00100000-0x7f375fff]
    Feb 23 17:33:34 miki_netbook kernel: On node 0 totalpages: 520965
    Feb 23 17:33:34 miki_netbook kernel: free_area_init_node: node 0, pgdat c158d880, node_mem_map f6556200
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 32 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 0 pages reserved
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 3951 pages, LIFO batch:0
    Feb 23 17:33:34 miki_netbook kernel: Normal zone: 1744 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: Normal zone: 221486 pages, LIFO batch:31
    Feb 23 17:33:34 miki_netbook kernel: HighMem zone: 2295 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: HighMem zone: 291457 pages, LIFO batch:31
    Feb 23 17:33:34 miki_netbook kernel: Using APIC driver default
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PM-Timer IO Port: 0x408
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Local APIC address 0xfee00000
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    Feb 23 17:33:34 miki_netbook kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
    Feb 23 17:33:34 miki_netbook kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ0 used by override.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ2 used by override.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ9 used by override.
    Feb 23 17:33:34 miki_netbook kernel: Using ACPI (MADT) for SMP configuration information
    Feb 23 17:33:34 miki_netbook kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Allowing 2 CPUs, 0 hotplug CPUs
    Feb 23 17:33:34 miki_netbook kernel: nr_irqs_gsi: 40
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Feb 23 17:33:34 miki_netbook kernel: e820: [mem 0x80000000-0xdfffffff] available for PCI devices
    Feb 23 17:33:34 miki_netbook kernel: Booting paravirtualized kernel on bare hardware
    Feb 23 17:33:34 miki_netbook kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
    Feb 23 17:33:34 miki_netbook kernel: PERCPU: Embedded 13 pages/cpu @f6530000 s32448 r0 d20800 u53248
    Feb 23 17:33:34 miki_netbook kernel: pcpu-alloc: s32448 r0 d20800 u53248 alloc=13*4096
    Feb 23 17:33:34 miki_netbook kernel: pcpu-alloc: [0] 0 [0] 1
    Feb 23 17:33:34 miki_netbook kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 516894
    Feb 23 17:33:34 miki_netbook kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677 ro quiet
    Feb 23 17:33:34 miki_netbook kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Feb 23 17:33:34 miki_netbook kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Feb 23 17:33:34 miki_netbook kernel: __ex_table already sorted, skipping sort
    Feb 23 17:33:34 miki_netbook kernel: Initializing CPU#0
    Feb 23 17:33:34 miki_netbook kernel: allocated 4168496 bytes of page_cgroup
    Feb 23 17:33:34 miki_netbook kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Feb 23 17:33:34 miki_netbook kernel: Initializing HighMem for node 0 (000377fe:0007f376)
    Feb 23 17:33:34 miki_netbook kernel: Memory: 2051608k/2084312k available (4099k kernel code, 32252k reserved, 1644k data, 556k init, 1175008k highmem)
    Feb 23 17:33:34 miki_netbook kernel: [379B blob data]
    Feb 23 17:33:34 miki_netbook kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
    Feb 23 17:33:34 miki_netbook kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Feb 23 17:33:34 miki_netbook kernel: Preemptible hierarchical RCU implementation.
    Feb 23 17:33:34 miki_netbook kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Feb 23 17:33:34 miki_netbook kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Feb 23 17:33:34 miki_netbook kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
    Feb 23 17:33:34 miki_netbook kernel: NR_IRQS:2304 nr_irqs:512 16
    Feb 23 17:33:34 miki_netbook kernel: CPU 0 irqstacks, hard=f5c08000 soft=f5c0a000
    Feb 23 17:33:34 miki_netbook kernel: Console: colour dummy device 80x25
    Feb 23 17:33:34 miki_netbook kernel: console [tty0] enabled
    Feb 23 17:33:34 miki_netbook kernel: hpet clockevent registered
    Feb 23 17:33:34 miki_netbook kernel: tsc: Fast TSC calibration failed
    Feb 23 17:33:34 miki_netbook kernel: tsc: PIT calibration matches HPET. 1 loops
    Feb 23 17:33:34 miki_netbook kernel: tsc: Detected 1595.989 MHz processor
    Feb 23 17:33:34 miki_netbook kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3193.97 BogoMIPS (lpj=5319963)
    Feb 23 17:33:34 miki_netbook kernel: pid_max: default: 32768 minimum: 301
    Feb 23 17:33:34 miki_netbook kernel: Security Framework initialized
    Feb 23 17:33:34 miki_netbook kernel: AppArmor: AppArmor disabled by boot time parameter
    Feb 23 17:33:34 miki_netbook kernel: Mount-cache hash table entries: 512
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpuacct
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys memory
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys devices
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys freezer
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys net_cls
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys blkio
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: CPU: Physical Processor ID: 0
    Feb 23 17:33:34 miki_netbook kernel: CPU: Processor Core ID: 0
    Feb 23 17:33:34 miki_netbook kernel: mce: CPU supports 5 MCE banks
    Feb 23 17:33:34 miki_netbook kernel: CPU0: Thermal monitoring enabled (TM2)
    Feb 23 17:33:34 miki_netbook kernel: process: using mwait in idle threads
    Feb 23 17:33:34 miki_netbook kernel: [113B blob data]
    Feb 23 17:33:34 miki_netbook kernel: Freeing SMP alternatives: 16k freed
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Core revision 20120913
    Feb 23 17:33:34 miki_netbook kernel: ftrace: allocating 17730 entries in 35 pages
    Feb 23 17:33:34 miki_netbook kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
    Feb 23 17:33:34 miki_netbook kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Feb 23 17:33:34 miki_netbook kernel: smpboot: CPU0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (fam: 06, model: 1c, stepping: 02)
    Feb 23 17:33:34 miki_netbook kernel: Performance Events: PEBS fmt0+, LBR disabled due to erratumAtom events, Intel PMU driver.
    Feb 23 17:33:34 miki_netbook kernel: ... version: 3
    Feb 23 17:33:34 miki_netbook kernel: ... bit width: 40
    Feb 23 17:33:34 miki_netbook kernel: ... generic registers: 2
    Feb 23 17:33:34 miki_netbook kernel: ... value mask: 000000ffffffffff
    Feb 23 17:33:34 miki_netbook kernel: ... max period: 000000007fffffff
    Feb 23 17:33:34 miki_netbook kernel: ... fixed-purpose events: 3
    Feb 23 17:33:34 miki_netbook kernel: ... event mask: 0000000700000003
    Feb 23 17:33:34 miki_netbook kernel: CPU 1 irqstacks, hard=f5cc0000 soft=f5cc2000
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Booting Node 0, Processors #1 OK
    Feb 23 17:33:34 miki_netbook kernel: Initializing CPU#1
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Feb 23 17:33:34 miki_netbook kernel: Brought up 2 CPUs
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Total of 2 processors activated (6386.95 BogoMIPS)
    Feb 23 17:33:34 miki_netbook kernel: devtmpfs: initialized
    Feb 23 17:33:34 miki_netbook kernel: PM: Registering ACPI NVS region [mem 0x7f46d000-0x7f4befff] (335872 bytes)
    Feb 23 17:33:34 miki_netbook kernel: RTC time: 15:33:30, date: 02/23/13
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 16
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type pci registered
    Feb 23 17:33:34 miki_netbook kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    Feb 23 17:33:34 miki_netbook kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using MMCONFIG for extended config space
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using configuration type 1 for base access
    Feb 23 17:33:34 miki_netbook kernel: bio: create slab <bio-0> at 0
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Module Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Processor Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: EC: Look up EC in DSDT
    Feb 23 17:33:34 miki_netbook kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f380c90 00239 (v02 PmRef Cpu0Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 00239 (v02 PmRef Cpu0Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f37fe10 001C7 (v02 PmRef Cpu0Cst 00003001 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 001C7 (v02 PmRef Cpu0Cst 00003001 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f380f10 000D0 (v02 PmRef Cpu1Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 000D0 (v02 PmRef Cpu1Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f37ef10 00083 (v02 PmRef Cpu1Cst 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 00083 (v02 PmRef Cpu1Cst 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Interpreter enabled
    Feb 23 17:33:34 miki_netbook kernel: ACPI: (supports S0 S3 S4 S5)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Using IOAPIC for interrupt routing
    Feb 23 17:33:34 miki_netbook kernel: ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    Feb 23 17:33:34 miki_netbook kernel: ACPI: No dock devices found.
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dsfield-211)
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f5c26dc8), AE_ALREADY_EXISTS (20120913/psparse-536)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Feb 23 17:33:34 miki_netbook kernel: PCI host bridge to bus 0000:00
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:00.0: [8086:27ac] type 00 class 0x060000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: [8086:27ae] type 00 class 0x030000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 10: [mem 0x94280000-0x942fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 14: [io 0x40c0-0x40c7]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 18: [mem 0x80000000-0x8fffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 1c: [mem 0x94300000-0x9433ffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.1: [8086:27a6] type 00 class 0x038000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.1: reg 10: [mem 0x94200000-0x9427ffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: reg 10: [mem 0x94340000-0x94343fff 64bit]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.0: reg 20: [io 0x4080-0x409f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.1: reg 20: [io 0x4060-0x407f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.2: reg 20: [io 0x4040-0x405f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.3: reg 20: [io 0x4020-0x403f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: reg 10: [mem 0x94344400-0x943447ff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.0: [8086:27b9] type 00 class 0x060100
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0068 (mask 0007)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: [8086:27c4] type 00 class 0x010180
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 10: [io 0x0000-0x0007]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 14: [io 0x0000-0x0003]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 18: [io 0x0000-0x0007]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 1c: [io 0x0000-0x0003]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 20: [io 0x40a0-0x40af]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.3: reg 20: [io 0x4000-0x401f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: [10ec:8136] type 00 class 0x020000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 10: [io 0x1000-0x10ff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 18: [mem 0x91010000-0x91010fff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 20: [mem 0x91000000-0x9100ffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 30: [mem 0xffff0000-0xffffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: supports D1 D2
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: PCI bridge to [bus 03] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [mem 0x80000000-0xfebfffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: on NUMA node 0
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dsfield-211)
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f5c26dc8), AE_ALREADY_EXISTS (20120913/psparse-536)
    Feb 23 17:33:34 miki_netbook kernel: pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Feb 23 17:33:34 miki_netbook kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: loaded
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: bridge control possible 0000:00:02.0
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using ACPI for IRQ routing
    Feb 23 17:33:34 miki_netbook kernel: PCI: pci_cache_line_size set to 64 bytes
    Feb 23 17:33:34 miki_netbook kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    Feb 23 17:33:34 miki_netbook kernel: e820: reserve RAM buffer [mem 0x7f376000-0x7fffffff]
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: Initializing
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: domain hash size = 128
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: unlabeled traffic allowed by default
    Feb 23 17:33:34 miki_netbook kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Feb 23 17:33:34 miki_netbook kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Feb 23 17:33:34 miki_netbook kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Feb 23 17:33:34 miki_netbook kernel: Switching to clocksource hpet
    Feb 23 17:33:34 miki_netbook kernel: pnp: PnP ACPI init
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type pnp registered
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [bus 00-ff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0000-0x0cf7 window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0cf8-0x0cff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0d00-0xffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c0000-0x000c3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c4000-0x000c7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c8000-0x000cbfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000cc000-0x000cffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d0000-0x000d3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d4000-0x000d7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d8000-0x000dbfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000dc000-0x000dffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e0000-0x000e3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e4000-0x000e7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e8000-0x000ebfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000ec000-0x000effff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000f0000-0x000fffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x80000000-0xfebfffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x002e-0x002f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0068-0x006f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0200-0x020f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0061]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0070]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0080]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0092]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x00b2-0x00b3]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0063]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0065]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0067]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0600-0x060f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0610]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0800-0x080f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0400-0x047f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0500-0x053f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xe0000000-0xefffffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed1c000-0xfed1ffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed14000-0xfed17fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed18000-0xfed18fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed19000-0xfed19fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfec00000-0xfec00fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfee00000-0xfee00fff]
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0200-0x020f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0600-0x060f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0610] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0800-0x080f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0400-0x047f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0500-0x053f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed14000-0xfed17fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfee00000-0xfee00fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0000-0x001f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0081-0x0091]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0093-0x009f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x00c0-0x00df]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [dma 4]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:03: [io 0x0070-0x0077]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [irq 0 disabled]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [irq 8]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [mem 0xfed00000-0xfed003ff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0103 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: [io 0x00f0]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: [irq 13]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:06: [mem 0xff800000-0xffffffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:06: Plug and Play ACPI device, IDs INT0800 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [io 0x0060]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [io 0x0064]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [irq 1]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:08: [irq 12]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:08: Plug and Play ACPI device, IDs SYN102c SYN1000 SYN0002 PNP0f13 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp: PnP ACPI: found 9 devices
    Feb 23 17:33:34 miki_netbook kernel: ACPI: ACPI bus type pnp unregistered
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0x91020000-0x9102ffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: PCI bridge to [bus 03]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 7 [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 0 [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 1 [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 2 [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 1 [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 2 [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 7 [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 2
    Feb 23 17:33:34 miki_netbook kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    Feb 23 17:33:34 miki_netbook kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    Feb 23 17:33:34 miki_netbook kernel: TCP: Hash tables configured (established 131072 bind 65536)
    Feb 23 17:33:34 miki_netbook kernel: TCP: reno registered
    Feb 23 17:33:34 miki_netbook kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 1
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: Boot video device
    Feb 23 17:33:34 miki_netbook kernel: PCI: CLS 0 bytes, default 64
    Feb 23 17:33:34 miki_netbook kernel: Unpacking initramfs...
    Feb 23 17:33:34 miki_netbook kernel: Freeing initrd memory: 2812k freed
    Feb 23 17:33:34 miki_netbook kernel: Simple Boot Flag value 0x5 read from CMOS RAM was invalid
    Feb 23 17:33:34 miki_netbook kernel: Simple Boot Flag at 0x44 set to 0x1
    Feb 23 17:33:34 miki_netbook kernel: apm: BIOS not found.
    Feb 23 17:33:34 miki_netbook kernel: audit: initializing netlink socket (disabled)
    Feb 23 17:33:34 miki_netbook kernel: type=2000 audit(1361633610.386:1): initialized
    Feb 23 17:33:34 miki_netbook kernel: bounce pool size: 64 pages
    Feb 23 17:33:34 miki_netbook kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
    Feb 23 17:33:34 miki_netbook kernel: VFS: Disk quotas dquot_6.5.2
    Feb 23 17:33:34 miki_netbook kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    Feb 23 17:33:34 miki_netbook kernel: msgmni has been set to 1717
    Feb 23 17:33:34 miki_netbook kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Feb 23 17:33:34 miki_netbook kernel: io scheduler noop registered
    Feb 23 17:33:34 miki_netbook kernel: io scheduler deadline registered
    Feb 23 17:33:34 miki_netbook kernel: io scheduler cfq registered (default)
    Feb 23 17:33:34 miki_netbook kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    Feb 23 17:33:34 miki_netbook kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
    Feb 23 17:33:34 miki_netbook kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
    Feb 23 17:33:34 miki_netbook kernel: vesafb: scrolling: redraw
    Feb 23 17:33:34 miki_netbook kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Feb 23 17:33:34 miki_netbook kernel: vesafb: framebuffer at 0x80000000, mapped to 0xf8080000, using 1216k, total 1216k
    Feb 23 17:33:34 miki_netbook kernel: Console: switching to colour frame buffer device 80x30
    Feb 23 17:33:34 miki_netbook kernel: fb0: VESA VGA frame buffer device
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: MWAIT substates: 0x20220
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: v0.4 model 0x1C
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: lapic_timer_reliable_states 0x2
    Feb 23 17:33:34 miki_netbook kernel: tsc: Marking TSC unstable due to TSC halts in idle states deeper than C2
    Feb 23 17:33:34 miki_netbook kernel: GHES: HEST is not enabled!
    Feb 23 17:33:34 miki_netbook kernel: isapnp: Scanning for PnP cards...
    Feb 23 17:33:34 miki_netbook kernel: isapnp: No Plug & Play device found
    Feb 23 17:33:34 miki_netbook kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Feb 23 17:33:34 miki_netbook kernel: i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUE] at 0x60,0x64 irq 1,12
    Feb 23 17:33:34 miki_netbook kernel: i8042: Warning: Keylock active
    Feb 23 17:33:34 miki_netbook kernel: i8042: Detected active multiplexing controller, rev 1.1
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: mousedev: PS/2 mouse device common for all mice
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: RTC can wake from S4
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    Feb 23 17:33:34 miki_netbook kernel: rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
    Feb 23 17:33:34 miki_netbook kernel: cpuidle: using governor ladder
    Feb 23 17:33:34 miki_netbook kernel: cpuidle: using governor menu
    Feb 23 17:33:34 miki_netbook kernel: EFI Variables Facility v0.08 2004-May-17
    Feb 23 17:33:34 miki_netbook kernel: drop_monitor: Initializing network drop monitor service
    Feb 23 17:33:34 miki_netbook kernel: TCP: cubic registered
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 10
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 17
    Feb 23 17:33:34 miki_netbook kernel: Key type dns_resolver registered
    Feb 23 17:33:34 miki_netbook kernel: Using IPI No-Shortcut mode
    Feb 23 17:33:34 miki_netbook kernel: PM: Hibernation image not present or could not be loaded.
    Feb 23 17:33:34 miki_netbook kernel: registered taskstats version 1
    Feb 23 17:33:34 miki_netbook kernel: Magic number: 1:324:589
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: setting system clock to 2013-02-23 15:33:31 UTC (1361633611)
    Feb 23 17:33:34 miki_netbook kernel: Freeing unused kernel memory: 556k freed
    Feb 23 17:33:34 miki_netbook kernel: Write protecting the kernel text: 4100k
    Feb 23 17:33:34 miki_netbook kernel: Write protecting the kernel read-only data: 1256k
    Feb 23 17:33:34 miki_netbook kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Feb 23 17:33:34 miki_netbook systemd-udevd[44]: starting version 197
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type usb registered
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new interface driver usbfs
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new interface driver hub
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new device driver usb
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: debug port 1
    Feb 23 17:33:34 miki_netbook kernel: SCSI subsystem initialized
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: irq 16, io mem 0x94344400
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type scsi registered
    Feb 23 17:33:34 miki_netbook kernel: libata version 3.00 loaded.
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Feb 23 17:33:34 miki_netbook kernel: hub 1-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 1-0:1.0: 8 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: version 2.13
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: MAP [
    Feb 23 17:33:34 miki_netbook kernel: P0 P2 IDE IDE ]
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: scsi0 : ata_piix
    Feb 23 17:33:34 miki_netbook kernel: scsi1 : ata_piix
    Feb 23 17:33:34 miki_netbook kernel: ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x40a0 irq 14
    Feb 23 17:33:34 miki_netbook kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x40a8 irq 15
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: irq 16, io base 0x00004080
    Feb 23 17:33:34 miki_netbook kernel: hub 2-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 2-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: irq 17, io base 0x00004060
    Feb 23 17:33:34 miki_netbook kernel: hub 3-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 3-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x00004040
    Feb 23 17:33:34 miki_netbook kernel: hub 4-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 4-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: irq 19, io base 0x00004020
    Feb 23 17:33:34 miki_netbook kernel: hub 5-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 5-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: ATA-8: SAMSUNG HM251JI, 2SS00_01, max UDMA7
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: configured for UDMA/133
    Feb 23 17:33:34 miki_netbook kernel: scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM251JI 2SS0 PQ: 0 ANSI: 5
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Write Protect is off
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 23 17:33:34 miki_netbook kernel: sda: sda1 sda2 sda3 sda4
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Feb 23 17:33:34 miki_netbook kernel: usb 1-5: new high-speed USB device number 3 using ehci_hcd
    Feb 23 17:33:34 miki_netbook kernel: usb 1-7: new high-speed USB device number 4 using ehci_hcd
    Feb 23 17:33:34 miki_netbook kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    Feb 23 17:33:34 miki_netbook kernel: usb 2-1: new low-speed USB device number 2 using uhci_hcd
    Feb 23 17:33:34 miki_netbook systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Feb 23 17:33:34 miki_netbook systemd[1]: Set hostname to <miki_netbook>.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Remote File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Remote File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Delayed Shutdown Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Delayed Shutdown Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Device-mapper event daemon FIFOs.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting LVM2 metadata daemon socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on LVM2 metadata daemon socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Encrypted Volumes.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Encrypted Volumes.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Feb 23 17:33:34 miki_netbook systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Kernel Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on udev Kernel Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Control Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on udev Control Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Expecting device dev-disk-by\x2duuid-9501e2aa\x2d4efe\x2d4497\x2d9b55\x2ddb7ebc7afe5d.device...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Journal Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Journal Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started File System Check on Root Device.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Remount Root and Kernel File Systems...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Debug File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting POSIX Message Queue File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Load Kernel Modules.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted FUSE Control File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Setup Virtual Console...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Kernel Device Manager...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Apply Kernel Variables...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Coldplug all Devices...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Configuration File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Huge Pages File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Set Up Additional Binary Formats.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Journal Service...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Journal Service.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Temporary Directory...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting home.automount.
    Feb 23 17:33:34 miki_netbook systemd[1]: Set up automount home.automount.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Setup Virtual Console.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Apply Kernel Variables.
    Feb 23 17:33:34 miki_netbook systemd-udevd[111]: starting version 197
    Feb 23 17:33:34 miki_netbook kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Journal started
    Feb 23 17:33:34 miki_netbook systemd[1]: Started udev Kernel Device Manager.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Remount Root and Kernel File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Debug File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted POSIX Message Queue File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Configuration File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Huge Pages File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Temporary Directory.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Local File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Local File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Recreate Volatile Files and Directories...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started udev Coldplug all Devices.
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Allowing system journal files to grow to 1.4G.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Load Random Seed.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Recreate Volatile Files and Directories.
    Feb 23 17:33:37 miki_netbook systemd[1]: Starting Sound Card.
    Feb 23 17:33:37 miki_netbook systemd[1]: Reached target Sound Card.
    Feb 23 17:33:39 miki_netbook systemd[1]: Found device SAMSUNG_HM251JI.
    Feb 23 17:33:39 miki_netbook systemd[1]: Activating swap /dev/disk/by-uuid/9501e2aa-4efe-4497-9b55-db7ebc7afe5d...
    Feb 23 17:33:39 miki_netbook systemd[1]: Activated swap /dev/disk/by-uuid/9501e2aa-4efe-4497-9b55-db7ebc7afe5d.
    Feb 23 17:33:39 miki_netbook systemd[1]: Starting Swap.
    Feb 23 17:33:39 miki_netbook systemd[1]: Reached target Swap.
    Feb 23 17:33:39 miki_netbook systemd[1]: Starting System Initialization.
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> NetworkManager (version 0.9.6.4) is starting...
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> WEXT support is enabled
    Feb 23 17:33:41 miki_netbook dbus[231]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Feb 23 17:33:41 miki_netbook polkitd[241]: Started polkitd version 0.109
    Feb 23 17:33:42 miki_netbook polkitd[241]: Loading rules from directory /etc/polkit-1/rules.d
    Feb 23 17:33:42 miki_netbook polkitd[241]: Loading rules from directory /usr/share/polkit-1/rules.d
    Feb 23 17:33:42 miki_netbook polkitd[241]: Finished loading, compiling and executing 1 rules
    Feb 23 17:33:42 miki_netbook dbus[231]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Feb 23 17:33:42 miki_netbook polkitd[241]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    Feb 23 17:33:42 miki_netbook NetworkManager[229]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Feb 23 17:33:45 miki_netbook NetworkManager[229]: keyfile: parsing default ...
    Feb 23 17:33:45 miki_netbook NetworkManager[229]: keyfile: read connection 'default'
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: keyfile: parsing Badt ...
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: keyfile: read connection 'Badt'
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> trying to start the modem manager...
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> monitoring kernel firmware directory '/lib/firmware'.
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/ieee80211/phy0/rfkill0) (driver rtl8187)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WiFi enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WWAN enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WiMAX enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> Networking is enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <warn> failed to allocate link cache: (-10) Operation not supported
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): carrier is OFF
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): exported as /org/freedesktop/NetworkManager/Devices/0
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): now managed
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): bringing up device.
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): preparing device.
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): deactivating device (reason 'managed') [2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/enp2s0
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): using nl80211 for WiFi device control
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): new 802.11 WiFi device (driver: 'rtl8187' ifindex: 3)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): exported as /org/freedesktop/NetworkManager/Devices/1
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): now managed
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): bringing up device.
    Feb 23 17:33:47 miki_netbook kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Network Manager.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Network.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Network.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Network Time Service...
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Power Button [PWRB]
    Feb 23 17:33:47 miki_netbook kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Lid Switch [LID0]
    Feb 23 17:33:47 miki_netbook kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
    Feb 23 17:33:47 miki_netbook dbus-daemon[231]: dbus[231]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Feb 23 17:33:47 miki_netbook dbus-daemon[231]: dbus[231]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Sleep Button [SLPB]
    Feb 23 17:33:47 miki_netbook kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Power Button [PWRF]
    Feb 23 17:33:47 miki_netbook kernel: intel_rng: FWH not detected
    Feb 23 17:33:47 miki_netbook kernel: ACPI: AC Adapter [ACAD] (on-line)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Requesting acpi_cpufreq
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Video Device [OVGA] (multi-head: yes rom: yes post: no)
    Feb 23 17:33:47 miki_netbook kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
    Feb 23 17:33:47 miki_netbook kernel: thermal LNXTHERM:00: registered as thermal_zone0
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Thermal Zone [THRM] (56 C)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Battery Slot [BAT1] (battery present)
    Feb 23 17:33:47 miki_netbook kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Invalid Power Resource to register!
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning:
    Feb 23 17:33:47 miki_netbook kernel: 0x00000428-0x0000042f SystemIO conflicts with Region \PMBA 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning: 0x00000530-0x0000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning: 0x00000500-0x0000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
    Feb 23 17:33:47 miki_netbook kernel: leds_ss4200: no LED devices found
    Feb 23 17:33:47 miki_netbook kernel: iTCO_vendor_support: vendor-support=0
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x0460)
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    Feb 23 17:33:47 miki_netbook kernel: microcode: CPU0 sig=0x106c2, pf=0x4, revision=0x208
    Feb 23 17:33:47 miki_netbook kernel: microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x208
    Feb 23 17:33:47 miki_netbook kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    Feb 23 17:33:47 miki_netbook kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    Feb 23 17:33:47 miki_netbook kernel: r8169 0000:02:00.0: irq 42 for MSI/MSI-X
    Feb 23 17:33:47 miki_netbook kernel: r8169 0000:02:00.0 eth0: RTL8102e at 0xf8814000, 00:23:8b:85:d8:aa, XID 04a00000 IRQ 42
    Feb 23 17:33:47 miki_netbook kernel: Linux agpgart interface v0.103
    Feb 23 17:33:47 miki_netbook kernel: cfg80211: Calling CRDA to update world regulatory domain
    Feb 23 17:33:47 miki_netbook kernel: [drm] Initialized drm 1.1.0 20060810
    Feb 23 17:33:47 miki_netbook kernel: usbcore: registered new interface driver usbhid
    Feb 23 17:33:47 miki_netbook kernel: usbhid: USB HID core driver
    Feb 23 17:33:47 miki_netbook kernel: media: Linux media interface: v0.10
    Feb 23 17:33:47 miki_netbook systemd-udevd[137]: renamed network interface eth0 to enp2s0
    Feb 23 17:33:47 miki_netbook kernel: Linux video capture interface: v2.00
    Feb 23 17:33:47 miki_netbook kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
    Feb 23 17:33:47 miki_netbook kernel: uvcvideo: Found UVC 1.00 device USB 2.0 Camera (064e:a127)
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: Intel 945GME Chipset
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: detected gtt size: 262144K total, 262144K mappable
    Feb 23 17:33:47 miki_netbook ntpd[253]: ntpd [email protected] Tue Dec 18 22:49:50 UTC 2012 (1)
    Feb 23 17:33:47 miki_netbook ntpd[254]: proto: precision = 1.955 usec
    Feb 23 17:33:47 miki_netbook ntpd[254]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Feb 23 17:33:47 miki_netbook ntpd[254]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Feb 23 17:33:47 miki_netbook ntpd[254]: Listen and drop on 1 v6wildcard :: UDP 123
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: detected 8192K stolen memory
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Network Time Service.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Multi-User.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Multi-User.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Graphical Interface.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Graphical Interface.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Update UTMP about System Runlevel Changes...
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Update UTMP about System Runlevel Changes.
    Feb 23 17:33:47 miki_netbook systemd[1]: Startup finished in 2s 641ms 739us (kernel) + 14s 238ms 5

    I had the exact same problem. For me the problem was the user groups. Apparently usergroups is not necessary for most use cases with systemd. And my user was in a lot of groups :-) . So I backed up my /etc/group and removed my username from almost every group.
    Hope it solves your problem!

  • W520 External Color Calibrator stopped working with updated Pantone v1.1 software

    Can someone from Lenovo help me with this issue? Lenovo updated the color calibrator software in Aug 2012. They broke an external color calibrator working. L1/2 has been completely unhelpful. I also escalated to customer service with little result except that they say it is not Lenovo software and they do not have to support it! Unacceptable, the software isprovided by Lenovo. Lenovo doc also says an external color calibrator is supported. Lenovo needs to take responsibility for fixing this. Here are the email chains. I really want a refund or someone to ensure this package that Lenovo distributes is fixed!
     Thanks for your help.
      From: Christopher Lang [mailto:christopherlang1] Sent: Wednesday, November 14, 2012 11:34 AM To: 'Kelli' Cc: doris Subject: RE: SF184142 Re: Fw: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator - case 184142 Importance: High Sensitivity: Private
    You are distributing this software and it is defective. Who do I NEED TO SPEAK TO AT LENOVO TO RESOLVE THIS? I WANT A REFUND ASAP!!!
      From: Christopher Lang [mailto:christopherlang1]  Sent: Wednesday, November 14, 2012 11:25 AM To: 'Kelli' Cc: doris Subject: RE: SF184142 Re: Fw: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator - case 184142 Importance: High Sensitivity: Private
    Hi Kelli,
    I do not want this case closed and disagree. This is Lenovo provided software and according to Lenovo an external calibrator is supported. I want someone to take responsibility for getting this fixed. Lenovo has provided this software and needs to work with the vendor to ensure it works. Who do I need to speak to in management? I do not appreciate the way support has just shuttled this around and nothing has gotten done.
    Sincerely,
    Christopher
    Lenovo Doc:
      3.0 System requirements =======================  Hardware requirements:  - Must have an embedded or external color sensor - Can be integrated or used with a USB color sensor device.    http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/pantone_color_calibrator_v1.1.0.txt
    From: Kelli  Sent: Wednesday, November 14, 2012 11:12 AM To: christopherlang1@ Subject: SF184142 Re: Fw: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator - case 184142 Sensitivity: Private
    Mr Lang,
    Please be advised that I have taken this case assigned to Doris. Lenovo is not able help you with this issue, We cannot provide support for a third party product.  The calibrator you are using is supported by X-Rite; any issues with the device need to be addressed by them,
    I am sorry for your frustration however Lenovo has exhausted all means to help with a non-hardware issue. At this time Lenovo is closing this case.
    Kelli Customer Advocate Customer Complaint Resolutions Lenovo US 1009 Think Place, Bldg 2 Morrisville, NC 27560
    Hi Doris,   Got you VM. No, Engineering is not wanting to do their jobs. What they are saying to you makes NO sense. There is even mention of an external calibrator being supported in the Lenovo doc. MANY PEOPLE USE EXTERNAL DISPLAYS AS WELL. Here is the Lenovo doc:   3.0 System requirements ======================= Hardware requirements: - Must have an embedded or external color sensor - Can be integrated or used with a USB color sensor device.   http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/pantone_color_calibrator_v1.1.0.txt      This is really upsetting me!!!!  Can we escalate to higher management?   Thanks,   Christopher  
    Hi Doris,
    Got you VM. No, Engineering is not wanting to do their jobs. What they are saying to you makes NO sense. There is even mention of an external calibrator being supported in the Lenovo doc. MANY PEOPLE USE EXTERNAL DISPLAYS AS WELL. Here is the Lenovo doc:
    3.0 System requirements
    =======================
    Hardware requirements:
    - Must have an embedded or external color sensor
    - Can be integrated or used with a USB color sensor device.
    http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/pantone_color_calibrator_v1.1.0.txt
    This is really upsetting me!!!!  Can we escalate to higher management?
    Thanks,
    Christopher
    From: Christopher Lang  Sent: Thursday, November 08, 2012 12:19 PM To: 'Doris' Subject: RE: FW: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator - case 184142 Importance: High
    Hi Doris,
    I have the internal calibrator I purchased with my W520 and also an external calibrator from x-rite. The device is an i1 Display 2. The external calibration is what fails with the updated calibrator software package.
    Thanks,
    Christopher
    From: Doris Sent: Thursday, November 08, 2012 12:13 PM To: Christopher Lang Subject: Re: FW: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator - case 184142 Importance: High
    Hi Christopher,
     I'm still working wtth L2.
    What exact model of color calibrator device do you have?
    Sincerely,
    Doris Customer Complaint Advocate   Lenovo 
    www.lenovo.com/www.lenovo.com   Print only when necessary    
    "Christopher   Lang" <christopherlang1@>
    11/07/2012   04:22 PM  
       Subject       
       FW:     Error with latest update to Pantone Color Calibrator Software (v1.1) and     Eye one external calibrator - case 184142    
    Hi Doris,    Thanks for your time, re: case 184142. Can we get this package fixed? Jeremy’s response below just makes no sense to me, same as that call center in Atlanta is so problematic. I work in IT and when I phone that call center I really wonder sometimes whether I am even speaking with another IT person on the other end of the line. These are Thinkpad, mines is an expensive one, and I am very upset that this is the level of support I get (especially after upgrading my warranty even!). Please see what you can do. I would also like a manager to speak to DeAndrea at the call center. I am sure the calls are recorded and he was completely out of line and not helpful. Just like now I wonder ‘why did Jeremy even contact me!’ what with the response below.    Please phone me tomorrow as we discussed.    Have a great day!    Thanks,    Christopher      From: Christopher Lang [mailto:christopherlang1@] Sent: Wednesday, November 07, 2012 9:38 AM To: 'Jeremy' Subject: RE: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator   Hi Jeremy,    I am really not sure how Doris will help me with this technical issue? I fel like I am getting the run around and I AM.    Thanks,    Christopher      From: Jeremy Sent: Wednesday, November 07, 2012 9:34 AM To: Christopher Lang Subject: RE: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator   Chris, I never said to call level one. I literally said "please contact your Customer Service rep". Your customer service rep is the highest level you will get at Lenovo to be able to assist you. He/She is also the same person that got you in touch with me in the first place. I hope this helps. Thank you!
    Jeremy Level 2 Support   Lenovo Systems Experts   Lenovo USA   1009 Think Place   Building 2 - Lab 2P22  
         "Christopher   Lang" <christopherlang1@>
    11/07/2012   09:08 AM  
       To       
       Jeremy   
       Subject       
       RE:     Error with latest update to Pantone Color Calibrator Software (v1.1) and     Eye one external calibrator    
    Hello Jeremy,   Uhhh.. My case was escalated to you now you are telling me to call level one again? WTH?   You know…I just started on a contract with IBM. You know what they give us…Not ‘Thinkpads’ but Toshibas. You ought to think about that.   I expect a phone call ASAP. I have also left a message with customer relations.   Thank you,   Christopher  
        From: Jeremy Sent: Wednesday, November 07, 2012 7:46 AM To: Christopher Lang Subject: RE: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator   Chris, This is not my department... please contact your Customer Service rep to get updates. Thank you!
    Jeremy Level 2 Support   Lenovo Systems Experts   Lenovo USA 
    www.Lenovo.com/United   States   Print only when necessary  
    "Christopher   Lang" <christopherlang1@>
    11/06/2012   04:08 PM  
         To       
       Jeremy    cc          Subject       
       RE:     Error with latest update to Pantone Color Calibrator Software (v1.1) and     Eye one external calibrator    
    Hi Jeremy,
    Any update on this package being fixed?
    Thanks,
    Christopher
    From: Christopher Lang [mailto:christopherlang1@] Sent: Thursday, October 25, 2012 12:42 PM To: 'Jeremy' Subject: Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator Importance: High
    Started failing when Lenovo updated the package for the w530.
    Token Ring
    Posts: 473 Registered: 03-10-2009
    0
    Error with latest update to Pantone Color Calibrator Software (v1.1) and Eye one external calibrator   09-19-201211:39 AM - edited 09-20-201209:10 AM Hi. Can someone have a look at the Pantone 1.1 package. I am using an eye one display calibrator with the updated Pantone software and the calibration does not work. I get an error about an 8 bit image missing (have attached a screenshot). The calibration is not correct and Windows Photoviewer is pink. This was working OK with the v1.0 of the software (no longer on the w520 driver page). The error message is "There was an error loading the specified profile. Please make sure the image has an embedded profile and it is an 8-bit image." This was working fine before the update to v1.1. Thanks
    Re: New Pantone Color Calibrator posted [ Edited ]
    10-21-201202:43 AM - edited 10-21-201202:47 AM This is broken on the w520. The external calibration does not work properly. You get an error about an 8-bit image missing when calibrating. Does anyone have a link to the v1.0 version that DOES WORK? Thanks Why is the support in Atlanta so awful that people keep telling me I need to REIMAGE my machine to repair this IDIOT problem!!!!!
    Re: New Pantone Color Calibrator posted [ Edited ] Options ·         Mark as New ·         Bookmark ·         Subscribe ·           ·         Subscribe to RSS Feed ·           ·         Highlight ·         Print ·         Email to a Friend ·           ·         Report Inappropriate Content 10-21-201205:23 AM - edited 10-21-201205:26 AM
    christopherlang wrote: This is broken on the w520. The external calibration does not work properly. You get an error about an 8-bit image missing when calibrating. Does anyone have a link to the v1.0 version that DOES WORK? Thanks Why is the support in Atlanta so awful that people keep telling me I need to REIMAGE my machine to repair this IDIOT problem!!!!!
    I've uploaded the 1.0 program.: http://www.mediafire.com/?62shz55gl757ahu
      From: Jeremy Sent: Thursday, October 25, 2012 11:24 AM To: christopherlang1 Subject: contact info
    here it is
    Moderator note; full names and full or partial contact details of Lenovo employees / agents edited Forum Rules

    I am getting the runaround!!!
    Hi Doris,
    I just left you a voice mail. One of the reasons I bought this laptop was for 3d photography. If I cannot use an external color calibrator and display then the laptop is not fit for purpose for the reasons I bought it. This software is ONLY available from Lenovo. According to Lenovo’s own doc, and the software’s doc, an external color calibrator is SUPPORTED. Lenovo needs to step to the plate and fix this. Not ME. If Lenovo needs to go to Pantone, or x-rite, then they Need to do that. Lenovo provided software that is not available to the public from x-rite or Pantone, and the software is to support Lenovo provided hardware (least so far as the internal calibrator), this software ALSO supports an external calibrator for use with an external display. The software supports both internal and external, and I would like to use my external display for 3d photography. This needs to be fixed please.
    What are we going to do to resolve this? At his point of the runaround I’ve been getting I would like a complete refund.
    Thanks,
    Christopher
    From: Christopher Lang [mailto:christopherlang1@]
    Sent: Wednesday, November 14, 2012 2:35 PM
    To: 'Kelli'
    Cc: doris
    Subject: RE: SF184142 LENOVO
    PS I hope you are aware Kelli that the Pantone software is not available from Pantone to customers….
    From: Christopher Lang [mailto:christopherlang1]
    Sent: Wednesday, November 14, 2012 2:26 PM
    To: 'Kelli'
    Cc: doris
    Subject: RE: SF184142 LENOVO
    Importance: High
    Hi Kelli,
    As you know the ‘software’ purchase is by virtue of purchasing the laptop with the color calibrator. Are you saying you will refund my cost for the calibrator? I don’t think you quite get how much time I have spent with support with this laptop. I have had multiple issues with the it. The calibrator, failed BT adapter, Sudden Shutdown syndrome (where the machine would just shutoff on its own –well documented in the Lenovo forums and I have at least a dozen emails on this issue) as well as many issues with the Displayport connection and an external 3d display for which I spent months working with Nvidia to resolve. This laptop has wasted a huge amount of my time. The support has been atrocious.
    I would like a refund for 1. The laptop 2. The external color calibrator I cannot use because the software from Lenovo does not work (this package is NOT available from x-rite as well –It is sold to Lenovo). I have a receipt for the color calibrator and would be happy to provide that.
    Thank you,
    Christopher
    From: Kelli
    Sent: Wednesday, November 14, 2012 2:09 PM
    To: Christopher Lang
    Subject: RE: SF184142 LENOVO
    Mr Lang,
    Your request for a refund on the laptop is declined. The machine has had not hardware issues and was purchased in February.  We are willing refund the software only.
    Kelli
    Customer Advocate
    Customer Complaint Resolutions
    Moderator note; full names and full or partial contact details of Lenovo employees / agents edited Forum Rules

  • 9236 enable shunt cal property crashes crio OS with scan engine

    I would like to inform users of the 9236 Quarter Bridge Strain Gauge Module of a bug. The Real-Time team is aware of this issue and I have been working with an app engineer on it for about a week and he has confirmed my findings. He says the problem is most likely a driver issue or scan engine issue and they are investigating it.
    There is a bug that completely crashes the cRIO operating system with the 9236 module. Currently when a cRIO device is loaded with LV2009 SP1 or LV2010 and using scan engine interface, attempting to write the "shunt cal enable" property of a 9236 module completely crashes the VxWorks OS. If you try to access the property again, the crio crashes and enters an error state where the crio has rebooted twice without being told to. The LED indicator blinks four times to indicate this.
    I have tested this with a few different hardware combinations with both the crio-9014 and crio-9012 controllers, combined with either the 8-channel 9104 back plane or the 4-channel 9102 back plane with the same results. The app engineer was able to duplicate this issue as well.
    To duplicate the bug:
    Load a crio device with 2009 SP1 or LV2010 and configure the device for scan engine. Locate the 9236 module in the project explorer and drag and drop it into a VI to create the IO variable. Right click the output terminal of the IO Variable and go to create > property > enable shunt calibration  on a channel. Once the property is dropped, right click on it and do change to write so that you can write a boolean to the variable. It doesn't matter if you write a true or false to the property, the results are the same. Hit run, watch it crash. When it reboots, hit run again. The crio is now in a state that can only be recovered by physically resetting the device.
    I love the crio stuff and I use it every day because it is very reliable and robust. This kind of thing is rare, which is why I am reporting it to the community as well as NI as it is a pretty big bug that took me a while to narrow down.
    [will work for kudos]

    rex1030,
    Shunt calibration can be accessed using a property node.  The operation will be the same, you still need to acquire two sets of data and compute the scalar.
    You can obtain the necessary reference by dragging the module to the block diagram from the project.  Please see http://zone.ni.com/devzone/cda/tut/p/id/9351 for more information on programmatic configuration.
    Let me know if you have any other questions.
    Sebastian

Maybe you are looking for