David, slamr cannot serve on a 64 bit system because there is a precompiled 32 bit componet slamr will compile on a 32 bit system, see below. On a 32 bit system ungrab-winmodem must be loaded before slamr to relieve the conflict with serial port capture. I'll separately send you a package for a 32 bit installation. MarvS scanModem maintainer On Wed, Nov 11, 2009 at 1:23 PM, David Dallas <djdallas.email@xxxxxxxxx> wrote: > Hi. > > I'm planning on using Ubuntu Karmic x86_64. I see there are some issues > with 64 bit and modems, so I can switch to i386 if my modem will > definitely work (a fax machine would be useful). > > I tried building the slamr and associated modules (correct versions not > available on the site yet), but slamr.ko and slusb.ko are not being > created during the builds. Not sure why. > > I've included dmesg.txt as there seems to be a kernel regression at play > as well. The pc sometimes fails to boot as it seems the kernel is > loading the wrong driver for the modem, then overloading it: > [ 73.705046] ttyS3: 32642 input overrun(s) > [ 73.868081] serial8250: too much work for irq17 > [ 73.995483] serial8250: too much work for irq17 > etc. > If these errors happen while the graphical logon screen is loading then > the pc locks up and needs to be hard-reset. Never did that before. It > does the same with the i386 version of karmic. The output of lspci > confirms that IRQ-17 is assigned to a Motorola SM56 modem and that the > diver is "serial", but that no kernel module is in use. Is my reasoning > correct here, because I'd like to report a bug at launchpad? > > Any help getting the modem working would be appreciated. Alternatively > some help on how to blacklist the appropriate pci device by it's id (can > you do that?) or blacklist the offending driver. (As above, I think it > might be the serial driver, but I'm not sure if I can safely blacklist > that module.) Lastly, if nothing else is going to work, just let me know > if I should pull the pci card. > > Many thanks, > David > >
