Seather
Apprentice
Joined: 23 May 2003
Posts: 194
Location: South Africa
|
 Posted: Sat Feb 12, 2005 9:59 am Post subject: wvdial + winmodem |
 |
|
Hi there, having a bit of a problem getting my winmodem to work for a faxserver.
lspci -vv gave me the following output:
| Code: | 0000:00:08.0 Communication controller: Agere Systems (former Lucent Microelectronics) F-1156IV WinModem (V90, 56KFlex) (rev 01)
Subsystem: GVC Corporation LT WinModem 56k Data+Fax+Voice+VoiceView+Dsvd
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (63000ns min, 3500ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at dfffbe00 (32-bit, non-prefetchable)
Region 1: I/O ports at cc00 [size=8]
Region 2: I/O ports at c800 [size=256]
Capabilities: <available only to root> |
So I emerged the ltmodem port, and loaded the two modules, which seemed to go just fine
| Code: | Feb 12 11:44:15 lucy kernel: Loading Lucent Modem Controller driver version 8.26
Feb 12 11:44:20 lucy kernel: Detected Parameters Irq=5 BaseAddress=0xc800 ComAddress=0xcc00
Feb 12 11:44:20 lucy kernel: ttyLT0 at I/O 0xc800 (irq = 5) is a Lucent Modem |
However, now when I try with wvdialconf, it doesn't pick it up
| Code: | lucy seather # wvdialconf /etc/wvdial.conf
Scanning your serial ports for a modem.
ttyLT0<Info>: Cannot set information for serial port.
Port Scan<*1>: LT0
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.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S2 S3 S4 S5 S6 S7
ttySLT0<Info>: Cannot set information for serial port.
Port Scan<*1>: SLT0
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://open.nit.ca/wvdial/
If you still have problems, send mail to wvdial-list@lists.nit.ca. |
Anyone know what I can do to make wvdial see it? |
|
Kernel & Hardware
