The fsck problem occurred after installing f2fsprogs. Modified the fstab
file to skip checking.
Next step is wireless. Seems like wpa_supplicant-gui is also among the
missing. Never knew I
was so dependent on graphical tools for configuration. Still have a set
of Linux Slackware diskettes
from around 1993.
When copying the memory device to a host I expect dd to generate an
8-Gbyte file. That
is ok for my limited use but we have a RPi users group near by which is
what started this
trip down the black hole. Will get another memory device to experiment
with shrinking
the partitions.
George
On 05/04/2014 12:26 PM, Gordan Bobic wrote:
On 05/04/2014 05:20 PM, Joshua Kramer wrote:
"Today it is failing to boot. Complaining about e2fsck on mmcblk0p2.
Google
should help."
This may be a sign that the SD card has gone bad. I've been through
this; lesson learned is that once you have a stable environment, remove
the SD, put it in another computer, and copy an image of it. So when it
goes bad you don't have to recreate all of your efforts.
It's plausible. Or it could just be an unclean shutdown. Put the card
into another machine, fsck it to make it "clean". It should work then.
By all means grab a backup copy of it at the same time.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
