Any luck using Berryboot to install Patchbox-os on p4?

Patchbox OS
1

I’ve been having a terrible time. Because of the particular case I’m using, I don’t have easy access to the SD card. Hence, I would really like to run Patchbox on a multi boot card. I dabbled briefly with Noobs, but would prefer to use Berryboot for it’s greater flexibility. Neither boot manager has allowed a successful install of Patchbox to date, however. Im inclined to think the problem is in how the 2nd partition filetype is not being recognized in the image file.

If no one has a eureka reply (I’m hoping I just missed the thread or FAQ explaining this), I’ll go into greater details of what I’ve tried so far.

Thanks!

2

Hi, I haven’t used Berryboot myself, but the Patchbox OS is based on the same image generator as Rasbpian’s images are, so I’d expect the image to be compatible.

Did you do the steps described here: https://www.berryterminal.com/doku.php/berryboot/adding_custom_distributions to convert the image to the right format for Berryboot? Did it succeed?

3

Hi Giedrius,
Thanks for getting back to me. Yes, I tried to implement the steps outlined in the link you mentioned. The kpartx command fails, which has lead to other pages addressing THAT issue and other attempts to work around, all of which failed in their own ways. I’ve apt-get install’d kpartx, squashfs, and various filetypes including ext4. In this process, I’ve come to find a few things not mentioned on the link you provided:
Bootberry expects an image file that has been compressed with squashfs, The Patchbox image is not squashed and so far, that is where I’m hung up. It seems I can not identify the filetype of the second partition of the Patchbox image as ext4 and even if I assume ext4, the resulting distribution will not run. Bootberry will recognize the squashed image file and install it to it’s own partition, but then the system crashes when I try to boot that partition via Bootberry. I am assuming a corrupted image, but I’m lost at that point.
I also made an SD that I used the dd command to place the Patchbox image onto it. Again, Berryboot recognized the image and added/copied it to the the Pi, but it failed to boot.
It’s been a long time since I’ve dug into linux, so I’m practically a noob, I’m sure I’ve missed something obvious to everyone else here! My next steps would be to swap the “main” SD card with one that I’ve created a distribution as per the Blokas tutorials. If I get that up and running, swap cards again and see if I can get Berryboot to somehow copy or back it up to the “main” SD. Ultimately, I want a multiboot system so that I don’t have to swap cards.
Again, any thoughts or suggestions would be greatly appreciated.

4

So I figured out a solution to use Berryboot to load Patchbox. 1) Unzip the patchbox image and install it to an SD card via Etcher. 2) mksquashfs the rootfs folder. Name the resulting file with a .img extension (e.g. ‘Patchbox.img’). 3) Use this squashed file as your new image file when you tell Berryboot to add a new OS via a USB stick.

I successfully added Patchbox and ran through the configurations. I’d love to say everything is working fine, but I’m now having problems with Patchbox loading the desktop. However, I believe this to be configuration errors on my part and beyond the issue of loading PB via Berryboot so at least this problem is solved.

1 Like
5

What do you mean by loading the desktop? You want it to start into console only? You may change it in patchbox utility (you may have to run update first)

6

Hi Giedrius (and all) - Sorry for the long delayed reply. Life tends to redirect me for large amounts of time. As to my earlier statement where I mentioned the desktop, I should have said, “run startx”. But I have had several problems and some success at getting my configuration up and running with Berryboot and I’ll come back to the startx issue in a moment with more context.

First off, getting an image of Patchbox loaded via Berryboot: Giedrius was correct with his original suggestion of the steps listed in https://www.berryterminal.com/doku.php/berryboot/adding_custom_distributions . For some reason, as I had mentioned above, I could not get kpartx to work for me to save my life. I won’t go into the massive odyssey that’s taken me on, only to say, I kept looking back at the original solution presented and saying, “that addresses all the problems I’m facing if only I could get it to work!” Then just a few days ago, for grins I tried it again… and it worked flawlessly! I can only assume kpartx or some dependency got an update that fixed my original problem. Regardless, I now have two copies on I can boot from as well as Rasbian on my RPi4. However, the installations have not been flawless and I’m currently trying to trouble shoot the resulting symptoms.

The first error I catch on bootup is something about the EPROM access(?) failing. Looked like some utility and it certainly wasn’t a critical failure. Sorry I can’t be more specific, as it flashes by early and quickly during the boot and I haven’t looked at it in journalctl deeply yet.

Next is dphys-swapfile produces an error on boot. Subsequent install get-update operations all mention an error trying to use dphys-swapfile, though the failure seems non-critical So far, changes to the parameters within dphys-swapfile have not made any change to the problem. Some of my readings suggest this is an inconsequential matter, but it’s one of the few failures I see when Patchbox boots up. Could this be because I’m using Berryboot (or any bootloader like NOOBS)?

Bluetooth. I have been unsuccessful at configuring bluethooth. Using patchbox>Manage Bluetooth>status, I get:

bluetooth_supported=0
bluetooth_service_active_state=active
bluetooth_service_sub_state=running
bluealsa_service_active_state=inactive
bluealsa_service_sub_state=dead
hciuart_service_active_state=inactive
hciuart_service_sub_state=dead

bluetoothctl>list returns empty
bluetoothctl>show and most other commands return, “No default controller available”.

rfkill list all shows
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

I have been able to start and connect to the Pisound WiFi, but can not get beyond that.

Before mentioning my problem with startx,I should go into how the RPi4 is configured, as this not only might shed light with my startx problem, but perhaps the other problems I’ve already mentioned.

The RPi4 has 4Gb, has an OFFICIAL RASPBERRY PI 7" touch sensitive monitor attached in via the ribbon port, is housed in an OFFICIAL RASPBERRY PI enclosure that have been upgraded with a dual-fan, full body heat sink (OFFICIAL RASPBERRY PI?) where I have then added header pins to extent the GPIO so as to allow the attachment of the Pisound card. I was running a wireless keyboard off of a usb port, but switched it out for a straight up usb keyboard to see if that effected the bluetooth problem, which it didn’t. There’s many reasons why I’d like to get this configuration to work, but i’m fully aware this is not typical setup or intent of most successful Pisound installations I’ve seen to date. To further add insult to injury, I am trying to come up the learning curve quickly and know a smattering of information randomly gleaned by running into problems such as this. So any specific information I provide that’s of any use to anyone is probably more luck than skill! Please bear with me.

Needless to say, when I try to run startx, my terminal becomes a blank cursor and is unresponsive to any commands. I have tried plugging a monitor into HDMI 1 and 2, but get nothing there. 1 just has the rainbow screen and 2 remains off. My only option at that point is a power cycle. Startx is not my first priority however, as my goal is to get up and running with the Pisound.

I realize I’m throwing a lot of issues out there that might not be directly related to the original Berryboot question. I think that issue is close to being put to bed with a successful resolution and then move the other issues to other threads as needs be, but again, I look to yours and the hivemind’s guidance in this matter.

Thank You!

7

Hey, could you attach the dmesg log produced after booting up?

I found that Raspberry Pi’s are not good at auto-detecting the display, so it has to be connected before powering on the device.

To recover the unresponsive terminal, you may try clicking Ctrl+C; Ctrl+Z; Ctrl+Alt+F1 (or Ctrl+Alt+F2, etc… up to F7 I think, these commands switch the currently active ‘terminal screen’)

8

Here is a dmesg log from a configuration w/o a monitor attached to an HDMI port. I’ll try to product that next. Also, at least w/o a monitor attached, none of the Ctrl+* commands had any noticeable effect. Perhaps my keyboard mapping might be off, though.

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]

[ 0.000000] Linux version 4.19.75v64 (max@lynx) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #1 SMP PREEMPT Sat Oct 5 03:06:01 CEST 2019

[ 0.000000] Machine model: Raspberry Pi 4 Model B Rev 1.2

[ 0.000000] efi: Getting EFI parameters from FDT:

[ 0.000000] efi: UEFI not found.

[ 0.000000] cma: Reserved 256 MiB at 0x000000001ec00000

[ 0.000000] On node 0 totalpages: 991232

[ 0.000000] DMA32 zone: 3456 pages used for memmap

[ 0.000000] DMA32 zone: 0 pages reserved

[ 0.000000] DMA32 zone: 221184 pages, LIFO batch:63

