Welcome to the Metaverse subreddit. Read our rules & FAQ before posting! No inappropriate behavior. This includes, but is not limited to: personal attacks, threats of violence, slurs of any kind, or posting of false information/ people's private information.

Keep price discussion and market talk, memes & exchanges to other subreddits such as 3. No duplicate threads. No spamming, drive by posting, unsolicited referral links or promotions.

No misleading titles.Please put a title that matches your post content. 6.English language only. Please provide accurate translations where appropriate.

No duplicated questions that are addressed in FAQ. If the current answer to the FAQ lacks details, use the comment function to ask more specific. Community Resources • • • • • • • • • • Wallet Resources • • Documentation & Explorers • • • • • List of Exchanges • • • • • • • •. Correct me if I am wrong please. But there is a lack of Linux wallet instructions so I will start this thread so people can add them. 1) Download the Linux wallet from mvs.live 2) extract the contents.

3) using the terminal go into the directory that was extracted: cd /insert_your_directory/mvs-linux-x86_64-v0.7.0a/ 4) enter the following:./mvs-install.sh 5) now you can a) close the terminal and execute mvsd and it will run the background or b) enter in the command line:./mvsd -u 1 6) using your favorite browser go to: 7)create a login and save the mnemonic somewhere save 8) login and use the wallet. Hope it helps.

Hi ColonialSoundMakers, please see below feedback from wallet team. Once we release update wallet this week, please refer. 1) Download the Linux wallet from 2) extract the contents(unzip -d./ mvs-linux-x86_64-v0.7.1.zip).

3) using the terminal go into the directory that was extracted: cd /insert_your_directory/mvs-linux-x86_64-v0.7.1/ 4) enter the following:./mvs-install.sh 5) now you can enter in the command line:./mvsd 6) using your favorite browser go to: 7) create a login account and save the mnemonic somewhere 8) login and use the wallet.

[ANN] Signatum - New Algorithm - Fair Launch - No Premine. Updated binary for Raspberry Pi 2 and 3 is pushed on. Dodopool Dodopool ETP Metaverse mining pool. Raspberry Pi Bitcoin Mining For 12 Hours! How to solo mine peercoin. Metaverse ETP - Duration: 16:23. Limit my search to r/Metaverse_Blockchain. Linux Wallet (how to). With the raspberry PI? Installation in terminal works.

Hi, clearly I'm a NOOB and this is my first post, but I'm having no luck Booting my PI Zero w with new OSs. I recently got a Pi Zero w with a SanDisk 16GB Micro SD card preinstalled and it boots up fine. So my PI works fine. I purchased a SanDIsk Ultra 64GB Micro SD card and it seems like I have been crawling through levels of problems to try and get it to boot with an OS. So far I have managed to get the card to read as a full 64GB and format it to Fat 32, which Win 10 wouldn't do so it involved downloading different Apps. I have now copied all the NOOBS files that I downloaded and unzipped.

The files appear on the card SD card OK. But when I put the card into the PI and switch on I do not even get a green LED to light and it does not boot. Einsteinium EMC2 Mining Pc Specs. I believe I have followed all the information from the Beginners posts to get this far. Can anyone help in suggesting what I have done wrong or need to do? Heydt wrote:Well. If it were me, I'd download Raspbian and follow the directions on the download page to unpack the image file and then transfer the image file to the SD card.

That way, on the first boot, Raspbian would automatically expand the root filesystem to use the whole card. I am curious, though, what are you planning to do with a Pi0W that needs a 64GB card? Hi, I tried this first off by downloading the latest image for Jessie from the site but it didn't boot even though my PC was showing the files present. I though the problem was that the Micro SD card only read at about 40mb or that it wasn't the NOOB files.

That's when I decided I needed to do something to format it a full 64GB Fat32 and just copy the NOOB files across but that didn't work either. I am beginning to get the impression that 64GB is a bit OTT? I just though it would be big enough to put any OS or, maybe several and it would be OK.

I also had the idea of using it for RETROPIE and thought that the space would allow for plenty of emulators and ROMS. In any case I still get not LED and no boot using this method. Could the problem be the 64GB card? I have now seen posts where people seem to be having trouble with 64GB cards and WIN 10 wont format them to FAT 32 which doesn't help either. B.Goode wrote:Please see for a summary of everything that is known about how to boot an RPi. The good news is that you have evidence from the first 16Mb card that your RPi is in working order: the only hurdle you have to overcome is correctly creating your own microSD card.

