From owner-freebsd-questions Wed Oct 23 8:27:58 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 ADEA237B401 for ; Wed, 23 Oct 2002 08:27:56 -0700 (PDT) Received: from sage-one.net (adsl-65-71-135-137.dsl.crchtx.swbell.net [65.71.135.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5318B43E65 for ; Wed, 23 Oct 2002 08:27:55 -0700 (PDT) (envelope-from jackstone@sage-one.net) Received: from sagea (sagea [192.168.0.3]) by sage-one.net (8.11.6/8.11.6) with SMTP id g9NFRfj03583; Wed, 23 Oct 2002 10:27:41 -0500 (CDT) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20021023102742.00e357f8@mail.sage-one.net> X-Sender: jackstone@mail.sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 23 Oct 2002 10:27:42 -0500 To: Jim Durham From: "Jack L. Stone" Subject: Re: Oops! rc.conf mistake Cc: "Roger 'Rocky' Vetterberg" , Steve Warwick , freebsd-questions@FreeBSD.ORG In-Reply-To: <3DB6BB9B.7020702@jcdurham.com> References: <3.0.5.32.20021023073055.00e357f8@mail.sage-one.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 At 11:09 AM 10.23.2002 -0400, Jim Durham wrote: >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 > That IS wierd! Usually the problem is limited to being on the same cable..... 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