Pinebook Pro instructions for F-34

[Peter Robinson]

For those that are interested here is the write up for getting
Pinebook Pro running Fedora:

https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/

Feel free to reply on this thread for questions.

[Andreas Reschke]

Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  For those that are interested here is the write up for getting
>  Pinebook Pro running Fedora:
>
>  https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>
>  Feel free to reply on this thread for questions.
>  _______________________________________________
>  arm mailing list -- arm(a)lists.fedoraproject.org
>  To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Hello Peter,

I have to thank you very much for your work !!

I've managed to install Fedora on my Pinebook Pro with your steps. The 
whole installation of Fedora I have to do over serial output. Even after 
finished installation and final boot the screen is blank. Green Power 
LED is on, serial output is working.

What I've done wrong?

Thanks

Andreas

[Peter Robinson]

On Tue, May 4, 2021 at 3:45 PM Andreas Reschke <arm_ml(a)rirasoft.de&gt; wrote:
>  Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  > For those that are interested here is the write up for getting
>  > Pinebook Pro running Fedora:
>  >
>  > https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>  >
>  > Feel free to reply on this thread for questions. 
>  Hello Peter,
>
>  I have to thank you very much for your work !!
>
>  I've managed to install Fedora on my Pinebook Pro with your steps. The
>  whole installation of Fedora I have to do over serial output. Even after
>  finished installation and final boot the screen is blank. Green Power
>  LED is on, serial output is working.
>
>  What I've done wrong? 
Are you sure it's booting with the Fedora built U-Boot and not an old
one on the EMMC?

If you're booting and seeing output over the serial console make sure
the U-Boot output is a 2021.04 version with a string something like:
U-Boot 2021.04 (Apr 28 2021 - 00:00:00)

[Andreas Reschke]

Am 04.05.21 um 16:48 schrieb Peter Robinson:
>  On Tue, May 4, 2021 at 3:45 PM Andreas Reschke
> <arm_ml(a)rirasoft.de&gt; wrote:
> >
> > Am 04.05.21 um 13:39 schrieb Peter Robinson:
> >> For those that are interested here is the write up for getting
> >> Pinebook Pro running Fedora:
> >>
> >> https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
> >>
> >> Feel free to reply on this thread for questions.
> > Hello Peter,
> >
> > I have to thank you very much for your work !!
> >
> > I've managed to install Fedora on my Pinebook Pro with your steps. The
> > whole installation of Fedora I have to do over serial output. Even after
> > finished installation and final boot the screen is blank. Green Power
> > LED is on, serial output is working.
> >
> > What I've done wrong?
>  Are you sure it's booting with the Fedora built U-Boot and not an old
>  one on the EMMC?
>
>  If you're booting and seeing output over the serial console make sure
>  the U-Boot output is a 2021.04 version with a string something like:
>  U-Boot 2021.04 (Apr 28 2021 - 00:00:00) 
U-Boot TPL 2021.04 (Apr 21 2021 -
00:00:00)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
Trying to boot from MMC2


U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM

SoC: Rockchip rk3399
Reset cause: RST
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0



load_video
set gfxpayload=keep
insmod gzio
linux ($root)/vmlinuz-5.11.17-300.fc34.aarch64 
root=UUID=2b11b4d4-a606-4ee3-a6eb-a9de50d75d95 ro rootflags=subvol=root00

initrd ($root)/initramfs-5.11.17-300.fc34.aarch64.img


I think there is rest of Manjaro U-Boot there...

[Peter Robinson]

Could you please trim your emails of unnecessary text!

>  > U-Boot 2021.04 (Apr 28 2021 - 00:00:00)
>  U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
>  Channel 0: LPDDR4, 50MHz
>  BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  Channel 1: LPDDR4, 50MHz
>  BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  256B stride
>  lpddr4_set_rate: change freq to 400000000 mhz 0, 1
>  lpddr4_set_rate: change freq to 800000000 mhz 1, 0
>  Trying to boot from BOOTROM
>  Returning to boot ROM...
>
>  U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
>  Trying to boot from MMC2
>
>
>  U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM 
Yep, so you probably need to disable the EMMC because it's loading it
from the EMMC for some reason.

If it loads to Fedora you can also run "dd if=/dev/zero
of=/dev/mmcblkX bs=1M count=10" (update the mmcblkX to the right one)
to zero out the beginning of the EMMC if you don't care about the
contents of it.

[Andreas Reschke]

Am 04.05.21 um 16:58 schrieb Peter Robinson:
> >> U-Boot 2021.04 (Apr 28 2021 - 00:00:00)
> > U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
> > Channel 0: LPDDR4, 50MHz
> > BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> > Channel 1: LPDDR4, 50MHz
> > BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> > 256B stride
> > lpddr4_set_rate: change freq to 400000000 mhz 0, 1
> > lpddr4_set_rate: change freq to 800000000 mhz 1, 0
> > Trying to boot from BOOTROM
> > Returning to boot ROM...
> >
> > U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
> > Trying to boot from MMC2
> >
> >
> > U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM
>  Yep, so you probably need to disable the EMMC because it's loading it
>  from the EMMC for some reason.
>
>  If it loads to Fedora you can also run "dd if=/dev/zero
>  of=/dev/mmcblkX bs=1M count=10" (update the mmcblkX to the right one)
>  to zero out the beginning of the EMMC if you don't care about the
>  contents of it.
>  _______________________________________________
>  arm mailing list -- arm(a)lists.fedoraproject.org
>  To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
After "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=10" I want to boot 
with Fedora-Everything-netinst-aarch64-34-1.2.iso

