From ckemp@spcbrass.com Thu Apr 23 18:21:35 1998 From: ckemp@spcbrass.com To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Thu, 23 Apr 1998 13:21:35 -0500 Message-ID: <353F8697.41DD000F@spcbrass.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3103424408898431379==" --===============3103424408898431379== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hello list, I'm installing an internal US Robotics Modem as Com3, with an IRQ of 5. Do I have to make a new device file for this capability?? If so how? Thanks Curt -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============3103424408898431379==-- From jpcowh01@ox.slug.louisville.edu Thu Apr 23 20:00:49 1998 From: jpcowh01@ox.slug.louisville.edu To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Thu, 23 Apr 1998 16:00:49 -0400 Message-ID: <199804232000.QAA02749@rabbit.slug.louisville.edu> In-Reply-To: <353F8697.41DD000F@spcbrass.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3007200336294427483==" --===============3007200336294427483== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable >=20 > Hello list, >=20 > I'm installing an internal US Robotics Modem as Com3, with an IRQ of 5. >=20 > Do I have to make a new device file for this capability?? If so how? >=20 > Thanks >=20 > Curt >=20 the device name of com3 is /dev/cua2 ... (check your motherboard man= ual for the which irqs are for which com ports) =20 Jonathan --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Jonathan Paul Cowherd jpcowh01@slug.louisville.edu http://www.slug.louisville.= edu/~jpcowh01> This is my world and I am... World Leader Pretend =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============3007200336294427483==-- From vhearn@wenet.net Thu Apr 23 21:51:31 1998 From: vhearn@wenet.net To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] an internal Modem as Com3 Date: Thu, 23 Apr 1998 14:51:31 -0700 Message-ID: <353FB7E3.A67832C9@wenet.net> In-Reply-To: <353F8697.41DD000F@spcbrass.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1306925157383968309==" --===============1306925157383968309== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit wow...i reinstallled everything....NOW howdo i run audio CD from x window???? Curt Kemp wrote: > Hello list, > > I'm installing an internal US Robotics Modem as Com3, with an IRQ of 5. > > Do I have to make a new device file for this capability?? If so how? > > Thanks > > Curt > > -- > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============1306925157383968309==-- From hongfeng@public.wh.hb.cn Thu Apr 23 22:42:16 1998 From: hongfeng@public.wh.hb.cn To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] an internal Modem as Com3 Date: Fri, 24 Apr 1998 06:42:16 +0800 Message-ID: <353FC3C8.39C4DEB0@public.wh.hb.cn> In-Reply-To: <353FB7E3.A67832C9@wenet.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1464010765142474346==" --===============1464010765142474346== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable you can read "Linux Multimedia Guide" by Jeff Tranter from O'Reilly
(http://www.oreilly.com>) for details. Rgds,
Frederic vic дµ½£º
wow...i reinstallled everything....NOW howdo i run audio CD from x
window???? Curt Kemp wrote: > Hello list,
>
> I'm installing an internal US Robotics Modem as Com3, with an IRQ of 5.
>
> Do I have to make a new device file for this capability?? If so how?
>
> Thanks
>
> Curt
>
> --
> To get out of this list, please send email to majordomo@suse.com with
> this text in its body: unsubscribe suse-linux-e --
To get out of this list, please send email to majordomo@suse.com with
this text in its body: unsubscribe suse-linux-e
=20 --===============1464010765142474346==-- From adavis@hayson.vmarketing.com Fri Apr 24 03:31:51 1998 From: adavis@hayson.vmarketing.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Thu, 23 Apr 1998 23:31:51 -0400 Message-ID: <19980423233151.A9480@Hayson.vmarketing.com> In-Reply-To: <199804232000.QAA02749@rabbit.slug.louisville.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0304399043624886463==" --===============0304399043624886463== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thu, Apr 23, 1998 at 04:00:49PM -0400, World Leader Pretend wrote: > > Hello list, > > I'm installing an internal US Robotics Modem as Com3, with an IRQ of 5. > > Do I have to make a new device file for this capability?? If so how? >=20 > the device name of com3 is /dev/cua2 ... (check your motherboard manual f= or the which irqs are for which com ports) =20 Not trying to be picky about right answers but try and get away from the=20 /dev/cu* devices, they are going away in favor of /dev/ttyS*=20 com3 <=3D> /dev/ttyS2=20 =20 --=20 Andrew L. Davis Network Operations adavis@vprlnk.net ViperLink International -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0304399043624886463==-- From lach@lach.net Fri Apr 24 15:13:14 1998 From: lach@lach.net To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Fri, 24 Apr 1998 10:13:14 -0500 Message-ID: <3540AC0A.35DDC164@lach.net> In-Reply-To: <19980423233151.A9480@Hayson.vmarketing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4272139536098421832==" --===============4272139536098421832== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Andrew L. Davis wrote: > On Thu, Apr 23, 1998 at 04:00:49PM -0400, World Leader Pretend wrote: > > > Hello list, > > > I'm installing an internal US Robotics Modem as Com3, with an IRQ of 5. > > > Do I have to make a new device file for this capability?? If so how? > > > > the device name of com3 is /dev/cua2 ... (check your motherboard m= anual for the which irqs are for which com ports) > > Not trying to be picky about right answers but try and get away from the > /dev/cu* devices, they are going away in favor of /dev/ttyS* > > com3 <=3D> /dev/ttyS2 > com3 ... Be it /dev/ttyS2 or /dev/cua2 aren't those devices wired for IRQ 4 ?= ?? What about the IRQ 5 requirement or is that automatic?? Lach PS I just installed 5.2, very nice, and KDE is coming along, life is good!! -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============4272139536098421832==-- From adavis@hayson.vmarketing.com Fri Apr 24 22:05:25 1998 From: adavis@hayson.vmarketing.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Fri, 24 Apr 1998 18:05:25 -0400 Message-ID: <19980424180525.A730@Hayson.vmarketing.com> In-Reply-To: <3540AC0A.35DDC164@lach.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5963327058506033782==" --===============5963327058506033782== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 24, 1998 at 10:13:14AM -0500, Lachlan Dunlop wrote: > com3 ... Be it /dev/ttyS2 or /dev/cua2 aren't those devices wired for IRQ 4= ??? What about the IRQ 5 requirement or is that > automatic?? You can set the value in the bios, there is a limited selection. --=20 Andrew L. Davis Network Operations adavis@vprlnk.net ViperLink International -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============5963327058506033782==-- From lach@lach.net Sat Apr 25 12:36:34 1998 From: lach@lach.net To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Sat, 25 Apr 1998 13:36:34 +0100 Message-ID: <3541D8D2.9865E0D1@lach.net> In-Reply-To: <19980424180525.A730@Hayson.vmarketing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8648676395786156862==" --===============8648676395786156862== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Andrew, I guess you missed my point. If Curt has an internal modem set for Com3, IRQ = 5. It has nothing to do with the bios in the PC weather linux will see the modem when you use the device /dev/ttyS2. I'm pre= tty sure /dev/ttyS2 is looking at the same I/O location but it is looking on IRQ 4, not IRQ 5. Later Lach Andrew L. Davis wrote: > On Fri, Apr 24, 1998 at 10:13:14AM -0500, Lachlan Dunlop wrote: > > com3 ... Be it /dev/ttyS2 or /dev/cua2 aren't those devices wired for IRQ= 4 ??? What about the IRQ 5 requirement or is that > > automatic?? > > You can set the value in the bios, there is a limited selection. > > -- > Andrew L. Davis Network Operations > adavis@vprlnk.net ViperLink International > -- > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============8648676395786156862==-- From lach@lach.net Mon Apr 27 13:18:48 1998 From: lach@lach.net To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Mon, 27 Apr 1998 14:18:48 +0100 Message-ID: <354485B8.970C51A7@lach.net> In-Reply-To: <3540AC0A.35DDC164@lach.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2405141148452819004==" --===============2405141148452819004== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Andrew, I guess you missed my point. If Curt has an internal modem set for Com3, IRQ = 5. It has nothing to do with the bios in the PC weather linux will see the modem when you use the device /dev/ttyS2. I'm pre= tty sure /dev/ttyS2 is looking at the same I/O location but it is looking on IRQ 4, not IRQ 5. Later Lach Andrew L. Davis wrote: > On Fri, Apr 24, 1998 at 10:13:14AM -0500, Lachlan Dunlop wrote: > > com3 ... Be it /dev/ttyS2 or /dev/cua2 aren't those devices wired for IRQ= 4 ??? What about the IRQ 5 requirement or is that > > automatic?? > > You can set the value in the bios, there is a limited selection. > > -- > Andrew L. Davis Network Operations > adavis@vprlnk.net ViperLink International > -- > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============2405141148452819004==-- From gecko@benham.net Mon Apr 27 16:26:43 1998 From: gecko@benham.net To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Mon, 27 Apr 1998 09:26:43 -0700 Message-ID: In-Reply-To: <354485B8.970C51A7@lach.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1024782156106384107==" --===============1024782156106384107== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Try looking in the file /sbin/init.d/serial. It's pretty well documented with TONS and TONS of samples. On 27-Apr-98 Lachlan Dunlop wrote: >=20 > Andrew, >=20 > I guess you missed my point. If Curt has an internal modem set for Com3, IRQ > 5. It has nothing to do with the bios in the PC > weather linux will see the modem when you use the device /dev/ttyS2. I'm > pretty sure /dev/ttyS2 is looking at the same I/O > location but it is looking on IRQ 4, not IRQ 5. >=20 > Later >=20 > Lach >=20 > Andrew L. Davis wrote: >=20 >> On Fri, Apr 24, 1998 at 10:13:14AM -0500, Lachlan Dunlop wrote: >> > com3 ... Be it /dev/ttyS2 or /dev/cua2 aren't those devices wired for IRQ >> > 4 ??? What about the IRQ 5 requirement or is that >> > automatic?? >> >> You can set the value in the bios, there is a limited selection. >> >> -- >> Andrew L. Davis Network Operations >> adavis@vprlnk.net ViperLink International >> -- >> To get out of this list, please send email to majordomo@suse.com with >> this text in its body: unsubscribe suse-linux-e >=20 >=20 >=20 >=20 > -- > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e ---------------------------------- http://homepages.skylink.net/~gec= ko/index.html> -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d+(-) s:+ a29 C++$ UL++>++++ P+++$ L++>++++ E? W+++$ N+(-) o? K- w+++$(--) O M-- V- PS-- PE++ Y++ PGP++ t+ 5 X R+ !tv b++++ DI+++ D++ G++>G+++ e h+ r* y+ ------END GEEK CODE BLOCK------ ---------------------------------- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============1024782156106384107==-- From adavis@hayson.vmarketing.com Mon Apr 27 20:24:45 1998 From: adavis@hayson.vmarketing.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Installing an internal Modem as Com3 Date: Mon, 27 Apr 1998 16:24:45 -0400 Message-ID: <19980427162445.A3295@Hayson.vmarketing.com> In-Reply-To: <3541D8D2.9865E0D1@lach.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3164474323949625446==" --===============3164474323949625446== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sat, Apr 25, 1998 at 01:36:34PM +0100, Lachlan Dunlop wrote: >=20 > Andrew, >=20 > I guess you missed my point. If Curt has an internal modem set for Com3, IR= Q 5. It has nothing to do with the bios in the PC > weather linux will see the modem when you use the device /dev/ttyS2. I'm p= retty sure /dev/ttyS2 is looking at the same I/O > location but it is looking on IRQ 4, not IRQ 5. If they are using com3 then IRQ 3 and IRQ 4 are already in use; to use the=20 other com ports they will have to use a different IRQ. To do this you need=20 to use setserial to change the IRQ number. --=20 Andrew L. Davis Network Operations adavis@vprlnk.net ViperLink International -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============3164474323949625446==--