* Setting console font [default8x16] ... putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented putfont: PIO_FONT trying ... ................... setfont: putfont: 256,8x16: failed: -1 putfont: PIO_FONT: Function not implemented [ !! ] * ERROR: consolefont failed to start The (pretty basic) STI framebuffer apparently doesn't respond very well to something in the consolefont script. Each try takes quite a long time to return so this slows down the boot process significantly. CC'ing release@ as it may prove useful to workaround the problem in the upcoming release by removing consolefont from the runlevels on HPPA boot media.
well, i really dont see there anything to "fix" in the init.d script itself. the default hppa framebuffer doesnt support changing fonts which means consolefont shouldnt be run. about the only thing worth doing is adding a line like: use hppa && rm -f "${D}"/usr/share/openrc/runlevels/boot/consolefont thus disabling consolefont on hppa by default for everyone ...
please note there's two ways to use STI from linux: - CONFIG_STI_CONSOLE "STI text console", this is a text console which has nothing to do with framebuffer. - CONFIG_FB_STI "HP STI frame buffer device support", that's an actual framebuffer and will create /dev/fbX and can be used by a "Framebuffer console" (CONFIG_FRAMEBUFFER_CONSOLE) if you're using the former there's no concept of "font" from the linux side of things, it's just a text interface. if you're using the latter, then I would expect to be able to change fonts and that fonts are handled by the framebuffer console driver, and not by the actual framebuffer driver (at least for non-accelerated framebuffers like STI). But I have to admit I haven't actually looked at the code and I don't have suitable hardware to test. (In reply to comment #1) > about the only thing worth doing is adding a line like: > use hppa && rm -f "${D}"/usr/share/openrc/runlevels/boot/consolefont > thus disabling consolefont on hppa by default for everyone ... hppa isn't limited to STI framebuffers. at least sst (Voodoo Graphics PCI) and some ATI cards presently work. I had an HPPA system with framebuffer (both console and X11) on sst (although I never tried to change fonts).
Created attachment 195107 [details, diff] openrc-0.4.3-r3.ebuild-hppa-consolefont.patch
This has been fixed, and the fix will be in openrc-0.8.2.
Thanks for the report.
