That's the modem I'm using, and I had to go to "windows" and move the modem
to com 2. Then go into bios and disable PNP os, disable any physical com 2,
that should give that device clear and free usage of com 2 settings.
----- Original Message -----
From: "-michael-" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 09, 2000 9:52 PM
Subject: Re: [newbie] Robotic ISA pnp and linuxconf
> You might try disabling com2 in your BIOS
>
> Daniel Velzi wrote:
>
> > Hi all, sorry for my bad english, hope understand this.
> >
> > When installing Mandrake 7.2 in working mode (personalise) all run ok,
but
> > when run linuxconf (only see setup, nothing to do) and close it I loss
> > internet conection by kppp or similar. Itīs imposible to conect in any
mode
> > (modem robotic ISA PNP). And kppp said SORRY, MODEM IS BUSY.
> > Gnome dialup canīt to work.
> > Canīt connect anymore (boot and problem persist).
> > Quit ppp0 from linuxconf, but problem persist.
> > Same problem is present when installing in expert mode but at first
time,
> > without run linuxconf.
> > Only can detect that my modem is in COM 2 (2f8) but when run linuxconf
it
> > said modem is in 3e8 and when put in 2f8 linuxconf give error (fault).
> > My pc is correctly set. Mandrake 7.0 and RedHat 7.0 run ok for a long
time.
> > And same error found in other 2 pcs with robotic isa PNP.
> > Really must a conflict in com2. So I write isapnp to force 2f8. Mandrake
> > give me error (conflict) no boot. Then probe with
> > setserial /dev/cua1 ^session_lockout
> > setserial /dev/cua1 ^pgrp_lockout
> > And all run ok, but only once time. When boot problem persist. Then
probe
> > with
> > setserial /dev/ttyS1 autoconf
> > And run again. But when boot again must type again. And canīt to
solution
> > conflict problem (whereīs search it ?)
> > Resume: Seems linuxconf crash ppp dialer and modem setup when run it.
Test
> > in 3 pcs with robotic isa PNP. All pcs run ok with others linux
> > distributions. Is there any mode to really correct this ? Anyone know
this
> > problem ? Is a Mandrake bug ?
>
>
>
