From sina@Glue.umd.edu Sun May 10 03:04:43 1998 From: sina@Glue.umd.edu To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] SMC9332 (Tulip) ethernet card Date: Sat, 09 May 1998 23:04:43 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5997424293547232190==" --===============5997424293547232190== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, I have updated my office machine from Red hat 4.2 to SuSE 5.2 and I've got to the following problem: While the driver for my SMC9332 ethernet card, also known as Tulip, was in the menu of the Red Hat installation and I had no problem configuring it, I can't find an entry for it in the SuSE Yast menu. Is There a way I can configure it manually? Also, what are these eth0, eth1, plip, etc options that are in the YaST menu? How do we know which one to chose?=20 Thanks, Ramin Sina -------------------------------------------------------- Ramin Sina =20 =20 Institute for Physical Science and Technology =20 University of Maryland College Park Maryland 20742 =20 email: sina@glue.umd.edu Voice (301) 405 4852 http://www.atic.umd.edu/~sina> Fax (301) 314 9363 -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============5997424293547232190==-- From satan@nfinity.com Sun May 10 04:16:04 1998 From: satan@nfinity.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] SMC9332 (Tulip) ethernet card Date: Sat, 09 May 1998 23:16:04 -0500 Message-ID: <35552A04.BAE358A5@nfinity.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8427595037549339542==" --===============8427595037549339542== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Start yast, goto integrate hardware into system, choose setup networking device, and DECchip "tulip" PCI is listed. eth0 is the device which linux will see it as, /dev/eth0 rather. Ramin Sina wrote: > Hi all, I have updated my office machine from Red hat 4.2 to SuSE 5.2 and > I've got to the following problem: While the driver for my SMC9332 > ethernet card, also known as Tulip, was in the menu of the Red Hat > installation and I had no problem configuring it, I can't find an entry > for it in the SuSE Yast menu. Is There a way I can configure it manually? > Also, what are these eth0, eth1, plip, etc options that are in the YaST > menu? How do we know which one to chose? > > Thanks, > Ramin Sina > > -------------------------------------------------------- > Ramin Sina > > Institute for Physical Science and Technology > University of Maryland College Park Maryland 20742 > email: sina@glue.umd.edu Voice (301) 405 4852 > http://www.atic.umd.edu/~sina> Fax (301) 314 9363 > > -- > 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 --===============8427595037549339542==-- From sina@Glue.umd.edu Sun May 10 15:17:53 1998 From: sina@Glue.umd.edu To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] SMC9332 (Tulip) ethernet card Date: Sun, 10 May 1998 11:17:53 -0400 Message-ID: In-Reply-To: <35552A04.BAE358A5@nfinity.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0976776049647395568==" --===============0976776049647395568== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Sat, 9 May 1998, Michael Lankton wrote: > > Start yast, goto integrate hardware into system, choose setup networking > device, and DECchip "tulip" PCI is listed. > eth0 is the device which linux will see it as, /dev/eth0 rather. > Great. Thanks. I also appreciate very much the responses I have got to my previous questions. Unfortunately Murphy's law has chosen me to prove its point. I try to start yast and it freezes. I get the message that yast is being started and the message does not go away. Does anyone know what might be causing that? Thanks again, Ramin -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0976776049647395568==-- From satan@nfinity.com Sun May 10 17:01:28 1998 From: satan@nfinity.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] SMC9332 (Tulip) ethernet card Date: Sun, 10 May 1998 12:01:28 -0500 Message-ID: <3555DD68.BF8E7525@nfinity.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8146574867709835774==" --===============8146574867709835774== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Yast takes a little while to start up on my p200mmx, so if you aren't giving it enough time it will appear to you that it locked up. If you are on anything slower than a p200 I imagine yast is a very slow starter.
Hope it's just a matter of you being impatient.
good luck Ramin Sina wrote:
On Sat, 9 May 1998, Michael Lankton wrote: >
> Start yast, goto integrate hardware into system, choose setup networking
> device, and DECchip "tulip" PCI is listed.
> eth0 is the device which linux will see it as, /dev/eth0 rather.
> Great. Thanks. I also appreciate very much the responses I have got to my
previous questions. Unfortunately Murphy's law has chosen me to prove its
point. I try to start yast and it freezes. I get the message that yast is
being started and the message does not go away. Does anyone know what
might be causing that? Thanks again,
Ramin --
To get out of this list, please send email to majordomo@suse.com with
this text in its body: unsubscribe suse-linux-e
-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d--- s++:++ a32 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 e h+ r* y+
------END GEEK CODE BLOCK------
--===============8146574867709835774==-- From sina@Glue.umd.edu Sun May 10 21:20:47 1998 From: sina@Glue.umd.edu To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] SMC9332 (Tulip) ethernet card Date: Sun, 10 May 1998 17:20:47 -0400 Message-ID: In-Reply-To: <3555DD68.BF8E7525@nfinity.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9111133941707648768==" --===============9111133941707648768== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Yast takes a little while to start up on my p200mmx, so if you aren't giving it enough time it will appear to you that it locked up. If you are on anything slower than a p200 I imagine yast is a very slow starter.
Hope it's just a matter of you being impatient.
good luck Ramin Sina wrote:
On Sat, 9 May 1998, Michael Lankton wrote: >
> Start yast, goto integrate hardware into system, choose setup networking
> device, and DECchip "tulip" PCI is listed.
> eth0 is the device which linux will see it as, /dev/eth0 rather.
> Great. Thanks. I also appreciate very much the responses I have got to my
previous questions. Unfortunately Murphy's law has chosen me to prove its
point. I try to start yast and it freezes. I get the message that yast is
being started and the message does not go away. Does anyone know what
might be causing that? Thanks again,
Ramin --
To get out of this list, please send email to majordomo@suse.com with
this text in its body: unsubscribe suse-linux-e
-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d--- s++:++ a32 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 e h+ r* y+
------END GEEK CODE BLOCK------
--===============9111133941707648768==-- From mantel@suse.de Mon May 11 10:32:24 1998 From: mantel@suse.de To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] Re: SMC9332 (Tulip) ethernet card Date: Mon, 11 May 1998 12:32:24 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0776800876882839263==" --===============0776800876882839263== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, On Sun, 10 May 1998, Ramin Sina wrote: > > Yast takes a little while to start up on my p200mmx, so if you aren't giv= ing > > it enough time it will appear to you that it locked up. If you are on > > anything slower than a p200 I imagine yast is a very slow starter. > > Hope it's just a matter of you being impatient. > > good luck >=20 > Hi Micheal. Sometimes Yast takes 10 seconds to startup; other times longer > than 5 minutes, at which time I kill the process. One of the things YaST does at startup is a "fdisk -l" to figure out the partition layout. On some machines, "fdisk -l" can hang sometimes if you have an EIDE CD-ROM drive and no CD in it. The problem normally is not reproducible. I suspect a kernel bug. > Ramin Hubert -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0776800876882839263==-- From sina@Glue.umd.edu Mon May 11 11:38:44 1998 From: sina@Glue.umd.edu To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] fdisk -l (was Re: SMC9332 (Tulip) ethernet card) Date: Mon, 11 May 1998 07:38:44 -0400 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5022546567763410606==" --===============5022546567763410606== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit > > One of the things YaST does at startup is a "fdisk -l" to figure out the > partition layout. On some machines, "fdisk -l" can hang sometimes if you > have an EIDE CD-ROM drive and no CD in it. The problem normally is not > reproducible. I suspect a kernel bug. > Thanks for this info. As a matter of fact when I do "ps", I sometimes see a "fdisk -l" entry with status job "D". Most of the time when I try to mount my zip disks, the process also hangs with status "D". I won't even get the prompt back. I am having these problems with my office machine which has two IDE hard disks. I have not had these problems yet with my computer at home (which has only one hard disk). Having said all these, is there a way to configure gateway and netmask addresses without using YaST. I think I might have entered wrong gateway address during installation. Thanks again, Ramin -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============5022546567763410606==--