- kppp does not reach /dev/ttySHSF0 etc....
Problem well known as udev setup problem.
I [J.G.] am referring to
There is a very simple solution, not limited to Conexant modems (it will of course work for /dev/ttyLT0, etc...
Note that for the SmartLink driver (slmodem) this is automatically performed when launching slmodemd, thus for slmodem this FAQ is irrelevant.
It is true that /dev/ttySHSF0 and /dev/ttySHCF0 do not appear in the kppp
modem selection menu but making them known (and on top of list) just
requires adding one or two lines in file ~/.kde/share/config/kppprc
The file is structured in sections.
One of the sections is [Modem]
If not found in the file, the line
[Modem] should be added, and then in the [Modem] section
Device=/dev/ttySHSF0 and/or more.
I failed to find (no real effort beyond find / -name kppprc) where the
same can be done at the global level, not only user level.
- Frequent mistake
in loading the SmartLink driver in ALSA mode.
- Selection of a driver for a PCTel
- HCF modem rings BUSY after having dialed the number: add AT F X1
in the initialization string.
- Newbies' problems installing Linuxant drivers under Mandrake 10.x
Two utilities for easy installation:
For HSF modems.
For HCF modems.
How-to in text.
- Everything seems to work fine but kppp does not work.
Something else may be wrong or kppp is not properly configured.
wvdial instead of kppp.
If it works and you still feel an uncontrollable desire for kppp, then
learn in detail how to make your kppp configuration equivalent to
the frequent serial<->slmodem clash with kernels 2.6.10 and higher.
- RedHat 9, Fedora, PCTEL 2304WT: solved by
Murray, many thanks Bill
- I have installed ltmodem but
Support status under 2.6.nn kernels
- Compilation problems with
- You have an AMR /
- You installed slmdm-2.7.14 and it does not work.
Is your chipset
a genuine SmartLink? No? Do not know for sure? Use slmdm-2.7.10 or
slmdm-2.9.x, it may work.
Otherwise carefully read the output of the
- The well known
problem: failure to find remote machines by name, is handled in the link above.
DNS is/are addresses of computers who know how to direct your computer to the place which you want to reach. These addresses are make known
to your computer by two possible ways:
- Automatically in the connection mechanism known as DHCP. This is almost always the case nowadays.
- Manually by inserting them yourself in the file /etc/resolv.conf if
the job was not done automatically.
- Usually but not always the automatic procedure overrides reexisting
DNS in computer memory.
After that memo was written, we have to add:
- with wvdial, enable a line Auto DNS = yes in /etc/wvdial.conf
if the ISP displays DNS addresses during the initial negotiation.
- with Kppp, accordingly set the DNS option in the Configuration tool to
Dynamic while Static requires that you manually
enter the addresses displayed by your ISP.
- and check twice that you have a consistent setting: either automatic, or manual with the
right DNS addresses at the right place.
- "Mandriva's" contribution to failure to browse while the modem is clearly
working: the default "security" lock which prevents browsing (Control Center,
- Conexant modem saying
after a successfull connection.
- Line hangs up during large file transfers?
- Reduce MTU using /sbin/ifconfig as root (man ifconfig first)
- Occurs during Web downloads? Try
(presentation, author, source code, installation)
also available ready-to-go as an RPM package
for your convenience (I do not commit myself to update the rpm).
Dial-in with 2.6 kernels not working Thanks to Radovan Garabik.
- New drivers from
. Still no support for 2.6.x kernels, except for kernel version 2.6.3-7mdk
Softmodem installation under Ubuntu kernel:
From firstname.lastname@example.org Sat Jul 23 22:48:13 2005
Subject: Re: scanModem, Ubuntu 5.04 "Hoary Hedgehog" kernel 2.6.10-5-386
Regardless of your modem hardware,
you will need to setup for compiling by installing packages for:
1) a a gcc-3.3.n compiler
2) kernel-kbuild-2.6-3 or later version
3) linux-headers-2.6.10-5-386 which will likely require linux-headers-2.6.10-5
Lines starting with # are commands. You do NOT want to type this character.
Unpack the following file in your Linux partition
# tar zvxf slamr_for_Ubuntu_kernel-2.6.10-5-386_ONLY.tar.gz
# cd slamr_for_2.6.10-5-386/
Try inserting the driver
# insmod ./slamr.ko
If insertion is sucessful, you can get a diagmostic readout from
# dmseg | grep slamr
Please report to the List
LTMODEM device, Debian:
From Marv, 27/7/05
Assuming Ubuntu used the same udev file structure as my Debian installation (see below),
create a file /etc/udev/ltmodem.rules with 3 lines
# UDEV rule for ltmodem
# creates symlink /dev/modem to /dev/ttyLTM0, and takes care of permissions
KERNEL="ttyLTM[0-9]", NAME="%k", MODE="0660", GROUP="dialout", SYMLINK="modem"
and set a symbolic link:
# ln -s /etc/udev/ltmodem.rules /etc/udev/rules.d/ltmodem.rules
# modprobe ltserial
/dev/modem --> /dev/ttyLTM0
- TRUE HARDWARE
In view of popular demand, and although "off list", see:
- Partial list and INSTALLATION
- Use Rob Clark's database:
Select one of the mirrors
Select the "Modem Database"
Choose among PCI, ISA, EXT, USB, PCMCIA
Discard any modem which is not
marked in GREEN.
Remember, when we write elsewhere "take this driver", we mean it, because
in the worst case it will just not work.
Not so here, we will never write "purchase this hardware modem".