From owner-freebsd-current@freebsd.org Mon Mar 20 22:09:10 2017 Return-Path: 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 A6890D13DC1 for ; Mon, 20 Mar 2017 22:09:10 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (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 7F619175D for ; Mon, 20 Mar 2017 22:09:10 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0ON400200W1MRQ00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Mon, 20 Mar 2017 22:09:09 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1490047749; bh=R4mG0amDhOYhko/2szjD6PoOLmak7vdlRZcE95BSX34=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=dbRmxwPZxqN4/CyifcQif3EqGiYO1DaKT1ZSEeiHu334nHqAcUSA9FNmat9m4jlRF mIESQUFKlksFvf49N1AkDrfrIwQiXMGkzoq6XH6ey8EcNii2yx06BW3KaL1Ri/2zj2 tktt5NIXrPrAvTW4jJyDx0lyNcmTnriWybpjIEETMntFa52j0gwg2mn5t29R5E+UI9 fldi61g5BNISnS1Vcn2q+chZpyFFb/rYKxaaCM6crrpQQDjoP1HOUF9+FpP2ZAa56A azvsOXhfxfM6qqNe5H5GonhoBwdBHmyqYCP9t+KlODHJLeb/mbwbSeKpC/HYV38jh3 qCjQ/AK5YkqTQ== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0ON400BKWW760540@st13p35im-asmtp002.me.com>; Mon, 20 Mar 2017 22:09:08 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-20_16:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1703200188 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Are textmode consoles/terminals still supported? From: Toomas Soome In-reply-to: <05ff1f84a0f3856823fda4b08266f211@ultimatedns.net> Date: Tue, 21 Mar 2017 00:09:06 +0200 Cc: FreeBSD CURRENT Content-transfer-encoding: quoted-printable Message-id: References: <05ff1f84a0f3856823fda4b08266f211@ultimatedns.net> To: Chris H X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2017 22:09:10 -0000 > On 20. m=C3=A4rts 2017, at 23:58, Chris H = wrote: >=20 > I'm attempting to get a video card that DTRT on FreeBSD. > I started with the graphics provided by an AMD A6-7470K, > only to discover it's not yet supported. So I forked out > for a recent nvidia card, and build/installed a new > world/kernel. > Everything seemed to be as one would expect, except there > was an issue with loader.efi. So I had to move mine aside, > and use the one off the install media (tho I understand > the (u)efi has since been fixed). Now, I'm attempting to > obtain textmode. The text stripped from a tty, and pasted > to a new file in a textmode editor -- ee(1) for example; > pads the line with spaces to EOL, and prefaces each line > following the first line with rubbish (about 1 to 2 > characters worth). > So "graphics mode" or vt(4) isn't going to get it, for me. > Textmode, and syscons(4) has always worked as expected, and > I thought I'd try to re-enable it, or get textmode via vt(4). > But all attempts fail. > excerpt from my KERNCONF >=20 > device vga > options VESA >=20 > device sc > options SC_PIXEL_MODE >=20 > device vt > device vt_vga > device vt_efifb >=20 > However, following the advice on the freebsd wiki, querying > the value in sysctl(8) returns: > # sysctl hw.vga.textmode > sysctl: unknown oid 'hw.vga.textmode' >=20 > OK how bout vidcontrol(1) > # vidcontrol -i adapter > vidcontrol: obtaining adapter information: Inappropriate ioctl for = device >=20 > So, it appears from my standpoint that textmode is no longer > supported? >=20 > FWIW: > FreeBSD trump.whitehouse.gov.test 12.0-CURRENT FreeBSD 12.0-CURRENT #0 = r314700: > Sun Mar 5 09:01:30 PST 2017 > root@trump.whitehouse.gov.test:/usr/obj/usr/src/sys/TESTKERN amd6 >=20 > Thank you for anything that might help me obtain textmode again. >=20 > - The problem with UEFI is that the fact if you can only get =E2=80=9Ctext=E2= =80=9D aka VGA text mode if your card happens to have the proper = firmware and you can set up the card=E2=80=A6 UEFI as such does only = provide framebuffer based console, and that framebuffer is either linear = memory mapped or pure software - in last case only KMS console = framebuffer will do any good. rgds, toomas