Re: PinebookPro Xorg?

2020-07-14 Thread Mark Kettenis
> Date: Tue, 14 Jul 2020 15:10:04 +1000
> From: Jonathan Gray 
> 
> On Mon, Jul 13, 2020 at 11:26:12PM +0200, Sebastian Reitenbach wrote:
> > Hi,
> > 
> > eventually got my hands on a PinebookPro, installation went fine.
> > 
> > Prepard SD card for initial installation alike:
> > 
> > mount /dev/${DEV}i /mnt
> > mkdir /mnt/rockchip
> > cp /usr/local/share/dtb/arm64/rockchip/rk3399-pinebook-pro.dtb 
> > /mnt/rockchip
> > umount /mnt
> 
> U-Boot includes a builtin dtb in this case, why use the linux one?
> 
> > dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/idbloader.img 
> > of=/dev/${DEV}c seek=64
> > dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/u-boot.itb 
> > of=/dev/${DEV}c seek=16384
> > 
> > DTB and u-boot files are from following packages:
> > dtb-5.7p0   Device Tree Blobs
> > u-boot-aarch64-2020.07 U-Boot firmware
> 
> You are not using U-Boot 2020.07 in your dmesg.
> "U-Boot 2020.01-4-g908d441fef (Jan 20 2020 - 05:02:39 +) Manjaro ARM"

The RK3399 SoC has the annoying property that it prefers eMMC over uSD
when booting.  I believe that there is a switch inside the pinebook
pro to disable the eMMC.  Alternatively you can wipe the start of the
eMMC or install the newer U-Boot on the eMMC.



Re: PinebookPro Xorg?

2020-07-14 Thread Robert Wilkinson
On Tue, Jul 14, 2020 at 05:48:34PM +0200, Mark Kettenis wrote:
> > Date: Tue, 14 Jul 2020 15:10:04 +1000
> > From: Jonathan Gray 
> > 
> > On Mon, Jul 13, 2020 at 11:26:12PM +0200, Sebastian Reitenbach wrote:
> > > Hi,
> > > 
> > > eventually got my hands on a PinebookPro, installation went fine.
> > > 
> > > Prepard SD card for initial installation alike:
> > > 
> > > mount /dev/${DEV}i /mnt
> > > mkdir /mnt/rockchip
> > > cp /usr/local/share/dtb/arm64/rockchip/rk3399-pinebook-pro.dtb 
> > > /mnt/rockchip
> > > umount /mnt
> > 
> > U-Boot includes a builtin dtb in this case, why use the linux one?
> > 
> > > dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/idbloader.img 
> > > of=/dev/${DEV}c seek=64
> > > dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/u-boot.itb 
> > > of=/dev/${DEV}c seek=16384
> > > 
> > > DTB and u-boot files are from following packages:
> > > dtb-5.7p0   Device Tree Blobs
> > > u-boot-aarch64-2020.07 U-Boot firmware
> > 
> > You are not using U-Boot 2020.07 in your dmesg.
> > "U-Boot 2020.01-4-g908d441fef (Jan 20 2020 - 05:02:39 +) Manjaro ARM"
> 
> The RK3399 SoC has the annoying property that it prefers eMMC over uSD
> when booting.  I believe that there is a switch inside the pinebook
> pro to disable the eMMC.  Alternatively you can wipe the start of the
> eMMC or install the newer U-Boot on the eMMC.

I had no problems installing Debian on my PinebookPro. I used some
old Debian and put it on the usb pendrive, booted off that and
installed an up-to-date Debian on uSD card, then booted from the uSD
card so I could encrypt the eMMC and replace the Manjaro with an
encrypted Debian.

At no point do I remember having to do anything other than preparing
the media, it always booted from either the pendrive or eMMC,
without me having to change anything.

Just my experience on my PinebookPro, and not related to OpenBSD.

R
-- 
"We are in the beginning of a mass extinction, and all you can talk
about is money and fairy tales of eternal economic growth."
  - Greta Thunberg



Re: PinebookPro Xorg?

2020-07-14 Thread Sebastian Reitenbach
Hi,

Am Dienstag, Juli 14, 2020 17:48 CEST, schrieb Mark Kettenis 
:

