Bug#248855: Useful clues for non-working USB keyboard on SunBlade 150 / sparc64

[Vincent.McIntyre@csiro.au]

> langagechooser runs before kbd-chooser so kbd-chooser bugfixes cannot
> apply to it. I had thought your keyboard was working before you got to
> kbd-chooser; if not it's probably a bug in the kernel/lack of loading
> the right module for a usb keyboard.
>

when does usb-discover run ? At first I thought: "well after
languagechooser". But now I'm not so sure.
I mention it because I noticed there is provision for detecting that
usb-ohci needs to be loaded, but the relevant config file seems to
be empty. (d-i/packages/usb-discover/ohci-pci.lst)

I scratched around the d-i tree, and from looking at
 lib/debian-installer-startup.d/ it seems it must run quite early.
But it seems kbd-chooser also runs at this time ... mph, me confused.
(NB I have been building x86 mini-isos, maybe this is all irrelevant)

$ ls \
d-i/installer/build/tmp/monolithic/tree/lib/debian-installer-startup.d

S01mount           S30read-environment  S40framebuffer-module-linux-x86
S05acpi-linux-x86  S33usb-linux         S55kbd-chooser
S10syslog          S35term
S20templates       S38lowmem

Although the README for usb-discover say it relies mainly on the normal
discover1 database,  I'm not seeing how that happens for modules like
usb-ohci. Is it that when usb-discover modprobes in usbkbd, hid and
keybdev, some modules.dep magic loads the correct module?

Cheers
Vince