1099.1

I'm running Suse 7.1 on a 900 Mhz Celeron. I did a reinstall, and now I can't get my ISA modem recognized, no matter which port I select. On my previous installation, I was able to configure it and get online, so I'm sure the modem is useable.

When I boot to Windows, the modem shows up connected to COM2, irq 3. So in Suse, I use setserial /dev/ttyS1, irq 3. (Have also tried ttyS0 and ttyS2, no success). I've tried Yast, Yast2, setserial, and wvdial, and can't see what I'm doing incorrectly. The command in setserial and Yast2 seems to work, but wvdial cannot find the modem. Lately, when I try to use Yast to 'configure a PPP network', it just crashes instead of going on to the next screen.

Can someone suggest proper steps, in correct sequence, to recognize modem and integrate it into the system?

Ron

Yeah buy a external modem.

Ok from what i recall from tinkering with isa stuff
much much earlier in time
use these tools:
pnpdump man pnpdump for more info
isapnp ditto, be sure to be root for using both
don't know what suse uses now but you maybe need to
add some aliases or options in a file called /etc/modules.conf (on my
mandrake/redhat boxes that is) in the early days sometimes
called conf.modules (a bit confusing)
maybe need to make a symlink to your dev/modem in relation to dev/ttyS1
but in kppp it should work with dev/ttyS1 also
And remember that in suse the Yast prog tends to overwrite your
handconfigured files with own defaults, so cp these files
Its one of the reasons i wiped suse of al my boxes
Here is a little part from a mdk 7.1 modules.conf concerning an isa
soundcard as thats the only isa thing around at the moment
.............
alias sound sb
options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
well it aint much but maybe gives you a some clues
enjoy