I got similar problem in the AMD64 based systems. There is a bug in the
AMD64 based the system. BIOS blocked any access beyond 256 bytes. I can
dump extended configuration registers in the Intel based system.
Regards,
Joyce
On 04/22/10 02:53 PM, Ron Babich wrote:
Hi all,
I've been trying to get 'lspci -xxxx' to display the extended
configuration registers for one of my devices, without success.
So far, I've only had this problem under Ubuntu, so I originally
submitted this issue to the Ubuntu bug tracker. The details are here:
https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/563458
I've tried installing the latest version of pciutils from source, with
no change. One thing that might be relevant is that Ubuntu 8.04 ships
with a much newer kernel (2.6.24-27) than the machine I'm comparing
against (CentOS 5.4, kernel version 2.6.18-164), where lspci behaves
as expected.
I've tried the various access methods (linux_sysfs, linux_proc, and
intel_conf1), again with no change. If I try to explicitly probe one
of the extended registers (0x180 in this example) using 'sudo setpci
-s 01:00.0 180.B', it always prints 'ff', which is the same thing I
get if I do it without root privileges.
For the sake of comparison, I've been looking at the video card in the
above examples, but I'm really interested in figuring this out so that
I can diagnose a chipset configuration problem. Any advice would be
much appreciated.
Thanks,
Ron
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