How to boot from USB?

Message

U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Trying to boot from SPI


U-Boot 2021.04 (Apr 21 2021 - 00:00:00 +0000)

SoC: Rockchip rk3399
Reset cause: RST
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page 
size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Pine64 Pinebook Pro
Net:   No ethernet found.
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 2 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 4 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
        scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
Card did not respond to voltage select! : -110

Device 0: Vendor: 0x15b7 Rev: 211070WD Prod: 2018FV440610
             Type: Hard Disk
             Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
... is now current device
** No partition table - nvme 0 **

Device 0: Vendor: Verbatim Rev: PMAP Prod: STORE N GO
             Type: Removable Hard Disk
             Capacity: 14808.0 MB = 14.4 GB (30326784 x 512)
... is now current device
Scanning usb 0:1...
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399-pinebook-pro-rk3399
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 
16 MiB
dhcp - boot image via network using DHCP/TFTP protocol

Usage:
dhcp [loadAddress] [[hostIPaddr:]bootfilename]
## Executing script at 00500000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
=>

[Andreas Reschke]

Am 05.05.21 um 17:51 schrieb Andreas Reschke:
>  Am 04.05.21 um 16:58 schrieb Peter Robinson:
> >>> U-Boot 2021.04 (Apr 28 2021 - 00:00:00)
> >> U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
> >> Channel 0: LPDDR4, 50MHz
> >> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> >> Channel 1: LPDDR4, 50MHz
> >> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> >> 256B stride
> >> lpddr4_set_rate: change freq to 400000000 mhz 0, 1
> >> lpddr4_set_rate: change freq to 800000000 mhz 1, 0
> >> Trying to boot from BOOTROM
> >> Returning to boot ROM...
> >>
> >> U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
> >> Trying to boot from MMC2
> >>
> >>
> >> U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM
> > Yep, so you probably need to disable the EMMC because it's loading it
> > from the EMMC for some reason.
> >
> > If it loads to Fedora you can also run "dd if=/dev/zero
> > of=/dev/mmcblkX bs=1M count=10" (update the mmcblkX to the right one)
> > to zero out the beginning of the EMMC if you don't care about the
> > contents of it.
> > _______________________________________________
> > arm mailing list -- arm(a)lists.fedoraproject.org
> > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/[e-mail]
> > Do not reply to spam on the list, report it: 
> > https://pagure.io/fedora-infrastructure
>
>  After "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=10" I want to boot 
>  with Fedora-Everything-netinst-aarch64-34-1.2.iso
>
>  How to boot from USB?
>
>  Message
>
>  U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
>  Channel 0: LPDDR4, 50MHz
>  BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  Channel 1: LPDDR4, 50MHz
>  BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  256B stride
>  lpddr4_set_rate: change freq to 400000000 mhz 0, 1
>  lpddr4_set_rate: change freq to 800000000 mhz 1, 0
>  Trying to boot from BOOTROM
>  Returning to boot ROM...
>
>  U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
>  Trying to boot from MMC2
>  mmc_load_image_raw_sector: mmc block read error
>  Trying to boot from SPI
>
>
>  U-Boot 2021.04 (Apr 21 2021 - 00:00:00 +0000)
>
>  SoC: Rockchip rk3399
>  Reset cause: RST
>  Model: Pine64 Pinebook Pro
>  DRAM:  3.9 GiB
>  PMIC:  RK808
>  MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
>  Loading Environment from SPIFlash... SF: Detected gd25q128 with page 
>  size 256 Bytes, erase size 4 KiB, total 16 MiB
>  *** Warning - bad CRC, using default environment
>
>  ---cut---
>
>  Device 0: Vendor: Verbatim Rev: PMAP Prod: STORE N GO
>              Type: Removable Hard Disk
>              Capacity: 14808.0 MB = 14.4 GB (30326784 x 512)
>  ... is now current device
>  Scanning usb 0:1...
>  ---cut---
>
>  Usage:
>  dhcp [loadAddress] [[hostIPaddr:]bootfilename]
>  ## Executing script at 00500000
>  Wrong image format for "source" command
>  SCRIPT FAILED: continuing...
>  =>
>  
Hello

I didn't manage to boot Fedora-Everything-netinst-aarch64-34-1.2.iso 
from USB, so I switched back to former Fedora Installation with modified 
kernel.

I will try it later.

Andreas

[Dan Horák]

On Wed, 5 May 2021 17:51:33 +0200
Andreas Reschke <arm_ml(a)rirasoft.de&gt; wrote:

>  
>  Am 04.05.21 um 16:58 schrieb Peter Robinson:
>  >>> U-Boot 2021.04 (Apr 28 2021 - 00:00:00)
>  >> U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
>  >> Channel 0: LPDDR4, 50MHz
>  >> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  >> Channel 1: LPDDR4, 50MHz
>  >> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  >> 256B stride
>  >> lpddr4_set_rate: change freq to 400000000 mhz 0, 1
>  >> lpddr4_set_rate: change freq to 800000000 mhz 1, 0
>  >> Trying to boot from BOOTROM
>  >> Returning to boot ROM...
>  >>
>  >> U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
>  >> Trying to boot from MMC2
>  >>
>  >>
>  >> U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM
>  > Yep, so you probably need to disable the EMMC because it's loading it
>  > from the EMMC for some reason.
>  >
>  > If it loads to Fedora you can also run "dd if=/dev/zero
>  > of=/dev/mmcblkX bs=1M count=10" (update the mmcblkX to the right one)
>  > to zero out the beginning of the EMMC if you don't care about the
>  > contents of it.
>  > _______________________________________________
>  > arm mailing list -- arm(a)lists.fedoraproject.org
>  > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  > Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>  
>  After "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=10" I want to boot 
>  with Fedora-Everything-netinst-aarch64-34-1.2.iso
>  
>  How to boot from USB? 
interrupt the autoboot countdown in u-boot and enter "run bootcmd_usb0"

