Following is what I have in aswer to your questions.
1. typed ls -1 /dev/modem
2. typed setserial -a /dev/modem
response /dev/modem,Line 1,UART:16550A,Port:0x02f8,IRQ:3
3. question: How does the modem behave?
answer: Works Ok in WIN98, no response at all in Linux.
4. question: Can you run minicom?
answer: I can run Minicom from the KDE desktop. When I maximize the
screen, the lowest row shows the modem to be "offline". I
could configure by typing ALT-O, selecting serial port
setup, entering /dev/modem, and saving file as dfl. I was
also able to set ECHO to ON, and initialize modem, but it
remained offline.It would not respond to ATDT.
5. question: Is IRQ 3 being used by something else?
answer: /proc/interrupts shows IRQ 3 assigned to "serial"
6. question: IRQ conflicts in WIN98?
answer: none that I could find
7. question: Contents of /proc/(devices,ioports,interrupts,pci)?
02f8-02ff : serial(auto)
03f8-03ff : serial(auto)
remaing 16 lines omitted
0: 501198 XT-PIC timer
1: 3537 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 0 XT-PIC serial
8: 2 XT-PIC rtc
12: 45577 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 471847 XT-PIC ide0
15: 8 XT-PIC ide1
pci devices found:
Bus 0, device 0, function 0:
Host bridge: Intel 440BX - 82443BX Host (rev 2)
Medium devsel. Master Capable. Latency=64
Prefetchable 32 bit memory at 0xe4000000 [0xe4000008]
Bus 0, device 1, function 0
PCI bridge: Intel 440BX - 82443BX AGP (rev2)
Medium devsel. Master Capable. Latency=64 Min Gnt=136
Bus 0, device 4, function 0:
ISA bridge: Intel 82371AB PIIX4 ISA (rev2).
Medium devsel. Fast back-to-back-capable. Master
Capable No bursts.
Bus 0, device 4, function 1:
IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
Medium devsel Fast back-to-back capable. Master
I/O at 0xd800 [0xd801]
Bus 0, device 4, function 2:
USB Controller: Intel 82371AB PIIX4 USB (rev 1).
Medium devsel. Fast back-to-back capable. IRQ 10.
Master Capable. Latency=32.
I/O at 0xd400 [0xd401].
Bus 0, device 4, function 3:
Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
Medium devsel. Fast back-to-back capable
Bus 1, device 0, function 0:
VGA compatible controller: Intel Unknown device (rev
Vendor id=8086. Device id=7800.
Medium devsel. Fast back-to-back capable. IRQ 11.
Master Capable. No bursts.
Prefetchable 32 bit memory at 0xe3000000 [0xe3000008]
Non-prefetchable 32 bit memory at 0xe2000000
8. question: Are you sure it's com2, irq 3?
answer: No I'm not sure, but see contents of included files.
Thanks for your patience. I looking at a lot of trees now, but I still
haven't seen the forest.
Silviu Minut wrote:
> Post _verbatim_ the output of
> ls -l /dev/modem
> setserial -a /dev/modem
> How exactly does the modem behave? Can you run minicom? Is IRQ 3 being
> something else? Look for IRQ conflicts in Win98. You can also look in
> (devices, ioports, interrupts, pci). Are you sure it's com2, irq 3?
> John Martin wrote:
> > Hi,
> > Thank you for your response to my cry for help.
> > Win98-Device Manager-Properties shows:
> > Interrupt request = 3 and input/output range = 02F8-02FF.
> > After booting Linux and logging in as root, I typed
> > ln -s /dev/ttyS1 /dev/modem
> > and received following response:
> > ln: /dev/modem: file exists
> > I typed:
> > setserial -a /dev/modem
> > and received following response:
> > /dev/modem, line 1, UART:16550A, Port: 0x02f8
> > Baud_base: 115200, close_delay:50, divisor: 0
> > closing_wait: 3000, closing_wait2: infinite
> > Flags: spd_normal skip_test
> > Appears that both Win98 and Linux are using the same IRQ--3.
> > Will appreciate hearing further from you.
> > Thanks again.
> > SIlviu Minut wrote:
> > > ln -s /dev/ttyS1 /dev/modem
> > > setserial -a /dev/modem and see what IRQ and IO
> > is
> > > Linux trying to use with the modem
> > > Boot W98 and go to Device Manager->properties and see the resources
> > the
> > > modem. Mine for instance uses irq 11 while Linux is by default hoping
> > irq
> > > 4.
> > > Suppose you see irq 11 in W98. Then in Linux
> > > setserial /dev/modem irq 11
> > > Similarly if you want to modify other settings. Note that IRQs and
> > are a
> > > hardware thing, and they are normally assigned by the BIOS (or with
> > jumpers).
> > > With setserial you're telling Linux what these resources are.
> > > John Martin wrote:
> > > > I have installed SuSe 6.1 Linux, and the KDE desktop.
> > > > I ran "yast" from the console to configure the modem, and then ran
> > > > from the desktop to configure the ISP connection.
> > > > However when I try to "connect" using Kppp, i receive: (1) modem
> > and
> > > > (2) sorry, modem does not respond.
> > > > I then ran wvdialconf as directed in the SuSE manual, but the
> > was
> > > > that no modem was detected.
> > > > I have two hard drives which can be exchanged using a
> > > > system. Windows 98 is installed on one drive and Linux on the
> > When
> > > > I use Windows 98, the modem is connected to com port 2, and using
> > Netscape
> > > > 4.5, I can connect to my ISP. So the modem appears to be functiona.
> > > > Advice and suggestions will be appreciated.
> > > > --
> > > > Posted via CNET Help.com
> > > > http://www.help.com/
> > --
> > Posted via CNET Help.com
> > http://www.help.com/
Posted via CNET Help.com