[S.u.S.E. Linux] SMC9332 (Tulip) ethernet card
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 <A HREF="http://www.atic.umd.edu/~sina"><A HREF="http://www.atic.umd.edu/~sina</A">http://www.atic.umd.edu/~sina</A</A>> 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
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 <A HREF="http://www.atic.umd.edu/~sina"><A HREF="http://www.atic.umd.edu/~sina</A">http://www.atic.umd.edu/~sina</A</A>> 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
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
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. <BR>Hope it's just a matter of you being impatient. <BR>good luck Ramin Sina wrote: <BLOCKQUOTE TYPE=CITE>On Sat, 9 May 1998, Michael Lankton wrote:
<BR>> Start yast, goto integrate hardware into system, choose setup networking <BR>> device, and DECchip "tulip" PCI is listed. <BR>> eth0 is the device which linux will see it as, /dev/eth0 rather. <BR>> Great. Thanks. I also appreciate very much the responses I have got to my <BR>previous questions. Unfortunately Murphy's law has chosen me to prove its <BR>point. I try to start yast and it freezes. I get the message that yast is <BR>being started and the message does not go away. Does anyone know what <BR>might be causing that? Thanks again, <BR>Ramin -- <BR>To get out of this list, please send email to majordomo@suse.com with <BR>this text in its body: unsubscribe suse-linux-e</BLOCKQUOTE> <PRE>-- -----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------</PRE>
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. <BR>Hope it's just a matter of you being impatient. <BR>good luck Ramin Sina wrote: <BLOCKQUOTE TYPE=CITE>On Sat, 9 May 1998, Michael Lankton wrote:
<BR>> Start yast, goto integrate hardware into system, choose setup networking <BR>> device, and DECchip "tulip" PCI is listed. <BR>> eth0 is the device which linux will see it as, /dev/eth0 rather. <BR>> Great. Thanks. I also appreciate very much the responses I have got to my <BR>previous questions. Unfortunately Murphy's law has chosen me to prove its <BR>point. I try to start yast and it freezes. I get the message that yast is <BR>being started and the message does not go away. Does anyone know what <BR>might be causing that? Thanks again, <BR>Ramin -- <BR>To get out of this list, please send email to majordomo@suse.com with <BR>this text in its body: unsubscribe suse-linux-e</BLOCKQUOTE> <PRE>-- -----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------</PRE>
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 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
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
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
participants (3)
-
mantel＠suse.de -
satan＠nfinity.com -
sina＠Glue.umd.edu