Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 lot. On 5/17/19, 9:10 AM, "Manuel Bouyer" wrote: 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 (2755909 bytes/sec) > > The link includes fdisk and disklabel info, along with before dd and after dd dmesg. > https://pastebin.com/vAR5U0tj it looks like you have real hardware errors here ... -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 (2755909 bytes/sec) > > The link includes fdisk and disklabel info, along with before dd and after dd > dmesg. > https://pastebin.com/vAR5U0tj it looks like you have real hardware errors here ... -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 dd and after dd dmesg. https://pastebin.com/vAR5U0tj On 5/16/19, 8:19 PM, "Mathew, Cherry G." wrote: 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 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 >> 29+0 records out >> 30408704 bytes transferred in 10.334 secs (2942587 bytes/sec) > >Anything in dmesg about this ? > >> >> Trying hard to not sound frustrated, but what am I missing. Is the >eMMC messed up maybe? Once I boot from the microSD card, what do I dd >to the raw ld2 device? I was able to dd arm64.img to /dev/rld2c, but I >am not sure how to install the u-boot portion. I hate being a pain, but >I really want my NetBSD. (Blast from the 80s?) > >You should be able to do it the same way to did your sd card. Silly unrelated question. Does anyone have pinebook 'ROM' image originals somewhere for download ? -- Sent from my phone. Please excuse my brevity.
re: Pinebook and NetBSD 8.99.39 [UPDATE]
> Silly unrelated question Does anyone have pinebook 'ROM' image originals > somewhere for download ? try pine64.org. :-) .mrg.
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
> 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 will dig it out and make a dump of it. -- thorpej
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 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 >> 29+0 records out >> 30408704 bytes transferred in 10.334 secs (2942587 bytes/sec) > >Anything in dmesg about this ? > >> >> Trying hard to not sound frustrated, but what am I missing. Is the >eMMC messed up maybe? Once I boot from the microSD card, what do I dd >to the raw ld2 device? I was able to dd arm64.img to /dev/rld2c, but I >am not sure how to install the u-boot portion. I hate being a pain, but >I really want my NetBSD. (Blast from the 80s?) > >You should be able to do it the same way to did your sd card. Silly unrelated question. Does anyone have pinebook 'ROM' image originals somewhere for download ? -- Sent from my phone. Please excuse my brevity.
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 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 10.334 secs (2942587 bytes/sec) Anything in dmesg about this ? > > Trying hard to not sound frustrated, but what am I missing. Is the eMMC > messed up maybe? Once I boot from the microSD card, what do I dd to the raw > ld2 device? I was able to dd arm64.img to /dev/rld2c, but I am not sure how > to install the u-boot portion. I hate being a pain, but I really want my > NetBSD. (Blast from the 80s?) You should be able to do it the same way to did your sd card. -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 29+0 records out 30408704 bytes transferred in 10.334 secs (2942587 bytes/sec) Trying hard to not sound frustrated, but what am I missing. Is the eMMC messed up maybe? Once I boot from the microSD card, what do I dd to the raw ld2 device? I was able to dd arm64.img to /dev/rld2c, but I am not sure how to install the u-boot portion. I hate being a pain, but I really want my NetBSD. (Blast from the 80s?) On 5/16/19, 1:31 PM, "Manuel Bouyer" wrote: 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 if=/usr/pkg/share/u-boot/pinebook/u-boot-sunxi-with-spl.bin of=pinebook1080p.img bs=1k seek=8 conv=sync > 5. scp image to Mac > 6. used Pinebook flash program for Mac to "flash" microSD with image pinebook1080p.img > 7. Booted Pinebook with pinebook1080p.img microSD card (booted perfectly) > 8. scp a copy of pinebook1080p.img to Pinebook booted from SD card > 9. arm64# dd if=pinebook1080p.img of=/dev/ld2c bs=1m conv=sync This should be /dev/rld2c -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 if=/usr/pkg/share/u-boot/pinebook/u-boot-sunxi-with-spl.bin > of=pinebook1080p.img bs=1k seek=8 conv=sync > 5. scp image to Mac > 6. used Pinebook flash program for Mac to "flash" microSD with image > pinebook1080p.img > 7. Booted Pinebook with pinebook1080p.img microSD card (booted perfectly) > 8. scp a copy of pinebook1080p.img to Pinebook booted from SD card > 9. arm64# dd if=pinebook1080p.img of=/dev/ld2c bs=1m conv=sync This should be /dev/rld2c -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 of=pinebook1080p.img bs=1k seek=8 conv=sync 5. scp image to Mac 6. used Pinebook flash program for Mac to "flash" microSD with image pinebook1080p.img 7. Booted Pinebook with pinebook1080p.img microSD card (booted perfectly) 8. scp a copy of pinebook1080p.img to Pinebook booted from SD card 9. arm64# dd if=pinebook1080p.img of=/dev/ld2c bs=1m conv=sync The last step, as usual, is generating a TON (907.185kg) of errors. It has been running for about three hours. I am thinking that's not a good sign. I'll let it run all night to see if it finishes. Question: should I instead try to dd if=/dev/ld0 of=/dev/ld2 bs=1m conv=sync? I mean, as long as the SD is the same size as eMMC (16G). 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 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: 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 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) > >Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? > >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: >#sizeoffset 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 > >I will surmise that overlapping partitions are not good? > >On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > > > >> 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 ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. > >You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > >> 3. dd image to /dev/rld2c >> 4. Power down, remove SD card and reboot. >> >> Correct? >> For YES, press 1 >> For NO, press 2 >> >> On 5/14/19, 10:15 AM, "Jared McNeill" wrote: >> >> 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 card, and power it back on. If something goes >> wrong, plug the SD card back in and it will boot from that device when you >> power it back on. >> >> >> On Tue, 14 May 2019, Ron Georgia wrote: >> >>> 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" Pinebook users. >>>
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 image from invisible.ca 2. I boot the Pinebook and ftp that same image to the microSD card. 3. I dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m sync=conv 4. Power off Pinebook and remove microSD card. 5. Power on. Should boot NetBSD. Is that correct? What about the message “ld2: mbr partition exceeds disk size?” Is that a problem? arm64$ ll -h total 1.6G -rw-r--r-- 1 xxx users 1.6G May 14 17:10 NetBSD-evbarm-aarch64-201905120950Z-pinebook.img arm64$ sudo 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 3 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) disklabel: boot block size 0 disklabel: super block size 0 disklabel: partitions a and c overlap arm64$ dmesg | grep -i ld2 [ 2.830954] ld2 at sdmmc2: <0x45:0x0100:DF4016:0x00:0xfe875b0b:0x000> [ 2.849514] ld2: 1024 MB, 1040 cyl, 32 head, 63 sec, 512 bytes/sect x 2097152 sectors [ 2.879516] ld2: mbr partition exceeds disk size [ 2.879516] ld2: 8-bit width, 200.000 MHz [ 7.895029] ld2: mbr partition exceeds disk size [75.708145] ld2: mbr partition exceeds disk size [ 398.482117] ld2: mbr partition exceeds disk size arm64$ sudo fdisk ld2 fdisk: Cannot determine the number of heads Disk: /dev/rld2 NetBSD disklabel disk geometry: cylinders: 1040, heads: 32, sectors/track: 63 (2016 sectors/cylinder) total sectors: 2097152, bytes/sector: 512 BIOS disk geometry: cylinders: 130, heads: 255, sectors/track: 63 (16065 sectors/cylinder) total sectors: 2097152 Partitions aligned to 2048 sector boundaries, offset 63 Partition table: 0: Linux native (sysid 131) start 40960, size 30736384 (15008 MB, Cyls 2/140/11-1915/204/17) PBR is not bootable: All bytes are identical (0x00) 1: 2: 3: No active partition. Drive serial number: 1687624172 (0x649719ec) 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 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: 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 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) > >Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? > >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: >#sizeoffset fstype [fsize bsize cpg/sgs] > c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) > e:
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 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: 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 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) > >Both commands generated a ton of "ld2c: error writing fsbn..." errors. > When I reboot I get a blank screen. ( Any thoughts on what I can do? > >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: >#sizeoffset 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 > >I will surmise that overlapping partitions are not good? > >On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > > > >> 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 >> ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ >> to microSD card. > >You can dd the invisible.ca imagine to the eMMC as well. It's just a > standard arm64.img with u-boot helpfully added by Jared; no need to download > a second one (to which you would then need to add u-boot). > >> 3. dd image to /dev/rld2c >> 4. Power down, remove SD card and reboot. >> >> Correct? >> For YES, press 1 >> For NO, press 2 >> >> On 5/14/19, 10:15 AM, "Jared McNeill" wrote: >> >> 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 card, and power it back on. If something goes >> wrong, plug the SD card back in and it will boot from that device when you >> power it back on. >> >> >> On Tue, 14 May 2019, Ron Georgia wrote: >> >>> 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" Pinebook users. >>> >>> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per >>> https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >>> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and >>> install? >>> >>> === MISC DATA === >>> arm64# disklabel ld0 >>> # /dev/rld0: >>> type: SCSI >>> disk: STORAGE DEVICE >>> label: fictitious >>> flags: removable >>> bytes/sector: 512 >>> sectors/track: 32 >>> tracks/cylinder: 64 >>> sectors/cylinder: 2048 >>> cylinders: 1641 >>> total sectors: 31116288 >>> rpm: 3600 >>> interleave: 1 >>> trackskew: 0 >>> cylinderskew: 0 >>> headswitch: 0 # microseconds >>> track-to-track seek: 0 # microseconds >>> drivedata: 0 >>> >>> 8 partitions: >>> #sizeoffset fstype [fsize bsize cpg/sgs] >>> a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - >>> 15193*) >>> b:262144196608 swap # (Cyl. 96 - >>> 223) >>> c: 31116288 0 unused 0 0# (Cyl. 0 - >>> 15193*) >>> d: 31116288 0 unused 0 0# (Cyl. 0 - >>> 15193*) >>> e:163840 32768 MSDOS # (Cyl. 16 - >>> 95) >>> >>> arm64# disklabel ld2 >>> # /dev/rld2: >>> type: ld >>> disk: ld2 >>> label: default label >>> flags: >>>
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 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 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: 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 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) > >Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? > >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: >#sizeoffset 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 > >I will surmise that overlapping partitions are not good? > >On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > > > >> 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 ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. > >You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > >> 3. dd image to /dev/rld2c >> 4. Power down, remove SD card and reboot. >> >> Correct? >> For YES, press 1 >> For NO, press 2 >> >> On 5/14/19, 10:15 AM, "Jared McNeill" wrote: >> >> 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 card, and power it back on. If something goes >> wrong, plug the SD card back in and it will boot from that device when you >> power it back on. >> >> >> On Tue, 14 May 2019, Ron Georgia wrote: >> >>> 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" Pinebook users. >>> >>> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >>> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >>> >>> === MISC DATA === >>> arm64# disklabel ld0 >>> # /dev/rld0: >>> type: SCSI >>> disk: STORAGE DEVICE >>> label: fictitious >>> flags: removable >>> bytes/sector: 512 >>> sectors/track: 32 >>> tracks/cylinder: 64 >>> sectors/cylinder: 2048 >>> cylinders: 1641 >>> total sectors: 31116288 >>> rpm: 3600 >>> interleave: 1 >>> trackskew: 0 >>> cylinderskew: 0 >>> headswitch: 0 # microseconds >>> track-to-track seek: 0 # microseconds >>> drivedata: 0 >>> >>> 8 partitions: >>> #size
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 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: 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 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) > >Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? > >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: >#sizeoffset 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 > >I will surmise that overlapping partitions are not good? > >On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > > > >> 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 ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. > >You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > >> 3. dd image to /dev/rld2c >> 4. Power down, remove SD card and reboot. >> >> Correct? >> For YES, press 1 >> For NO, press 2 >> >> On 5/14/19, 10:15 AM, "Jared McNeill" wrote: >> >> 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 card, and power it back on. If something goes >> wrong, plug the SD card back in and it will boot from that device when you >> power it back on. >> >> >> On Tue, 14 May 2019, Ron Georgia wrote: >> >>> 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" Pinebook users. >>> >>> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >>> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >>> >>> === MISC DATA === >>> arm64# disklabel ld0 >>> # /dev/rld0: >>> type: SCSI >>> disk: STORAGE DEVICE >>> label: fictitious >>> flags: removable >>> bytes/sector: 512 >>> sectors/track: 32 >>> tracks/cylinder: 64 >>> sectors/cylinder: 2048 >>> cylinders: 1641 >>> total sectors: 31116288 >>> rpm: 3600 >>> interleave: 1 >>> trackskew: 0 >>> cylinderskew: 0 >>> headswitch: 0 # microseconds >>> track-to-track seek: 0 # microseconds >>> drivedata: 0 >>> >>> 8 partitions: >>> #sizeoffset fstype [fsize bsize cpg/sgs] >>> a: 30657536458752
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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: 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 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) Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? 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: #sizeoffset 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 I will surmise that overlapping partitions are not good? On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > 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 ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > 3. dd image to /dev/rld2c > 4. Power down, remove SD card and reboot. > > Correct? > For YES, press 1 > For NO, press 2 > > On 5/14/19, 10:15 AM, "Jared McNeill" wrote: > >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 card, and power it back on. If something goes >wrong, plug the SD card back in and it will boot from that device when you >power it back on. > > >On Tue, 14 May 2019, Ron Georgia wrote: > >> 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" Pinebook users. >> >> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >> >> === MISC DATA === >> arm64# disklabel ld0 >> # /dev/rld0: >> type: SCSI >> disk: STORAGE DEVICE >> label: fictitious >> flags: removable >> bytes/sector: 512 >> sectors/track: 32 >> tracks/cylinder: 64 >> sectors/cylinder: 2048 >> cylinders: 1641 >> total sectors: 31116288 >> rpm: 3600 >> interleave: 1 >> trackskew: 0 >> cylinderskew: 0 >> headswitch: 0 # microseconds >> track-to-track seek: 0 # microseconds >> drivedata: 0 >> >> 8 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs] >> a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - 15193*) >> b:262144196608 swap # (Cyl. 96 -223) >> c: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) >> d: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) >>
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 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) Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? 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: #sizeoffset 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 I will surmise that overlapping partitions are not good? On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > 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 ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > 3. dd image to /dev/rld2c > 4. Power down, remove SD card and reboot. > > Correct? > For YES, press 1 > For NO, press 2 > > On 5/14/19, 10:15 AM, "Jared McNeill" wrote: > >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 card, and power it back on. If something goes >wrong, plug the SD card back in and it will boot from that device when you >power it back on. > > >On Tue, 14 May 2019, Ron Georgia wrote: > >> 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" Pinebook users. >> >> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >> >> === MISC DATA === >> arm64# disklabel ld0 >> # /dev/rld0: >> type: SCSI >> disk: STORAGE DEVICE >> label: fictitious >> flags: removable >> bytes/sector: 512 >> sectors/track: 32 >> tracks/cylinder: 64 >> sectors/cylinder: 2048 >> cylinders: 1641 >> total sectors: 31116288 >> rpm: 3600 >> interleave: 1 >> trackskew: 0 >> cylinderskew: 0 >> headswitch: 0 # microseconds >> track-to-track seek: 0 # microseconds >> drivedata: 0 >> >> 8 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs] >> a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - 15193*) >> b:262144196608 swap # (Cyl. 96 - 223) >> c: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) >> d: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) >> e:163840 32768 MSDOS # (Cyl. 16 - 95) >> >> 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 >> >> 3 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs]
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
> 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 > ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ > to microSD card. You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > 3. dd image to /dev/rld2c > 4. Power down, remove SD card and reboot. > > Correct? > For YES, press 1 > For NO, press 2 > > On 5/14/19, 10:15 AM, "Jared McNeill" wrote: > >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 card, and power it back on. If something goes >wrong, plug the SD card back in and it will boot from that device when you >power it back on. > > >On Tue, 14 May 2019, Ron Georgia wrote: > >> 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" >> Pinebook users. >> >> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per >> https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and >> install? >> >> === MISC DATA === >> arm64# disklabel ld0 >> # /dev/rld0: >> type: SCSI >> disk: STORAGE DEVICE >> label: fictitious >> flags: removable >> bytes/sector: 512 >> sectors/track: 32 >> tracks/cylinder: 64 >> sectors/cylinder: 2048 >> cylinders: 1641 >> total sectors: 31116288 >> rpm: 3600 >> interleave: 1 >> trackskew: 0 >> cylinderskew: 0 >> headswitch: 0 # microseconds >> track-to-track seek: 0 # microseconds >> drivedata: 0 >> >> 8 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs] >> a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - >> 15193*) >> b:262144196608 swap # (Cyl. 96 - >> 223) >> c: 31116288 0 unused 0 0# (Cyl. 0 - >> 15193*) >> d: 31116288 0 unused 0 0# (Cyl. 0 - >> 15193*) >> e:163840 32768 MSDOS # (Cyl. 16 - >> 95) >> >> 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 >> >> 3 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs] >> a: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - >> 1040*) >> c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - >> 1040*) >> disklabel: boot block size 0 >> disklabel: super block size 0 >> disklabel: partitions a and c overlap >> >> arm64# gpt show ld0 >> GPT not found, displaying data from MBR. >> >>start size index contents >>0 1 MBR >>1 32767 Unused >>32768163840 1 MBR part 12 (active) >> 196608262144 Unused >> 458752 30657536 2 MBR part 169 >> >> arm64# gpt show ld2 >> gpt: /dev/rld2: map entry doesn't fit media: new start + new size < start + >> size >> (1 + 1f < a000 + 1d5) >> >> arm64# dmesg | grep ld >> [ 1.16] axpreg5 at axppmic0: eldo2 >> [ 2.737735] sdmmc1: autoconfiguration error: couldn't enable card: 60 >> [ 2.811871] ld2 at sdmmc2: <0x45:0x0100:DF4016:0x00:0xfe875b0b:0x000> >> [ 2.811871] ld2: 1024 MB, 1040 cyl, 32 head, 63 sec, 512 bytes/sect x >> 2097152 sectors >> [ 2.828746] ld0 at sdmmc0: <0x03:0x5344:SS16G:0x80:0x42ce3d51:0x122> >> [ 2.848748] ld0: 15193 MB, 7717 cyl, 64 head, 63 sec, 512 bytes/sect x >> 31116288 sectors >> [ 2.848748] ld2: mbr partition exceeds disk size >> [ 2.848748] ld2: 8-bit width, 200.000 MHz >> [ 2.876482] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz >> [ 7.617842] ld2: mbr partition exceeds disk size >> [ 7.627841] boot device: ld0 >> [ 7.627841] root on ld0a dumps on ld0b >> [ 424.699875] ld2: mbr partition exceeds disk size >> [ 424.709875] ld2: mbr partition exceeds disk size >> [ 431.049997] ld2: mbr
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 /dev/rld2c 4. Power down, remove SD card and reboot. Correct? For YES, press 1 For NO, press 2 On 5/14/19, 10:15 AM, "Jared McNeill" wrote: 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 card, and power it back on. If something goes wrong, plug the SD card back in and it will boot from that device when you power it back on. On Tue, 14 May 2019, Ron Georgia wrote: > 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" Pinebook users. > > How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? > Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? > > === MISC DATA === > arm64# disklabel ld0 > # /dev/rld0: > type: SCSI > disk: STORAGE DEVICE > label: fictitious > flags: removable > bytes/sector: 512 > sectors/track: 32 > tracks/cylinder: 64 > sectors/cylinder: 2048 > cylinders: 1641 > total sectors: 31116288 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 8 partitions: > #sizeoffset fstype [fsize bsize cpg/sgs] > a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - 15193*) > b:262144196608 swap # (Cyl. 96 - 223) > c: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) > d: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) > e:163840 32768 MSDOS # (Cyl. 16 - 95) > > 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 > > 3 partitions: > #sizeoffset fstype [fsize bsize cpg/sgs] > a: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) > c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) > disklabel: boot block size 0 > disklabel: super block size 0 > disklabel: partitions a and c overlap > > arm64# gpt show ld0 > GPT not found, displaying data from MBR. > > start size index contents > 0 1 MBR > 1 32767 Unused > 32768163840 1 MBR part 12 (active) >196608262144 Unused >458752 30657536 2 MBR part 169 > > arm64# gpt show ld2 > gpt: /dev/rld2: map entry doesn't fit media: new start + new size < start + size > (1 + 1f < a000 + 1d5) > > arm64# dmesg | grep ld > [ 1.16] axpreg5 at axppmic0: eldo2 > [ 2.737735] sdmmc1: autoconfiguration error: couldn't enable card: 60 > [ 2.811871] ld2 at sdmmc2: <0x45:0x0100:DF4016:0x00:0xfe875b0b:0x000> > [ 2.811871] ld2: 1024 MB, 1040 cyl, 32 head, 63 sec, 512 bytes/sect x 2097152 sectors > [ 2.828746] ld0 at sdmmc0: <0x03:0x5344:SS16G:0x80:0x42ce3d51:0x122> > [ 2.848748] ld0: 15193 MB, 7717 cyl, 64 head, 63 sec, 512 bytes/sect x 31116288 sectors > [ 2.848748] ld2: mbr partition exceeds disk size > [ 2.848748] ld2: 8-bit width, 200.000 MHz > [ 2.876482] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz > [ 7.617842] ld2: mbr partition exceeds disk size > [ 7.627841] boot device: ld0 > [ 7.627841] root on ld0a dumps on ld0b > [ 424.699875] ld2: mbr partition exceeds disk size > [ 424.709875] ld2: mbr partition exceeds disk size > [ 431.049997] ld2: mbr partition exceeds disk size > [ 431.059997] ld2: mbr partition exceeds
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
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 card, and power it back on. If something goes wrong, plug the SD card back in and it will boot from that device when you power it back on. On Tue, 14 May 2019, Ron Georgia wrote: 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" Pinebook users. How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? === MISC DATA === arm64# disklabel ld0 # /dev/rld0: type: SCSI disk: STORAGE DEVICE label: fictitious flags: removable bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 1641 total sectors: 31116288 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 8 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - 15193*) b:262144196608 swap # (Cyl. 96 -223) c: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) d: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) e:163840 32768 MSDOS # (Cyl. 16 - 95) 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 3 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) disklabel: boot block size 0 disklabel: super block size 0 disklabel: partitions a and c overlap arm64# gpt show ld0 GPT not found, displaying data from MBR. start size index contents 0 1 MBR 1 32767 Unused 32768163840 1 MBR part 12 (active) 196608262144 Unused 458752 30657536 2 MBR part 169 arm64# gpt show ld2 gpt: /dev/rld2: map entry doesn't fit media: new start + new size < start + size (1 + 1f < a000 + 1d5) arm64# dmesg | grep ld [ 1.16] axpreg5 at axppmic0: eldo2 [ 2.737735] sdmmc1: autoconfiguration error: couldn't enable card: 60 [ 2.811871] ld2 at sdmmc2: <0x45:0x0100:DF4016:0x00:0xfe875b0b:0x000> [ 2.811871] ld2: 1024 MB, 1040 cyl, 32 head, 63 sec, 512 bytes/sect x 2097152 sectors [ 2.828746] ld0 at sdmmc0: <0x03:0x5344:SS16G:0x80:0x42ce3d51:0x122> [ 2.848748] ld0: 15193 MB, 7717 cyl, 64 head, 63 sec, 512 bytes/sect x 31116288 sectors [ 2.848748] ld2: mbr partition exceeds disk size [ 2.848748] ld2: 8-bit width, 200.000 MHz [ 2.876482] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz [ 7.617842] ld2: mbr partition exceeds disk size [ 7.627841] boot device: ld0 [ 7.627841] root on ld0a dumps on ld0b [ 424.699875] ld2: mbr partition exceeds disk size [ 424.709875] ld2: mbr partition exceeds disk size [ 431.049997] ld2: mbr partition exceeds disk size [ 431.059997] ld2: mbr partition exceeds disk size [ 431.059997] ld2: mbr partition exceeds disk size [ 431.14] ld2: mbr partition exceeds disk size [ 442.320213] ld2: mbr partition exceeds disk size [ 746.325984] ld2: mbr partition exceeds disk size [ 746.335984] ld2: mbr partition exceeds disk size [ 1592.422047] ld2: mbr partition exceeds disk size [ 1592.422047] ld2: mbr partition exceeds disk size [ 1679.653695] ld2: mbr partition exceeds disk size [ 1679.673697] ld2: mbr partition exceeds disk size [ 1684.513788] ld2: mbr partition exceeds disk size [ 1684.513788] ld2: mbr partition exceeds disk size [ 1684.563793] ld2: mbr partition exceeds disk size [ 1684.583793] ld2: mbr partition exceeds disk size [ 1684.583793] ld2: mbr partition exceeds disk size [ 1761.785290] ld2: mbr partition exceeds disk size [ 1778.945617] ld2: mbr partition exceeds disk size [ 1993.819664] ld2: mbr partition exceeds disk size arm64# mount /dev/ld0a on / type ffs (noatime, local) /dev/ld0e on /boot type msdos (local) kernfs on /kern type kernfs (local) ptyfs on
