From owner-freebsd-questions Wed Oct 23 8: 9:39 2002 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 80DC937B401 for ; Wed, 23 Oct 2002 08:09:37 -0700 (PDT) Received: from w2xo.jcdurham.com (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB2E043E42 for ; Wed, 23 Oct 2002 08:09:36 -0700 (PDT) (envelope-from durham@jcdurham.com) Received: from jcdurham.com (pgh.nepinc.com [66.207.129.50]) by w2xo.jcdurham.com (8.11.6/8.11.6) with ESMTP id g9NF9Go74016; Wed, 23 Oct 2002 15:09:16 GMT (envelope-from durham@jcdurham.com) Message-ID: <3DB6BB9B.7020702@jcdurham.com> Date: Wed, 23 Oct 2002 11:09:15 -0400 From: Jim Durham User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc3) Gecko/20020811 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jack L. Stone" Cc: "Roger 'Rocky' Vetterberg" , Steve Warwick , freebsd-questions@FreeBSD.ORG Subject: Re: Oops! rc.conf mistake References: <3.0.5.32.20021023073055.00e357f8@mail.sage-one.net> 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 Jack L. Stone wrote: > At 09:28 AM 10.23.2002 +0200, Roger 'Rocky' Vetterberg wrote: > >>Steve Warwick wrote: >> >>>Hey all, >>> >>>I wonder if anyone can tell me how to get out of this stupid mistake. >>> >>>I edited rc.conf to add a virtual interface and left a quote off the end >>>(unterminated string) - now I cannot get past mounting root, so no editors. >>>And before you ask, no, I did not backup rc.conf... I told you it was >>>stupid. >>> >>>BTW: I noticed that ad0 is "limited to UDMA33" - I have UDMA133 motherboard >>>and drive so, I this really true? >>> >>> >>>TIA, >>> >>>Steve >>> >> >>Since other have answered the rc.conf question, I give the "limited to >>UDMA33" a shot. >>Are you using a UDMA133 cable? I cant recall the UDMA133 specs, but I >>know UDMA66 and 100 use a different cable then UDMA33. UDMA133 might >>use the same cable as 66 and 100, but Im certain a 33 cable would >>force the drive to be UDMA33 only, even if both drive and controller >>is capable of UDMA133. >>It might also be a BIOS issue, check your settings. >> >>-- >>R >> > > > I have noticed that some CD-ROM drives will make the system think it is on > a non-compliant cable or UDMA33. For instance, this from dmesg on one > machine with an older CD_ROM drive. > > "ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable" If I change > to a newer CD player, it's okay. > > Best regards, > Jack L. Stone, > Administrator > > SageOne Net > http://www.sage-one.net > jackstone@sage-one.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message This may sound wierd, but I had this problem when I had the hard drives on the 2nd IDE interface and the CD on the 1st IDE interface. Reversing the cables and changing /etc/fstab fixed the problem. This was on an A-Open motherboard. -Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message