[ 0.000000] Normal zone: 12032 pages used for memmap

[ 0.000000] Normal zone: 770048 pages, LIFO batch:63

[ 0.000000] random: get_random_bytes called from start_kernel+0xb4/0x480 with crng_init=0

[ 0.000000] percpu: Embedded 24 pages/cpu s57368 r8192 d32744 u98304

[ 0.000000] pcpu-alloc: s57368 r8192 d32744 u98304 alloc=24*4096

[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected PIPT I-cache on CPU0

[ 0.000000] CPU features: enabling workaround for EL2 vector hardening

[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 975744

[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M smsc95xx.macaddr=DC:A6:32:66:C7:02 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 elevator=deadline quiet bootmenutimeout=10 datadev=mmcblk0p2

[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)

[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)

[ 0.000000] software IO TLB: mapped [mem 0x31fff000-0x35fff000] (64MB)

[ 0.000000] Memory: 3549028K/3964928K available (9148K kernel code, 942K rwdata, 2700K rodata, 1024K init, 1122K bss, 153756K reserved, 262144K cma-reserved)

[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

[ 0.000000] ftrace: allocating 29516 entries in 116 pages

[ 0.000000] rcu: Preemptible hierarchical RCU implementation.

[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.

[ 0.000000] Tasks RCU enabled.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4

[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0

[ 0.000000] GIC: Using split EOI/Deactivate mode

[ 0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).

[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns

[ 0.000006] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns

[ 0.000217] Console: colour dummy device 80x25
[ 0.000240] console [tty0] enabled

[ 0.000283] Calibrating delay loop (skipped), value calculated using timer frequency… 108.00 BogoMIPS (lpj=216000)

[ 0.000302] pid_max: default: 32768 minimum: 301
[ 0.000589] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)

[ 0.000640] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)

[ 0.024052] ASID allocator initialised with 32768 entries

[ 0.032048] rcu: Hierarchical SRCU implementation.

[ 0.040552] EFI services will not be available.

[ 0.048105] smp: Bringing up secondary CPUs …

[ 0.080308] Detected PIPT I-cache on CPU1

[ 0.080371] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]

[ 0.112399] Detected PIPT I-cache on CPU2

[ 0.112443] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]

[ 0.144519] Detected PIPT I-cache on CPU3

[ 0.144562] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]

[ 0.144704] smp: Brought up 1 node, 4 CPUs

[ 0.144714] SMP: Total of 4 processors activated.

[ 0.144727] CPU features: detected: 32-bit EL0 Support

[ 0.145394] CPU: All CPU(s) started at EL2

[ 0.145432] alternatives: patching kernel code

[ 0.146533] devtmpfs: initialized

[ 0.154583] Enabled cp15_barrier support

[ 0.154609] Enabled setend support

[ 0.154984] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns

[ 0.155006] futex hash table entries: 1024 (order: 4, 65536 bytes)

[ 0.161671] xor: measuring software checksum speed

[ 0.200638] 8regs : 2536.000 MB/sec

[ 0.240716] 8regs_prefetch: 2181.000 MB/sec

[ 0.280799] 32regs : 2855.000 MB/sec

[ 0.320885] 32regs_prefetch: 2510.000 MB/sec

[ 0.320894] xor: using function: 32regs (2855.000 MB/sec)

[ 0.320912] pinctrl core: initialized pinctrl subsystem

[ 0.321545] DMI not present or invalid.

[ 0.321953] NET: Registered protocol family 16

[ 0.323174] cpuidle: using governor menu

[ 0.323424] vdso: 2 pages (1 code @ (ptrval), 1 data @ (ptrval))

[ 0.323437] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.

[ 0.326010] DMA: preallocated 1024 KiB pool for atomic allocations

[ 0.326098] Serial: AMBA PL011 UART driver
[ 0.329808] bcm2835-mbox fe00b880.mailbox: mailbox enabled

[ 0.425373] raid6: int64x1 gen() 343 MB/s

[ 0.493422] raid6: int64x1 xor() 329 MB/s

[ 0.561561] raid6: int64x2 gen() 476 MB/s

[ 0.629652] raid6: int64x2 xor() 472 MB/s

[ 0.697836] raid6: int64x4 gen() 705 MB/s

[ 0.765930] raid6: int64x4 xor() 523 MB/s

[ 0.834134] raid6: int64x8 gen() 652 MB/s

[ 0.902220] raid6: int64x8 xor() 517 MB/s

[ 0.970318] raid6: neonx1 gen() 696 MB/s

[ 1.038491] raid6: neonx1 xor() 779 MB/s

[ 1.106652] raid6: neonx2 gen() 913 MB/s

[ 1.174744] raid6: neonx2 xor() 953 MB/s

[ 1.242898] raid6: neonx4 gen() 1256 MB/s

[ 1.311008] raid6: neonx4 xor() 1076 MB/s

[ 1.379147] raid6: neonx8 gen() 1352 MB/s

[ 1.447290] raid6: neonx8 xor() 1164 MB/s

[ 1.447299] raid6: using algorithm neonx8 gen() 1352 MB/s

[ 1.447307] raid6: … xor() 1164 MB/s, rmw enabled

[ 1.447316] raid6: using neon recovery algorithm

[ 1.447885] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1

[ 1.450186] vgaarb: loaded

[ 1.450510] SCSI subsystem initialized

[ 1.450735] usbcore: registered new interface driver usbfs

[ 1.450790] usbcore: registered new interface driver hub

[ 1.450896] usbcore: registered new device driver usb

[ 1.450980] pps_core: LinuxPPS API ver. 1 registered

[ 1.450989] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it

[ 1.451015] PTP clock support registered

[ 1.458746] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-06-01 13:24, variant start_x

[ 1.462755] raspberrypi-firmware soc:firmware: Firmware hash is 6379679d1ec6a8c746d7e77e015f5b56b939976f

[ 1.468043] clocksource: Switched to clocksource arch_sys_counter

[ 1.551120] VFS: Disk quotas dquot_6.6.0
[ 1.551203] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

[ 1.551397] FS-Cache: Loaded
[ 1.551610] CacheFiles: Loaded

[ 1.552318] simple-framebuffer 3ea50000.framebuffer: framebuffer at 0x3ea50000, 0x177000 bytes, mapped to 0x(ptrval)

[ 1.552333] simple-framebuffer 3ea50000.framebuffer: format=a8r8g8b8, mode=800x480x32, linelength=3200

[ 1.554610] Console: switching to colour frame buffer device 100x30

[ 1.556463] simple-framebuffer 3ea50000.framebuffer: fb0: simplefb registered!

[ 1.565670] NET: Registered protocol family 2

[ 1.566440] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes)

[ 1.566484] TCP established hash table entries: 32768 (order: 6, 262144 bytes)

[ 1.566709] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)

[ 1.567136] TCP: Hash tables configured (established 32768 bind 32768)

[ 1.567325] UDP hash table entries: 2048 (order: 4, 65536 bytes)

[ 1.567385] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)

[ 1.567663] NET: Registered protocol family 1

[ 1.567700] PCI: CLS 0 bytes, default 64

[ 1.567947] Trying to unpack rootfs image as initramfs…

[ 1.572421] Freeing initrd memory: 164K
[ 1.574404] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available

[ 1.576380] Initialise system trusted keyrings

[ 1.576580] workingset: timestamp_bits=46 max_order=20 bucket_order=0

[ 1.583605] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[ 1.585089] aufs 4.19.17±20190311

[ 1.587055] Key type asymmetric registered

[ 1.587067] Asymmetric key parser ‘x509’ registered

[ 1.587115] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)

[ 1.587299] io scheduler noop registered

[ 1.587309] io scheduler deadline registered (default)

[ 1.587453] io scheduler cfq registered

[ 1.587464] io scheduler mq-deadline registered (default)

[ 1.587473] io scheduler kyber registered

[ 1.620719] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x00000000c0000000

[ 1.620745] brcm-pcie fd500000.pcie: could not get clock

[ 1.620820] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:

[ 1.620862] brcm-pcie fd500000.pcie: MEM 0x600000000…0x603ffffff -> 0xf8000000

[ 1.672074] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)

[ 1.672381] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00

[ 1.672397] pci_bus 0000:00: root bus resource [bus 00-01]

