Interfacinf of digital correlator
Hi,
i want to interface a hardware known as digital correlator with the computer using labview.
digital correlator is a DSP tipe kit that provides calculation of correlation between signals.
Do any one know more about digital correlator? How it provides output in its different channels?
i want to see this correlation results in labview. Can anyone hepl me?please reply me.
See http://sss-mag,com/corr.html about how they work (or google).
How the results get back to the computer, depends on which device you have.
NI has DSP's that can be programmed, so you can deside yourself how you get
results.
This is also possible with an FPGA cart from NI.
Regards,
Wiebe.
Similar Messages
-
Trying to get dll calls to work like c++
Hi,
I understand there have been many posts about dll files. I have reviewed them and found nothing that helps me. I have a segment of c++ code that communicates with a digital correlator, reading data from it. The c++ code works fine, but when I wrote the code in Labview, I get results that are reasonable sometimes....sometimes I get good data, sometimes odd data, and sometimes no data. The c++ code ALWAYS yields good data. The function prototypes in each of the call library functions matches that in the c++ code.
The C++ code is attached.
NOTE THAT there are a few things (like calculating delay times and writing to file I don't do in the labview code).
The labview code never outputs any values in TraceA or TraceB, which should be values around 300,000. The DLL location is set correctly, as evidenced by the fact that the code works....just not consistently.
Any help would be greatly appreciated.
Josh
Attachments:
Correlator.vi 38 KB
sample.cpp 6 KBYour message is very clear!
I have no idea how the fact that this particular code was made to work would help you unless you try to use the same DLL which would seem rather strange. As to what the OP posters problem was:
One has to provide buffers to DLL functions for ALL parameters when one calls them. Yes LabVIEW does take care about buffer allocations everywhere else so you don't have to worry about that, but when calling C code, LabVIEW can't even guess what buffers the function may need. And therefore it correctly doesn't try to guess at all.
Those arrays that the function should write into, have to be allocated BEFORE one calls the function. It's the single most problem why DLL calls don't work as expected either returning rubbish or crashing. And anyone claiming to have read all the posts about DLL calling on this board or also on lavag.org should have gotten across at least two dozen messages from me where I pointed that out and explained it in detail.
in detail: The graph arrays do get initialized but in the same frame all control get initialized to default. That is completely wrong! one does either one or the other but not both and definitly not in the same frame because of uncertainety which is executed first.
nTrace is initialized to 0 and then used as indication in the CallLibrary Node, how large the array needs to be. Well a 0 element array is just that an array of no content, therefore a buffer that can hold no information and therefore it's sheer unluck that the Call Library Node doesn't crash.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Dear expert
Is digital image correlation (DIC) algorithm for strain measurement implemented in Labview? If not, does somebody share Labview vi for DIC?
I found that several free version of DIC in the web but, there is no Labview version.
Does anyone have any idea on this?
Thanks
Solved!
Go to Solution.Digital Image Correlation is not implemented in LabVIEW as part of a toolkit or module at this point. This may be something good to suggest on the LabVIEW Idea Exchange if you're interested.
Blake C.
Applications Engineer
National Instruments
www.ni.com/support -
Generating frequency dependant square pulse and making it digital
trying to generate a square wave pulse at a specific frequency
it would be great if its simple as setting the amount of frequency (i.e., 50 , 50 pulses per sec)
but it gets complicated because of the sample rate
my problem is to convert it to digital and i don't know whats wrong
i attached a pic of my block diagram
as you can see, one pulse has frequency F, the other F/2, and lastly F/4
i need it to be compatible with the VI attached as well. can anyone help? thanks in advance!
Message Edited by sdkpark on 10-10-2009 12:19 AM
Attachments:
Create Digital Waveform.vi 20 KB
Correlated Dig Write With Counter.vi 31 KBHello again Sdkpark,
Apologies the message I was writing didn't include my full post. Take a look at this great community example for a prebuilt solution to what I believe you're trying to accomplish:
http://decibel.ni.com/content/docs/DOC-5763
Let me know if this isn't what you're looking for and I'll reply back. Have a great day!
-John Sullivan
Analog Engineer -
How to force digital input sample rate?
Does anyone know how to force a Digital Input sample rate and/or tell Core Audio which conversion clock to use... internal or external? Apparently both things can be done from Pro Tools, but I don't have it. My problem is locking onto an A/D converter's 48K Toslink output. I can set 48K in 'Audio - Midi' setup and the audio is perfect, but a few seconds later Core Audio returns to the default 44.1K. I need to force it to stay at 48K, or clock on the signal rather than internal clock.
Braver,
Let me clarify a few things. First, the 6733 supports correlated digital I/O. This means that the digital operation does not have its own clock. You can correlate the digital operation with the AO clock, which will allow a digital operation up to the max AO rate. You can generate a pulse train with an onboard counter and use that as your digital clock source. Also, you can use a completely external clock source to achieve the max digital rate of 10MHz. The knowledge base, linked below, points you to a couple of examples that ship with LabVIEW. Be sure and read the documentation associated with each example.
Knowlege Base
As for
the example CDI Single Point clocked by Counter (E).vi, notice how the output of... -
Using a SCC counter pulse train to control a SCC digital out signal
I am trying to send a digital high signal on a SCC-Digital ouput module for a certain number of pulses generated by a SCC-Counter/timer pulse train. I have found examples of how to route such signals through PFI12 etc on an M-series board but I am trying to achieve this without referring to the card, just the SCC modules themselves.
I cannot find a way to use the sample clock from the counter generated pulse train to synchronise the digital output.
Is there any way I can do this without referring to the connected M-series DAQ card channels?
Thanks in advance for your assistance.
Cheers.Hi Phil,
The SCC carrier is only conditioning your signals (i.e. if your signals are not in optimal ranges, bandwidth or need external excitation). The actual counters and all digital lines are controlled directly by the M-series board. This means you will never be able to refer to a counter in the SCC module.
If you route the signals of the M-Series board, is as if you had done so externally from the SCC. Look at this example and might give you more insight to how to implement it (This is software timing). The hardware timing would be doing correlation DIO. Here is an example that needs to be modified to adapt to your timing: http://zone.ni.com/devzone/cda/epd/p/id/4414
Hope this helps,
Yardov
Gerardo O.
RF Systems Engineering
National Instruments
Attachments:
Finite Dig Output High.vi 31 KB -
Fast multi-channel digital to analog converter
Hello,
I’m a PhD student working in a mechanics laboratory in France (LMT Cachan) and one of the goals of my thesis is to control a hydraulic testing machine using digital image correlation techniques. In order to do this, I need to take a photo of a sample, process it, extract 4 parameters and send them to the testing machine. This process needs to be repeated at a frequency of approximately 80Hz. We need a device to send these values from a Linux computer to the 4 analog entries of the machine (0-10V, 0.5 mA) by coaxial BNC cable. We managed to do this for one channel using an USB connected oscilloscope by sending a continuous current by changing the offset using C++. The problem is that this solution is too slow and has only one channel.
For this we would need a device that has a viable and fast connection (Ethernet, PCI, even USB if recommended) that can send data from a Linux computer (ideally using C++) with a latency of around 1ms, frequency of at least 100Hz, precision of 0.1% and on 4 synchronized analog outputs. Given that I am not particularly specialized in the field of electronics, researching such a device among the large quantity of items produced by your firm proves to be a difficult task.
I would like to know if you have a product that fits our needs and if similar purpose programming has already been done (or could easily be done) to send data from a linux computer to analog outputs (using C++ ideally).
Best regards,
Ionut PrisacariHi,
I advise you to call our Sales Services 01 57 66 24 24
They can provide you some advise and find the correct DAQ Board. Nevertheless starting with your requirements, most of them can work in your case.
Thanks
-
Extract the message from correlation id what is this problem
Message
Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=7.8...
Leaving Monitored Scope (EnsureListItemsData). Execution Time=9.6533039437744
Leaving Monitored Scope (EnsureListItemsData). Execution Time=8.79880032784031
Leaving Monitored Scope (EnsureListItemsData#1). Execution Time=9.3416421251...
Leaving Monitored Scope (CachedObjectFactory: Caching ListItem at: /Pages/Ho...
Leaving Monitored Scope (Activate web part connections). Execution Time=152....
Leaving Monitored Scope (CachedObjectFactory: Caching ListItem at: Pages/Hom...
Leaving Monitored Scope (DataBinding DataFormWebPart (Announcement)). Execut...
Leaving Monitored Scope (EnsureListItemsData#3). Execution Time=146.96476702...
Leaving Monitored Scope (EnsureListItemsData#4). Execution Time=69.062041643...
System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxx...Hi,
It will be better if you can give us more information about what you do to get the correlation error id.
We can also to find the error from the ULS log by the following ULS Viewer, it will be easier and better to find the details error.
http://habaneroconsulting.com/insights/An-Even-Better-Way-to-Get-the-Real-SharePoint-Error#.VAQARvmSzkI
http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support -
Just starting to build digital wave replace for counter signal in my DAQ.
I can't get logical AND result as shown in attachment.
In case of irregular pulses, How to build up or edit digital waveform more conveniently?
Attachments:
digital.jpg 68 KBHi Labmaster,
It appears to me that in your graph picture, you show "plot 0" offset from "line 1" by 1/2 of a clock period.
This would mean that for each clock period in "line 1" there are two possible states for "plot 0". That creates a
problem when trying to line up the data for comparison.
If you double the sample rate you could get back to a 1 to 1 correlation.
The attached example uses twice the number of samples for the same amount of data (as your example) and allows
you to select a logic operation on the two waveforms.
I hope this is helpful,
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help.
Attachments:
dig wfm.vi 41 KB -
Digital ı/o problem in mseries 6229 daq card
In our lab, we have a 6229 M series daq card. We want to send digital output ,
( three square waves and their direction values for driving 3 dc motors.
We will change pulses or frequencies during application). we tried to send the signals from single lines
(altogether we need 6 lines.) but we failed. We could only send pulses from counter ports but
unfortunately there are only 2 counter ports. Can anybody help us about this problem?
If anybody could also send a labview 7.x program for this application we will be thankful.Hi,
You can use the correlated dio functionality of your M series board to output digital waveforms. However, you will need to construct the waveform before actually outputting the data. Here is the link to another discussion forum with more information on this including links to examples: How do I output a digital waveform?
Regards,
Hal L. -
1mS Digital aquisition realistic for AI-16XE-50/Pentium/Win98?
I'm trying to sample digital levels + buffered period measurement at 1mS
or better. Setting the tick counter for 1mS intervals apparently causes
too much overhead on my old laptop, and the samples are 3-4 mS intervals
at best. Running the acquisition loop flat out with no waiting will
sample the digitals at barely 1mS or faster, but some buffered period
measurement samples are missing, even though it's contained within the
same acquire loop. D'oh! Since the period measurement is apparently the
slowest, I'm thinking there should be a way to hold off the digital
sampling until the period measurement is done, so they all have the same
time correlation, but I dunno how, seein' as I 'aint never tried this
here Lab
view stuff before.
DougDoug,
Win 98 is not a real-time (deterministic) operating system... you're always
going to loose samples and the interval will never be precise.
I haven't used it but, I believe NI makes a LabView RealTime version that
actually uses a separate interrupt driven microprocessor on one of their DAQ
boards to do the periodic sampling... at least that's how I think it works?
Are you trying to trap really narrow spikes or could an averaging technique
be used to average out the varying period?
Bill
D. Berry wrote in message
news:[email protected]..
> I'm trying to sample digital levels + buffered period measurement at 1mS
> or better. Setting the tick counter for 1mS intervals apparently causes
> too much overhead on my old la
ptop, and the samples are 3-4 mS intervals
> at best. Running the acquisition loop flat out with no waiting will
> sample the digitals at barely 1mS or faster, but some buffered period
> measurement samples are missing, even though it's contained within the
> same acquire loop. D'oh! Since the period measurement is apparently the
> slowest, I'm thinking there should be a way to hold off the digital
> sampling until the period measurement is done, so they all have the same
> time correlation, but I dunno how, seein' as I 'aint never tried this
> here Labview stuff before.
>
> Doug
> -
Interface with I2C SDA and SCL with PCI 6224 digital ouputs in C/C++
I am trying to use the pci 6224 in order to send SDA and SCL to an I2C. I have been able to control the Digital Output, but I have been unsuccessful with generating a clock source to satify the I2C. I am writing this code in C/C++. Any ideas or examples would surely be appreciated. I need a good starting point, but I have not been able to find any useful examples that have worked. I am using the SCB-68 and I am trying to use my digital multi-meter to verify my code.
I have looked at the examples provided, but is there a description of these functions that are being called using the NIDAQmx.h?Hello VJohnson,
The counter will give you control of the clock frequency and duty cycle. However, this card also has correlated DIO, which means that you can clock your digital lines. Because of this, you can write a specific pattern (101010) to the buffer and just have it continuously output. However, you will have to write this in a way that you know what values you're writing based on the part of the clock you're at.
My I2C implemetation knowledge isn't the greatest, so I do not know how big each of your communication packets will be, but one implemetation would be to write your data in packets to regulate your SDA and SCL lines. The WriteDigChan-ExtClk is the best option that shows how to write a digital channel with a clock. You will just need to modify the DAQmxCfgSampClkTiming( function call. The second input should be changed from "/Dev1/PFI0" to OnboardClock or NULL. Hope this helps!
ColeR
Field Engineer -
Newbie: 6020E (USB) slow performance with mixed digital and analog input
Hi,
I'm using a 6020E to do analog and digital input, and I'm getting very bad performance.
Please note that doing IO in Labview is new to me!
I have read the post about 6020E slow performance, and it says I should do buffered IO.
Can anybody point me to some DOC or SAMPLE that actually shows or explains how one should do this. I need to read several digital IO lines (which I can combine in one port-read), and several analog inputs.
Seeing how slow the reading on the 6020E is, I am amazed there is only one post that deals with this issue.
I would be satisfied to get the 6020E into some sort of continuous read mode so that whenever I need data, I get the latest reading right away.
thanks,
Peter D'HoyeHi Peter,
Your cannot do buffered digital I/O with your daqpad. It doesn't have that capability. You can only make direct software calls with digital read/write from/to your port. So your digital IO is completely software clocked and not hardware clocked. The example you are trying is only for specific Simultanuous sampling boards or now also for M-series boards that are able to do correlated DIO.
Use the Cont Acq&Graph Voltage-Int Clk.vi example for your analog measurements. (NI Example Finder) For your digital IO you can only use the examples like Read Dig Chan.vi, Read Dig Port,...
There are indeed some slow performance issues with single point I/O Operations, that is correct.
Check the explaination below:
DAQPads are offered for the Universal Serial Bus (USB) and the IEEE 1394 (also known as FireWire). Both of these standards use a high-speed serial communication protocol between the computer and the device with a bandwidth up to 12 MB/s for USB and 400 MB/s for FireWire.
During a single point operation, the DAQ device requires a complete set of configuration commands. This is done through serial communication (USB or FireWire), making the process slower than in a PCI-based board. The speed obtained for single point operation in a DAQPad is system dependent; this means that your computer processor, memory, bus speed, and other factors alter the speed at which you can do single-point operations with a DAQPad.
For example, on the DAQPad-6020E, timed non-buffered analog input operations are limited to about 50 Hz. At higher rates, the software may become unresponsive. On a FireWire device, you can expect stable operation around 3,000 Hz. But again, these figures are system dependent.
Regards.
JV
NI -
XOrg crashes correlated to Java (?)
I am experiencing several XOrg crashes, that seem strongly correlated to Java problems. It happens when I open GeoGebra or when I try to open some Java applets online. The same thing also happens, although not systematically, when I search for a font on XFCE settings, simply scrolling the list of fonts available.
I realize this is too little information but I have no clue of what the cause of the problem may be.
Thanks for help.Here are the results of the logs obtained with the dmesg command. The messages are the same after the execution of the Java application or after font search for selection (followed by XOrg crash):
[117564.463200] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[117564.463205] [drm] PCIE gen 2 link speeds already enabled
[117564.465904] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
[117564.466266] radeon 0000:03:00.0: WB enabled
[117564.466268] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88024d4c9c00
[117564.466270] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88024d4c9c04
[117564.466272] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88024d4c9c08
[117564.466273] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88024d4c9c0c
[117564.466274] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88024d4c9c10
[117564.467814] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90023035a18
[117564.659791] [drm] ring test on 0 succeeded in 1 usecs
[117564.659796] [drm] ring test on 1 succeeded in 1 usecs
[117564.659800] [drm] ring test on 2 succeeded in 1 usecs
[117564.659808] [drm] ring test on 3 succeeded in 4 usecs
[117564.659815] [drm] ring test on 4 succeeded in 4 usecs
[117564.847070] [drm] ring test on 5 succeeded in 2 usecs
[117564.847077] [drm] UVD initialized successfully.
[117564.847107] [drm] ib test on ring 0 succeeded in 0 usecs
[117564.847135] [drm] ib test on ring 1 succeeded in 0 usecs
[117564.847163] [drm] ib test on ring 2 succeeded in 0 usecs
[117564.847190] [drm] ib test on ring 3 succeeded in 0 usecs
[117564.847219] [drm] ib test on ring 4 succeeded in 1 usecs
[117564.999064] [drm] ib test on ring 5 succeeded
This is what is on the file /var/log/Xorg.0.log after a crash caused by a Java application.
[117928.492]
X.Org X Server 1.16.2
Release Date: 2014-11-10
[117928.492] X Protocol Version 11, Revision 0
[117928.492] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[117928.492] Current Operating System: Linux XxX 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64
[117928.493] Kernel command line: initrd=\initramfs-linux.img root=/dev/sda5 rw
[117928.493] Build Date: 10 November 2014 07:52:13PM
[117928.493]
[117928.493] Current version of pixman: 0.32.6
[117928.493] Before reporting problems, check [url]http://wiki.x.org[/url]
to make sure that you have the latest version.
[117928.493] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[117928.493] (==) Log file: "/var/log/Xorg.0.log", Time: Sun May 3 17:48:45 2015
[117928.493] (==) Using config directory: "/etc/X11/xorg.conf.d"
[117928.493] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[117928.493] (==) No Layout section. Using the first Screen section.
[117928.493] (==) No screen section available. Using defaults.
[117928.493] (**) |-->Screen "Default Screen Section" (0)
[117928.493] (**) | |-->Monitor "<default monitor>"
[117928.493] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[117928.493] (==) Automatically adding devices
[117928.493] (==) Automatically enabling devices
[117928.493] (==) Automatically adding GPU devices
[117928.493] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[117928.493] Entry deleted from font path.
[117928.493] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[117928.493] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[117928.493] Entry deleted from font path.
[117928.493] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[117928.493] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[117928.493] (==) ModulePath set to "/usr/lib/xorg/modules"
[117928.493] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[117928.493] (II) Loader magic: 0x818d80
[117928.493] (II) Module ABI versions:
[117928.493] X.Org ANSI C Emulation: 0.4
[117928.493] X.Org Video Driver: 18.0
[117928.493] X.Org XInput driver : 21.0
[117928.493] X.Org Server Extension : 8.0
[117928.495] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c7
[117928.495] (II) xfree86: Adding drm device (/dev/dri/card0)
[117928.495] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[117928.495] (II) xfree86: Adding drm device (/dev/dri/card1)
[117928.495] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 9 paused 0
[117928.496] (--) PCI:*(0:0:2:0) 8086:0a16:1025:0775 rev 9, Mem @ 0xc0000000/4194304, 0xb0000000/268435456, I/O @ 0x00004000/64
[117928.496] (--) PCI: (0:3:0:0) 1002:6600:1025:0776 rev 0, Mem @ 0xa0000000/268435456, 0xc0500000/262144, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
[117928.496] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[117928.496] (II) LoadModule: "glx"
[117928.496] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[117928.497] (II) Module glx: vendor="X.Org Foundation"
[117928.497] compiled for 1.16.2, module version = 1.0.0
[117928.497] ABI class: X.Org Server Extension, version 8.0
[117928.497] (==) AIGLX enabled
[117928.497] (==) Matched intel as autoconfigured driver 0
[117928.497] (==) Matched ati as autoconfigured driver 1
[117928.497] (==) Matched intel as autoconfigured driver 2
[117928.497] (==) Matched modesetting as autoconfigured driver 3
[117928.497] (==) Matched fbdev as autoconfigured driver 4
[117928.497] (==) Matched vesa as autoconfigured driver 5
[117928.497] (==) Assigned the driver to the xf86ConfigLayout
[117928.497] (II) LoadModule: "intel"
[117928.497] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[117928.497] (II) Module intel: vendor="X.Org Foundation"
[117928.497] compiled for 1.16.1, module version = 2.99.916
[117928.497] Module class: X.Org Video Driver
[117928.497] ABI class: X.Org Video Driver, version 18.0
[117928.497] (II) LoadModule: "ati"
[117928.497] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[117928.497] (II) Module ati: vendor="X.Org Foundation"
[117928.497] compiled for 1.16.1, module version = 7.5.0
[117928.498] Module class: X.Org Video Driver
[117928.498] ABI class: X.Org Video Driver, version 18.0
[117928.498] (II) LoadModule: "radeon"
[117928.498] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[117928.498] (II) Module radeon: vendor="X.Org Foundation"
[117928.498] compiled for 1.16.1, module version = 7.5.0
[117928.498] Module class: X.Org Video Driver
[117928.498] ABI class: X.Org Video Driver, version 18.0
[117928.498] (II) LoadModule: "modesetting"
[117928.498] (WW) Warning, couldn't open module modesetting
[117928.498] (II) UnloadModule: "modesetting"
[117928.498] (II) Unloading modesetting
[117928.498] (EE) Failed to load module "modesetting" (module does not exist, 0)
[117928.498] (II) LoadModule: "fbdev"
[117928.498] (WW) Warning, couldn't open module fbdev
[117928.498] (II) UnloadModule: "fbdev"
[117928.498] (II) Unloading fbdev
[117928.498] (EE) Failed to load module "fbdev" (module does not exist, 0)
[117928.498] (II) LoadModule: "vesa"
[117928.498] (WW) Warning, couldn't open module vesa
[117928.498] (II) UnloadModule: "vesa"
[117928.498] (II) Unloading vesa
[117928.498] (EE) Failed to load module "vesa" (module does not exist, 0)
[117928.498] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[117928.498] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[117928.498] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[117928.498] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[117928.498] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
ATI Mobility Radeon HD 4670, ATI FirePro M5750,
ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
SUMO, SUMO, SUMO2, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
ATI Radeon 4100, ATI Mobility Radeon HD 4200,
ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
AMD Radeon HD 6300 Series Graphics,
AMD Radeon HD 6200 Series Graphics, PALM, PALM, PALM, CYPRESS,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
AMD Firestream 9350, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
ATI Mobility Radeon HD 5800 Series,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
ATI Mobility Radeon Graphics, CEDAR,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
BARTS, BARTS, Mobility Radeon HD 6000 Series,
Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
HAINAN, HAINAN, HAINAN, HAINAN, HAINAN, HAINAN, BONAIRE, BONAIRE,
BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE,
BONAIRE, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
MULLINS, MULLINS, MULLINS, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
[117928.501] (++) using VT number 1
[117928.501] (--) controlling tty is VT number 1, auto-enabling KeepTty
[117928.501] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140725
[117928.501] (II) [KMS] Kernel modesetting enabled.
[117928.501] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4400
[117928.502] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
[117928.502] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[117928.502] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[117928.502] (==) intel(0): RGB weight 888
[117928.502] (==) intel(0): Default visual is TrueColor
[117928.502] (II) intel(0): Output eDP1 has no monitor section
[117928.502] (--) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[117928.502] (II) intel(0): Enabled output eDP1
[117928.502] (II) intel(0): Output DP1 has no monitor section
[117928.502] (II) intel(0): Enabled output DP1
[117928.502] (II) intel(0): Output HDMI1 has no monitor section
[117928.502] (II) intel(0): Enabled output HDMI1
[117928.502] (II) intel(0): Output HDMI2 has no monitor section
[117928.502] (II) intel(0): Enabled output HDMI2
[117928.502] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[117928.502] (II) intel(0): Output VIRTUAL1 has no monitor section
[117928.502] (II) intel(0): Enabled output VIRTUAL1
[117928.502] (--) intel(0): Output eDP1 using initial mode 1366x768 on pipe 0
[117928.502] (==) intel(0): TearFree disabled
[117928.502] (==) intel(0): DPI set to (96, 96)
[117928.502] (II) Loading sub module "dri2"
[117928.502] (II) LoadModule: "dri2"
[117928.502] (II) Module "dri2" already built-in
[117928.502] (II) Loading sub module "present"
[117928.502] (II) LoadModule: "present"
[117928.502] (II) Module "present" already built-in
[117928.502] (==) RADEON(G0): Depth 24, (--) framebuffer bpp 32
[117928.502] (II) RADEON(G0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[117928.502] (==) RADEON(G0): Default visual is TrueColor
[117928.502] (==) RADEON(G0): RGB weight 888
[117928.502] (II) RADEON(G0): Using 8 bits per RGB (8 bit DAC)
[117928.502] (--) RADEON(G0): Chipset: "OLAND" (ChipID = 0x6600)
[117928.502] (II) Loading sub module "dri2"
[117928.502] (II) LoadModule: "dri2"
[117928.502] (II) Module "dri2" already built-in
[117928.502] (II) Loading sub module "glamoregl"
[117928.502] (II) LoadModule: "glamoregl"
[117928.502] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[117928.505] (II) Module glamoregl: vendor="X.Org Foundation"
[117928.505] compiled for 1.16.2, module version = 1.0.0
[117928.505] ABI class: X.Org ANSI C Emulation, version 0.4
[117928.505] (II) glamor: OpenGL accelerated X.org driver based.
[117928.538] (II) glamor: EGL version 1.4 (DRI2):
[117928.549] (II) RADEON(G0): glamor detected, initialising EGL layer.
[117928.549] (II) RADEON(G0): KMS Color Tiling: enabled
[117928.549] (II) RADEON(G0): KMS Color Tiling 2D: enabled
[117928.549] (II) RADEON(G0): KMS Pageflipping: enabled
[117928.549] (II) RADEON(G0): SwapBuffers wait for vsync: enabled
[117928.549] (II) RADEON(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[117928.549] (II) RADEON(G0): mem size init: gart size :3fbce000 vram size: s:80000000 visible:7f888000
[117928.549] (==) RADEON(G0): DPI set to (96, 96)
[117928.549] (II) Loading sub module "fb"
[117928.549] (II) LoadModule: "fb"
[117928.549] (II) Loading /usr/lib/xorg/modules/libfb.so
[117928.549] (II) Module fb: vendor="X.Org Foundation"
[117928.549] compiled for 1.16.2, module version = 1.0.0
[117928.549] ABI class: X.Org ANSI C Emulation, version 0.4
[117928.549] (II) Loading sub module "ramdac"
[117928.549] (II) LoadModule: "ramdac"
[117928.549] (II) Module "ramdac" already built-in
[117928.549] (==) Depth 24 pixmap format is 32 bpp
[117928.549] (II) RADEON(G0): [DRI2] Setup complete
[117928.549] (II) RADEON(G0): [DRI2] DRI driver: radeonsi
[117928.549] (II) RADEON(G0): [DRI2] VDPAU driver: radeonsi
[117928.549] (II) RADEON(G0): Front buffer size: 3072K
[117928.549] (II) RADEON(G0): VRAM usage limit set to 1877760K
[117928.549] (==) RADEON(G0): Backing store enabled
[117928.549] (II) RADEON(G0): Direct rendering enabled
[117928.610] (II) RADEON(G0): Use GLAMOR acceleration.
[117928.610] (II) RADEON(G0): Acceleration enabled
[117928.610] (==) RADEON(G0): DPMS enabled
[117928.610] (==) RADEON(G0): Silken mouse enabled
[117928.612] (II) RADEON(G0): Set up textured video (glamor)
[117928.612] (II) RADEON(G0): [XvMC] Associated with GLAMOR Textured Video.
[117928.612] (II) RADEON(G0): [XvMC] Extension initialized.
[117928.612] (II) RADEON(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
[117928.612] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[117928.612] (==) intel(0): Backing store enabled
[117928.612] (==) intel(0): Silken mouse enabled
[117928.612] (II) intel(0): HW Cursor enabled
[117928.612] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[117928.612] (==) intel(0): DPMS enabled
[117928.612] (II) intel(0): [DRI2] Setup complete
[117928.612] (II) intel(0): [DRI2] DRI driver: i965
[117928.612] (II) intel(0): [DRI2] VDPAU driver: i965
[117928.612] (II) intel(0): direct rendering: DRI2 enabled
[117928.612] (II) intel(0): hardware support for Present enabled
[117928.612] (==) intel(0): display hotplug detection enabled
[117928.612] (--) RandR disabled
[117928.624] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[117928.624] (II) AIGLX: enabled GLX_ARB_create_context
[117928.624] (II) AIGLX: enabled GLX_ARB_create_context_profile
[117928.624] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[117928.624] (II) AIGLX: enabled GLX_INTEL_swap_event
[117928.624] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[117928.624] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[117928.624] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[117928.624] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[117928.624] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[117928.624] (II) AIGLX: Loaded and initialized i965
[117928.624] (II) GLX: Initialized DRI2 GL provider for screen 0
[117928.638] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[117928.648] (II) intel(0): Setting screen physical size to 361 x 203
[117928.668] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[117928.669] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[117928.669] (**) Power Button: Applying InputClass "Keyboard Defaults"
[117928.669] (II) LoadModule: "evdev"
[117928.669] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[117928.669] (II) Module evdev: vendor="X.Org Foundation"
[117928.669] compiled for 1.16.0, module version = 2.9.0
[117928.669] Module class: X.Org XInput Driver
[117928.669] ABI class: X.Org XInput driver, version 21.0
[117928.669] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 18 paused 0
[117928.669] (II) Using input driver 'evdev' for 'Power Button'
[117928.669] (**) Power Button: always reports core events
[117928.669] (**) evdev: Power Button: Device: "/dev/input/event6"
[117928.669] (--) evdev: Power Button: Vendor 0 Product 0x1
[117928.669] (--) evdev: Power Button: Found keys
[117928.669] (II) evdev: Power Button: Configuring as keyboard
[117928.669] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event6"
[117928.669] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[117928.669] (**) Option "xkb_rules" "evdev"
[117928.669] (**) Option "xkb_model" "pc104"
[117928.669] (**) Option "xkb_layout" "it"
[117928.683] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
[117928.683] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[117928.683] (**) Video Bus: Applying InputClass "Keyboard Defaults"
[117928.683] (II) systemd-logind: got fd for /dev/input/event13 13:77 fd 19 paused 0
[117928.683] (II) Using input driver 'evdev' for 'Video Bus'
[117928.683] (**) Video Bus: always reports core events
[117928.683] (**) evdev: Video Bus: Device: "/dev/input/event13"
[117928.683] (--) evdev: Video Bus: Vendor 0 Product 0x6
[117928.683] (--) evdev: Video Bus: Found keys
[117928.683] (II) evdev: Video Bus: Configuring as keyboard
[117928.683] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input14/event13"
[117928.683] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[117928.683] (**) Option "xkb_rules" "evdev"
[117928.683] (**) Option "xkb_model" "pc104"
[117928.683] (**) Option "xkb_layout" "it"
[117928.684] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[117928.684] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[117928.684] (**) Power Button: Applying InputClass "Keyboard Defaults"
[117928.684] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 20 paused 0
[117928.684] (II) Using input driver 'evdev' for 'Power Button'
[117928.684] (**) Power Button: always reports core events
[117928.684] (**) evdev: Power Button: Device: "/dev/input/event4"
[117928.684] (--) evdev: Power Button: Vendor 0 Product 0x1
[117928.684] (--) evdev: Power Button: Found keys
[117928.684] (II) evdev: Power Button: Configuring as keyboard
[117928.684] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input5/event4"
[117928.684] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[117928.684] (**) Option "xkb_rules" "evdev"
[117928.684] (**) Option "xkb_model" "pc104"
[117928.684] (**) Option "xkb_layout" "it"
[117928.684] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
[117928.684] (II) No input driver specified, ignoring this device.
[117928.684] (II) This device may have been added with another device file.
[117928.684] (II) config/udev: Adding input device Sleep Button (/dev/input/event5)
[117928.684] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[117928.684] (**) Sleep Button: Applying InputClass "Keyboard Defaults"
[117928.685] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 21 paused 0
[117928.685] (II) Using input driver 'evdev' for 'Sleep Button'
[117928.685] (**) Sleep Button: always reports core events
[117928.685] (**) evdev: Sleep Button: Device: "/dev/input/event5"
[117928.685] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[117928.685] (--) evdev: Sleep Button: Found keys
[117928.685] (II) evdev: Sleep Button: Configuring as keyboard
[117928.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0E:00/input/input6/event5"
[117928.685] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[117928.685] (**) Option "xkb_rules" "evdev"
[117928.685] (**) Option "xkb_model" "pc104"
[117928.685] (**) Option "xkb_layout" "it"
[117928.685] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
[117928.685] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[117928.685] (**) Video Bus: Applying InputClass "Keyboard Defaults"
[117928.685] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 22 paused 0
[117928.685] (II) Using input driver 'evdev' for 'Video Bus'
[117928.685] (**) Video Bus: always reports core events
[117928.685] (**) evdev: Video Bus: Device: "/dev/input/event12"
[117928.685] (--) evdev: Video Bus: Vendor 0 Product 0x6
[117928.685] (--) evdev: Video Bus: Found keys
[117928.685] (II) evdev: Video Bus: Configuring as keyboard
[117928.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:38/LNXVIDEO:00/input/input13/event12"
[117928.685] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 10)
[117928.685] (**) Option "xkb_rules" "evdev"
[117928.685] (**) Option "xkb_model" "pc104"
[117928.685] (**) Option "xkb_layout" "it"
[117928.686] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event14)
[117928.686] (II) No input driver specified, ignoring this device.
[117928.686] (II) This device may have been added with another device file.
[117928.686] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event15)
[117928.686] (II) No input driver specified, ignoring this device.
[117928.686] (II) This device may have been added with another device file.
[117928.686] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event16)
[117928.686] (II) No input driver specified, ignoring this device.
[117928.686] (II) This device may have been added with another device file.
[117928.686] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[117928.686] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[117928.687] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 23 paused 0
[117928.687] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[117928.687] (**) Logitech USB Receiver: always reports core events
[117928.687] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event1"
[117928.687] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52f
[117928.687] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[117928.687] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[117928.687] (--) evdev: Logitech USB Receiver: Found relative axes
[117928.687] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[117928.687] (II) evdev: Logitech USB Receiver: Configuring as mouse
[117928.687] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[117928.687] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[117928.687] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[117928.687] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C52F.0001/input/input2/event1"
[117928.687] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 11)
[117928.687] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[117928.687] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[117928.687] (**) Logitech USB Receiver: (accel) acceleration profile 0
[117928.687] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[117928.687] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[117928.687] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[117928.687] (II) No input driver specified, ignoring this device.
[117928.687] (II) This device may have been added with another device file.
[117928.687] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[117928.687] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[117928.687] (**) Logitech USB Receiver: Applying InputClass "Keyboard Defaults"
[117928.687] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 24 paused 0
[117928.687] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[117928.687] (**) Logitech USB Receiver: always reports core events
[117928.688] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event2"
[117928.688] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52f
[117928.688] (--) evdev: Logitech USB Receiver: Found 1 mouse buttons
[117928.688] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[117928.688] (--) evdev: Logitech USB Receiver: Found relative axes
[117928.688] (II) evdev: Logitech USB Receiver: Forcing relative x/y axes to exist.
[117928.688] (--) evdev: Logitech USB Receiver: Found absolute axes
[117928.688] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[117928.688] (--) evdev: Logitech USB Receiver: Found keys
[117928.688] (II) evdev: Logitech USB Receiver: Configuring as mouse
[117928.688] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[117928.688] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[117928.688] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[117928.688] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[117928.688] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:046D:C52F.0002/input/input3/event2"
[117928.688] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 12)
[117928.688] (**) Option "xkb_rules" "evdev"
[117928.688] (**) Option "xkb_model" "pc104"
[117928.688] (**) Option "xkb_layout" "it"
[117928.688] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[117928.688] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[117928.688] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[117928.688] (**) Logitech USB Receiver: (accel) acceleration profile 0
[117928.688] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[117928.688] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[117928.688] (II) config/udev: Adding input device HD WebCam (/dev/input/event10)
[117928.688] (**) HD WebCam: Applying InputClass "evdev keyboard catchall"
[117928.688] (**) HD WebCam: Applying InputClass "Keyboard Defaults"
[117928.688] (II) systemd-logind: got fd for /dev/input/event10 13:74 fd 25 paused 0
[117928.688] (II) Using input driver 'evdev' for 'HD WebCam'
[117928.688] (**) HD WebCam: always reports core events
[117928.688] (**) evdev: HD WebCam: Device: "/dev/input/event10"
[117928.688] (--) evdev: HD WebCam: Vendor 0x4f2 Product 0xb3f6
[117928.688] (--) evdev: HD WebCam: Found keys
[117928.688] (II) evdev: HD WebCam: Configuring as keyboard
[117928.688] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/input/input12/event10"
[117928.688] (II) XINPUT: Adding extended input device "HD WebCam" (type: KEYBOARD, id 13)
[117928.688] (**) Option "xkb_rules" "evdev"
[117928.688] (**) Option "xkb_model" "pc104"
[117928.688] (**) Option "xkb_layout" "it"
[117928.689] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event17)
[117928.689] (II) No input driver specified, ignoring this device.
[117928.689] (II) This device may have been added with another device file.
[117928.689] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event18)
[117928.689] (II) No input driver specified, ignoring this device.
[117928.689] (II) This device may have been added with another device file.
[117928.689] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event19)
[117928.689] (II) No input driver specified, ignoring this device.
[117928.689] (II) This device may have been added with another device file.
[117928.689] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[117928.689] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[117928.689] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
[117928.689] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 26 paused 0
[117928.689] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[117928.689] (**) AT Translated Set 2 keyboard: always reports core events
[117928.689] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[117928.689] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[117928.689] (--) evdev: AT Translated Set 2 keyboard: Found keys
[117928.689] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[117928.689] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[117928.689] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
[117928.689] (**) Option "xkb_rules" "evdev"
[117928.689] (**) Option "xkb_model" "pc104"
[117928.689] (**) Option "xkb_layout" "it"
[117928.690] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event11)
[117928.690] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[117928.690] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[117928.690] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[117928.690] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[117928.690] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[117928.690] (II) LoadModule: "synaptics"
[117928.690] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[117928.690] (II) Module synaptics: vendor="X.Org Foundation"
[117928.690] compiled for 1.16.0, module version = 1.8.1
[117928.690] Module class: X.Org XInput Driver
[117928.690] ABI class: X.Org XInput driver, version 21.0
[117928.690] (II) systemd-logind: got fd for /dev/input/event11 13:75 fd 27 paused 0
[117928.690] (II) Using input driver 'synaptics' for 'ETPS/2 Elantech Touchpad'
[117928.690] (**) ETPS/2 Elantech Touchpad: always reports core events
[117928.690] (**) Option "Device" "/dev/input/event11"
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: x-axis range 0 - 2960 (res 0)
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: y-axis range 0 - 1480 (res 0)
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: pressure range 0 - 255
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: finger width range 0 - 15
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: buttons: left right double triple
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: Vendor 0x2 Product 0xe
[117928.738] (**) Option "AreaLeftEdge" "600"
[117928.738] (**) Option "AreaRightEdge" "2200"
[117928.738] (**) Option "VertTwoFingerScroll" "on"
[117928.738] (**) Option "HorizTwoFingerScroll" "on"
[117928.738] (**) Option "TapButton1" "1"
[117928.738] (**) Option "TapButton2" "2"
[117928.738] (**) Option "TapButton3" "3"
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[117928.738] (**) ETPS/2 Elantech Touchpad: always reports core events
[117928.738] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event11"
[117928.738] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 15)
[117928.738] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[117928.738] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MaxSpeed is now 1.75
[117928.738] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) AccelFactor is now 0.060
[117928.738] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[117928.738] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 1
[117928.738] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[117928.738] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[117928.738] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[117928.738] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1)
[117928.738] (**) ETPS/2 Elantech Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"
[117928.739] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
[117928.739] (II) No input driver specified, ignoring this device.
[117928.739] (II) This device may have been added with another device file.
[117928.739] (II) config/udev: Adding input device Acer WMI hotkeys (/dev/input/event8)
[117928.739] (**) Acer WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[117928.739] (**) Acer WMI hotkeys: Applying InputClass "Keyboard Defaults"
[117928.739] (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 28 paused 0
[117928.739] (II) Using input driver 'evdev' for 'Acer WMI hotkeys'
[117928.739] (**) Acer WMI hotkeys: always reports core events
[117928.739] (**) evdev: Acer WMI hotkeys: Device: "/dev/input/event8"
[117928.739] (--) evdev: Acer WMI hotkeys: Vendor 0 Product 0
[117928.739] (--) evdev: Acer WMI hotkeys: Found keys
[117928.739] (II) evdev: Acer WMI hotkeys: Configuring as keyboard
[117928.739] (**) Option "config_info" "udev:/sys/devices/virtual/input/input10/event8"
[117928.739] (II) XINPUT: Adding extended input device "Acer WMI hotkeys" (type: KEYBOARD, id 16)
[117928.739] (**) Option "xkb_rules" "evdev"
[117928.739] (**) Option "xkb_model" "pc104"
[117928.739] (**) Option "xkb_layout" "it"
[117928.739] (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/event9)
[117928.739] (II) No input driver specified, ignoring this device.
[117928.739] (II) This device may have been added with another device file.
[117928.740] (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/js0)
[117928.740] (II) No input driver specified, ignoring this device.
[117928.740] (II) This device may have been added with another device file.
[117928.828] (II) intel(0): EDID vendor "AUO", prod id 18668
[117928.828] (II) intel(0): Printing DDC gathered Modelines:
[117928.828] (II) intel(0): Modeline "1366x768"x0.0 76.30 1366 1404 1426 1592 768 771 777 798 -hsync -vsync (47.9 kHz eP)
[120084.521] (EE)
[120084.521] (EE) Backtrace:
[120084.521] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593d36]
[120084.521] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197e89) [0x597e89]
[120084.521] (EE) 2: /usr/lib/libc.so.6 (0x7f3abb0d9000+0x33b20) [0x7f3abb10cb20]
[120084.521] (EE)
[120084.521] (EE) Segmentation fault at address 0x0
[120084.521] (EE)
Fatal server error:
[120084.521] (EE) Caught signal 11 (Segmentation fault). Server aborting
[120084.521] (EE)
[120084.521] (EE)
Please consult the The X.Org Foundation support
at [url]http://wiki.x.org[/url]
for help.
[120084.521] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[120084.521] (EE)
[120084.521] (II) AIGLX: Suspending AIGLX clients for VT switch
[120085.500] (EE) Server terminated with error (1). Closing log file. -
Real-time - how to control speed of digital waveform
Deploying the VI attached to my RT desktop target I generate digital waveform on 8 channels on port0 and acquire data on AI [PXIe-6358].
The digital output frequency and analog input sample frequency are 10000 Hz therefore I expect that while one 8-bit digital code is active [valid] for 100us, one single analog sample is acquired. That means that I would expect one cycle of the while loop to finish in 100us x 2^8 = 100us x 256 = 25600us = 25.6ms.
However what happens is that the while loop finishes in 6ms regardless the set frequency. The loop finishes in 6ms even if I set 5/10/15kHz or if I put a 100us delay into the while loop. I also tried to set the source of the analog input sample clock to 'Dev/do/SampleClock' but nothing seemed to work so far.
How can I force the digital generation to be in correlation with the analog acquisition? I need to acquire 1 data point per channel while the respective digital code is active.
Thanks,
Krivan
Attachments:
RT_ai_dig_wave_gen.vi 56 KBHello krivan,
Thank you for your post on the forum.
Do you want the digital generation to start at the same time as the analog acquisition?
Shalini B
Applications Engineer
National Instruments UK & Ireland
Maybe you are looking for
-
DAQmx driver for DAQ 6009? Need DAQ Assistant in Block Panel palette.
Do I understand things right? The Ni USB DAQ 6009 is supported in DAQmx base and not DAQmx, or is this only true for the 6008? I need the DAQ Assistant in my LV 2009 Block Panel palette. Do I go to my Ni-DAQmx 8.8 CDs, or do I download something.
-
Flash Player works only for Local Admins
Hi! We have about 40 computers in our organisation with the same problem: Since few weeks the Adobe Flash Player (ActiveX) works only, when the user has administrative privileges. If a normal user wants to watch youtube-films or other flash objects,
-
Email buttons inactive on some emails
Certain email buttons are inactive on some of my Verizon.net - received emails: delete, move to folder. These buttons are "greyed". These messages may, going down, display the original message, a "page 2" logo and a block of Java programming comments
-
My old laptop has crashed and I'm using a new machine.
How do I go about re-downloading software (Photoshop) already purchased onto my new laptop?
-
I downloaded lion but it wont install, it says that the software has been tampered with. But i downloaded from the app store.