Any input to modem problem?

[cyoung at bbnplanet.com (Chuck Young)]

Is there any plug-and-play hanky-panky going on here?  Perhaps NT is
getting the new info from the BIOS and Linux is not handling it the same
way.  Can you override plug'n'play with your BIOS setup?

Just one idea for starters...

Chuck Young
GTE Internetworking

On Mon, 28 Sep 1998, Kuan Lee wrote:

   
   hi guys,
   
   I'm having a problem installing a Zoom 56K internal modem.
   Have already contacted Zoom's support which up until now
   have been less than helpful.  I wanted to see if anyone
   might have any suggestions or what you think of it.
   (I've jumpered the new modem for the COM port/IRQ of the old modem,
    and even went as far as removed unnecessary cards,
    trying other COM ports and card slots, slowing the speed
    of the port to 38400 and 9600 (setserial).    Here's the kicker,
    the card works under NT on another machine.)
   
   It looks like the modem is yanking the IRQ line (continuously) 
   when it shouldn't.
   Here's the /proc/interrupts data after running kermit
   On my old modem no interrupts are serviced until after I 
   connect to the modem (which is normal).
   
   Has anyone with more experience any comments or suggestions.
   
   -Kuan
   
   > caliope:~# kermit
   > 
   > C-Kermit 5A(189), 30 June 93, POSIX
   > Type ? or HELP for help
   > C-Kermit>suspend
   > 
   > [2]+  Stopped (signal)        kermit
   > 
   > caliope:~# cat /proc/interrupts
   >  0:      21607   timer
   >  1:        424   keyboard
   >  2:          0   cascade
   >  4:    1122336 + serial
   > 12:          0   PS/2 Mouse
   > 13:          1   math error
   > 14:      11348 + ide0
   > 15:          5 + ide1
   > caliope:~# sleep 80;cat /proc/interrupts
   >  0:      29822   timer
   >  1:        482   keyboard
   >  2:          0   cascade
   >  4:    6618339 + serial
   > 12:          0   PS/2 Mouse
   > 13:          1   math error
   > 14:      11464 + ide0
   > 15:          5 + ide1
   > /*
   > ** Note 5,496,003 interupts in about 80 seconds !! 
   > ** again when there shouldn't be any.  
   > ** Higher DTE speed (38400 vs. 9600) is probably responsible for the 
   > ** increase (from 10K to 68.7K interupts/sec)
   > ** It's starting to affect other devices (like the timer!), i.e 5 sec
   > ** delay in the while loop has now turned into 8 secs
   > */
   
   
   
   -- 
   -==-
   Kuan
   
   ***
   Subcription/unsubscription/info requests: send e-mail with subject of
   "subscribe", "unsubscribe", or "info" to discuss-request at blu.org
   

***
Subcription/unsubscription/info requests: send e-mail with subject of
"subscribe", "unsubscribe", or "info" to discuss-request at blu.org