Anyway, Google Chrome gives an error message, because the downloaded file might be pontentially harmful. Might worth a check why.
Foolishly I tried to install it at work, and there are only Windows computers here, and no instructions how to use it on Windows. Not really a problem, I just go home and try again.
An another not really problem, that Kernel 4.9 changed the way how GPIO controllers work. Leap 42.2 uses 4.4, so apparently not a problem, but I don’t know what will 42.3 use. (But I can guess. ) pi4j hasn’t been updated for a while now, so this API won’t work under the other Kernel. I used Raspbian before, and I had to roll back to 4.4 so I could use GPIO+JAVA+LINUX+PI4J at the same time. I don’t know any other API for Raspberry GPIO under Java. Anyway, just a note, you probably can’t do anything about it.
I guessed poorly. I just though about it, since Leaps tended to use (at least the latest two) the latest LTS kernel by their time. But of course, it’s only a problem when using the Pi4J lib. (Or API or whatever it is.)
EDIT: wait a minute, I need the JeOS one. Thanks for catching that one.
Hi
Not set to read only? Unmount the device as well, I don’t know about sudo never use it, always use ‘su -’ the command works for me last time I wrote one (16GB micro sd card)…
Ok, so I put it in into the Pi, but it shows no reaction. The power led is lit, but the others are not even blinking. This Pi works fine with Raspbian. So I still think it’s the SD card, or something with the image? There is an another thread here, but that one at least managed to reach the GRUB. (Plus, he uses X11, and I use JeOS.)
Or wipefs completly annihilates the FS underneath? I just thought it resets it. But then why didn’t xzcat send any message, when it copied the image to the card?
Ok, so I put it in into the Pi, but it shows no reaction. The power led
is lit, but the others are not even blinking. This Pi works fine with
Raspbian. So I still think it’s the SD card, or something with the
image? There is an another thread here, but that one at least managed to
reach the GRUB. (Plus, he uses X11, and I use JeOS.)
Or wipefs completly annihilates the FS underneath? I just thought it
resets it. But then why didn’t xzcat send any message, when it copied
the image to the card?
Hi
Yes, wipefs cleand out all info, use fdisk and create a new partition
on it, then format to say fat and see if it works ok…
Because xzcat is piped through dd, so no output from dd… you can use
the kill command to see where it’s at…
kill -USR1 <pid of dd command>
You did check the md5 sum on the image?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.22.2|4.4.62-18.6-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hi, Malcolm,
Sorry I’m late to this or I might have helped. “sudo do-something | do-something-else” has root privs only for the first command. If you start with a decompressed .raw file, then “sudo dd …” works. But when I’m doing several steps, I find it easiest to just “su -” and then do the tasks, as you suggested. (And yes, I understand the dangers, so I exit back to my account as soon as I’m done. Did my first “su; cd /; rm *” in about 1988 on an AT&T 3B2 box. Took a LONG time to rebuild that thing!).