Corbin Bird <corbinbird <at> charter.net> writes:
> The hardware ID's database may need to be updated ( or supplemented ).
> The package "sys-apps/pciutils" has the hardware database included in it.
looking at the ebuild for 'pci-utils' we see::
RDEPEND="${DEPEND}
sys-apps/hwids
So if you want the latest data on hwids, install::
'sys-apps/hwids-99999999'
> I have a 990FX chipset MB that is constantly ID as a 880 chipset board.
> No info on 990FX chipsets found in the hardware ID's database.
> The kernel keeps applying a 880 chipset workaround for the PCI bus,
> every boot.
>
> Same problem I think, different hardware.
OK, so both of you guys should use serial sniffers and usb sniffers and log
those sessions on a separate machine for rigorous analysis. Commercial
sniffers are very user friendly. Some cheap embedded boards can sniff usb
readily (but you'll have to search them out yourself).
For a usb sniffer, you may need special hardware to intercept those singnals
from the actual communications link. sniffing from inside
of a host is sometime problematic on catching every charcter, timings,
and other such critical signal information. sniffing RS-232 is well
documented around the net. When I sniff usb, I try to first use usb-1.0
or 1.1, as the slower speeds are easier to watch and collect critical data.
good-hunting.
hth,
James