the installer probably starts OK (responds to pings), but the screen is
off


		Dan

[Andreas Reschke]

Hello to all,

I want to flash it again but it didn't work:

U-Boot 2021.04 (Apr 21 2021 - 00:00:00 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page 
size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Pine64 Pinebook Pro
Net:   No ethernet found.
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 2 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 3 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
        scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
=> ls mmc 1:1
    167509   idbloader.img
    335872   idbloader.spi
    975536   u-boot.itb
   9331376   u-boot-rockchip.bin

4 file(s), 0 dir(s)

=> sf probe
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 
16 MiB
=> load mmc 1:1 ${fdt_addr_r} idbloader.spi
335872 bytes read in 39 ms (8.2 MiB/s)
=> sf update ${fdt_addr_r} 0 ${filesize}
device 0 offset 0x0, size 0x52000
0 bytes written, 335872 bytes skipped in 0.279s, speed 1228331 B/s
=> load mmc 1:1 ${fdt_addr_r} u-boot.itb
975536 bytes read in 106 ms (8.8 MiB/s)
=> sf update ${fdt_addr_r} 60000 ${filesize}
device 0 offset 0x60000, size 0xee2b0
0 bytes written, 975536 bytes skipped in 0.814s, speed 1225704 B/s
=>

How to fixit?

Thanks Andreas

[Andreas Reschke]

Am 06.05.21 um 21:47 schrieb Dan Horák:
>  On Wed, 5 May 2021 17:51:33 +0200
>  Andreas Reschke <arm_ml(a)rirasoft.de&gt; wrote:
>
> > Am 04.05.21 um 16:58 schrieb Peter Robinson:
> >>>> U-Boot 2021.04 (Apr 28 2021 - 00:00:00)
> >>> U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
> >>> Channel 0: LPDDR4, 50MHz
> >>> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> >>> Channel 1: LPDDR4, 50MHz
> >>> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> >>> 256B stride
> >>> lpddr4_set_rate: change freq to 400000000 mhz 0, 1
> >>> lpddr4_set_rate: change freq to 800000000 mhz 1, 0
> >>> Trying to boot from BOOTROM
> >>> Returning to boot ROM...
> >>>
> >>> U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
> >>> Trying to boot from MMC2
> >>>
> >>>
> >>> U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM
> >> Yep, so you probably need to disable the EMMC because it's loading it
> >> from the EMMC for some reason.
> >>
> >> If it loads to Fedora you can also run "dd if=/dev/zero
> >> of=/dev/mmcblkX bs=1M count=10" (update the mmcblkX to the right one)
> >> to zero out the beginning of the EMMC if you don't care about the
> >> contents of it.
> >> _______________________________________________
> >> arm mailing list -- arm(a)lists.fedoraproject.org
> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> >> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> >> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
> > After "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=10" I want to boot
> > with Fedora-Everything-netinst-aarch64-34-1.2.iso
> >
> > How to boot from USB?
>  interrupt the autoboot countdown in u-boot and enter "run bootcmd_usb0"
>
>  the installer probably starts OK (responds to pings), but the screen is
>  off
>
>
>  		Dan
>  _______________________________________________
>  arm mailing list -- arm(a)lists.fedoraproject.org
>  To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Hello Dan,

you're right, after  "run bootcmd_usb0" Fedora boots from USB. I've edit

the boot cmdline and removed "rhgb quite console=tty0".

So i run the installations process but the screen is off. Only network 
access and serial console is working.

Andreas

[Alessio]

On Tue, 2021-05-04 at 16:44 +0200, Andreas Reschke wrote:
>  
>  Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  > For those that are interested here is the write up for getting
>  > Pinebook Pro running Fedora:
>  > 
>  > https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>  >  
After using the internal switch to turn off the eMMC temporarily, I was
able to follow "Writing the firmware to flash". Then I issued "mmc
erase 0 1000; boot", otherwise the preloaded Manjaro OS was still
booting despite the mSD card was inserted). Then I managed to boot
Fedora Workstation from the mSD card. 
I was unable to boot Workstation Live from the USB (the screen stays
black).
Then, (unorthodoxly) using dd, I copied the mSD content to eMMC (I
suppose). Removed the mSD card, now Fedora boots from eMMC (I suppose).
I installed the RPM containing the WiFi firmware.
The only weird thing is: reboot doesn't work. The screen become gray
with some gray vertical lines. And in the background, even if blurred,
I can still see the GNOME top bar.

Thanks.
A.

[Jonathan Rioux]

Thanks for the information.
I just got my pbp and it has manjaro on it. Fully updated, but I feel more at home with
Fedora :)
First time out of the x86 playground, so U-boot is unfamiliar land.

I have a few questions :
1) Is it mandatory to upgrade U-boot, on newer pbp ?
2) Can I know what version it has without serial port ? Missing config file for
fw_printenv.
3) Can I write U-boot from manjaro ?
4) Is the pcie support is not already enabled in manjaro ? Could you just use it's
kernel config like https://github.com/bengtfredh/pinebook-pro-fedora-installer. 

