On Sat, Jun 23, 2001 at 11:42:19AM -0400, Aaron Traas wrote: | Overall, I love Debian as an OS. I've used it many times in a work | environment, and apt-get simply rules. However, I have yet to | successfully install Debian on one of my home machines. Here is the | situation: | | I have 5 different ethernet cards without a permanent home: 4 different | Tulip variants, and a Netgear FA311. I'm trying to get these to work on | Debian 2.2r2. I am unable to get 2.2r3 because A) my CDRW on my Windoze | box just died, and B) I can't get this machine to work with any ethernet | card I have, so installing over the network is not an option.
I'm curios as to the what your tulip variants are. I have heard some mention on this list that the tulip driver with kernel 2.2 (or maybe it was just with potato) doesn't work. I, OTOH, have a tulip card and have never had problems (starting with RH5.2, kernel 2.0.36). My card is a LinkSys LNE100TX rev 2.0 (Lite-On made the actual tulip chip). I don't remember where, but there was somewhere that one could get a different version of the tulip driver that was supposed to work fine. Another possibility would be to buy 1 more NIC that is know for sure to work and upgrade to woody from that. Some NICs can be bought for about $15. The Netgear, Linksys, and DLink ISA cards all work (NE2000 clones). I think the model for the netgear is FA310 or maybe FA312 (I have 2 of them in 486 boxes and they are fine -- just boot to DOS first to disable PnP). | insmod tulip | ifconfig eth0 inet 10.1.1.50 netmask 255.255.255.0 broadcast 10.1.1.255 | ifconfig eth0 up | ping 10.1.1.1 | | And everything worked fine! It was great! So I decided to re-install the | system, and configure everything I wanted. If this works fine, why re-install? Just store the settings in /etc/interfaces and /etc/modutils/aliases. If this works you could start the network connection manually, then use apt to upgrade to woody over the network. HTH, -D
