Comment 56 for bug 375148

I suspect the compile failed because there have been over 100 updates sent out
for Karmic between the two compiles.

While the device was created, the driver did not work. No amount of tweaking
got wvdial to get a dial tone, but the phone line was tested with a regular
phone to ensure there was dial tone prior to the test.

I have no reason to believe this modem doesn't work, but I can power down and
swap in one of the other modems like it I have here. I guess it won't matter
since the device won't survive a reboot and with all of these updates that's
nearly every day.

On Sunday 06 September 2009 04:48:59 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> Actually I don't think there's a reason to test the old version of
> sl-modem, since according to Roland's experiment, /dev/ttySL0 did get
> created when he used sl-modem version that's in karmic
> (2.9.11~20080817-3ubuntu2).
>
> As for the reason why DKMS build failed with him, is that dkms script in
> sl-modem uses bash commands (pushd/popd) which worked in Jaunty, yet the
> dkms version in karmic had this change in Aug 21st:
>
> - When possible, run builds as the 'nobody' user rather than root.
>
> since the default shell of 'nobody' is dash, hence those commands
> failed. (Thanks for Mario Limonciello for the tip on this one)
>
> Yet I don't understand why it worked for him two days ago, then failed
> yesterday !
>
> Anyways, when Roland installed the slamr module using module-assistant,
> /dev/ttySL0 did get created, then when he restarted it vanished. Which
> makes me again suspect that this behaviour is because of Ubuntu's policy
> of not having static devices in /dev, so when he rebooted the static
> /dev/slamr0 device, that was created during install of
> sl-modem-modules-$KVER (that resulted from module-assistant), got
> removed at reboot.
>
> If someone is willing to experiment wether what I said is true or not,
> please install sl-modem modules using module-assistant, then if
> /dev/ttySL0 did get created, and then disappear again after reboot, try
> running:
>
> sudo dpkg-reconfigure sl-modem-modules-$(uname -r)
>
> Unfortanely, I don't always have a laptop with smartlink modem chip
> under my hands. That's why I ask those who are suffering the bug to
> help.
>

--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.logikalsolutions.com