[ 1.672412] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])

[ 1.672460] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400

[ 1.672619] pci 0000:00:00.0: PME# supported from D0 D3hot

[ 1.675489] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

[ 1.675700] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330

[ 1.675829] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]

[ 1.676245] pci 0000:01:00.0: PME# supported from D0 D3cold

[ 1.678995] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01

[ 1.679047] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]

[ 1.679065] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]

[ 1.679136] pci 0000:00:00.0: PCI bridge to [bus 01]

[ 1.679153] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff]

[ 1.679250] pci 0000:00:00.0: enabling device (0000 -> 0002)

[ 1.679302] pci 0000:01:00.0: enabling device (0000 -> 0002)

[ 1.681431] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled

[ 1.683421] iproc-rng200 fe104000.rng: hwrng registered

[ 1.683717] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)

[ 1.684461] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000

[ 1.684738] cacheinfo: Unable to detect cache hierarchy for CPU 0

[ 1.694476] brd: module loaded

[ 1.704400] loop: module loaded

[ 1.705256] Loading iSCSI transport class v2.0-870.

[ 1.705684] iscsi: registered transport (tcp)

[ 1.707071] libphy: Fixed MDIO Bus: probed

[ 1.707544] bcmgenet fd580000.genet: failed to get enet clock

[ 1.707561] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000

[ 1.707578] bcmgenet fd580000.genet: failed to get enet-wol clock

[ 1.707592] bcmgenet fd580000.genet: failed to get enet-eee clock

[ 1.707614] bcmgenet: Skipping UMAC reset

[ 1.707854] unimac-mdio unimac-mdio.-19: DMA mask not set

[ 1.716082] libphy: bcmgenet MII bus: probed

[ 1.740639] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)

[ 1.741546] usbcore: registered new interface driver r8152

[ 1.741598] usbcore: registered new interface driver lan78xx

[ 1.741645] usbcore: registered new interface driver smsc95xx

[ 1.742048] xhci_hcd 0000:01:00.0: xHCI Host Controller

[ 1.742077] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1

[ 1.747543] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890

[ 1.747858] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 42

[ 1.748770] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19

[ 1.748784] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[ 1.748795] usb usb1: Product: xHCI Host Controller

[ 1.748805] usb usb1: Manufacturer: Linux 4.19.75v64 xhci-hcd

[ 1.748815] usb usb1: SerialNumber: 0000:01:00.0

[ 1.749364] hub 1-0:1.0: USB hub found

[ 1.749445] hub 1-0:1.0: 1 port detected

[ 1.749918] xhci_hcd 0000:01:00.0: xHCI Host Controller

[ 1.749938] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2

[ 1.749963] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed

[ 1.750311] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19

[ 1.750323] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[ 1.750333] usb usb2: Product: xHCI Host Controller

[ 1.750343] usb usb2: Manufacturer: Linux 4.19.75v64 xhci-hcd

[ 1.750352] usb usb2: SerialNumber: 0000:01:00.0

[ 1.750824] hub 2-0:1.0: USB hub found

[ 1.750890] hub 2-0:1.0: 4 ports detected

[ 1.752106] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)

[ 1.777752] dwc_otg fe980000.usb: base=(ptrval)

[ 1.980528] Core Release: 2.80a

[ 1.980540] Setting default values for core params

[ 1.980568] Finished setting default values for core params

[ 2.084074] usb 1-1: new high-speed USB device number 2 using xhci_hcd

[ 2.182932] Using Buffer DMA mode

[ 2.182941] Periodic Transfer Interrupt Enhancement - disabled

[ 2.182949] Multiprocessor Interrupt Enhancement - disabled

[ 2.182959] OTG VER PARAM: 0, OTG VER FLAG: 0

[ 2.182980] Dedicated Tx FIFOs mode

[ 2.183474] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = ffffff800b3c1000 dma = 0x00000000ded34000 len=9024

[ 2.183506] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled

[ 2.183516] dwc_otg: Microframe scheduler enabled

[ 2.183649] WARN::hcd_init_fiq:497: MPHI regs_base at ffffff800918d200

[ 2.183726] dwc_otg fe980000.usb: DWC OTG Controller

[ 2.183754] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3

[ 2.183795] dwc_otg fe980000.usb: irq 23, io mem 0x00000000

[ 2.183847] Init: Port Power? op_state=1

[ 2.183856] Init: Power Port (0)

[ 2.184148] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19

[ 2.184162] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[ 2.184173] usb usb3: Product: DWC OTG Controller

[ 2.184184] usb usb3: Manufacturer: Linux 4.19.75v64 dwc_otg_hcd

[ 2.184193] usb usb3: SerialNumber: fe980000.usb

[ 2.184726] hub 3-0:1.0: USB hub found

[ 2.184776] hub 3-0:1.0: 1 port detected

[ 2.185386] dwc_otg: FIQ enabled

[ 2.185396] dwc_otg: NAK holdoff enabled

[ 2.185403] dwc_otg: FIQ split-transaction FSM enabled

[ 2.185415] Module dwc_common_port init

[ 2.185665] usbcore: registered new interface driver uas

[ 2.185780] usbcore: registered new interface driver usb-storage

[ 2.185953] mousedev: PS/2 mouse device common for all mice

[ 2.186065] rpi-ft5406 rpi_ft5406: Probing device

[ 2.186455] input: FT5406 memory based driver as /devices/virtual/input/input0

[ 2.188663] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer

[ 2.188871] bcm2835-cpufreq: min=600000 max=1500000

[ 2.189548] sdhci: Secure Digital Host Controller Interface driver

[ 2.189557] sdhci: Copyright© Pierre Ossman

[ 2.189994] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe

[ 2.190403] sdhci-pltfm: SDHCI platform and OF driver helper

[ 2.193516] ledtrig-cpu: registered to indicate activity on CPUs

[ 2.193662] hidraw: raw HID events driver © Jiri Kosina

[ 2.200086] usbcore: registered new interface driver usbhid

[ 2.200095] usbhid: USB HID core driver

[ 2.200412] ashmem: initialized

[ 2.201350] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0

[ 2.204979] Initializing XFRM netlink socket

[ 2.205010] NET: Registered protocol family 17

[ 2.205061] Key type dns_resolver registered

[ 2.205891] registered taskstats version 1

[ 2.205913] Loading compiled-in X.509 certificates

[ 2.207336] Btrfs loaded, crc32c=crc32c-generic

[ 2.214390] uart-pl011 fe201000.serial: cts_event_workaround enabled

[ 2.214504] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 19, base_baud = 0) is a PL011 rev2

[ 2.217665] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver

[ 2.218295] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver

[ 2.218979] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0

[ 2.218990] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated

[ 2.234775] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21

[ 2.234788] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0

[ 2.234799] usb 1-1: Product: USB2.0 Hub

[ 2.236540] hub 1-1:1.0: USB hub found

[ 2.236874] hub 1-1:1.0: 4 ports detected

[ 2.245205] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1

[ 2.264690] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)

[ 2.266309] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

[ 2.267926] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

[ 2.270836] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)

[ 2.272454] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

[ 2.277203] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA

[ 2.283733] of_cfs_init

[ 2.283822] of_cfs_init: OK

[ 2.287589] Freeing unused kernel memory: 1024K

[ 2.287688] Run /init as init process

[ 2.324607] random: fast init done
[ 2.347613] mmc1: new high speed SDIO card at address 0001

[ 2.384143] mmc0: new ultra high speed DDR50 SDXC card at address aaaa

[ 2.389584] mmcblk0: mmc0:aaaa SK128 119 GiB
[ 2.395381] mmcblk0: p1 p2

[ 2.532104] usb 1-1.2: new low-speed USB device number 3 using xhci_hcd

[ 2.641157] usb 1-1.2: New USB device found, idVendor=045e, idProduct=07f8, bcdDevice= 3.00

[ 2.641174] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 2.641186] usb 1-1.2: Product: Wired Keyboard 600

[ 2.641196] usb 1-1.2: Manufacturer: Microsoft

[ 2.653413] input: Microsoft Wired Keyboard 600 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:045E:07F8.0001/input/input1

[ 2.712904] hid-generic 0003:045E:07F8.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Wired Keyboard 600] on usb-0000:01:00.0-1.2/input0

