Beige G3 minitower (again!)
OK, we're getting there. I've now got a 2.6.5 kernel compiled and
running, and some things definitely work better. The major issue at
the moment is that the keyboard doesn't work; the PCI display board
does, but it's a bit weird (more later).
I have the following config options set:
# Macintosh device drivers
# CONFIG_ADB_PMU is not set
# CONFIG_MAC_SERIAL is not set
# CONFIG_THERM_WINDTUNNEL is not set
# CONFIG_THERM_ADT746X is not set
# CONFIG_ANSLCD is not set
# Input device support
# Userland interfaces
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVBUG is not set
It's interesting to note that the help that comes with
CONFIG_INPUT_ADBHID says, among other things, that you also need to
set CONFIG_INPUT_KEYBDEV, but that option soesn't seem to exist in 2.6
kernels (except in the arm architecture, and that may be an error).
I still get nothing happening when I hit keyboard keys. Have I missed
something? And I've seen some references to having to map adb keys to
Linux: is this still necessary?
Now to the IMS Twin Turbo display. It does work, sort of. It's even
almost readable: the first two characters of each line are at the
right end of the screen, and the rest of the characters are on the
next line. It's like it does a line break two characters late. And,
no, it's not a screen positioning/foldover thing (wish it was: I know
how to fix that). Anyone seen this one before?
So for now I'm accessing the box via SSH or the serial console, and
most other things seem to be working. Boot is via BootX; maybe one day
I'll get quik working, but for now it auto-boots and that's all I
I did find that compiling a kernel can be trying: there seem to be a
lot of things that don't compile as modules but work fine when
included in the kernel.
Ron Murray (email@example.com)
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C D66B 8ADA A3C4 D86C 74DE