Hi, Yes this is the Sticky I was using and learned that the Zero needs NOOBS and that cards need to be FAT32 etc. That's why I resorted to pleading for help because I think I have exhausted the information here and I still cant get an image to boot of my 64GB SanDisk card. KLL wrote:you could go the easy way: -a- read the 16GB SD on win laptop win32diskimager to a 16GB.img file -b- write that.img file to the 64GB SD -c- with raspian only would need to run sudo raspi-config to use full SD, NOOBS??? If usb port and card reader on RPI can use the desktop menu 'sd card copier tool.' Thanks but it's not only raspian I want to run but I suppose if I could get it to BOOT of my card that would be progress.

The problem seems to be that it just wont boot with this 64GB card even with and image written to it. I have been using win32diskimager for the job as well as just copying the files.

Garry1540 wrote: The problem seems to be that it just wont boot with this 64GB card even with and image written to it. I have been using win32diskimager for the job as well as just copying the files. You appear to be inventing solutions that won't ever work. The NOOBS Installer requires files to be copied onto a microSD card pre-formatted as FAT (not exFAT).

A direct OS image such as Raspbian requires the image to be 'flashed' with a tool such as Etcher or Win32DiskImager. The prior format of the card is irrelevant. Copying the image to the card will not work.

DougieLawson wrote:Zero does NOT need NOOBS, it will boot plain Raspbian Jessie 2017-04-10 just as well as NOOBS. Follow the video at: and you should be able to get things working. Start with a download of Jessie from (you don't even need to unzip that). Then grab Etcher from Hi thanks for trying to help.

The 3rd post on the Zero in this link, states 'You must use NOOBS 1.5 (or later) for the PiZero' I have tried what you and the video suggested and used the latest Jessie zip file and Etcher to write it to this card. Etcher says that it was Flashed successfully and the files are present but I have the same issue, when I insert it into my Zero w and power up nothing happens and the green LED that comes on with my 16GB card doesn't for my 64GB one. I'm coming to the conclusion that my problem isn't a simple idiot beginners mistake or an easy fix. Could this Sandisk card be incompatible in some way? I may have to get a 32GB one to try. Garry1540 wrote: The problem seems to be that it just wont boot with this 64GB card even with and image written to it.

I have been using win32diskimager for the job as well as just copying the files. You appear to be inventing solutions that won't ever work. The NOOBS Installer requires files to be copied onto a microSD card pre-formatted as FAT (not exFAT). A direct OS image such as Raspbian requires the image to be 'flashed' with a tool such as Etcher or Win32DiskImager. The prior format of the card is irrelevant.

Copying the image to the card will not work. I don't think I have been making the mistakes you suggest.

I first tried writing the image to the card using win32diskimager and have now tried with Etcher. When I couldn't get the card to boot I then formatted the card ensuring it was Fat32 - I learned from the sticky that exFAT was no good - and then copied the NOOBS files manually to see if that worked but it didn't.

I am starting to think the problem is that for some unknown reason this card isn't compatible and might get a 32GB one. I'm scared to write anything to my 16GB one as I know that definitely works and don't was to muck it up if its something I'm getting wrong. Drgeoff wrote:Are you sure the 64 Gbyte card is not a fake?

Download hw2testw and check it. Fairly sure its not fake. Got it from Amazon and can partition and format it to 62GB. That of itself proves nothing. The only realistic test is to check that it can actually store and retrieve that much data.

Amazon, like eBay, is a marketplace for thousands of traders, many reliable and many not so. There are many tests that can validate if an sd card is indeed fake, and yes buying fake cards from places like amazon is a big problem. Google for 'fake sd card test' to find a suitable test program for your OS. B.Goode wrote:Please see for a summary of everything that is known about how to boot an RPi.

Can you clarify where exactly it says that an RPi Zero requires the NOOBS Installer? Because that would be wrong. Perhaps I misunderstand the post but the third one here; states 'You must use NOOBS 1.5 (or later) for the PiZero' so I assumed that NOOBS had to be used for the PiZero W.

It should say 'If you choose to use NOOBS, you MUST use NOOBS 1.5 or later for a PiZero (PiZ), You MUST use NOOBS 2.4 or later for a PiZero with WiFi (PIZW).' Drgeoff wrote:Are you sure the 64 Gbyte card is not a fake? Download hw2testw and check it. Fairly sure its not fake. Got it from Amazon and can partition and format it to 62GB. That of itself proves nothing. The only realistic test is to check that it can actually store and retrieve that much data.

Amazon, like eBay, is a marketplace for thousands of traders, many reliable and many not so. Asic Ethereum ETH Miner Hardware. Thanks for the help, I ran the h2testw application and went to work as it does take some time like you said and according to the produced report it is likely to be defective so that could well be my problem all along. I have contacted the Vendor for a replacement, we'll see how that goes, Thanks again for the help.