search for: setpci

...ttest and we found that this was (in their words) 'extremely low', with 'best' and > 'worst' readings of 99.975586% and 99.963379% respectively. Might want to give PCI latency setting a try, it helped for me. My ZTTEST would drop occasionally to 99.95% until I set: setpci -v -s 01:01.0 latency_timer=ff <--Digium PRI card setpci -v -s 01:04:0 latency_timer=ff <--Digium 401 4 X FXS setpci -v -s XX:XX:X latency_timer=0 <--1 entry for every other PCI card in system from LSPCI output, modify XX:XX accordingly Before setpci I would get best in ZTTEST at 99.9877...

Is there anything special I need to know in Dom0 when trying to use setpci to enable and move the boot ROM on an Ethernet adapter? I am able to enable the ROM, but it is in the same place as the RAM, and I can''t seem to move it. I have 1Gb of RAM, which I believe is mapped from 0x00000000 to 0x3fffffff, but the ROM is set to 0x3ff00000, and using something like:...

Has anyone had any compatibility issues with a TE110P card installed on a Dell Poweredge 1950? I noted the following error on the LCD display of the Dell Poweredge 1950: E1711 PCI PErr Slot 1 E171F PCIE Fatal Error B0 D4 F0. The Dell hardware owners manual states that it means the system BIOS has reported a PCI parity error on a component that resides in PCI configuration space at bus 0,

If a PCI device has been passed to a domU is it possible to set its latency from the domU or does it have to be done from the domO? When I attempt to set a devices latency from the domU with setpci I do not receive an error message back indicating a problem, however the latency as viewed with lspci -v is not changed. The same setpci command from the dom0 successfully changes the latency and the change is shown with lspci -v on both dom0 and the domU to which the device has been passed. - Be...

I was browsing the applications developed in zaptel and came across zttest. After I run it, I get the following: Opened pseudo zap interface, measuring accuracy... 99.975586% 99.987793% 99.987793% 99.987793% 99.987793% 100.000000% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.975586% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%

...ap with no apparent ill effects. Can anyone commment on long term effects with moderate load (say, 30 SIP phones / 2-3K calls /day) 3. Can anyone comment on using ramdisk as swap and whether this is a good idea or bad idea? I'm using 2.6 kernel. I've modified the PCI latency in rc.local: setpci -v -s <my T100P address> latency_timer=ff Anyone else have any performance tips?

