Re: Oops! rc.conf mistake
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 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 > >> [EMAIL PROTECTED] > >> > >> To Unsubscribe: send mail to [EMAIL PROTECTED] > >> 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 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 [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Oops! rc.conf mistake
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 >> [EMAIL PROTECTED] >> >> To Unsubscribe: send mail to [EMAIL PROTECTED] >> 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 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Oops! rc.conf mistake
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 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Oops! rc.conf mistake
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 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Oops! rc.conf mistake
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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Oops! rc.conf mistake
On 2002-10-22 00:21, Steve Warwick <[EMAIL PROTECTED]> wrote: > > 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. Please read: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RCCONF-READONLY If you still can't get past your problem, it is a problem of the documentation and I would be grateful if you kept notes during the recovery process and emailed your comments back to me or the [EMAIL PROTECTED] mailing list. -- [EMAIL PROTECTED] FreeBSD: The Power to Serve FreeBSD 5.0-CURRENT #14: Mon Oct 21 06:51:14 EEST 2002 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Oops! rc.conf mistake
On Tue, 2002-10-22 at 17:21, 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. Boot to single user: # mount -uw / # mount /usr # vi /etc/rc.conf This assumes you have access to the console :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Oops! rc.conf mistake
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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
