19 Jan
2009
19 Jan
'09
2:06 p.m.
On Mon, Jan 19, 2009 at 2:58 PM, Hugo Doria <hugodoria@gmail.com> wrote:
(sorry for the double post)
kernel26 2.6.28.1 is running fine here now. So here goes my signoff for x86_64.
I think the problem was related with a bad download (or something like this). Thomas had a different md5sum for /boot/vmlinuz26 than mine.
rm /var/cache/pacman/pkg/kernel26-2.6.28.1-1-x86_64.pkg.tar.gz pacman -Sy testing/kernel26 again solved the problem.
The correct md5sum is the one i sent in the last email:
# m5sum /boot/vmlinuz26 6c96af7941680c91ecb25926a949d88a /boot/vmlinuz26
Shouldn't pacman md5 check catch bad download? The md5 of kernel26-2.6.28.1-1-x86_64.pkg.tar.gz is normally stored in the database, and pacman normally checks this after a download.