wvdial.conf when accessing "modem= /dev/usb/ttyUSB0 will not read more than /dev/usb deep into the directory. The error message gives cannot access /dev/usb: this is a directory. To get the usb modem to work you have to delete /dev/modem (rm /dev/modem) and symlink /dev/usb/ttyUSB0 to /dev/modem (ln -s /dev/usb/ttyUSB0 /dev/modem)
Then open up /etc/wvdial.conf and change the modem line to read "Modem= /dev/modem". (instead of "Modem=/dev/usb/ttyUSB0") Then start Pupdial and it should connect if your usb is a ttyUSB0 modem. I have this setup in /etc/rc.d/rc.local
----------------
rm /dev/modem
ln -s /dev/usb/ttyUSB0 /dev/modem
---------------
When booting it works now
I have also found in both puppy 4.00's (2.6.21 kernel and .25 kernels) that the modem doesn't stay online it dials in but I cannot get a connection. On further experimenting the modem stays online by changing the connection speed from 57600 (default) to 115200.
How to use USB dialup modem with wvdial.conf
How to use USB dialup modem with wvdial.conf
Last edited by russ on Wed 21 May 2008, 01:45, edited 1 time in total.
Setting /dev/modem
russ,
Thanks for posting this info. However, the modem-initialization scripts should do that for you, if the USB modem is plugged in before booting. Hotplugging has not yet been fully addressed.
If you did have the modem plugged in at boot-up, then the failure of the script to set /dev/modem appropriately could be considered a bug. Otherwise, please try that and report any failure in the Bugs forum, Puppy4 DINGO. I have focussed on getting modems to be detected correctly, so you could help me straighten this out. In your posting, please include details of your modem and computer setup.
Thanks.
Richard
Thanks for posting this info. However, the modem-initialization scripts should do that for you, if the USB modem is plugged in before booting. Hotplugging has not yet been fully addressed.
If you did have the modem plugged in at boot-up, then the failure of the script to set /dev/modem appropriately could be considered a bug. Otherwise, please try that and report any failure in the Bugs forum, Puppy4 DINGO. I have focussed on getting modems to be detected correctly, so you could help me straighten this out. In your posting, please include details of your modem and computer setup.
Thanks.
Richard
I have the usb modem plugged in at bootup and it properly links the modem to /dev/usb/ttyUSB0 in the wvdial.conf setup but the Pupdial does not read to the /dev/usb/ttyUSB0 file...it will only get to /dev/usb and gives the above error message "/dev/usb is a directory". It will however read to the "2 directory deep" file /dev/modem. I am guessing that this is correct because everything works fine when accessed to this 2 deep directory.
I have a Toshiba M35x-s311 laptop (pentium-m centrino, 768mb memory using puppy 3.01 liveCD with setting on a usb thumb drive. My modem is a Actiontec EX560LKU external USB/Serial 56k hardware setup.
I have tried it also on the new Puppy 4.0 using both kernels (2.6..21 and .25)and it tries to access the modem the same way on all three setups (which includes this 3.01 setup). However I can dial out (after making the first post adjustments) using both 4.0's but cannot establish a connection like I can in 3.01 which maybe another bug. I posted most of the above in the "Dingo 4.0 bugs" site.
I have a Toshiba M35x-s311 laptop (pentium-m centrino, 768mb memory using puppy 3.01 liveCD with setting on a usb thumb drive. My modem is a Actiontec EX560LKU external USB/Serial 56k hardware setup.
I have tried it also on the new Puppy 4.0 using both kernels (2.6..21 and .25)and it tries to access the modem the same way on all three setups (which includes this 3.01 setup). However I can dial out (after making the first post adjustments) using both 4.0's but cannot establish a connection like I can in 3.01 which maybe another bug. I posted most of the above in the "Dingo 4.0 bugs" site.
Thanks for the details. What does the "USB Interfaces" display in PupScan show? Does it list the modem but with module "unknown"? Please post the USB-Interfaces info. Also post the content of /tmp/bootsysinit.log, which could hold a clue.
I expect the driver/module name is pl2303; the script for it sets up /dev/modem as /dev/usb/ttyUSB0. My guess is that Puppy doesn't detect the modem and associate it with the driver. The script would be /etc/init.d/Pl2303, but it probably will not be there.
I understand that you:
1. boot up with it plugged in
2. run the two commands you mentioned
3. edit wvdial.conf to set "modem=/dev/modem"
4. run pupdial, etc.
Anything else?
Does pupdial show anything other than "ATZ" in the initialization-string fields?
I see with google that people have had trouble with this modem. They seem to need to "reset" it for each boot-up, whatever that means.
Please confirm or counter my assumptions above, to get a "handle" on this. Please run without your commands in rc.local, to avoid confounding things, possibly with pfix=ram and a new pupsave. Thanks.
Richard
I expect the driver/module name is pl2303; the script for it sets up /dev/modem as /dev/usb/ttyUSB0. My guess is that Puppy doesn't detect the modem and associate it with the driver. The script would be /etc/init.d/Pl2303, but it probably will not be there.
I understand that you:
1. boot up with it plugged in
2. run the two commands you mentioned
3. edit wvdial.conf to set "modem=/dev/modem"
4. run pupdial, etc.
Anything else?
Does pupdial show anything other than "ATZ" in the initialization-string fields?
I see with google that people have had trouble with this modem. They seem to need to "reset" it for each boot-up, whatever that means.
Please confirm or counter my assumptions above, to get a "handle" on this. Please run without your commands in rc.local, to avoid confounding things, possibly with pfix=ram and a new pupsave. Thanks.
Richard
( I do have a built-in software modem that is not working that the kernel still sees)
Running computer in ram only off of live-cd:
1.On bootup can hear modem responding after "Detecting analog modem"
2 Pupscan USB devices:
Manufacturer=SanDisk
Product=U3 Cruzer Micro
SerialNumber=0000187B8573B52A
VendorID=0781 ProductID=5406 KERNEL-MODULE=usb-storage
Manufacturer=Prolific Technology Inc.
Product=USB-Serial Controller
VendorID=067b ProductID=2303 KERNEL-MODULE=pl2303
3. /etc/init.d/Pl2303 is there.
4 /tmp/bootsysinit.log:
-----------------------------------------------
cat /tmp/bootsysinit.log
Mounting devpts: Mounting /sys: Starting /etc/rc.d/rc.modules...
loading modules for core usb...
loading modules for pci interfaces...
loading module intel-agp
loading module i2c-i801
loading module snd-intel8x0
loading module slamr
loading module 8139too
loading module ipw2200
loading module yenta_socket
loading module sdhci
loading modules for pcmcia...
yenta_socket 26892 1
rsrc_nonstatic 13312 1 yenta_socket
Running PCMCIA cardmgr program...
cardmgr[4700]: watching 1 socket
Fetching x dri modules (but not loading)...
Setting hostname: puppypc
loading extra usb modules...
Loading pl2303
You have chosen "us.map" keyboard map.
Note, this information is saved in file /etc/keymap
Loading /usr/share/kbd/keymaps/i386/qwerty/us.map
The following interfaces have been found: eth0 eth1
Trying to connect
WARNING: Interface eth0 has not been configured. Use the network wizard.
WARNING: Interface eth1 has not been configured. Use the network wizard.
Starting sound driver: snd-intel8x0
done
No state is present for card I82801DBICH4
cups: started scheduler.
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
Starting PCMCIA services:
<PCIC already loaded>
skip running setserial
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
------------------------------
5. Pupdial error:
--> WvDial: Internet dialer version 1.41
--> Cannot open /dev/usb: Is a directory.
6. Contents of wvdial.conf:
A-)Before Pupdial is run:
[Dialer Defaults]
Modem = /dev/usb/ttyUSB0
Baud = 57600
Init1 = ATZ
Init2 = ATQ0V1E1S0=0&C1&D2S11=55+FCLASS=0
Carrier Check = no
Dial Command = ATDT
Phone = MYISPPHONENUM
Username = MYUSERNAME
Password = MYPASSWORD
[Dialer isp2]
Phone = MY2ISPPHONENUM
Username = MY2USERNAME
Password = MY2PASSWORD
B-)after Pupdial is run:
[Dialer Defaults]
Modem = /dev/usb
Baud = 57600
Init1 = ATZ
Init2 = ATQ0V1E1S0=0&C1&D2S11=55+FCLASS=0
Carrier Check = no
Dial Command = ATDT
Phone = MYISPPHONENUM
Username = MYUSERNAME
Password = MYPASSWORD
[Dialer isp2]
Phone = MY2ISPPHONENUM
Username = MY2USERNAME
Password = MY2PASSWORD
7. there is a symlink in /dev/modem to /usb/ttyUSB0
If you change wvdial.conf to read:
Modem=/dev/modem (instead of Modem=/dev/usb/ttyUSB0) the modem works. It doesn't stay online but it does dials out.
Running computer in ram only off of live-cd:
1.On bootup can hear modem responding after "Detecting analog modem"
2 Pupscan USB devices:
Manufacturer=SanDisk
Product=U3 Cruzer Micro
SerialNumber=0000187B8573B52A
VendorID=0781 ProductID=5406 KERNEL-MODULE=usb-storage
Manufacturer=Prolific Technology Inc.
Product=USB-Serial Controller
VendorID=067b ProductID=2303 KERNEL-MODULE=pl2303
3. /etc/init.d/Pl2303 is there.
4 /tmp/bootsysinit.log:
-----------------------------------------------
cat /tmp/bootsysinit.log
Mounting devpts: Mounting /sys: Starting /etc/rc.d/rc.modules...
loading modules for core usb...
loading modules for pci interfaces...
loading module intel-agp
loading module i2c-i801
loading module snd-intel8x0
loading module slamr
loading module 8139too
loading module ipw2200
loading module yenta_socket
loading module sdhci
loading modules for pcmcia...
yenta_socket 26892 1
rsrc_nonstatic 13312 1 yenta_socket
Running PCMCIA cardmgr program...
cardmgr[4700]: watching 1 socket
Fetching x dri modules (but not loading)...
Setting hostname: puppypc
loading extra usb modules...
Loading pl2303
You have chosen "us.map" keyboard map.
Note, this information is saved in file /etc/keymap
Loading /usr/share/kbd/keymaps/i386/qwerty/us.map
The following interfaces have been found: eth0 eth1
Trying to connect
WARNING: Interface eth0 has not been configured. Use the network wizard.
WARNING: Interface eth1 has not been configured. Use the network wizard.
Starting sound driver: snd-intel8x0
done
No state is present for card I82801DBICH4
cups: started scheduler.
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
Starting PCMCIA services:
<PCIC already loaded>
skip running setserial
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
------------------------------
5. Pupdial error:
--> WvDial: Internet dialer version 1.41
--> Cannot open /dev/usb: Is a directory.
6. Contents of wvdial.conf:
A-)Before Pupdial is run:
[Dialer Defaults]
Modem = /dev/usb/ttyUSB0
Baud = 57600
Init1 = ATZ
Init2 = ATQ0V1E1S0=0&C1&D2S11=55+FCLASS=0
Carrier Check = no
Dial Command = ATDT
Phone = MYISPPHONENUM
Username = MYUSERNAME
Password = MYPASSWORD
[Dialer isp2]
Phone = MY2ISPPHONENUM
Username = MY2USERNAME
Password = MY2PASSWORD
B-)after Pupdial is run:
[Dialer Defaults]
Modem = /dev/usb
Baud = 57600
Init1 = ATZ
Init2 = ATQ0V1E1S0=0&C1&D2S11=55+FCLASS=0
Carrier Check = no
Dial Command = ATDT
Phone = MYISPPHONENUM
Username = MYUSERNAME
Password = MYPASSWORD
[Dialer isp2]
Phone = MY2ISPPHONENUM
Username = MY2USERNAME
Password = MY2PASSWORD
7. there is a symlink in /dev/modem to /usb/ttyUSB0
If you change wvdial.conf to read:
Modem=/dev/modem (instead of Modem=/dev/usb/ttyUSB0) the modem works. It doesn't stay online but it does dials out.
Thanks, russ, for the listings.
Is the /tmp/bootsysinit.log listing from puppy 4.00? I ask that because I expect to see "loading modules for pci interfaces" followed by "loading yenta-socket". Do you have anything in the PCcard slot?
The loading of "slamr" indicates your built-in modem is a SmartLink, which I would expect to work. On the chance that pupdial could be confused by the presence of two modem drivers, please blacklist slamr, using the system>bootmanager.
For the USB modem, it appears that it is detected and set into /dev/modem OK. But wvdial itself, within pupdial, does not seem to like more than two levels in "modem =", as you have already concluded. Let's try an easy fix, to see if it is sufficient. Please edit a script then reboot (saving to a pupsave).
Edit file /etc/init.d/Pl2303, to change line 14 into two lines:
That should satisfy wvdial; maybe blacklisting slamr might help in connecting (fingers crossed).
Could you also post the "PCI Interfaces" list from PupScan (before you blacklist slamr), so I can check on the Smartlink modem. In what way does it not work, if you leave the USB modem unplugged at bootup? (USB takes precedence.)
I may be delayed in responding, due to a busy day tomorrow.
Richard
Is the /tmp/bootsysinit.log listing from puppy 4.00? I ask that because I expect to see "loading modules for pci interfaces" followed by "loading yenta-socket". Do you have anything in the PCcard slot?
The loading of "slamr" indicates your built-in modem is a SmartLink, which I would expect to work. On the chance that pupdial could be confused by the presence of two modem drivers, please blacklist slamr, using the system>bootmanager.
For the USB modem, it appears that it is detected and set into /dev/modem OK. But wvdial itself, within pupdial, does not seem to like more than two levels in "modem =", as you have already concluded. Let's try an easy fix, to see if it is sufficient. Please edit a script then reboot (saving to a pupsave).
Edit file /etc/init.d/Pl2303, to change line 14 into two lines:
Code: Select all
Old line 14: ln -snf usb/ttyUSB0 /dev/modem
New lines 14 &15:
ln -snf usb/ttyUSB0 /dev/ttyUSB0
ln -snf ttyUSB0 /dev/modemCould you also post the "PCI Interfaces" list from PupScan (before you blacklist slamr), so I can check on the Smartlink modem. In what way does it not work, if you leave the USB modem unplugged at bootup? (USB takes precedence.)
I may be delayed in responding, due to a busy day tomorrow.
Richard
Congratulations! Your solution worked! The following are the stats you asked for.
/tmp/bootsysinit.log from Dingo 4.0 (kernel 2.6.25)
# cat /tmp/bootsysinit.log
Mounting devpts: Mounting /sys: Starting /etc/rc.d/rc.modules...
loading modules for core usb...
loading modules for pci interfaces...
loading module yenta_socket
loading module intel-agp
loading module i2c-i801
loading module snd-intel8x0
loading module slamr
loading module 8139too
loading module ipw2200
loading module sdhci
Running PCMCIA cardmgr program...
cardmgr[5000]: watching 1 socket
Fetching x dri modules (but not loading)...
Setting hostname: puppypc
loading extra usb modules...
Loading pl2303
You have chosen "us.map" keyboard map.
Note, this information is saved in file /etc/keymap
Loading /usr/share/kbd/keymaps/i386/qwerty/us.map
The following interfaces have been found: eth0 eth1
Trying to connect
WARNING: Interface eth0 has not been configured. Use the network wizard.
WARNING: Interface eth1 has not been configured. Use the network wizard.
Starting sound driver: snd-intel8x0 done
cups: started scheduler.
skip running setserial
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
Remark: the original /tmp/bootsysinit.log was from puppy 3.01, the immediate above is Dingo 4.0
------------------------------------------------------
PCI interfaces before blacklisting slamr:
DESCRIPTION: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller
VENDOR: 8086 DEVICE: 3580 KERNEL MODULE: intel-agp
DESCRIPTION: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller
VENDOR: 8086 DEVICE: 3584 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller
VENDOR: 8086 DEVICE: 3585 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82852/855GM Integrated Graphics Device
VENDOR: 8086 DEVICE: 3582 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82852/855GM Integrated Graphics Device
VENDOR: 8086 DEVICE: 3582 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1
VENDOR: 8086 DEVICE: 24c2 KERNEL MODULE: uhci-hcd
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2
VENDOR: 8086 DEVICE: 24c4 KERNEL MODULE: uhci-hcd
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3
VENDOR: 8086 DEVICE: 24c7 KERNEL MODULE: uhci-hcd
DESCRIPTION: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller
VENDOR: 8086 DEVICE: 24cd KERNEL MODULE: ehci-hcd
DESCRIPTION: Intel Corporation 82801 Mobile PCI Bridge
VENDOR: 8086 DEVICE: 2448 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge
VENDOR: 8086 DEVICE: 24cc KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DBM (ICH4-M) IDE Controller
VENDOR: 8086 DEVICE: 24ca KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller
VENDOR: 8086 DEVICE: 24c3 KERNEL MODULE: i2c-i801
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
VENDOR: 8086 DEVICE: 24c5 KERNEL MODULE: snd-intel8x0
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller
VENDOR: 8086 DEVICE: 24c6 KERNEL MODULE: slamr
DESCRIPTION: VIA Technologies, Inc. IEEE 1394 Host Controller
VENDOR: 1106 DEVICE: 3044 KERNEL MODULE: unknown
DESCRIPTION: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
VENDOR: 10ec DEVICE: 8139 KERNEL MODULE: 8139too
DESCRIPTION: Intel Corporation PRO/Wireless 2200BG Network Connection
VENDOR: 8086 DEVICE: 4220 KERNEL MODULE: ipw2200
DESCRIPTION: ENE Technology Inc CB-710/2/4 Cardbus Controller
VENDOR: 1524 DEVICE: 1411 KERNEL MODULE: yenta_socket
DESCRIPTION: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
VENDOR: 1524 DEVICE: 0530 KERNEL MODULE: unknown
DESCRIPTION: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller
VENDOR: 1524 DEVICE: 0550 KERNEL MODULE: sdhci
DESCRIPTION: ENE Technology Inc FLASH memory: ENE Technology Inc:
VENDOR: 1524 DEVICE: 0520 KERNEL MODULE: unknown
---------------------------------------------------------------------
edited pl2303 to look like:
#!/bin/sh
#usb/serial modem
#Barry Kauler, LGPL 2007
#called from rc.local0. note, rc.local0 calls rc.modem beforehand which
#sets /dev/modem if a serial modem found (otherwise /dev/modem deleted).
#if a modem found, quit...
[ -h /dev/modem ] && exit #v3.98
[ ! $1 ] && exit
[ "$1" != "start" ] && exit
if [ "`lsmod | grep '^pl2303'`" != "" ];then
ln -snf usb/ttyUSB0 /dev/ttyUSB0 < --changed this line and next
ln -snf ttyUSB0 /dev/modem <--
fi
-----------------------------------
black listed slamr in bootup
By the way, I have been able to make the modem stay online by changing the login speed from 57600 (default) to 115200
Using Dingo 4.0 (with usb modem) now to send this message
/tmp/bootsysinit.log from Dingo 4.0 (kernel 2.6.25)
# cat /tmp/bootsysinit.log
Mounting devpts: Mounting /sys: Starting /etc/rc.d/rc.modules...
loading modules for core usb...
loading modules for pci interfaces...
loading module yenta_socket
loading module intel-agp
loading module i2c-i801
loading module snd-intel8x0
loading module slamr
loading module 8139too
loading module ipw2200
loading module sdhci
Running PCMCIA cardmgr program...
cardmgr[5000]: watching 1 socket
Fetching x dri modules (but not loading)...
Setting hostname: puppypc
loading extra usb modules...
Loading pl2303
You have chosen "us.map" keyboard map.
Note, this information is saved in file /etc/keymap
Loading /usr/share/kbd/keymaps/i386/qwerty/us.map
The following interfaces have been found: eth0 eth1
Trying to connect
WARNING: Interface eth0 has not been configured. Use the network wizard.
WARNING: Interface eth1 has not been configured. Use the network wizard.
Starting sound driver: snd-intel8x0 done
cups: started scheduler.
skip running setserial
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
[1]+ Done modem-stats $@ >/tmp/modemstatsret
Remark: the original /tmp/bootsysinit.log was from puppy 3.01, the immediate above is Dingo 4.0
------------------------------------------------------
PCI interfaces before blacklisting slamr:
DESCRIPTION: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller
VENDOR: 8086 DEVICE: 3580 KERNEL MODULE: intel-agp
DESCRIPTION: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller
VENDOR: 8086 DEVICE: 3584 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller
VENDOR: 8086 DEVICE: 3585 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82852/855GM Integrated Graphics Device
VENDOR: 8086 DEVICE: 3582 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82852/855GM Integrated Graphics Device
VENDOR: 8086 DEVICE: 3582 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1
VENDOR: 8086 DEVICE: 24c2 KERNEL MODULE: uhci-hcd
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2
VENDOR: 8086 DEVICE: 24c4 KERNEL MODULE: uhci-hcd
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3
VENDOR: 8086 DEVICE: 24c7 KERNEL MODULE: uhci-hcd
DESCRIPTION: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller
VENDOR: 8086 DEVICE: 24cd KERNEL MODULE: ehci-hcd
DESCRIPTION: Intel Corporation 82801 Mobile PCI Bridge
VENDOR: 8086 DEVICE: 2448 KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge
VENDOR: 8086 DEVICE: 24cc KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DBM (ICH4-M) IDE Controller
VENDOR: 8086 DEVICE: 24ca KERNEL MODULE: unknown
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller
VENDOR: 8086 DEVICE: 24c3 KERNEL MODULE: i2c-i801
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
VENDOR: 8086 DEVICE: 24c5 KERNEL MODULE: snd-intel8x0
DESCRIPTION: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller
VENDOR: 8086 DEVICE: 24c6 KERNEL MODULE: slamr
DESCRIPTION: VIA Technologies, Inc. IEEE 1394 Host Controller
VENDOR: 1106 DEVICE: 3044 KERNEL MODULE: unknown
DESCRIPTION: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
VENDOR: 10ec DEVICE: 8139 KERNEL MODULE: 8139too
DESCRIPTION: Intel Corporation PRO/Wireless 2200BG Network Connection
VENDOR: 8086 DEVICE: 4220 KERNEL MODULE: ipw2200
DESCRIPTION: ENE Technology Inc CB-710/2/4 Cardbus Controller
VENDOR: 1524 DEVICE: 1411 KERNEL MODULE: yenta_socket
DESCRIPTION: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
VENDOR: 1524 DEVICE: 0530 KERNEL MODULE: unknown
DESCRIPTION: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller
VENDOR: 1524 DEVICE: 0550 KERNEL MODULE: sdhci
DESCRIPTION: ENE Technology Inc FLASH memory: ENE Technology Inc:
VENDOR: 1524 DEVICE: 0520 KERNEL MODULE: unknown
---------------------------------------------------------------------
edited pl2303 to look like:
#!/bin/sh
#usb/serial modem
#Barry Kauler, LGPL 2007
#called from rc.local0. note, rc.local0 calls rc.modem beforehand which
#sets /dev/modem if a serial modem found (otherwise /dev/modem deleted).
#if a modem found, quit...
[ -h /dev/modem ] && exit #v3.98
[ ! $1 ] && exit
[ "$1" != "start" ] && exit
if [ "`lsmod | grep '^pl2303'`" != "" ];then
ln -snf usb/ttyUSB0 /dev/ttyUSB0 < --changed this line and next
ln -snf ttyUSB0 /dev/modem <--
fi
-----------------------------------
black listed slamr in bootup
By the way, I have been able to make the modem stay online by changing the login speed from 57600 (default) to 115200
Using Dingo 4.0 (with usb modem) now to send this message
russ,
Good job! Thanks for trying it. The login speed might be something to fix. I will have to defer that until the end of the month, as I will be away.
Another bug to report! Thanks to your help. Could you re-title your initial post to report a bug? Specifically that PupDial cannot connect to device /dev/usb/ttyUSB0.
Richard
Moderator: Please move this thread to the Bugs forum, since it includes a fix for puppy 4. Thanks.
Barry: Please consider this a fix for script Pl2303. The same type of correction should be made to other scripts that set /dev/modem to a three-level-down device. Thanks.
Good job! Thanks for trying it. The login speed might be something to fix. I will have to defer that until the end of the month, as I will be away.
Another bug to report! Thanks to your help. Could you re-title your initial post to report a bug? Specifically that PupDial cannot connect to device /dev/usb/ttyUSB0.
Richard
Moderator: Please move this thread to the Bugs forum, since it includes a fix for puppy 4. Thanks.
Barry: Please consider this a fix for script Pl2303. The same type of correction should be made to other scripts that set /dev/modem to a three-level-down device. Thanks.
I have a problem with a usb modem.Pupscan sees the modemManufacturer=Sirius Technologies
Product=Roadster II 56 USB
VendorID=06ea ProductID=0002 KERNEL-MODULE=(none)
Bootsysinit log with the modem connected shows
Mounting devpts: Mounting /sys: Loading swap partition /dev/hda2...
Starting /etc/rc.d/rc.modules...
loading modules for core usb...
loading modules for pci interfaces...
loading module via-agp
loading module via-agp
loading module i2c-viapro
loading module snd-via82xx
loading module via-rhine
Fetching x dri modules (but not loading)...
Setting hostname: puppypc
loading extra usb modules...
Loading /usr/share/kbd/keymaps/i386/dvorak/dvorak.map
Starting sound driver: snd-via82xx done
The following interfaces have been found: eth0
Trying to connect
Log message on pupdial when probed for modem shows
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
Port Scan<*1>: S1 S2 S3
ttyS4<Info>: No such device or address
Port Scan<*1>: S4
ttyS_ESS0<Info>: No such device or address
Port Scan<*1>: S_ESS0
ttyS_PCTEL0<Info>: No such device or address
Port Scan<*1>: S_PCTEL0
I cannot find any trace of Pl2303 which I assume is a driver.
The OS was obtained from Barry Kauler on CD and is labelled bootable cd version 4.00 and is installed on the hard disc Is this enough info
The computer is a desktop of some years of age with amd 2200 CPU I have been using Puppy since version and never had success with usb modem . All is well with serial modem.
Any help would be appreciated. Regards Dennis
Product=Roadster II 56 USB
VendorID=06ea ProductID=0002 KERNEL-MODULE=(none)
Bootsysinit log with the modem connected shows
Mounting devpts: Mounting /sys: Loading swap partition /dev/hda2...
Starting /etc/rc.d/rc.modules...
loading modules for core usb...
loading modules for pci interfaces...
loading module via-agp
loading module via-agp
loading module i2c-viapro
loading module snd-via82xx
loading module via-rhine
Fetching x dri modules (but not loading)...
Setting hostname: puppypc
loading extra usb modules...
Loading /usr/share/kbd/keymaps/i386/dvorak/dvorak.map
Starting sound driver: snd-via82xx done
The following interfaces have been found: eth0
Trying to connect
Log message on pupdial when probed for modem shows
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
Port Scan<*1>: S1 S2 S3
ttyS4<Info>: No such device or address
Port Scan<*1>: S4
ttyS_ESS0<Info>: No such device or address
Port Scan<*1>: S_ESS0
ttyS_PCTEL0<Info>: No such device or address
Port Scan<*1>: S_PCTEL0
I cannot find any trace of Pl2303 which I assume is a driver.
The OS was obtained from Barry Kauler on CD and is labelled bootable cd version 4.00 and is installed on the hard disc Is this enough info
The computer is a desktop of some years of age with amd 2200 CPU I have been using Puppy since version and never had success with usb modem . All is well with serial modem.
Any help would be appreciated. Regards Dennis
Dalderton,
I am not an expert on modems but I do know that some USB modems are "software" modems in that very little hardware (no processor) is used and more software is used to run modem. These are usually called winmodems. Linux has a hard time using these types of software modems. I tried to google your modem and I found this page on a Roadster II 56 USB modem (about 20 lines down from beginning comments)
http://www.qbik.ch/usb/devices/showdev.php?id=52
edit:
You might try the "modem-wizard" located in /usr/sbin/modem-wizard. Just click on the file and it should start the program. From the lineup of the setups to use try the "ttySL0" selection then "USA" for "Choose country" (if from USA) then "USB" under "Choose type of smart-link modem". If success then "save"
I am not an expert on modems but I do know that some USB modems are "software" modems in that very little hardware (no processor) is used and more software is used to run modem. These are usually called winmodems. Linux has a hard time using these types of software modems. I tried to google your modem and I found this page on a Roadster II 56 USB modem (about 20 lines down from beginning comments)
http://www.qbik.ch/usb/devices/showdev.php?id=52
edit:
You might try the "modem-wizard" located in /usr/sbin/modem-wizard. Just click on the file and it should start the program. From the lineup of the setups to use try the "ttySL0" selection then "USA" for "Choose country" (if from USA) then "USB" under "Choose type of smart-link modem". If success then "save"
Hi Dennis!
Welcome to the "usb-modem workshop."
If you suspect your modem uses driver pl2303 (Pl2303 is the name of its modem-initialization script.), then you need to make the same change that russ made, described in my post of May 19, above. That allows PupDial to work with it. With that fix in place, we can work from there. First, please post the content /tmp/bootsysinit.log and the listing provided by PupScan for USB Interfaces. That may tell us what driver is used.
russ,
[Reply moved to another thread, in response to kapper, not russ.]
Richard
Welcome to the "usb-modem workshop."
If you suspect your modem uses driver pl2303 (Pl2303 is the name of its modem-initialization script.), then you need to make the same change that russ made, described in my post of May 19, above. That allows PupDial to work with it. With that fix in place, we can work from there. First, please post the content /tmp/bootsysinit.log and the listing provided by PupScan for USB Interfaces. That may tell us what driver is used.
russ,
[Reply moved to another thread, in response to kapper, not russ.]
Richard
Last edited by rerwin on Wed 28 May 2008, 16:39, edited 1 time in total.
Russ Thanks for the reply.I tried the Modem Wizard with no success and I think my problem is a little earlier in the sequence.It seems strange that Puppyscan sees the Modem but nothing else does. In the boot sequence the Serial modem is recognised and spoken to at some length but if I erase the wvdial.conf file and boot up with the usb modem plugged in the bootup sequence only remarks that there is no modem present.This seems to me to indicate that this is the area that needs modification.I must say here that I only know enough about this stuff to know how much I dont know.
Richard The info from Pupscan on the modem is included in my original post as is the /tmp/bootsysinit.log with the wvdial.conf file blank and the Roadster 11 56 USB modem plugged in at startup.
I tried the mods that you suggested to Russ along with his original mods with no success. My reference to the Pl2303 was because of the reference to it by Russ in his original post.I created the file shown I.e /etc/init.d/Pl2303 without really knowing why and it made no difference either.
Where now??? Regards Dennis
Richard The info from Pupscan on the modem is included in my original post as is the /tmp/bootsysinit.log with the wvdial.conf file blank and the Roadster 11 56 USB modem plugged in at startup.
I tried the mods that you suggested to Russ along with his original mods with no success. My reference to the Pl2303 was because of the reference to it by Russ in his original post.I created the file shown I.e /etc/init.d/Pl2303 without really knowing why and it made no difference either.
Where now??? Regards Dennis
Dennis,
Sorry to be so dense, in requesting info you already provided. My excuse is that I have been away from the subject awhile, 3,000 miles from home and preoccupied.
I have searhed on the modem name and found old info here:http://www.qbik.ch/usb/devices/showdev.php?id=52
that indicates that the driver is "acm". Our version of that is cdcacm; at least that driver supports /dev/input/ttyACM0. However, only Rev. 3 of that modem works with linux; earlier ones are non-standard. Since your product ID is 1 higher than the one discussed, I would expect it to be at least Rev. 3.
Even if Puppy detected your modem as an "ACM" type, it would have a problem and fix similar to that russ tried with his modem. But the script Cdcacm is the one to fix. Where the "ln -snf input/ttyACM0 /dev/modem" instruction appears, it should be changed toThat will allow PupDial to handle it. (Don't bother with the modem probe; it only looks for ttyS-something.)
It appears that Puppy doesn't know about that hardware. As an experiment, try using the BootManager to load cdcacm as an additional module, to see if it detects the modem.
Currently, there is no simple way to add a USB module to the list Puppy recognizes. If Barry hasn't already done it for 4.01, I expect to implement an override scheme similar to that used for PCI hardware. But to test your modem before that, I would modify the file /lib/modules/...usb-map (something like that -- I have no access to Puppy this week, so cannot try it until the weekend) The trick would be to copy one of the statements beginning with "cdcacm" and substitute your vendor and product IDs in the second and third fields -- but first verify that it is not already there. I can set it up after I return home, if you don't want to.
I have written the above with no reference to Puppy code, so hope I got it right. I hope your modem is Rev. 3 and that we can get it to work, although the link above suggests people had trouble with it faster than 28.8k.
Richard
PS: I also found this at another site, referencing the same hardware ID as yours:First verify that "/dev/usb/acm/0" exists.
Sorry to be so dense, in requesting info you already provided. My excuse is that I have been away from the subject awhile, 3,000 miles from home and preoccupied.
I have searhed on the modem name and found old info here:http://www.qbik.ch/usb/devices/showdev.php?id=52
that indicates that the driver is "acm". Our version of that is cdcacm; at least that driver supports /dev/input/ttyACM0. However, only Rev. 3 of that modem works with linux; earlier ones are non-standard. Since your product ID is 1 higher than the one discussed, I would expect it to be at least Rev. 3.
Even if Puppy detected your modem as an "ACM" type, it would have a problem and fix similar to that russ tried with his modem. But the script Cdcacm is the one to fix. Where the "ln -snf input/ttyACM0 /dev/modem" instruction appears, it should be changed to
Code: Select all
ln -snf input/ttyACM0 /dev/ttyACM0
ln -snf ttyACM0 /dev/modemIt appears that Puppy doesn't know about that hardware. As an experiment, try using the BootManager to load cdcacm as an additional module, to see if it detects the modem.
Currently, there is no simple way to add a USB module to the list Puppy recognizes. If Barry hasn't already done it for 4.01, I expect to implement an override scheme similar to that used for PCI hardware. But to test your modem before that, I would modify the file /lib/modules/...usb-map (something like that -- I have no access to Puppy this week, so cannot try it until the weekend) The trick would be to copy one of the statements beginning with "cdcacm" and substitute your vendor and product IDs in the second and third fields -- but first verify that it is not already there. I can set it up after I return home, if you don't want to.
I have written the above with no reference to Puppy code, so hope I got it right. I hope your modem is Rev. 3 and that we can get it to work, although the link above suggests people had trouble with it faster than 28.8k.
Richard
PS: I also found this at another site, referencing the same hardware ID as yours:
So you might try substituting the following, instead of the above code:. . NetComm (AU) .
AUS C-Tick #N367 Roadster II 56 USB, Model AM5050R3, Conexant CDC USB chipset, use "ln -s /dev/usb/acm/0 /dev/modem" (USB\VID_06EA&PID_0002) USB John Reid
Code: Select all
ln -snf usb/acm/0 /dev/ttyACM0
ln -snf ttyACM0 /dev/modemRichard
Thanks for the info,Iwill have a play tomorrow and see what happens.
I found Pl2303 in the boot manager and installed it and the boot sequence recognised an analog modem but did not seem to communicate with the modem as the serial one does. When I used pupdial it showed a modem /dev/ttyUSB0 but said it was a directory etc I then tried the fixes suggested by you and Russ but when I tried to connect the modem flashed once and that was it. Still some progress is made. I will let you know how your latest tricks go.
Thanks again Regards Dennis
ps Incidentally some years ago this usb modem worked quite well on a version of Mandrake however it only worked on one then later it did not.
Module cdcacm sounds familiar. Regards Dennis
Thanks for the info,Iwill have a play tomorrow and see what happens.
I found Pl2303 in the boot manager and installed it and the boot sequence recognised an analog modem but did not seem to communicate with the modem as the serial one does. When I used pupdial it showed a modem /dev/ttyUSB0 but said it was a directory etc I then tried the fixes suggested by you and Russ but when I tried to connect the modem flashed once and that was it. Still some progress is made. I will let you know how your latest tricks go.
Thanks again Regards Dennis
ps Incidentally some years ago this usb modem worked quite well on a version of Mandrake however it only worked on one then later it did not.
Module cdcacm sounds familiar. Regards Dennis
Richard..
I installed cdc-acm via the bootmanager and removed Pl2303 and on boot the modem was not detected. I called it a number of things on wvdial.conf and pup dial showed it but could not see it.There was no /dev/ttyACM0 so I created it (mknod etc) but nothing would work.Strangely with Pl2303 installed in the boot up it showed detection of analog modem but did not communicate as the serial modem does when detected at boot.I am at the limit of my imagination at this time. It really does not matter if I get it going or not as the serial modem works fine so if you have better things to do thats OK. I am just curious to see why it does not work and would like to see how it compares with the serial modem.I only have dialup and it is slow anyway in country NSW.
Regards Dennis.
I installed cdc-acm via the bootmanager and removed Pl2303 and on boot the modem was not detected. I called it a number of things on wvdial.conf and pup dial showed it but could not see it.There was no /dev/ttyACM0 so I created it (mknod etc) but nothing would work.Strangely with Pl2303 installed in the boot up it showed detection of analog modem but did not communicate as the serial modem does when detected at boot.I am at the limit of my imagination at this time. It really does not matter if I get it going or not as the serial modem works fine so if you have better things to do thats OK. I am just curious to see why it does not work and would like to see how it compares with the serial modem.I only have dialup and it is slow anyway in country NSW.
Regards Dennis.
Dennis,
I was real sure that my modem would work with puppy because when I would boot puppy and the kernel was trying to find the modem it would actually get to the point of not only recognizing the modem (lights would light up) but would also go all the way up to a dialtone. I had a feeling that something was wrong with the program (pupdial) that dialed in. The only other thing I would suggest is try to use the other kernel (if you are not using it). Puppy 4.0 has 2 kernel versions and some have said they have more luck with older computers with the later kernels (2.6.23 and above). Puppy 4.0 has a 2.6.25 kernel and a 2.6.21... kernel.
I was real sure that my modem would work with puppy because when I would boot puppy and the kernel was trying to find the modem it would actually get to the point of not only recognizing the modem (lights would light up) but would also go all the way up to a dialtone. I had a feeling that something was wrong with the program (pupdial) that dialed in. The only other thing I would suggest is try to use the other kernel (if you are not using it). Puppy 4.0 has 2 kernel versions and some have said they have more luck with older computers with the later kernels (2.6.23 and above). Puppy 4.0 has a 2.6.25 kernel and a 2.6.21... kernel.
russ,
Sorry for my reply to you about a PCMCIA modem. I intended it for kapper in another thread, so have moved it there.
Dennis,
I too am interested in getting your USB modem working (for everyone who has one like it), or knowing why it won't. Be sure the name you put into the BootManager is "cdcacm" without a hyphen. Before doing that, you might enter "modprobe cdcacm" in a console window, after booting with the modem plugged in. It should just return with the # prompt, without any message about no such device detected. That should settle whether cdcacm is appropriate. Then we can mess with the /dev entries.
I don't think you need to add nodes; we need to see what the driver expects, which should be one of those already present in Puppy. Then we need a softlink (/dev/ttyACM0) to whatever that is, so PupDial/wvdial can reference it; that technique worked for russ with the pl2303 driver.
Richard
Sorry for my reply to you about a PCMCIA modem. I intended it for kapper in another thread, so have moved it there.
Dennis,
I too am interested in getting your USB modem working (for everyone who has one like it), or knowing why it won't. Be sure the name you put into the BootManager is "cdcacm" without a hyphen. Before doing that, you might enter "modprobe cdcacm" in a console window, after booting with the modem plugged in. It should just return with the # prompt, without any message about no such device detected. That should settle whether cdcacm is appropriate. Then we can mess with the /dev entries.
I don't think you need to add nodes; we need to see what the driver expects, which should be one of those already present in Puppy. Then we need a softlink (/dev/ttyACM0) to whatever that is, so PupDial/wvdial can reference it; that technique worked for russ with the pl2303 driver.
Richard
Richard . Thanks for the continuing help.. If I modprobe cdcacm I get FATAL no module In the Module add-list manager it shows the module cdc_acm and if I modprobe cdc_acm it goes to the cursor. lsmod shows cdc_acm and it was present when I last tested the modem as shown in the last post.
Neither Pl2303 or cdc_acm were in the lsmod when I started this investigation. Incidentally I tried the modem with a blank wvdial.conf with either,both,or neither of these modules with the result shown in earlier posts. If I try with the existing wvdial for the serial modem it apparently looks no further than the previously used modem.
There is no cdcacm without the hyphen shown on the module add-list manager.
Regards Dennis
Neither Pl2303 or cdc_acm were in the lsmod when I started this investigation. Incidentally I tried the modem with a blank wvdial.conf with either,both,or neither of these modules with the result shown in earlier posts. If I try with the existing wvdial for the serial modem it apparently looks no further than the previously used modem.
There is no cdcacm without the hyphen shown on the module add-list manager.
Regards Dennis