> > Date: Tue, 14 Jul 2020 15:10:04 +1000
> > From: Jonathan Gray 
> >
> > On Mon, Jul 13, 2020 at 11:26:12PM +0200, Sebastian Reitenbach wrote:
> > > Hi,
> > >
> > > eventually got my hands on a PinebookPro, installation went fine.
> > >
> > > Prepard SD card for initial installation alike:
> > >
> > > mount /dev/${DEV}i /mnt
> > > mkdir /mnt/rockchip
> > > cp /usr/local/share/dtb/arm64/rockchip/rk3399-pinebook-pro.dtb 
> > > /mnt/rockchip
> > > umount /mnt
> >
> > U-Boot includes a builtin dtb in this case, why use the linux one?
> >
> > > dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/idbloader.img 
> > > of=/dev/${DEV}c seek=64
> > > dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/u-boot.itb 
> > > of=/dev/${DEV}c seek=16384
> > >
> > > DTB and u-boot files are from following packages:
> > > dtb-5.7p0   Device Tree Blobs
> > > u-boot-aarch64-2020.07 U-Boot firmware
> >
> > You are not using U-Boot 2020.07 in your dmesg.
> > "U-Boot 2020.01-4-g908d441fef (Jan 20 2020 - 05:02:39 +) Manjaro ARM"
>
> The RK3399 SoC has the annoying property that it prefers eMMC over uSD
> when booting.  I believe that there is a switch inside the pinebook
> pro to disable the eMMC.  Alternatively you can wipe the start of the
> eMMC or install the newer U-Boot on the eMMC.

 Thanks for these hints, and it really seemed to take the u-boot from the 
internal eMMC
instead of the one on the uSD card.

So, my first try was to disable the eMMC via the switch, but then the machine 
refused
to start at all, had to reset as described here [1]

once that solved, and it booted again, I installed u-boot-aarch64 package and I 
did that
to the eMMC:

dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/idbloader.img 
of=/dev/sd0c seek=64
dd if=/usr/local/share/u-boot/pinebook-pro-rk3399/u-boot.itb 
of=/dev/sd0c seek=16384

and reboot. I kind of panicked, since the console stayed black, nothing moving, 
same
to the display, I already thought I kind of bricked it. Also the power LED is 
not lit up.
However, after a while, I suddenly saw the console login prompt again. I could 
login to the machine,
reboot, and wait, nothing on the console after reboot, only after a minute or 
two, another
fresh login prompt. However, dmesg seems to say: efi0: Das U-Boot rev 0x20200700
full dmesg below.

Then, still on serial console, I entered:
rcctl -f start xenodm
The command returned, and serial console stopped taking input.
I saw the display getting grey, with some odd vertical stripes.
It seems, with CTRL-ALT F1 etc. I can switch between consoles and xenodm, 
however,
also there, just more dark, and lighter vertical stripes. I could blindly login,
and issue reboot command.
Then on the console, I suddenly saw:
syncing disks... done
rebooting...

dmesg, and Xorg.0.log below.

Any hints on how to get the output of the u-boot, kernel etc. back onto the 
serial console?
Try other, older versions of u-boot and dd that onto eMMC? Someone can
recommend/knows a version better working?

thanks,
Sebastian


[1] 
https://wiki.pine64.org/index.php/Pinebook_Pro#Pinebook_Pro_will_not_power_on_after_toggling_the_eMMC_enable.2Fdisable_switch

OpenBSD 6.7-current (GENERIC.MP) #711: Fri Jul 10 13:46:35 MDT 2020
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 4075687936 (3886MB)
avail mem = 3875155968 (3695MB)
random: good seed from bootblocks
mainbus0 at root: Pine64 Pinebook Pro
psci0 at mainbus0: PSCI 1.1, SMCCC 1.2
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 512KB 64b/line 16-way L2 cache
cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu1: 512KB 64b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu2: 512KB 64b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu3: 512KB 64b/line 16-way L2 cache
cpu4 at mainbus0 mpidr 100: ARM Cortex-A72 r0p2
cpu4: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache
cpu4: 1024KB 64b/line 16-way L2 cache
cpu5 at mainbus0 mpidr 101: ARM Cortex-A72 r0p2
cpu5: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache
cpu5: 1024KB 64b/line 16-way L2 cache
efi0 at mainbus0: UEFI 2.8
efi0: Das U-Boot rev 0x20200700
apm0 at mainbus0
agintc0 at mainbus0 sec shift 3:3 nirq 288 nredist 6 ipi: 0, 1: 
"interrupt-controller"
agintcmsi0 at agintc0
syscon0 at mainbus0: "qos"
syscon1 at mainbus0: "qos"
syscon2 at mainbus0: "qos"
syscon3 at mainbus0: "qos"
syscon4 at mainbus0: "qos"
syscon5 at mainbus0: "qos"
syscon6 at mainbus0: "qos"
syscon7 at mainbus0: "qos"
syscon8 at mainbus0: "qos"
syscon9 at mainbus0