SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
it seems the files in kdei/ are missing, so the checksum failed because the file doesn't exists.
One file is considered bad, because it has a wrong checksums and that's the kernel-firmware-20120109git-noarch-1.txz.asc file, not the kernel-firmware package itself, so it's not a corrupted package
Last edited by willysr; 02-02-2012 at 07:40 AM.
Reason: Added clarification about wrong checksums
Do you have those error messages? it's almost the same machine as you have.
Quote:
Originally Posted by cgorac
If anyone is with ThinkPad machine (well - W520 in particular), and Slackware64 is hanging about 6 secs into boot after this upgrade - just turn off ACPI (adding "acpi=off" to LILO command line), and it should boot. Have no idea yet what may be the problem here...
Here, "slackpkg upgrade-all" is also reporting md5sum error with kernel-firmware-20120109git-noarch-1 package - so I downloaded it through wget, and applied upgradepkg manually for this package.
Do you have those error messages? it's almost the same machine as you have.
Great pointer, thanks: I haven't seen any of error messages mentioned in this article, but still - out of suggestions proposed there, it appears that turning VT-d off in BIOS is solving problem for me. I guess it's now awaiting for the next kernel update, and then turning if on again.
Sorry for hijacking the thread somewhat. On the other side, I'd say this is good example why long silence in -current, and then pushing number of important packages at once, is bad thing: I was supposing it's some sort of kernel regression, but when several kernel revisions skipped, it's very hard to find what may be the problem. Unfortunately, this mode of operation is seemingly a norm now after each Slackware release...
The checksum problem on kernel-firmware is also fixed in the latest update:
Code:
Thu Feb 2 15:07:23 UTC 2012
a/kernel-firmware-20120202git-noarch-1.txz: Upgraded.
There were some reports of a failing checksum on the .asc (which
did verify, so the package was good). So, we'll replace it with
a new build to make sure that it syncs out.
Perhaps, your mirror is in progress of syncing
yes, you can download the package manually and perform manual upgrade process.. it will have a same results
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.