Thanks, just got my pbp yesterday and didn't have lots of time to tinker with it yet.

[Peter Robinson]

>  I have a few questions :
>  1) Is it mandatory to upgrade U-boot, on newer pbp ? 
Yes, if you want assistance, I have no idea what manjaro uses, I do
know it's on the EMMC.

>  2) Can I know what version it has without serial port ? Missing
> config file for fw_printenv. 
The Fedora one? It's 2021.04 with some fixes. The Fedora one outputs
all the version information to the screen. No clue on manjaro one,
I've never used it.

>  3) Can I write U-boot from manjaro ? 
No idea, I've never tested it.

>  4) Is the pcie support is not already enabled in manjaro ? Could you
> just use it's kernel config like
> https://github.com/bengtfredh/pinebook-pro-fedora-installer. 
See the bug report linked in my blog post, in short "No, it's not that
straight forward"

[Matthew Miller]

On Tue, May 04, 2021 at 11:11:31PM +0100, Peter Robinson wrote:
>  The Fedora one? It's 2021.04 with some fixes. The Fedora one
> outputs
>  all the version information to the screen. No clue on manjaro one,
>  I've never used it. 
As it happens, I just got mine. When you hit the power button, the tiny
green light comes on and there is no apparent activity for about fifteen
seconds. Just long enough for you to think "huh, is this gonna work", and
then the boot spinner comes up for about two seconds, and then you're at a
login screen.

Hitting keys (ESC or anything else) during that fifteen-second silence does not
seem to do anything.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Jonathan Rioux]

@PeterRobinson
By querying pacman, I get that package uboot-pinebookpro-bsp 1.5-8 is installed on my new
machine.
There seems to be a 2021.4-1 package available also.

Ok, for nvme and deep sleep; it seems it needs bsp patches for uboot to work.
https://forum.pine64.org/showthread.php?tid=10264
But on the same site, it say we can put the uboot on the eMMC, should be less risks to
debug than flashing on the SPI.

@MatthewMiller
Well there's work to get graphical uboot here :
https://github.com/samueldr/wip-pinebook-pro/pull/13
Is that what you're looking for ?

[Peter Robinson]

On Wed, May 5, 2021 at 2:11 PM Jonathan Rioux <jonathanrioux(a)gmail.com&gt; wrote:
>  @PeterRobinson
>  By querying pacman, I get that package uboot-pinebookpro-bsp 1.5-8 is installed on my new
> machine.
>  There seems to be a 2021.4-1 package available also.
>
>  Ok, for nvme and deep sleep; it seems it needs bsp patches for uboot to work.
> https://forum.pine64.org/showthread.php?tid=10264 
That's based on a post from July 2020 where the upstream PBP was
basic, a lot has changed since then and most of what you reference is
irrelevant

>  But on the same site, it say we can put the uboot on the eMMC, should
> be less risks to debug than flashing on the SPI. 
What do you base the risk on? There's no risk of permanently bricking
the PBP with SPI flash, there's a recovery button that allows you to
recover over USB-C, as the person that submitted the upstream support
for the PBP believe me I've tried that functionality a lot!

>  @MatthewMiller
>  Well there's work to get graphical uboot here :
> https://github.com/samueldr/wip-pinebook-pro/pull/13 
We already have most of the patches to enable display graphics

[Peter Robinson]

On Wed, May 5, 2021 at 2:21 PM Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
>  On Wed, May 5, 2021 at 2:11 PM Jonathan Rioux <jonathanrioux(a)gmail.com&gt; wrote:
>  >
>  > @PeterRobinson
>  > By querying pacman, I get that package uboot-pinebookpro-bsp 1.5-8 is installed on
> my new machine.
>  > There seems to be a 2021.4-1 package available also.
>  >
>  > Ok, for nvme and deep sleep; it seems it needs bsp patches for uboot to work.
> https://forum.pine64.org/showthread.php?tid=10264
>
>  That's based on a post from July 2020 where the upstream PBP was
>  basic, a lot has changed since then and most of what you reference is
>  irrelevant 
In fact looking at the patch set we have a much newer more advanced
U-Boot, and most of the patches they reference were in fact my
patches.

>  > But on the same site, it say we can put the uboot on the eMMC,
> should be less risks to debug than flashing on the SPI.
>
>  What do you base the risk on? There's no risk of permanently bricking
>  the PBP with SPI flash, there's a recovery button that allows you to
>  recover over USB-C, as the person that submitted the upstream support
>  for the PBP believe me I've tried that functionality a lot!
>
>  > @MatthewMiller
>  > Well there's work to get graphical uboot here :
> https://github.com/samueldr/wip-pinebook-pro/pull/13
>
>  We already have most of the patches to enable display graphics 
The only thing we don't already have is a logo, and there's reasons
why I've not done that yet. I'm working on proper BGRT shiny boot.

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 05 May 2021 at 15:21, Peter Robinson wrote:
>  On Wed, May 5, 2021 at 2:11 PM Jonathan Rioux
> <jonathanrioux(a)gmail.com&gt; wrote:
>  >
>  > @PeterRobinson
>  > By querying pacman, I get that package uboot-pinebookpro-bsp 1.5-8 is installed on
> my new machine.
>  > There seems to be a 2021.4-1 package available also.
>  >
>  > Ok, for nvme and deep sleep; it seems it needs bsp patches for uboot to work.
> https://forum.pine64.org/showthread.php?tid=10264
>  
>  That's based on a post from July 2020 where the upstream PBP was
>  basic, a lot has changed since then and most of what you reference is
>  irrelevant
>  
>  > But on the same site, it say we can put the uboot on the eMMC, should be less risks
> to debug than flashing on the SPI.
>  
>  What do you base the risk on? There's no risk of permanently bricking
>  the PBP with SPI flash, there's a recovery button that allows you to
>  recover over USB-C, as the person that submitted the upstream support
>  for the PBP believe me I've tried that functionality a lot! 
The recovery button doesn't seem to work. I had to enter the maskrom
mode by shorting VSS and CLK pins on the SPI as documented here:
https://wiki.pine64.org/wiki/Pinebook_Pro_SPI#Maskrom_mode_.28reliable_me...

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

