Date: Wed, 1 Nov 2017 18:37:13 +0100 (CET) From: "farrok@t-online.de" <farrok@t-online.de> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: system stuck on bios splash after reboot only Message-ID: <1509557833573.6010923.908b14ffced2e628dc55d89fb3fc9d56b6448c24@spica.telekom.de>
next in thread | raw e-mail | index | archive | help
Firstly, I couldn't find an answer for this specific problem, so I
apologize when this is a common problem.
Recently I installed FreeBSD again on a new laptop (Thinkpad T470
20HES2SF00). On my desktop, the OS runs without problems with Xorg.
I have chosen FreeBSD 12.0-CURRENT for that, because I need support for
the iwm 8265 device + kabylake support via drm-next-kmod.
Booting into the OS after the installation works (I use ZFS + GELI
encryption), but when I reboot via reboot(8)
<https://www.freebsd.org/cgi/man.cgi?query=3Dreboot&sektion=3D8&manpath=
=3Dfreebsd-release-ports>=20
or shutdown -r now I'm stuck on the BIOS splash screen.
Shutting down the computer and do a fresh boot works as expected, only
rebooting doesn't work. The OS before (void linux, and well the
preinstalled windows 10) didn't have that problem. Furthermore, the
reboot is stuck only when fully logged in on the system before,
rebooting from the FreeBSD bootloader works without problems.
FreeBSD 11.1-RELEASE is stuck on reboot too.
BIOS is version 1.30. Boot order is primary the SSD (I deactivated all
others to test) UEFI boot, tried with/-out secure boot and old bios
boot too.
Is this a known problem? How can i fix it? Or how can I debug the
problem, I would be thankful for some pointers.
FreeBSD is pretty new to me, using it for some month as a second system
on my desktop computer, but using GNU/Linux for over a decade and use
the terminal extensively, so I hope I'm not completely incapable to fix
the problem with some help!
Hope it was understandable and thanks in advance!
=20
=20
copy of https://forums.freebsd.org/threads/63050/
=EF=BB=BF
From owner-freebsd-current@freebsd.org Wed Nov 1 18:37:35 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAF74E620CD
for <freebsd-current@mailman.ysv.freebsd.org>;
Wed, 1 Nov 2017 18:37:35 +0000 (UTC) (envelope-from tsoome@me.com)
Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com
[17.164.199.64])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id C26787D24C
for <freebsd-current@freebsd.org>; Wed, 1 Nov 2017 18:37:35 +0000 (UTC)
(envelope-from tsoome@me.com)
Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by
st13p35im-asmtp001.me.com
(Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7
2017)) id <0OYR00H0051P9500@st13p35im-asmtp001.me.com> for
freebsd-current@freebsd.org; Wed, 01 Nov 2017 18:37:29 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017;
t=1509561449; bh=vaFacFOD47nZ6Gs1rq6XOICv7hNq8rOa07QyFa9P1mE=;
h=Content-type:MIME-version:Subject:From:Date:Message-id:To;
b=LfC61H8X7oebCVJb21nQoN/vM6w7aMy5aM0/rCp3AkxrUYzE5OzQ67ut0gLNbWNVW
KBNZKwGsPxLhdergJYDHRR5BZBCmzTmBD0HLfLIZN2mFx+MRR6UxR135DO0sFNtT+/
fKIq5x7rPeSp2poDZVCdfhRP8RJ+qufHHD6ysAQcEW9M1KhMFfB8vL1zEAwNudTuc0
UkYnH4NQOk4+K82GF40CivriSOboEaTiLHQdDLSpplReHCLZoJSwm2itJOKhpNPwbX
zK/JF4tYbJW6V5FBmJRgKrScG5eRZoSAfIXQSwAwiy4/ptT/J2BlAOd1lH51ZXTt5F
Qd0Jd+Gq/9g4w==
Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com
(Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7
2017)) with ESMTPSA id <0OYR00OON52E8220@st13p35im-asmtp001.me.com>; Wed,
01 Nov 2017 18:37:28 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,,
definitions=2017-11-01_05:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
clxscore=1011 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0
bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1
engine=8.0.1-1707230000 definitions=main-1711010244
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
Subject: Re: system stuck on bios splash after reboot only
From: Toomas Soome <tsoome@me.com>
X-Priority: 3
In-reply-to: <1509557833573.6010923.908b14ffced2e628dc55d89fb3fc9d56b6448c24@spica.telekom.de>
Date: Wed, 01 Nov 2017 20:37:25 +0200
Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Content-transfer-encoding: quoted-printable
Message-id: <FEB27CDB-2113-401E-8BF1-EE4094BC0BAA@me.com>
References: <1509557833573.6010923.908b14ffced2e628dc55d89fb3fc9d56b6448c24@spica.telekom.de>
To: "farrok@t-online.de" <farrok@t-online.de>
X-Mailer: Apple Mail (2.3445.1.7)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Nov 2017 18:37:36 -0000
> On 1 Nov 2017, at 19:37, farrok@t-online.de wrote:
>=20
> Firstly, I couldn't find an answer for this specific problem, so I
> apologize when this is a common problem.
>=20
> Recently I installed FreeBSD again on a new laptop (Thinkpad T470
> 20HES2SF00). On my desktop, the OS runs without problems with Xorg.
>=20
> I have chosen FreeBSD 12.0-CURRENT for that, because I need support =
for
> the iwm 8265 device + kabylake support via drm-next-kmod.
>=20
> Booting into the OS after the installation works (I use ZFS + GELI
> encryption), but when I reboot via reboot(8)
> =
<https://www.freebsd.org/cgi/man.cgi?query=3Dreboot&sektion=3D8&manpath=3D=
freebsd-release-ports>=20
> or shutdown -r now I'm stuck on the BIOS splash screen.
>=20
> Shutting down the computer and do a fresh boot works as expected, =
only
> rebooting doesn't work. The OS before (void linux, and well the
> preinstalled windows 10) didn't have that problem. Furthermore, the
> reboot is stuck only when fully logged in on the system before,
> rebooting from the FreeBSD bootloader works without problems.
>=20
> FreeBSD 11.1-RELEASE is stuck on reboot too.
>=20
> BIOS is version 1.30. Boot order is primary the SSD (I deactivated =
all
> others to test) UEFI boot, tried with/-out secure boot and old bios
> boot too.
>=20
> Is this a known problem? How can i fix it? Or how can I debug the
> problem, I would be thankful for some pointers.
>=20
> FreeBSD is pretty new to me, using it for some month as a second =
system
> on my desktop computer, but using GNU/Linux for over a decade and =
use
> the terminal extensively, so I hope I'm not completely incapable to =
fix
> the problem with some help!
>=20
> Hope it was understandable and thanks in advance!
>=20
>=20
>=20
> copy of https://forums.freebsd.org/threads/63050/
> =EF=BB=BF
This sounds like that system needs more serious resetting; The reboot =
from boot loader can work because boot loader does not really touch the =
hardware much - the boot loader only is using firmware services and =
those (probably) do not change the hardware state that much.
Still the first thing to check is the firmware/bios update=E2=80=A6.
rgds,
toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1509557833573.6010923.908b14ffced2e628dc55d89fb3fc9d56b6448c24>
