Christopher == Christopher S Swingley [EMAIL PROTECTED] writes:
A big guess, but are you guys sure you have no interrupt or
similar conflicts? I have a problem with Xircom modem which
sounds similar to the ones described in pcmcia-howto in
relation to the interrupt conflict
The other poster has suggested removing setserial; is there anything
bad that can result from it (i.e. what does setserial do on a laptop)?
The reason the poster suggested that is because by default setserial
will store and reload serial port configuration information before
PCMCIA card
Hi Christopher S. Swingley; unless Mutt is confused, you wrote:
The other poster has suggested removing setserial; is there anything
bad that can result from it (i.e. what does setserial do on a laptop)?
The reason the poster suggested that is because by default setserial
will store and
I haven't tried this solution yet with 3.1.8, but I'll give it a shot
tomorrow and see if I can get my Xircom modem to work with the latest
PCMCIA.
FWIW, my setserial is seeing the port ttyS1, even though it is disabled
in the bios. /cat/interrupts, OTOH, does not show irq 3, which makes
Hi Brian May; unless Mutt is confused, you wrote:
Also, this isn't the worst of my problems... If I try to bootup with
the card in, or shutdown, the computer will lock up, and require a
hardware reset in order to fix the problem. Inserting/removing the
card after bootup seems to be OK
I recently upgraded my laptop to Linux 2.2.14 (from 2.0.36) with the
latest pcmcia-* and modutils, too. I compiled both the kernel and the
pcmcia-source myself. I don't know if the kernel upgrade is
significant or the upgrade of pcmcia-*.
I don't think it's the kernel. I used to run 2.2.9
On Sun, 16 Jan 2000, Christopher S. Swingley wrote:
The other poster has suggested removing setserial; is there anything
bad that can result from it (i.e. what does setserial do on a laptop)?
The reason the poster suggested that is because by default setserial
will store and reload serial
After buying a pcmcia nic I thought that upgrading the pcmcia-*
packages and recompiling the pcmcia modules would be a good
idea. While I was at it, I upgraded modutils as well. Now I'm
running:
pcmcia-cs_3.1.8-4.deb
pcmcia-source_3.1.8-4.deb
modutils_2.3.9-2.deb
I didn't even start to mess
lehman == lehman [EMAIL PROTECTED] writes:
lehman After buying a pcmcia nic I thought that upgrading the pcmcia-*
lehman packages and recompiling the pcmcia modules would be a good
lehman idea. While I was at it, I upgraded modutils as well. Now I'm
lehman running:
Hi Brian May; unless Mutt is confused, you wrote:
Also, this isn't the worst of my problems... If I try to bootup with
the card in, or shutdown, the computer will lock up, and require a
hardware reset in order to fix the problem. Inserting/removing the
card after bootup seems to be OK though.
A big guess, but are you guys sure you have no interrupt or similar
conflicts? I have a problem with Xircom modem which sounds similar to
the ones described in pcmcia-howto in relation to the interrupt conflict
even though my /proc/interrupt doesn't show one.
I have the same problem whenever
[EMAIL PROTECTED] writes:
After buying a pcmcia nic I thought that upgrading the pcmcia-*
packages and recompiling the pcmcia modules would be a good
idea.
[...]
this broke
my ppp setup somehow. I have a 56K pcmcia modem, running as
ttyS2 (pppd uses /dev/modem which is a symlink
12 matches
Mail list logo
