Re: [expert] Modem Busy? IRQ conflict?
> use setserial to put the modem on ttyS2 (COM3) and it shld work fine :) > your motherboard might have 2 serial ports running.. so make this the > 3rd one. You could also use setserial to put it in irq polling mode (set it to irq0). I had to do this on my laptop. "setserial /dev/ttyS1 irq 0" works for me (obviously change the tty to suit your case). Regards, Ozz. Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Modem Busy? IRQ conflict?
use setserial to put the modem on ttyS2 (COM3) and it shld work fine :) your motherboard might have 2 serial ports running.. so make this the 3rd one. -sarang Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Modem Busy? IRQ conflict?
"Riley, Patrick (Patrick)** CTR **" wrote: > > Hi everyone, I'm about ready to explode because I can't get this problem > figured out. I just recently switched to Mandrake 7.1 from Redhat 6.2 and > I'm > > trying to dial through KPPP and I keep getting "modem is busy". I also try > to go dial out through other things (minicom, and so on) and I get pretty > much the same response. I had this modem working fine under Redhat by just > adding the "setserial /dev/ttyS0 port 0xdc00 irq 5" line but now it won't > work with > > Mandrake. What could have changed? Is something conflicting with my modem > (by the way, it is NOT a winmodem)? It's a US Robotics 56k Model > > 2977. I've copied some of my system info below if it might help. I would > appreciate any help that anyone could give on how I might get this working. > > Thanks. > My machine is a Athlon 650, 128Mb RAM, Abit Ka7 if it helps. Ok...first of all if you're listing the correct com ports (/dev/ttyS0) that you have the modem setup on then it's no wonder the modem isn't working cause /dev/ttyS0 is COM port 1 and that's where the mouse goes. Mandrake will install the mouse there by default during the installation unless you tell it otherwise. It doesn't matter whether you're using a PS/2 mouse or a serial mouse. It will be assigned the device port of /dev/ttyS0. The modem is generally placed on /dev/ttyS1 (COM 2) and works there quite happily. Change the setting for your modem in the KPPP setup options and try dialing out again. This should work for you. -- Mark ** =/\= No Penguins were harmed | ICQ#27816299 ** <_||_> in the making of this | ** =\/= message...| Registered Linux user #182496
Re: [expert] Modem Busy? IRQ conflict?
Submitted 08-Sep-00 by Riley, Patrick (Patrick)** CTR **: > Yes, if I do a dmesg, it shows /dev/ttyS0 and /dev/ttyS1. I had the modem > working great under RH 6.2 on /dev/ttyS0 port 0xdc00 irq 5, but now "modem > busy". It's got me baffled, I've tried what seems like everything. Okay. Took a closer look at your devices and that may be where the problem lies: 5: 12 XT-PIC usb-uhci, usb-uhci IRQ 5 is in fact in use by the above mentioned devices (your Apollo USB controllers), thus "Device or resource busy." Can you reconfigure the card to IRQ 9? I've had to do that with an internal modem when 5 wasn't available (jumperless soundcard took it). -- Anton GrahamGPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request There is nothing wrong with writing ... as long as it is done in private and you wash your hands afterward.
RE: [expert] Modem Busy? IRQ conflict?
Yes, if I do a dmesg, it shows /dev/ttyS0 and /dev/ttyS1. I had the modem working great under RH 6.2 on /dev/ttyS0 port 0xdc00 irq 5, but now "modem busy". It's got me baffled, I've tried what seems like everything. > -- > From: Anton Graham[SMTP:[EMAIL PROTECTED]] > Reply To: [EMAIL PROTECTED] > Sent: Friday, September 08, 2000 3:11 AM > To: [EMAIL PROTECTED] > Subject: Re: [expert] Modem Busy? IRQ conflict? > > Do you have other serial ports in the machine and might another of them be > /dev/ttyS0? What does "dmesg | grep ttyS" show? > > -- > Anton GrahamGPG ID: 0x18F78541 > <[EMAIL PROTECTED]> RSA key available upon request > > "It is as natural to man to die as to be born; and to a little infant, > perhaps, the one is as painful as the other." > -- Francis Bacon, Of Death > >
Re: [expert] Modem Busy? IRQ conflict?
Do you have other serial ports in the machine and might another of them be /dev/ttyS0? What does "dmesg | grep ttyS" show? -- Anton GrahamGPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request "It is as natural to man to die as to be born; and to a little infant, perhaps, the one is as painful as the other." -- Francis Bacon, Of Death
[expert] Modem Busy? IRQ conflict?
Hi everyone, I'm about ready to explode because I can't get this problem figured out. I just recently switched to Mandrake 7.1 from Redhat 6.2 and I'm trying to dial through KPPP and I keep getting "modem is busy". I also try to go dial out through other things (minicom, and so on) and I get pretty much the same response. I had this modem working fine under Redhat by just adding the "setserial /dev/ttyS0 port 0xdc00 irq 5" line but now it won't work with Mandrake. What could have changed? Is something conflicting with my modem (by the way, it is NOT a winmodem)? It's a US Robotics 56k Model 2977. I've copied some of my system info below if it might help. I would appreciate any help that anyone could give on how I might get this working. Thanks. My machine is a Athlon 650, 128Mb RAM, Abit Ka7 if it helps. *** less /proc/interrupts CPU0 0: 193956 XT-PIC timer 1: 1735 XT-PIC keyboard 2: 0 XT-PIC cascade 5: 12 XT-PIC usb-uhci, usb-uhci 8: 1 XT-PIC rtc 10: 361084 XT-PIC emu10k1 11: 0 XT-PIC eth0 12: 79640 XT-PIC PS/2 Mouse 13: 1 XT-PIC fpu 14: 6561 XT-PIC ide0 15: 5 XT-PIC ide1 NMI: 0 ** lspci -v 00:08.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com USR-56k Internal FAX Modem (Model 2977) Flags: medium devsel, IRQ 5 I/O ports at dc00 Capabilities: [dc] Power Management version 2 ** less /proc/pci PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies VT 8371 [KX133] (rev 2). Medium devsel. Master Capable. No bursts. Prefetchable 32 bit memory at 0xd000 [0xd008]. Bus 0, device 1, function 0: PCI bridge: VIA Technologies VT 8371 PCI Bridge (rev 0). Medium devsel. Master Capable. No bursts. Min Gnt=12. Bus 0, device 7, function 0: ISA bridge: VIA Technologies VT 82C686 Apollo Super (rev 34). Medium devsel. Master Capable. No bursts. Bus 0, device 7, function 1: IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 16). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. I/O at 0xd000 [0xd001]. Bus 0, device 7, function 2: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16). Medium devsel. IRQ 5. Master Capable. Latency=32. I/O at 0xd400 [0xd401]. Bus 0, device 7, function 3: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16). Medium devsel. IRQ 5. Master Capable. Latency=32. I/O at 0xd800 [0xd801]. Bus 0, device 7, function 4: Host bridge: VIA Technologies VT 82C686 Apollo Super ACPI (rev 48). Medium devsel. Fast back-to-back capable. Bus 0, device 8, function 0: Serial controller: Unknown vendor Unknown device (rev 1). Vendor id=12b9. Device id=1008. Medium devsel. IRQ 5. I/O at 0xdc00 [0xdc01]. Bus 0, device 13, function 0: Ethernet controller: Winbond NE2000-PCI (rev 0). Medium devsel. Fast back-to-back capable. IRQ 11. I/O at 0xe000 [0xe001]. Bus 0, device 17, function 0: Multimedia audio controller: Unknown vendor Unknown device (rev 8). Vendor id=1102. Device id=2. Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=2.Max Lat=20. I/O at 0xe400 [0xe401]. Bus 0, device 17, function 1: Input device controller: Unknown vendor Unknown device (rev 8). Vendor id=1102. Device id=7002. Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. I/O at 0xe800 [0xe801]. Bus 1, device 0, function 0: VGA compatible controller: NVidia Unknown device (rev 17). Vendor id=10de. Device id=2d. Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xd400 [0xd400]. Prefetchable 32 bit memory at 0xd600 [0xd608]. ** setserial /dev/ttyS0 port 0xdc00 irq 5 ** ls -l /dev/modem lrwxrwxrwx 1 rootroot10 Sep 7 11:36 /dev/modem -> /dev/ttyS0 ** setserial /dev/ttyS0 /dev/ttyS0, UART: 16550A, Port: 0xdc00, IRQ: 5 **
