11-29-2018, 03:10 PM
(This post was last modified: 11-29-2018, 03:10 PM by caps.)
Thank you for saving my life. This is beautiful.
Excited to try this out.
Great Job! many thanks for the hard work.
12-01-2018, 01:14 AM
(This post was last modified: 12-01-2018, 11:10 AM by rpm.)
This is really snappy! Thanks!
No luck on HDMI---any suggestions?
The keyboard layout is a little off: shift+2 (@ symbol) and shift+3 (# symbol) yield double quotes and the pound symbol, respectively. @ and # can be found on shift+fn+- and fn+= instead.
Is there a keyboard layout that I can select with dietpi-config that fixes this?
I have the 1080p Pinebook, and have run a few different distros on both emmc and sd without too much hassle. Both "dd" and Pinebook installer seem to produce usable SD cards.
But I'm having difficulty getting this (dietpi) to run on my Pinebook1080p ... I'm trying to run it from SD. I've made attempts with SD written by the Pine64 Installer, downloaded directly from the dietpi site and written via both dd and pv, and each time I end up with the same situation so I don't believe any of the write methods is failing differently than the others.
A few screens full of text flies by, and when it all stops I have a "=>" prompt. What I see next appears to be the "help" output for the fdt command, followed by:
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
** Can't read partition table on 0:0 **
** Invalid partition 1 **
Loading kernel and initrd...
## Error: "load_kernel" not defined
SCRIPT FAILED: continuing...
After that are a bunch of "missing environment variable: {pxeuuid, bootfile, etc.}"
I'm not certain exactly what the Pinebook Installer does, but when using dd and pv I'm writing the decompressed image directly to the block device (/dev/sdb on my linux box, /dev/rdisk2 on my mac). Each method seems to result in the same thing.
I feel like I may be missing something simple and stupid, but cannot seem to find anything in these (or the dietpi) forums. Assistance would be happily accepted.
12-09-2018, 10:03 AM
(This post was last modified: 12-09-2018, 10:05 AM by dhylton.)
Just a quick update ... Still wondering whether something was confusing internal versus external storage, I overwrote the SD with archlinux and booted it without issue. From there, I proceeded to wipe the internal emmc storage and write the dietpi image to that. To my surprise, the pinebook booted right into dietpi that way.
I performed a small bit of configuration and allowed it to update itself and followed with a reboot. The boot failed with similar messages as with the sd boot failures. I powered down and rebooted again. And again. And again. After about 5 attempts, it booted. I immediately tried again, and boot failed.
I wonder what is different between dietpi and the other distributions which make it so unreliable on my pinebook - I have seen zero boot failures from either SD or emmc for 5-6 distributions I've played with. I also wonder what is different with my 1080p pinebook, as I don't see evidence of others having this issue.
I purchased the 64GB emmc along with the 1080p pinebook, and that is what is currently installed. So while I could have botched that connection somehow, doing so would have shown up with all the other distributions as well.
So ... any ideas?
I'm after the most nimble distribution, upon which I'll be running i3 or awesome or another small tiling window manager. I don't need much - the web browser used for research will be the biggest drain, tmux/ssh/nmap will be 90% of what this is used for. The dietpi distribution looks like it should be a good match, but only if I can get it to run ...
I just got a used 14in Pinebook and DietPi 6.18 also won't boot on mine via SD Card. It has the 64GB eMMC upgrade installed.
Armbian 5.56 stable works from both the SD and eMMC so I don't think it's a hardware issue.
![[Image: dietpi-logo_150.png]](http://dietpi.com/images/dietpi-logo_150.png){kind=logo}
