Slackware - ARMThis forum is for the discussion of Slackware ARM.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Raspbian does it from within, not sure how, might be worth taking a look at.
Are you creating your new cards as bootable disks when you create your partition on them(?).
Also the type of formatting has something to do with whether they boot or not, (I think it might have to be 32bit dos formatted).
Sorry I can't be more helpful, as I only bought my one to see if it could replace a desktop computer for every day usage.
I'm taking a bootable MicroSD with a running OS on it, shutting down that OS and DD'ing it to an image. So its copying partitions, formatting, etc. Then I try to DD it back to a new MicroSD and then pop that new microSD into the Pi and it won't boot.
Its similar to how you would download rasbain from the RPi foundation and DD it to a blank card.
I don't use Raspian, but with Arch, I just copy (as in cp or rsync) the files up to my PC hard disk, then stick a new SDCard in and copy back. Works on a pi3, and also a goflex home backup system (Marvell Sheeva plug) in which I installed a new (real) hard disk about a week ago.
Has the side benefit you know the source filesystem(s) is ok and readable.
Edit: presumes U-Boot or similar has been flashed successfully beforehand.
from my own mileage:
1. Some cards ("non brand" names) seem to misbehave on R_Pi?
2. what has the same md5 is the same (try comparing md5sum of the image got from the copy?)
3. R_Pi seems to be cherry picking SDcards, so try sticking to Samsung or the like branded ones for testing?
Once just as I was about to quit, I reiterated with a "branded" SDcard, and got it going?
And I don't speak off top of my head here:
On the zero "track", usually there is the boot loader that "imports" the kernel et al. (in between the partition table and the 1st partition) to the RAM, there from all that matter is the parttion(s) contain filesystems that the kernel has modules for (built-in or pre-loaded (initrd->RAM) )
So for testing try an known good SDcard and only the "boot payload" (the begin and the fat partition).
If You get lucky, go for it and buy an device from an reputable brand?
If fail, try pull back the image from the 2nd SDcard and compare the two copies?
maybe the card reader is faulty, or it has intermittent problems (cable? plugs?)