Re: wscons.conf ledstate and screen issues
> Sent: Friday, December 14, 2018 at 12:20 PM > From: "Valery Ushakov" > To: netbsd-users@netbsd.org > Subject: Re: wscons.conf ledstate and screen issues [...] > The above is 9 screens, not 8. Oh, right, thank you. I removed the `screen 8' line and the error in dmesg disappeared. Now, the remaining issue is about Num Lock: is there a way to activate it, other than pressing the button? Something similar to `ledstate -> 1' in wscons configuration, but with effect on Num Lock. Rocky > > -uwe > >
Re: wscons.conf ledstate and screen issues
Rocky Hotas wrote: > Second issue is about the creation of new screens. I modified from default > the wscons.conf file as follows: > > #screen 0 - vt100 > screen 1- vt100 > screen 2- vt100 > screen 3- vt100 > screen 4- vt100 > screen 5- vt100 > screen 6- vt100 > screen 7- vt100 > screen 8- - > > in order to have not only 4, but 8 available screens at boot, which can be > accessed through Ctrl+Alt+Fn. However, this generated a > > wsconscfg: WSDISPLAYIO_ADDSCREEN > > error. It was impossible to create them. The above is 9 screens, not 8. -uwe
Re: wscons.conf ledstate and screen issues
> Sent: Wednesday, December 12, 2018 at 9:04 PM > From: "Valery Ushakov" > To: netbsd-users@netbsd.org > Subject: Re: wscons.conf ledstate and screen issues [...] > From a quick look - ledstate only controls the lights, not the > internal state of the keyboard driver (that handles numlock ). Yes, you are right. So, this is an "appearance" issue. As regards the numlock instead, is there a way to set it, in particular at boot? As regards the additional screens, I followed The NetBSD Guide here http://www.netbsd.org/docs/guide/en/chap-cons.html#chap-cons-wscons-wsdisplay Not only /etc/wscons.conf must be modified, but also (and accordingly) /etc/ttys. I obtained the 8 screens and they are ok, but the kernel still prints an error: wsconscfg: WSDISPLAYIO_ADDSCREEN Invalid argument Bye! Rocky > > -uwe > >
Re: wscons.conf ledstate and screen issues
Rocky Hotas wrote: > After installing 8.0 amd64 and tweaking wscons.conf, I experienced exactly > the same issue as in this old message: > > https://mail-index.netbsd.org/netbsd-users/2012/09/24/msg011493.html > > I would like to have num lock (and its led) active at the login screen. > > # wsconsctl -w ledstate=2 > > works for the current session. I put the line > > setvar wskbd ledstate2 > > in /etc/wscons.conf. After a reboot, this configuration is correctly > applied, as shown by the led and the screen messages; however, the *first* > key that is pressed (whatever it is) causes the default ledstate=0 to be > restored. > What could it be the problem? >From a quick look - ledstate only controls the lights, not the internal state of the keyboard driver (that handles numlock ). -uwe
wscons.conf ledstate and screen issues
Hello! After installing 8.0 amd64 and tweaking wscons.conf, I experienced exactly the same issue as in this old message: https://mail-index.netbsd.org/netbsd-users/2012/09/24/msg011493.html I would like to have num lock (and its led) active at the login screen. # wsconsctl -w ledstate=2 works for the current session. I put the line setvar wskbd ledstate2 in /etc/wscons.conf. After a reboot, this configuration is correctly applied, as shown by the led and the screen messages; however, the *first* key that is pressed (whatever it is) causes the default ledstate=0 to be restored. What could it be the problem? Second issue is about the creation of new screens. I modified from default the wscons.conf file as follows: #screen 0 - vt100 screen 1- vt100 screen 2- vt100 screen 3- vt100 screen 4- vt100 screen 5- vt100 screen 6- vt100 screen 7- vt100 screen 8- - in order to have not only 4, but 8 available screens at boot, which can be accessed through Ctrl+Alt+Fn. However, this generated a wsconscfg: WSDISPLAYIO_ADDSCREEN error. It was impossible to create them. Is it normal? Did I make a wrong configuration? Thank you anyway! Bye :) Rocky