...that the BIOS does not give me the ability to manually set the IRQ. I've even taken one of the TE121's out of the server (it isn't being used anyways). Everything I've done so far has not fixed it. All the cards (as well as USB1) all use IRQ 16. The other option given was to use setpci, but I am unfamiliar with that command. I did what I could to try and find the setting (based on what the man page on Ubuntu's web site) where I could see the value 16, but not getting anywhere. I know that this is more of an Asterisk forum than Digium. If I need to put in a case at Digium I...

...,7 +69,7 @@ force: lib/config.h lib/config.mk: cd lib && ./configure -lspci: lspci.o ls-vpd.o ls-caps.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) +lspci: lspci.o ls-vpd.o ls-caps.o ls-caps-vendor.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) setpci: setpci.o common.o lib/$(PCILIB) LSPCIINC=lspci.h pciutils.h $(PCIINC) diff --git a/ls-caps-vendor.c b/ls-caps-vendor.c new file mode 100644 index 0000000..edcc44a --- /dev/null +++ b/ls-caps-vendor.c @@ -0,0 +1,59 @@ +/* + * The PCI Utilities -- Show Vendor-specific Capabilities + * + * Copyrig...

...,7 +69,7 @@ force: lib/config.h lib/config.mk: cd lib && ./configure -lspci: lspci.o ls-vpd.o ls-caps.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) +lspci: lspci.o ls-vpd.o ls-caps.o ls-caps-vendor.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) setpci: setpci.o common.o lib/$(PCILIB) LSPCIINC=lspci.h pciutils.h $(PCIINC) diff --git a/ls-caps-vendor.c b/ls-caps-vendor.c new file mode 100644 index 0000000..edcc44a --- /dev/null +++ b/ls-caps-vendor.c @@ -0,0 +1,59 @@ +/* + * The PCI Utilities -- Show Vendor-specific Capabilities + * + * Copyrig...

...,7 +69,7 @@ force: lib/config.h lib/config.mk: cd lib && ./configure -lspci: lspci.o ls-vpd.o ls-caps.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) +lspci: lspci.o ls-vpd.o ls-caps.o ls-caps-vendor.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) setpci: setpci.o common.o lib/$(PCILIB) LSPCIINC=lspci.h pciutils.h $(PCIINC) diff --git a/ls-caps-vendor.c b/ls-caps-vendor.c new file mode 100644 index 0000000..4cdfe22 --- /dev/null +++ b/ls-caps-vendor.c @@ -0,0 +1,76 @@ +/* + * The PCI Utilities -- Show Vendor-specific Capabilities + * + * Copyrig...

...,7 +69,7 @@ force: lib/config.h lib/config.mk: cd lib && ./configure -lspci: lspci.o ls-vpd.o ls-caps.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) +lspci: lspci.o ls-vpd.o ls-caps.o ls-caps-vendor.o ls-ecaps.o ls-kernel.o ls-tree.o ls-map.o common.o lib/$(PCILIB) setpci: setpci.o common.o lib/$(PCILIB) LSPCIINC=lspci.h pciutils.h $(PCIINC) diff --git a/ls-caps-vendor.c b/ls-caps-vendor.c new file mode 100644 index 0000000..4cdfe22 --- /dev/null +++ b/ls-caps-vendor.c @@ -0,0 +1,76 @@ +/* + * The PCI Utilities -- Show Vendor-specific Capabilities + * + * Copyrig...

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

...bus/pci/devices/0000:00:1c.0/rescan 4. Load nouveau driver 5. Start X I worked through the rescan codepath until I had isolated the specific code which magically makes things work (in pci_bridge_check_ranges). Having found that, step 3 in the above test procedure can be replaced with a simple: setpci -s 00:1c.0 0x28.l=0 > When you say "parent PCI" bridge, is that actually the device you see in > "lspci -tv"? On a Dell XPS 9560, the GPU is under a different device: > > -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM...

https://bugs.freedesktop.org/show_bug.cgi?id=75985 Priority: medium Bug ID: 75985 Assignee: nouveau at lists.freedesktop.org Summary: HDMI audio device only visible after rescan QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jean-louis at

...ks just fine, there is no audio. I asked about this on IRC, the logs are at <https://people.freedesktop.org/~cbrill/dri-log/index.php?channel=nouveau&highlight_names=&date=2017-11-24#t-2034>. The summary is that I tried running the following script (after stopping X): rmmod nouveau setpci -s 01:00.0 0x488.l=0x2000000:0x2000000 echo 1 > /sys/bus/pci/devices/0000:01:00.0/remove #echo 1 > /sys/bus/pci/devices/0000:00:01.0/rescan echo 1 > /sys/bus/pci/rescan modprobe nouveau But that did not help. I then started X again, and lspci still shows only $ sudo lspci -nn -d 10de: 0...

Hello List, first let remind the question and the answers: http://www.networkupstools.org/docs/FAQ.html#_my_powermac_g4_won_8217_t_power_back_up_by_itself_into_linux_after_the_ups_shuts_down_what_can_i_do_about_this As a matter of fact my box is not a `Power Mac G4' but a `mac mini server' (macmini4,1), and it is Linux Debian box (Squeeze): the main issue is that the box does not boot

...t, etc (to give you more IRQ choices). Run /usr/src/zaptel/zttest before and after and see if it makes any difference. If it does (i.e. ZTTEST yields ~98.X% before and ~99.X% after) then right there that's going to help. I have used these statements in /etc/rc.d/rc.local to good effect (YMMV) setpci -v -s 01:04:0 latency_timer=ff <--Specific statement for Digium TDM04, you will have to do lspci -vv for the pci vendor id of your specific Digium card setpci -v -s XX:XX:X latency_timer=0 <-- Replace XX:XX:X with the PCI Vendor ID of every other card that lspci -vv recognizes. What the se...

OK... maybe I got a little anxious and ran out and bought a Tyan GX28 with dual Opteron (dual core) processors. (It is a nice server ;) ) I did neglect to find out that you can not manually set the IRQ's on this motherboard. I am now stuck sharing an IRQ with the ethernet controller and no foreseeable end to my dilemma. I have a Digium TE210P and zttest consistently runs at 99.97% which

...Load nouveau driver > 5. Start X > > I worked through the rescan codepath until I had isolated the specific > code which magically makes things work (in pci_bridge_check_ranges). > > Having found that, step 3 in the above test procedure can be replaced > with a simple: > setpci -s 00:1c.0 0x28.l=0 > >> When you say "parent PCI" bridge, is that actually the device you see in >> "lspci -tv"? On a Dell XPS 9560, the GPU is under a different device: >> >> -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v6/7th Gen Core Process...