Open ghost opened 2 years ago
Hello,
The kernel actually has a config entry for exposing its config file through sysfs. My first guess is that your running kernel has that option disabled or the config is exposed at a non standard location.
Hello,
The kernel actually has a config entry for exposing its config file through sysfs. My first guess is that your running kernel has that option disabled or the config is exposed at a non standard location.
I know where my kernel config is (/boot/config-lts/), so how do I force the script to go to the right place?
Is that a standard location or user-set ?
Simply copy the config from there to a file somewhere and use the _configfile
option in the customization.cfg
file to refer to it.
Also, I believe /boot/config-lts
is the path where the config gets installed along with the kernel no ? Or is that really the path where the running kernel actually exposes its config ? Which means the file there is different for each kernel you boot?
Also, I believe
/boot/config-lts
is the path where the config gets installed along with the kernel no ? Or is that really the path where the running kernel actually exposes its config ? Which means the file there is different for each kernel you boot?
Not sure if it's a static config file or if it's the running kernel's config, can't really test it without having multiple kernels installed, and unfortunately Alpine doesn't provide any options to install prebuilt kernels other than the one that comes with the iso. Regardless, I followed the steps to provide my own config and I'm getting further in the install, but now it doesn't know where to get ncurses (Yes, I have it installed.)
[Installation is normal up until this point...]
-> Setting config
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/confdata.o
HOSTCC scripts/kconfig/expr.o
LEX scripts/kconfig/lexer.lex.c
YACC scripts/kconfig/parser.tab.[ch]
HOSTCC scripts/kconfig/lexer.lex.o
HOSTCC scripts/kconfig/menu.o
HOSTCC scripts/kconfig/parser.tab.o
HOSTCC scripts/kconfig/preprocess.o
HOSTCC scripts/kconfig/symbol.o
HOSTCC scripts/kconfig/util.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
*
* Unable to find the ncurses package.
* Install ncurses (ncurses-devel or libncurses-dev
* depending on your distribution).
*
* You may also need to install pkg-config to find the
* ncurses installed in a non-default location.
*
make[1]: *** [scripts/kconfig/Makefile:212: scripts/kconfig/mconf-cfg] Error 1
make: *** [Makefile:628: menuconfig] Error 2
-> exit cleanup done
alpine:~/linux-tkg$
[END]
Seems like a running theme of Alpine having everything needed to work, but the script not knowing where to find it. It DOES detect ncurses properly when I tried to use the arch installation again, so I guess I'll try to compile it that way in the meantime?
Well nevermind! The ncurses tui doesn't load for some reason when using makepkg -si, though I still get the crappy CLI configuration thing. Yippee.
Do you have pkg-config installed and available, as it suggests ? Although ncurses may not have pkg-config entry 🤔
Otherwise, you can look up where the ncurses .so file is and add its parent folder in the LD_LIBRARY_PATH environment variable.
Uh... weird thing. When I use the default archlinux config file provided, make menuconfig works fine (probsbly won't boot, since systemd definitely isn't gonna work with openrc, so I won't compile that) and doing the stuff you suggested didn't help when I used my own. So... I guess I'll just go without configuring the kernel for now and try to build it now?
Finished compiling. Kernel won't boot. There's a chance that me pressing enter on all of the config prompts didn't actually draw from my provided config, though I didn't pay attention to check. Had this same issue when trying to run the zen kernel; during the initialization nothing happens and the cursor doesn't blink. Odd stuff...
Both the generic install and the arch install (more on that later) fail to grab the running-kernel config, and the installation promptly exits thereafter. The script command does not seem to exist on Alpine Linux, and neither does shell-output.log, and checks for it prevent the installation from running without some tweaking... (See below...)
Distro: Alpine Linux, hijacked with bedrock and Artix stratum added. Using "edge" repositories (latest releases of available Alpine packages) Arch repos are enabled in the pacman.conf. (More on that later...)
The issue: The generic install.sh refuses to start without hacking the shell script, and it cannot detect the config file of the running kernel.
When I use the Arch install, I do not have to hack the shell script, but it still cannot detect the config file of the running kernel. (Skipping over some more complicated stuff that isn't relevant right now, Bedrock allow me to basically meld Artix, and by proxy, Arch, into Alpine, with all of their tools and pacman included.)
(shell-output.log inherently cannot be provided. This is what I meant by hacking the shell script; the section at the start of the install.sh that deals with shell-output.log needed to be deleted in order to start the generic install.)
All other elements of the installation up until it failed to grab the running kernel config appeared to work just fine. The installation then stopped there before it could continue.
Here's what happened in the cli, I guess. More context available here --> https://www.reddit.com/r/AlpineLinux/comments/vyazb8/what_am_i_missing_installing_tkg_kernel/
[START]
[END]