Date: Tue, 18 Nov 2014 15:37:35 +0200 From: Kimmo Paasiala <kpaasial@gmail.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Mountroot prompt with the new vt(4) console not working. Message-ID: <CA%2B7WWSer3a1dGaP4yWjYaVQ7yryEELgqQSv7q6MFhu4PXo5ctQ@mail.gmail.com> In-Reply-To: <op.xpinr310kndu52@ronaldradial.radialsg.local> References: <CA%2B7WWSeG1=nosP2wc6P22vZYhhrVqXL7=9yrNnY%2BKEsrjUMJrg@mail.gmail.com> <op.xpinr310kndu52@ronaldradial.radialsg.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 18, 2014 at 12:37 PM, Ronald Klop <ronald-lists@klop.ws> wrote: > On Sat, 15 Nov 2014 13:03:38 +0100, Kimmo Paasiala <kpaasial@gmail.com> > wrote: > >> I'm not able to use the mountroot prompt with the new vt(4) console on >> any of the systems I have, all of them either stable/10 or >> releng/10.1. The problem is that I can't type anything at the prompt >> or if I can the letters appear as garbage and they come out like one >> character every five seconds. Is the mountroot prompt working for >> anyone who is using the new vt(4) console? >> >> -Kimmo > > > Not much reaction on this one. It can help if you tell more about your > setup. > - What kind of keyboard (USB or PS/2)? What country/language is the keyboard > for? > - GENERIC kernel or custom? > - What video driver are you using with vt? > - Any custom settings while booting? > - etc. > > Regards, > Ronald. > _______________________________________________ It's a PS/2 keyboard. Only the default VGA driver is used with vt(4). These are my loader.conf(5) settings on one of my systems: loader_logo="beastie" hw.usb.no_pf=1 kern.cam.ada.legacy_aliases=0 kern.vty=vt kern.geom.label.gptid.enable=0 This particular system is a firewall based on rather old Jetway J7F2WE1F2E Mini-ITX motherboard: http://www.jetwaycomputer.com/J7F2.html I don't exactly need vt(4) console on my systems because they are just firewalls and servers so no X anywhere but I'd like to know if other people have the same problem and if it's a problem with the vt(4) driver or something peculiar to my systems, BIOS problem or something else. -Kimmo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7WWSer3a1dGaP4yWjYaVQ7yryEELgqQSv7q6MFhu4PXo5ctQ>