From owner-freebsd-current@freebsd.org Tue Jun 21 01:01:16 2016 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 BC546A7AC6D for ; Tue, 21 Jun 2016 01:01:16 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 840D7184D; Tue, 21 Jun 2016 01:01:16 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x234.google.com with SMTP id n127so3374734iof.3; Mon, 20 Jun 2016 18:01:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=pqH1lyTXiuGn/01Xo0ZjI94qZ1QWmm/MiNrOjwtsr2E=; b=Rjckyv/ERTsgWbiOGHNqVTq/oLZR9bZ8H7/PX6HfambsyumvHOKQwomoGFPDlrsMUO gIT9hnmxKt9B2Sq7i8XPiLyBeADheVKyyutaAQ5OYjmliQjb2WvozMFIYbg5ehmFnl6G /KarQQICsC4jIagtGafvN6z0sGtzFnyfNRsTGkIwAezL+g1gUXfMDMJqPoXa3prxqB6c YtFDMpqlaN0ocNDl387FfZe6U9/UoEiwCVjnhsQeSNS0r5DRvEyDnDRWhA1ck5T13J5j DTQaOV17C0ZCpUYNbzNG0NQCeVhCsVeCssIwAKnesqvMB6hb0sXWNpDLzd+KhY/fj5m9 B8iQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=pqH1lyTXiuGn/01Xo0ZjI94qZ1QWmm/MiNrOjwtsr2E=; b=NZxM58ZnwZm0kI/0dPRwcOq+3QFQrLaJs4dE+JLMpa2v76ii49SqSMbDW8wYAEH69J pmYsTAHLxDCJshafSOaggHqLmb9iD0MfE68Vn22A7kBWy0ZSbSdeLXm5OdyqjTNKa7/K kO74IKSyB+GoCoMlUE8h38J8b3v6Iy0yEfOT/c/fs7J6Uu/EIog+zTmhXA2qvkoTySYV jf7sLyPkEtO/wtkKwZ3oD4vDAydsHYsT4DZw4O5etQcy71XyrYBJqIEyOaVF65kXVSkV Lasl08TVFno0FMISj0qv7yNSML4og0edoz5naavXaU4/JbAfPtrygKsyFNIl6wdyawD5 HJKQ== X-Gm-Message-State: ALyK8tIS1rsbG2YVo03skly0f0Vc5Z5/ZuiogYPf5ERsGg1CcdhCZt4Na4I3q/HPEeDqxg== X-Received: by 10.107.26.76 with SMTP id a73mr1265544ioa.13.1466470875819; Mon, 20 Jun 2016 18:01:15 -0700 (PDT) Received: from [10.0.10.3] (cpe-184-56-210-236.neo.res.rr.com. [184.56.210.236]) by smtp.googlemail.com with ESMTPSA id o2sm164567ith.7.2016.06.20.18.01.14 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Jun 2016 18:01:15 -0700 (PDT) Message-ID: <576891F8.1010200@gmail.com> Date: Mon, 20 Jun 2016 21:01:44 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: John Baldwin CC: Ed Maste , =?ISO-8859-1?Q?Trond_Endrest=F8l?= , FreeBSD current Subject: Re: console in 11.0-ALPHA4 References: <57680D69.7030309@gmail.com> <576857F3.5040102@gmail.com> <31205295.d0H0JTrSWj@ralph.baldwin.cx> In-Reply-To: <31205295.d0H0JTrSWj@ralph.baldwin.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 21 Jun 2016 01:01:16 -0000 John Baldwin wrote: > On Monday, June 20, 2016 04:54:11 PM Ernie Luzar wrote: >> Ed Maste wrote: >>> On 20 June 2016 at 14:29, Ernie Luzar wrote: >>>> I found the cause of this boot time message >>>> "vicontrol: setting cursor type: Inappropriate ioctl for device" >>>> >>>> In my rc.conf I had this statement >>>> vidcontrol -c blink -h 250 >>>> From testing it seems that vt does not handle the "blink" option for causing >>>> the cursor to blink. Is there a vt option to enable cursor blinking >>> I've submitted two PRs for the issues you reported here: >>> Bug 210413 - vidcontrol -c does not work with vt(4) >>> Bug 210415 - vidcontrol -h does not work with vt(4) (edit) >>> >>> There is currently no option to enable cursor blinking. >> >> Further testing shows that: >> >> 1. The rc.conf option screen saver "saver= " and the "blanktime= " >> options work in vt for both text and graph modes. >> >> 2. The cursor copy/paste does not work in vt text mode. It only works in >> vt graph mode. vt needs to be fixed so copy/paste function also works in >> text mode. >> >> 3. Boot time splash screen does not work in vt at all no matter which >> mode is enabled. Using this in loader.conf >> splash_bmp_load="YES" >> bitmap_name="/boot/splash.bmp" >> bitload_load="YES" >> >> This works in 10.x. The splash screen function can not be allowed to be >> removed from the base system just because vt can not handle it. This >> also means any vt changes need to updated in the handbook section on >> splash screen. >> >> In conclusion, vt is not ready to replace the sc console driver yet. vt >> needs to be fixed before becoming the default in 11.0. Using vt as the >> default console driver effects every user. It completely changes the >> FreeBSD experience. It's detrimental to the public relations and the >> professional image of FreeBSD to publish the 11.0-RELEASE using vt in >> its current condition. If time doesn't permit to get these vt things >> fixed before publishing 11.0 then vt should not become the default >> console driver. > > OTOH, if you use EFI, then you can't use sc(4). You get no working console > with EFI (which is becoming more popular) if you use sc(4). You also do > not get non-ASCII characters with sc(4), so you don't have a UTF-8 capable > console if you use sc(4). You also do not have a working console after > loading the KMS drivers (either by starting X or via explicit kldload) when > using sc(4). This affects just about every modern Intel system using an > Intel GPU (so more widespread than EFI even). > > There are trade offs in both directions. Neither console is a subset of the > other. However, sc(4) is not really expendable to support the things it is > missing. vt(4) is actively worked on, and patches for the features it lacks > that you need are certainly welcomed. > This sounds like a integration design error. From your description of the hardware that vt is designed for and sc is designed for indicates the need for some code to be added to the boot process that inspects the hardware and decides whether vt or sc is to be launched. Or maybe bsdinstall should inspect the hardware and give the installer the option to select what console is best for his hardware. Just forcing this version of vt that lacks long time functions as the default console driver is not the professional way to handle such conflicts. I am at a lost to understand how any development administrator would approve making vt the default console driver in light of the standard functions missing from it. And furthermore what kind of vt testing was done that these problems were missed. Any one of these problems is enough cause to reverse the decision to make vt the default console driver for 11.0. This would give time for these problems to be address and correctly tested and when ready then be paced in some other 11.x release.