On Tuesday 21 October 2014 at 21:57:09, Michal Sekletar wrote: > On Tue, Oct 21, 2014 at 09:39:46PM +0400, Ivan Shapovalov wrote: > > On Tuesday 21 October 2014 at 19:03:17, Michal Sekletar wrote: > > > On Tue, Oct 14, 2014 at 09:04:56AM +0200, Jan Synacek wrote: > > > > Michal Sekletar <msekl...@redhat.com> writes: > > > > > On Mon, Oct 13, 2014 at 09:36:16AM +0200, Jan Synacek wrote: > > > > >> Hello, > > > > >> > > > > >> currently, unicode characters are not correctly displayed in the > > > > >> console. After login, when I run /usr/bin/unicode_start, unicode > > > > >> works > > > > >> fine. I tried to create a service file that runs this script, linking > > > > >> tty to stdout and stderr, but that didn't work. Is there a way how to > > > > >> turn on unicode support in console after boot using a service file? > > > > >> Or > > > > >> any other type of unit? Or is this something that has to be patched > > > > >> in > > > > >> the source (logind perhaps?)? > > > > > > > > > > Please try editing > > > > > /usr/lib/systemd/system/systemd-vconsole-setup.service and > > > > > remove RemainAfterExit=yes, then regenerate your initramfs image by > > > > > running > > > > > dracut command. Add back RemainAfterExit=yes to service file. Reboot. > > > > > > > > Yep, this helped. Could you please explain why? Also, I believe this > > > > should be fixed in all Fedora versions. > > > > > > I must admit I'm not sure why this workaround works. Maybe there is some > > > race > > > condition with some kernel initialization or settings get unapplied > > > because of > > > switch-root. > > > > > > Also, if we go with workaround in Fedora I think dracut needs to fixed to > > > include version on unit file *without* RemainAfterExit=yes. > > > > IIUC, this makes unit to be re-run outside of initramfs, so the VT is set > > up twice, > > second time after switching the framebuffer driver. > > > > And the latter condition is not mandated by anything, it's just a > > coincidence... > > I guess that what you are saying pretty much summarizes the situation here. > Can > we make something about framebuffer driver, thus settings applied in initramfs > are not thrashed?
I don't know if there is a valid solution. Maybe someone familiar with the VT subsystem knows... Personally I've worked around this problem as follows: the fb driver (i915) is included into the initramfs, while systemd-vconsole-setup is ran only in the real root. -- Ivan Shapovalov / intelfx /
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