[ 2.719078] input: Microsoft Wired Keyboard 600 Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:045E:07F8.0002/input/input2

[ 2.776445] input: Microsoft Wired Keyboard 600 System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:045E:07F8.0002/input/input3

[ 2.776708] hid-generic 0003:045E:07F8.0002: input,hidraw1: USB HID v1.11 Device [Microsoft Wired Keyboard 600] on usb-0000:01:00.0-1.2/input1

[ 3.745686] bcmgenet: Skipping UMAC reset

[ 3.766990] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem

[ 3.767004] EXT4-fs (mmcblk0p2): write access will be enabled during recovery

[ 3.816642] bcmgenet fd580000.genet: configuring instance for external RGMII (no delay)

[ 4.653629] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs

[ 4.656788] EXT4-fs (mmcblk0p2): 7 orphan inodes deleted
[ 4.656799] EXT4-fs (mmcblk0p2): recovery complete

[ 4.686146] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

[ 4.696181] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.726109] udevd[115]: starting version 3.2.5

[ 4.748947] random: udevd: uninitialized urandom read (16 bytes read)

[ 4.749195] random: udevd: uninitialized urandom read (16 bytes read)

[ 4.749304] random: udevd: uninitialized urandom read (16 bytes read)

[ 4.756920] udevd[117]: starting eudev-3.2.5

[ 4.832291] bcmgenet fd580000.genet eth0: Link is Down

[ 4.857067] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.866860] media: Linux media interface: v0.10

[ 4.869233] bcm2835_vc_sm_cma_probe: Videocore shared memory driver

[ 4.869253] [vc_sm_connected_init]: start

[ 4.876015] [vc_sm_connected_init]: installed successfully

[ 4.900996] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x0000ffff

[ 4.901494] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00000fff

[ 4.901940] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x0000ffff

[ 4.902377] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x0000ffff

[ 4.909335] videodev: Linux video capture interface: v2.00

[ 4.955123] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.955187] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.993541] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.995758] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.

[ 5.003701] bcm2835_audio soc:audio: card created with 8 channels

[ 5.019606] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.

[ 5.041122] udevd[130]: Error running install command for drm

[ 5.053627] udevd[127]: Error running install command for drm

[ 5.084558] pisound: Searching for spi device…

[ 5.084574] pisound: Found!

[ 5.085088] cfg80211: Loading compiled-in X.509 certificates for regulatory database

[ 5.189216] pisound: Detected Pisound card:

[ 5.189230] pisound: Serial: PS-0WZBBSZ

[ 5.189238] pisound: Version: 1.03

[ 5.189245] pisound: Id: 1e93153555313630360c0d16

[ 5.191699] snd-rpi-pisound soc:sound: snd-soc-dummy-dai <-> fe203000.i2s mapping ok

[ 5.191718] snd-rpi-pisound soc:sound: ASoC: no DMI vendor name!

[ 5.408358] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’

[ 5.464831] brcmfmac: F1 signature read @0x18000000=0x15264345

[ 5.470700] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

[ 5.471089] usbcore: registered new interface driver brcmfmac

[ 5.629248] bcm2835-codec bcm2835-codec: Device registered as /dev/video10

[ 5.629284] bcm2835-codec bcm2835-codec: Loaded V4L2 decode

[ 5.632418] bcm2835-codec bcm2835-codec: Device registered as /dev/video11

[ 5.632452] bcm2835-codec bcm2835-codec: Loaded V4L2 encode

[ 5.636513] bcm2835-codec bcm2835-codec: Device registered as /dev/video12

[ 5.636538] bcm2835-codec bcm2835-codec: Loaded V4L2 isp

[ 5.693550] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

[ 5.706744] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

[ 7.904309] bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

[ 11.001386] systemd[1]: System time before build time, advancing clock.

[ 11.075904] NET: Registered protocol family 10

[ 11.076755] Segment Routing with IPv6

[ 11.106442] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)

[ 11.106741] systemd[1]: Detected architecture arm64.

[ 11.112473] systemd[1]: Set hostname to .

[ 11.359761] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.

[ 11.359772] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)

[ 11.600094] urandom_read: 2 callbacks suppressed

[ 11.600099] random: systemd: uninitialized urandom read (16 bytes read)

[ 11.600869] systemd[1]: Listening on Syslog Socket.

[ 11.601277] random: systemd: uninitialized urandom read (16 bytes read)

[ 11.601585] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.

[ 11.601633] random: systemd: uninitialized urandom read (16 bytes read)

[ 11.603578] systemd[1]: Created slice system-getty.slice.

[ 11.604299] systemd[1]: Listening on Journal Socket (/dev/log).

[ 11.604690] systemd[1]: Listening on Journal Socket.

[ 11.800432] RPC: Registered named UNIX socket transport module.

[ 11.800438] RPC: Registered udp transport module.

[ 11.800442] RPC: Registered tcp transport module.

[ 11.800445] RPC: Registered tcp NFSv4.1 backchannel transport module.

[ 11.866440] systemd-journald[201]: Received request to flush runtime journal from PID 1

[ 12.586931] random: crng init done

[ 12.586940] random: 2 urandom warning(s) missed due to ratelimiting

[ 12.791999] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])

[ 12.792011] checking generic (3ea50000 177000) vs hw (0 ffffffffffffffff)

[ 12.792015] fb: switching to vc4drmfb from simple

[ 12.792254] Console: switching to colour dummy device 80x25

[ 12.798280] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1

[ 12.798291] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

[ 12.798295] [drm] No driver support for vblank timestamp query.

[ 12.798299] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL

[ 12.806876] Console: switching to colour frame buffer device 100x30

[ 12.823162] vc4-drm soc:gpu: fb0: DRM emulated frame buffer device

[ 12.825801] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0

[ 12.878733] 8021q: 802.1Q VLAN Support v1.8

[ 13.175604] brcmfmac: power management disabled

[ 13.175903] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ 13.250862] Bluetooth: Core ver 2.22

[ 13.250912] NET: Registered protocol family 31

[ 13.250916] Bluetooth: HCI device and connection manager initialized

[ 13.250928] Bluetooth: HCI socket layer initialized

[ 13.250934] Bluetooth: L2CAP socket layer initialized

[ 13.250957] Bluetooth: SCO socket layer initialized

[ 13.654696] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[ 13.654703] Bluetooth: BNEP filters: protocol multicast

[ 13.654715] Bluetooth: BNEP socket layer initialized

