From owner-freebsd-current Sat Nov 20 0:28:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id BB64214DF5 for ; Sat, 20 Nov 1999 00:28:22 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup5-52.iptelecom.net.ua [212.9.227.52]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA05077; Sat, 20 Nov 1999 10:32:18 +0200 (EET) Message-ID: <38365B59.3D5B2725@altavista.net> Date: Sat, 20 Nov 1999 10:27:05 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Mike Smith Cc: S ren Schmidt , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: NewATA on ISA and PCI References: <199911191842.KAA00694@dingo.cdrom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > > Does anybody can explain why kernel with NewATA driver booted on machine > > > > > with ISA based IDE adapter trying to mount wd* as root f/s, while > > > > > exactly *the same* kernel booted on PCI based mobo mounts ad* as root? > > > > > > > > /etc/fstab ? > > > > > > No, I do not talking about /etc/fstab, I'm talking about what device kernel is > > > using to mount root *before* starting /sbin/init (e.g. "changing root device to > > > ..." in dmesg). > > > > Hmm, the bootblock or the loader might be responsible.... > > This is -current. If the message is "changing root device to..." you > are out of date and must update before we can help you. > > The root mount code has changed quite a lot just recently, and > debugging the 'old' code isn't practical anymore. You are not right - I'm usually rebuilding kernel in one-three days, and world in a week. My current kernel built from sources sup'ed (cvsup.freebsd.org) yesterday. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message