As a current sufferer. Yes. Some hair has already been lost. Dave
On Mon, 2015-11-02 at 10:03 -0600, Tilghman Lesher wrote: > You really are campaigning to give Howard trichotillomania, aren't you? ;-) > > On Mon, Nov 2, 2015 at 9:53 AM, David R. Wilson <[email protected]> wrote: > > I saw it after the posting I made. I should have waited :-). > > That sounds like a similar problem. I didn't try moving this card to > > another slot, or reseating it yet. The RealTek on the motherboard > > worked fine, but the second card refused to and gave me errors. > > > > I was too lazy to go after the problem, so I ordered another card to > > avoid the hassle. This was one of the few times recently that I have > > seen such problems. > > > > If you need some more decrepit cards from last century guaranteed to > > give you gray hairs, don't hesitate to ask :-). > > > > Dave > > > > > > On Mon, 2015-11-02 at 09:08 -0600, Howard White wrote: > >> You have no doubt seen the play-by-play that followed my initial plaint. > >> Did the Intel card not play nice with the RealTek on the motherboard? > >> We didn't really go nuts to find out. The Intel card tried to work > >> but then didn't show up at all when I moved it to a different slot. > >> > >> It would help if most of my parts came from this century... > >> > >> Howard > >> > >> On 11/02/2015 08:52 AM, David R. Wilson wrote: > >> > It might not be the problem you are thinking it is. I found this > >> > weekend one of the network cards added to one of my boxes was not one > >> > that the tulip driver supported (at least not yet). It would not > >> > surprise me if it was a bad implementation that happened to be > >> > convenient to dump on ebay. > >> > > >> > I would see what routines are handling the networking. I have Centos > >> > running on a box with multiple addresses with no problem. From past > >> > experience I would look around to see what is mucking things up and > >> > disable that routine and write a shell script to set things up with > >> > static addresses if that is necessary. > >> > > >> > Sometimes the automatic screw up fairy works overtime. > >> > > >> > One thing you could do after both cards are active is to do an ifconfig > >> > and then look for errors in the list of cards. That will at least point > >> > you in the right direction. > >> > > >> > Dave > >> > > >> > On Sun, 2015-11-01 at 10:49 -0600, Howard White wrote: > >> >> Okay, I admit to being lazy. I am on the course of creating some tools > >> >> for phreakNIC next weekend. Like a fool, I have chosen to use CentOS 7 > >> >> as one platform in part as self-education. I am having to learn more > >> >> than I wish to just to accomplish simple things. > >> >> > >> >> Ergo - add a second NIC to CentOS 7 minimal. Server is going to provide > >> >> an Installfest private network with a firewall to the (gasp) phreakNIC > >> >> environment. Need two NICs. Have two NICs. lspci sees two NICs. May > >> >> I address two NICs with nmcli, nmtui or ifconfig (yes, I added the > >> >> net-tools package)??? Nooooooooo. > >> >> > >> >> Is my google-foo good enough to find an example? By my research, people > >> >> only run CentOS 7 in VMware or VirtualBox. Really? > >> >> > >> >> What gives? > >> >> > >> >> Howard > >> >> > >> >> -- > >> > > >> > > >> > >> -- > > > > > > -- > > -- > > You received this message because you are subscribed to the Google Groups > > "NLUG" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > > http://groups.google.com/group/nlug-talk?hl=en > > > > --- > > You received this message because you are subscribed to the Google Groups > > "NLUG" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Tilghman > > -- -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