[ 15.024008] ICMPv6: process `dhcpcd’ is using deprecated sysctl (syscall) net.ipv6.neigh.eth0.retrans_time - use net.ipv6.neigh.eth0.retrans_time_ms instead

[ 19.134999] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[ 21.197984] brcmfmac: power management disabled

[ 21.198924] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ 23.066106] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
9

I don’t see any obvious errors in the log, especially around Bluetooth.

What is the current biggest issue that we should focus on debugging? :slight_smile:

10

I’ve been spending some time with the bluetooth issue, and I have strong suspensions this is a hardware problem. So while I pursue other avenues for a solution to that problem, perhaps you could give me some hints to get startx running? There are no problems running X on the touchscreen I have attached via the ribbon port when booted into Rasbian. So at the very least, it would be nice to have the GUI up on the touchscreen under Patchbox. There might be other issues trying to run BOTH the touchscreen port and either or both of the HDMI ports concurrently, so that might be a stretch goal for me. :wink:

Below is the dmesg from when I booted up with an HDMI monitor plugged into HDMI 1. Does this provide any infor mation as to how I can troubleshoot startx?

Thanks again.

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]

[ 0.000000] Linux version 4.19.75v64 (max@lynx) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #1 SMP PREEMPT Sat Oct 5 03:06:01 CEST 2019

[ 0.000000] Machine model: Raspberry Pi 4 Model B Rev 1.2

[ 0.000000] efi: Getting EFI parameters from FDT:

[ 0.000000] efi: UEFI not found.

[ 0.000000] cma: Reserved 256 MiB at 0x000000001ec00000

[ 0.000000] On node 0 totalpages: 991232

[ 0.000000] DMA32 zone: 3456 pages used for memmap

[ 0.000000] DMA32 zone: 0 pages reserved

[ 0.000000] DMA32 zone: 221184 pages, LIFO batch:63

[ 0.000000] Normal zone: 12032 pages used for memmap

[ 0.000000] Normal zone: 770048 pages, LIFO batch:63

[ 0.000000] random: get_random_bytes called from start_kernel+0xb4/0x480 with crng_init=0

[ 0.000000] percpu: Embedded 24 pages/cpu s57368 r8192 d32744 u98304

[ 0.000000] pcpu-alloc: s57368 r8192 d32744 u98304 alloc=24*4096

[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3

[ 0.000000] Detected PIPT I-cache on CPU0

[ 0.000000] CPU features: enabling workaround for EL2 vector hardening

[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 975744

[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=DC:A6:32:66:C7:02 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 elevator=deadline quiet bootmenutimeout=10 datadev=mmcblk0p2

[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)

[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)

[ 0.000000] software IO TLB: mapped [mem 0x31fff000-0x35fff000] (64MB)

[ 0.000000] Memory: 3549028K/3964928K available (9148K kernel code, 942K rwdata, 2700K rodata, 1024K init, 1122K bss, 153756K reserved, 262144K cma-reserved)

[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

[ 0.000000] ftrace: allocating 29516 entries in 116 pages

[ 0.000000] rcu: Preemptible hierarchical RCU implementation.

[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.

[ 0.000000] Tasks RCU enabled.

[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4

[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0

[ 0.000000] GIC: Using split EOI/Deactivate mode

[ 0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).

[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns

[ 0.000006] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns

[ 0.000221] Console: colour dummy device 80x25
[ 0.000244] console [tty0] enabled

[ 0.000289] Calibrating delay loop (skipped), value calculated using timer frequency… 108.00 BogoMIPS (lpj=216000)

[ 0.000308] pid_max: default: 32768 minimum: 301

[ 0.000594] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)

[ 0.000647] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)

[ 0.024052] ASID allocator initialised with 32768 entries

[ 0.032047] rcu: Hierarchical SRCU implementation.

[ 0.040560] EFI services will not be available.

[ 0.048103] smp: Bringing up secondary CPUs …

[ 0.080306] Detected PIPT I-cache on CPU1

[ 0.080369] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]

[ 0.112397] Detected PIPT I-cache on CPU2

[ 0.112442] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]

[ 0.144513] Detected PIPT I-cache on CPU3

[ 0.144557] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]

[ 0.144697] smp: Brought up 1 node, 4 CPUs

[ 0.144707] SMP: Total of 4 processors activated.

[ 0.144719] CPU features: detected: 32-bit EL0 Support

[ 0.145378] CPU: All CPU(s) started at EL2

[ 0.145416] alternatives: patching kernel code
[ 0.146524] devtmpfs: initialized

[ 0.154596] Enabled cp15_barrier support

[ 0.154623] Enabled setend support

[ 0.155001] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns

[ 0.155023] futex hash table entries: 1024 (order: 4, 65536 bytes)

[ 0.161764] xor: measuring software checksum speed

[ 0.200636] 8regs : 2536.000 MB/sec

[ 0.240715] 8regs_prefetch: 2181.000 MB/sec

[ 0.280797] 32regs : 2855.000 MB/sec

[ 0.320882] 32regs_prefetch: 2510.000 MB/sec

[ 0.320891] xor: using function: 32regs (2855.000 MB/sec)

[ 0.320910] pinctrl core: initialized pinctrl subsystem

[ 0.321539] DMI not present or invalid.

[ 0.321953] NET: Registered protocol family 16

[ 0.323172] cpuidle: using governor menu

[ 0.323428] vdso: 2 pages (1 code @ (ptrval), 1 data @ (ptrval))

[ 0.323441] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.

[ 0.326033] DMA: preallocated 1024 KiB pool for atomic allocations

[ 0.326123] Serial: AMBA PL011 UART driver

[ 0.329832] bcm2835-mbox fe00b880.mailbox: mailbox enabled

[ 0.425295] raid6: int64x1 gen() 342 MB/s

[ 0.493375] raid6: int64x1 xor() 329 MB/s

[ 0.561581] raid6: int64x2 gen() 476 MB/s

[ 0.629660] raid6: int64x2 xor() 472 MB/s

[ 0.697822] raid6: int64x4 gen() 692 MB/s

[ 0.765905] raid6: int64x4 xor() 523 MB/s

[ 0.834075] raid6: int64x8 gen() 647 MB/s

[ 0.902167] raid6: int64x8 xor() 517 MB/s

[ 0.970365] raid6: neonx1 gen() 696 MB/s

[ 1.038472] raid6: neonx1 xor() 779 MB/s

[ 1.106624] raid6: neonx2 gen() 913 MB/s

[ 1.174732] raid6: neonx2 xor() 953 MB/s

[ 1.242908] raid6: neonx4 gen() 1262 MB/s

[ 1.311015] raid6: neonx4 xor() 1076 MB/s

[ 1.379177] raid6: neonx8 gen() 1354 MB/s

[ 1.447276] raid6: neonx8 xor() 1164 MB/s

[ 1.447285] raid6: using algorithm neonx8 gen() 1354 MB/s

[ 1.447293] raid6: … xor() 1164 MB/s, rmw enabled

[ 1.447302] raid6: using neon recovery algorithm

[ 1.447868] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1

[ 1.450177] vgaarb: loaded

[ 1.450504] SCSI subsystem initialized

[ 1.450732] usbcore: registered new interface driver usbfs

[ 1.450786] usbcore: registered new interface driver hub

[ 1.450891] usbcore: registered new device driver usb

[ 1.450977] pps_core: LinuxPPS API ver. 1 registered

[ 1.450986] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it

[ 1.451012] PTP clock support registered

[ 1.458731] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-06-01 13:24, variant start_x

[ 1.462741] raspberrypi-firmware soc:firmware: Firmware hash is 6379679d1ec6a8c746d7e77e015f5b56b939976f

[ 1.468022] clocksource: Switched to clocksource arch_sys_counter

[ 1.551135] VFS: Disk quotas dquot_6.6.0

[ 1.551219] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

[ 1.551414] FS-Cache: Loaded

[ 1.551630] CacheFiles: Loaded

[ 1.552343] simple-framebuffer 3ea4e000.framebuffer: framebuffer at 0x3ea4e000, 0x177000 bytes, mapped to 0x(ptrval)

[ 1.552358] simple-framebuffer 3ea4e000.framebuffer: format=a8r8g8b8, mode=800x480x32, linelength=3200

[ 1.554640] Console: switching to colour frame buffer device 100x30

[ 1.556494] simple-framebuffer 3ea4e000.framebuffer: fb0: simplefb registered!

[ 1.565672] NET: Registered protocol family 2

[ 1.566446] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes)

[ 1.566490] TCP established hash table entries: 32768 (order: 6, 262144 bytes)

[ 1.566715] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)

[ 1.567153] TCP: Hash tables configured (established 32768 bind 32768)

[ 1.567356] UDP hash table entries: 2048 (order: 4, 65536 bytes)

[ 1.567417] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)

[ 1.567706] NET: Registered protocol family 1

[ 1.567744] PCI: CLS 0 bytes, default 64

[ 1.567993] Trying to unpack rootfs image as initramfs…

[ 1.572450] Freeing initrd memory: 164K

[ 1.574441] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available

[ 1.576421] Initialise system trusted keyrings

[ 1.576627] workingset: timestamp_bits=46 max_order=20 bucket_order=0

[ 1.583677] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[ 1.585160] aufs 4.19.17±20190311

[ 1.587060] Key type asymmetric registered

[ 1.587071] Asymmetric key parser ‘x509’ registered

[ 1.587116] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)

[ 1.587305] io scheduler noop registered

[ 1.587315] io scheduler deadline registered (default)

[ 1.587481] io scheduler cfq registered

[ 1.587492] io scheduler mq-deadline registered (default)

[ 1.587501] io scheduler kyber registered

[ 1.620736] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x00000000c0000000

[ 1.620763] brcm-pcie fd500000.pcie: could not get clock

[ 1.620838] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:

[ 1.620882] brcm-pcie fd500000.pcie: MEM 0x600000000…0x603ffffff -> 0xf8000000

[ 1.672060] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)

[ 1.672372] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00

[ 1.672390] pci_bus 0000:00: root bus resource [bus 00-01]

[ 1.672411] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])

[ 1.672460] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400

[ 1.672620] pci 0000:00:00.0: PME# supported from D0 D3hot

[ 1.675686] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

[ 1.675900] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330

[ 1.676101] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]

[ 1.676433] pci 0000:01:00.0: PME# supported from D0 D3cold

[ 1.679372] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01

[ 1.679423] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]

[ 1.679440] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]

[ 1.679511] pci 0000:00:00.0: PCI bridge to [bus 01]

[ 1.679527] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff]

[ 1.679625] pci 0000:00:00.0: enabling device (0000 -> 0002)

[ 1.679677] pci 0000:01:00.0: enabling device (0000 -> 0002)

[ 1.681824] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled

[ 1.683859] iproc-rng200 fe104000.rng: hwrng registered

[ 1.684207] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)

[ 1.684912] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000

[ 1.685190] cacheinfo: Unable to detect cache hierarchy for CPU 0

[ 1.694938] brd: module loaded

[ 1.704892] loop: module loaded

[ 1.705744] Loading iSCSI transport class v2.0-870.

[ 1.706178] iscsi: registered transport (tcp)

[ 1.707593] libphy: Fixed MDIO Bus: probed

[ 1.708122] bcmgenet fd580000.genet: failed to get enet clock

[ 1.708139] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000

[ 1.708154] bcmgenet fd580000.genet: failed to get enet-wol clock

[ 1.708169] bcmgenet fd580000.genet: failed to get enet-eee clock

[ 1.708191] bcmgenet: Skipping UMAC reset

[ 1.708432] unimac-mdio unimac-mdio.-19: DMA mask not set

[ 1.720063] libphy: bcmgenet MII bus: probed

[ 1.744626] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)

[ 1.745521] usbcore: registered new interface driver r8152

[ 1.745571] usbcore: registered new interface driver lan78xx

[ 1.745619] usbcore: registered new interface driver smsc95xx

[ 1.746023] xhci_hcd 0000:01:00.0: xHCI Host Controller

[ 1.746052] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1

[ 1.751534] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890

[ 1.751865] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 42

[ 1.752770] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19

[ 1.752784] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[ 1.752795] usb usb1: Product: xHCI Host Controller

[ 1.752806] usb usb1: Manufacturer: Linux 4.19.75v64 xhci-hcd

[ 1.752815] usb usb1: SerialNumber: 0000:01:00.0

[ 1.753362] hub 1-0:1.0: USB hub found

[ 1.753451] hub 1-0:1.0: 1 port detected

[ 1.753922] xhci_hcd 0000:01:00.0: xHCI Host Controller

[ 1.753942] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2

[ 1.753962] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed

[ 1.754309] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19

[ 1.754322] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[ 1.754332] usb usb2: Product: xHCI Host Controller

[ 1.754343] usb usb2: Manufacturer: Linux 4.19.75v64 xhci-hcd

[ 1.754352] usb usb2: SerialNumber: 0000:01:00.0

[ 1.754827] hub 2-0:1.0: USB hub found

[ 1.754891] hub 2-0:1.0: 4 ports detected

[ 1.756185] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)

[ 1.781843] dwc_otg fe980000.usb: base=(ptrval)

[ 1.984396] Core Release: 2.80a

[ 1.984408] Setting default values for core params

[ 1.984436] Finished setting default values for core params

[ 2.088055] usb 1-1: new high-speed USB device number 2 using xhci_hcd

[ 2.186803] Using Buffer DMA mode

[ 2.186813] Periodic Transfer Interrupt Enhancement - disabled

[ 2.186822] Multiprocessor Interrupt Enhancement - disabled

[ 2.186831] OTG VER PARAM: 0, OTG VER FLAG: 0

[ 2.186853] Dedicated Tx FIFOs mode

[ 2.187346] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = ffffff800b3d3000 dma = 0x00000000ded34000 len=9024

[ 2.187377] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled

[ 2.187387] dwc_otg: Microframe scheduler enabled

[ 2.187519] WARN::hcd_init_fiq:497: MPHI regs_base at ffffff800918d200

[ 2.187597] dwc_otg fe980000.usb: DWC OTG Controller

[ 2.187624] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3

[ 2.187665] dwc_otg fe980000.usb: irq 23, io mem 0x00000000

[ 2.187717] Init: Port Power? op_state=1
[ 2.187726] Init: Power Port (0)

[ 2.187992] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19

[ 2.188030] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[ 2.188042] usb usb3: Product: DWC OTG Controller

[ 2.188053] usb usb3: Manufacturer: Linux 4.19.75v64 dwc_otg_hcd

[ 2.188063] usb usb3: SerialNumber: fe980000.usb

[ 2.188594] hub 3-0:1.0: USB hub found

[ 2.188642] hub 3-0:1.0: 1 port detected

[ 2.189247] dwc_otg: FIQ enabled

[ 2.189256] dwc_otg: NAK holdoff enabled

[ 2.189264] dwc_otg: FIQ split-transaction FSM enabled

[ 2.189276] Module dwc_common_port init

[ 2.189552] usbcore: registered new interface driver uas

[ 2.189667] usbcore: registered new interface driver usb-storage

[ 2.189842] mousedev: PS/2 mouse device common for all mice

[ 2.189955] rpi-ft5406 rpi_ft5406: Probing device

[ 2.190346] input: FT5406 memory based driver as /devices/virtual/input/input0

[ 2.192589] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer

[ 2.192805] bcm2835-cpufreq: min=600000 max=1500000

[ 2.193486] sdhci: Secure Digital Host Controller Interface driver

[ 2.193495] sdhci: Copyright© Pierre Ossman

[ 2.193946] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe

[ 2.194364] sdhci-pltfm: SDHCI platform and OF driver helper

[ 2.197475] ledtrig-cpu: registered to indicate activity on CPUs

[ 2.197620] hidraw: raw HID events driver © Jiri Kosina

[ 2.199981] usbcore: registered new interface driver usbhid

[ 2.199990] usbhid: USB HID core driver

[ 2.200338] ashmem: initialized

[ 2.201288] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0

[ 2.204883] Initializing XFRM netlink socket

[ 2.204913] NET: Registered protocol family 17

[ 2.204969] Key type dns_resolver registered

[ 2.205778] registered taskstats version 1

[ 2.205798] Loading compiled-in X.509 certificates

[ 2.207223] Btrfs loaded, crc32c=crc32c-generic

[ 2.214249] uart-pl011 fe201000.serial: cts_event_workaround enabled

[ 2.214363] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 19, base_baud = 0) is a PL011 rev2

[ 2.217568] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver

[ 2.218131] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver

[ 2.218790] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0

[ 2.218801] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated

[ 2.238746] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21

[ 2.238760] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0

[ 2.238771] usb 1-1: Product: USB2.0 Hub

[ 2.240582] hub 1-1:1.0: USB hub found

[ 2.240917] hub 1-1:1.0: 4 ports detected

[ 2.244965] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1

[ 2.265503] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)

[ 2.267121] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

[ 2.268740] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

[ 2.271637] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)

[ 2.273252] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

[ 2.276679] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA

[ 2.278886] of_cfs_init

[ 2.278982] of_cfs_init: OK

[ 2.282736] Freeing unused kernel memory: 1024K

[ 2.282835] Run /init as init process

[ 2.325792] random: fast init done

[ 2.349502] mmc1: new high speed SDIO card at address 0001

[ 2.385294] mmc0: new ultra high speed DDR50 SDXC card at address aaaa

[ 2.386672] mmcblk0: mmc0:aaaa SK128 119 GiB

[ 2.392460] mmcblk0: p1 p2

[ 2.536091] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd

[ 2.646022] usb 1-1.2: New USB device found, idVendor=1997, idProduct=2433, bcdDevice= 1.08

[ 2.646039] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 2.646050] usb 1-1.2: Product: mini keyboard

[ 2.646061] usb 1-1.2: Manufacturer:

[ 2.656773] input: mini keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:1997:2433.0001/input/input1

[ 2.717124] hid-generic 0003:1997:2433.0001: input,hidraw0: USB HID v1.01 Keyboard [ mini keyboard] on usb-0000:01:00.0-1.2/input0

[ 2.723616] input: mini keyboard Mouse as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:1997:2433.0002/input/input2

[ 2.724122] input: mini keyboard System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:1997:2433.0002/input/input3

[ 2.784482] input: mini keyboard Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:1997:2433.0002/input/input4

[ 2.784783] hid-generic 0003:1997:2433.0002: input,hidraw1: USB HID v1.01 Mouse [ mini keyboard] on usb-0000:01:00.0-1.2/input1

[ 3.692308] bcmgenet: Skipping UMAC reset

[ 3.712658] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem

[ 3.712672] EXT4-fs (mmcblk0p2): write access will be enabled during recovery

[ 3.764431] bcmgenet fd580000.genet: configuring instance for external RGMII (no delay)

[ 3.793521] EXT4-fs (mmcblk0p2): recovery complete

[ 3.795984] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

[ 3.805212] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

[ 3.827824] udevd[115]: starting version 3.2.5

[ 3.849414] random: udevd: uninitialized urandom read (16 bytes read)

[ 3.849663] random: udevd: uninitialized urandom read (16 bytes read)

[ 3.849770] random: udevd: uninitialized urandom read (16 bytes read)

[ 3.857440] udevd[117]: starting eudev-3.2.5

[ 3.977187] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x0000ffff

[ 3.978295] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00000fff

[ 3.978808] media: Linux media interface: v0.10

[ 3.979291] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.

[ 3.979434] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x0000ffff

[ 3.979972] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x0000ffff

[ 3.982711] bcm2835_vc_sm_cma_probe: Videocore shared memory driver

[ 3.982729] [vc_sm_connected_init]: start

[ 4.000555] [vc_sm_connected_init]: installed successfully

[ 4.009587] videodev: Linux video capture interface: v2.00

[ 4.047975] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.060993] udevd[124]: Error running install command for drm

[ 4.064255] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.082767] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.083954] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.

[ 4.103559] bcm2835_audio soc:audio: card created with 8 channels

[ 4.113079] pisound: Searching for spi device…

[ 4.113095] pisound: Found!

[ 4.136157] udevd[119]: Error running install command for drm

[ 4.254742] cfg80211: Loading compiled-in X.509 certificates for regulatory database

[ 4.273035] pisound: Detected Pisound card:

[ 4.273048] pisound: Serial: PS-0WZBBSZ

[ 4.273056] pisound: Version: 1.03

[ 4.273064] pisound: Id: 1e93153555313630360c0d16

[ 4.276101] snd-rpi-pisound soc:sound: snd-soc-dummy-dai <-> fe203000.i2s mapping ok

[ 4.276120] snd-rpi-pisound soc:sound: ASoC: no DMI vendor name!

[ 4.550355] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’

[ 4.603717] brcmfmac: F1 signature read @0x18000000=0x15264345

[ 4.611105] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

[ 4.611504] usbcore: registered new interface driver brcmfmac

[ 4.706535] bcm2835-codec bcm2835-codec: Device registered as /dev/video10

[ 4.706572] bcm2835-codec bcm2835-codec: Loaded V4L2 decode

[ 4.710264] bcm2835-codec bcm2835-codec: Device registered as /dev/video11

[ 4.710299] bcm2835-codec bcm2835-codec: Loaded V4L2 encode

[ 4.714960] bcm2835-codec bcm2835-codec: Device registered as /dev/video12

[ 4.715004] bcm2835-codec bcm2835-codec: Loaded V4L2 isp

[ 4.768198] bcmgenet fd580000.genet eth0: Link is Down

[ 4.838943] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

[ 4.851640] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

[ 14.896906] systemd[1]: System time before build time, advancing clock.

[ 14.971957] NET: Registered protocol family 10

[ 14.972520] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[ 14.972648] Segment Routing with IPv6

[ 15.002298] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)

[ 15.002592] systemd[1]: Detected architecture arm64.

[ 15.008690] systemd[1]: Set hostname to .

[ 15.235599] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.

[ 15.235610] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)

[ 15.530898] urandom_read: 2 callbacks suppressed

[ 15.530903] random: systemd: uninitialized urandom read (16 bytes read)

[ 15.531186] systemd[1]: Started Forward Password Requests to Wall Directory Watch.

[ 15.531300] random: systemd: uninitialized urandom read (16 bytes read)

[ 15.531783] systemd[1]: Listening on Journal Socket (/dev/log).

[ 15.531830] random: systemd: uninitialized urandom read (16 bytes read)

[ 15.531978] systemd[1]: Listening on initctl Compatibility Named Pipe.

[ 15.532534] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.

[ 15.532893] systemd[1]: Listening on udev Kernel Socket.

[ 15.699275] RPC: Registered named UNIX socket transport module.

[ 15.699282] RPC: Registered udp transport module.

[ 15.699285] RPC: Registered tcp transport module.

[ 15.699289] RPC: Registered tcp NFSv4.1 backchannel transport module.

[ 15.795133] systemd-journald[201]: Received request to flush runtime journal from PID 1

[ 16.611978] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0

[ 16.633452] random: crng init done

[ 16.633462] random: 2 urandom warning(s) missed due to ratelimiting

[ 16.662270] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])

[ 16.662281] checking generic (3ea4e000 177000) vs hw (0 ffffffffffffffff)

[ 16.662285] fb: switching to vc4drmfb from simple
[ 16.662380] Console: switching to colour dummy device 80x25

[ 16.667146] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1

[ 16.667155] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

[ 16.667158] [drm] No driver support for vblank timestamp query.

[ 16.667162] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL

[ 16.684656] Console: switching to colour frame buffer device 100x30

[ 16.701656] vc4-drm soc:gpu: fb0: DRM emulated frame buffer device

[ 16.875883] 8021q: 802.1Q VLAN Support v1.8

[ 17.023075] Bluetooth: Core ver 2.22

[ 17.023132] NET: Registered protocol family 31

[ 17.023136] Bluetooth: HCI device and connection manager initialized

[ 17.023148] Bluetooth: HCI socket layer initialized

[ 17.023155] Bluetooth: L2CAP socket layer initialized

[ 17.023175] Bluetooth: SCO socket layer initialized

[ 17.175087] brcmfmac: power management disabled

[ 17.175357] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ 17.570849] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[ 17.570856] Bluetooth: BNEP filters: protocol multicast

[ 17.570867] Bluetooth: BNEP socket layer initialized

[ 29.191085] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[ 30.531564] ICMPv6: process `dhcpcd’ is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use net.ipv6.neigh.wlan0.retrans_time_ms instead

