Date: Sat, 4 Jun 2016 13:54:30 +0200 From: Michael Gmelin <freebsd@grem.de> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-current@freebsd.org Subject: Re: r300951: mountroot: waiting for device /dev/ad4s1a... Message-ID: <20160604135430.42e2f849@bsd64.grem.de> In-Reply-To: <20160604114852.GA5261@c720-r292778-amd64> References: <20160604101826.GA4660@c720-r292778-amd64> <20160604112806.GA5079@c720-r292778-amd64> <20160604134046.00fc182f@bsd64.grem.de> <20160604114852.GA5261@c720-r292778-amd64>
index | next in thread | previous in thread | raw e-mail
On Sat, 4 Jun 2016 13:48:52 +0200 Matthias Apitz <guru@unixarea.de> wrote: > Hi Michael, > > El día Saturday, June 04, 2016 a las 01:40:46PM +0200, Michael Gmelin > escribió: > > > Hi Matthias, > > > > Did you try to connect an external USB keyboard? > > no; it uses the laptop onboard keyboard; > > > i386 or amd64? > > i386; > > > Did you do a full clean build? > > GENERIC or custom kernel config? > > yes, clean 'make buildkernel KERNCONF=GENERIC' And then 'make installkernel KERNCONF=GENERIC' I suppose. > > interestingly: I can type at the prompt 'mountroot> ' into the dark > and always when I press Ctrl the chars are written to the screen and > so I can specify 'ufs:/dev/ad4s1a' which than leads to the same error > 19. Did you try ufs:/dev/ada0s1a? -m > > I can as well boot an USB key with the old kernel r269739, mount > /dev/ad4s1a to /mnt, all fine; I did even a fsck while booted from USB > on /dev/ad4s1a. The FS is clean. > > matthias > -- Michael Gmelinhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160604135430.42e2f849>