On Mon, Sep 23, 2019 at 07:39:33PM +0100, Ken Moffat via lfs-dev wrote:
> On Mon, Sep 23, 2019 at 12:40:54PM -0500, Bruce Dubbs via lfs-dev wrote:
> > On 9/23/19 12:20 PM, Ken Moffat via lfs-dev wrote:
> > >
> > > But using setfont for an 8x16 font in the console init script was
> > > still failing although I could run it on each tty after logging in.
> > > There was also an error message from that script, although it said
> > > [ok] afterwards:
> > >
> > > *ERROR* construct Invalid Connector Object ID for Adapter Service for
> > > connector index:2! type 0 expected 3
> > >
> > > Instrumenting the script, and suspecting a race, I eventually
> > > settled on the following change (and put the error as a comment):
> > >
> > > diff -Naur a/lfs/init.d/console b/lfs/init.d/console
> > > --- a/lfs/init.d/console 2013-01-24 22:25:14.000000000 +0000
> > > +++ b/lfs/init.d/console 2019-09-23 16:50:09.579343530 +0100
> > > @@ -80,7 +80,11 @@
> > > done
> > > # Set the font (if not already set above) and the keymap
> > > - [ "${use_fb}" == "1" ] || [ -z "${FONT}" ] || setfont $FONT ||
> > > failed=1
> > > + # Without the sleep, setfont can fail on amdgpu framebuffer
> > > + # and even with it there can be an error message on 5.2 kernels
> > > + # *ERROR* construct Invalid Connector Object ID for Adapter Service
> > > + # for connector index:2! type 0 expected 3
> > > + [ "${use_fb}" == "1" ] || [ -z "${FONT}" ] || sleep 1 ; setfont
> > > $FONT || failed=1
> > > [ -z "${KEYMAP}" ] ||
> > > loadkeys ${KEYMAP} >/dev/null 2>&1 ||
> > >
> > >
> > > Using that in 5.2.17 now successfully loads my specified font but
> > > still produces the ERROR message (I tried adding 2>/dev/null but
> > > that did not suppress it). So, I was going to use this on future
> > > builds.
> > >
> > > But when booting 5.3.1 I no-longer get the error message so whenever
> > > I make my next build (probably not this week) I'll try without the
> > > patch. I suspect the problem might be specific to Picasso APUs and
> > > 5.2 kernels (noted with 5.2.11 and 5.2.17, no earlier kernels were
> > > used).
> >
> > Yes, it is. You might want to try 'sleep 0.1;
> >
> LOL, I think I'm doing that in real life when I go to bed ;) My
> plan is to wait until I build a new system (I'd hoped that would be
> this week, but now unlikely) and try without.
>
Sorry for not trimming the above, I'm now too pissed off to decide
how little of the above is actually needed to keep sufficient
context!
With linux 5.3.1 I am now booting with the kernel's Sun-12x22 font,
the error message has gone. If I reinstate the 'sleep 1' (or,
indeed, 'sleep 0.1') I get the expected LatGrkCyr-12x22 (so ĸ shows
as kra, like cyrillic and greek lowercase k-equivalents, instead of
a small square) - but only on tty1.
On other ttys I have to 'setfont LatGrkCyr-12x22'. For the moment
I'll just live with this, too much else to look at.
ĸen
--
thread 'main' panicked at 'giraffe',
/tmp/rustc-1.32.0-src/src/test/run-fail/while-panic.rs:17:13
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