[ 36.212836] brcmfmac: power management disabled

[ 36.214109] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ 38.063804] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

11

Okay, I was totally barking up the wrong tree, but I’ve been getting a quick education along the way. I have the GUI up and running on the touchscreen. First off, apologies for subjecting everyone to all the dmesg logs. I started poking around in Xorg.0.log on both the Rasbian and the Patchbox distros to compare and troubleshoot. Long story short, I commented out the single entry in /usr/share/X11/xorg.conf.d/99-fbturbo.conf which forced startx to bypass any settings that it was otherwise choosing as a default device.
Now to resolve the problem Patchbox has with dphy-swapfile. This is causing patchbox->update to fail.

As to the question about getting Patchbox to install and boot using Berryboot, the answer is, “Yes, it works!” Obviously, I’ll continue to tweek and troubleshoot (there’s still the nagging problem with Bluetooth) , but don’t think any of my current problems are related to using Berryboot.

12

I think /usr/share/ is more for ‘read only data’ to be shared for software users mostly as examples, and the configuration that actually gets used and should be customized for individual systems are under /etc/, so probably it’d be /etc/X11/xorg.conf.d/99-fbturbo.conf or somethnig similar.

Could you please share the exact change you had to do to its contents?

I think Raspbian is not using swap files by default, neither does Patchbox. What is the error that patchbox->update prints?

