Date: Wed, 29 Jan 1997 14:55:10 -0800 (PST) From: Dara Ghahremani <dara@salk.edu> To: Terry Lambert <terry@lambert.org> Cc: current@freebsd.org Subject: Re: installing network cards Message-ID: <Pine.SUN.3.95.970129143941.21571F-100000@helmholtz> In-Reply-To: <199701292112.OAA18568@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The machine is a Dell XPS P133c running AMIBIOS A02 with 64 MB RAM. It's running IDE w/ one disk. The dmesg scrolls too quickly off the screen for me to tell if it uses CMD640b IDE (neither "more" or any editor is installed on the local disk). I don't see any reference to the L1 or L2 cache in the BIOS setup. The machine gets to the point where it's pingable from another host and telneting works until after the password is entered. Then, the system doesn't respond to control-Cs as I described in a previous message. By the way, the machine works fine when I change to the previous 3COM 509 card so I believe there is something about this 3COM 595c card that is bringing about these problems. Perhaps the author of the vx0 driver for this card would know what's going on? Dara On Wed, 29 Jan 1997, Terry Lambert wrote: > > I apologize for not being more specific about this, I do get a keyboard > > response, but not a system response - i.e. control-D and C appear as ^C > > or ^D on the screen and no response returns other than the characters > > that appear on the screen. > > > > I will check on the SCSI situation that you wrote about now. > > It's possible that you have a bad chipset. What chipset do you have > (if you know) and do you have more than 16M of RAM? Also, if you > disable the L1 and L2 cache in the BIOS setup, does the problem go > away? Are you running IDE? If so, do you have a CMD640b IDE > controller chip and two or more disks? You need to provide more > specific information about the machine... if it is hanging where > ^C and ^D can't interrupt it, it may be that you are running a > shell which is trying to do a DNS lookup (and failing), in which > case it will eventually come back, OR it may be that your shell > image is being corruped as it is loaded into memory, either from > stale cache data because of your chipset, or even bad cache RAM > or main memory, OR the freeze-up is occuring in the disk driver > because of some hardware problem (like a CMD640b with two or more > devices on it or a WD IDE drive slaved to a non-WD IDE drive, etc.). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.95.970129143941.21571F-100000>