search for: pcilib

...problem but after I get some errors like : Applying Intel Microcode update: FATAL: Error inserting microcode (/lib/modules/2.6.9-78.0.1.ELsmp/kernel/arch/i386/kernel/microcode.ko): Invalid module format ERROR: Module microcode does not exist in /proc/modules .... Starting MPT Fusion (ctl) drivers: pcilib: Cannot open /proc/bus/pci^M lspci: Cannot find any working access method. pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working...

...e 100644 ls-caps-vendor.c diff --git a/Makefile b/Makefile index 8d49afa..39a07d1 100644 --- a/Makefile +++ b/Makefile @@ -69,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 --- /d...

...OS5.1 as dom0. I have hidden a network interface in dom0 to pass it to domU. The domU can come up with the NIC when it''s OS is CentOS5.1 or RHEL5. But when it comes to RedHat4.5 , the NIC can not be found. As I type the command "lspci" in RHEL4.5 domU, it returned: pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. And I found the three lines in "dmesg" output: XENBUS: Device with no drvier: device/vbd/51713 XENBUS: Device with no driver: device/pci/0 XENBUS: Device with no driver: device/vif/0...

...e 100644 ls-caps-vendor.c diff --git a/Makefile b/Makefile index 8d49afa..39a07d1 100644 --- a/Makefile +++ b/Makefile @@ -69,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 --- /d...

...e 100644 ls-caps-vendor.c diff --git a/Makefile b/Makefile index 8d49afa..39a07d1 100644 --- a/Makefile +++ b/Makefile @@ -69,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 --- /d...

...e 100644 ls-caps-vendor.c diff --git a/Makefile b/Makefile index 8d49afa..39a07d1 100644 --- a/Makefile +++ b/Makefile @@ -69,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 --- /d...

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

...ding facts in uspspuppetfacts info: Loading facts in network info: Loading facts in buildinfo info: Loading facts in hcs_service info: Loading facts in os_version info: Loading facts in memorysize info: Loading facts in uspspuppetfacts info: Loading facts in network info: Loading facts in buildinfo pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. info: Caching catalog for info: Applying configuration version ''1306952659'' notice: /Stage[main]/Common/Service[cron]/ensure: current_value stopped, should be running (noop) notice: /Stage[main]/Common/Notify...

...U with pci = [ ''00:1d.0'' , ''00:1d.1'' , ''00:1d.2'' , ''00:1d.3'' , ''00:1d.7'', ''02:01.0'' , ''02:02.0'' ] but nothing shows up in the domU: [root@web ~]# lsusb [root@web ~]# lspci pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. [root@web ~]# How can I make the domU recognize the two LAN interface and 2 usb devices (usb drive and ethernet interface) plugged in? Thanks, Pascal Here is part of the dmesg pciback 0000:00:1d.0: seizing device pciback 0...

...was not installed properly). SoSC installs just fine from the CD, but will not invoke: $ wine Streets.exe No PCI Bus detected. Searching on Google Code suggests that the only source for this message (with the trailing period and without "PCI:" in front of it) is Glide in /swlibs/newpci/pcilib/fxpci.c; the PCI_ERR_NO_BUS error comes from pciOpen() after it's attempted two different detection methods and both have failed. That's as far as I can understand it. I've never heard of Glide before, but apparently it's something to do with OpenGL. Is there some underlying OpenGL...

...g Linux 2.6.32-5-xen-amd64 ...' multiboot /boot/xen-4.0-amd64.gz placeholder module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder root=/dev/mapper/traveller-xen ro quiet echo 'Loading initial ramdisk ...' module /boot/initrd.img-2.6.32-5-xen-amd64 } lspci (made later in Fedora): pcilib: Cannot open /proc/bus/pci 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960...

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

Hi, This series targets automatic boot menu generation, but most of it is the Lua upgrade, because I got tired reading deprecated API docs. It's mostly a straightforward forward port of the earlier Syslinux specific changes to Lua 5.1, except that: * I chose the add a stub getenv() implementation to the COM32 API instead of #ifdefing out all the references in Lua, and * I kept oslib

Hello all Xen devels, I''m writing howto''s in brazilian portuguese language about Xen-3.3.0 stubdom, pv-grub and others configurations. Following what is written in xen-3.3.0/stubdom/README, I tried start a HVM but without success. When I start the virtual machine calling ''xm create hvmtest'' command, in a few seconds the virtual machine is dead (see