Hi, -----Original Message----- From: Syeh Abidin [SMTP:A3@Telkom.net] Sent: Wednesday, May 24, 2000 8:51 AM
Hello All, This is very confuse problem. I will tell what I do for My winmodem (HSP PCTEL AUDIOMODEM Riser 56k)
1. Download the Driver named HSPPCTEL 2. Copy the module pctel.o to /lib/modules/2.2.10/net 3. Write line /sbin/insmod pctel in /sbin/init.d/boot.local
Every time boot there is messages IRQ 11 /dev/ttyS15 is PCTel. or something like that.
4. use kppp to query modem. Said, sorry modem isn't responding.
Check /dev/modem to make sure it is a symbolic link to /dev/ttyS15, if not create or modify it as necessary.
5. I use cat /proc/interrupts There is no Interrupts for number 11
I have a lucent pci modem that also uses its own module. It only shows up in /proc/interrupts when it is actually in use and releases it otherwise, so I assume this is normal.
6. I use lsmod There is module pctel loaded..
Try looking through the output of lspci, see if it shows up there. I don't know how Linux handles AMR devices, hopefully they are treated like normal pci. If not maybe it is treated like an isa card so check that too (try pnpdump or whatever it is, I'm not that familiar with isapnp cards). Post any output relating to the PCtel.
7. I use cat /dsp/ttyS15 , Nothing...Out
I assume this is a typo? it should be /dev/ttyS15.
So PCtel loaded but not use IRQ 11 ...Why ? and how to solve it. Someone has recommended me setserial /dev/ttyS15 irq 11 # can't
So WHat 's thing ..!!
Finally, check the permissions on /dev/ttyS15 and /dev/modem, IIRC when I ran the install script for my Lucent modem it changed them. What's the output of ls -l /dev/ttyS15 -----Original Message----- From: Rik Dunphy [SMTP:Rik.Dunphy@motorola.com]
Usually when I see "modem isn't responding" it's because there is no uart setup. This is caused by the char-major-4 (in modules.conf) being set to serial, yet I have compiled the serial ports into the kernel. I can only assume that maybe the pctel module is causing a similar problem.
The easy check is to set char-major-4 to off, and reboot.
The Lucent install script changes this to a different char-major (it uses one in the experimental/local range) to avoid such conflicts. His might be similiar, and probably should be. Tim -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/