New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
otakutyrant opened this issue
Feb 15, 2021
· 31 comments
Comments
I would like to provide a detailed report but I am away from my PC and posting this issue on my phone instead. Actually I think it is needless to explicate it so far because today the new version of glibic is released so that thereafter everyone who have once updated their system will, maybe, encounter the same issue. I think it may be time to update the kernel of ArchWSL and release it.
Update: The specific issue is that when you upgrade the system, you will encounter «FATAL: kernel too old» after the update of glibc and some programs (maybe because they are depended on it?) and every prompt in a Shell.
had the same issue, at the end «solved» by updating the kernel with these instructions and switching to WSL 2
had the same issue, at the end «solved» by updating the kernel with these instructions and switching to WSL 2
Is it possible for me to stay on wsl1? Since wsl2 has terrible IO performance on Windows disks, a simple git status can take more 10 seconds.
It’s most likely due to glibc 2.33-4 update which happened today.
I have the same issue, arch wsl conldn’t work after glibc update.
just a work around if you want to use WSL 1:
I switched to WSL 2, changed my pacman mirror to point to the 31st of January archive
Server = https://archive.archlinux.org/repos/2021/01/31/$repo/os/$arch
and reverted all of my packages to that point with pacman -Syyuu.
I bricked my WSL install a couple of times in the process, so try at your own risk.
had the same issue, at the end «solved» by updating the kernel with these instructions and switching to WSL 2
I studied those instructions and found out installing a preview build of Windows 10 is required but I do not want to put my working computer at risk of using an unstable system. It can’t be helped.
I googled how to upgrade the kernel of WSL but no useful information was found.
Set your distribution version to WSL 2:
wsl -l -v
NAME STATE VERSION
* Arch Stopped 1
wsl --set-version Arch 2
If version still shows 1, run the following and reboot:
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
Run wsl --set-version Arch 2 again.
Conversion in progress, this may take a few minutes...
If update successful, wsl -l -v will list as version 2:
wsl -l -v
NAME STATE VERSION
* Arch Stopped 2
For those who want to stay at WSL1 and want to fix the problem, a simple (also risky) solution is to overwrite the WSL installation directly with the old glibc package.
Update: Please follow the #190 (comment) for more detailed steps.
In detail, use the /usr part from glibc-2.33-3 to overwrite your WSL installation, then you can get into it and downgrade glibc-2.33-4 to glibc-2.33-3. Remember to modify pacman.conf to ignore subsequent upgrades of glibc.
It is important to reiterate that there are risks associated with this operation, such as the permissions of the replaced files being reset. Although in my case these file permissions would be reset to 777, making it possible to go into WSL and reinstall glibc. After reinstallation these permissions will be corrected.
According to this document, permissions are stored in NTFS extended attributes. Using some specific way to overwrite (e.g. dd) can preserve NTFS extended attributes, which is also safer.
For those who want to stay at WSL1 and want to fix the problem, a simple (also risky) solution is to overwrite the WSL installation directly with the old glibc package.
In detail, use the
/usrpart from glibc-2.33-3 to overwrite your WSL installation, then you can get into it and downgradeglibc-2.33-4toglibc-2.33-3. Remember to modifypacman.confto ignore subsequent upgrades of glibc.It is important to reiterate that there are risks associated with this operation, such as the permissions of the replaced files being reset. Although in my case these file permissions would be reset to
777, making it possible to go into WSL and reinstall glibc. After reinstallation these permissions will be corrected.According to this document, permissions are stored in NTFS extended attributes. Using some specific way to overwrite (e.g. dd) can preserve NTFS extended attributes, which is also safer.
I had tried this myself, but by overwriting all the files of glibc package, and unfortunately it broke the installation even further. I now tried to overwrite all files from glibc-2.33-4 (to restore a «clean» state) and then /usr files only from glibc-2.33-3, but it is still broken (shell immediately closes).
In the end I had to install a new instance of Arch and set the server to the archive as suggested by @claudiocabral. Packages from the 14th of February are still ok.
Server = https://archive.archlinux.org/repos/2021/02/14/$repo/os/$arch
Very annoying I had to reinstall/reconfigure everything though.
After more testing, I have refined that solution. Here are the steps.
- Make a another WSL1 installation, no matter what distro is. Get into it when you finshied the install.
- Remount the drive with featrue
metadatawhere your broken ArchWSL installation is located. If it is on driveC:it should be:
sudo umount /mnt/c
sudo mount -t drvfs C: /mnt/c -o metadata - Get glibc-2.33-3 and extract it with tar. Be careful to keep the permissions correct. For example:
sudo tar --zstd -xf glibc-2.33-3-x86_64.pkg.tar.zst - Overwrite the
/usrpart with the extracted package. Remember to change to your specific location.
sudo cp -r --preserve=all --force <Extracted Pakage>/usr/ <Broken ArchWSL Location>/rootfs/ - Restart the service
LxssManager. This can force a file system refresh, which may be delayed in some cases. Please note that this will stop all WSL instances. - You should be able to get into the broken ArchWSL.
The whole point of the process is to make sure that the replaced files have proper permissions. While this may be the safest steps, please note that it still carries risks. You can also try upgrading to WSL2 first, downgrading glibc and then downgrade to WSL1. This should work too.
There is also a glibc-linux4 from AUR.
Enter-tainer, otakutyrant, Moret84, Varun-garg, and ArchGuyWu reacted with heart emoji
For those who want to stay at WSL1 and want to fix the problem, a simple (also risky) solution is to overwrite the WSL installation directly with the old glibc package.
In detail, use the/usrpart from glibc-2.33-3 to overwrite your WSL installation, then you can get into it and downgradeglibc-2.33-4toglibc-2.33-3. Remember to modifypacman.confto ignore subsequent upgrades of glibc.
It is important to reiterate that there are risks associated with this operation, such as the permissions of the replaced files being reset. Although in my case these file permissions would be reset to777, making it possible to go into WSL and reinstall glibc. After reinstallation these permissions will be corrected.
According to this document, permissions are stored in NTFS extended attributes. Using some specific way to overwrite (e.g. dd) can preserve NTFS extended attributes, which is also safer.I had tried this myself, but by overwriting all the files of glibc package, and unfortunately it broke the installation even further. I now tried to overwrite all files from
glibc-2.33-4(to restore a «clean» state) and then/usrfiles only fromglibc-2.33-3, but it is still broken (shell immediately closes).In the end I had to install a new instance of Arch and set the server to the archive as suggested by @claudiocabral. Packages from the 14th of February are still ok.
Server = https://archive.archlinux.org/repos/2021/02/14/$repo/os/$archVery annoying I had to reinstall/reconfigure everything though.
I also tested that the shell immediately closes may be because the overwritten file permissions have been reset to unreadable or unexecutable.
If you still want to try to fix it, consider referring to the new comment I just posted. Following that should ensure that the overwritten files have the correct permissions from the start. You may need to overwrite with the entire package since you’ve done that before.
@dynxer thanks, will try for sure in the next days
@dynxer
- Overwrite the
/usrpart with the extracted package. Remember to change to your specific location.
sudo cp -r --preserve=all --force <Extracted Pakage>/usr/ <Broken ArchWSL Location>/rootfs/
I checked my location C:Users86139AppDataLocalPackages but I am not sure what directory is the ArchWSL location. No directory contains «Arch». Ony that Canical.Unbuntu contains rootfs when I searched the latter. Any idea?
I have a sneaking suspiction that my ArchWSL is overwrited by Ubuntu which I have just installed in order to follow @dynxer steps. However it still returns the FATAL error when I open Powershell and execute wsl.
@dynxer
- Overwrite the
/usrpart with the extracted package. Remember to change to your specific location.
sudo cp -r --preserve=all --force <Extracted Pakage>/usr/ <Broken ArchWSL Location>/rootfs/I checked my location
C:Users86139AppDataLocalPackagesbut I am not sure what directory is the ArchWSL location. No directory contains «Arch». Ony that Canical.Unbuntu containsrootfswhen I searched the latter. Any idea?
The rootfs location should under the folder where you extract the ArchWSL installer zip.
I have a sneaking suspiction that my ArchWSL is overwrited by Ubuntu which I have just installed in order to follow @dynxer steps. However it still returns the FATAL error when I open Powershell and execute
wsl.
If you still get FATAL, this means that ArchWSL has not been overwrited. You can check your all WSL installation with wsl -l
The
rootfslocation should under the folder where you extract the ArchWSL installer zip.
Okay, I found my ArchWSL location. Let me try again.
If you still get FATAL, this means that ArchWSL has not been overwrited. You can check your all WSL installation with
wsl -l
You are right. My wsl -l shows that there are ArchWSL, regarded as default, and Ubuntu.
My ArchWSL reborned successfully! I thought arch-chroot but I didn’t know where to chroot into. Now @dynxer dispensed a viable way. Thanks a lot!
It seems microsoft never update WSL1 kernel version, so if we do not want to use WSL2, we need keep glibc to IgnorePkg in /etc/pacman.conf. Since glibc-2.33-3 works well, but glibc-2.33-4 break the system, maybe next version glibc will not complain kernel version too old? just a hope…
To fix the problem temporarily, just download a pacman-static and ./pacman-static -U /var/cache/pacman/pkg/glibc-2.33-3-x86_64.pkg.tar.zst
I really do not like WSL2, which memory usage is a hell, I am really upset now.
ArchLinux will never have a plan to solve it, see here
Archlinux on WSL is not Archlinux? I think Archlinux on WSL is just an Archlinux with one package replaced, which names is linux.
While microsoft update is very slow, and it seems WSL1 kernel is not updated for a long time. And more, see here, Recent release notes are all about WSL2! although microsoft says «WSL1 is not abandoned»,
just a work around if you want to use WSL 1:
I switched to WSL 2, changed my pacman mirror to point to the 31st of January archive
Server = https://archive.archlinux.org/repos/2021/01/31/$repo/os/$arch
and reverted all of my packages to that point withpacman -Syyuu.
I bricked my WSL install a couple of times in the process, so try at your own risk.
Thanks very much! This did work. For China users, TUNA has provided an Arch Linux Rollback Machine. I successfully recovered my access to Archlinux on WSL1 using the mirror below.
Server = https://arch-archive.tuna.tsinghua.edu.cn/2021/02-08/$repo/os/$arch
In case you don’t want to deal with separate files and risk breaking your machine more than it already is, while it no longer starts up, here’s what you can do:
- In PowerShell list your distributions
wsl -l -v - Then run the export command
wsl --export <distro name from above command> Arch.tar - Copy the .tar file to ANY linux machine. I happened to have a VirtualBox running another Arch instance so I went there.
- In the Linux machine, create a new directory, go there, and run this command
sudo tar --same-owner -xvpf /path/to/Arch.tar - Now that you have your full wsl machine in a directory, chroot to it:
sudo chroot . /bin/bash -i - Download the working glibc:
wget https://archive.archlinux.org/packages/g/glibc/glibc-2.33-3-x86_64.pkg.tar.zst - Install the working glibc:
pacman -U glibc-2.33-3-x86_64.pkg.tar.zst - Test if 2.33-3 is installed:
pacman -Qi glibc - Edit
/etc/pacman.confand add glibc toIgnorePkg, for example:IgnorePkg = fakeroot glibc - Clean up
rm glibc-2.33-3-x86_64.pkg.tar.zst - re-tar your directory
sudo tar --same-owner -cvpf ../Arch2.tar . - Copy the new tar file to the Windows machine with wsl troubles
- Unregister the old distribution if you want to re-use the name
wsl --unregister <distro name> - Import the «fixed» distribution (you also get to choose where it’s storing the rootfs and temp directories):
wsl --import <distro name you want to use> M:wslArch C:PathToArch2.tar - Your wsl is ready and working. But you it’s like a new WSL, so you need to apply any old configuration you have, for example:
Arch.exe config --default-user {username}
$ pacman -Qi glibc
Name : glibc
Version : 2.33-3
$ sudo pacman -Syuu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: fakeroot: ignoring package upgrade (1.25.3-1 => 1.25.3-2)
warning: glibc: ignoring package upgrade (2.33-3 => 2.33-4)
there is nothing to do
Updated for both new WslFS and old LxFS
There is another method which do not need another Linux or WSL distro.
- If you have update to glibc-2.34 or greater, do not below, upgrade to WSL2 or reinstall
- Download https://archive.archlinux.org/packages/g/glibc/glibc-2.33-3-x86_64.pkg.tar.zst
- Use https://github.com/mcmilk/7-Zip-zstd/ to extract files in
glibc*.zst/usr/lib/below to a temp dird:usrlibfor example
ld-2.33.so
libc-2.33.so
libdl-2.33.so
libm-2.33.so
libpthread-2.33.so
libresolv-2.33.so
librt-2.33.so
libutil-2.33.so
- Use https://github.com/viruscamp/lxssattr/ in cmd to copy correct posix attrib to copied files
> cd <Your WSL Distro Folder>rootfsusrlib
# found a valid source file , make sure the file is Ownership(Uid: (0 / ), Gid: (0 / )) and Access((0755) -rwxr-xr-x)
> lxssattr libdl-2.33.so
# output for new WslFS
$LXUID: Uid: (0 / )
$LXGID: Gid: (0 / )
$LXMOD: Mode: 100755 (octal)
Access: (0755) -rwxr-xr-x
# output for old LxFS
LXATTRB:
Flags: 0
Version: 1
Mode: 100755 (octal)
Ownership: Uid: (0 / ), Gid: (0 / )
Access: (0755) -rwxr-xr-x
Last status change: 2019-11-19 18:29:52.102270300 +0800
Last file access: 2019-11-19 18:29:52.000000000 +0800
Last file modification: 2019-11-14 01:57:46.000000000 +0800
# copy and set files listed in step 2
> copy d:usrlibld-2.33.so .
> lxssattr libdl-2.33.so ld-2.33.so
> copy d:usrliblibc-2.33.so .
> lxssattr libdl-2.33.so libc-2.33.so
# last one, change a source
> copy d:usrliblibdl-2.33.so .
> lxssattr ld-2.33.so libdl-2.33.so
- Restart Windows service LxssManager
- Now you can open bash of ArchWSL. Let’s follow @apisarenco ‘s advices FATAL: kernel too old #190 (comment)
- Install the working glibc:
pacman -U glibc-2.33-3-x86_64.pkg.tar.zst - Test if 2.33-3 is installed:
pacman -Qi glibc - Edit /etc/pacman.conf and add glibc to IgnorePkg, for example: IgnorePkg = fakeroot glibc
- Done. It’s OK to do:
sudo pacman -Syuu
There is another method which do not need another Linux or WSL distro.
- Download https://archive.archlinux.org/packages/g/glibc/glibc-2.33-3-x86_64.pkg.tar.zst
- Use https://github.com/mcmilk/7-Zip-zstd/ to extract files below to /rootfs/usr/lib
/usr/lib/ld-2.33.so /usr/lib/libc-2.33.soMake sure the files are overwritten, otherwise you have to fix the symbol links.
- Use https://github.com/viruscamp/lxssattr/ to copy correct posix attrib to copied files
> cd <Your WSL Distro Folder>rootfsusrlib > lxssattr libdl-2.33.so Flags: 0 Version: 1 Mode: 100755 (octal) Ownership: Uid: (0 / ), Gid: (0 / ) Access: (0755) -rwxr-xr-x Last status change: 2021-02-27 12:29:53.349915600 +0800 Last file access: 2021-02-27 12:29:53.000000000 +0800 Last file modification: 2021-02-06 08:09:35.000000000 +0800 > lxssattr libdl-2.33.so ld-2.33.so > lxssattr libdl-2.33.so libc-2.33.soMake sure the source file has the same Ownership(Uid: (0 / ), Gid: (0 / )) and Access((0755) -rwxr-xr-x)
- Restart Windows service LxssManager
- Now you can open bash of ArchWSL. Let’s follow @apisarenco ‘s advices #190 (comment)
- Install the working glibc: pacman -U glibc-2.33-3-x86_64.pkg.tar.zst
- Test if 2.33-3 is installed: pacman -Qi glibc
- Edit /etc/pacman.conf and add glibc to IgnorePkg, for example: IgnorePkg = fakeroot glibc
- Done. It’s OK to do: sudo pacman -Syuu
This saved my WSL. However, I encountered errors when using lxssattr
[ERROR] NtQueryEaFile: 0xc0000052
But the operation seems succeeded anyway, so if anyone have met the same issue just don’t worry. After some searching I learned what that lxssattr command do is copying the file attributes including the permissions so that Permission denied won’t be thrown during loading libraries. Thus, when you lxssattr ld-2.33.so and lxssattr libc-2.33.so and it reports permission 755 , it means the operations succeeded.
ArchWSL installed as WSL1 recently used the new WslFS file system, for which old version of lxssattr is invalid.
ArchWSL installed long ago is still using the old LxFS file system, for which old version of lxssattr is valid. You may use wslconfig /upgrade <distro> change to WslFS.
As microsoft/WSL#1744 (comment) said:
Before the upgrade LxFs files used LXATTRB extended attribute to store the permissions but now both use LXGID LXMOD and LXUID.
#1 2011-01-24 13:04:06
- a.san
- Member
- Registered: 2008-05-22
- Posts: 5
Didn’t update for so long, and now «Kernel is too old»
I had a pacman -Syu after a long time and now the system is completely unusable:
# ls
FATAL: kernel too old
# cat
FATAL: kernel too oldSince I can’t even cat the logs, I’ll paste the screen report of the installation:
# pacman -Syu
:: Synchronizing package databases...
core 36.6K 84.6K/s 00:00:00 [#######################################################] 100%
extra 461.2K 177.4K/s 00:00:03 [#######################################################] 100%
community-testing 12.6K 87.8K/s 00:00:00 [#######################################################] 100%
community 417.8K 263.1K/s 00:00:02 [#######################################################] 100%
archlinuxfr 26.3K 117.2K/s 00:00:00 [#######################################################] 100%
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
resolving dependencies...
looking for inter-conflicts...
Targets (1): pacman-3.4.2-1
Total Download Size: 0.69 MB
Total Installed Size: 2.39 MB
Proceed with installation? [Y/n]
:: Retrieving packages from core...
pacman-3.4.2-1-x86_64 708.0K 418.4K/s 00:00:02 [#######################################################] 100%
checking package integrity...
(1/1) checking for file conflicts [#######################################################] 100%
(1/1) upgrading pacman [#######################################################] 100%
# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community-testing is up to date
community is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
warning: ruby: ignoring package upgrade (1.9.1_p429-1 => 1.9.2_p136-2)
resolving dependencies...
looking for inter-conflicts...
Targets (109): linux-api-headers-2.6.36.2-1 tzdata-2010o-1 glibc-2.12.2-2 attr-2.4.44-2 acl-2.2.49-2 ncurses-5.7-4 readline-6.1.002-2 bash-4.1.009-3
gdbm-1.8.3-8 gcc-libs-4.5.2-4 db-5.1.19-3 zlib-1.2.5-3 cracklib-2.8.18-1 pam-1.1.3-1 gmp-5.0.1-2 libcap-2.19-2 coreutils-8.9-1
perl-5.12.2-1 automake-1.11.1-2 binutils-2.21-2 run-parts-3.4.1-1 openssl-1.0.0.c-1 findutils-4.4.2-3 sed-4.2.1-3
ca-certificates-20090814+nmu2-1 cloog-ppl-0.15.10-2 libusb-1.0.8-1 libusb-compat-0.1.3-1 pcre-8.12-1 glib2-2.26.1-1
module-init-tools-3.12-2 pciutils-3.1.7-2 udev-165-1 device-mapper-2.02.79-1 popt-1.16-3 cryptsetup-1.2.0-1 curl-7.21.3-1
dash-0.5.6.1-2 dhcpcd-5.2.9-1 diffutils-3.0-2 e2fsprogs-1.41.14-1 elfutils-0.150-1 expat-2.0.1-6 filesystem-2010.12-1
fakeroot-1.14.5-1 file-5.05-1 freetype2-2.4.4-2 gawk-3.1.8-2 mpfr-3.0.0.p8-1 libmpc-0.8.2-3 gcc-4.5.2-4 gen-init-cpio-2.6.36-1
perl-error-0.17016-2 git-1.7.3.5-2 gzip-1.4-2 texinfo-4.13a-5 groff-1.21-1 hdparm-9.36-1 sqlite3-3.7.4-1 libsasl-2.1.23-5
libldap-2.4.23-1 heimdal-1.3.3-4 tar-1.25-1 libtool-2.4-2 libsm-1.2.0-1 xproto-7.0.20-1 libx11-1.4.1-1 libxt-1.0.9-1 libxext-1.2.0-1
imagemagick-6.6.6.10-2 inetutils-1.8-2 initscripts-2010.07-2 iptables-1.4.10-1 irssi-0.8.15-4 jfsutils-1.1.14-2 less-436-2
libjpeg-8.3.0-1 libmysqlclient-5.1.54-1 libpcap-1.1.1-2 libpng-1.4.5-1 libxdmcp-1.1.0-1 libxml2-2.7.8-1 lzo2-2.04-1 man-db-2.5.9-1
man-pages-3.32-1 mlocate-0.23.1-2 mysql-clients-5.1.54-1 mysql-5.1.54-1 nano-2.2.6-1 nginx-0.8.54-1 libedit-20090923_3.0-1
openssh-5.6p1-2 pacman-mirrorlist-20101223-1 patch-2.6.1-2 php-5.3.5-1 php-cgi-5.3.5-1 php-curl-5.3.5-1 php-gd-5.3.5-1
pkg-config-0.25-3 procinfo-ng-2.0.304-2 procps-3.2.8-3 python-3.1.3-1 reiserfsprogs-3.6.21-3 screen-4.0.3-10 sdparm-1.06-1
sudo-1.7.4.p6-1 syslog-ng-3.2.1-1 usbutils-001-2 which-2.20-4
Total Download Size: 112.34 MB
Total Installed Size: 619.29 MB
Proceed with installation? [Y/n]
:: Retrieving packages from core...
linux-api-headers-2.6.36.2-1-x86_64 542.1K 341.4K/s 00:00:02 [#######################################################] 100%
tzdata-2010o-1-x86_64 179.8K 154.4K/s 00:00:01 [#######################################################] 100%
glibc-2.12.2-2-x86_64 7.2M 1509.9K/s 00:00:05 [#######################################################] 100%
attr-2.4.44-2-x86_64 63.6K 117.8K/s 00:00:01 [#######################################################] 100%
acl-2.2.49-2-x86_64 132.6K 154.9K/s 00:00:01 [#######################################################] 100%
ncurses-5.7-4-x86_64 918.1K 518.1K/s 00:00:02 [#######################################################] 100%
readline-6.1.002-2-x86_64 289.0K 200.7K/s 00:00:01 [#######################################################] 100%
bash-4.1.009-3-x86_64 715.9K 202.9K/s 00:00:04 [#######################################################] 100%
gdbm-1.8.3-8-x86_64 35.5K 86.9K/s 00:00:00 [#######################################################] 100%
gcc-libs-4.5.2-4-x86_64 594.4K 373.4K/s 00:00:02 [#######################################################] 100%
db-5.1.19-3-x86_64 1085.7K 695.9K/s 00:00:02 [#######################################################] 100%
zlib-1.2.5-3-x86_64 78.2K 141.7K/s 00:00:01 [#######################################################] 100%
cracklib-2.8.18-1-x86_64 238.4K 238.4K/s 00:00:01 [#######################################################] 100%
pam-1.1.3-1-x86_64 618.8K 419.2K/s 00:00:01 [#######################################################] 100%
gmp-5.0.1-2-x86_64 422.9K 339.9K/s 00:00:01 [#######################################################] 100%
libcap-2.19-2-x86_64 32.7K 87.8K/s 00:00:00 [#######################################################] 100%
coreutils-8.9-1-x86_64 2009.9K 1144.5K/s 00:00:02 [#######################################################] 100%
perl-5.12.2-1-x86_64 12.5M 1471.6K/s 00:00:09 [#######################################################] 100%
automake-1.11.1-2-any 524.8K 381.4K/s 00:00:01 [#######################################################] 100%
binutils-2.21-2-x86_64 3.2M 772.0K/s 00:00:04 [#######################################################] 100%
run-parts-3.4.1-1-x86_64 7.8K 62.6K/s 00:00:00 [#######################################################] 100%
openssl-1.0.0.c-1-x86_64 3.6M 758.0K/s 00:00:05 [#######################################################] 100%
findutils-4.4.2-3-x86_64 370.3K 329.4K/s 00:00:01 [#######################################################] 100%
sed-4.2.1-3-x86_64 108.7K 175.3K/s 00:00:01 [#######################################################] 100%
ca-certificates-20090814+nmu2-1-any 108.8K 173.2K/s 00:00:01 [#######################################################] 100%
cloog-ppl-0.15.10-2-x86_64 112.6K 181.6K/s 00:00:01 [#######################################################] 100%
libusb-1.0.8-1-x86_64 42.8K 113.9K/s 00:00:00 [#######################################################] 100%
libusb-compat-0.1.3-1-x86_64 12.8K 94.2K/s 00:00:00 [#######################################################] 100%
pcre-8.12-1-x86_64 511.0K 325.0K/s 00:00:02 [#######################################################] 100%
glib2-2.26.1-1-x86_64 1527.8K 560.8K/s 00:00:03 [#######################################################] 100%
module-init-tools-3.12-2-x86_64 348.8K 245.6K/s 00:00:01 [#######################################################] 100%
pciutils-3.1.7-2-x86_64 219.6K 191.2K/s 00:00:01 [#######################################################] 100%
udev-165-1-x86_64 229.1K 249.0K/s 00:00:01 [#######################################################] 100%
device-mapper-2.02.79-1-x86_64 119.2K 138.6K/s 00:00:01 [#######################################################] 100%
popt-1.16-3-x86_64 58.7K 117.4K/s 00:00:01 [#######################################################] 100%
cryptsetup-1.2.0-1-x86_64 87.6K 164.7K/s 00:00:01 [#######################################################] 100%
dash-0.5.6.1-2-x86_64 69.5K 120.6K/s 00:00:01 [#######################################################] 100%
dhcpcd-5.2.9-1-x86_64 61.3K 112.7K/s 00:00:01 [#######################################################] 100%
diffutils-3.0-2-x86_64 274.7K 241.0K/s 00:00:01 [#######################################################] 100%
e2fsprogs-1.41.14-1-x86_64 571.1K 389.0K/s 00:00:01 [#######################################################] 100%
elfutils-0.150-1-x86_64 551.5K 294.0K/s 00:00:02 [#######################################################] 100%
expat-2.0.1-6-x86_64 103.8K 163.2K/s 00:00:01 [#######################################################] 100%
filesystem-2010.12-1-any 4.1K infG/s 00:00:00 [#######################################################] 100%
fakeroot-1.14.5-1-x86_64 47.0K 126.4K/s 00:00:00 [#######################################################] 100%
file-5.05-1-x86_64 196.5K 224.3K/s 00:00:01 [#######################################################] 100%
gawk-3.1.8-2-x86_64 686.5K 445.8K/s 00:00:02 [#######################################################] 100%
mpfr-3.0.0.p8-1-x86_64 324.4K 289.6K/s 00:00:01 [#######################################################] 100%
libmpc-0.8.2-3-x86_64 61.0K 122.1K/s 00:00:01 [#######################################################] 100%
gcc-4.5.2-4-x86_64 16.3M 1620.9K/s 00:00:10 [#######################################################] 100%
gen-init-cpio-2.6.36-1-x86_64 5.6K 45.3K/s 00:00:00 [#######################################################] 100%
gzip-1.4-2-x86_64 73.4K 146.8K/s 00:00:01 [#######################################################] 100%
texinfo-4.13a-5-x86_64 674.1K 492.7K/s 00:00:01 [#######################################################] 100%
groff-1.21-1-x86_64 2.4M 1065.6K/s 00:00:02 [#######################################################] 100%
hdparm-9.36-1-x86_64 64.2K 128.5K/s 00:00:01 [#######################################################] 100%
sqlite3-3.7.4-1-x86_64 362.7K 323.8K/s 00:00:01 [#######################################################] 100%
libsasl-2.1.23-5-x86_64 87.4K 139.2K/s 00:00:01 [#######################################################] 100%
libldap-2.4.23-1-x86_64 357.3K 319.0K/s 00:00:01 [#######################################################] 100%
heimdal-1.3.3-4-x86_64 1874.8K 935.5K/s 00:00:02 [#######################################################] 100%
tar-1.25-1-x86_64 559.6K 411.4K/s 00:00:01 [#######################################################] 100%
libtool-2.4-2-x86_64 377.7K 261.6K/s 00:00:01 [#######################################################] 100%
inetutils-1.8-2-x86_64 275.1K 218.4K/s 00:00:01 [#######################################################] 100%
initscripts-2010.07-2-x86_64 14.2K 47.8K/s 00:00:00 [#######################################################] 100%
iptables-1.4.10-1-x86_64 253.9K 218.9K/s 00:00:01 [#######################################################] 100%
jfsutils-1.1.14-2-x86_64 166.5K 176.4K/s 00:00:01 [#######################################################] 100%
less-436-2-x86_64 87.4K 121.4K/s 00:00:01 [#######################################################] 100%
libpcap-1.1.1-2-x86_64 174.9K 193.5K/s 00:00:01 [#######################################################] 100%
lzo2-2.04-1-x86_64 59.0K 107.6K/s 00:00:01 [#######################################################] 100%
man-db-2.5.9-1-x86_64 433.1K 250.6K/s 00:00:02 [#######################################################] 100%
man-pages-3.32-1-any 4.3M 1198.4K/s 00:00:04 [#######################################################] 100%
mlocate-0.23.1-2-x86_64 74.8K 103.9K/s 00:00:01 [#######################################################] 100%
nano-2.2.6-1-x86_64 300.9K 232.2K/s 00:00:01 [#######################################################] 100%
libedit-20090923_3.0-1-x86_64 184.4K 205.8K/s 00:00:01 [#######################################################] 100%
openssh-5.6p1-2-x86_64 507.2K 320.2K/s 00:00:02 [#######################################################] 100%
pacman-mirrorlist-20101223-1-any 2.1K infG/s 00:00:00 [#######################################################] 100%
patch-2.6.1-2-x86_64 61.1K 116.6K/s 00:00:01 [#######################################################] 100%
pkg-config-0.25-3-x86_64 30.5K 82.0K/s 00:00:00 [#######################################################] 100%
procinfo-ng-2.0.304-2-x86_64 39.9K 99.8K/s 00:00:00 [#######################################################] 100%
procps-3.2.8-3-x86_64 166.1K 190.4K/s 00:00:01 [#######################################################] 100%
reiserfsprogs-3.6.21-3-x86_64 211.8K 212.7K/s 00:00:01 [#######################################################] 100%
sdparm-1.06-1-x86_64 82.0K 164.0K/s 00:00:01 [#######################################################] 100%
sudo-1.7.4.p6-1-x86_64 315.5K 316.8K/s 00:00:01 [#######################################################] 100%
syslog-ng-3.2.1-1-x86_64 238.2K 237.3K/s 00:00:01 [#######################################################] 100%
usbutils-001-2-x86_64 163.9K 219.1K/s 00:00:01 [#######################################################] 100%
which-2.20-4-x86_64 13.7K 110.6K/s 00:00:00 [#######################################################] 100%
:: Retrieving packages from extra...
curl-7.21.3-1-x86_64 437.3K 313.2K/s 00:00:01 [#######################################################] 100%
freetype2-2.4.4-2-x86_64 457.8K 382.7K/s 00:00:01 [#######################################################] 100%
perl-error-0.17016-2-any 17.4K 70.3K/s 00:00:00 [#######################################################] 100%
git-1.7.3.5-2-x86_64 2.4M 1032.7K/s 00:00:02 [#######################################################] 100%
libsm-1.2.0-1-x86_64 47.0K 126.2K/s 00:00:00 [#######################################################] 100%
xproto-7.0.20-1-any 135.6K 180.3K/s 00:00:01 [#######################################################] 100%
libx11-1.4.1-1-x86_64 1954.9K 952.6K/s 00:00:02 [#######################################################] 100%
libxt-1.0.9-1-x86_64 394.6K 251.0K/s 00:00:02 [#######################################################] 100%
libxext-1.2.0-1-x86_64 92.8K 136.4K/s 00:00:01 [#######################################################] 100%
imagemagick-6.6.6.10-2-x86_64 1864.6K 720.4K/s 00:00:03 [#######################################################] 100%
irssi-0.8.15-4-x86_64 536.5K 309.7K/s 00:00:02 [#######################################################] 100%
libjpeg-8.3.0-1-x86_64 191.2K 209.6K/s 00:00:01 [#######################################################] 100%
libmysqlclient-5.1.54-1-x86_64 9.0M 1523.8K/s 00:00:06 [#######################################################] 100%
libpng-1.4.5-1-x86_64 187.2K 204.4K/s 00:00:01 [#######################################################] 100%
libxdmcp-1.1.0-1-x86_64 23.7K 87.0K/s 00:00:00 [#######################################################] 100%
libxml2-2.7.8-1-x86_64 1455.4K 632.8K/s 00:00:02 [#######################################################] 100%
mysql-clients-5.1.54-1-x86_64 153.0K 160.1K/s 00:00:01 [#######################################################] 100%
mysql-5.1.54-1-x86_64 7.7M 1286.1K/s 00:00:06 [#######################################################] 100%
php-5.3.5-1-x86_64 2.8M 911.5K/s 00:00:03 [#######################################################] 100%
php-cgi-5.3.5-1-x86_64 1613.4K 818.1K/s 00:00:02 [#######################################################] 100%
php-curl-5.3.5-1-x86_64 20.8K 72.1K/s 00:00:00 [#######################################################] 100%
php-gd-5.3.5-1-x86_64 75.6K 147.6K/s 00:00:01 [#######################################################] 100%
python-3.1.3-1-x86_64 7.7M 1299.6K/s 00:00:06 [#######################################################] 100%
screen-4.0.3-10-x86_64 461.3K 368.4K/s 00:00:01 [#######################################################] 100%
:: Retrieving packages from community...
nginx-0.8.54-1-x86_64 245.1K 253.2K/s 00:00:01 [#######################################################] 100%
checking package integrity...
(109/109) checking for file conflicts [#######################################################] 100%
( 1/109) upgrading linux-api-headers [#######################################################] 100%
( 2/109) upgrading tzdata [#######################################################] 100%
( 3/109) upgrading glibc [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 4/109) upgrading attr [#######################################################] 100%
( 5/109) upgrading acl [#######################################################] 100%
( 6/109) upgrading ncurses [#######################################################] 100%
( 7/109) upgrading readline [#######################################################] 100%
( 8/109) upgrading bash [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 9/109) upgrading gdbm [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 10/109) upgrading gcc-libs [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 11/109) upgrading db [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 12/109) upgrading zlib [#######################################################] 100%
( 13/109) upgrading cracklib [#######################################################] 100%
( 14/109) upgrading pam [#######################################################] 100%
( 15/109) upgrading gmp [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 16/109) upgrading libcap [#######################################################] 100%
( 17/109) upgrading coreutils [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 18/109) upgrading perl [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 19/109) upgrading automake [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 20/109) upgrading binutils [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 21/109) upgrading run-parts [#######################################################] 100%
( 22/109) upgrading openssl [#######################################################] 100%
( 23/109) upgrading findutils [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 24/109) upgrading sed [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 25/109) upgrading ca-certificates [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 26/109) upgrading cloog-ppl [#######################################################] 100%
( 27/109) upgrading libusb [#######################################################] 100%
( 28/109) installing libusb-compat [#######################################################] 100%
( 29/109) upgrading pcre [#######################################################] 100%
( 30/109) upgrading glib2 [#######################################################] 100%
( 31/109) upgrading module-init-tools [#######################################################] 100%
( 32/109) upgrading pciutils [#######################################################] 100%
( 33/109) upgrading udev [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 34/109) upgrading device-mapper [#######################################################] 100%
( 35/109) upgrading popt [#######################################################] 100%
( 36/109) upgrading cryptsetup [#######################################################] 100%
( 37/109) upgrading curl [#######################################################] 100%
( 38/109) upgrading dash [#######################################################] 100%
( 39/109) upgrading dhcpcd [#######################################################] 100%
( 40/109) upgrading diffutils [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 41/109) upgrading e2fsprogs [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 42/109) upgrading elfutils [#######################################################] 100%
( 43/109) upgrading expat [#######################################################] 100%
( 44/109) upgrading filesystem [#######################################################] 100%
warning: /etc/profile installed as /etc/profile.pacnew
warning: /etc/hosts installed as /etc/hosts.pacnew
warning: /etc/fstab installed as /etc/fstab.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
FATAL: kernel too old
error: command failed to execute correctly
( 45/109) upgrading fakeroot [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 46/109) upgrading file [#######################################################] 100%
( 47/109) upgrading freetype2 [#######################################################] 100%
( 48/109) upgrading gawk [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 49/109) upgrading mpfr [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 50/109) upgrading libmpc [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 51/109) upgrading gcc [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 52/109) upgrading gen-init-cpio [#######################################################] 100%
( 53/109) upgrading perl-error [#######################################################] 100%
( 54/109) upgrading git [#######################################################] 100%
( 55/109) upgrading gzip [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 56/109) upgrading texinfo [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 57/109) upgrading groff [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 58/109) upgrading hdparm [#######################################################] 100%
( 59/109) upgrading sqlite3 [#######################################################] 100%
( 60/109) installing libsasl [#######################################################] 100%
Optional dependencies for libsasl
cyrus-sasl: saslauthd
cyrus-sasl-plugins: authentication plugins other than sasldb
( 61/109) installing libldap [#######################################################] 100%
( 62/109) upgrading heimdal [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 63/109) upgrading tar [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 64/109) upgrading libtool [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 65/109) upgrading libsm [#######################################################] 100%
( 66/109) upgrading xproto [#######################################################] 100%
( 67/109) upgrading libx11 [#######################################################] 100%
( 68/109) upgrading libxt [#######################################################] 100%
( 69/109) upgrading libxext [#######################################################] 100%
( 70/109) upgrading imagemagick [#######################################################] 100%
( 71/109) upgrading inetutils [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 72/109) upgrading initscripts [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 73/109) upgrading iptables [#######################################################] 100%
( 74/109) upgrading irssi [#######################################################] 100%
( 75/109) upgrading jfsutils [#######################################################] 100%
( 76/109) upgrading less [#######################################################] 100%
( 77/109) upgrading libjpeg [#######################################################] 100%
( 78/109) upgrading libmysqlclient [#######################################################] 100%
( 79/109) upgrading libpcap [#######################################################] 100%
( 80/109) upgrading libpng [#######################################################] 100%
( 81/109) upgrading libxdmcp [#######################################################] 100%
( 82/109) upgrading libxml2 [#######################################################] 100%
( 83/109) upgrading lzo2 [#######################################################] 100%
( 84/109) upgrading man-db [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 85/109) upgrading man-pages [#######################################################] 100%
( 86/109) upgrading mlocate [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 87/109) upgrading mysql-clients [#######################################################] 100%
( 88/109) upgrading mysql [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 89/109) upgrading nano [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
( 90/109) upgrading nginx [#######################################################] 100%
( 91/109) installing libedit [#######################################################] 100%
( 92/109) upgrading openssh [#######################################################] 100%
warning: /etc/ssh/sshd_config installed as /etc/ssh/sshd_config.pacnew
( 93/109) upgrading pacman-mirrorlist [#######################################################] 100%
warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
( 94/109) upgrading patch [#######################################################] 100%
( 95/109) upgrading php [#######################################################] 100%
warning: /etc/php/php.ini installed as /etc/php/php.ini.pacnew
( 96/109) upgrading php-cgi [#######################################################] 100%
( 97/109) upgrading php-curl [#######################################################] 100%
( 98/109) upgrading php-gd [#######################################################] 100%
( 99/109) upgrading pkg-config [#######################################################] 100%
(100/109) upgrading procinfo-ng [#######################################################] 100%
(101/109) upgrading procps [#######################################################] 100%
(102/109) upgrading python [#######################################################] 100%
(103/109) upgrading reiserfsprogs [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
(104/109) upgrading screen [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
(105/109) upgrading sdparm [#######################################################] 100%
(106/109) upgrading sudo [#######################################################] 100%
(107/109) upgrading syslog-ng [#######################################################] 100%
warning: /etc/syslog-ng.conf installed as /etc/syslog-ng.conf.pacnew
(108/109) upgrading usbutils [#######################################################] 100%
(109/109) upgrading which [#######################################################] 100%
FATAL: kernel too old
error: command failed to execute correctly
FATAL: kernel too old
error: command failed to execute correctlyI think I have some mismatch between glibc and the kernel now, but the question is: how do I get out of this? This installation is on a VPS and I only have remote access. In case of emergency I can just restore yesterday’s backup, but first I’d like to know if there is some other solution.
Thanks
#2 2011-01-24 13:14:39
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,246
- Website
Re: Didn’t update for so long, and now «Kernel is too old»
#3 2011-01-24 13:17:36
- fabioamd87
- Member
- Registered: 2008-11-22
- Posts: 125
Re: Didn’t update for so long, and now «Kernel is too old»
i think you can try to build yourself last version of kernel, booting the system from it and try to upgrade…
#4 2011-01-24 13:23:25
- a.san
- Member
- Registered: 2008-05-22
- Posts: 5
Re: Didn’t update for so long, and now «Kernel is too old»
that is to say: I can’t do anything remotely, right?
#5 2011-01-24 13:34:02
- wonder
- Developer
- From: Bucharest, Romania
- Registered: 2006-07-05
- Posts: 5,941
- Website
Re: Didn’t update for so long, and now «Kernel is too old»
i guess you run arch as a openvz vps. you can use my repo
https://wiki.archlinux.org/index.php/VPS_Repo
Last edited by wonder (2011-01-24 13:34:15)
Give what you have. To someone, it may be better than you dare to think.
#6 2011-01-24 15:10:10
- eldragon
- Member
- From: Buenos Aires
- Registered: 2008-11-18
- Posts: 1,028
Re: Didn’t update for so long, and now «Kernel is too old»
seeing that many upgrades failed. i guess you should restore yesterday’s backup.
and make an upgrade plan so that this doesnt happen again.
btw: why wasnt your kernel upgraded along with the rest of the packages?
#7 2011-01-24 16:04:46
- Radioactiveman
- Member
- From: Germany
- Registered: 2010-05-13
- Posts: 388
Re: Didn’t update for so long, and now «Kernel is too old»
A vServer uses the kernel of the host system.
@a.san: you should add
to your pacman.conf
#8 2011-01-24 16:16:57
- Mr Green
- Forum Fellow
- From: U.K.
- Registered: 2003-12-21
- Posts: 5,867
Re: Didn’t update for so long, and now «Kernel is too old»
Might be way off but can you not connect remote system via Arch cd? chroot in and repair system?
#9 2011-01-24 16:28:44
- wonder
- Developer
- From: Bucharest, Romania
- Registered: 2006-07-05
- Posts: 5,941
- Website
Re: Didn’t update for so long, and now «Kernel is too old»
Radioactiveman wrote:
A vServer uses the kernel of the host system.
@a.san: you should add
to your pacman.conf
no he shouldn’t. if he does that and then upgraded packages that have been compiled against newer glibc, it would have errors. not to mention about newer toolchains
for a proper fix, see my previous post
Give what you have. To someone, it may be better than you dare to think.
#10 2011-01-24 21:25:26
- ViruSzZ
- Member
- From: The Streets
- Registered: 2010-10-14
- Posts: 202
- Website
Re: Didn’t update for so long, and now «Kernel is too old»
Nice one 
.. I have Arch VPS running on a Vserver virtualization where the host’s kernel is 2.6.22.16 and that do the job ….
Respect
Their Momma Made Em, Their Momma Gave em & now she can`t even SAVE`em | My WebLog
#11 2011-08-26 15:58:00
- arre
- Member
- Registered: 2007-08-25
- Posts: 10
Re: Didn’t update for so long, and now «Kernel is too old»
Lol, I had the same problem just now:) System became completely unusable!
Luckily I found the old glibc package without too much trouble, and with the help of a LiveCD I manually extracted the package and put the old files back in place. All back to normal. Phew! 
I’m kinda happy I didn’t have to setup a Vserver for it:)
My 10 year old pc, now performing admirably as a simple router, lives on!
Модератор: Модераторы разделов
-
IMB
- Сообщения: 2555
- ОС: Debian
FATAL: kernel too old
Доброго дня!
Пробую плавно перейти на новый toolchain, пересобрал всю систему и при запуске вижу
Код:
# ./busybox -?
FATAL: kernel too old
Segmentation fault
Информация о файле
Код:
# file rootfs/bin/busybox
rootfs/bin/busybox: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, stripped
Сейчас используется linux-2.6.23.17, в состав нового toolchain входит linux-2.6.32.61, мигрировать наверное можно, но это время…
Как можно «обмануть» программы при запуске со старым linux?
Собственно как glibc получает информацию о текущей версии linux?
Если я подменю вывод uname или модифицирую текущий linux на отдачу более старшей версии, этого хватит?
Спасибо.
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: FATAL: kernel too old
Сообщение
Bizdelnick » 02.12.2016 18:05
IMB писал(а): ↑
02.12.2016 17:42
Как можно «обмануть» программы при запуске со старым linux?
Обмануть сегфолтящуюся программу? Никак. Надо пересобирать. Воероятно, вместе с тулчейном или как минимум libc (но обновиться, скорее всего, будет проще). Хотя не исключено, что вопрос решается и опциями компилятора/линковщика, не знаю. Конкретно с такой ошибкой я не сталкивался.
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |
-
IMB
- Сообщения: 2555
- ОС: Debian
Re: FATAL: kernel too old
Сообщение
IMB » 02.12.2016 18:09
Насколько я понимаю segfault вызывает libc из-за несоответствия версии linux
(https://gcc.gnu.org/ml/gcc-help/2009-10/msg00401.html) писал(а):You can set the minimum supported kernel when you configure glibc with the —enable-kernel option
Пересобирать glibc как-то тоже не тянет.
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: FATAL: kernel too old
Сообщение
Bizdelnick » 02.12.2016 18:17
Тогда остаётся или обновлять ядро, или использовать старый тулчейн.
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |
-
IMB
- Сообщения: 2555
- ОС: Debian
Re: FATAL: kernel too old
Сообщение
IMB » 05.12.2016 11:20
Код:
# /tmp/strace -v /tmp/busybox -?
execve("/tmp/busybox", ["/tmp/busybox", "-?"]
uname({sysname="Linux", nodename="zzz", release="2.6.23.17", version="#9 PREEMPT Wed Nov 23 21:28:46 UTC 2016", machine="sh4", domainname="(none)"}) = 0
open("/dev/tty", O_RDWR|O_NOCTTY|O_NONBLOCK) = 3
writev(3, [{iov_base="FATAL: kernel too oldn", iov_len=22}], 1FATAL: kernel too old) = 22
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x29557000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x2967b048} ---
+++ killed by SIGSEGV +++
Segmentation fault
надо попробовать «подменить» версию linux в выводе uname
-
Bizdelnick
- Модератор
- Сообщения: 19826
- Статус: nulla salus bello
- ОС: Debian GNU/Linux
Re: FATAL: kernel too old
Сообщение
Bizdelnick » 05.12.2016 12:19
Так Вы добьётесь только того, что Ваши программы будут падать в самый неожиданный момент.
Пишите правильно:
| в консоли вку́пе (с чем-либо) в общем вообще |
в течение (часа) новичок нюанс по умолчанию |
приемлемо проблема пробовать трафик |