Date: Mon, 28 Jul 2014 05:29:39 -0700 From: Filippo Moretti <filippomore@yahoo.com> To: Stefan Esser <se@freebsd.org> Cc: Tom Evans <tevans.uk@googlemail.com>, "stable@freebsd.org" <stable@freebsd.org> Subject: Re: Problem with italian keyboard Message-ID: <1406550579.20496.YahooMailNeo@web140904.mail.bf1.yahoo.com> In-Reply-To: <53D63CEE.2010106@freebsd.org> References: <1406542670.84373.YahooMailNeo@web140906.mail.bf1.yahoo.com> <CAFHbX1JNMi1t5uw2x6TmLkKYvkHxVDR5Q=isYvLPUuwDrTut4A@mail.gmail.com> <53D63CEE.2010106@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I ran kbdmap -l and now is working properly=0Athank you=0AFilippo=0A=0A=0A= =0AOn Monday, July 28, 2014 2:17 PM, Stefan Esser <se@freebsd.org> wrote:= =0A =0A=0A=0AAm 28.07.2014 um 13:20 schrieb Tom Evans:=0A> On Mon, Jul 28, = 2014 at 11:17 AM, Filippo Moretti via freebsd-stable=0A>> Configuring sysco= ns: keymapkbdcontrol: keymap file "it.iso.kbd" not found: No such file or d= irectory=0A>> however there is it.iso.kbd in /usr/share/syscons/keymaps=0A>= =0A> You need to convert this and put it in /usr/share/vt/keymaps since yo= u=0A> are no longer using syscons.=0A=0AFor LATIN encodings (e.g. ISO8859-1= ) no conversion is required=0A(the result of the conversion is identical to= the file for=0Asyscons).=0A=0AYou can copy over the file from /usr/share/s= yscons/keymaps/ to=0A/usr/share/vt/keymaps/, or you can put the full path t= o the=0Akeymap file into rc.conf (or use it on the command line).=0A=0AI th= ink we should have a working solution in the upcoming=0AFreeBSD-10.1.=0A=0A= Since the keymaps for LATIN encodings are compatible between=0Asyscons and = newcons, they could be=A0 installed into both places,=0Asyscons/keymaps and= vt/keymaps.=0A=0AAlternatively, kbdcontrol could use the syscons/keymaps= =0Adirectory as a fallback for keymaps not found in vt/keymaps.=0AThis work= -around is currently active in -CURRENT, since there=0Aare only 3 converted= keymap files in vt/keymaps and everybody=0Atrying out newcons has the same= problem.=0A=0ARegards, STefan=0A=0A_______________________________________= ________=0Afreebsd-stable@freebsd.org mailing list=0Ahttp://lists.freebsd.o= rg/mailman/listinfo/freebsd-stable=0ATo unsubscribe, send any mail to "free= bsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Jul 28 16:07:54 2014 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25BEDD8B; Mon, 28 Jul 2014 16:07:54 +0000 (UTC) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E15602D2A; Mon, 28 Jul 2014 16:07:53 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id eu11so10823196pac.3 for <multiple recipients>; Mon, 28 Jul 2014 09:07:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yp5TauZv/+AhYnH+GsFaMbC9qs/9wQRw8Ft61+mJ6P8=; b=Jb7e0vB/GKvrwCNcf5/UMGOYBgmUDRRx4C92P46hVH6s4FsxcZK9VdcmcquMYG9n+L xXByVP3HVvukKwurdbjo+zoKR3F1jUW8vA4CZjx5TycTBczjFJ0jkNEc2wdFv2nfIzTP tahWLTY/D91bsFnurUkXaFQRvHe5NA5JX7C0zD6qba0Hx5PPt30qnA2rHn+V/krdzCYe +XYdjInpZrTo/m3UocxgNEEgun2nOC0CZfNkBRHtVxmmm57J2na/zWdUqWHDoBDhzj6n M1i6G6OW4v80RvmmboF7dlF26r5lEXRz/yrukjky6hFSdIhWeZ2cQpCjya9zUETMJ2Do RYUg== X-Received: by 10.69.2.35 with SMTP id bl3mr39230690pbd.83.1406563673502; Mon, 28 Jul 2014 09:07:53 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:9cc1:8b97:b7d9:aa45? ([2601:8:ab80:7d6:9cc1:8b97:b7d9:aa45]) by mx.google.com with ESMTPSA id gb1sm18071177pbd.76.2014.07.28.09.07.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jul 2014 09:07:52 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel From: Garrett Cooper <yaneurabeya@gmail.com> In-Reply-To: <EBEA5B58-A94B-4639-AFBA-181D4EE1D402@gmail.com> Date: Mon, 28 Jul 2014 09:07:52 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3BFFF901-F5C0-4079-834E-F3199A188EF8@gmail.com> References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <201307221208.22060.jhb@freebsd.org> <EBEA5B58-A94B-4639-AFBA-181D4EE1D402@gmail.com> To: John Baldwin <jhb@freebsd.org> X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 28 Jul 2014 16:07:54 -0000 On Jul 22, 2013, at 10:58 AM, Garrett Cooper <yaneurabeya@gmail.com> = wrote: > On Jul 22, 2013, at 9:08 AM, John Baldwin <jhb@freebsd.org> wrote: >=20 >> On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: >>> I have a KERNCONF that previously had PS/2 support compiled into the = kernel. If I comment out the following lines like so: >>>=20 >>> # atkbdc0 controls both the keyboard and the PS/2 mouse >>> #device atkbdc # AT keyboard controller >>> #device atkbd # AT keyboard >>>=20 >>> then I'm able to mount root again (it was failing with ENOXDEV). >>>=20 >>> The working kernel was as follows: >>>=20 >>> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETTA >>> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>> = gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-st= able-9/sys/BAYONETTA >>> gcc version 4.2.1 20070831 patched [FreeBSD] >>> FreeBSD >>> 9.1-STABLE >>> BAYONETTA >>> $ cd /usr/src; git log 0304216 >>> commit 03042167f73c213732b44218a24d8e1bbea00f8c >>> Merge: 2edcad2 974abfb >>> Author: Garrett Cooper <yanegomi@gmail.com> >>> Date: Mon Jun 24 19:00:45 2013 -0700 >>>=20 >>> Merge remote-tracking branch 'upstream/stable/9' into stable/9 >>>=20 >>> The working kernel [with atkbdc] was as follows: >>>=20 >>> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 r+c178034: = Sun Jul 21 20:19:38 PDT 2013 =20 >> = root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-stabl= e-9/sys/BAYONETTA amd64 >>> $ git log c178034 >>> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 >>> Author: avg <avg@FreeBSD.org> >>> Date: Tue Jul 9 08:30:31 2013 +0000 >>>=20 >>> zfsboottest.sh: remove checks for things that are not strictly = required >>>=20 >>> MFC after: 10 days >>>=20 >>> (Yes, I had to backport some things because they are busted on = stable/9 due to other incomplete/missing MFCs). >>>=20 >>> I can test out patches, but I don't have time to bisect the actual = commit that caused the failure. That being said my intuition says it's = this >> commit should be looked at first: >>>=20 >>> commit 28f961058b0667841d7e9d8639bfd02ed8689faa >>> Author: jhb <jhb@FreeBSD.org> >>> Date: Wed Jul 17 14:04:18 2013 +0000 >>>=20 >>> MFC 252576: >>> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI = bridges. If >>> we are probing a PCI-PCI bridge it is because we found one by = enumerating >>> the devices on a PCI bus, so the bridge is definitely present. A = few >>> BIOSes report incorrect status (_STA) for some bridges that = claimed they >>> were not present when in fact they were. >>>=20 >>> While here, move this check earlier for Host-PCI bridges so attach = fails >>> before doing any work that needs to be torn down. >>>=20 >>> PR: kern/91594 >>> Approved by: re (marius) >>=20 >> I strongly doubt that this is related. It would be most helpful if = you could >> obtain a dmesg from the new kernel however (perhaps via a serial = console) to >> rule it out. All you would need to see is if the new kernel sees = more "pcib" >> devices than the old one to see if this change even has an effect on = your >> system. >=20 > Unfortunately the USB keyboard is broken as well at the mount root = prompt and the workstation doesn't have a uart on it that I can play = with (it's my home box), so I'm dead in the water when it panics at the = mount root prompt right now. >=20 > I guess I can revert this and a handful of other amd64/ata_cam/zfs = commits to see if this goes away, but I won't be getting to that before = next Sunday probably as this is my file server and DNS server now. I ran into the issue going from vanilla 9.2-RELEASE-p10 to = 9.3-RELEASE as well :(. I=92ve filed this bug to track the issue: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 . I=92ll see = if GENERIC can boot my system sometime this week (the KERNCONF has been = working for several releases, but it could be an issue with that that=92s = being overlooked by accident). Thanks! -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1406550579.20496.YahooMailNeo>