Now how about a rewrite that the noob's can understand posted in the wiki the first line is pure uber-geek gibberishalexchamberlain wrote:You can use `piimg` to mount an SD card properly - with /dev, /proc, /sys and /boot. Then you can chroot into sort out any problems if necessary.
I've written a bit a related guide over at Raspberry Pi.SE. It explains how to install QEMU etc.
Obviously, this is not necessary if you just want the log files, but I think it's the easiest way to install new software.
The only problem is Windows users! I think I might have to publish a Raspberry Pi rescue CD...
Hialexchamberlain wrote:Linux logs everything! Once your Raspberry Pi dies, you can plug the SD card into your Linux desktop, mount it and diagnose any problems.
Would you prefer a Linux Live CD (designed for this situation) or a piece of Windows software that could read the Linux partitions?PaulCheffus wrote:Thats ok if you have a Linux desktop but what happens if you only have Windows available?
Hialexchamberlain wrote:Would you prefer a Linux Live CD (designed for this situation) or a piece of Windows software that could read the Linux partitions?PaulCheffus wrote:Thats ok if you have a Linux desktop but what happens if you only have Windows available?
Hialexchamberlain wrote: My main concern is people destroying their hard drive...
Hialexchamberlain wrote:Would you want a GUI?
There are a couple of applications out there that claim to read ext partitions on Windows, but they aren't actively maintained from what I can tell. My fear would be that Windows upgrades would mean significant effort to make it work again. All this for a solution that limits it to reading.Jonn wrote:A utility for Windows would be fabulous: Windows users (such as I am) would be able to get the information without having to close applications for rebooting the PC. This would hold also for classrooms where Windows is the default OS. Read-only access should be sufficient (and safer) for diagnosis: if included, write access should be 'advanced'. Of course, a user could simply lock the SD card as a precaution.
This is the possibility I would vote for, except slightly more permanent. A specially designed Live CD for managing SD card images. I've just pushed to https://github.com/alexchamberlain/rpi_manage_live. Please raise an Issue to suggest any more features it should have.Jonn wrote:I have a 'lightly-used' Linux live CD that I can boot on a second, older PC, so I'll see if I can download and set up piimg on that. (Probably I should save the installed-version piimg files to a USB stick to save having to re-install each time I start up fresh with the Linux live CD.)
No idea.Jonn wrote:I do have a question: I saved the SD card files (.img, .txt, etc.) to Windows directories a couple times (from re-imaging of the SD card different times), but only the config.txt files have differing timestamps because of raspi-config and/or manual editing. The SD card is writable, because I have reformatted it and re-imaged it ... in Windows. It did show empty of files and of full capacity, and then at 59 MB after re-imaging. File comparisons between two previous incarnations and the current version of kernel.img show the contents to be the same. Are the logs stored in the RAM and not written to the SD card (yet)?
Code: Select all
[email protected] ~ $ scp -p [email protected][i]IP_Address[/i]:/mnt/SD2/var/log/dmesg . The authenticity of host '[i]IP_Address[/i]([i]IP_Address[/i])' can't be established. RSA key fingerprint is 03:[i][edited][/i]:69. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[i]IP_Address[/i]' (RSA) to the list of known hosts. [email protected][i]IP_Address[/i]'s password: dmesg 100% 19KB 18.9KB/s 00:00 [email protected] ~ $
This is totally not ready, but at least you burned a raw Arch Linux disk and got stuff sorted. Be careful not to bork your own system with Live CDs though!Jonn wrote: I downloaded the zip file from https://github.com/alexchamberlain/rpi_manage_live, unzipped it to a USB stick, and found the releng/root-image/root/install.txt file. It references https://wiki.archlinux.org/index.php/Installation_Guide for making an Arch Linux CD.
Happily I knew little enough that I had to proceed slowly. I think copying the files to view on another PC helped keep me from trouble too. I could have goofed up with an editor, but I didn't know or check for what editor is available in Arch Linux.Be careful not to bork your own system with Live CDs though!
... so maybe I'll leave it off for another week and try again...Polyfuses can take a very long time to completely recover from a "trip", sometimes days, even weeks, in fact in a sense they never get completely the same, but if they get down to say 3 Ohm (for the USB polyfuses F1 & F2) or 0.2 Ohm for the input polyfise F3 on the back of the board you can say they are "cured". http://www.raspberrypi.org/phpBB3/viewt ... 799#p94555
You know that runningJonn wrote:So... I guess I'll wait for the September Raspbian and let the board rest some more.
Code: Select all
sudo apt-get update sudo apt-get upgrade sudo reboot