search for: lspci

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 2 +- lspci.h | 4 +++ 4 files changed, 82 insertions(+), 2 deletions(-) create mode 100644 ls-ca...

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 2 +- lspci.h | 4 +++ 4 files changed, 82 insertions(+), 2 deletions(-) create mode 100644 ls-ca...

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 9 ++++++++- lspci.h | 4 ++++ 4 files changed, 72 insertions(+), 2 deletions(-) create mode 1006...

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ls-caps.c | 9 ++++++++- lspci.h | 4 ++++ 4 files changed, 72 insertions(+), 2 deletions(-) create mode 1006...

Is there an LSPCI comboot module that someone has written? Or a linux style boot disk that has: a KERNEL b LSPCI c very small size d quick boot time I am currently having to get through a 5 - 7 minute boot cycle with a fedora setup just t...

https://bugs.freedesktop.org/show_bug.cgi?id=101665 Bug ID: 101665 Summary: lspci blocks forever with a GP107M Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.o...

Can anyone point me to a "Writing Puppet recipes for Dummies" doc? I''m trying to do a basic probe using lspci to see if I have a Qlogic HBA installed on the machine, and if so, install the Qlogic scli package. Here''s a shell script of what I''m trying to do: #!/bin/bash vendor=1077 # QLogic model=2422 # 24xx hba /sbin/lspci -n -d $vendor:$model | grep $vendor | grep $model > /dev/n...

...oticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ... http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 ... doesn't match what qemu is doing. Huh? Also note: [root at fedora ~]# ~kraxel/projects/pciutils/lspci -vvsa 00:0a.0 Communication controller: Red Hat, Inc Virtio console [ ... ] Capabilities: [64] VirtIO: Notify BAR=2 offset=00003000 size=00400000 multiplier=00010000 [ ... ] Why multiplier is 64k instead of 4k? Just a tyops? cheers, Gerd -------------- next part -------------- A non-tex...

...oticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ... http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 ... doesn't match what qemu is doing. Huh? Also note: [root at fedora ~]# ~kraxel/projects/pciutils/lspci -vvsa 00:0a.0 Communication controller: Red Hat, Inc Virtio console [ ... ] Capabilities: [64] VirtIO: Notify BAR=2 offset=00003000 size=00400000 multiplier=00010000 [ ... ] Why multiplier is 64k instead of 4k? Just a tyops? cheers, Gerd -------------- next part -------------- A non-tex...

...Intel Corporation 8 Series/C220 Series Chipset >Family USB xHCI (rev 05) >00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >Family USB EHCI #2 (rev 05) >00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >Family USB EHCI #1 (rev 05) > >lspci -s 00:14.0 -v >00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >Family USB xHCI (rev 05) (prog-if 30 [XHCI]) > ??????? Subsystem: ASUSTeK Computer Inc. Device 201f > ??????? Flags: bus master, medium devsel, latency 0, IRQ 25 > ??????? Memory at dd600000 (64-bi...

lspci | grep Digium 03:05.0 Ethernet controller: Digium, Inc. Wildcard TE122 single-span T1/E1/J1 card (rev 11) dahdi_scan So I have a card in a box - lspci shows it... dahdi_scan reports nothing. Is my card dead? Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL:...

I pulled a working TE405P from one box and put it in another box. I compiled the zaptel modules, modprobe zaptel, modprobe wct4xxp, but no lights on the card come on. I do an lspci and the card shows up there. I ran ztcfg -vv and got the error message Unable to open master device '/dev/zap/ctl' so I followed the instructions in README.udev the error message went away, but now when I run ztcfg I just get "0 channels configured" Thanks! Wayne

...se: 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) ??????? Subsystem: ASUSTeK Computer Inc. Device 201f ??????? Flags: bus master, medium devsel, latency 0, IRQ 25 ??????? Memory at dd600000 (64-bit, non-prefetchable)...

...at centos.org Subject: Re: [CentOS] SCSI drives and Centos 7 Date: Sat, 29 Apr 2017 11:19:38 -0700 On 4/29/2017 10:49 AM, Gregory P. Ennis wrote: > I am remote from the unit today, and do not have a good way to look at > the board today, but the contents of /proc/scsi/scsi is : what does `lspci` have to say about this raid card ? John, Thanks for the prompt : lspci demonstrates : 02:01.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID (rev 01) 02:02.0 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10) 02:02.1 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10) Greg

...close to a solution... > > > Nick > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > what do you get when you boot the VM (I imagine with supergrub2 you described) and run this lspci lspci -kn in particular in respect with scsi devices ad kernel modules used eg in a VM of mine under oVirt [root at ractorshe ~]# lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 I...

...he following output: # nvidia-detect Error getting device_class nvidia-detect also quits with exit-code 255. Could this be a bug in nvidia-detect? Or is it an unsupported configuration? The following hardware is detected, it seems some sort of unknown Intel device is detected by the OS: # lspci | grep VGA 00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4 21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1) # lspci -n | egrep '00:1f.5|21:00.0' 00:1f.5 0000: 8086:a2a4 21:00.0 0300: 10de:1cb2 (rev a1) Tested with the following versio...

https://bugs.freedesktop.org/show_bug.cgi?id=103409 Bug ID: 103409 Summary: [GM107] reboot/suspend/lspci hang with nouveau Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedeskt...

Hello all, I'm debugging a card that the Nvidia blob recognizes as an 8200 but lspci says is a GeForce 9200M G. ?My original bug report is in launchpad.(https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/557895), but I have been trying to debug further by using the nightly builds. It still requires the noaccel flag to be set to work. I was wondering if there...

Attached full dmesg and lspci for the box experiencing this problem -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg Type: application/octet-stream Size: 73592 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121113/d0a58abf/attachme...

lspci dont show Digium card. The motherboard is Intel 945gnt. 00:00.0 Host bridge: Intel Corporation 945G/P Memory Controller Hub (rev 02) 00:02.0 Display controller: Intel Corporation 945G Integrated Graphics Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Por...