[Matthew Miller]

On Wed, May 05, 2021 at 01:11:32PM -0000, Jonathan Rioux wrote:
>  @MatthewMiller
>  Well there's work to get graphical uboot here :
> https://github.com/samueldr/wip-pinebook-pro/pull/13
>  Is that what you're looking for ? 
I'm just reporting what mine does out of the box.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Dan Horák]

On Tue, 4 May 2021 12:39:27 +0100
Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:

>  For those that are interested here is the write up for getting
>  Pinebook Pro running Fedora:
>  
>  https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>  
>  Feel free to reply on this thread for questions. 
first thanks for the instructions, I could finally put my PBP to use. I
have couple updates someone might find useful

- soft-disable of the eMMC could be done also from u-boot with
"mmc erase 0 1000; boot"

- when I have USB ethernet adapter (bought together with PBP,
ID 0bda: 8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet
Adapter) plugged into any of the 2 USB ports, then u-boot fails to boot
the OS and instead prints "Rx: failed to receive ..." forever


		Dan

[Michal Toman]

Hey Peter,

thanks for finally making my Pinebook Pro usable.

Following your instructions I was able to boot Fedora (XFCE) from an SD
card, then repeated the procedure to burn it onto the internal eMMC and
it works great.

I was starting with a stock u-boot, used the serial console to write the
SPI flash to be sure, but I have had video output throughout the process
so it should be doable even without serial.

I have been using the laptop as my primary workstation for two days
which made me test almost every feature, here I am sharing my
observations, many of which you already mention in the blog post:
- The USB2 port on the right side works fine
- Anything plugged into the USB3 port on the left side has to be
re-plugged after reboot.
- USB-C charging does not work. I tried 4 random chargers I have had
around - 2 of them seem to do absolutely nothing when plugged in, 2 of
them have the device switch between charging and battery every ~10 seconds.
- USB-C display output does not work.
- USB-C works as a standard USB port, I have a hub with Ethernet plugged
in and it works fine. The hub must not be powered though, otherwise it
would behave like a charger.
- Onboard WiFi and BT do not work (obviously because of the firmware).
Even with the temporary firmware the WiFi is quite unstable and
sometimes causes the whole machine to freeze needing a hard reboot.
Removed the firmware, switched to a USB dongle and the issue went away.
- Sound does not play from the speakers even though pulseaudio thinks it
is. I have not tested the headphone jack as I am using it for serial
console.
- PCI Express does not work.
- The kernel framebuffer does not show kernel logs, but some pixels are
flashing at the very top of the screen after u-boot goes away. The first
actual video output after u-boot is Plymouth or lightDM depening on
whether I have rhgb or not.
- The webcam somewhat works - it shows a picture but it is pretty laggy
and definitely not 1080p.

All in all this is a pretty decent experience and for me personally it
is already usable as it is. Great job!

Michal

On 5/4/21 1:39 PM, Peter Robinson wrote:
> For those that are interested here is the write up for getting
> Pinebook Pro running Fedora:
> 
> https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
> 
> Feel free to reply on this thread for questions.
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>

[Matthew Miller]

On Fri, May 07, 2021 at 07:01:52AM +0200, Michal Toman wrote:
>  - USB-C charging does not work. I tried 4 random chargers I have had
>  around - 2 of them seem to do absolutely nothing when plugged in, 2 of
>  them have the device switch between charging and battery every ~10 seconds. 
Hmmm, that's interesting. I haven't reinstalled mine yet, but it's plugged
in via USB-C (with a spare Lenovo power supply) right now. Did yours work
with USB-C power before reinstalling?

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Peter Robinson]

On Fri, May 7, 2021 at 2:17 PM Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  On Fri, May 07, 2021 at 07:01:52AM +0200, Michal Toman wrote:
>  > - USB-C charging does not work. I tried 4 random chargers I have had
>  > around - 2 of them seem to do absolutely nothing when plugged in, 2 of
>  > them have the device switch between charging and battery every ~10 seconds.
>
>  Hmmm, that's interesting. I haven't reinstalled mine yet, but it's plugged
>  in via USB-C (with a spare Lenovo power supply) right now. Did yours work
>  with USB-C power before reinstalling? 
There's some issue, the install on it has a bunch of non upstream
patches, when I was playing with it a few weeks back and monitoring
with upower it was detecting USB-C PD but it seemed to constantly
bounce. As per my blog post it's on the to look at list but I figured
it was better to get the details out so people could play rather than
waiting until it was perfect.....

[Michal Toman]

So I was playing with this a bit more and was able to find some chargers
that do work.

