Re: newcons and beeping X
Are there any problems with MFC? -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5916170.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
On Sat, 17 May 2014 08:59:14 -0700 (PDT) Jakub Lach wrote: > Hello, > > as of FreeBSD 10.0-STABLE #0 r266216 I still have > a mute console in X (which isn't surprising, as there > was no MFC) > > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5913086.html > Sent from the freebsd-current mailing list archive at Nabble.com. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Hi Jakub, Yes, I'm did not MFC it yet. Will do it in next few days. WBW -- Aleksandr Rybalko ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
Hello, as of FreeBSD 10.0-STABLE #0 r266216 I still have a mute console in X (which isn't surprising, as there was no MFC) -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5913086.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
On Thu, 1 May 2014 03:31:21 -0500 "Matthew D. Fuller" wrote: > > A little investigation showed that the KDMKTONE ioctl handler was a > > complete stub, so anything X tried to do to ring the bell was > > completely unavailing. > > Sub'd as http://www.freebsd.org/cgi/query-pr.cgi?pr=189170 > > > -- > Matthew Fuller (MF4839) | fulle...@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ >On the Internet, nobody can hear you scream. Hello Matthew, sorry for delay, been busy with other part of vt(4). I've just commit your patch. Thank you very much for your help! WBW -- Aleksandr Rybalko ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
By choppy I've also meant it's noticeably slower than syscons, but I think it's already known. The shell was a shells/mksh. I think I may switch to newcons permanently after a merge of bell patch thing. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908275.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
On 1 May 2014 17:31, Jakub Lach wrote: > I'm aware of another problem though (and can > clarify it now). > > If I use any other character than a basic latin set, my > prompt is not preserved. Thanks for testing! With which shell do you observe this? I don't with csh from base and zsh from ports, and it appears sh doesn't accept the characters at all. (I am testing with -CURRENT, though.) > Apart form that, newcons works, albeit kind of choppy, > do I have any control of it's resolution? Right now it defaults to 80x25 characters in a 640x480 framebuffer, and the resolution won't change until the specific driver is loaded (e.g. i915kms), and it should then switch to the proper resolution for your display. This happens automatically when X starts, but you can also manually kldload the driver. There is unfortunately no way to choose a resolution yet. > Can I make it more seamless with both X and bootloader? > > (now I have bootloader for a splitsecond, abrupt video reset, > newcons spawned with the same resolution but with > different font, after starting X and going back to newcons > it preserves X resolution) For now if you have the driver load you'll have a seamless experience between console and X, but still a blip when switching from the loader to kernel. That will be addressed on UEFI systems, but we probably won't be able to do anything about it for the non-UEFI case. -Ed ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
I've used attached script for making usable kbd. I'm aware of another problem though (and can clarify it now). If I use any other character than a basic latin set, my prompt is not preserved. e. g. Kuba@Thinkpad:/usr/home/Kuba $ abcdefghi Kuba@Thinkpad:/usr/home/Kuba $ Kuba@Thinkpad:/usr/home/Kuba $ ąćęłóźż Kuba@Thinkpad:/usr/ho Apart form that, newcons works, albeit kind of choppy, do I have any control of it's resolution? Can I make it more seamless with both X and bootloader? (now I have bootloader for a splitsecond, abrupt video reset, newcons spawned with the same resolution but with different font, after starting X and going back to newcons it preserves X resolution) -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908080.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
Thanks for reply, that helped me somehow. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908076.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
On 1 May 2014 13:00, Jakub Lach wrote: > As far as I can tell, the situation is the same on > FreeBSD 10.0-STABLE #0 r265185 amd64. > > newcons uses my X font (terminus), Newcons' font is built-in, it's not using your X font. (It just happens that you and Ed made the same choice.) > albeit it produces > no polish letters (some random glyphs are produced), ... > keymap=pl_PL.ISO8859-2 Oh, here's the issue - we need a UTF-8 Polish keyboard map. It's the input path that's confused. Newcons can display Polish characters fine - you should be able to confirm this is working by running /usr/bin/printf \\305\\201 which should give you a stroked L (Ł). There's some explanation in Aleksandr's blog post: http://raybsd.blogspot.ca/2013/10/newcons-international-keyboard-input.html ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
As far as I can tell, the situation is the same on FreeBSD 10.0-STABLE #0 r265185 amd64. newcons uses my X font (terminus), albeit it produces no polish letters (some random glyphs are produced), bell is working but initila terminal offset is wrong- I can "overwrite" my terminal prompt, X is mute but correctly localized. I've added: device vt device vt_vga #device sc #device vga I have in rc.conf font8x14=iso02-8x14 font8x16=iso02-8x16 font8x8=iso02-8x8 keymap=pl_PL.ISO8859-2 but it makes no difference on newcons iirc from last time. newcons work similarly to xterm those few times I've unsuccessfully tried to switch to UTF-8 (I've distinctly remember prompt offset problem and indexed 3 in place of ł). -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908019.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
I think that newcons used somehow my terminus font from X (?) and there were no polish characters. I had/have in rc.conf font8x14=iso02-8x14 font8x16=iso02-8x16 font8x8=iso02-8x8 but it made no difference. It was on 10-STABLE, somewhat early after merge. I may try it again later today. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5907951.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
On 1 May 2014 05:05, Jakub Lach wrote: > [...] no localised font in system console Can you clarify what you mean here -- what character set do you wish to use? The default Newcons font includes extended Latin, Greek, and Cyrillic. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
newcons beeping in X and no localised font in system console is why I've dropped newcons. Thanks for submission. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5907856.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newcons and beeping X
> A little investigation showed that the KDMKTONE ioctl handler was a > complete stub, so anything X tried to do to ring the bell was > completely unavailing. Sub'd as http://www.freebsd.org/cgi/query-pr.cgi?pr=189170 -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
newcons and beeping X
I switched my workstation over to newcons today, and it worked just fine, so yay. After using it a while, it slowly dawned on me that I wasn't making hardly any typing mistakes, nor was there any annoying email coming in. After all, if either were happing, I'd be getting beeps; vt is making my life easier! ... wait... A little investigation showed that the KDMKTONE ioctl handler was a complete stub, so anything X tried to do to ring the bell was completely unavailing. Urg. That's... unpleasant. >From poking around in vt and comparing with syscons, I've come up with the following patch which makes it work (as the couple beeps I've spawned just writing this email show). It's kinda fugly; should probably be better factored, or less magic-numberized. Possibly vtterm_bell() should be able to take pitch/duration like sc_bell() does. But it's _much_ better than nothing; the bell should work! Index: sys/dev/vt/vt_core.c === --- sys/dev/vt/vt_core.c(revision 264991) +++ sys/dev/vt/vt_core.c(working copy) @@ -1636,7 +1636,11 @@ #endif return (0); case KDMKTONE: /* sound the bell */ - /* TODO */ + if(*(int*)data) + sysbeep(1193182 / ((*(int*)data)&0x), + (((*(int*)data)>>16)&0x)*hz/1000); + else + vtterm_bell(tm); return (0); case KIOCSOUND: /* make tone (*data) hz */ /* TODO */ -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
