RE: [SLE] Winmodem can't work, Please read this
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/
Hello Tim, One More Messages when booting It's said : #this is Serial Devices Messages Setting up PCtel serial ttyS15 on Interrups 11 PCtel (undefined) Thursday, May 25, 2000, 8:21:36 PM, you wrote: TD> Check /dev/modem to make sure it is a symbolic link to /dev/ttyS15, if TD> not create or modify it as necessary. All normally, It's linked TD> I have a lucent pci modem that also uses its own module. It only shows TD> up in /proc/interrupts when it is actually in use and releases it TD> otherwise, so I assume this is normal. Ok! TD> Try looking through the output of lspci, see if it shows up there. I TD> don't know how Linux handles AMR devices, hopefully they are treated TD> like normal pci. If not maybe it is treated like an isa card so check TD> that too (try pnpdump or whatever it is, I'm not that familiar with TD> isapnp cards). TD> Post any output relating to the PCtel. It's PCI device but Onboard
7. I use cat /dsp/ttyS15 , Nothing...Out Sorry, I mean /dev/ttyS15 TD> I assume this is a typo? it should be /dev/ttyS15.
TD> Finally, check the permissions on /dev/ttyS15 and /dev/modem, IIRC when TD> I ran the install script for my Lucent modem it changed them. TD> What's the output of ls -l /dev/ttyS15 This Right, and even I work as root
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 TD> 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. No, This cause more problem char-major-4 is where is the mouse on ttyS0
-- Best regards, Syeh mailto:A3@Telkom.net -- 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/
Hi Syeh, type.. setserial /dev/ttyS15 what's the output? Is it possible that something else is sharing the interrupt, even though it it's not in use? For example, I have the ACPI of my BIOS set to int11, Sound to int10 and DVD to int9. But only int10 and int11 are shown when I do a cat /proc/interrupts. (I haven't had time to compile in the power management stuff yet!). You say your using ttyS0 for a mouse. Is there any chance of moving to a PS/2 mouse? These can be picked up very cheaply these days. The reason I ask is that it may be useful to disable the serial ports in your BIOS for now, until you get this working. Also PS/2 mouse moves to int12 ( if I remember correctly). I used to have a winmodem that just refused to work, unless I removed COM1 from the BIOS. Moving the serial port to COM3 in the BIOS worked, but only after I got the modem to come up properly. So on that note, maybe it might be worth disabling the serial ports in your BIOS, and while your there check that the PnP is controlled by the BIOS and not the OS. Then boot into console mode (since you'll have no mouse), and see if you can get it working now. (try wvdial rather than kppp so that you don't need to run X-windows). Good luck, RikD Syeh Abidin wrote:
Hello Tim,
One More Messages when booting It's said : #this is Serial Devices Messages Setting up PCtel serial ttyS15 on Interrups 11 PCtel (undefined)
Thursday, May 25, 2000, 8:21:36 PM, you wrote:
TD> Check /dev/modem to make sure it is a symbolic link to /dev/ttyS15, if TD> not create or modify it as necessary. All normally, It's linked
TD> I have a lucent pci modem that also uses its own module. It only shows TD> up in /proc/interrupts when it is actually in use and releases it TD> otherwise, so I assume this is normal. Ok!
TD> Try looking through the output of lspci, see if it shows up there. I TD> don't know how Linux handles AMR devices, hopefully they are treated TD> like normal pci. If not maybe it is treated like an isa card so check TD> that too (try pnpdump or whatever it is, I'm not that familiar with TD> isapnp cards). TD> Post any output relating to the PCtel. It's PCI device but Onboard
7. I use cat /dsp/ttyS15 , Nothing...Out Sorry, I mean /dev/ttyS15 TD> I assume this is a typo? it should be /dev/ttyS15.
TD> Finally, check the permissions on /dev/ttyS15 and /dev/modem, IIRC when TD> I ran the install script for my Lucent modem it changed them. TD> What's the output of ls -l /dev/ttyS15 This Right, and even I work as root
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 TD> 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. No, This cause more problem char-major-4 is where is the mouse on ttyS0
-- Best regards, Syeh mailto:A3@Telkom.net
-- 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/
-- 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/
Hello Rik,
Thank's for Helping Me find this things, I owe you a lot..
But..
Friday, May 26, 2000, 4:06:24 PM, you wrote:
RD> type..
RD> setserial /dev/ttyS15
it's something like
/dev/ttyS15 uart: not defined io=<forget> irq 11
I tried to use #setserial /dev/ttyS15 uart
Syeh, when you do the setserial there are a number of uarts you can try. The most basic one to try is 16450, then try 16550. e.g. setserial /dev/ttyS15 uart 16450 then do a setserial /dev/ttyS15 and ensure it's been set. COM1 and COM3 both share an interrupt. COM2 and COM4 share another. You can use more than one device, but not at the same time. For example, if the mouse is on COM1 then COM3 can't be used. But... This is the normal settings, you may notice in your BIOS that you can change the configuration of the serial ports, in which case things can change. Windows simply maps your serial port to COM2. IN the BIOS did you make sure that the Plug and Play controlled by is set to BIOS not OS? This is very important if you are dual booting. Did you try /dev/ttyS1? Maybe the modem is remembering something from it's windows set up? I'm not too sure on how to disable the check for serial ports. I think you need to make sure that char-major-4 and char-major-5 are set to off in modules.conf, and that the serial ports are compiled as modules for the kernel. Unfortunately there's not much more I can help you with. I had terrible trouble with my winmodem, and went out and both an externel modem. I got an ELSA modem for about $70. Things worked first time with it! Good Luck Rik -- 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/
Hello Rik, Monday, May 29, 2000, 3:34:22 PM, you wrote: RD> when you do the setserial there are a number of uarts you can try. RD> The most basic one to try is 16450, then try 16550. I give up, Now I have two kernel. File System.map in /boot overwrite the old one RD> e.g. setserial /dev/ttyS15 uart 16450 Now..If I do any to /dev/ttyS15 said /dev/ttyS15: No such device And every time boot said that: modprobe: char-major-62 failed.. I give UPPPPP..... RD> Did you try /dev/ttyS1? Maybe the modem is remembering something from it's RD> windows set up? Now I can't use anything /dev/ttyS15: no such device. He..the drivers sayd that it on /dev/ttyS15, If I can programming maybe I can set it to /dev/ttyS1 -- Best regards, Syeh mailto:A3@Telkom.net -- 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/
participants (3)
-
A3＠Telkom.net -
Rik.Dunphy＠motorola.com -
tduggan＠dekaresearch.com