no connect yet

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



You will need to make sure that the kernel that you are running knows how
to talk to this serial card.  There are different compile time options
that you need to look at.

HTH
FC


On Sat, 15 Sep 2001, Jude DaShiell wrote:

> I'm not sure, minicom once configured doesn't show the initialization
> string on the screen nor does it show the ok which should be coming back
> from the modem.  I'm pretty sure nothing happened to the modem, probably
> can  have it checked out for life later this weekend.  The other thing is,
> I tried temporarily switching modem and doubletalk lt in ttyS0 and ttyS1.
> The doubletalk lt wouldn't talk when it was placed in ttyS1.  The
> difference between those two ports is ttyS0 is my only isa port on the
> machine and ttyS1 is one of those siig 20x pci serial ports.  It's
> possible I'll have to have setpci run to wake this second serial card up.
> As things stand, red hat really badly identified my sound card.  It called
> it a real card with vortex audio.  It's got vortex audio, but it's a
> voyatra turtle beach montego 2 card and in any case is unsupported.  I
> made a mistake in dealing with a computer vendor that insisted on putting
> their own parts selections into this machine in so far as I couldn't get
> two isa slots on it.  The turtle beach choice was my fault though since I
> thought at the time it would have better Linux support.  So am I the only
> one on the list with a siig 20x serial card?  If not, might someone have
> the settings for setpci?  As things stand setserial identifies everything
> correctly except my uart.  I think that's a 16550A but can't get setserial
> to save any update to the blank uart field.





[Index of Archives]     [Linux Speakup]     [Fedora]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]