/bin/loadkeys not found after emerge -DuN world

[LGTrader]

Hi,
   I've completed my updates of this older Mac Mini. The machine boots
and runs fine but there's a small problem in the boot console:

* Loading key mappings
* /bin/loadkeys not found
** ERROR: cannot start consolefont as keymaps could not start

   None of this occurred prior to the emerge -DuN world.

   I tried using equery belongs /bin/loadkeys but it didn't find
anything, There seem to be a number of bugs that discuss this which
are a bit beyond my understanding of what to do, like this one:

http://bugs.gentoo.org/show_bug.cgi?id=232072

   I guess it's caused by some issue in baselayout and may be fixed in
a newer version. I can wait for the new version to become stable if
this won't cause any big problems but I cannot evaluate the severity
of this on my own.

   Comments? Can I leave it alone and not worry about problems?

Thanks,
Mark

[Albert Hopkins-4]

On Fri, 2009-01-16 at 07:24 -0800, Mark Knecht wrote:

> Hi,
>    I've completed my updates of this older Mac Mini. The machine boots
> and runs fine but there's a small problem in the boot console:
>
> * Loading key mappings
> * /bin/loadkeys not found
> ** ERROR: cannot start consolefont as keymaps could not start
>
>    None of this occurred prior to the emerge -DuN world.
>
>    I tried using equery belongs /bin/loadkeys but it didn't find
> anything, There seem to be a number of bugs that discuss this which
> are a bit beyond my understanding of what to do, like this one:
>

My loadkeys is in /usr/bin

> http://bugs.gentoo.org/show_bug.cgi?id=232072
>
>    I guess it's caused by some issue in baselayout and may be fixed in
> a newer version. I can wait for the new version to become stable if
> this won't cause any big problems but I cannot evaluate the severity
> of this on my own.
>
>    Comments? Can I leave it alone and not worry about problems?

A word of advice, when a bugzilla is resolved as DUPLICATE you should
(almost always) immediately click on the bug that it's a duplicate of
because that's where all the action is taking place:

http://bugs.gentoo.org/show_bug.cgi?id=215496

HTH,
-a

[LGTrader]

On Fri, Jan 16, 2009 at 7:32 AM, Albert Hopkins <marduk@...> wrote:

> On Fri, 2009-01-16 at 07:24 -0800, Mark Knecht wrote:
>> Hi,
>>    I've completed my updates of this older Mac Mini. The machine boots
>> and runs fine but there's a small problem in the boot console:
>>
>> * Loading key mappings
>> * /bin/loadkeys not found
>> ** ERROR: cannot start consolefont as keymaps could not start
>>
>>    None of this occurred prior to the emerge -DuN world.
>>
>>    I tried using equery belongs /bin/loadkeys but it didn't find
>> anything, There seem to be a number of bugs that discuss this which
>> are a bit beyond my understanding of what to do, like this one:
>>
> My loadkeys is in /usr/bin

Interesting difference. I'm setting up this Power PC based MacMini to
be a secondary MythTV backend server. My x86 backend server agrees
with you:

<x86>
Sector9 ~ # slocate loadkeys
/usr/share/man/man1/loadkeys.1.bz2
/bin/loadkeys
Sector9 ~ #

<ppc>
MacMini ~ # slocate loadkeys
/usr/bin/loadkeys
/usr/share/man/man1/loadkeys.1.bz2
MacMini ~ #

That file seems to be supplied by kbd:

MacMini ~ # equery belongs /usr/bin/loadkeys
[ Searching for file(s) /usr/bin/loadkeys in *... ]
sys-apps/kbd-1.14.1-r1 (/usr/bin/loadkeys)
MacMini ~ #

However the keymaps initscript comes from baselayout?

MacMini ~ # equery belongs /etc/init.d/keymaps
[ Searching for file(s) /etc/init.d/keymaps in *... ]
sys-apps/baselayout-1.12.11.1 (/etc/init.d/keymaps)
MacMini ~ #

It seems that my current mythbackend machine has an older kbd package:
Sector9 ~ # emerge -pv baselayout kbd

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-apps/baselayout-1.12.11.1  USE="unicode -bootstrap
-build -static" 0 kB
[ebuild   R   ] sys-apps/kbd-1.13-r1  USE="nls" 0 kB

Total: 2 packages (2 reinstalls), Size of downloads: 0 kB
Sector9 ~ #

>
>> http://bugs.gentoo.org/show_bug.cgi?id=232072
>>
>>    I guess it's caused by some issue in baselayout and may be fixed in
>> a newer version. I can wait for the new version to become stable if
>> this won't cause any big problems but I cannot evaluate the severity
>> of this on my own.
>>
>>    Comments? Can I leave it alone and not worry about problems?
>
> A word of advice, when a bugzilla is resolved as DUPLICATE you should
> (almost always) immediately click on the bug that it's a duplicate of
> because that's where all the action is taking place:
>
> http://bugs.gentoo.org/show_bug.cgi?id=215496
>

Actually I should/could have posted that but it seemed to me it didn't
say much of anything. I thought the one I posted had more info.

Anyway, I see the older version is in portage so I suppose I should
jsut go back to that for now?

MacMini ~ # eix -I kbd
[I] sys-apps/kbd
     Available versions:  1.12-r8 1.13-r1 1.14.1-r1 ~1.15 {nls}
     Installed versions:  1.14.1-r1(14:18:42 01/15/09)(nls)
     Homepage:            http://freshmeat.net/projects/kbd/
     Description:         Keyboard and console utilities