The key is indeed Power Delivery, the chargers that use it seem to just
infinitely offer configurations to the PBP but the two will never fully
agree. This generates cca 10 upower events per second and you can see
upowerd to jump to cca 40% CPU consumption while the charger is plugged
in. The switching between battery and charging every ~10 seconds as I
described it seems to be just some presentation-level rate limiting, it
actually happens more often.

I have specifically tried with my ThinkPad's charger (it was working
fine with it before reinstalling) and the result is the same.

The ones that work include:
- The original RPi4 PSU
- Two unbranded phone chargers from a local store
- A powerbank when connected using a USB-A to USB-C cable. When I
connect the same powerbank using a USB-C to USB-C cable, PD kicks in and
it does not work.

This makes me think that any charger that uses a USB-A to USB-C cable
will probably be OK as well.

A good indicator is the red charging LED on the left side - for me it
will not flash with a PD charger connected while it will with the barrel
jack or any of the chargers mentioned above.

On 5/7/21 6:03 PM, Peter Robinson wrote:
> On Fri, May 7, 2021 at 2:17 PM Matthew Miller <mattdm(a)fedoraproject.org&gt;
wrote:
>>
>> On Fri, May 07, 2021 at 07:01:52AM +0200, Michal Toman wrote:
>>> - USB-C charging does not work. I tried 4 random chargers I have had
>>> around - 2 of them seem to do absolutely nothing when plugged in, 2 of
>>> them have the device switch between charging and battery every ~10 seconds.
>>
>> Hmmm, that's interesting. I haven't reinstalled mine yet, but it's
plugged
>> in via USB-C (with a spare Lenovo power supply) right now. Did yours work
>> with USB-C power before reinstalling?
> 
> There's some issue, the install on it has a bunch of non upstream
> patches, when I was playing with it a few weeks back and monitoring
> with upower it was detecting USB-C PD but it seemed to constantly
> bounce. As per my blog post it's on the to look at list but I figured
> it was better to get the details out so people could play rather than
> waiting until it was perfect.....
>

[Andreas Reschke]

Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  For those that are interested here is the write up for getting
>  Pinebook Pro running Fedora:
>
>  https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>
>  Feel free to reply on this thread for questions.
>  _______________________________________________
>  arm mailing list -- arm(a)lists.fedoraproject.org
>  To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Please help me to boot Fedora, it didn't work for me:

U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
Trying to boot from MMC2


U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Pine64 Pinebook Pro
Net:   No ethernet found.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Hit any key to stop autoboot:  0
=> run bootcmd_usb0
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
USB is stopped. Please issue 'usb start' first.
=> usb start
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
=>

Thanks

Andreas

[Dominik 'Rathann' Mierzejewski]

On Saturday, 08 May 2021 at 10:50, Andreas Reschke wrote:
>  Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  > For those that are interested here is the write up for getting
>  > Pinebook Pro running Fedora:
>  > 
>  > https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>  > 
>  
>  Please help me to boot Fedora, it didn't work for me:
>  
>  U-Boot TPL 2021.04 (Apr 21 2021 - 00:00:00)
>  Channel 0: LPDDR4, 50MHz
>  BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  Channel 1: LPDDR4, 50MHz
>  BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
>  256B stride
>  lpddr4_set_rate: change freq to 400000000 mhz 0, 1
>  lpddr4_set_rate: change freq to 800000000 mhz 1, 0
>  Trying to boot from BOOTROM
>  Returning to boot ROM...
>  
>  U-Boot SPL 2021.04 (Apr 21 2021 - 00:00:00 +0000)
>  Trying to boot from MMC2
>  
>  
>  U-Boot 2020.10-1 (Oct 14 2020 - 10:43:46 +0000) Manjaro ARM
>  
>  SoC: Rockchip rk3399
>  Reset cause: POR
>  Model: Pine64 Pinebook Pro
>  DRAM:  3.9 GiB
>  PMIC:  RK808
>  MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
>  Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
>  *** Warning - spi_flash_probe_bus_cs() failed, using default environment
>  
>  In:    serial
>  Out:   serial
>  Err:   serial
>  Model: Pine64 Pinebook Pro
>  Net:   No ethernet found.
>  starting USB...
>  Bus usb@fe380000: failed to get usb phy
>  Port not available.
>  Bus usb@fe3a0000: failed to get usb phy
>  Port not available.
>  Bus usb@fe3c0000: failed to get usb phy
>  Port not available.
>  Bus usb@fe3e0000: failed to get usb phy
>  Port not available.
>  Bus dwc3: Failed to get PHY0 for dwc3
>  Port not available.
>  Bus dwc3: Failed to get PHY0 for dwc3
>  Port not available.
>  Hit any key to stop autoboot:  0
>  => run bootcmd_usb0 
Instead of booting from USB, flash the u-boot image to SPI first, like
the blog post says and reset. You should be able to boot from USB with
no issues after that.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

[Andreas Reschke]

Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  For those that are interested here is the write up for getting
>  Pinebook Pro running Fedora:
>
>  https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>
>  Feel free to reply on this thread for questions.
>  _______________________________________________
>  arm mailing list -- arm(a)lists.fedoraproject.org
>  To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Hello together,

I've managed to get Fedora on my Pinebook Pro.
Here are my steps:
- flash firmware as described by Peter
- reboot
- arm-image-installer --media=/dev/sda --resizefs --target=none 
--image=Fedora-KDE-34-1.2.aarch64.raw.xz
on 2 USB-Sticks
- reboot
- interrupt the autoboot countdown in u-boot and enter "run 
bootcmd_usb0" (thanks to Dan Horak)
- boot and configure first USB-Stick
- reboot
- boot and configure second USB-Stick
- with second USB online copy first USB-Stick to EMMC
dd if=/dev/sda of=/dev/mmcblk2 bs=4M status=progress
- reboot without any USB-Stick from EMMC
- resize BTRFS Filesystem
- install firmware for WIFI as described
- customize installation

