<cruxbot>
[opt/3.7]: [notify] thunderbird-bin: updated to version 115.8.0; security update
<cruxbot>
[opt/3.7]: bash-completion: updated to version 2.12.0
tarxvfz has quit [Quit: tarxvfz]
zorz_ has joined #crux
CleverTom has joined #crux
<CleverTom>
Hi there! I'm having an issue with starting X on a virtual machine (Virtualbox) install of CRUX. Since I don't have X, I don't think I can paste in my Xorg.0.log, but if you're any familiar with the
<CleverTom>
Sorry, pressed enter too early. Give me a second...
<CleverTom>
Anyways, if you're any familiar with the "keyboard initialization failed" error, that's what I've been getting. I've tried chmod 1777 on both /tmp and /var/tmp, as well as checking my disk space (I'm about 60% full), and both have done nothing. Reinstalling xorg-xkbcomp did nothing. I apologize sincerely if I'm being too vague here, but I don't have a single clue as to what's happening here; I've been
<CleverTom>
looking across several forum posts for a while now, to no avail.
<CleverTom>
Again, to be more specific about the error message, it's something like: "XKB: Could not invoke xkbcomp," then "XKB: Couldn't compiile keymap," then "Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config"
<CleverTom>
Yes, the latter package (xkeyboard-config) is installed; I have tried re-installing this package already.
<CleverTom>
I'm thinking that it might be some sort of error with xkbcomp itself, as, when I tried compiling a dummy .km file, I got an error to the effect of: "syntax error: line 17 of rules/evdev," then "errors encountered in rules/evdev; not compiled."
<CleverTom>
Someone on an archlinux forum also suggested "getting xkbcomp to work," by checking "permission PATH, and everything you can," but (at the risk of being or sounding like a total fool that doesn't belong here at all) I'm not so sure what to look for.
<remiliascarlet>
When compiling the Linux kernel, did you make sure to enable all Virtualbox related modules as well as modules related to your host hardware?
<CleverTom>
Oh dear
<CleverTom>
I don't think I did, and they're definitely not enabled by default
<CleverTom>
I guess I wasted your time, then
<CleverTom>
Sorry about that.
<remiliascarlet>
Yeah, nothing gets enabled by default. The kernel is just the stock kernel straight from kernel.org.
<remiliascarlet>
No need to re-install the distro, you can simply go to the kernel in /usr/src, and follow the steps to compile your kernel.
<remiliascarlet>
And then reboot of course.
<CleverTom>
I'm aware; I'm in the middle of that :)