MacMini ~ #

Thanks,
Mark

[Albert Hopkins-4]

On Fri, 2009-01-16 at 07:56 -0800, Mark Knecht wrote:
[...]

> > A word of advice, when a bugzilla is resolved as DUPLICATE you should
> > (almost always) immediately click on the bug that it's a duplicate of
> > because that's where all the action is taking place:
> >
> > http://bugs.gentoo.org/show_bug.cgi?id=215496
> >
>
> Actually I should/could have posted that but it seemed to me it didn't
> say much of anything. I thought the one I posted had more info.
>

If I'm not mistaken, comments #4 and #5 (the last two comments) pertain
to you.

[LGTrader]

On Fri, Jan 16, 2009 at 10:36 AM, Albert Hopkins <marduk@...> wrote:

> On Fri, 2009-01-16 at 07:56 -0800, Mark Knecht wrote:
> [...]
>> > A word of advice, when a bugzilla is resolved as DUPLICATE you should
>> > (almost always) immediately click on the bug that it's a duplicate of
>> > because that's where all the action is taking place:
>> >
>> > http://bugs.gentoo.org/show_bug.cgi?id=215496
>> >
>>
>> Actually I should/could have posted that but it seemed to me it didn't
>> say much of anything. I thought the one I posted had more info.
>>
> If I'm not mistaken, comments #4 and #5 (the last two comments) pertain
> to you.

Well, yes, but they don't say anything (to me) as best I read. Or
maybe I don't understand how the folks that work in those areas talk
these days.

Basically it seems it's broken for ppc, the folks in that thread
understand it's broken, and then what? Those comments were two months
ago.

I'm lost.

I went back to kbd-1.13-r1and the problem is gone but then another
problem appears where it cannot map character code 0 to some other
value. I've lost that message for now as I start MythTV automatically
and cannot get back in the console becuase of X messages but it's in
the bug system somewhere. I found it earlier this morning.

Anyway, I think the two sides (x86/amd64 && ppc) aren't consistently
handled and that these folks know it but haven't fixed it for some
reason. I only ran into it because of an update to a machine that's
been gathering dust.

- Mark

[Albert Hopkins-4]

On Fri, 2009-01-16 at 10:59 -0800, Mark Knecht wrote:
[...]
> >>
> > If I'm not mistaken, comments #4 and #5 (the last two comments) pertain
> > to you.
>
> Well, yes, but they don't say anything (to me) as best I read. Or
> maybe I don't understand how the folks that work in those areas talk
> these days.
>
I believe what comment #4 is saying is that while,
sys-apps/baselayout-1.12.12 fixes the issue that version is not in ppc
stable.

I believe what vapier is saying, albeit crudely and tersely, in comment
#5 is that he did is job (which was to fix the bug) and if you need the
fix in stable then you need to file a ppc stabilization bug.  Presumably
vapier doesn't handle ppc stabilization bugs so he's passing the buck.

> Basically it seems it's broken for ppc, the folks in that thread
> understand it's broken, and then what? Those comments were two months
> ago.
>
If the author of comment #4 hasn't already done so, I would recommend
that you file a ppc stabilization bug for baselayout-1.12.12.

> I'm lost.

HTH

> I went back to kbd-1.13-r1and the problem is gone but then another
> problem appears where it cannot map character code 0 to some other
> value. I've lost that message for now as I start MythTV automatically
> and cannot get back in the console becuase of X messages but it's in
> the bug system somewhere. I found it earlier this morning.
>
Ok... but that's a separate issue...

> Anyway, I think the two sides (x86/amd64 && ppc) aren't consistently
> handled and that these folks know it but haven't fixed it for some
> reason. I only ran into it because of an update to a machine that's
> been gathering dust.

Not wanting to go in to a long discussion (too late for that I guess)
there is basically the "regular" dev folks, who presumably vapier
belongs to, and then there are the arch teams (the above is 3 sides,
actually; not two) who handle testing and stabilization on a particular
platform.  These are not always the same people and, as often the case
in the Gentoo development world, one side doesn't necessarily know/care
what the other side is doing.  Even between the arch teams there is
little "consistency" i.e. the x86 arch team doesn't care what's
happening in the ppc world.  Vapier handles the software, but he doesn't
necessarily mess with the ACCEPT_KEYWORDS variable. That's why he's
requesting you open another bug for that.

-a

[Blackheartsx]

Hi,
temporary you can create a symlink "/bin/loadkeys" to "/usr/bin/loadkeys".
This will fix it for the first time.

Greets Black

Mark Knecht wrote:

Hi,
   I've completed my updates of this older Mac Mini. The machine boots
and runs fine but there's a small problem in the boot console:

* Loading key mappings
* /bin/loadkeys not found
** ERROR: cannot start consolefont as keymaps could not start

   None of this occurred prior to the emerge -DuN world.

   I tried using equery belongs /bin/loadkeys but it didn't find
anything, There seem to be a number of bugs that discuss this which
are a bit beyond my understanding of what to do, like this one:

http://bugs.gentoo.org/show_bug.cgi?id=232072

   I guess it's caused by some issue in baselayout and may be fixed in
a newer version. I can wait for the new version to become stable if
this won't cause any big problems but I cannot evaluate the severity
of this on my own.

   Comments? Can I leave it alone and not worry about problems?

Thanks,
Mark