From owner-freebsd-questions Wed Oct 23 12:33:36 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 04D6537B401 for ; Wed, 23 Oct 2002 12:33:34 -0700 (PDT) Received: from pgh.nepinc.com (pgh.nepinc.com [66.207.129.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5F1D43E3B for ; Wed, 23 Oct 2002 12:33:32 -0700 (PDT) (envelope-from durham@jcdurham.com) Received: from jimslaptop.pgh.nepinc.com (jimslaptop.pgh.nepinc.com [192.100.100.107]) by pgh.nepinc.com (8.11.4/8.11.3) with ESMTP id g9NJX9c53453; Wed, 23 Oct 2002 15:33:09 -0400 (EDT) (envelope-from durham@jcdurham.com) Content-Type: text/plain; charset="iso-8859-1" From: Jim Durham Reply-To: durham@jcdurham.com Organization: JC Durham Consulting To: "Jack L. Stone" Subject: Re: Oops! rc.conf mistake Date: Wed, 23 Oct 2002 15:33:03 -0400 User-Agent: KMail/1.4.2 Cc: "Roger 'Rocky' Vetterberg" , Steve Warwick , freebsd-questions@FreeBSD.ORG References: <3.0.5.32.20021023073055.00e357f8@mail.sage-one.net> <3.0.5.32.20021023102742.00e357f8@mail.sage-one.net> In-Reply-To: <3.0.5.32.20021023102742.00e357f8@mail.sage-one.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210231533.03905.durham@jcdurham.com> 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 On Wednesday 23 October 2002 11:27 am, Jack L. Stone wrote: > 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 mistak= e. > >>>> > >>>>I edited rc.conf to add a virtual interface and left a quote off th= e > >>>> end (unterminated string) - now I cannot get past mounting root, s= o no > > editors. > > >>>>And before you ask, no, I did not backup rc.conf... I told you it w= as > >>>>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..... > You bet! I originally made a mistake identifying the IDE connectors, and I put the hard drives on connector 2 and the CD on connector 1. I saw this when I ran sysintall, but I had put a zillion screws in the box and I said, "FreeBSD doesn't care...so I'll leave it" and I installed it that= way. Same message you got...ad4 limited to 33mhz, etc. So, I took the box apart, changed cables (although I already had 80 conductor cables on it) and tried various sysctl options. All no go. Finally, I thought since= I=20 had the box open now, I'd make the cables right and fix /etc/fstab. Voila! Now the drives report 133 on boot. Go figure... -Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message