Thanks for all your help. I'll just stick with Ubuntu and KDE for now until my
new 64G eMMC device arrives. A bit if irony, the microSD -> eMMC install works
and shows a 16G device. I tried to install Archlinux and ran into problems as
well.
Again... thank you all for your help. I learned a
On Fri, May 17, 2019 at 08:59:37AM -0400, Ron Georgia wrote:
> What I did:
> # sudo dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c
> bs=1m conv=sync
>
> dd: /dev/rld2c: Input/output error
> 30+0 records in
> 29+0 records out
> 30408704 bytes transferred in 11.034 secs
What I did:
# sudo dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c
bs=1m conv=sync
dd: /dev/rld2c: Input/output error
30+0 records in
29+0 records out
30408704 bytes transferred in 11.034 secs (2755909 bytes/sec)
The link includes fdisk and disklabel info, along with before
> Silly unrelated question Does anyone have pinebook 'ROM' image originals
> somewhere for download ?
try pine64.org. :-)
.mrg.
> On May 16, 2019, at 5:18 PM, Mathew, Cherry G. wrote:
>
> Silly unrelated question. Does anyone have pinebook 'ROM' image originals
> somewhere for download ?
I preserved mine (and installed a 64GB module in its place that has my NetBSD
install). I have a Pine64 eMMC->USB adapter, so I
On 17 May 2019 2:20:40 AM GMT+05:30, Manuel Bouyer
wrote:
>On Thu, May 16, 2019 at 02:47:02PM -0400, Ron Georgia wrote:
>> I did try that, but did not get the results I expected.
>>
>> Expected:
>> 1641+1 records in
>> 1642+0 records out
>> 1721761792 bytes transferred in 14.421 secs (119392676
On Thu, May 16, 2019 at 02:47:02PM -0400, Ron Georgia wrote:
> I did try that, but did not get the results I expected.
>
> Expected:
> 1641+1 records in
> 1642+0 records out
> 1721761792 bytes transferred in 14.421 secs (119392676 bytes/sec)
>
> Actual:
> arm64# time dd if=pinebook1080p.img
I did try that, but did not get the results I expected.
Expected:
1641+1 records in
1642+0 records out
1721761792 bytes transferred in 14.421 secs (119392676 bytes/sec)
Actual:
arm64# time dd if=pinebook1080p.img of=/dev/rld2c bs=1m conv=sync
dd: /dev/rld2c: Input/output error
30+0 records in
On Thu, May 16, 2019 at 12:55:03PM -0400, Ron Georgia wrote:
> I am trying this again. A little different take.
> 1. Downloaded arm64.img to my NetBSD workstation
> 2. make, install of pkgsrc/sysutils/u-boot-pinebook
> 3. dd if=arm64.img of=pinebook1080p.img bs=1m conv=sync,notrunc
> 4. dd
I am trying this again. A little different take.
1. Downloaded arm64.img to my NetBSD workstation
2. make, install of pkgsrc/sysutils/u-boot-pinebook
3. dd if=arm64.img of=pinebook1080p.img bs=1m conv=sync,notrunc
4. dd if=/usr/pkg/share/u-boot/pinebook/u-boot-sunxi-with-spl.bin
Okay… let’s try this again. I restored my Pinebook 1080p to its original
condition. I am including some maybe, helpful data below. I just want to make
sure I understand the process so I do not end up in the same place I just came
out of.
1. I created a NetBSD bootable microSD card using the
You have to write the image to the “entire disk” partition (rld2c), which will
overwrite the disk label anyway.
> On May 14, 2019, at 4:27 PM, Ron Georgia wrote:
>
> Question: if I disklabel -eI ld2 and remove partition e, then dd the image
> again to /dev/rld2e, will that work or will I have
When I dd from a terminal on my Mac, I get an error printed to the console,
"ld2: mbr partition exceeds disk size"
On 5/14/19, 3:38 PM, "Jared McNeill" wrote:
You have to write the image to the “entire disk” partition (rld2c), which
will overwrite the disk label anyway.
> On May
I did, but I get a massive amount of errors.
On 5/14/19, 3:38 PM, "Jared McNeill" wrote:
You have to write the image to the “entire disk” partition (rld2c), which
will overwrite the disk label anyway.
> On May 14, 2019, at 4:27 PM, Ron Georgia wrote:
>
> Question: if I
Question: if I disklabel -eI ld2 and remove partition e, then dd the image
again to /dev/rld2e, will that work or will I have a Pinebrick?
On 5/14/19, 1:54 PM, "Ron Georgia" wrote:
Well... I did both
arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
dd: /dev/rld2c:
Well... I did both
arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
dd: /dev/rld2c: Input/output error
30+0 records in
29+0 records out
30408704 bytes transferred in 9.927 secs (3063231 bytes/sec)
And
arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c
bs=1m
> On May 14, 2019, at 9:33 AM, Ron Georgia wrote:
>
> If I understand correctly:
> 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable Images
> from https://www.invisible.ca/arm/
> 2. download arm64.img from
>
If I understand correctly:
1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable Images
from https://www.invisible.ca/arm/
2. download arm64.img from
ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/
to microSD card.
3. dd image to
Easiest way is to download the image to the SD card, then dd it to the
eMMC:
# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
You can't "wreck" your Pinebook this way as it will always try to boot
from SD card first. So after writing the image to eMMC, shutdown the
computer, remove the SD
Instead of creating the image with dd, I followed the suggestion of building
the image with "highly recommend" Etcher. I am now able to login as root! Not
sure what happened. I am documenting every step of the way in order to make my
journey, mistakes and all, available to other "not so savvy"
20 matches
Mail list logo
