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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slackware 13.37 x86_64 desktop, Slackware-current on laptop
Posts: 43
Rep:
armedslack 13.37
Does anyone have any experience with armedslack? I am using a sheevaplug from globalscale and when booting the kernel, when verifying the checksum I get a crc error.
Code:
Marvell>> bootm 0x00800000 0x01100000
## Booting image at 00800000 ...
Image Name: Linux-2.6.38.4-kirkwood
Created: 2011-04-22 11:50:56 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2033128 Bytes = 1.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... Bad Data CRC
Marvell>>
This may be a Shevaplug issue. This device (and other Marvell devices) are notorious for odd issues and failures. Some can even brick their Shevaplug completely.
I had 13.1 running on both SD card and USB stick, but something bad happened - my fault or what, I don't know. I've written about it in my LQ blog, under the arm tag. http://www.linuxquestions.org/questions/blog/tags/arm/
Distribution: slackware 13.37 x86_64 desktop, Slackware-current on laptop
Posts: 43
Original Poster
Rep:
The issue was when I ftp'd the armedslack tree from the server, it was set to ascii transfer, ascii is known for trashing binary files, transfered again in binary and it worked fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.