NetBSD will does not install to eMMC

[ronverbs]

I downloaded the NetBSD Pinebook image from invisible.ca (https://www.invisible.ca/arm/) and created a microSD card, as directed using Etcher. My Pinebook (1080p) booted, but when I dd'd the image to /dev/rdl2c I got a ton of errors. Now my Pinebook does not boot, unless there is a SD card inserted.

arm64# 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.143 secs (2728951 bytes/sec)
This generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen.

My disklabel looks like this:
arm64# disklabel ld2

    # /dev/rld2:

    type: ld

    disk: ld2

    label: default label

    flags:

    bytes/sector: 512

    sectors/track: 63

    tracks/cylinder: 32

    sectors/cylinder: 2016

    cylinders: 1040

    total sectors: 2097152

    rpm: 3600

    interleave: 1

    trackskew: 0

    cylinderskew: 0

    headswitch: 0           # microseconds

    track-to-track seek: 0  # microseconds

    drivedata: 0

    5 partitions:

    #        size    offset     fstype [fsize bsize cpg/sgs]

     c:   2097152         0     4.2BSD      0     0     0  # (Cyl.      0 -   1040*)

     e:    163840     32768      MSDOS                     # (Cyl.     16*-     97*)

    disklabel: boot block size 0

    disklabel: super block size 0
    disklabel: partitions c and e overlap

Any ideas on how to get NetBSD running on my brand new Pinebook?

[url=http://www.invisible.ca/][/url]

[haukef]

I downloaded the NetBSD Pinebook image from invisible.ca (https://www.invisible.ca/arm/) and created a microSD card, as directed using Etcher. My Pinebook (1080p) booted, but when I dd'd the image to /dev/rdl2c I got a ton of errors. Now my Pinebook does not boot, unless there is a SD card inserted.

arm64# 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.143 secs (2728951 bytes/sec)
This generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen.

The bs=1M sounds excessive... depending on the hardware, there are limitations on the block size the kernel will handle. 
Oh, and leave out the conv=sync? The man page says "Pad every input block to the input buffer size." - you don't want that.

Maybe re-try with something like 

dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=32k

?

[ronverbs]

I downloaded the NetBSD Pinebook image from invisible.ca (https://www.invisible.ca/arm/) and created a microSD card, as directed using Etcher. My Pinebook (1080p) booted, but when I dd'd the image to /dev/rdl2c I got a ton of errors. Now my Pinebook does not boot, unless there is a SD card inserted.

arm64# 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.143 secs (2728951 bytes/sec)
This generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen.

The bs=1M sounds excessive... depending on the hardware, there are limitations on the block size the kernel will handle. 
Oh, and leave out the conv=sync? The man page says "Pad every input block to the input buffer size." - you don't want that.

Maybe re-try with something like 

dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=32k

?

Thank you for your response. I did try that and got the same response, that is dd errors and a blank screen upon rebooting. For now I may stick with KDE Neon. At least that works. Sad though, I am such a NetBSD fan boy.

[KC9UDX]

I don't know why the error (it looks like you're writing beyond the end of the partition). But 1m does not sound excessive to me, I tend to use 8m.

And maybe I'm missing something but I think you want to write to /dev/rld2 rather than /dev/rld2c no?