Could you check the Bluetooth out with Patchbox OS or Raspbian images written directly, to rule out any Berryboot or hardware specifics? (We’ve seen at least one RPi board where Bluetooth stopped working at all, regardless of OS)

13

It appears that Patchbox has the extra file, 99-fbturbo.conf in the /etc/X11/xorg.conf.d/ folder that Rasbian does not. In comparing Xorg.0.log files from the two distros, you can see that they both check the xorg.conf.d folder in their search for default device descriptions. Rasbian gets no joy and moves on elsewhere for configuration info. Patchbox catches the 99.fbturbo.conf file and can never start the server as a result.
Since this is ‘read only data’, I couldn’t rm the file, but I did a chmod 666 and ran nano to comment out the single entry:

#This is a minimal sample config file, which can be copied to #/etc/X11/xorg.conf in order to make the Xorg server pick up #and load xf86-video-fbturbo driver installed in the system. # #When troubleshooting, check /var/log/Xorg.0.log for the debugging #output and error messages. # #Run "man fbturbo" to get additional information about the extra #configuration options for tuning the driver.

#Section “Device”
#Identifier “Allwinner A10/A13 FBDEV”
#Driver “fbturbo”
#Option “fbdev” “/dev/fb0”
#Option “SwapbuffersWait” “true”
#EndSection

