Please excuse my lack of knowledge, but what is the basic function of
slmodemd? I'm trying to understand the impact on driver support for modems
using slmodem.
Also, I tried removing slmodem from my Ubuntu 8.04 installation by reversing
the steps previously taken to install slmodem by a ./setup script that came
with the slmodem package.
I used the following commands to uninstall slmodem for my failed PCI
SmartLink 1800 Chipset Modem that is no longer installed in my Ubuntu 8.04
installation:
sudo modprobe -r slamr
sudo modprobe -r ungrab-winmodem
sudo rm /lib/modules/2.6.24-26-386/extra/*.ko
sudo rmdir /lib/modules/2.6.24-26-386/extra
sudo depmod -a
sudo dpkg -p sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb
* Received an error on the last command, so I used Synaptic Package Manager
to completely removed the program
(sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb ) and its
configuration files, if any.
I ran the latest scanModem, and noted toward the bottom of ModemData.txt
(see attached) it indicated the following:
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
I could not locate the ttySL0 file in either the /dev or /etc/udev/
directories. That's very mysterious to me. But, that's nothing new...Linux
overwhelms me a times. :)
So...did I completely removed slmodem from my Ubuntu 8.04 installation? Or,
did I miss some steps?
I appreciate any assistance or advice.
Thanks,
Ken
----- Original Message -----
From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx>
To: "Keneth W. Jones" <kjones@xxxxxxxxx>
Cc: <discuss@xxxxxxxxxxxxx>
Sent: Monday, December 28, 2009 6:52 PM
Subject: Re: Ken, USA kernel 2.6.24-26-386: Request Replacement
Recommendation for a PCI SmartLink 1800 Chipset Modem
Ken,
Functionality of slmodemd has been lost in the 2.6.28 kernels,
and this List has no one with skills to do the fix, even if the
problem is in the Open Source section of its code.
Thus you may be better off choosing one of the modem (chipsets)
remaining functional.
Read the InfoGeneral.txt output by scanModem for options. But for a
few dollars more,
you could get either and internal modem or USB modem served entirely
by Open Source Linux code.
MarvS
scanModem maintainer
On Mon, Dec 28, 2009 at 4:23 PM, Keneth W. Jones <kjones@xxxxxxxxx> wrote:
(Attached is an old ModemData.txt that was created; prior, to a power
surge,
that shorted out my PCI Smartlink 1800 Chipset Modem).
I'm currently looking for a replacement PCI Modem that is supported by
the
Sasha Khapyorsky's maintained slamr modem driver, and I'm having some
difficuties in locating a suitable inexpensive replacement PCI modem via
the
Internet.
I've been able to locate some inexpensive PCI SmartLink 2801 chipset
modems,
but I'm unsure if the SL2801 chipset on these PCI modems is supported by
the
slamr driver.
Based on the information I acquired from the Internet concerning
supported
PCI SmartLink chipset modems, the slamr driver supports the following:
SL1500: SmartPCI56 (3-chip)
SL1800: SmartPCI561 (3-chip)
SL1900: SmartPCI562 (2-chip, silicon DAA)
SL1801: SmartPCI563 (2-chip, transformer DAA)
And, there is no mention of support for a PCI SL2801 chipset modem.
Any recommendations for an inexpensive PCI modem replacement is
appreciated.
Thanks,
Ken
P.S. Not having a modem in my dual boot Windows XP/Ubuntu (Hardy 8.04)
desktop PC is a pain. :(
Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.24-26-386
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in YourCountry
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for dialup service.
Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.24-26-386 (buildd@vernadsky) (gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)) #1 Tue Dec 1 17:56:13 UTC 2009
scanModem update of: 2009_12_26
The dkms driver upgrade utilities are installed,
Modem drivers blocked from loading during bootup are listed in /etc/modprobe* file lines:
/etc/modprobe.d/blacklist-restricted:blacklist ltmodem
Potentially useful modem drivers now loaded are:
Attached USB devices are:
ID 6253:0100 TwinHan Technology Co., Ltd Ir reciver f. remote control
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html
A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
------------------------------------------------
with USB and bridge devices not displayed.
If your modem is connected by an external serial cable,
or mounted internally on an ISA card, scanModem would not access it.
Try with Root permission
$ sudo wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
sudo gedit /etc/wvdial.conf
will be able to dial out with Root permission:
sudo wvdial
Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems
If the above tests fail, please provide any independent information available on your modem.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System
Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information. From the Driver Details TAB, copy out the VENdor and DEVice information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.2.4
and the compiler used in kernel assembly: 4.2.4
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.24-26-386/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking pppd properties:
-rwsr-xr-x 1 root dip 269256 2007-10-04 14:57 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/blacklist-restricted:blacklist ltmodem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
