[EMAIL PROTECTED] wrote: > Here are what seem to be the pertinent portions of dmesg output. Let me know > if you want the whole thing and I'll send it directly. > > I don't know what all that corrupt SPROM CRC stuff is all about. I followed > the directions to extract the firmware to /lib/firmware using b43-fwcutter. > Not sure if that's the same thing, though. > > Linux version 2.6.24-gentoo-r4 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Gentoo > 4.1.2 p1.1)) #1 SMP Wed May 14 18:11:04 EDT 2008 > [snip] > PCI: Setting latency timer of device 0000:02:00.0 to 64 > ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) > ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) > ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) > ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) > ssb: WARNING: Invalid SPROM CRC (corrupt SPROM) > ssb: Unsupported SPROM revision 255 detected. Will extract v1 > WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask() > Pid: 5404, comm: modprobe Not tainted 2.6.24-gentoo-r4 #1 > [<f96423a5>] [<f9643293>] [<f9645381>] [<f9642981>] [<f96446a5>] > [<f964420f>] [<f9642e63>] [<f9643f7c>] [<f9642f67>] [<c0339d7d>] > [<f96447cd>] [<c033b853>] [<c0398838>] [<c0468689>] [<c0398948>] > [<c039898e>] [<c0397e4b>] [<c039869f>] [<c0398948>] [<c03980f6>] > [<c033b990>] [<f90c9040>] [<c013717c>] [<c013fded>] [<f967c914>] > [<c03982a1>] [<c0103dc2>] ======================= > ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0 > [snip] > > lspci -nnv output (for completeness) > > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4310 USB > Controller [14e4:4315] (rev 01)
I also have one of these devices that are reported as a BCM4310 USB. It has an LP-PHY, and is not supported by any current driver. It also has a rev 8 SPROM and we do not know where the information is stored in the PROM. In fact, I am working on the reverse engineering in order to write the specifications so that the driver can be modified. As much as I hate to make this recommendation, your only recourse is to use ndiswrapper and the Windows driver. I was fortunate enough to have a BCM4311/2 on the shelf, which I used to replace the BCM4310 - at least for the moment. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
