You are not logged in.
Pages: 1
Hi all,
in an attempt to get uvesafb working, I have recompiled klibc against my kernel.
But when I reboot with the new image, I get a kernel panic.
-/init: 44: replace: not found
-/init: 44: replace: not found
export: 44: bad variable name
like this one, it seems I'm not the only one with the problem.
However, my setup is a bit different from what is specified in the afore-mentioned thread:
First of all, I am on kernel-2.6zen/x86_64 with UVESAFB compiled in permanently.
Then, here are snippets of the diverse files involved:
klibc-PKGBUILD:
pkgname=klibc
pkgver=1.5.8
_klibcbranch=Testing #Stable/Testing
_kver=2.6.24-zen
pkgrel=1
pkgdesc="a minimal libc made for early-userspace"
arch=(i686 x86_64)
url="http://www.kernel.org/pub/linux/libs/klibc/"
license=('BSD')
groups=('base')
options=(!ccache)
source=(http://www.kernel.org/pub/linux/libs/klibc/$_klibcbranch/$pkgname-$pkgver.tar.gz
multiple_raid_assembly_fix.patch
klibc-compile-shared-by-default.patch
klibc-module-init-tools.patch)
build()
{
cd $startdir/src/$pkgname-$pkgver
#INI_DEBUG causes ipconfig to fail within kinit
# sed -i "/#define INI_DEBUG/d" usr/kinit/kinit.h
ln -sf /usr/src/linux-${_kver} linux
# patch -p1 -i ../multiple_raid_assembly_fix.patch || return 1
# make klibc-module-init-tools compile
# don't build insmod
# patch -p1 -i ../klibc-module-init-tools.patch || return 1
# compile binaries shared by default
patch -p1 -i ../klibc-compile-shared-by-default.patch
make EXTRA_KLIBCFLAGS='' || return 1
make INSTALLROOT=$startdir/pkg install
#simplify
mv $startdir/pkg/usr/lib/klibc/bin/sh.shared $startdir/pkg/usr/lib/klibc/bin/sh
rm $startdir/pkg/usr/lib/klibc/bin/mknod
rm $startdir/pkg/usr/lib/klibc/bin/kill
}
md5sums=('22c7774f0022311fef8a4f30a1a37231'
'8d257d50a4554d57b8f461c6a87a2877'
'c263a7c3fd290fcc84a4e230d456d022'
'4d78311ebce63f2fbb711f8518e71839')
(on spock' site it says to better use klibc 1.5.8 upwards, this is in testing branch, and only the last patch from abs would apply cleanly.)
/etc/mkinitcpio.conf:
# All MODULES defs are commented out...
BINARIES="/sbin/modprobe"
FILES="/etc/modprobe.conf \
/usr/share/kbd/keymaps/i386/qwertz/de-latin1-nodeadkeys.map.gz \
/usr/share/kbd/unimaps/8859-15.a0-ff.uni \
/usr/share/kbd/consolefonts/lat0-16.psfu.gz"
HOOKS="base udev autodetect pata uvesafb keymap v86d userui uresume filesystems"
(v86d is provided b AUR/v86d which I have installed)
I suppose that the uvesafb hooks both aren't really needed when uvesafb is compiled in, but it shouldn't cause a kernel panic to leave'em there, should it? (It's somehow a leftover of the wiki, which describes how to set it up with a uvesafb module.)
Any hints on what the problem could be?
TIA
Offline
The kernel panic has nothing to do with uvesafb and the hooks, it is a problem between klibc and 2.6.24 kernels. If (as in some configurations) you can not use uvesafb without a recompiled klibc against 2.6.24, I think you have to wait until a fixed klibc is out. Till that moment, do not recompile klibc and (as a consequence) do not use uvesafb.
Mortuus in anima, curam gero cutis
Offline
I will update the wiki article to alert about this risk
Mortuus in anima, curam gero cutis
Offline
it is a problem between klibc and 2.6.24 kernels. [...] I think you have to wait until a fixed klibc is out. Till that moment, do not recompile klibc and (as a consequence) do not use uvesafb.
Just to make sure I understand it right: You're saying that even klibc 1.5.8 (from testing branch) probably/possibly hasn't fixed the issues yet (and thus 1.5.8 wouldn't fall in the "fixed klibc" category)?
Thanks for your help so far,
Andreas
Offline
Ugh, using something that is "in testing" to boot your system is never a good idea. That said, you MUST get the abs patches to apply if you want to do this. You're going to need both klibc-module-init-tools and klibc-extras.
Additionally, show me your kernel command line. You have a lone "44" in there somewhere which is breaking the mkinitcpio hooks.
Offline
Ugh, using something that is "in testing" to boot your system is never a good idea. That said, you MUST get the abs patches to apply if you want to do this. You're going to need both klibc-module-init-tools and klibc-extras.
ah. good to know. I'll see where they fail when I get to it. (I used that version because spock suggested "1.5.8 or newer" on his site. It's from December 11th, so I was hoping it'd be okay even tho still in testing branch. Well, that's what I have the testing boot image for...)
Additionally, show me your kernel command line. You have a lone "44" in there somewhere which is breaking the mkinitcpio hooks.
You mean /boot/grub/menu.lst:
...
# (2) Arch Zen Test
title Zen Test
root (hd0,2)
kernel /vmlinuz26zen showopts root=/dev/sda6 resume=/dev/sda8 video=uvesafb:1024x768-32 ro
initrd /kernel26zen-test.img
...
Also, in messages.log, it says:
Kernel command line: root=/dev/sda6 resume=/dev/sda8 video=uvesafb:1024x768-32 ro
I'm in non-testing mode now and will try to investigate further (get the exact error message and search for any 44's) when I find the time.
Offline
The problem for my opinion is in kernel 2.6.24, because if i compile klibc on kernel 2.6.24, recreated the mkinitcpio, and if i run on kernel 2.6.22 or 2.6.23, the kernel works fine, but only on 2.6.24 go in panic, with this error:
::Loading Initramfs
-/init: 44: replace: not found
-/init: 44: replace: not found
export: 44: bad variable name
.
I have tried with klibc 1.5-3 and with klibc 1.5.8.
Developer/TU: Can you resolve this bug ??
Last edited by ech0s7 (2008-02-14 15:30:01)
Offline
You're missing klibc-extras. I said that.
Offline
klibc-extras doesn't compiles on kernel 2.6.24, this is the log of makepkg for klibc-extras: http://pastebin.archlinux.org/28770 .
I have already write on bugs.archlinux: http://bugs.archlinux.org/task/9482
Offline
Have you solved this error??
Offline
didn't try again yet. time's too short these days.
Offline
I had the same problem with klibc-1.5-4 (which seems to be retracted) I had to upgrade to testing klibc-1.5-5 to solve it
Offline
Pages: 1