PCI Implementation
Hi,
Can u please guide me the how to setup Payment Card Industry.What are the security products are required and how to implement those products .
Waiting for your reply.
Regards
Sivaji.P
I think one of the first things you need to do is download the PCI Self Assessment and PCI DSS. then, depending on what policies, processes, procedures, documentation you have, make a decision as to whether you want to set out alone remediating. If your company is big and you have a long ways to go, I would suggest getting a partner to assist in remediation. We decided to do the remediation ourselves but we contracted with a company to give us a roadmap.
As far as the actual security products needed, there is nothing specifically named. It is more of a set of guidelines for minimum functionality. basically, if you go through the DSS, you can start to carve out what products will work for you in each area. I think that process took us longer than anything.
Similar Messages
-
Hello,
I am new with the PCI implementation.
I explain first my problem:
I have an older PCI program implemented on a Spartan 2, xc2s50 –pq208 (using the PCI Logicore 3.0). I would like to implement this to a new Target: Artix-7, XC7A15T- FTG256. And I need to support older PCI interfaces with my new board.
Win7, 64 bit with Vivado 2014.4.
How do I proceed?
Is there any user guide for this!
Thanks!
UmuhireHello,
Just adding other questions:
Do I need in this case to buy another Logicore? Or there is another way to reuse the same code?
Thanks
Umuhire -
Need Help on using Forge Config Manager and CAS. Questions listed in the content below
Hi All,
I have an existing Endeca pipeline implementation where we read the data sets (Product Catalog Information) from Oracle database using JDBC adapters. The data set undergoes a series of manipulation until it gets indexed to the Endeca system. We make use of PCI for dimensions and dimension values. However, we now want to extend PCI to also include the Product catalog information. The current implementation also does not make use of CAS adapters to consume the dimensions data in PCI. The next consideration is to implement PCI as close to Out of the Box provisions and standardize it. Therefore we are also considering to implement CAS.
The questions are as below:
1. What are the ideal parameters that should support the use of PCI implementation (Dataset + dimension + precedence Rules + schema information) ? Note: We DO NOT have any product catalog system (like ATG) between database and Endeca.
2. Considering that we do not have any product catalog system to organize and maintain data, how feasible is it to read directly from database through CAS Adapters and process the data ?
3. We also plan to introduce partial update pipeline in future releases. Keeping that in mind should CAS based approach help us to read from a record store at the time of partial updates ?
4.in case we are limiting to a business case of implementing partial updates in the above explained existing design, should a custom CAS approach be a better design ? Custom CAS approach = writing the baseline output data to record store and later referring it at the time of partial updates.
5. Will CAS based approach help to reduce the baseline timings ?
6. What is the best way to export data to record store instance in the above design ? (Record store API / Command line utility / CAS crawl)
Thanks,
NitinHi Neeraj,
You cam use both PI SLD and Solman Local SLD for LMDB synchronization. Now here you make to make sure that correct ranks are assigned to PI and Solman SLD. With the help of multiple sld, you can remove the cause of concern. Local SLD should always be of solman.
For CR content. that you can do for solution manager system in a click.
Divyanshu -
[POSDM] Credit card number masking
Hi Experts
We have a requirement to mask the credit card number on display (i.e. POS workbench) BUT show full card number on data level for BW data processing.
I am able to mask the card number on display through the config below:
Cross Application Component --> Payment Cards --> Make Security Settings for Payment Cards. (Masked Display and Encrypted When Saved)
Appreciate if you can kindly guide me to the setting for allowing to show the full card number on data level.
Moreover, I have searched in the note here that Installation of the encryption library "SAPCRYPTOLIB" is needed. Is it true?
PCI Implementation - Logistics - SAP Library
Thanks a lot for your help.
DominicHi Lam,
Your question is not clear,
You can achive the BW data processing from following IMG settings,
Here we can do the Enrichment/Modification of Data During Update to BW for masked credit card details,
Credit card details in BW (POS ANALYTICS) can be achived from the below datasource,
Thanks and Regards,
Ramesh D -
Z68A-GD80 use both PCIEX1 slots same time?
Hi- can't find answer to this using the search, so:
On a Z68A-GD80 motherboard, I am trying to use a PCI SATA3 card in PCIEX1_1 and PCIEX1_2 at the same time to add 4 extra SATA3 ports, but if both cards are in, only the top one is recognized. If the second one is in alone, both drives attached to that are recognized, but I cannot use all 4 extra ports at teh same time. Is there any way round this, or is this some limitation of PCI implementation?
Thanks.Ok. Need a little clarification here. To end any confusion about SATA 6Gb/s, SATA III, SATA 6.0 being confused with SATA3 which is the mainboards #3 Intel SATA II controlled port.
Is this mainboard the Z68 'B3' or 'G3'?
Excerpt from the 'B3' manual;
Slots
3 PCIE x16 slots
PCI_E2 supports up to PCIE x16 speed (when PCI_E4 is empty),
or PCI_E2 supports up to PCIE x8 speed (when PCI_E4 is installed)
PCI_E4 supports up to PCIE x8 speed
PCI_E5 supports up to PCIE x4 speed ***
(***due to the PCIE lanes limitation of chipset, when the PCI_E5 has been
installed with a PCIE x16/ x8/ x4 device, 1 eSATA port, 1 SATA port (SATA7), 1
onboard front USB 3.0 connector (JUSB4), 1 1394 port (back panel), 1 onboard
1394 connector (J1394_1) and 2 PCI slots will become unavailable.)
2 PCIE x1 slots
When both of the PCIE x1 (PCI_E1, PCI_E3) slots have been installed, only the
PCI_E1 slot is available, using one PCIE x1 slot is recommended.
Quote
I am trying to use a PCI SATA III card in PCIEX1_1 and PCIEX1_2 at the same time to add 4 extra SATA III ports, but if both cards are in, only the top one is recognized.
A PCI card can't be used in a PCI-E slot. -
Implementing a Lock In Amplifier using a PCI-6034E DAQ card
I am looking for a lock-in amplifier and have read about the Lock-in Amplifier kit provided by NI. I am wonder in is it possible to implement a solution with a PCI-6034E DAQ card instead of the 4472? And if so what would be the limitions of using the 6034 for this application?
The requirements for the Lock In Amplifier are contained within the document linked bellow. The S series can be used with the Lock In Amplifier but not the E-series.
http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/ebaadbd271adfec586256c86007b63f9?OpenDocument
Regards
Jon Bowers
Applications Engineer
NIUK -
How do you on board loop the memory using pci 6534 implementing LabVIEW. Which VI do you use?
How do you on board loop the memory using pci 6534 implementing LabVIEW. Which VI do you use?
Hello,
You will need to set the Pattern Generation Loop Enable attribute to ON in the DIO Parameter VI. This is
specified on page 2-22 of the 653x User Manual (Jan 2001)
Hope this helps,
LA -
What is PCI DSS(),how it can be implemented, it can be on Portal
Hi Frndz,
This is Rajesh am actualy EP Consultant,we have a requirment to implemet PCI DSS, n this is the first time am hearing this word.
Can anybody give me the story about PCI DSS and tell me how to implment it.
And kindly let me know it can be implement on portal(WDP java, j2ee).,if not tell me how and on what techlogies needed to implement.
Regards
RajeshDid you ever find a solution?!?
Thank you
Heiko
mawa-solutions GmbH -
[SOLVED] switching from onboard video to a pci express card
Hello,
I have an onboard video card [VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2)].
I have been running the nouveau driver, but the video card is not truly supported so I bought a [VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2)].
However my lspci -k | grep -A 2 -i "VGA" gives this:
00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2)
Subsystem: Hewlett-Packard Company Device 2a6c
Kernel driver in use: nouveau
02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2)
Subsystem: eVga.com. Corp. Device 1302
Kernel driver in use: nouveau
Kernel modules: nouveau
Subsystem: eVga.com. Corp. Device 1302
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
And my xrandr -q gives:
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA-1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 408mm x 255mm
1440x900 59.9*+ 75.0
1400x1050 60.0
1280x1024 60.0
1280x960 60.0
1152x864 75.0
1280x720 60.0
1024x768 75.1 70.1 66.0 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 72.8 75.0 66.7 60.0
720x400 70.1
I receive no output from the second card at all. Any help to troubleshoot this problem would be greatly appreciated. I simply would like to use one monitor through the VGA port on the new video card.
thanks.
Last edited by forshark (2013-05-30 19:10:25)Thanks for the reply,
My bios isn't awesome enough to allow me to disable onboard video or set a default card. I'll hunt around for the rest. Also I am using lxdm if that is helpful. Heres my Xorg.0.log:
[ 4.803]
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 4.803] X Protocol Version 11, Revision 0
[ 4.803] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 4.803] Current Operating System: Linux office 3.9.4-1-ARCH #1 SMP PREEMPT Sat May 25 16:14:55 CEST 2013 x86_64
[ 4.803] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8e550028-e5f5-40c2-b8f9-f43ac9ebf8ef ro quiet
[ 4.803] Build Date: 17 April 2013 02:37:06PM
[ 4.803]
[ 4.803] Current version of pixman: 0.30.0
[ 4.803] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4.803] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.803] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 30 12:51:52 2013
[ 4.807] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4.808] (==) No Layout section. Using the first Screen section.
[ 4.808] (==) No screen section available. Using defaults.
[ 4.808] (**) |-->Screen "Default Screen Section" (0)
[ 4.808] (**) | |-->Monitor "<default monitor>"
[ 4.808] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 4.808] (==) Automatically adding devices
[ 4.808] (==) Automatically enabling devices
[ 4.808] (==) Automatically adding GPU devices
[ 4.812] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 4.812] Entry deleted from font path.
[ 4.813] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 4.813] Entry deleted from font path.
[ 4.813] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 4.813] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 4.813] Entry deleted from font path.
[ 4.813] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 4.813] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 4.813] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4.813] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4.813] (II) Loader magic: 0x7fcc20
[ 4.813] (II) Module ABI versions:
[ 4.813] X.Org ANSI C Emulation: 0.4
[ 4.813] X.Org Video Driver: 14.1
[ 4.813] X.Org XInput driver : 19.1
[ 4.813] X.Org Server Extension : 7.0
[ 4.814] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 4.814] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 4.816] (--) PCI:*(0:0:13:0) 10de:03d0:103c:2a6c rev 162, Mem @ 0xfc000000/16777216, 0xc0000000/268435456, 0xfb000000/16777216, BIOS @ 0x????????/131072
[ 4.816] (--) PCI: (0:2:0:0) 10de:10c3:3842:1302 rev 162, Mem @ 0xf9000000/16777216, 0xd0000000/268435456, 0xee000000/33554432, I/O @ 0x0000dc00/128, BIOS @ 0x????????/524288
[ 4.816] Initializing built-in extension Generic Event Extension
[ 4.816] Initializing built-in extension SHAPE
[ 4.816] Initializing built-in extension MIT-SHM
[ 4.816] Initializing built-in extension XInputExtension
[ 4.816] Initializing built-in extension XTEST
[ 4.816] Initializing built-in extension BIG-REQUESTS
[ 4.816] Initializing built-in extension SYNC
[ 4.816] Initializing built-in extension XKEYBOARD
[ 4.816] Initializing built-in extension XC-MISC
[ 4.816] Initializing built-in extension SECURITY
[ 4.816] Initializing built-in extension XINERAMA
[ 4.816] Initializing built-in extension XFIXES
[ 4.816] Initializing built-in extension RENDER
[ 4.816] Initializing built-in extension RANDR
[ 4.816] Initializing built-in extension COMPOSITE
[ 4.816] Initializing built-in extension DAMAGE
[ 4.816] Initializing built-in extension MIT-SCREEN-SAVER
[ 4.816] Initializing built-in extension DOUBLE-BUFFER
[ 4.816] Initializing built-in extension RECORD
[ 4.816] Initializing built-in extension DPMS
[ 4.816] Initializing built-in extension X-Resource
[ 4.817] Initializing built-in extension XVideo
[ 4.817] Initializing built-in extension XVideo-MotionCompensation
[ 4.817] Initializing built-in extension XFree86-VidModeExtension
[ 4.817] Initializing built-in extension XFree86-DGA
[ 4.817] Initializing built-in extension XFree86-DRI
[ 4.817] Initializing built-in extension DRI2
[ 4.817] (II) LoadModule: "glx"
[ 4.818] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4.822] (II) Module glx: vendor="X.Org Foundation"
[ 4.822] compiled for 1.14.1, module version = 1.0.0
[ 4.822] ABI class: X.Org Server Extension, version 7.0
[ 4.822] (==) AIGLX enabled
[ 4.823] Loading extension GLX
[ 4.823] (==) Matched nouveau as autoconfigured driver 0
[ 4.823] (==) Matched nvidia as autoconfigured driver 1
[ 4.823] (==) Matched nv as autoconfigured driver 2
[ 4.823] (==) Matched nouveau as autoconfigured driver 3
[ 4.823] (==) Matched nvidia as autoconfigured driver 4
[ 4.823] (==) Matched nv as autoconfigured driver 5
[ 4.823] (==) Matched nouveau as autoconfigured driver 6
[ 4.823] (==) Matched nvidia as autoconfigured driver 7
[ 4.823] (==) Matched nv as autoconfigured driver 8
[ 4.823] (==) Matched vesa as autoconfigured driver 9
[ 4.823] (==) Matched modesetting as autoconfigured driver 10
[ 4.823] (==) Matched fbdev as autoconfigured driver 11
[ 4.823] (==) Assigned the driver to the xf86ConfigLayout
[ 4.823] (II) LoadModule: "nouveau"
[ 4.823] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 4.826] (II) Module nouveau: vendor="X.Org Foundation"
[ 4.826] compiled for 1.14.0, module version = 1.0.7
[ 4.826] Module class: X.Org Video Driver
[ 4.826] ABI class: X.Org Video Driver, version 14.1
[ 4.826] (II) LoadModule: "nvidia"
[ 4.827] (WW) Warning, couldn't open module nvidia
[ 4.827] (II) UnloadModule: "nvidia"
[ 4.827] (II) Unloading nvidia
[ 4.827] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 4.827] (II) LoadModule: "nv"
[ 4.827] (WW) Warning, couldn't open module nv
[ 4.827] (II) UnloadModule: "nv"
[ 4.827] (II) Unloading nv
[ 4.827] (EE) Failed to load module "nv" (module does not exist, 0)
[ 4.827] (II) LoadModule: "vesa"
[ 4.827] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 4.828] (II) Module vesa: vendor="X.Org Foundation"
[ 4.828] compiled for 1.14.0, module version = 2.3.2
[ 4.828] Module class: X.Org Video Driver
[ 4.828] ABI class: X.Org Video Driver, version 14.1
[ 4.828] (II) LoadModule: "modesetting"
[ 4.828] (WW) Warning, couldn't open module modesetting
[ 4.828] (II) UnloadModule: "modesetting"
[ 4.828] (II) Unloading modesetting
[ 4.828] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 4.828] (II) LoadModule: "fbdev"
[ 4.829] (WW) Warning, couldn't open module fbdev
[ 4.829] (II) UnloadModule: "fbdev"
[ 4.829] (II) Unloading fbdev
[ 4.829] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 4.829] (II) NOUVEAU driver
[ 4.829] (II) NOUVEAU driver for NVIDIA chipset families :
[ 4.829] RIVA TNT (NV04)
[ 4.829] RIVA TNT2 (NV05)
[ 4.829] GeForce 256 (NV10)
[ 4.829] GeForce 2 (NV11, NV15)
[ 4.829] GeForce 4MX (NV17, NV18)
[ 4.829] GeForce 3 (NV20)
[ 4.829] GeForce 4Ti (NV25, NV28)
[ 4.829] GeForce FX (NV3x)
[ 4.829] GeForce 6 (NV4x)
[ 4.829] GeForce 7 (G7x)
[ 4.829] GeForce 8 (G8x)
[ 4.829] GeForce GTX 200 (NVA0)
[ 4.829] GeForce GTX 400 (NVC0)
[ 4.829] (II) VESA: driver for VESA chipsets: vesa
[ 4.829] (++) using VT number 7
[ 4.834] (II) [drm] nouveau interface version: 1.1.0
[ 4.834] (II) [drm] nouveau interface version: 1.1.0
[ 4.834] (WW) Falling back to old probe method for vesa
[ 4.834] (II) Loading sub module "dri"
[ 4.834] (II) LoadModule: "dri"
[ 4.835] (II) Module "dri" already built-in
[ 4.835] (II) NOUVEAU(0): Loaded DRI module
[ 4.835] (--) NOUVEAU(0): Chipset: "NVIDIA NV4c"
[ 4.835] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 4.835] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 4.835] (==) NOUVEAU(0): RGB weight 888
[ 4.835] (==) NOUVEAU(0): Default visual is TrueColor
[ 4.835] (==) NOUVEAU(0): Using HW cursor
[ 4.835] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 4.835] (==) NOUVEAU(0): Page flipping enabled
[ 4.835] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 4.927] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 4.989] (II) NOUVEAU(0): EDID for output VGA-1
[ 4.989] (II) NOUVEAU(0): Manufacturer: HSD Model: 240f Serial#: 0
[ 4.989] (II) NOUVEAU(0): Year: 2010 Week: 52
[ 4.989] (II) NOUVEAU(0): EDID Version: 1.3
[ 4.990] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 4.990] (II) NOUVEAU(0): Sync: Separate SyncOnGreen
[ 4.990] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 41 vert.: 26
[ 4.990] (II) NOUVEAU(0): Gamma: 2.20
[ 4.990] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 4.990] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 4.990] (II) NOUVEAU(0): redX: 0.640 redY: 0.329 greenX: 0.300 greenY: 0.600
[ 4.990] (II) NOUVEAU(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329
[ 4.990] (II) NOUVEAU(0): Supported established timings:
[ 4.990] (II) NOUVEAU(0): 720x400@70Hz
[ 4.990] (II) NOUVEAU(0): 640x480@60Hz
[ 4.990] (II) NOUVEAU(0): 640x480@67Hz
[ 4.990] (II) NOUVEAU(0): 640x480@72Hz
[ 4.990] (II) NOUVEAU(0): 640x480@75Hz
[ 4.990] (II) NOUVEAU(0): 800x600@56Hz
[ 4.990] (II) NOUVEAU(0): 800x600@60Hz
[ 4.990] (II) NOUVEAU(0): 800x600@72Hz
[ 4.990] (II) NOUVEAU(0): 800x600@75Hz
[ 4.990] (II) NOUVEAU(0): 832x624@75Hz
[ 4.990] (II) NOUVEAU(0): 1024x768@60Hz
[ 4.990] (II) NOUVEAU(0): 1024x768@70Hz
[ 4.990] (II) NOUVEAU(0): 1024x768@75Hz
[ 4.990] (II) NOUVEAU(0): 1152x864@75Hz
[ 4.990] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 4.990] (II) NOUVEAU(0): Supported standard timings:
[ 4.990] (II) NOUVEAU(0): #0: hsize: 1440 vsize 900 refresh: 75 vid: 3989
[ 4.990] (II) NOUVEAU(0): #1: hsize: 1400 vsize 1050 refresh: 60 vid: 16528
[ 4.990] (II) NOUVEAU(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 4.990] (II) NOUVEAU(0): #3: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 4.990] (II) NOUVEAU(0): #4: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 4.990] (II) NOUVEAU(0): #5: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 4.990] (II) NOUVEAU(0): #6: hsize: 1024 vsize 768 refresh: 66 vid: 18017
[ 4.990] (II) NOUVEAU(0): Supported detailed timing:
[ 4.990] (II) NOUVEAU(0): clock: 106.5 MHz Image Size: 408 x 255 mm
[ 4.990] (II) NOUVEAU(0): h_active: 1440 h_sync: 1520 h_sync_end 1672 h_blank_end 1904 h_border: 0
[ 4.990] (II) NOUVEAU(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 934 v_border: 0
[ 4.990] (II) NOUVEAU(0): Serial No: 052AW1WY01107
[ 4.990] (II) NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 24 H max: 75 kHz, PixClock max 145 MHz
[ 4.990] (II) NOUVEAU(0): Monitor name: iP192A
[ 4.990] (II) NOUVEAU(0): EDID (in hex):
[ 4.990] (II) NOUVEAU(0): 00ffffffffffff0022640f2400000000
[ 4.990] (II) NOUVEAU(0): 341401030a291a78eade95a3544c9926
[ 4.990] (II) NOUVEAU(0): 0f5054bfee80950f90408180814081c0
[ 4.990] (II) NOUVEAU(0): 714f614601019a29a0d0518422305098
[ 4.990] (II) NOUVEAU(0): 360098ff1000001c000000ff00303532
[ 4.990] (II) NOUVEAU(0): 41573157593031313037000000fd0038
[ 4.990] (II) NOUVEAU(0): 4b184b0e000a202020202020000000fc
[ 4.990] (II) NOUVEAU(0): 006950313932410a0a0a0a0a0a0a0047
[ 4.991] (II) NOUVEAU(0): Printing probed modes for output VGA-1
[ 4.991] (II) NOUVEAU(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 4.991] (II) NOUVEAU(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x66.0 71.64 1024 1080 1192 1360 768 769 772 798 -hsync +vsync (52.7 kHz)
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 4.991] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 4.991] (II) NOUVEAU(0): Output VGA-1 connected
[ 4.991] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 4.991] (II) NOUVEAU(0): Output VGA-1 using initial mode 1440x900
[ 4.991] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 4.991] (--) NOUVEAU(0): Virtual size is 1440x900 (pitch 0)
[ 4.991] (**) NOUVEAU(0): Driver mode "1440x900": 106.5 MHz (scaled from 0.0 MHz), 55.9 kHz, 59.9 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 4.991] (**) NOUVEAU(0): Driver mode "1400x1050": 121.8 MHz (scaled from 0.0 MHz), 65.3 kHz, 60.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "1440x900": 136.8 MHz (scaled from 0.0 MHz), 70.6 kHz, 75.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 4.991] (**) NOUVEAU(0): Mode "1280x720": 74.4 MHz (scaled from 0.0 MHz), 44.7 kHz, 60.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 4.991] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 4.991] (**) NOUVEAU(0): Mode "1024x768": 71.6 MHz (scaled from 0.0 MHz), 52.7 kHz, 66.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x66.0 71.64 1024 1080 1192 1360 768 769 772 798 -hsync +vsync (52.7 kHz)
[ 4.991] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 4.991] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 4.991] (**) NOUVEAU(0): Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
[ 4.992] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 4.992] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 4.992] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 4.992] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 4.992] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 4.992] (==) NOUVEAU(0): DPI set to (96, 96)
[ 4.992] (II) Loading sub module "fb"
[ 4.992] (II) LoadModule: "fb"
[ 4.992] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 5.023] (II) Module fb: vendor="X.Org Foundation"
[ 5.023] compiled for 1.14.1, module version = 1.0.0
[ 5.023] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.023] (II) Loading sub module "exa"
[ 5.023] (II) LoadModule: "exa"
[ 5.023] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 5.025] (II) Module exa: vendor="X.Org Foundation"
[ 5.026] compiled for 1.14.1, module version = 2.6.0
[ 5.026] ABI class: X.Org Video Driver, version 14.1
[ 5.026] (II) Loading sub module "shadowfb"
[ 5.026] (II) LoadModule: "shadowfb"
[ 5.026] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 5.029] (II) Module shadowfb: vendor="X.Org Foundation"
[ 5.029] compiled for 1.14.1, module version = 1.0.0
[ 5.029] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.029] (II) Loading sub module "dri"
[ 5.029] (II) LoadModule: "dri"
[ 5.029] (II) Module "dri" already built-in
[ 5.029] (II) NOUVEAU(G0): Loaded DRI module
[ 5.029] (--) NOUVEAU(G0): Chipset: "NVIDIA NVa8"
[ 5.029] (==) NOUVEAU(G0): Depth 24, (--) framebuffer bpp 32
[ 5.029] (==) NOUVEAU(G0): RGB weight 888
[ 5.029] (==) NOUVEAU(G0): Default visual is TrueColor
[ 5.029] (==) NOUVEAU(G0): Using HW cursor
[ 5.029] (==) NOUVEAU(G0): GLX sync to VBlank disabled.
[ 5.029] (==) NOUVEAU(G0): Page flipping enabled
[ 5.029] (==) NOUVEAU(G0): Swap limit set to 2 [Max allowed 2]
[ 5.060] (II) NOUVEAU(G0): Output DVI-I-1 has no monitor section
[ 5.068] (II) NOUVEAU(G0): Output HDMI-1 has no monitor section
[ 5.178] (II) NOUVEAU(G0): Output VGA-2 has no monitor section
[ 5.189] (II) NOUVEAU(G0): EDID for output DVI-I-1
[ 5.196] (II) NOUVEAU(G0): EDID for output HDMI-1
[ 5.249] (II) NOUVEAU(G0): EDID for output VGA-2
[ 5.249] (II) NOUVEAU(G0): Manufacturer: DEL Model: a00c Serial#: 808793676
[ 5.249] (II) NOUVEAU(G0): Year: 2004 Week: 47
[ 5.249] (II) NOUVEAU(G0): EDID Version: 1.3
[ 5.249] (II) NOUVEAU(G0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 5.249] (II) NOUVEAU(G0): Sync: Separate
[ 5.249] (II) NOUVEAU(G0): Max Image Size [cm]: horiz.: 30 vert.: 23
[ 5.249] (II) NOUVEAU(G0): Gamma: 2.20
[ 5.249] (II) NOUVEAU(G0): DPMS capabilities: Off; RGB/Color Display
[ 5.249] (II) NOUVEAU(G0): Default color space is primary color space
[ 5.249] (II) NOUVEAU(G0): First detailed timing is preferred mode
[ 5.249] (II) NOUVEAU(G0): redX: 0.631 redY: 0.347 greenX: 0.309 greenY: 0.582
[ 5.249] (II) NOUVEAU(G0): blueX: 0.149 blueY: 0.088 whiteX: 0.312 whiteY: 0.328
[ 5.249] (II) NOUVEAU(G0): Supported established timings:
[ 5.249] (II) NOUVEAU(G0): 720x400@70Hz
[ 5.249] (II) NOUVEAU(G0): 640x480@60Hz
[ 5.249] (II) NOUVEAU(G0): 640x480@72Hz
[ 5.249] (II) NOUVEAU(G0): 640x480@75Hz
[ 5.249] (II) NOUVEAU(G0): 800x600@56Hz
[ 5.249] (II) NOUVEAU(G0): 800x600@60Hz
[ 5.249] (II) NOUVEAU(G0): 800x600@72Hz
[ 5.249] (II) NOUVEAU(G0): 800x600@75Hz
[ 5.249] (II) NOUVEAU(G0): 1024x768@60Hz
[ 5.249] (II) NOUVEAU(G0): 1024x768@70Hz
[ 5.249] (II) NOUVEAU(G0): 1024x768@75Hz
[ 5.249] (II) NOUVEAU(G0): Manufacturer's mask: 0
[ 5.249] (II) NOUVEAU(G0): Supported detailed timing:
[ 5.249] (II) NOUVEAU(G0): clock: 65.0 MHz Image Size: 304 x 228 mm
[ 5.249] (II) NOUVEAU(G0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0
[ 5.249] (II) NOUVEAU(G0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0
[ 5.249] (II) NOUVEAU(G0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 63 kHz, PixClock max 85 MHz
[ 5.249] (II) NOUVEAU(G0): Serial No: D82544BF056L
[ 5.249] (II) NOUVEAU(G0): Monitor name: DELL E153FP
[ 5.249] (II) NOUVEAU(G0): EDID (in hex):
[ 5.249] (II) NOUVEAU(G0): 00ffffffffffff0010ac0ca04c363530
[ 5.253] (II) NOUVEAU(G0): 2f0e0103681e17782eb060a1584f9526
[ 5.253] (II) NOUVEAU(G0): 165054afce0001010101010101010101
[ 5.253] (II) NOUVEAU(G0): 01010101010164190040410026301888
[ 5.253] (II) NOUVEAU(G0): 360030e410000018000000fd00384c1e
[ 5.253] (II) NOUVEAU(G0): 3f08000a202020202020000000ff0044
[ 5.253] (II) NOUVEAU(G0): 383235343442463035364c0a000000fc
[ 5.253] (II) NOUVEAU(G0): 0044454c4c204531353346500a200025
[ 5.253] (II) NOUVEAU(G0): Printing probed modes for output VGA-2
[ 5.253] (II) NOUVEAU(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 5.253] (II) NOUVEAU(G0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 5.253] (II) NOUVEAU(G0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 5.253] (II) NOUVEAU(G0): Output DVI-I-1 disconnected
[ 5.253] (II) NOUVEAU(G0): Output HDMI-1 disconnected
[ 5.253] (II) NOUVEAU(G0): Output VGA-2 connected
[ 5.253] (II) NOUVEAU(G0): Using exact sizes for initial modes
[ 5.253] (II) NOUVEAU(G0): Output VGA-2 using initial mode 1024x768
[ 5.253] (II) NOUVEAU(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 5.253] (--) NOUVEAU(G0): Virtual size is 1440x900 (pitch 0)
[ 5.253] (**) NOUVEAU(G0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 5.253] (**) NOUVEAU(G0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 5.253] (II) NOUVEAU(G0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 5.253] (**) NOUVEAU(G0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 5.254] (II) NOUVEAU(G0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 5.254] (==) NOUVEAU(G0): DPI set to (96, 96)
[ 5.254] (II) Loading sub module "fb"
[ 5.254] (II) LoadModule: "fb"
[ 5.254] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 5.254] (II) Module fb: vendor="X.Org Foundation"
[ 5.254] compiled for 1.14.1, module version = 1.0.0
[ 5.254] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.254] (II) Loading sub module "exa"
[ 5.254] (II) LoadModule: "exa"
[ 5.254] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 5.254] (II) Module exa: vendor="X.Org Foundation"
[ 5.254] compiled for 1.14.1, module version = 2.6.0
[ 5.254] ABI class: X.Org Video Driver, version 14.1
[ 5.254] (II) Loading sub module "shadowfb"
[ 5.254] (II) LoadModule: "shadowfb"
[ 5.254] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 5.254] (II) Module shadowfb: vendor="X.Org Foundation"
[ 5.254] compiled for 1.14.1, module version = 1.0.0
[ 5.254] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.254] (II) UnloadModule: "vesa"
[ 5.254] (II) Unloading vesa
[ 5.254] (--) Depth 24 pixmap format is 32 bpp
[ 5.255] (II) NOUVEAU(G0): Opened GPU channel 0
[ 5.261] (II) NOUVEAU(G0): [DRI2] Setup complete
[ 5.261] (II) NOUVEAU(G0): [DRI2] DRI driver: nouveau
[ 5.261] (II) NOUVEAU(G0): [DRI2] VDPAU driver: nouveau
[ 5.266] (II) EXA(256): Driver allocated offscreen pixmaps
[ 5.266] (II) EXA(256): Driver registered support for the following operations:
[ 5.266] (II) Solid
[ 5.266] (II) Copy
[ 5.266] (II) Composite (RENDER acceleration)
[ 5.266] (II) UploadToScreen
[ 5.266] (II) DownloadFromScreen
[ 5.266] (==) NOUVEAU(G0): Backing store disabled
[ 5.266] (==) NOUVEAU(G0): Silken mouse enabled
[ 5.267] (II) NOUVEAU(G0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 5.267] (II) NOUVEAU(G0): [XvMC] Extension initialized.
[ 5.267] (==) NOUVEAU(G0): DPMS enabled
[ 5.267] (II) NOUVEAU(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 5.269] (II) NOUVEAU(0): Opened GPU channel 0
[ 5.273] (II) NOUVEAU(0): [DRI2] Setup complete
[ 5.273] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 5.273] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 5.276] (II) EXA(0): Driver allocated offscreen pixmaps
[ 5.276] (II) EXA(0): Driver registered support for the following operations:
[ 5.276] (II) Solid
[ 5.277] (II) Copy
[ 5.277] (II) Composite (RENDER acceleration)
[ 5.277] (II) UploadToScreen
[ 5.277] (II) DownloadFromScreen
[ 5.277] (==) NOUVEAU(0): Backing store disabled
[ 5.277] (==) NOUVEAU(0): Silken mouse enabled
[ 5.277] (II) NOUVEAU(0): [XvMC] Associated with NV40 texture adapter.
[ 5.277] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 5.277] (==) NOUVEAU(0): DPMS enabled
[ 5.277] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 5.277] (--) RandR disabled
[ 5.444] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 5.444] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 5.444] (II) AIGLX: enabled GLX_ARB_create_context
[ 5.444] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 5.445] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 5.445] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 5.445] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 5.447] (II) AIGLX: Loaded and initialized nouveau
[ 5.447] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 5.456] (II) NOUVEAU(0): NVEnterVT is called.
[ 5.457] (II) NOUVEAU(0): Setting screen physical size to 381 x 238
[ 5.457] resize called 1440 900
[ 5.688] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 5.688] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 5.688] (II) LoadModule: "evdev"
[ 5.688] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 5.690] (II) Module evdev: vendor="X.Org Foundation"
[ 5.690] compiled for 1.14.0, module version = 2.8.0
[ 5.690] Module class: X.Org XInput Driver
[ 5.690] ABI class: X.Org XInput driver, version 19.1
[ 5.690] (II) Using input driver 'evdev' for 'Power Button'
[ 5.690] (**) Power Button: always reports core events
[ 5.690] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 5.690] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 5.690] (--) evdev: Power Button: Found keys
[ 5.690] (II) evdev: Power Button: Configuring as keyboard
[ 5.690] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 5.690] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 5.690] (**) Option "xkb_rules" "evdev"
[ 5.690] (**) Option "xkb_model" "evdev"
[ 5.690] (**) Option "xkb_layout" "us"
[ 5.771] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 5.771] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 5.771] (II) Using input driver 'evdev' for 'Power Button'
[ 5.771] (**) Power Button: always reports core events
[ 5.771] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 5.771] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 5.771] (--) evdev: Power Button: Found keys
[ 5.771] (II) evdev: Power Button: Configuring as keyboard
[ 5.771] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[ 5.771] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 5.771] (**) Option "xkb_rules" "evdev"
[ 5.771] (**) Option "xkb_model" "evdev"
[ 5.771] (**) Option "xkb_layout" "us"
[ 5.772] (II) config/udev: Adding input device Lite-On Technology Corp. USB Keyboard (/dev/input/event2)
[ 5.772] (**) Lite-On Technology Corp. USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 5.772] (II) Using input driver 'evdev' for 'Lite-On Technology Corp. USB Keyboard'
[ 5.772] (**) Lite-On Technology Corp. USB Keyboard: always reports core events
[ 5.772] (**) evdev: Lite-On Technology Corp. USB Keyboard: Device: "/dev/input/event2"
[ 5.772] (--) evdev: Lite-On Technology Corp. USB Keyboard: Vendor 0x4ca Product 0x4b
[ 5.772] (--) evdev: Lite-On Technology Corp. USB Keyboard: Found keys
[ 5.772] (II) evdev: Lite-On Technology Corp. USB Keyboard: Configuring as keyboard
[ 5.772] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/input/input2/event2"
[ 5.772] (II) XINPUT: Adding extended input device "Lite-On Technology Corp. USB Keyboard" (type: KEYBOARD, id 8)
[ 5.772] (**) Option "xkb_rules" "evdev"
[ 5.772] (**) Option "xkb_model" "evdev"
[ 5.772] (**) Option "xkb_layout" "us"
[ 5.772] (II) config/udev: Adding input device Lite-On Technology Corp. USB Keyboard (/dev/input/event3)
[ 5.772] (**) Lite-On Technology Corp. USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 5.772] (II) Using input driver 'evdev' for 'Lite-On Technology Corp. USB Keyboard'
[ 5.772] (**) Lite-On Technology Corp. USB Keyboard: always reports core events
[ 5.772] (**) evdev: Lite-On Technology Corp. USB Keyboard: Device: "/dev/input/event3"
[ 5.772] (--) evdev: Lite-On Technology Corp. USB Keyboard: Vendor 0x4ca Product 0x4b
[ 5.773] (--) evdev: Lite-On Technology Corp. USB Keyboard: Found 1 mouse buttons
[ 5.773] (--) evdev: Lite-On Technology Corp. USB Keyboard: Found scroll wheel(s)
[ 5.773] (--) evdev: Lite-On Technology Corp. USB Keyboard: Found relative axes
[ 5.773] (II) evdev: Lite-On Technology Corp. USB Keyboard: Forcing relative x/y axes to exist.
[ 5.773] (--) evdev: Lite-On Technology Corp. USB Keyboard: Found absolute axes
[ 5.773] (II) evdev: Lite-On Technology Corp. USB Keyboard: Forcing absolute x/y axes to exist.
[ 5.773] (--) evdev: Lite-On Technology Corp. USB Keyboard: Found keys
[ 5.773] (II) evdev: Lite-On Technology Corp. USB Keyboard: Configuring as mouse
[ 5.773] (II) evdev: Lite-On Technology Corp. USB Keyboard: Configuring as keyboard
[ 5.773] (II) evdev: Lite-On Technology Corp. USB Keyboard: Adding scrollwheel support
[ 5.773] (**) evdev: Lite-On Technology Corp. USB Keyboard: YAxisMapping: buttons 4 and 5
[ 5.773] (**) evdev: Lite-On Technology Corp. USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 5.773] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.1/input/input3/event3"
[ 5.773] (II) XINPUT: Adding extended input device "Lite-On Technology Corp. USB Keyboard" (type: KEYBOARD, id 9)
[ 5.773] (**) Option "xkb_rules" "evdev"
[ 5.773] (**) Option "xkb_model" "evdev"
[ 5.773] (**) Option "xkb_layout" "us"
[ 5.776] (II) evdev: Lite-On Technology Corp. USB Keyboard: initialized for relative axes.
[ 5.776] (WW) evdev: Lite-On Technology Corp. USB Keyboard: ignoring absolute axes.
[ 5.777] (**) Lite-On Technology Corp. USB Keyboard: (accel) keeping acceleration scheme 1
[ 5.777] (**) Lite-On Technology Corp. USB Keyboard: (accel) acceleration profile 0
[ 5.777] (**) Lite-On Technology Corp. USB Keyboard: (accel) acceleration factor: 2.000
[ 5.777] (**) Lite-On Technology Corp. USB Keyboard: (accel) acceleration threshold: 4
[ 5.777] (II) config/udev: Adding input device USB Optical Mouse (/dev/input/event4)
[ 5.777] (**) USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 5.777] (II) Using input driver 'evdev' for 'USB Optical Mouse'
[ 5.777] (**) USB Optical Mouse: always reports core events
[ 5.777] (**) evdev: USB Optical Mouse: Device: "/dev/input/event4"
[ 5.777] (--) evdev: USB Optical Mouse: Vendor 0x461 Product 0x4d20
[ 5.777] (--) evdev: USB Optical Mouse: Found 3 mouse buttons
[ 5.777] (--) evdev: USB Optical Mouse: Found scroll wheel(s)
[ 5.777] (--) evdev: USB Optical Mouse: Found relative axes
[ 5.777] (--) evdev: USB Optical Mouse: Found x and y relative axes
[ 5.777] (II) evdev: USB Optical Mouse: Configuring as mouse
[ 5.777] (II) evdev: USB Optical Mouse: Adding scrollwheel support
[ 5.777] (**) evdev: USB Optical Mouse: YAxisMapping: buttons 4 and 5
[ 5.777] (**) evdev: USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 5.777] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.0/usb2/2-3/2-3:1.0/input/input4/event4"
[ 5.777] (II) XINPUT: Adding extended input device "USB Optical Mouse" (type: MOUSE, id 10)
[ 5.777] (II) evdev: USB Optical Mouse: initialized for relative axes.
[ 5.778] (**) USB Optical Mouse: (accel) keeping acceleration scheme 1
[ 5.778] (**) USB Optical Mouse: (accel) acceleration profile 0
[ 5.778] (**) USB Optical Mouse: (accel) acceleration factor: 2.000
[ 5.778] (**) USB Optical Mouse: (accel) acceleration threshold: 4
[ 5.778] (II) config/udev: Adding input device USB Optical Mouse (/dev/input/mouse0)
[ 5.778] (II) No input driver specified, ignoring this device.
[ 5.778] (II) This device may have been added with another device file.
[ 5.778] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 5.778] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 5.779] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 5.779] (II) No input driver specified, ignoring this device.
[ 5.779] (II) This device may have been added with another device file.
[ 7.250] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 7.250] (II) No input driver specified, ignoring this device.
[ 7.250] (II) This device may have been added with another device file.
[ 7.252] (II) config/udev: Adding input device HDA NVidia Line (/dev/input/event7)
[ 7.252] (II) No input driver specified, ignoring this device.
[ 7.252] (II) This device may have been added with another device file.
[ 7.254] (II) config/udev: Adding input device HDA NVidia Front Mic (/dev/input/event8)
[ 7.254] (II) No input driver specified, ignoring this device.
[ 7.254] (II) This device may have been added with another device file.
[ 7.256] (II) config/udev: Adding input device HDA NVidia Rear Mic (/dev/input/event9)
[ 7.256] (II) No input driver specified, ignoring this device.
[ 7.256] (II) This device may have been added with another device file.
[ 7.258] (II) config/udev: Adding input device HDA NVidia Front Headphone (/dev/input/event10)
[ 7.258] (II) No input driver specified, ignoring this device.
[ 7.258] (II) This device may have been added with another device file.
[ 7.260] (II) config/udev: Adding input device HDA NVidia Line Out (/dev/input/event11)
[ 7.260] (II) No input driver specified, ignoring this device.
[ 7.260] (II) This device may have been added with another device file.
[ 7.270] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event12)
[ 7.270] (II) No input driver specified, ignoring this device.
[ 7.270] (II) This device may have been added with another device file.
[ 7.272] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event13)
[ 7.272] (II) No input driver specified, ignoring this device.
[ 7.272] (II) This device may have been added with another device file.
[ 7.274] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event14)
[ 7.274] (II) No input driver specified, ignoring this device.
[ 7.274] (II) This device may have been added with another device file.
[ 7.289] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event15)
[ 7.289] (II) No input driver specified, ignoring this device.
[ 7.289] (II) This device may have been added with another device file.
[ 16.144] (II) NOUVEAU(0): EDID vendor "HSD", prod id 9231
[ 16.144] (II) NOUVEAU(0): Using EDID range info for horizontal sync
[ 16.144] (II) NOUVEAU(0): Using EDID range info for vertical refresh
[ 16.144] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16.145] (II) NOUVEAU(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 16.145] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1400x1050"x0.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 16.145] (II) NOUVEAU(0): Modeline "1024x768"x66.0 71.63 1024 1080 1192 1360 768 769 772 798 -hsync +vsync (52.7 kHz e)
[ 16.979] (II) NOUVEAU(0): EDID vendor "HSD", prod id 9231
[ 16.979] (II) NOUVEAU(0): Using hsync ranges from config file
[ 16.979] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 16.979] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16.979] (II) NOUVEAU(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 16.979] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1400x1050"x0.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 16.979] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 16.982] (II) NOUVEAU(0): Modeline "1024x768"x66.0 71.63 1024 1080 1192 1360 768 769 772 798 -hsync +vsync (52.7 kHz e)
[ 16.984] resize called 1440 900 -
How to implement start & stop ai triggers when # scans unknown
I can't seem to find an implementation example for this application.
Some are close but seem to have a big gap on close examination.
The application is to log an unknown number of samples for a
single rotation of a variable speed drum. The drum is connected
to a tachometer which generates 1 pulse per revolution and is the
trigger source.
The user will initiate the data collection and only a single
rotation's
worth of data need be collected and displayed.
The board is a PCI 6111E sampling a single input at ~2 Megahz.
All the examples I've found using a start and stop trigger depend
on knowing how many scans to acquire.
Is there any way to get around that? It seems so simple to
have a
start and stop pulse, a scan rate constant, and just get
the data out of a buffer. But it does not seem to be that simple
or am I missing something here?
There is also an issue with the identical tach signal being used
for both the start and stop trigger. I think that can be gotten
around by using a divide by n counter and feeding that to
trigger config vi but if anyone has any suggestions for that,
they would be greatly appreciated.
Gene CouchI'm afraid I can't help you beyond that. We use NI boards and NI-DAQ library
of functions in custom control systems with software written in C++. I have
not had opportunity to use LabView. Sorry.
gcouch wrote:
>On 5 Jun 2000 09:38:46 -0500, "J. Wolters" >wrote>Thank
you for the response but I'm not sure what the DAQ_Rate function>is. With
LabVIEW 5.1 it does not appear in the DAQ pallette and I>cannot find it in
the example vi's. Do you know where it can be>found?>>>>>>Have you looked
that DAQ_Rate function? You should be able to use this function>>to obtain
your # of samples.>>>>>>gcouch wrote>>I can't seem
to find an implementation example for this application.>Some>>a
re close but
seem to have a big gap on close examination.>>The application>>is to log
an unknown number of samples for a >single rotation of a variable>>speed
drum. The drum is connected>to a tachometer which generates 1 pulse>>per
revolution and is the>trigger source.>>The user will initiate the data>>collection
and only a single>rotation's>worth of data need be collected and>>displayed.>>The
board is a PCI 6111E sampling a single input at ~2 Megahz.>> >>All the examples
I've found using a start and stop trigger depend>on knowing>>how many scans
to acquire.>>Is there any way to get around that? It seems>>so simple to>have
a start and stop pulse, a scan rate constant, and just>>get>the data out
of a buffer. But it does not seem to be that simple>or>>am I missing something
here?>>There is also an issue with the identical tach>>signal being used>for
both the start and stop trigger. I think that can>>be gotten>around by using
a divide by n counter and feeding that to>trigger>>config v
i but if anyone
has any suggestions for that,>they would be greatly>>appreciated.>>Gene Couch>>> -
Conceptual problem in using a PCI-6602?
Hi, All You Wild and Crazy NI/LabVIEW Types --
I have a problem that's been close to sending me off the deep end for more than a month now, and I think that I'm so enmeshed in it that I can't see the forest for the trees anymore. I'd like to apologize in advance for the length of this post, but there are some details that might or might not be important, and I'd rather make the mistake of giving you too much information than not enough.
We do impact-cratering experiments, using a gun to launch (usually) spherical projectiles at a variety of targets. One of our big efforts is to measure the velocities at which material is ejected from growing craters. We do that with a line-generating laser, oriented so the "sheet" of laser light is perpendicular to the target's surface and through the impact point; we strobe the laser at a programmed rate (with our PCI-6259 board) and take a time exposure of the scene with a Nikon D100 DSLR. When target material -- usually grains of sand -- is ejected, the laser illuminates a "slice" through the curtain of ejecta, illuminating a small portion of the fragments numerous times in their trajectories. Since we know the scale of the photograph and its orientation relative to the laser's illumination, and we also know the rate at which the laser is flashing, we can easily calculate the velocities of the illuminated particles. I'm attaching a picture (file 4044, cropped.jpg) of an example taken with an older camera to give you an idea. In the picture, the laser's illuminating the scene from the right of the frame and the projectile flew into the picture from the top of the frame, traveling along the left-hand edge. The brightest portion is the flash from the impact, and the rest of the parabolic trajectories are the grains of sand in flight. The target bucket, full of coarse sand, is the elliptical looking cylinder at the bottom of the picture. It's roughly 28 cm in outside diameter, if you'd like a scale.
As you might imagine, with our projectiles moving anywhere between 0.7 and 3 km/s, sequencing everything is pretty important. We're using (or trying to use) LabVIEW to do all of the sequencing, instrument control, and data storage. Things are going pretty well so far, except for what I'll describe in more detail below. A couple more things, though, first. It's important that we measure the projectile's speed in each shot, as that controls impact energy and momentum, which are critical to know in a given experiment. We do that with simple laser-photodetector pairs (which we normally call "velocity stations") arranged along the projectile's trajectory. As the projectile passes between a laser and its detector, its shadow is detected and a TTL pulse is sent to our PCI-6602 board. Depending on the experiment, we use three or four such laser-dector pairs. They use counters 0, 1, 2, and 3. We know the distances between the laser stations and, once we get the times between detections, it's s simple matter to calculate the projectile's velocity.
We also use LabVIEW to fire the gun, and we do that because opening the camera's shutter has to be synchronized with the firing pulse, which currently is sent via P1.1 on the 6259. Here's the problem: when we test the laser-detector arrays in a "standalone" mode (that is, without any other tasks or operations being done with LabVIEW), they work infallibly. It's when we try to use LabVIEW to fire the gun that we get either very erratic results from the velocity stations/6602 or no results at all.
I've tried a range of things, from starting the two-edge measurement task before the firing signal is sent, to trying to force things with a timed sequence, to doing things with brute force via a seuqence structure. When I try to start the two-edge measurement task first, though, the firing signal isn't sent until the counters time out. This of course, wrecks the experiment, because all of the timing is then messed up. The VI that I've attached (Version 1.vi) is a HIGHLY simplified version of the initial attempt I made at doing this, with all sorts of background stuff removed just so I can cut to the chase. (Only one two-edge measurement task is shown, for instance.) I think that the VI is pretty self-explanatory (and embarrassingly primitive), so it probably doesn't need much in the way of explanation. Counter 7 and PFI 0 on the 6602 are used to accept the signal from the firing button and trigger the event structure, which contains the two-edge separation and gun-firing tasks. (In reality, I use a separate VI to have three to four concurrent two-edge separation tasks running concurrently, one for each velocity station.) I start the two-edge separation tasks first so the detectors and counters are ready for the projectile. It's not necessary here, but I kept the 500 ms wait frame in this example because that's why the sequence structure exists -- to allow the shutter of the Nikon to open completely before the gun fires. After those 500 ms, the firing signal is sent to the circuit that actually fires the gun.
What happens in this configuration is that the second frame of the sequence structure doesn't execute until the 5-s timeout transpires in the two-edge separation task. I've also tried this using a line on the 6602 to fire the gun instead of P0.1 on the 6259, but that ends up with the same result. (Both counters are used on the 6259 to strobe the main illumination laser, so they're unavailable, if you're wondering. In any case, we need four counters for the four velocity stations.)
FINALLY, my question: What am I doing wrong, here? If I put the two-edge separation tasks in the same frame of the sequence structure as the firing task, the gun fires when it's supposed to, but we get no velocity measurements. I've also tried to force the timing with another version of a sequence structure; I'm attaching another very simplified version below as Fire and speed example.vi.
After you recover from your violent fits of laughter, I'd really appreciate hearing what you might recommend. (And no, surrender isn't an option.)
Thanks for taking all of your valuable time to read this huge post -- I really appreciate it!
Mark
Attachments:
4044, cropped.jpg 197 KB
Version 1.vi 35 KB
Fire and speed example.vi 30 KBI agree with all 3 of Kevin's points. His first suggestion will probably fix your problem (see below). The 2nd and 3rd suggestion would improve efficiency and responsiveness, but #2 might not be possible since independently triggering four outputs in hardware would require the use of 4 counters (on the 6602 anyway) which might be busy doing other tasks in your application (although if you don't need the stations to trigger independently then you could implement this with a single counter).
I think I have an explanation of the problematic behavior you are seeing based off of the following bits of information from your post:
1. Running the small example code by itself works flawlessly, but adding other simultaneous functionality fails. You mentioned you are doing this on 4 stations, so I'm assuming 4 counter input tasks running in parallel.
2. The behavior you are seeing is that the 2nd sequence does not execute until after the read times out (note that the sequence is supposed to be executing in parallel with the read).
It sounds like the problem is coming from a combination of calling into DAQmx Read before data is available (this consumes one of the threads that LabVIEW has allocated to your application until DAQmx Read finishes executing) along with the fact that LabVIEW allocates 4 threads per execution system per priority by default. Since all of your threads (from what I can tell) are executing on the same priority, the 4 reads you are calling will block anything else from executing until they have completed. By then it's too late and the firing of your gun happens after the counter task has already timed out.
You *may* increase the number of threads allocated to your application by using a VI that is included with LabVIEW (vi.lib\Utility\sysinfo.llb\threadconfig.vi) and this would also probably remedy the behavior you are seeing. However, rather than throwing more threads at this application I think the better solution would be to change the sequencing of your tasks like Kevin suggested ("create and start the 2-edge task before entering the sequence structure, and defer the 2-edge *reading* until *after* firing the DO")--in doing this you would now expect to see data immediately upon calling DAQmx Read and you avoid the situation where Read is blocking indefinitely and consuming an application thread. You could take this a step further by checking the Available Samples per Channel property (or using the DAQmx EveryNSamplesAcquiredIntoBuffer event) to ensure that data is actually available before calling Read.
Best Regards,
John Passiak -
"PCI Configuration" terminates ethernet connection, randomly.
Mavericks 10.10.1, Macbook Pro Retina (Mid 2012), Thunderbolt Ethernet Adapter.
Found my network connection (en4) dropping randomly and found a few different reasons in console for this.
I've tried:
setting a location in network preferences
removing thunderbolt adapter in network settings and adding it again
removing thunderbolt bridge
rebooting computer
keeping the system awake by using it - still goes down while using it (clearly not a 'sleep' issue?)
changing thunderbolt sockets
testing another thunderbolt ethernet adapter
Console info below. Any help would be much appreciated, this is a really frustrating problem.
Here is one event in the Console, showing the link going down due to "PCI configuration":
(i've highlighted the link going down in bold)
16/01/2015 11:26:56.000 am kernel[0]: ASP_TCP Detach: Reply queue not empty?
16/01/2015 11:26:56.610 am com.apple.backupd[1158]: Ejected Time Machine network volume.
16/01/2015 11:27:29.000 am kernel[0]: Google Chrome He (map: 0xffffff803c583780) triggered DYLD shared region unnest for map: 0xffffff803c583780, region 0x7fff92e00000->0x7fff93000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
16/01/2015 11:27:53.000 am kernel[0]: Google Chrome He (map: 0xffffff803ebd4690) triggered DYLD shared region unnest for map: 0xffffff803ebd4690, region 0x7fff92e00000->0x7fff93000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
16/01/2015 11:28:52.825 am SystemUIServer[243]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
16/01/2015 11:29:36.121 am DesktopServicesHelper[877]: notify name "com.apple.filecoordination.dump_request" has been registered 40 times - this may be a leak
16/01/2015 11:29:37.000 am kernel[0]: [ PCI configuration begin ]
16/01/2015 11:29:37.000 am kernel[0]: [ PCI configuration end, bridges 12, devices 17 ]
16/01/2015 11:29:37.000 am kernel[0]: AppleBCM5701Ethernet [en4]: willTerminate - offline
16/01/2015 11:29:37.122 am configd[26]: bootp_client_bind_socket_to_if(en4, 9): setsockopt IP_BOUND_IF failed
16/01/2015 11:29:37.122 am discoveryd[51]: Basic Network GetExtendedFlags ioctl failed Device not configured
16/01/2015 11:29:37.122 am configd[26]: DHCP en4: RELEASE transmit failed
16/01/2015 11:29:37.125 am discoveryd[51]: Basic Network GetExtendedFlags ioctl failed Device not configured
16/01/2015 11:29:37.131 am networkd[127]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
16/01/2015 11:29:37.132 am configd[26]: network changed: v4(en4-:192.168.1.198) DNS- Proxy-
16/01/2015 11:29:37.136 am discoveryd[51]: Basic WABServer NetResolverEvent no resolvers, resetting domains
16/01/2015 11:29:37.136 am discoveryd[51]: Basic Bonjour stop listening on en4
16/01/2015 11:29:37.000 am kernel[0]: smb2_smb_parse_change_notify: smb_rq_reply failed 60
16/01/2015 11:29:37.000 am kernel[0]: smb2_smb_parse_change_notify: smb_rq_reply failed 60
16/01/2015 11:29:37.000 am kernel[0]: smb2_smb_parse_change_notify: smb_rq_reply failed 60
16/01/2015 11:29:37.000 am kernel[0]: smb2_smb_read_write_async: smb_rq_reply failed 60
16/01/2015 11:29:41.833 am com.apple.iCloudHelper[1238]: objc[1238]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
16/01/2015 11:29:41.839 am com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
16/01/2015 11:29:42.140 am netbiosd[1077]: network_reachability_changed : network is not reachable, netbiosd is shutting down
Here is a similar situation (ethernet going down) but a different trigger (apparently?):
16/01/2015 3:41:09.000 am kernel[0]: pci pause: SDXC
16/01/2015 3:41:36.000 am kernel[0]: PM response took 1998 ms (27, powerd)
16/01/2015 3:41:36.000 am kernel[0]: ARPT: 288540.420526: AirPort_Brcm43xx::powerChange: System Sleep
16/01/2015 3:41:36.000 am kernel[0]: ARPT: 288540.420532: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.
16/01/2015 3:41:37.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 3:41:37.000 am kernel[0]: AppleBCM5701Ethernet [en4]: 0 0 memWrInd fBJP_Wakeup_Timer
16/01/2015 3:41:38.000 am kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 86
16/01/2015 5:04:00.000 am kernel[0]: Wake reason: RTC (Alarm)
As an overview of down/up events, this is a filtered view for "link" in the console, showing when the ethernet link going up and down last night while I was asleep:
15/01/2015 11:04:23.757 pm com.apple.backupd[14541]: Copied 186 items (12.6 MB) from volume Macintosh HD. Linked 8558.
15/01/2015 11:17:22.000 pm kernel[0]: en4: attached with 4 suspended link-layer multicast membership(s)
15/01/2015 11:17:26.000 pm kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,2301,0c01,0200,c5e1,3800]
16/01/2015 12:12:58.705 am com.apple.backupd[14832]: Copied 959 items (22 MB) from volume Macintosh HD. Linked 9314.
16/01/2015 1:21:48.047 am com.apple.backupd[14954]: Copied 179 items (12.8 MB) from volume Macintosh HD. Linked 7713.
16/01/2015 2:10:19.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 3:10:21.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,2301,0c01,0200,c5e1,3800]
16/01/2015 3:10:32.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 3:34:00.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0c01,0200,c5e1,3800]
16/01/2015 3:34:00.000 am kernel[0]: AppleBCM5701Ethernet [en4]: 0 0 Linkup - sending up wakeup packet
16/01/2015 3:34:52.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 3:40:32.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0c01,0200,c5e1,3800]
16/01/2015 3:41:37.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 5:04:07.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0c01,0200,c5e1,3800]
16/01/2015 5:08:36.823 am com.apple.backupd[15061]: Copied 144 items (12.7 MB) from volume Macintosh HD. Linked 7781.
16/01/2015 5:09:52.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 6:34:56.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0c01,0200,c5e1,3800]
16/01/2015 6:35:59.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 7:36:03.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0c01,0200,c5e1,3800]
16/01/2015 7:37:01.000 am kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp enabled, proxy 1379)
16/01/2015 8:22:17.000 am kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0c01,0200,c5e1,3800]I think I've solved the problem.
The thunderbolt bridge was re-added to my config and I thought it would never go away. So I'd left it there. Problem still existed.
Then I randomly thought to remove it again. Now the problem hasn't yet returned. If it does, I'll post back here. -
What are the 3-bit field choices for Hw_Arm_Sel in PCI-6601
Hi,
I am programming our own driver to operate the PCI-6601. For our application we need hardware arm option. I know it is possible to use 2 counters for that, but NI-TIO should support also hw_arm. Although it is not explained in the registry document at all, after some tedious check in the DDK examples I found that this bits are located in the Gi counting mode register. I know the position of the HW_enable as well as the position of the 3 bits for pin sellect options. What I do not know is What are the 3-bit field choices for Hw_Arm_Sel . I contacted NI support but got no support. How can NI sell boards and when a customer who is not using LAbview or Measurement Studio or DDK, but is implementing his own driver is then so arrogantly turned down from NI? Also, how can NI publish just part of the registers the board support, and when a customer contacs and asks for some registers get not at all support? I can not foretell the missing registers, and it is pretty unprofessional to document just partly the registers of 660x devices. And on request you got nothing.
I hope someone from the community know about this Hw_Arm_Sel 3 pin options. Otherwise, there is just an option of error and trial. Or simply throw the board in the garbage.
Dr. Kirco Arsov
Solved!
Go to Solution.Hi Kirco,
I have some more information for you :-)
I haven't been able to speak to the developer who is the most familiar with TIO programming since he's out of the office, but I have come across his notes from when he was writing support for the DAQmx driver.
As I described earlier, the HW_Arm_Sel bits don't select a connector I/O pin, but an internal trigger signal. There are seven internal trigger lines, and the HW_Arm_Sel bits map directly to the internal trigger signal: 0b000 - 0b111 map to 0d0 - 0d7. In order to route an I/O pin to an internal trigger, you must also write to a few more registers.
From what I've read, there are two more register families that need to be programmed: TG_x_LevelEdgeReg and TG_x_CombinationReg, where x is the internal trigger number. In your case, you only need one pin from the I/O connector to be your arm start trigger, so TG_0_LevelEdgeReg and TB_0_CombinationReg will suffice for your application.
TB_0_LevelEdgeReg :: Offset 0x660
TG_0_LevelEdgeReg is only 8 bits wide, and maps as follows:
7..6: EdgeMode
5..0: LESel
LESel selects the I/O connector pin to use as the source for the internal trigger signal. 0d0 - 0d39 will select the I/O pin of the same number. NB: behavior for TG_x_LevelEdgeReg is more limited for triggers 1-7, and only a small subset of the I/O pins can be selected for those trigger signals. Trigger 0 can use any I/O pin. Setting these bits to 0d63 forces the trigger source low, and can be used as a way to 'unroute' it when you're finished with your program.
EdgeMode determines whether the TIO will detect an edge of the incoming signal, or just pass the signal level straight through. When detecting edges, it will latch the signal and generate a single TIMEBASE3 pulse instead. 0b00 sets level mode; 0b01 sets rising edge; 0b10 sets falling edge; 0b11 sets either edge.
TG_0_CombinationReg :: Offset 0x6A0
TG_0_CombinationReg is 32 bits wide, and has three fields of interest:
19..16: CombFunction
5..4: CombTypeB
1..0: CombTypeA
CombTypeA controls which trigger subsystem to use as the source for the trigger signal. Since you're coming from an I/O pin and using the edge/level subsystem, you must set these bits to 0b01.
CombTypeB is similar to CombTypeA, and although you won't be using trigger B, set it to 0b01 to be safe.
CombFunction performs a simple logic function on A and B. Since you're only using a single I/O connector, you only need the A output, so set these bits to 0b1100.
All of the other bits should be set to 0b0.
Unfortunately, I'm unable to test these statements since my test machine is currently being used for another research project. Please let me know what happens if you decide to test.
Joe Friedchicken
NI VirtualBench Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Multifunction Instruments Applications Group
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008) -
Detect and employ PCI or PXI chassis
I'm currently on a project which has historically bee based around a PCI backplane (in a desktop PC) containing a couple of PCI-6229 cards and a PCI-7833R. This forms the core of a testrig of which there are about 25 instances worldwide. In addition, we also support many rigs which are cored around a NI PXI chassis.
There is a drive to replace the PCs and we have opted for a for smaller footprint unit having fewer PCI slots. These are being equipped with an MXI extender card to a PXI backplane. This means in future, we need only keeps spares in the PXI format. Supporting two sets of backplanes containing near-identical hardware without implementing two near-identical pieces of software does present its problems: The FPGA bitmap build for the PCI version of the card will not open through the reference type for the PXI version of the card. We need to have a PCI and a PXI version of the bitmap. Irritatingly, the source code for these two is identical.
The first part of the solution is to establish which backplane we're using. This is straightforward. Supplying the VISA Find Resource function with the appropriate search string will identify if any PXI backplanes are connected. (Figure 1.)
Next, we need to maintain references to both FPGA VIs. Figure 2 illustrates how the FPGA to be used can be opened and proposes a structure in which the references to all available FPGA types (this example actually has four FPGA bitmaps which might be selected). In each of the other cases, the appropriate bitmap is selected in the Open FPGA Reference VI. Further, in each case, the reference is wired to the appropriate component from the cluster. (For calibration records, we also find it necessary to return the serial number of the card, but that portion of this code can be ignored.) Notice that the FPGA_Type component of the cluster is used to control which bitmap loads and which Ref component is used to store its Reference. This is necessary because the reference types are different for each bitmap.
Having set FPGA_Type, Figure 3 shows how to employ the selected resource. A separate Read/Write Control must be coded for each FPGA type.
Closing the resource also requires a case for each FPGA type.
I hope anyone else planning a stepped migration between backplanes can make use of this.To program any DAQ card for use in Linux you need to use Register Level Programming. Unfortunately, Register level programming for the counter/timer products based on the NI-TIO ASIC (includes the 660x boards) is not supported.
-
What is the PCI bus performance of the 1422?
I'm currently using an IMAQ PCI-1422 to acquire images from a camera. The image size is 1280x1024 @ 8-bits a pixel. Currently the camera can only run freely at 20 fps. So this data rate is roughly 26 MB/s. The IMAQ card seems to be able to acquire these images at that rate. However, I need to be able to retrieve these images into system memory at the same rate. At this time, I've only managed to retrieve the images at around 12 fps which is about 16 MB/s. Is this all I can reasonably expect from this card? There is no other activity along the PCI bus except for perhaps minor updates to the video display.
I'm acquiring images using a Grab. I use a callback on the Buffer Done signal to trigger an acquisit
ion running in another thread. Actually, I'd prefer to the acquisition in the callback itself, but I am uncertain as to how the callback is implemented and what I can and can't do in a callback. Is there documentation somewhere that I'm missing?
Oh yeah. I'm using MSVC++ and Windows 98.
ThanksI tried the example and removed the clipping the ROI to the size of the canvas and also took out the image plot to make sure we would get accurate times. I get the same frame rate with that example as I did with my own code (around 12 fps). Also, I neglected to mention that for my own code I placed calls to timers just before and just after the call to imgGrab, and the time difference is what you would expect: about .083 seconds (average) to retrieve one frame.
I know nothing about the internal structure of the PCI-1422, but considering that we are retrieving images from the same SDRAM memory that is being used to acquire images, are we seeing some sort of bus contention on the PCI-1422 itself? Also, the camera I'm using is an evaluation board, and I have access
to the schematics and should soon have access to the CPLD design. So I can verify the design of the camera itself. I'm glad to hear that you expect to be able to transfer at 45MB/sec. That probably means that there is something not quite right either in the camera interface or perhaps in the computer system being used. But if you have any other ideas, I'd be glad to hear them.
Thanks for the response.
Maybe you are looking for
-
Having multiple CAs share the same private key
We are developing a system which implements an HA cluster across two separate geographical locations. Each site will have several Windows Server 2012 machines and at least one DC, and we basically have to do a master-master replication between the tw
-
HT201406 The bottom line appears not work when tried maps and calculator is there any fix for this
My iPhone bottom line on touch screen is very irisponsive( works some times) is there anything I can do about this
-
How to create a standard SOAP request message from a given WSDL file?
Hello, If I have a WSDL file (either from a .net web service or from the famous Amazon web services), what is the best way to generate a SOAP compliant request message? I am having trouble understanding the role of WSDL file in a given web service. Q
-
I want only the Illustrator and Photoshop. Is there a plan to buy for this?
I want only the Illustrator and Photoshop. Is there a plan to buy for this?
-
I lost the serial number of my Flash Cs5 PRO
Posted yesterday a problem about my serial Flash Cs5 Pro. I do not have this number. I have this program for many years and this serial should have been lost on my old PC. Recently, however, every time I open the program, I asked is the serial. I can