Pavel Roskin <[EMAIL PROTECTED]> writes: > Quoting Jim Haynes <[EMAIL PROTECTED]>: > >> This relates to the youngster I am trying to help get into Linux >> and get networking going. I reported earlier we are using the >> Netgear WPN311 wireless PCI card. Here is what lspci -vn -d 168c: >> reports: >> >> 00:0c.0 0200: 168c:ff16 (rev 01) >> Flags: busmaster, medium devsel, latency 32, IRQ11 >> memory at e41200000 (32 bit, non-prefetchable) [size=64k] >> Capabilities: [44] Power management version 6 >> >> 00:0c.1 0700: 168c:ff96 (rev 01) (prog-if 02 [16550]) >> Subsystem: 168c:ec96 >> Flags: busmaster, medium devsel, latency 32, IRQ16 >> I/O ports at d400 [size=8] >> memory at e4131000 (32-bit, non-prefetchable) >> Capabilities: [44] Power management version 0 [size=4k] >> Kernel driver in use serial >> >> (above subject to possible errors in reading my writing instead of >> writing it to something machine-readable that I can carry around) > > That's strange. I've never heard of Atheros devices with a serial > port on board. And the device ID "ff16" is not in the PCI ID table of > the devices supported by ath5k. There is nothing even remotely close > to that. Yet the memory size is correct, even the device class is > "correct" (Atheros uses 0x200, which means Ethernet). Maybe your > lspci is showing something wrong. > > Anyway, you device is supported somehow, and the IP configuration > issues are not related to the driver.
Googling for the pci id got me http://madwifi.org/ticket/198 which seems to suggest that it's a hardware compatibility problem. Is this an old (pre PCI 2.2) PC? Bjørn -- You must be a real SysThug to think that Lassie was dead _______________________________________________ ath5k-users mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-users
