|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
hi, i have this pretty straight forward ISA modem, 33.6 and running
off /dev/ttyS3:
orange:~> setserial -a /dev/ttyS3
/dev/ttyS3, Line 3, UART: 16550A, Port: 0x02e8, IRQ: 3
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal auto_irq
i am running 2.4.2, serial.o is inserted into the kernel as a module
by kmod, and i use minicom for testing right now.
it's configured to go via /dev/modem, which is a symlink to ttyS3,
115200 8N1 as usual. and on the upswing, it kind of works: i enter
ATZ^M into minicom and it responds with OK.
*but*:
it takes between 10 and 20 seconds to respond with OK. that's not
normal... and it looks almost like an IRQ conflict to me. but nothing
is reported in the logs.
i don't have a manual for the modem, nor can i find info online as i
don't even know what brand it is. all i know is that it uses the
Rockwel RCV288DST chipset R6628 and that's about it. nevertheless, the
above configuration 0x02e8/irq3 looks absolutely fine for an internal
modem...
do you guys have any experience, tips, hints, whatever?
thanks a lot!
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
--
all i ask of life is a constant and
exaggerated sense of my own importance.
______________________________________________________________________
Philadelphia Linux Users Group - http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|