Whats missing:
- working with installed NVME-disc (PCIe-support needs to be fixed)
- Bluetooth isn't working
- Sound (internal speaker + headphone) isn't working
- Subjective perception : KDE is working faster with X11 than Wayland


Thanks to all people involved in getting Fedora on Pinebook Pro, special 
to Peter Robinson


Greetings
Andreas

[Dominik 'Rathann' Mierzejewski]

On Tuesday, 11 May 2021 at 17:32, Andreas Reschke wrote:
>  Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  > For those that are interested here is the write up for getting
>  > Pinebook Pro running Fedora:
>  > 
>  > https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>  > 
>  > Feel free to reply on this thread for questions. 
>  I've managed to get Fedora on my Pinebook Pro. 
Congratulations!

[...]
>  Whats missing:
>  - working with installed NVME-disc (PCIe-support needs to be fixed)
>  - Bluetooth isn't working 
You need another firmware blob (BCM4345C5.hcd) e.g. from here:
https://gitlab.manjaro.org/manjaro-arm/packages/community/ap6256-firmware
It works for me with my BT headset just fine.

>  - Sound (internal speaker + headphone) isn't working 
Check alsamixer -c0 settings. I had to unmute the followin:
Left Headphone Mixer Left DAC
Right Headphone Mixer Right DAC
before getting any sound.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

[Andreas Reschke]

Am 12.05.21 um 12:07 schrieb Dominik 'Rathann' Mierzejewski:
>  On Tuesday, 11 May 2021 at 17:32, Andreas Reschke wrote:
> > Am 04.05.21 um 13:39 schrieb Peter Robinson:
> >> For those that are interested here is the write up for getting
> >> Pinebook Pro running Fedora:
> >>
> >> https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
> >>
> >> Feel free to reply on this thread for questions.
> > I've managed to get Fedora on my Pinebook Pro.
>  Congratulations!
>
>  [...]
> > Whats missing:
> > - working with installed NVME-disc (PCIe-support needs to be fixed)
> > - Bluetooth isn't working
>  You need another firmware blob (BCM4345C5.hcd) e.g. from here:
>  https://gitlab.manjaro.org/manjaro-arm/packages/community/ap6256-firmware
>  It works for me with my BT headset just fine.
>
> > - Sound (internal speaker + headphone) isn't working
>  Check alsamixer -c0 settings. I had to unmute the followin:
>  Left Headphone Mixer Left DAC
>  Right Headphone Mixer Right DAC
>  before getting any sound.
>
>  Regards,
>  Dominik 

Hello Dominik,

thanks for your support. I've downloaded the firmware blob. It's looks 
better but it didn't work yet.

