I have an external usb dial up modem. lsusb shows:
Bus 001 Device 002: ID 2001:f10d D-Link Corp. [hex] Accent Communications Modem
How do I set this up? It probably needs a driver, how do I check it, or better yet, can I get yast to tell me if it recognizes the modem or needs firmware?
I know linux and dial up is like the seventh circle of hell. Just wondering if there was a snowball’s chances of getting this working.
Sorry if this is the wrong section to ask in. Seemed like as good as any when I checked.
Hopefully your device is just recognised (as a serial modem device). With the device just plugged in, type this command
ls -l /dev/ttyUSB*
If /dev/ttyUSB[0,1 or 2] is present, then you may be able to configure with
YaST > Network Devices > Modem
Dialling utilities like kinternet,kppp, or wvdial can be installed via the yast software installer, and used to control the modem.
That returned:
ls: cannot access /dev/ttyUSB*: No such file or directory
From “hardware”, in yast:
usb.2: usb
usb dev: /devices/pci0000:00/0000:00:07.2/usb1
usb dev: /devices/pci0000:00/0000:00:07.2/usb1/1-1
usb device: name = usb1
path = /devices/pci0000:00/0000:00:07.2/usb1
usb device: name = 1-0:1.0
path = /devices/pci0000:00/0000:00:07.2/usb1/1-0:1.0
modalias = "usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00"
bInterfaceNumber = 0
bInterfaceClass = 9
bInterfaceSubClass = 0
bInterfaceProtocol = 0
if: 1-0:1.0 @ /devices/pci0000:00/0000:00:07.2/usb1
bDeviceClass = 9
bDeviceSubClass = 0
bDeviceProtocol = 0
idVendor = 0x1d6b
idProduct = 0x0001
manufacturer = "Linux 2.6.31.12-0.2-default uhci_hcd"
product = "UHCI Host Controller"
serial = "0000:00:07.2"
bcdDevice = 0206
speed = "12"
usb device: name = 1-1
path = /devices/pci0000:00/0000:00:07.2/usb1/1-1
usb device: name = 1-1:1.0
path = /devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0
modalias = "usb:v2001pF10Dd0100dc02dsc00dpFFic0Aisc00ip00"
bInterfaceNumber = 0
bInterfaceClass = 10
bInterfaceSubClass = 0
bInterfaceProtocol = 0
if: 1-1:1.0 @ /devices/pci0000:00/0000:00:07.2/usb1/1-1
bDeviceClass = 2
bDeviceSubClass = 0
bDeviceProtocol = 255
idVendor = 0x2001
idProduct = 0xf10d
manufacturer = "Conexant Systems, Inc."
product = "OD-EMU-100 USB V.92 Modem"
serial = "00000001"
bcdDevice = 0100
speed = "12"
usb device: name = 1-1:1.1
path = /devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.1
modalias = "usb:v2001pF10Dd0100dc02dsc00dpFFic02isc01ipFF"
bInterfaceNumber = 1
bInterfaceClass = 2
bInterfaceSubClass = 1
bInterfaceProtocol = 255
if: 1-1:1.1 @ /devices/pci0000:00/0000:00:07.2/usb1/1-1
bDeviceClass = 2
bDeviceSubClass = 0
bDeviceProtocol = 255
idVendor = 0x2001
idProduct = 0xf10d
manufacturer = "Conexant Systems, Inc."
product = "OD-EMU-100 USB V.92 Modem"
serial = "00000001"
bcdDevice = 0100
speed = "12"
removed: /devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.1
Ok, I haven’t been able to find anything on this modem chipset as far as linux goes, but lets give this a shot. Plug in the device and do
modprobe -r usbserial
modprobe usbserial vendor=0x2001 product=0xf10d
Then note what is reported with
dmesg |tail
51.537329] NET: Registered protocol family 17
61.052101] eth0: no IPv6 routers present
286.705077] usbcore: registered new interface driver usbserial
286.705142] USB Serial support registered for generic
286.705192] usbserial_generic 1-1:1.0: generic converter detected
286.705478] usb 1-1: generic converter now attached to ttyUSB0
286.705518] usbserial_generic 1-1:1.1: Generic device with no bulk out, not allowed.
286.705552] usbserial_generic: probe of 1-1:1.1 failed with error -5
286.705616] usbcore: registered new interface driver usbserial_generic
286.705636] usbserial: USB Serial Driver core
usb 1-1: generic converter now attached to ttyUSB0
This line looks promising. You should be able to find this device now
ls -l /dev/ttyUSB*
Try this
wvdialconf
What is reported?
You could also do
ln -s /dev/ttyUSB0 /dev/modem
then configure with YaST > Network Devices > Modem
You will then need to install kinternet to dial (if you don’t want to use wvdial).
Note: You may have to use the modprobe commands I gave you earlier to re-enable your modem again, but we can automate all that if you can get your modem configured ok.
Bad news:
ls: cannot access /dev/ttyUSB*: No such file or directory
Bad news:
ls: cannot access /dev/ttyUSB*: No such file or directory
Reply With Quote
Ok, just to be sure, did you start with the modprobe commands (immediately after plugging in your device)?
linux-mttm:/home/pottzie # modprobe -r usbserial
linux-mttm:/home/pottzie # modprobe usbserial vendor=0x2001 product=0xf10d
linux-mttm:/home/pottzie # dmesg |tail
49.526528] NET: Registered protocol family 17
59.176074] eth0: no IPv6 routers present
216.214290] usbcore: registered new interface driver usbserial
216.214355] USB Serial support registered for generic
216.214407] usbserial_generic 1-1:1.0: generic converter detected
216.214685] usb 1-1: generic converter now attached to ttyUSB0
216.214727] usbserial_generic 1-1:1.1: Generic device with no bulk out, not allowed.
216.214777] usbserial_generic: probe of 1-1:1.1 failed with error -5
216.214830] usbcore: registered new interface driver usbserial_generic
216.214850] usbserial: USB Serial Driver core
linux-mttm:/home/pottzie # ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 2010-06-16 15:12 /dev/ttyUSB0
linux-mttm:/home/pottzie # wvdialconf
bash: wvdialconf: command not found
linux-mttm:/home/pottzie # ln -s /dev/ttyUSB0 /dev/modem
l
When I ran yast it didn’t show a modem, just a blank page when it finished.
Installed wvdialconfg.
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: Scanning ttyUSB0 first, /dev/modem is a link to it.
WvModem<*1>: Cannot get information for serial port.
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Well, it looks like your modem does not conform to the usual serial modem standards ie the usbserial modem driver is not able to communicate with it properly. (Sometimes, adding the product and vendor codes is enough to create a working device). Searching around the internet (using Accent and the chipset codes etc) has not yielded any success stories either.
I note from your hardware info
idProduct = 0xf10d
manufacturer = “Conexant Systems, Inc.”
product = “OD-EMU-100 USB V.92 Modem”
It might be possible to use a Linuxant driver (given that it uses a Conexant chipset), but the chances are probably remote. Sorry, but I can’t help you any further on this. Given the price of modem hardware, I would purchase another brand - make sure you do your research first though.
Any suggestions as to which brands, or a source to look for linux compatible modems?
They can be tricky to find nowadays, but here’s a couple:
Zoom Telephonics: External 56K USB Modem Products
USRobotics - 56K Internal and External Modems, Gigabit Ethernet Networking
Went to linmodems.org and downloaded scanmodem. It’s a .gz file, and the instructions say to open it by running “gunzip scanModem.gz”
When I do that I get “No such file or directory”. Any idea what I’m doing wrong?
Do you have gunzip installed? Maybe try another utility like tar to do this. Make sure you provide the path to your file, or cd to the directory its been downloaded to. For example
tar -zxvf /path/to/the/nameof.tar.gz
I got it to run.Output (information overload!):
Only plain text email is forwarded by the Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry Welcome to openSUSE 11.2 "Emerald" - Kernel kernel 2.6.31.12-0.2-default
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@Linmodems.org 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, Welcome , ALSA_version=1.0.20
Linux version 2.6.31.12-0.2-default (geeko@buildhost) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 SMP 2010-03-16 21:25:39 +0100
scanModem update of: 2010_05_29
DISTRIB_ID not found
Presently install your Linux Distributions dkms package. It provides for automated driver updates,
following upgrade of your kernel. For details see http://linux.dell.com/projects.shtml#dkms
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
Attached USB devices are:
ID 2001:f10d D-Link Corp. [hex] Accent Communications Modem
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@linmodems.org
Candidate PCI devices with modem chips are:
00:03.1 Serial controller: Xircom Mini-PCI V.90 56k Modem
High Definition Audio cards can host modem chips.
For candidate card in slot 00:03.1, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.1 115d:000c 8086:2408 Serial controller: Xircom Mini-PCI V.90 56k Modem
Modem interrupt assignment and sharing:
9: 13181 XT-PIC-XT acpi, eth0
--- Bootup diagnostics for card in PCI slot 00:03.1 ----
0.727488] pci 0000:00:03.1: reg 10 io port: [0x1840-0x1847]
0.727505] pci 0000:00:03.1: reg 14 32bit mmio: [0xf4121000-0xf4121fff]
0.727564] pci 0000:00:03.1: supports D1 D2
0.727573] pci 0000:00:03.1: PME# supported from D0 D1 D2 D3hot D3cold
0.727584] pci 0000:00:03.1: PME# disabled
1.954925] serial 0000:00:03.1: PCI INT A -> Link[LNKC] -> GSI 9 (level, low) -> IRQ 9
The PCI slot 00:03.1 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 00:03.1:
Modem chipset detected on
NAME="Serial controller: Xircom Mini-PCI V.90 56k Modem"
CLASS=0700
PCIDEV=115d:000c
SUBSYS=8086:2408
IRQ=9
IDENT=Agere.DSP
For candidate modem in: 00:03.1
0700 Serial controller: Xircom Mini-PCI V.90 56k Modem
Primary device ID: 115d:000c
Support type needed or chipset: Agere.DSP
Vendor 115d is XIRCOM, which was purchased by Intel
The following devices have Lucent/AgereSystems DSP chipsets supported by the
Martian variant of the AgereSystems ltmodem software.
XIRCOM 0x115d 0x0000-0x000F
XIRCOM 0x115d 0x0440-0x045c
XIRCOM 0x115d 0x0010-0x03ff
At http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
get the martian-full-20080625.tar.gz and follow Readme-NOW.html
For kernels 2.6.20 and less, usr martian-full-20080407.tar.gz.
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.4.1
and the compiler used in kernel assembly: 4.4
linux-headers-2.6.31.12-0.2-default resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
kernel-source-2.6.31.12-0.2-default
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:
-rwxr-xr-x 1 root dialout 330764 2009-10-19 11:45 /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)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
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
For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
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:
/etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", ENV{INTERFACE}=="lo*|dummy*|vif*.*|br*|bond*|vlan*|gre*|sit*|tap*|tun*|ipip*|ip6tnl*|ipsec*|ppp*|ippp*|isdn*|modem*|dsl*|plip*|irda*", GOTO="skip_ifup"
Within /etc/modprobe.conf files:
/etc/modprobe.d/00-system.conf:# Linux ACP modem (Mwave)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
Attached USB devices are:
ID 2001:f10d D-Link Corp. [hex] Accent Communications Modem
I can see it has picked up your usb device, but no advice given as to what support might exsist.
In addition, I note you have an internal PCI modem device reported:
Modem chipset detected on
NAME=“Serial controller: Xircom Mini-PCI V.90 56k Modem”
CLASS=0700
PCIDEV=115d:000c
SUBSYS=8086:2408
IRQ=9
IDENT=Agere.DSP
Vendor 115d is XIRCOM, which was purchased by Intel
The following devices have Lucent/AgereSystems DSP chipsets supported by the
Martian variant of the AgereSystems ltmodem software.
XIRCOM 0x115d 0x0000-0x000F
XIRCOM 0x115d 0x0440-0x045c
XIRCOM 0x115d 0x0010-0x03ff
Some info on this driver here:
Martian - Agere Systems WinModem driver for Linux
An openSUSE thread on this topic:
I can’t offer any further help here though. You might need to research further with google etc.
hi friend i have same problem but i connect my modem first you restart your pc then run all command step by step when you see your modem is connected on /dev/ttyUSB0 then you can run wvdial then you can connect net
i send you some command u can edit for your device
example
wvdial.conf
[Dialer 3g]
Auto DNS = 1
Init1 = ATZ
Init2 = at+cgdcont=1,“ip”,“bsnlnet”
Stupid Mode = 1
Modem Type = USB Modem
ISDN = 0
Idle Seconds = 300
Ask Password = 0
Compuserve = 0
Phone = 99**1#
Modem = /dev/ttyUSB0
Dial Command = ATDT
Baud = 460800
use this command in su mode
rose:/home/king #lsusb
rose:/home/king # modprobe -v option
rose:/home/king # sudo /sbin/modprobe usbserial vendor=0x0421 product=0x0491
rose:/home/king # dmesg | tail -n10
rose:/home/king # wvdial
i hope this is usful for you if usful rply me friend…best of luck…
On 2010-06-16 06:46, deano ferrari wrote:
>
>> usb 1-1: generic converter now attached to ttyUSB0
>>
>
> This line looks promising. You should be able to find this device now
No, because it fails a few lines ahead.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)