Hi,
I'm looking for some help getting a modem working on Linux (Slackware-10.1).
Here's where I've got to so far.
The modem is internal (ISA) and was working with Win95 before I installed
Linux. From visual inspection of the modem I can see that it contains a
Cirrus Logic CL-MD34XX chip which should work fine with Linux.
http://www.toombeola.com/board.jpghttp://free.hostdepartment.com//g/gromitkc/intel/cirrus_cl-md34xx.html
<http://free.hostdepartment.com/g/gromitkc/intel/cirrus_cl-md34xx.html>
Looking at the boot messages I can see the kernel picked it up fine
bash-3.00# dmesg | grep isa
isapnp: Scanning for PnP cards...
isapnp: Card 'Logicode Technology, Inc.; Model 33H-V-P'
isapnp: 1 Plug & Play card detected total
I'm pretty sure the BIOS was PnP configuring it OK but just in case I forced
a configuration with the isapnp configuration file
bash-3.00# grep -v \# /etc/isapnp.conf | grep -v ^$
(READPORT 0x0273)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFIGURE LTI000c/-1 (LD 0
(IO 0 (SIZE 8) (BASE 0x03f8) (CHECK))
(INT 0 (IRQ 4 (MODE +E)))
(NAME "LTI000c/-1[0]{Logicode Technology, Inc.; Model 33H-V-P}")
(ACT Y)
))
(WAITFORKEY)
Key points here being the IO port and IRQ. The confirmation was produced by
doing a "pnpdump --config". The docs for the version of isapnptools I'm
using say that it will detect conflicts so I should be OK there.
Looking at the serial configuration I have the following
bash-3.00# head /etc/serial.conf
#
# This is a sample serial.conf file. You should uncomment out and modify
# the relevant lines as necessary.
#
# These are the standard COM1 through COM4 devices
#
/dev/ttyS0 port 0x3F8 auto_irq autoconfig
/dev/ttyS1 port 0x2f8 auto_irq autoconfig
#/dev/ttyS2 uart 16450 port 0x3E8 irq 4
The autoconfig, auto_irq options seem to have picked up the correct IRQ and
configured the other bits
bash-3.00# setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal auto_irq
/dev/modem is linked to /dev/ttySO
bash-3.00# ls -al /dev/modem
lrwxrwxrwx 1 root root 5 2005-07-04 19:09 /dev/modem -> ttyS0
Based on the above, as far as I can see, the card knows the correct port/IRQ
as does the driver. When I fire up minicom to see if all this has worked I
get nothing. An "AT" command does not get the "OK" response it should -
there's just a blank screen.
So anybody got any ideas of where I could go next with this?
* I don't have the option of booting back into Windows to check any of
the settings but I'm pretty sure that the pnpdump setting are OK.
* I'm suspicious that despite the chip in the card it may in fact be a
WinModem - any idea if there is any way to confirm this?
* I'm not expecting a "do X and it will work" type answer - any other
avenues I could look at would be helpful.
* Obviously the easiest solution would be to nip down to Peats and
pick up a PCI Linux compatible modem - the 20 euro would not kill me! So
this is more about figuring it out than getting it done if you know what I
mean.
Thanks,
Paschal.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!