From owner-freebsd-hackers Tue Nov 12 05:23:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA23072 for hackers-outgoing; Tue, 12 Nov 1996 05:23:13 -0800 (PST) Received: from home.winc.com (root@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA23051; Tue, 12 Nov 1996 05:22:52 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by home.winc.com (8.7.5/8.7.3) with SMTP id IAA08890; Tue, 12 Nov 1996 08:22:43 -0500 Message-ID: <32887A8B.2781E494@aristar.com> Date: Tue, 12 Nov 1996 08:24:27 -0500 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.01b1 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: hackers , FreeBSD Hardware group Subject: Dell laptop problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, all, Well, I *thought* I had this stupid machine working... When I boot the machine (2.1.5R) with the 3Com pc-card in it, these symptoms are a little less annoying, but they're still there: When I boot the machine, it runs SLOOOOOW (75Mhz Pentium). If I boot with -c, and then do 'vi' I get 'blocky' response: it does a few lines of text, waits for 60 seconds, does a little more, etc. If I do anything like press X to expand everything, I still wait. When I'm finally done, it hangs for about 3-4 minutes trying to find psm0, which I've configured correctly, I think. It finds all the devices, eventually. It also wants to hang on wd0 when it finds it. Finally, after init starts, I have to press Ctrl-C a few times to get it to finish the sequence of startups. When the system is all done booting, it seems to run fine when I login as root. Can anyone shed any light on what I might be doing wrong? Some of this behaviour is inconsistent: for example sometimes the CPU identification runs quickly (1-3 seconds), but other times it takes a couple of minutes. I'm guessing maybe something's wrong with the BIOS settings, but I would have no idea where to start. Thanks in advance, guys, Matt -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961