I suppose I could have put a blank 99-fbturbo.conf in /etc/ to achieve the same effect? As I said, it’s been a long time since I’ve played around in UNIX/LINIX and just because I might be able to trace stuff and tinker with it doesn’t mean I know what I’m doing! However, I’ll try to change the file back to it’s original state and put a fix in /etc/X11/xorg.cong file instead when time permits and see what happens.Either way, the intent is to make sure startx doesn’t get the chance to consider picking up the Xorg server with the xf86-video-fbturbo driver. I suspect this might only be an issue when using a touchscreen via the DSI connector?

In a related note, I completely uninstalled dphys-swapfile and now I can run updates w/o error. My reading up on this seems to indicate that using dphys-swapfile is (was?) best employed in headless configuration situations. I’m curious if Patchbox still benefits from it on a RPi4? While I’m not currently configuring my setup to be headless, I am hoping for as low a latency as I can achieve and will certainly be working with Pisound headlessly in the future.

Finally, I still have the Bluetooth problem (which I believe is a bad bluetooth chip) and I have issues with ALSA starting up. So that’s what currently has my attention. Bluetooth service will start, but will fail shortly afterwards. That’s why you don’t see anything obvious in the dmesg logs. It appears that the service returns a running status before it receives any actual hardware responses. Then, when you run patchbox->bluetooth->status, you get:

bluetooth_supported=0 bluetooth_service_active_state=active bluetooth_service_sub_state=running ... ... and then the point of the problem I'm working on right now: bluealsa_service_active_state=inactive bluealsa_service_sub_state=dead hciuart_service_active_state=inactive hciuart_service_sub_state=dead

I’ve tried to run bluetooth on this RPi4 from both Patchbox and Rasbian with no luck, but I have not eliminated Berryboot yet. Needless to say, I’m making my above statements based on trolling many threads and forums as well as running several tests myself, so my interpretation of the situation isn’t up to scientific rigor. Aside from trying to eliminate Berryboot as a factor, another experiment I can now perform since I’ve now resolved my updating problems, is to hold blue at 5.50-1.2~deb10u1 as some folks have reported success with getting their bluetooth to be responsive that way. However, those folks generally have been experiencing a conflict between the Wlan and the Bluetooth on their RPi4s and my RPi4 seems to fail on a step prior to where everyone else had gone on to see success with the version holding. That result tends to put me in the misc bin of folks that have tried everything, couldn’t figure out what was wrong for weeks, only to replace the RPi4 and find they had a bad chipset. I’ve heard the BT chipset with the RPi4 has a possibly ‘high’ failure rate, but I don’t know if that’s got any substantiation to it. As I stated earlier, the Pi is in a full body, dual fan heat sink. I wonder if that might be a factor as well?

It’s been a few weeks since I received my Pisound and I’m getting a bit anxious to plug some cables into it and make some music!

14

Ugh.
Finally got the chance to pull apart my “official” RPi4, case, touchscreen, and heat shield so that I could once again swap SD cards. I figured I might as well since I had so much indication that the Bluetooth chipset was dead and I’d need to swap the Pi out eventually anyway. This gave me the chance to run a distro of… anything… w/o Berryboot involved to see if that might be the cause of of my bluetooth problems. I mean, why not? At least it’ll eliminate the outside chance I actually have a good chipset.

So of course I now have bluetooth running.

I suppose this is good news as I have more information to troubleshoot my problem… But I think I’m getting a migraine over all this! Here’s what I’m thinking my next steps will be, but please chime in if you think I’m setting myself up to bang my head on a wall some more:

  1. Gather version numbers and other info about the current configuration. Then see if updates to the system break Bluetooth.

  2. Put the Berryboot’d Patchbox distro SD back in the RPi4 and see if I can get Bluetooth back and running by using what I’ve learned (if anything) from step 1 and/or exploring the notion of needing very specific driver versions from bluez.org as opposed to the latest updates as I’ve seen from discussions such as this one: https://github.com/RPi-Distro/firmware-nonfree/issues/8

As always, any advice is most welcome!

15

Did you get BT working on Raspbian OS or Patchbox OS? If the former, it may be worth trying out Patchbox OS without Berryboot too, just to make sure whether it works or not for you in the base system.

16

Sadly, the former (Raspbian). I’d be surprised at this point if I couldn’t get Bluetooth working on a clean Patchbox distro, but also at this point, the more I learn the easier it is to stick my foot in my mouth, so a clean Patchbox will be another experiment!

I’ve stated before that my setup is far from a headless Pisound box. My objective is something like a Zynthian minus all the problems that seems it’s had with HiFiBerry. Not only do I want to make use of the Pisound, but I also want to break out the GPIO for controllers and other I/O. I want a platform I can run N-Synth on. And finally, a platform I can do development for other headless Pisound projects. With the release of RPi4, I figured I could wait for others to maybe develop my dream platform, or now is the time to do it myself. Even when complete, this platform will be hosting MY learning curve for years to come.

I realize in some ways, I could be seen as needlessly complicating a problem, but I also hope that this bears a lot of fruit in terms of information that others on the forum can use.

17

Wow.

Patchbox is a beautiful thing! I have it running clean and have my phone paired and running the app. Not only that, but I can see that there’s settings and resources available to the GUI that did not map over with Berryboot such as the splashscreen and the menu icon had been pushed left off the display.

1 Like
18

Btw, if your case involves metal around Raspberry Pi, it might interfere heavily with Bluetooth, and WiFi connectivity. Could this have been the issue with Bluetooth? :slight_smile:

19

I had wondered the same. However, so far as I can tell, running without Berryboot has yielded a perfectly fine installation of Patchbox/Pisound. I haven’t progressed any further with trying to get Berryboot working because I’ve been playing music all night (finally)! Bluetooth and WiFi are working just fine.

So now I have a quandary: because the touchscreen housing (not the full-metal heat sink) prevents me from getting to the SD card when fully assembled, I seem to have no way to switch back and forth between other distros and at least Patchbox specifically. Berryboot seemingly offers a solution and unlike NOOBS, supposedly allows you to boot from a thumb drive. I have not explored that option yet, nor have I looked into the RPi4 firmware update that supposedly incorporates that capability directly in the PI. In reading the thread on the RPi4 firmware update, you (Giedrius) mention the possibility of having to recompile Patchbox with with the regular kernal (Support for boot from USB? Pi 4b). In using the “adding custom distributions” process of incorporating Patchbox into Berryboot solution, would I be mistaken to say that this process might also swap out the Patchbox kernal for one provided via Berryboot? I’m left wondering if the cost of having a bootloader on the SD card or even booting from a USB stick is ultimately going to come back around and impact the low latency performance that’s the hallmark of Patchbox? I’d love to resolve this ‘bootloader quandry’ so that I can get on with the ‘meat and potatoes’ work I hope to accomplish with the Pisound, but I’m starting to wonder what the cost of resolving this problem will be vs moving on with a single purpose RPi4 box? I feel that would be a very inconvenient solution, but one I’ll accept if there’s presently no better solution worth pursuing. However, it also feels like this nut is half cracked and I shouldn’t give up yet. Maybe getting this right will help others along the way.

20

We don’t know yet for certain whether the booting from USB happens all within Raspberry Pi’s firmware, or whether the kernel in the sd card is involved in anyway, if not, whether the kernel image in the USB that’s booted into must have some certain configuration options enabled. Hopefully not, but someone must give it a try. :slight_smile: If some changes are necessary, we’ll look into updating the kernel Patchbox OS is using.