Hi Marvin
Thanks for the quick response and stuff you sent.
I've tried under karmic 32 bit and did not succeed. On dialout I got a
'no carrier' warning that continued indefinitely. No luck playing with
alsa support and settings.
I had a few issues with failed installs, and ended up running the
commands manually.
Here are a couple things I noticed in the ./setup file:
* slmodemd was being un-installed by the ./setup file.
Line 35: dpkg -i *.deb
(Installs the deb package)
Line 55:
mv /usr/sbin/slmodemd /usr/sbin/slmodemd.version_2.9.9
(renames slmodemd which was just installed)
Line 56: cp slmodemd /usr/sbin/
(tries to copy a file which doesn't exist, and fails)
All subsequent calls on slmodemd fail as the only version
on /usr/bin/ is named "slmodemd.version_2.9.9"
* Line 110: $ sudo gedit /etc/init.d/sl-modem-daemon
Should read: $ sudo /etc/init.d/sl-modem-daemon restart
* Line 96 onward to end: seems to be something missing and there
are a few syntax errors (not that I'm at all an expert). Also,
text that looks like it should be echoed, isn't being echoed in
terminal.
Anyway, I had hoped that my boot issues would be solved after installing
the smartlink modules. However, I gave up and pulled the PCI card, as
the IRQ problem on my machine continued even after an attempt at
blacklisting and updating initramfs.
Thanks again for the help
David
On Wed, 2009-11-11 at 14:59 -0500, Marvin Stodolsky wrote:
> Jacques,
> attached is for the Smartlink/Ubuntu/ folder
>
> David,
> FYI a driver can be compiled for USB on 32 or 64 bit systems, but
> formally it is not Linux legal. We do not as yet have a slamr success
> report under 2.6.31 kernels. 2.6.30 was OK on a SLACKware system. But
> there was a failure to dialout under 2.6.31 on the same SLACK system.
> Some of these failures prove to be kernel specific. So it is worth
> trying under Ubuntu 32 bit.
>
> After the
> $ sudo ./setup
> set the country to SOUTHAFRICA using
> $ sudo gedit /etc/default/sl-modem-daemon
>
> Presently report back to the List, not me directly
>
> Marv
>
> On Wed, Nov 11, 2009 at 2:50 PM, Marvin Stodolsky
> wrote:
> > 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 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
> >>
> >>
> >
