Please could you tell me were I can get a driver for windows XP to go with my
SupraExpress 56e PRO modem. I want to download this from the Internet if posible.
Yours Ian Weatherhead.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 09:05:47PM -0700, ben wrote:
On Thursday 20 June 2002 08:32 pm, Paul Johnson wrote:
a clean cut and healed nicely without professional attention. The case
in question is a Koolance PC6-2 not a bad case, the lid has
On Thursday 20 June 2002 09:07 pm, Paul Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 09:05:47PM -0700, ben wrote:
On Thursday 20 June 2002 08:32 pm, Paul Johnson wrote:
a clean cut and healed nicely without professional attention. The case
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 09:43:14PM -0700, ben wrote:
you might have a case there, baloo (don't even pardon the pun). give us a
date on the settlement party.
I'm not suing Koolance. The case edge was obviously capable of breaking
skin (as is
On Thursday 20 June 2002 10:22 pm, Paul Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 09:43:14PM -0700, ben wrote:
you might have a case there, baloo (don't even pardon the pun). give us a
date on the settlement party.
I'm not suing Koolance. The
* Paul Johnson ([EMAIL PROTECTED]) [020620 19:43]:
price doesn't seem to play a factor in, and the last thing I want is a
device I plug into a line I know goes to the top of telephone poles
subject to lightning strikes slapped directly on my motherboard.
Another advantage with externals is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 11:24:50PM -0700, Vineet Kumar wrote:
You should be able to find a surge protector with RJ11 jacks on it for
around $9.95 at circuit city...
These tend to introduce a considerable amount of line noise and you end
up
* Paul Johnson ([EMAIL PROTECTED]) [020620 23:28]:
On Thu, Jun 20, 2002 at 11:24:50PM -0700, Vineet Kumar wrote:
You should be able to find a surge protector with RJ11 jacks on it for
around $9.95 at circuit city...
These tend to introduce a considerable amount of line noise and you end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 11:44:21PM -0700, Vineet Kumar wrote:
[CPU]--serial-cable--[modem]--phone-line--wall
| |
| power cord
| |
+-[surge protector]---wall
[CPU]--serial
* Paul Johnson ([EMAIL PROTECTED]) [020621 00:17]:
On Thu, Jun 20, 2002 at 11:44:21PM -0700, Vineet Kumar wrote:
Where's the misunderstanding?
On my part, to be sure. (Re-reading this I realize that I didn't word it
so as to imply that that was my guess; apologies if it sounded rude.)
The
Have you taken a look in /etc/serial.conf? Check very carefully to see if
any lines are uncommented, and if so that they match what your modem setup
really is.
Thanks for the idea :)
I have just checked my serial.conf and it seemed alright--but I've
played with it for the past hour anyways.
Your internal modem, if roasted and ground sufficiently fine, will make
a surprisingly strong espresso. Go get an external modem.
http://www.linuxmafia.com/~rick/faq/#internalmodem
*Sigh*
At first I thought this advice was unhelpful and a bit short. Then I
spent another two days playing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 04:54:25PM -0700, Seth Carbon wrote:
I have seen the light. External good. LEDs are *very helpful* for
diagnostics.
Wouldn't that be, I have seen the lights? 8:o)
See how much easier that was? I hate internal modems
On Thursday 20 June 2002 07:36 pm, Paul Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 04:54:25PM -0700, Seth Carbon wrote:
I have seen the light. External good. LEDs are *very helpful* for
diagnostics.
Wouldn't that be, I have seen the lights?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 20, 2002 at 08:16:03PM -0700, ben wrote:
modems also generate heat; an external modem reduces the cooling load on the
system. on top of that, anything that, on breakage, demands that i take the
cover off the box just pisses me off
On Thursday 20 June 2002 08:32 pm, Paul Johnson wrote:
[snip]
I hate dealing with opening the case, even though it's held on by two
thumbscrews and a padlock. Last time I opened it, I dropped the case
lid, and when I tried to catch it, one corner stuck into the wall, and
the other corner
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jun 17, 2002 at 07:22:59PM -0700, Seth Carbon wrote:
Summary: I cannot get my USR modem to work with the 2.4.18 kernel.
modem: US Robotic internal ISA 56k Data (on-card DSP) (prod#: 005687-03)
Any help or pointers would be greatly
On Tue, 2002-06-18 at 03:13, Paul Johnson wrote:
Your internal modem, if roasted and ground sufficiently fine, will
make
a surprisingly strong espresso. Go get an external modem.
http://www.linuxmafia.com/~rick/faq/#internalmodem
Even if I'm destined for a good string cup, I'd still like to
Throwing this back over the fence...
--
Baloo
---BeginMessage---
On Tue, 2002-06-18 at 03:13, Paul Johnson wrote:
Your internal modem, if roasted and ground sufficiently fine, will make
a surprisingly strong espresso. Go get an external modem.
On 18 Jun 2002, Seth Carbon wrote:
1) The modem has worked fine with every kernel I've put in since I
installed potato. Now both potato (with bunk's upgrades) and woody
fail.
Have you taken a look in /etc/serial.conf? Check very carefully to see if
any lines are uncommented, and if so that
Summary: I cannot get my USR modem to work with the 2.4.18 kernel.
I have recently started trying to upgrade my Debian Potato sytem to the
newer 2.4.18 kernel. Everything is fine except that my USR PnP modem no
longer works. When I check, it is listed in /proc/isapnp (although with
the
Thanks, the article was good. Turns out the problem was a faulty
network card - I know, I should have checked this first. But it
literally gave out while I was installing Debian, so I kinda ignored
that possibility.
Luke
Josh McKinney wrote:
On approximately Thu, Oct 11, 2001 at
Hello everyone. I've recently erased my RedHat Linux machine and
installed Debian Woody. I used [EMAIL PROTECTED] (in Canada) with RedHat just
fine, using either Pump or DHCPCD - specifying the hostname and
interface - with no problems whatever. Now when I try to use the
dynamic IP
I have rogers and I'm working fine although my setup is a little
different from yours (2.2.17 kernel, unstable). I used dhcp-client and
here's my dhclient.conf file
send host-name hostname;
and here's my /etc/network/interfaces
iface lo inet loopback
iface eth0 inet dhcp
And everything works
Strange. I'll try that when I get home today. Did you change any of
the kernel parameters in the /proc filesystem? I remember reading a
blurb about that somewhere affecting DHCP systems. Thanks!
Luke
Kyle Girard wrote:
I have rogers and I'm working fine although my setup is a
On approximately Thu, Oct 11, 2001 at 12:50:25PM -0400, Luke Reeves wrote:
Hello everyone. I've recently erased my RedHat Linux machine and
installed Debian Woody. I used [EMAIL PROTECTED] (in Canada) with RedHat
just
fine, using either Pump or DHCPCD - specifying the hostname and
Nope i'm using the stock debian kernel
On Thu, 2001-10-11 at 14:37, Luke Reeves wrote:
Strange. I'll try that when I get home today. Did you change any of
the kernel parameters in the /proc filesystem? I remember reading a
blurb about that somewhere affecting DHCP systems. Thanks!
This isn't really a debian problem, but a general Linux problem. Anyway, I
have an internal 56k ISA *jumpered* (not the most common things these days)
modem. For simplicity, I disabled the first serial port on my mother board,
and set the modem to live it's space (I'm just use to pointing to
It's also interesting to note that the modem works fine under W2k. Oh, and
I thought that that it could have been pppd not correctly telling my modem
to disconnect, so I tried echoing ATH0 to the device after the connection
was brought down, which didn't help...
Any ideas?
sounds more
It's also interesting to note that the modem works fine under W2k. Oh, and
I thought that that it could have been pppd not correctly telling my modem
to disconnect, so I tried echoing ATH0 to the device after the connection
was brought down, which didn't help...
Any ideas?
sounds more
uar=unknown means that you dont have any hardware on those devices ttyS2
and ttyS3. You can put you device ttySx on any io address you want. That
is , you only need to have as many devices as serial ports.
your problem is that very likely your modem doesnt get identified.
try documentation for the
On Mon, Jul 23, 2001 at 09:31:42PM -0500, Jeremy wrote:
output of dmesg:
Serial driver version 5.05a (2001-03-20) with MANY_PORTS SHARE_IRQ SERIAL_PCI
ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Redundant entry in serial pci_table. Please
I have a USR 5610A pci modem that worked fine with the
2.2.18 series kernel if I set the parameters in my
/etc/serial.conf file (it was /dev/ttyS2), but last
night I got the 2.4.6 source from Sid and built my own
kernel, and now my modem doesn't work. I have ISA PNP
enabled (although it says it
Did you also get the 2.4.? ppp? That is required when
you upgrade to a 2.4.* kernel. You can also try
setserial -g /dev/ttyS* and see what is listed as the
modem. It should be listed as UART 16550A if memory
serves me right.
Don
--- Jeremy Whetzel [EMAIL PROTECTED] wrote:
I have a USR 5610A pci
further more, I remember I also had a strange problem
I had to recompile pppd in order to work with 2.4
well
probably you have 3 serial ports. two on board and one for your modem.
one way to find wich ports are detect is listing /proc/ioports
3f8 states as ttyS0
2f8 ttyS1
3e8 ttyS2
238 ttyS3
that is, if you stick with the normal settings in /etc/serial.conf
You can
D. Hoyem [EMAIL PROTECTED] writes:
Did you also get the 2.4.? ppp? That is required when
you upgrade to a 2.4.* kernel. You can also try
setserial -g /dev/ttyS* and see what is listed as the
modem. It should be listed as UART 16550A if memory
serves me right.
Don
Okay... here's the nitty
Dang it all... I went and forgot my Radeon sidenote. Anyway, I was wondering
if anyone has gotten the ATI Radeon VE video card (AGP) working with X.
(preferably 4.0.3). Anytime I try to use it, I get broken server connection
messages. Any suggestions?
TIA,
Jeremy
I recently purchased a USR internal 56k PCI modem (model 3CP5610A), but
I've had no luck getting it working on my woody box. In the
instructions in the box, it tells me that to get it working with linux,
I need kernel 2.3 or above. Good time to upgrade! I thought, and I
went for the 2.4.6
- Original Message -
From: Jeremy [EMAIL PROTECTED]
To: Debian List debian-user@lists.debian.org
Sent: Monday, July 09, 2001 12:10 PM
Subject: USR modem problems
I recently purchased a USR internal 56k PCI modem (model 3CP5610A), but
I've had no luck getting it working on my woody box
I forwarded this installation instruction for a PCI modem:
quote
IV. To set Linux to configure the modem upon boot-up.
There are several options. One method is going to the /etc/rc.d/
directory, and using an editing program such as jed edit the
rc.local file, and insert
- Original Message -
From: Mark Garland [EMAIL PROTECTED]
To: Debian List debian-user@lists.debian.org
Sent: Monday, July 09, 2001 7:34 PM
Subject: Re: USR modem problems
I forwarded this installation instruction for a PCI modem:
quote
IV. To set Linux to configure the modem upon
i would just use apt-get install dhcp-client also check out the dhcp
client setup at http://home.cfl.rr.com/aawtrey/ he has laid out a nice
howto.begin:vcard
n:Bardin;Jon
x-mozilla-html:FALSE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
note:www.gamesig.com -uniting the linux gaming
Greetings,
I am using road runner for cable modem service. I am using pump for my
dhcp client ob a potato box (Pentium 233MMX -- 16MB RAM). The cable modem
I've got is a SURFboard 2100. My problem is that occasionally that my cable
modem will lock up -- The activity LED will light up
Leonardo Stern writes:
I tried pppconfig too : with windows configurations or non /dev/ttyS1
^^ ^^
??
with /dev/ttyS1 IRQ X (x = 3,4,5,6,7) the modem don't respond to pon
Does the modem respond to minicom?
--
John Hasler
I tried pppconfig too : with windows configurations or non /dev/ttyS1
^^ ^^
??
I mean I tried the modem configurations used in windows and all other 3
ports ... (even ttyS0 , used by my mouse). With ttyS0, ttyS2 and ttyS3
I also did :
pnpdump test.txt
isapnp test.txt
.. found 3 devices (the modem too) .. now what ?
(also tried pnpdump then setting a com port with the values from
pnpdump)
Are you sure this isn't a winmodem?
I don't think .. its supposed to run on DOS 6.0
On Tue, 04 Jul 2000, Leonardo Stern
On Tue, Jul 04, 2000 at 09:22:20PM -0300, Leonardo Stern wrote:
I also did :
pnpdump test.txt
isapnp test.txt
.. found 3 devices (the modem too) .. now what ?
(also tried pnpdump then setting a com port with the values from
pnpdump)
If I remember correctly, wvdial has a configure file
*** on bottom ***
I also did :
pnpdump test.txt
isapnp test.txt
.. found 3 devices (the modem too) .. now what ?
(also tried pnpdump then setting a com port with the values from
pnpdump)
If I remember correctly, wvdial has a configure file that tells it
which ttyS? to use. Did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[EMAIL PROTECTED] writes:
Has anyone experienced the problem where uucp system produces Low Level
Protocol (LLP) errors?
I've never had any problems with UUCP. I must admit to being fairly new
to it though. What protocol are you using? Is
Hi all
Has anyone experienced the problem where uucp system produces Low Level
Protocol (LLP) errors?
ie. our system uploads hl7files to a mailbox via uucp... when i dial up
the mailbox and download the hl7 files (emulating a doctors practice) i get
a random amount of LLP/CRC errors. But most
Your serial port that your modem uses is probable using an IRQ greater
than 4. If so, Linux won't detect the serial port. You have to tell
Linux that the serial port is using IRQ n. Check in windows first:
find out which COM your modem is in. Then check which IRQ this COM is
usin:
control
Hi
I hope someone can help me with this.
I loaded the Debian base on my laptop, hoping to get the rest of the
packages off the net using dselect.
At first I thought that I had a problem using pppconfig, so I got Minicom
and wvdial and found that after issuing ATZ to the modem that the modem
On Tue, Aug 10, 1999 at 11:13:46AM +0100, Thys van der Merwe wrote:
Hi
I hope someone can help me with this.
I loaded the Debian base on my laptop, hoping to get the rest of the
packages off the net using dselect.
At first I thought that I had a problem using pppconfig, so I got Minicom
On Wed, Jul 21, 1999 at 02:11:52AM -0600, David Karlin wrote:
Is there an advantange to using isapnptools over disabling PNP?
1. It's easier to change your settings later on. For example, lets say you
used IRQ 7 for your modem because your printer doesn't need it's IRQ anyway
but later you
On Wed, Jul 21, 1999 at 10:07:45AM -0500, John Hasler wrote:
David Karlin writes:
Is there an advantange to using isapnptools over disabling PNP?
Quite the contrary. PNP is best avoided even in Windows.
The problem is that Windows insists on re-detecting everything every time
you re-boot
On Wed, 21 Jul 1999, David Karlin wrote:
Out of curiousity, did you properly set up the modem with isapnptools,
and
then use setserial to set the irq, port, and everything?
Nope. I disabled PNP and set everything with the jumpers as described
in appendix A of the manual.
To: Julian Gilbey
Cc: debian-user@lists.debian.org
Subject: Re: SupraExpress Modem problems
Julian writes:
- the /var/log/ppp.log file showed that the intial connection had
been attempted, and that after precisely 45 seconds, an alarm
happened and the connection attempt failed
On Tue, 20 Jul 1999, David Karlin wrote:
As I said in an earlier post, I installed one of these modems in a
slink box last evening. I think I remember a similar plog entry before
I disabled the pnp and set the irq and com port with the jumpers.
Out of curiousity, did you properly set up the
I disabled the pnp and set the irq and com port with the jumpers.
Out of curiousity, did you properly set up the modem with isapnptools, and
then use setserial to set the irq, port, and everything?
Nope. I disabled PNP and set everything with the jumpers as described
in appendix A of the
David Karlin writes:
Is there an advantange to using isapnptools over disabling PNP?
Quite the contrary. PNP is best avoided even in Windows.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On Wed, 21 Jul 1999, David Karlin wrote:
I disabled the pnp and set the irq and com port with the jumpers.
Out of curiousity, did you properly set up the modem with isapnptools, and
then use setserial to set the irq, port, and everything?
Nope. I disabled PNP and set everything with
Out of curiousity, did you properly set up the modem with isapnptools, and
then use setserial to set the irq, port, and everything?
Nope. I disabled PNP and set everything with the jumpers as described
in appendix A of the manual. This seems to have worked fine. Is there
an
[Please Cc: me in replies.]
I have just tried setting up a Debian system for someone, and have
been unable to get his modem to work. The details are:
- fresh slink (Debian 2.1) installation from the official CDs on a
Pentium.
- Windows reports the modem to be a SupraExpress 56i Sp Intl
-
On 20-Jul-99 Julian Gilbey wrote:
[Please Cc: me in replies.]
I have just tried setting up a Debian system for someone, and have
been unable to get his modem to work. The details are:
- fresh slink (Debian 2.1) installation from the official CDs on a
Pentium.
- Windows reports the
Julian,
I just installed a Diamond Supra Express in a slink box this
evening.
The first thing I did was disable PNP and set the com port
and irq via the jumpers (see Appendix A of the Supra Express
Getting Started Manual).
I was lucky that I knew the com port and irq settings of the
old modem;
Julian writes:
- the /var/log/ppp.log file showed that the intial connection had
been attempted, and that after precisely 45 seconds, an alarm
happened and the connection attempt failed. Nothing happened
between the expect OK and the alarm lines in the log.
Sounds like the modem did
This is the init string I use for my SupraExpress external modem
from /etc/diald/connect:
MODEM_INIT=ATF2C1D2K3M0
Some Supra modems use F2 instead of F
--
Andrew
Interesting little problem here. I have two machines, one at work, one at
home, both running slink.
As far as I know, both systems are running the same package versions for
everything installed (Synced from Slink CD and www.us.debian.org using
APT) and both have kernel 2.2.2 from
Ok, got my new debian system up and running at work (yahoo!!), now i'm
trying to do the same at home. Everything seems to have installed
properly, but i can't get my modem to respond. I tried a cat /dev/
ttyS1 atdt## to see if i could get a response, and nothing. I'm sure
that the modem is on
On Thu, Dec 31, 1998 at 11:33:08AM -0600, Brent Hueth wrote:
Ok, got my new debian system up and running at work (yahoo!!), now i'm
trying to do the same at home. Everything seems to have installed
properly, but i can't get my modem to respond. I tried a cat /dev/
ttyS1 atdt## to see if i
On Sun, 27 Sep 1998, Tracheotomy Bob wrote:
I am damned if I can get my modem to work under linux. Here's the
general situation.
From your symptoms, it seems *very* doubtful that it's a Winmodem, but
*just* for the sake of paranoia, are you sure it's not? Does it work under
DOS?
Poking
I am damned if I can get my modem to work under linux. Here's the
general situation.
While I installed from the floppies and selected to do an ftp install,
the modem seemed to work. I say seemed because I was having problems
with it under Windows 98 that have now been resolved. However on the
I have just upgraded from bo to hamm (which was quite a task -- I put
in the wrong directory structure into dpkg-ftp and it completely
corrupted my status file -- thank Gd for backups...).
I've now updated all my packages to the versions in the stable hamm
release, and have recompiled my kernel
Just a little more info on this one: I have compiled all of the
requisite parts of the kernel, and I even compiled them in directly
rather than as modules, as I thought that might be part of the
problem.
I have just upgraded from bo to hamm (which was quite a task -- I put
in the wrong
I tried to connect a 33600 modem to my system.
This is a deferent computer then the one the hardisk usually runs on
if that changes anything (on the regular computer there is a 14400
modem which works fine)
I tried to set up using pppconfig.
when i start pon i get a response (in plog)
pppd 2.3.3
1) Is the modem plug and play, and if so, are you using isapnp?
2) What version of Debian are you using?
If you are using hamm you should be able to allow normal users to use
dial-up services by adding them to group dip. This probably holds true in
bo also, but I'm not sure (I had to change some
The log files could help you tracking the problem.
Perhaps sending the relevant parts to the list might also help.
When connecting to the internet via pppd, my connection is
VERY slow, i average 400bytes/sec, ping time to my isp is
...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
I have now my Zyxel Omni.net plus ISDN modem up and running. The
crucial informaton seemed to have comed from the Serial-programing
HOWTO and involves IRQ priorities. Enabling `irqtune' in
/etc/rc.boot/hwtools seems to have done the trick.
When connecting to the internet via pppd, my connection is
VERY slow, i average 400bytes/sec, ping time to my isp is
~.500ms. I am using an ACER 28.8 and the modem worked
speedily in windows, but ever since the crossover to linux
i have been plagued by this annoying problem, if anyone
has had
On Sat, Apr 25, 1998 at 12:13:42AM -0400, Brent Wooden wrote:
When connecting to the internet via pppd, my connection is
VERY slow, i average 400bytes/sec, ping time to my isp is
~.500ms. I am using an ACER 28.8 and the modem worked
speedily in windows, but ever since the crossover to
Jens == Jens B Jorgensen [EMAIL PROTECTED] writes:
Jens I use a Zyxel OMNI TA 128U (almost the exact same beast) with a single 64K
Jens channel. It has no problems. My server machine is a P90 overclocked to
100 with
Jens 40MB of memory. Perhaps you're getting buffer overruns on your serial
I use a Zyxel OMNI TA 128U (almost the exact same beast) with a single 64K
channel. It has no problems. My server machine is a P90 overclocked to 100 with
40MB of memory. Perhaps you're getting buffer overruns on your serial port. What
baud rate are you running your serial port at?
Christian
I have just got myself an ISDN line and a Zyxel Omni.net plus modem,
but I have problems in getting it to work smoothly.
The problem is that I keep getting error messages saying something to
the effect of:
ppp: frame with bad fcs, excess = 4de9
The more trafic (for instance with ping) I
Is there a neat utility to display what things are using what IRQs?
Does not
cat /proc/interrupts
be of some help ?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
I was trying to setup debian on another computer:
The serial module only detects /dev/ttyS1.
Is the modem on differenet tty ? Perhaps it is a PNP modem ?
I tried to get minicom to dial out on /dev/ttyS1, but it doesnt seem to
initialize it, and the modem doesn't make any noise when I try to
Is there a neat utility to display what things are using what IRQs?
Thanks,
Timothy
Sounds like you have an IRQ conflict. Read the 'dmesg' output and see
exactly what interrupt the serial port is on, and make sure it's not
the same interrupt as another card.
--
TO UNSUBSCRIBE FROM
On Tue, Feb 24, 1998 at 11:36:19PM +0400, Timothy M. Hospedales wrote:
Is there a neat utility to display what things are using what IRQs?
cat /proc/interrupts
Jeff
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL
On Tue, 24 Feb 1998, Timothy M. Hospedales wrote:
: Is there a neat utility to display what things are using what IRQs?
:
: Thanks,
: Timothy
cat /proc/interrupts
:
: Sounds like you have an IRQ conflict. Read the 'dmesg' output and see
: exactly what interrupt the serial port is on,
cat /proc/interrupts
bob
[EMAIL PROTECTED] writes:
Is there a neat utility to display what things are using what IRQs?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
I was trying to setup debian on another computer:
The serial module only detects /dev/ttyS1.
I tried to get minicom to dial out on /dev/ttyS1, but it doesnt seem to
initialize it, and the modem doesn't make any noise when I try to dial.
Any suggestions as to where I should go from here to try and
Timothy == Timothy M Hospedales [EMAIL PROTECTED] writes:
Timothy I was trying to setup debian on another computer: The
Timothy serial module only detects /dev/ttyS1. I tried to get
Timothy minicom to dial out on /dev/ttyS1, but it doesnt seem to
Timothy initialize it, and the
On Mon, 23 Feb 1998 13:16:47 +0400, Timothy M. Hospedales wrote:
I was trying to setup debian on another computer:
The serial module only detects /dev/ttyS1.
I tried to get minicom to dial out on /dev/ttyS1, but it doesnt seem to
initialize it, and the modem doesn't make any noise when I try
On Sat, Jan 03, 1998 at 01:58:10PM -0600, Mark W. Blunier wrote:
That seems odd. I thought that Linux would only set
tty00 and tty01 at bootup.
/etc/rc.boot/0setserial will only set up the first two ports,
because the ttyS2 and S3 have less standard locations (especially
IRQs), and also S3 and
Please help. I can't get my modem to work under linux, but it works
fine in NT. The settings in NT are:
IRQ 3 and IO 0x2e8 (COM4) .
When booting linux, it sees my serial ports at :
/dev/tty00 at 0x03f8 (irq = 4) is a 16550A
/dev/tty03 at 0x02e8 (irq = 3) is a 16550A
and after
In article [EMAIL PROTECTED],
Dennis Drapeau [EMAIL PROTECTED] wrote:
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
/dev/ttyS3 at 0x02e8 (irq = 3) is a 16550A
Seems ok to me, but I cannot dial out from port /dev/ttyS3.The group
on /dev/ttyS3 is dialout.
What do you mean with cannot dialout ?
On Sat, 3 Jan 1998, Dennis Drapeau wrote:
Please help. I can't get my modem to work under linux, but it works
fine in NT. The settings in NT are:
IRQ 3 and IO 0x2e8 (COM4) .
When booting linux, it sees my serial ports at :
/dev/tty00 at 0x03f8 (irq = 4) is a 16550A
/dev/tty03 at
hi again
when I run :
setserial -a /dev/ttyS3 I get:
/dev/ttyS3, Line 3, UART: 16550A, Port: 0x02e8, IRQ: 3
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000, closing_wait2: infinte
Flags: spd_vhi split_termios
On Sun, Oct 26, 1997 at 11:04:55PM +1300, Andrew J Tarr wrote:
On Fri, 24 Oct 1997, Jens B. Jorgensen wrote:
Andrew J Tarr wrote:
Struggling with my modem:
[SNIP]
Is your modem set for fixed serial speed (ATB1 on a sportster 28.8)?
No, it wasn't. Yes, it fixed it, thanks a
Andrew J Tarr [EMAIL PROTECTED] writes:
No, it wasn't. Yes, it fixed it, thanks a lot. I don't suppose anyone
wants to explain why it needs fixed serial speed?
Because there is very little Linux software that adjusts the TTY speed
according to what follows the CONNECT. I suspect that it
1 - 100 of 108 matches
Mail list logo
