From: Samuli Suominen <ssuominen@gentoo.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Kay Sievers <kay@vrfy.org>
Subject: Re: lspci -k is broken with depmod from kmod since it doesn't generate modules.pcimap anymore
Date: Wed, 27 Mar 2013 00:37:08 +0200 [thread overview]
Message-ID: <51522314.7050203@gentoo.org> (raw)
In-Reply-To: <CAErSpo5wG8FUyomySdze56-e9Jr+3DevoCGGAnhLM8vpOBvQ5w@mail.gmail.com>
On 27/03/13 00:35, Bjorn Helgaas wrote:
> On Tue, Mar 26, 2013 at 3:31 PM, Samuli Suominen <ssuominen@gentoo.org> wrote:
>> The depmod from kmod no longer generates file modules.pcimap, and lspci -k
>> relies on that as noted at:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=462982
>>
>> null pciutils-3.1.10 # grep -r modules.*map *
>> ls-kernel.c: sprintf(name, "/lib/modules/%s/modules.pcimap",
>> uts.release);
>> lspci.c:char *opt_pcimap; /* Override path to Linux
>> modules.pcimap */
>> lspci.c:"-p <file>\tLook up kernel modules in a given file instead of
>> default modules.pcimap\n"
>> lspci.man:.RI /lib/modules/ kernel_version /modules.pcimap.
>
> I don't think this is a kernel problem, and I don't know where to
> point you. Maybe Lucas or Kay will know?
This is the mailing list referred at pciutils homepage:
http://mj.ucw.cz/sw/pciutils/
"Feedback:
You can ask questions and report bugs on the linux-pci mailing list
running on Vger"
Some bug tracking system would be nice.
next prev parent reply other threads:[~2013-03-26 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 21:31 lspci -k is broken with depmod from kmod since it doesn't generate modules.pcimap anymore Samuli Suominen
2013-03-26 22:35 ` Bjorn Helgaas
2013-03-26 22:37 ` Samuli Suominen [this message]
2013-03-26 22:44 ` Bjorn Helgaas
2013-03-27 15:11 ` Lucas De Marchi
2013-03-27 17:00 ` Kay Sievers
2013-04-01 11:45 ` Martin Mares
2013-04-01 13:46 ` Martin Mares
2013-04-01 14:09 ` Samuli Suominen
2013-04-01 19:26 ` Martin Mares
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51522314.7050203@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=bhelgaas@google.com \
--cc=kay@vrfy.org \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox