Well, too soon to be happy. cron runs periodically rmmod -a . Then when I want to use the modem again serial driver is re-loaded: Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A And the modem is inaccessible again. setserial shows that /dev/ttyS4 reverted to original parameters. I have to run the setserial command manually again. How can I fix this? BTW I have added proper setserial command to /etc/rc.boot/0setserial as mentioned in the manpage. Tomasz.
- Re: cannot talk with AT modem Phil Brutsche
- Re: cannot talk with AT modem Pavel M. Penev
- Re: cannot talk with AT modem Tomasz Barszczak
- xfs-xtt - cannot establish any listening sockets Brendon B
- Re: xfs-xtt - cannot establish any listening so... [EMAIL PROTECTED]
- Re: cannot talk with AT modem Phil Brutsche
- Re: cannot talk with AT modem John Pearson
- Re: cannot talk with AT modem ferret
- Re: cannot talk with AT modem Tomasz Barszczak
- Re: cannot talk with AT modem Phil Brutsche
- Re: cannot talk with AT modem Tomasz Barszczak
- Re: cannot talk with AT modem Phil Brutsche
- Re: cannot talk with AT modem Lehel Bernadt