You are not logged in.
# pacman -Syu
looking for inter-conflicts... done.
Targets: alsa-lib-1.0.14-5 alsa-utils-1.0.14-2 kernel26-2.6.22.4-1
kima-0.7.4-3 libice-1.0.4-1 libxrender-0.9.3-1 xorg-apps-1.0.3-1
error: failed to commit transaction (corrupted package)
archive kernel26-2.6.22.4-1.pkg.tar.gz was corrupted (bad MD5 or SHA1 checksum
Last edited by JaDa (2007-08-24 03:14:33)
openSUSE
Arch Linux
USALUG
Offline
There is already a -2 , so better wait for it :
http://archlinux.org/packages/4197/
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
After installing kernel26 2.6.22.4-2 I rebooted my computer and I got evil error message preventing me to boot my computer. Straight after GRUB it said "uncompressing kernel" and failed with a "CRC error" message.
Is it just me or is there something badly wrong with this package?
Last edited by lanxu (2007-08-21 18:56:49)
Offline
I just hosed a machine too
What's the best way to recover from this?
Offline
I have also experienced the same problem. I tried booting into the install cd and using pacman with the --root option to downgrade my kernel but the older versions that used to work now also come up with the same error. Any ideas?
Offline
It appears that my own ignorance once again has gotten in the way of me having a working system. I had forgotten to mount the boot partition which was separate, so I was installing old kernels in the wrong place. After correctly mounting the boot partition my 2.6.22.3-1 works fine.
Offline
I just ended up booting from an ftp install cd and entering "boot root=/dev/sda1". It booted into my system using the installer kernel.
I'm fine running on this until the package is fixed. Hopefully this is resolved sooner than later.
Offline
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
I had the same problem, fortunately I found an old install cd of
Arch 0.7.2 and booted with arch root=/dev/hda2 noinitrd ro, so
the install cd kernel started with my / then I was able to downgrade
the kernel to 2.6.22.3 found in /var/cache/pacman.
chrooting on ubuntu live cd didn't work (initrd was not created correctly
and / couldn't be mounted.
Offline
I had the same problem, fortunately I found an old install cd of
Arch 0.7.2 and booted with arch root=/dev/hda2 noinitrd ro, so
the install cd kernel started with my / then I was able to downgrade
the kernel to 2.6.22.3 found in /var/cache/pacman.chrooting on ubuntu live cd didn't work (initrd was not created correctly
and / couldn't be mounted.
I can confirm this. I wasn't able to fix this problem with chrooting or using pacman with --root flag. These methods gave me really nasty errors. However, booting from Arch CD by using your root partition and updating kernel with older one worked like a charm.
I feel something like this shouldn't never happen. I bet there are a lot of Arch users who can't fix this when/if they face it. I recommend a new kernel26 package to the repositories as fast as possible.
Last edited by lanxu (2007-08-21 21:25:54)
Offline
atomclock's instructions worked for me with an arch 2007.8 cd. I hope the arch dev team puts a kernel26-2.6.22.4-3 into the repos very quickly that fix the crc error before too many arch users cant boot their system and can't fix it.
Offline
Is it possible to save a problem without CD?
Offline
Uncompressing Linux ... crc error --System halted
I was hoping this box will make it until KDE 4
So you managed to install it? I thought the package was corrupted..
/me is confused
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
i've experienced the same problem, so I did just like atomclock (by myself, i've read this later ha ha ha ha) and fixed my problem... I guess there are some issues about kernel 2.6.22.4-1 to be solved... but I can't do much things, except to tell anyone to "NOT" upgrade to kernel 2.6.22.4-1... 'cause the system just avoid booting...
Offline
So you managed to install it? I thought the package was corrupted..
/me is confused
First was kernel26-2.6.22.4-1
now it is kernel26-2.6.22.4-2, but now I am in trouble to fix this problem
I think I need a new Insall
openSUSE
Arch Linux
USALUG
Offline
First was kernel26-2.6.22.4-1
now it is kernel26-2.6.22.4-2, but now I am in trouble to fix this problem
Oh, I see, that's interesting
I think I need a new Install
No you don't. Besides, repairing a broken install is a good way of learning new things.
Just do the common procedure as everyone already suggested.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Just got an update notification for:
kernel26-2.6.22.4-2.1
Is the -2.1 (as opposed to -2) okay, or is it the same thing. Or if it's different, maybe no one is brave enough to try it?
Offline
Just got an update notification for:
kernel26-2.6.22.4-2.1
if it's different, maybe no one is brave enough to try it?
I would love to try it cause I've got nothing to lose since I have already installed 2.6.22.4-2, but when I pacman -Syu, it says that everything is up to date, 2.6.22.4-2 kinda is the latest version although I don't see it on the website anymore and it's substituted with 2.6.22.4-2.1
Offline
With 2.6.22.4-2 I have the same problem. Maybe I would be lucky with next version...
But my question is: because Kernel is not the same as the Doom for example does anyone tested it before posted for download, please?
Offline
With 2.6.22.4-2 I have the same problem. Maybe I would be lucky with next version...
But my question is: because Kernel is not the same as the Doom for example does anyone tested it before posted for download, please?
Could someone check here:
http://cvs.archlinux.org/cgi-bin/viewcv … ag=CURRENT
I can't find any difference between -2 and -2.1? Maybe I'm doing something wrong? All I can find is that they changed the PKGBUILD pkgrel#.
Last edited by MrWeatherbee (2007-08-22 01:13:04)
Offline
DON'T PANIC!!!!!!!!
lol, at least the name fits.
Offline
After upgrading from -2 to -2.1 the system is bootable again.
Offline
I just made some images of my partitions to be safe, and then I upgraded to kernel26-2.6.22.4-2.1.
Whether I would have had issues with kernel26-2.6.22.4-2 I can't say definitively as I didn't try that one, but everything seems fine with kernel26-2.6.22.4-2.1.
Last edited by MrWeatherbee (2007-08-22 03:47:26)
Offline
this crc-problem had exist only for i686 in kernel26-2.6.22.4-2. it's fixed in kernel26-2.6.22.4-2.1! if your system cannot boot kernel26-2.6.22.4-2 - use another installed (suspend2-,ck-,mm-,custom-)kernel to boot or follow the shown way above with the install cd to rescue your system.
Offline