root@fedora ~]# dmesg | grep Bluetooth
[   24.884209] Bluetooth: Core ver 2.22
[   24.884374] Bluetooth: HCI device and connection manager initialized
[   24.884394] Bluetooth: HCI socket layer initialized
[   24.884404] Bluetooth: L2CAP socket layer initialized
[   24.884432] Bluetooth: SCO socket layer initialized
[   24.987000] Bluetooth: HCI UART driver ver 2.3
[   24.987027] Bluetooth: HCI UART protocol H4 registered
[   24.987031] Bluetooth: HCI UART protocol BCSP registered
[   24.987126] Bluetooth: HCI UART protocol LL registered
[   24.987131] Bluetooth: HCI UART protocol ATH3K registered
[   24.987173] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   24.987576] Bluetooth: HCI UART protocol Intel registered
[   24.987938] Bluetooth: HCI UART protocol Broadcom registered
[   24.987989] Bluetooth: HCI UART protocol QCA registered
[   24.987995] Bluetooth: HCI UART protocol AG6XX registered
[   24.988140] Bluetooth: HCI UART protocol Marvell registered
[   25.372023] Bluetooth: hci1: BCM: chip id 130
[   25.372443] Bluetooth: hci1: BCM: features 0x0f
[   25.413854] Bluetooth: hci1: BCM4345C5
[   25.413890] Bluetooth: hci1: BCM4345C5 (003.006.006) build 0000
[   25.416193] Bluetooth: hci1: BCM4345C5 'brcm/BCM4345C5.hcd' Patch
[   27.511662] Bluetooth: hci1: command 0x213c tx timeout
[   28.487823] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   28.487853] Bluetooth: BNEP filters: protocol multicast
[   28.487875] Bluetooth: BNEP socket layer initialized
[   35.671772] Bluetooth: hci1: BCM: Patch command 213c failed (-110)
[   35.671807] Bluetooth: hci1: BCM: Patch failed (-110)
[   37.751753] Bluetooth: hci1: command 0xfc18 tx timeout
[   45.912069] Bluetooth: hci1: BCM: failed to write update baudrate (-110)
[   47.992080] Bluetooth: hci1: command 0x0c03 tx timeout
[   56.151804] Bluetooth: hci1: BCM: Reset failed (-110)
[root@fedora ~]#
[root@fedora ~]# bluetoothctl list
[root@fedora ~]# bluetoothctl devices
No default controller available
[root@fedora ~]# bluetoothctl scan on
No default controller available
[root@fedora ~]#

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 12 May 2021 at 13:24, Andreas Reschke wrote:
>  Am 12.05.21 um 12:07 schrieb Dominik 'Rathann' Mierzejewski:
>  > On Tuesday, 11 May 2021 at 17:32, Andreas Reschke wrote:
>  > > Am 04.05.21 um 13:39 schrieb Peter Robinson:
>  > > > For those that are interested here is the write up for getting
>  > > > Pinebook Pro running Fedora:
>  > > > 
>  > > > https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
>  > > > 
>  > > > Feel free to reply on this thread for questions.
>  > > I've managed to get Fedora on my Pinebook Pro.
>  > Congratulations!
>  > 
>  > [...]
>  > > Whats missing:
>  > > - working with installed NVME-disc (PCIe-support needs to be fixed)
>  > > - Bluetooth isn't working
>  > You need another firmware blob (BCM4345C5.hcd) e.g. from here:
>  > https://gitlab.manjaro.org/manjaro-arm/packages/community/ap6256-firmware
>  > It works for me with my BT headset just fine.
>  > 
>  > > - Sound (internal speaker + headphone) isn't working
>  > Check alsamixer -c0 settings. I had to unmute the followin:
>  > Left Headphone Mixer Left DAC
>  > Right Headphone Mixer Right DAC
>  > before getting any sound. 
[...]
>  thanks for your support. I've downloaded the firmware blob.
> It's looks
>  better but it didn't work yet. 
Is your bluetooth enabled at all? What does `rfkill' say?

Also, try the blob from armbian:
https://github.com/armbian/firmware/raw/master/BCM4345C5.hcd

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

[Andreas Reschke]

Am 12.05.21 um 13:28 schrieb Dominik 'Rathann' Mierzejewski:
>  On Wednesday, 12 May 2021 at 13:24, Andreas Reschke wrote:
> > Am 12.05.21 um 12:07 schrieb Dominik 'Rathann' Mierzejewski:
> >> On Tuesday, 11 May 2021 at 17:32, Andreas Reschke wrote:
> >>> Am 04.05.21 um 13:39 schrieb Peter Robinson:
> >>>> For those that are interested here is the write up for getting
> >>>> Pinebook Pro running Fedora:
> >>>>
> >>>> https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
> >>>>
> >>>> Feel free to reply on this thread for questions.
> >>> I've managed to get Fedora on my Pinebook Pro.
> >> Congratulations!
> >>
> >> [...]
> >>> Whats missing:
> >>> - working with installed NVME-disc (PCIe-support needs to be fixed)
> >>> - Bluetooth isn't working
> >> You need another firmware blob (BCM4345C5.hcd) e.g. from here:
> >> https://gitlab.manjaro.org/manjaro-arm/packages/community/ap6256-firmware
> >> It works for me with my BT headset just fine.
> >>
> >>> - Sound (internal speaker + headphone) isn't working
> >> Check alsamixer -c0 settings. I had to unmute the followin:
> >> Left Headphone Mixer Left DAC
> >> Right Headphone Mixer Right DAC
> >> before getting any sound.
>  [...]
> > thanks for your support. I've downloaded the firmware blob. It's looks
> > better but it didn't work yet.
>  Is your bluetooth enabled at all? What does `rfkill' say?
>
>  Also, try the blob from armbian:
>  https://github.com/armbian/firmware/raw/master/BCM4345C5.hcd
>
>  Regards,
>  Dominik 
Hi,

other firmware didn't help.

[root@fedora ~]# bluetoothctl list
[root@fedora ~]# bluetoothctl devices
No default controller available
[root@fedora ~]# rfkill
ID TYPE      DEVICE      SOFT      HARD
  0 wlan      phy0   unblocked unblocked
  1 bluetooth hci0   unblocked unblocked
  2 bluetooth hci1   unblocked unblocked
[root@fedora ~]#

Bluetoth seems to be available, but didn't work.

Andreas

[Ting-Wei Wan]

Thanks for your wonderful instruction, Peter. Flashing U-Boot on SPI works at the first
try.
I got my pinebook pro yesterday and is now running fedora on emmc. So far, it's
working as you described in your write-up. 

There is one thing that caught me though. That is this pinebook pro with U-Boot on SPI
does not boot iso images from USB or SD card.
Initially I wanted to do a installation from Workstation LiveCD, but after the GRUB menu,
the screen display remains dark and hanged indefinitely while the power LED lights up
green. The only way I can boot fedora is to use arm-image-installer to write raw.xz files
to USB or SD card or emmc, all of them boots.

I guess there may be some issues between the EFI and the U-Boot that causes the iso files
does not boot?

Thanks again for your write-up and hard work.

Cheers.

[Dominik 'Rathann' Mierzejewski]

On Tuesday, 01 June 2021 at 09:30, Ting-Wei Wan wrote:
[...]
>  There is one thing that caught me though. That is this pinebook pro
>  with U-Boot on SPI does not boot iso images from USB or SD card.
>  Initially I wanted to do a installation from Workstation LiveCD, but
>  after the GRUB menu, the screen display remains dark and hanged
>  indefinitely while the power LED lights up green. 
It's not hanging, but the display goes to the second framebuffer which
is not mapped to the console. Adding fbcon=map:1 to the kernel command
line works around the issue. Kernels 5.12.5 and later contain the fix
for this.

You can also access the ISO installer via VNC.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

[Ting-Wei Wan]

Thanks for your explanation. I got so much more to learn and try as a novice.