Version: (using KDE KDE 3.0.99)
Installed from: Gentoo Packages
Compiler: gcc (GCC) 3.2.1 20021207 (Gentoo Linux 3.2.1-20021207)
When I try to use the Linux Kernel Configurator in the KDE Control Panel, configuring kernel 2.5.52, I get the following error message:
cannot open /usr/src/linux-beta//arch/i386/config.in for reading
This is because there are no config.in files in this kernel tree - perhaps the kernel config file layout has changed? It would be useful for the control module to work with the development kernels, and indeed with the future 2.6 series.
(I don't know whether this is relevant, but I'm actually running kernel 2.4.19 at the moment, but trying to configure 2.5.52.)
Yes we haven't added support for the new kernel configuration system yet.
*** Bug 54271 has been marked as a duplicate of this bug. ***
2.5 kernel uses QT interface when you choose make xconfig.
Maybe that helps you until this bug is fixed.
This bug appears to be in the new 2.4 kernels as well. I tested kcmlinuz from
KDE 3.1.2 against 2.4.21-rc2-ac2 and it said:
The kernel configuration could not be read due to the following error:
cannot open /usr/src/kernel-source-2.4.21-rc2-ac2//arch//config.in for reading
Either your kernel sources contain invalid configuration rules or you just
found a bug in the KDE Kernel Configurator.
It also wouldn't show anything in the arch drop down box.
Here goes my suggest:
Add support for the newer kernels like 2.6.x, and add support for applying
patchs to kernel.
Yeah it would like to see this working too.
Would be nice to be able to configure my 2.6 kernel in kcontrol
Yes, I think about 20% use 2.6.x kernels.
Since 2.6.2 it runs on my machine.
Kernel 2.6 is standard in many new Distributions
(like: SuSE LINUX 9.1/9.2;Debian 3.1 sarge ...).
Now it's time for it!
Kernel 2.6 has been out for quite some time now. Seeing kcmlinuz say that it doesn't support kernel 2.5 or higher is a bit strange. If nobody can update it to support current kernels, maybe you should consider removing that module?
I couldn't agree more with the previous comment: fix it or drop it.
This is not meant as an offense, it's just that kcmlinuz is totally outdated and reflects badly on the excellent overall quality of the control center.
Should this bug then be closed as "INVALID"? Please see http://lists.kde.org/?l=kde-core-devel&m=110727153114866&w=2
The bug is valid and releasecritical.
kcmlinuz should be removed from stable sources and remain in beta until someone fixes this bug.
Uhm, follow the link. It's exactly because it -was- removed from release sources. And no, this is not release critical at all.
Closed because of removal from source package.