Jeff 1057:3052 (Motorola) works, miraculously, because the PCI ID 1057:3052 was added into the init recognition code 11d4:1805 Analog Devices fails, even though its PCI ID, was added after the reported success with 1057:3052 10b9:5459 (Smartlink SL1800) initializes OK, but hangs system on dialing This is BAD because slamr was written to support this modem. Perhaps check for a resource comflict. 14e4:4212 (Broadcom) "cannot init card"- There is no hope for 14e4:4212 cards under 2.6.n kernels. Last support was in mid 2.4.n Just get the current scanModem and run: $ ./scanModem test 1057:3052 ( or orther PCI IDs) to get cogent gossip/URLs MarvS On 7/18/07, Jeff Trull <linmodemstudent@xxxxxxxxx> wrote:
Hi all, I'm in the unusual position of having access to a lot of used winmodems, due to volunteering with some electronics reuse organizations, and I've recently started looking at modems that may be compatible with the Smartlink driver. I judged which ones might work by looking at the slamr code (specifically, amrmo_init.c). There's a nice list in there defined in the amrmo_pci_tbl structure, and I decided to get some with matching PCI id's and try them. Here are the results: 1057:3052 (Motorola) works 10b9:5459 (Smartlink SL1800) initializes OK, but hangs system on dialing 11d4:1805 (Motorola on chip but lspci says Analog Devices) "cannot init card" 14e4:4212 (Broadcom) "cannot init card" The Smartlink brand card system hang occurs on kernels ranging from 2.6.8 (Debian Sarge) to 2.6.20 (Ubuntu Feisty) and on more than one such modem (I have two). The two "cannot init card" failures give somewhat different output in the system log when I enable debug messages (with the debug= module parameter). 11d4:1805 dies pretty quickly, complaining about "BaseAddress==0, can not initialize IOSpace". The Broadcom card gets further, detecting a SiL3052 chipset, revision three, and assuming a 32.768MHz crystal (which is wrong!) but failing "because DAA not ready". I'd be interested in hearing from people who've tried any of this hardware and can report success (and, especially, the debug logs from the driver). Thanks and regards, Jeff Trull
