From owner-freebsd-questions Sat Feb 8 22:21:30 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5467137B401 for ; Sat, 8 Feb 2003 22:21:29 -0800 (PST) Received: from mailhost.det3.ameritech.net (mailhost2-sfldmi.sfldmi.ameritech.net [206.141.193.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CC7043F3F for ; Sat, 8 Feb 2003 22:21:28 -0800 (PST) (envelope-from dbailey27@ameritech.net) Received: from ameritech.net ([67.38.16.140]) by mailhost.det3.ameritech.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20030209062105.OWSF20886.mailhost.det3.ameritech.net@ameritech.net>; Sun, 9 Feb 2003 01:21:05 -0500 Message-ID: <3E45F344.7070202@ameritech.net> Date: Sun, 09 Feb 2003 01:20:52 -0500 From: northern snowfall User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: Tom Vier Cc: freebsd-questions@FreeBSD.ORG Subject: Re: installer: / write failed device full References: <20030209060819.GA452@yzero> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > >well, i put my drive on the sym controller (since it's not seeing my aic7x >chips) and now when i starts downloading and extracting the binary sets it >stops and says there's no space. this is obviously wrong, since just before >that it does a newfs on an almost 9gig slice. > >has anyone else had this problem? this is on my alpha. > >also, only certain sites work from the installer. they work fine using >ncftp, but most others hang while "looking up...". > I've also had this problem. Instead of installing into the mounted target drive the installer attempts to fill up /, which is just mfs. I have newfs bug is, but, I've had the same occurance. However, it doesn't seem to *do* anything... As far as the "look up" hang: this occurs due to mishandled interrupts in the network controller. I don't think its driver specific. Once I installed a PCI device and configured the IRQ to use a non-shared interrupt, the installer was A-OK. I used a Kingston KNE111TX/100B. The base system is a 400mhz Xeon Intel CPU with 128MB RAM. ATA0.0 has a 6449 MB WD. ATA1.0 has a LITE-ON CD. The only other card on the motherboard is an Intel i740 AGP. The motherboard is an Intel 440BX AGPset GA-6BXC. Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message