You are not logged in.
Pages: 1
Hi!
I did pacman -Syu minutes ago (around 23:40 CET) it upgraded allot stuff including kernel.
after the reboot the system won't boot the new kernel including the fallback.
root (hd0)
Filesystem type is extfs, partition type 0x83
kernel /boot/vmlinuz26 root=/dev/sda1 ro
[Linux-bzImage, setup=0x1e00, size=01afdf8]
initrd /boot/kernel26-fallback.img
[Linux-initrd @ 0x1fbb2000, 043d72e, bytes]
Uncompressing Linux...
crc error
-- System halted
How do i fix this please someone help.
Last edited by decaturguy (2007-08-21 22:54:41)
Offline
This issue is currently discussed on #archlinux in IRC.
One possibility to solve this problem is to chroot (or directly boot) into your system with a live cd (or your archlinux install cd) from where you can downgrade the kernel, because it's a bug in the current i686 kernel.
brain0 is already about to fix this in a new package release.
Last edited by harlekin (2007-08-21 22:27:53)
Hail to the thief!
Offline
Thanks harlekin!
please someone post how to guide with archlinux install cd.
Offline
http://wiki.archlinux.org/index.php/Res … oot_loader
http://wiki.archlinux.org/index.php/Downgrade_packages
Those articles may be helpful though not up to date.
If you have troubles with them, post and I'll post a complete how to.
You can also insert your archlinux installation cd and enter:
arch root=/dev/sda3
whereas /dev/sda3 is your / (root) partition. This will boot your root partition with the installation cd's kernel.
Hail to the thief!
Offline
Thanks again
Solved using this guide:
I just had this problem and fixed it by...
boot with another linux CD (arch install disk will work)
Mount the partition that contains your Arch install.
enter the mounted directory and type
chroot . /bin/bash
then
cd /var/cache/pacman/pkg/
then type
ls kernel26*
Pick a kernel that is older... and
pacman -U kernel26.......
Fixed my system...
This sort of thing seems to happen a lot... although this is the first time in about 4 kernel updates...
Offline
Harlekin, would you recommend doing an IngnorePkg=kernel26 in pacman.conf for now, since this seems to be happening for everyone upgrading?
Offline
It seems as if only i686 systems are affected by this bug. So if you're running x86_64 arch, you should be fine without worrying.
If you're running i686, adding the kernel to IgnorePkg may be an option until the new kernel package is released / available for your mirror.
As brain0 already updated the kernel package, I'd simply wait with a system upgrade until your mirror is sync'ed.
Hail to the thief!
Offline
Ok.
And please give us back the Harley Quinn av. Please!
Offline
Ok.
And please give us back the Harley Quinn av. Please! :D
But... but Nyuu is *a lot* more cute! )':
:D
Last edited by harlekin (2007-08-21 23:33:18)
Hail to the thief!
Offline
happened to me, too.
https://www.skatox.com/blog -> Visit my blog about (Linux, Hacking, Open Source, Web Development, Windows, Mac Os X, Internet and more......)
Offline
Thanks again
Solved using this guide:
atomclock wrote:...
I managed to solve it with this guide as well
Offline
First post here, so my question is probably caused by not knowing the history of Arch well enough.
This thread is labeled "solved", but others are still open, so my question is:
- both kernel26-2.6.22.4-2.1 and kernel26-2.6.22.4-2 gives a "crc erro" - maybe not for all users but for quite many - so are we expecting a new updated one, or the above will stay until it will eventually be updated for other reasons?
I've no problem, because I had the install CD and could easily roll back to the kernel26.2.6.22.3-1. I'm not questioning anything (I'm very pleased with Arch which so far is exactly what I searched for), I'm just interested in how these matters usually work regarding Arch.
Last edited by KimTjik (2007-08-22 09:19:24)
Offline
kernel26 2.6.22.4-2.1 is now in the repos, and solves this problem.
Offline
Hm, browsing the repo packages shows kernel26 2.6.22.4-2.1 to be the current kernel (http://www.archlinux.org/packages/4197/). However if using Pacman there's no ~-2.1 but just the broken (in my system) ~2.2. I've syncronized pacman several times during the day and still it doesn't give any ~2.1 kernel. What am I doing wrong?
[root@kimtjik kimolee]# pacman -Syu kernel
:: Synchronizing package databases...
current is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies... done.
looking for inter-conflicts... done.Targets: kernel26-2.6.22.4-2
Total Package Size: 22,53 MB
Proceed with installation? [Y/n] n
[root@kimtjik kimolee]#
Last edited by KimTjik (2007-08-22 13:28:25)
Offline
Hm, browsing the repo packages shows kernel26 2.6.22.4-2.1 to be the current kernel (http://www.archlinux.org/packages/4197/). However if using Pacman there's no ~-2.1 but just the broken (in my system) ~2.2. I've syncronized pacman several times during the day and still it doesn't give any ~2.1 kernel. What am I doing wrong?
The only thing you're doing wrong is being too fast. Your selected mirror probably hasn't synchronized with the master server yet - just give it a bit of time and it should show up.
Offline
Ah, stupid me! I totally forgot about the mirrors. I believe my brain hasn't got synchronized either; to bad there's no master brain to connect to.
Thanks!
Offline
Hello, is this thread still active?
I'm also having the "crc error", only in my case the error is on a Ubuntu distribution, not ArchLinux! I've already tried asking on Ubuntu forums, but got directed here!
I'm wondering if the same solution that was suggested here, will also work on mine, only perhaps changing the commands a little bit? I have Ubuntu 8.10, by the way!
Cheers!
Offline
Pages: 1