Login

dmozell · 08-03-2021, 11:57 AM

I'm using Moode with a Raspberry Pi 3B and a Hifiberry DAC+ADC Pro. Sometimes I take it outside on the porch and run it with a battery. It tends to crash and the logs show a power issue. Actually I've had the same crashes plugged in but it happans much more frequently with a battery. I'm using a Charmast 5 volt 3 amp usb battery intended for charging cell phones. The official raspberry power supply is 5.1 volts. Does that 0.1 volt difference matter? Anyone know of a better battery for this purpose? I can't seem to find anything online with better specs. I tried using the same equipment with Volumio (I prefer Moode) and it did the same thing. I've got another pi3b with Hifiberry DAC+ADC Pro running rasbian stretch desktop version with icecast and darkice to transmit anything from my audio system and it never fails (though I've never tried that setup with a battery). There seem to be so many possible factors. Does a Hifiberry hat draw more power than others? Do all audiophile renderers use more power than other types of software.

The bottom line question is: Will I get better results with a different battery and who makes the best battery? Thanks.

**Tim Curtis** · 08-03-2021, 01:04 PM

System crashes are abnormal and typically due to something that is external to moOde software for example bad SDCard, power supply issues, system modifications or 3rd party software installed, other hardware issues, etc.

Reboot and post the Moode startup log.

Code:
moodeutl -l

dmozell

(08-03-2021, 01:04 PM)Tim Curtis Wrote: System crashes are abnormal and typically due to something that is external to moOde software for example bad SDCard, power supply issues, system modifications or 3rd party software installed, other hardware issues, etc.

Reboot and post the Moode startup log.

Code:
moodeutl -l

Code:
pi@moode:~ $

Code:
pi@moode:~ $ moodeutl -l

20210703 072117 worker: -- Start

20210703 072118 worker: Successfully daemonized

20210703 072118 worker: Integrity check (passed)

20210703 072118 worker: Session loaded

20210703 072118 worker: Debug logging (on)

20210703 072118 worker: Device raw: (0ndrpihifiberry|1:empty|i2s:HiFiBerry DAC+)

20210703 072118 worker: Device cfg: (HiFiBerry DAC+|0|0|Digital|0)

20210703 072118 worker: ALSA volume set to (0%)

20210703 072118 worker: -- System

20210703 072120 worker: Host name     (moode)

20210703 072120 worker: moOde release (6.4.2 2020-02-12)

20210703 072120 worker: Raspbian OS   (10.2)

20210703 072120 worker: Linux kernel  (4.19.97-v7+ #1293)

20210703 072120 worker: Platform      (Pi-3B+ 1GB v1.3)

20210703 072120 worker: Architecture  (armv7l)

20210703 072120 worker: MPD version   (0.21.16)

20210703 072120 worker: CPU governor  (ondemand)

20210703 072120 worker: USB boot enabled

20210703 072120 worker: File system not expanded yet

20210703 072121 worker: HDMI port on

20210703 072121 worker: File check (OK)

20210703 072121 worker: -- Network

20210703 072121 worker: eth0 exists

20210703 072121 worker: eth0 wait 0 for IP address

20210703 074605 worker: eth0 wait 1 for IP address

20210703 074608 worker: eth0 wait 2 for IP address

20210703 074612 worker: eth0 wait 3 for IP address

20210703 074615 worker: eth0 wait 4 for IP address

20210703 074618 worker: eth0 address not assigned

20210703 074618 worker: wlan0 exists

20210703 074618 worker: wifi country (US)

20210703 074618 worker: wlan0 trying SSID (FiOS-ADV3E)

20210703 074618 worker: IP addr (192.168.1.190)

20210703 074618 worker: Netmask (255.255.255.0)

20210703 074618 worker: Gateway (192.168.1.1)

20210703 074618 worker: Pri DNS (192.168.1.1)

20210703 074618 worker: Domain  (fios-router.home)

20210703 074619 worker: -- Audio

20210703 074619 worker: ALSA outputs unmuted

20210703 074619 worker: ALSA card number (0)

20210703 074619 worker: Audio output (I2S audio device)

20210703 074619 worker: Audio device (HiFiBerry DAC+)

20210703 074619 worker: Audio formats (S16_LE, S24_LE, S32_LE)

20210703 074619 worker: ALSA mixer name (Digital)

20210703 074619 worker: MPD volume control (software)

20210703 074619 worker: Hdwr volume controller exists

20210703 074619 worker: Max ALSA volume (100%)

20210703 074619 worker: -- Services

20210703 074619 worker: Reset renderer active state

20210703 074620 worker: MPD conf updated

20210703 074620 worker: MPD started

20210703 074620 openMpdSocket(): connection failed (1)

20210703 074620 openMpdSocket(): errorno: 111, Connection refused

20210703 074620 worker: MPD accepting connections

20210703 074620 worker: Configure MPD outputs

20210703 074620 worker: MPD output 1 ALSA default (off)

20210703 074620 worker: MPD output 2 ALSA crossfeed (off)

20210703 074620 worker: MPD output 3 ALSA parametric eq (off)

20210703 074620 worker: MPD output 4 ALSA graphic eq (on)

20210703 074620 worker: MPD output 5 ALSA polarity inversion (off)

20210703 074620 worker: MPD output 6 ALSA bluetooth (off)

20210703 074620 worker: MPD output 7 HTTP stream (off)

20210703 074620 worker: MPD crossfade (off)

20210703 074620 worker: Audio source (Local)

20210703 074620 worker: Output device (Local)

20210703 074621 worker: (/usr/local/bin/shairport-sync -vv -a "Moode Airplay" -- -d alsaequal > /var/log/shairport-sync.log 2>&1 &)

20210703 074621 worker: Airplay receiver started

20210703 074621 worker: UPnP renderer started

20210703 074622 worker: DLNA server started

20210703 074622 worker: Shellinabox SSH started

20210703 074622 worker: USB auto-mounter (udisks-glue)

20210703 074622 worker: -- Music sources

20210703 074622 worker: USB sources (none attached)

20210703 074622 worker: NAS and UPnP sources (none configured)

20210703 074622 worker: -- Miscellaneous

20210703 074622 worker: Saved MPD vol level (0)

20210703 074622 worker: Preamp volume level (0)

20210703 074622 worker: MPD volume level (30) restored

20210703 074623 worker: ALSA volume level (100%)

20210703 074623 worker: Auto-play (On)

20210703 074623 worker: ALSA output (closed)

20210703 074623 worker: Auto-playing id (2)

20210703 074623 worker: ALSA output (closed)

20210703 074623 worker: Auto-shuffle service (Off)

20210703 074623 worker: Maintenance interval (3 hrs)

20210703 074623 worker: Screen saver activation (Never)

20210703 074623 worker: Session permissions (OK)

20210703 074623 worker: Watchdog started

20210703 074623 worker: Ready

pi@moode:~ $ dmesg

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Linux version 4.19.97-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1293 SMP Wed Jan 22 17:10:55 GMT 2020

[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d

[    0.000000] CPU: div instructions available: patching division code

[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3

[    0.000000] Memory policy: Data cache writealloc

[    0.000000] cma: Reserved 8 MiB at 0x3ac00000

[    0.000000] On node 0 totalpages: 242688

[    0.000000]   Normal zone: 2133 pages used for memmap

[    0.000000]   Normal zone: 0 pages reserved

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

[    0.000000] random: get_random_bytes called from start_kernel+0xac/0x4b4 with crng_init=0

[    0.000000] percpu: Embedded 16 pages/cpu s36864 r8192 d20480 u65536

[    0.000000] pcpu-alloc: s36864 r8192 d20480 u65536 alloc=16*4096

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

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

[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:BE:5E5 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  net.ifnames=0 console=ttyS0,115200 console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

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

[    0.000000] Memory: 939076K/970752K available (8192K kernel code, 653K rwdata, 2220K rodata, 1024K init, 822K bss, 23484K reserved, 8192K cma-reserved)

[    0.000000] Virtual kernel memory layout:

                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)

                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)

                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)

                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)

                   modules : 0x7f000000 - 0x80000000   (  16 MB)

                     .text : 0x(ptrval) - 0x(ptrval)   (9184 kB)

                     .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)

                     .data : 0x(ptrval) - 0x(ptrval)   ( 654 kB)

                      .bss : 0x(ptrval) - 0x(ptrval)   ( 823 kB)

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

[    0.000000] ftrace: allocating 26858 entries in 79 pages

[    0.000000] rcu: Hierarchical RCU implementation.

[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16

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

[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns

[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns

[    0.000024] Switching to timer-based delay loop, resolution 52ns

[    0.000288] Console: colour dummy device 80x30

[    0.000913] console [tty1] enabled

[    0.000969] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)

[    0.001012] pid_max: default: 32768 minimum: 301

[    0.001371] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)

[    0.001408] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)

[    0.002373] CPU: Testing write buffer coherency: ok

[    0.002858] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

[    0.003536] Setting up static identity map for 0x100000 - 0x10003c

[    0.003706] rcu: Hierarchical SRCU implementation.

[    0.004523] smp: Bringing up secondary CPUs ...

[    0.005435] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001

[    0.006431] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002

[    0.007347] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003

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

[    0.007554] SMP: Total of 4 processors activated (153.60 BogoMIPS).

[    0.007578] CPU: All CPU(s) started in HYP mode.

[    0.007599] CPU: Virtualization extensions available.

[    0.008589] devtmpfs: initialized

[    0.021936] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4

[    0.022215] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns

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

[    0.022879] pinctrl core: initialized pinctrl subsystem

[    0.023749] NET: Registered protocol family 16

[    0.026778] DMA: preallocated 1024 KiB pool for atomic coherent allocations

[    0.032527] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.

[    0.032563] hw-breakpoint: maximum watchpoint size is 8 bytes.

[    0.032785] Serial: AMBA PL011 UART driver

[    0.035134] bcm2835-mbox 3f00b880.mailbox: mailbox enabled

[    0.050028] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-01-22 17:25, variant start

[    0.060041] raspberrypi-firmware soc:firmware: Firmware hash is 53a54c770c493957d99bf49762dfabc4eee00e45

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

[    0.104914] SCSI subsystem initialized

[    0.105165] usbcore: registered new interface driver usbfs

[    0.105240] usbcore: registered new interface driver hub

[    0.105353] usbcore: registered new device driver usb

[    0.106914] clocksource: Switched to clocksource arch_sys_counter

[    0.196784] VFS: Disk quotas dquot_6.6.0

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

[    0.197100] FS-Cache: Loaded

[    0.197324] CacheFiles: Loaded

[    0.207377] NET: Registered protocol family 2

[    0.208236] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)

[    0.208302] TCP established hash table entries: 8192 (order: 3, 32768 bytes)

[    0.208432] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)

[    0.208637] TCP: Hash tables configured (established 8192 bind 8192)

[    0.208797] UDP hash table entries: 512 (order: 2, 16384 bytes)

[    0.208868] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)

[    0.209130] NET: Registered protocol family 1

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

[    0.209756] RPC: Registered udp transport module.

[    0.209778] RPC: Registered tcp transport module.

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

[    0.211517] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available

[    0.214616] Initialise system trusted keyrings

[    0.214824] workingset: timestamp_bits=14 max_order=18 bucket_order=4

[    0.224658] FS-Cache: Netfs 'nfs' registered for caching

[    0.225255] NFS: Registering the id_resolver key type

[    0.225301] Key type id_resolver registered

[    0.225323] Key type id_legacy registered

[    0.225354] nfs4filelayout_init: NFSv4 File Layout Driver Registering...

[    0.227707] Key type asymmetric registered

[    0.227737] Asymmetric key parser 'x509' registered

[    0.227804] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)

[    0.227992] io scheduler noop registered

[    0.228016] io scheduler deadline registered (default)

[    0.228233] io scheduler cfq registered

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

[    0.228281] io scheduler kyber registered

[    0.230524] bcm2708_fb soc:fb: FB found 1 display(s)

[    0.239910] Console: switching to colour frame buffer device 82x26

[    0.246738] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 656x416

[    0.253506] bcm2835-rng 3f104000.rng: hwrng registered

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

[    0.261544] vc-sm: Videocore shared memory driver

[    0.264310] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000

[    0.280071] brd: module loaded

[    0.292715] loop: module loaded

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

[    0.298977] libphy: Fixed MDIO Bus: probed

[    0.301487] usbcore: registered new interface driver lan78xx

[    0.303942] usbcore: registered new interface driver smsc95xx

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

[    0.336566] dwc_otg 3f980000.usb: base=(ptrval)

[    0.539225] Core Release: 2.80a

[    0.541601] Setting default values for core params

[    0.544045] Finished setting default values for core params

[    0.746789] Using Buffer DMA mode

[    0.749198] Periodic Transfer Interrupt Enhancement - disabled

[    0.751619] Multiprocessor Interrupt Enhancement - disabled

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

[    0.756337] Dedicated Tx FIFOs mode

[    0.759044] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = bad14000 dma = 0xfad14000 len=9024

[    0.763622] FIQ FSM acceleration enabled for :

               Non-periodic Split Transactions

               Periodic Split Transactions

               High-Speed Isochronous Endpoints

               Interrupt/Control Split Transaction hack enabled

[    0.774540] dwc_otg: Microframe scheduler enabled

[    0.774598] WARN::hcd_init_fiq:457: FIQ on core 1

[    0.776829] WARN::hcd_init_fiq:458: FIQ ASM at 8067fbe4 length 36

[    0.779042] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000

[    0.781301] dwc_otg 3f980000.usb: DWC OTG Controller

[    0.783566] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1

[    0.785893] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000

[    0.788221] Init: Port Power? op_state=1

[    0.790463] Init: Power Port (0)

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

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

[    0.799834] usb usb1: Product: DWC OTG Controller

[    0.802200] usb usb1: Manufacturer: Linux 4.19.97-v7+ dwc_otg_hcd

[    0.804625] usb usb1: SerialNumber: 3f980000.usb

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

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

[    0.812648] dwc_otg: FIQ enabled

[    0.812654] dwc_otg: NAK holdoff enabled

[    0.812659] dwc_otg: FIQ split-transaction FSM enabled

[    0.812669] Module dwc_common_port init

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

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

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

[    0.821229] bcm2835-cpufreq: min=600000 max=1400000

[    0.824072] sdhci: Secure Digital Host Controller Interface driver

[    0.826489] sdhci: Copyright© Pierre Ossman

[    0.829311] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe

[    0.832255] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe

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

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

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

[    0.844589] usbcore: registered new interface driver usbhid

[    0.847248] usbhid: USB HID core driver

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

[    0.854693] [vc_sm_connected_init]: start

[    0.863389] [vc_sm_connected_init]: end - returning 0

[    0.866975] Initializing XFRM netlink socket

[    0.869405] NET: Registered protocol family 17

[    0.871909] Key type dns_resolver registered

[    0.874783] Registering SWP/SWPB emulation handler

[    0.877902] registered taskstats version 1

[    0.880308] Loading compiled-in X.509 certificates

[    0.889536] uart-pl011 3f201000.serial: cts_event_workaround enabled

[    0.892067] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2

[    0.898843] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0

[    0.901380] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated

[    0.930058] sdhost: log_buf @ (ptrval) (fad13000)

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

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

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

[    0.978594] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)

[    0.982092] of_cfs_init

[    0.984347] of_cfs_init: OK

[    0.987005] Waiting for root device PARTUUID=6c586e13-02...

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

[    1.037039] Indeed it is in host mode hprt0 = 00021501

[    1.105180] random: fast init done

[    1.122561] mmc0: host does not support reading read-only switch, assuming write-enable

[    1.131011] mmc0: new high speed SDHC card at address aaaa

[    1.135345] mmcblk0: mmc0:aaaa SC32G 29.7 GiB

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

[    1.146016]  mmcblk0: p1 p2

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

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

[    1.246954] usb 1-1: new high-speed USB device number 2 using dwc_otg

[    1.249407] Indeed it is in host mode hprt0 = 00001101

[    1.487216] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3

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

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

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

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

[    1.728232] EXT4-fs (mmcblk0p2): 2 orphan inodes deleted

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

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

[    1.753074] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.

[    1.765525] devtmpfs: mounted

[    1.773100] Freeing unused kernel memory: 1024K

[    1.787298] Run /sbin/init as init process

[    1.816954] usb 1-1.1: new high-speed USB device number 3 using dwc_otg

[    1.947256] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3

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

[    1.956028] hub 1-1.1:1.0: USB hub found

[    1.958856] hub 1-1.1:1.0: 3 ports detected

[    2.314326] dwc_otg_handle_wakeup_detected_intr lxstate = 2

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

[    2.541444] NET: Registered protocol family 10

[    2.545309] Segment Routing with IPv6

[    2.594732] 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)

[    2.603831] systemd[1]: Detected architecture arm.

[    2.635459] systemd[1]: Set hostname to <moode>.

[    2.640626] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument

[    2.837005] usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg

[    2.967511] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00

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

[    3.243790] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed

[    3.250643] libphy: lan78xx-mdiobus: probed

[    3.287178] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64

[    3.346567] systemd[1]: /lib/systemd/system/winbind.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/winbindd.pid → /run/samba/winbindd.pid; please update the unit file accordingly.

[    3.435914] systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.

[    3.484463] systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.

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

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

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

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

[    3.645963] systemd[1]: Created slice system-systemd\x2dfsck.slice.

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

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

[    4.569390] systemd-journald[119]: Received request to flush runtime journal from PID 1

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

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

[    5.271075] bcm2835_vc_sm_cma_probe: Videocore shared memory driver

[    5.271091] [vc_sm_connected_init]: start

[    5.273232] [vc_sm_connected_init]: installed successfully

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

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

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

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

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

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

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

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

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

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

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

[    5.547461] snd-rpi-hifiberry-dacplus socound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry

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

[    5.819841] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

[    5.886094] snd-rpi-hifiberry-dacplus socound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry

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

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

[    5.907959] usbcore: registered new interface driver brcmfmac

[    5.908645] snd-rpi-hifiberry-dacplus socound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry

[    6.099104] random: crng init done

[    6.099121] random: 7 urandom warning(s) missed due to ratelimiting

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

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

[    6.472098] pcm512x 1-004d: Linked as a consumer to regulator.1

[    6.588990] snd-rpi-hifiberry-dacplus socound: pcm512x-hifi <-> 3f203000.i2s mapping ok

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

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

[    8.612025] brcmfmac: power management disabled

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

[    8.898524] 8021q: adding VLAN 0 to HW filter on device eth0

[    9.597070] Under-voltage detected! (0x00050005)

[   12.107043] brcmfmac: brcmf_run_escan: error (-52)

[   12.107055] brcmfmac: brcmf_cfg80211_scan: scan error (-52)

[   13.109906] brcmfmac: brcmf_run_escan: error (-52)

[   13.109918] brcmfmac: brcmf_cfg80211_scan: scan error (-52)

[   14.112771] brcmfmac: brcmf_run_escan: error (-52)

[   14.112783] brcmfmac: brcmf_cfg80211_scan: scan error (-52)

[   15.837033] Voltage normalised (0x00000000)

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

[   30.397058] Under-voltage detected! (0x00050005)

[   34.557113] Voltage normalised (0x00000000)

[   55.357316] Under-voltage detected! (0x00050005)

[   59.517110] Voltage normalised (0x00000000)

[  342.392624] rpi_firmware_get_throttled: 1 callbacks suppressed

[  342.392633] Under-voltage detected! (0x00050005)

[  346.552599] rpi_firmware_get_throttled: 1 callbacks suppressed

[  346.552606] Voltage normalised (0x00000000)

[  487.991461] Under-voltage detected! (0x00050005)

[  494.231161] Voltage normalised (0x00000000)

[  731.352489] Under-voltage detected! (0x00050005)

[  735.512505] Voltage normalised (0x00000000)

[  781.272257] Under-voltage detected! (0x00050005)

[  787.512229] Voltage normalised (0x00000000)

[  804.152142] Under-voltage detected! (0x00050005)

[  808.312038] Voltage normalised (0x00000000)

[ 1087.029838] rpi_firmware_get_throttled: 1 callbacks suppressed

[ 1087.029847] Under-voltage detected! (0x00050005)

[ 1091.189805] rpi_firmware_get_throttled: 1 callbacks suppressed

[ 1091.189813] Voltage normalised (0x00000000)

[ 1134.869409] Under-voltage detected! (0x00050005)

[ 1141.109256] Voltage normalised (0x00000000)

pi@moode:~ $

**Tim Curtis** · 08-03-2021, 01:31 PM

Try a fresh 7.3.0 image.

**TheOldPresbyope** · 08-03-2021, 05:02 PM

Quote:
Code:
... [ 30.397058] Under-voltage detected! (0x00050005) [ 34.557113] Voltage normalised (0x00000000) [ 55.357316] Under-voltage detected! (0x00050005) [ 59.517110] Voltage normalised (0x00000000) [ 342.392624] rpi_firmware_get_throttled: 1 callbacks suppressed [ 342.392633] Under-voltage detected! (0x00050005) [ 346.552599] rpi_firmware_get_throttled: 1 callbacks suppressed [ 346.552606] Voltage normalised (0x00000000) [ 487.991461] Under-voltage detected! (0x00050005) [ 494.231161] Voltage normalised (0x00000000) [ 731.352489] Under-voltage detected! (0x00050005) [ 735.512505] Voltage normalised (0x00000000) [ 781.272257] Under-voltage detected! (0x00050005) [ 787.512229] Voltage normalised (0x00000000) [ 804.152142] Under-voltage detected! (0x00050005) [ 808.312038] Voltage normalised (0x00000000) [ 1087.029838] rpi_firmware_get_throttled: 1 callbacks suppressed [ 1087.029847] Under-voltage detected! (0x00050005) [ 1091.189805] rpi_firmware_get_throttled: 1 callbacks suppressed [ 1091.189813] Voltage normalised (0x00000000) [ 1134.869409] Under-voltage detected! (0x00050005) [ 1141.109256] Voltage normalised (0x00000000) ...

For sure the RPi isn't happy with its power source. I'd be surprised if an up-to-date moOde install would change this but I've been known to be wrong before Tongue

In addition to the usual voltage/current numbers published for rechargeable batteries, one has to know the battery is a "stiff" power source, e.g., the voltage doesn't droop with high current draw. Some are; some aren't.

Then there's the USB cable between the battery and the RPi. It should be short and have adequately sized conductors so the voltage drop with high current draw is manageable.

Regards,
Kent

JonPike · (This post was last modified: 08-04-2021, 07:12 AM by JonPike.)

Yep, the dmesg log is the way to see those undervolt events. I know that (at least some of the Pi versions) the power LED is supposed to flash or change color, but I swear there have been times I haven't seen that, and then there were lots of u-v events in the log.

I have had cables be the culprit, with an otherwise OK power supply, on several occasions. You want one with heavier wires, there are some amazingly thin ones out there, though this isn't often documented. Try ones that say they're for charging rather than just data. If they document that... A cheap, super thin wire cable will have more drop, as TOP has said, and with enough drop your voltage goes too low. A "5.1V" vs a "5V" would give you another tenth of a volt to lose over a cable, so that would be leeway. If the supply is doing that.

For testing, try the following. It might be worth trying to create as much load as you can, run high bitrate radio, turn on resampling to high bit and data rates, maybe other CPU using features, for a worst case current draw. Then try swapping different cables in and out, and reading the log for undervolt events. That's the quickest, easiest thing to do.
Then try swapping the supplies, with a known "better" cable. Standard process of elimination process. Hopefully you end up with at least 2 good cables, throw away a few bad ones, and find both supplies worthy.

Interesting note on the "5.1V" battery. There is no such thing as a 5.1V battery. All "batteries" that provide a USB compatible voltage are batteries
(usually single cell Lithium at 3.6V or therabouts) with a switching power supply to bring it up to 5 or 5.1V. So, you're actually at the mercy of the switcher supply in the battery pack, as to stiffness under load. If well designed, that would be better than a raw battery. I'd normally ask if you had a decent meter to measure the voltage, but it's difficult on USB systems, since it's hard to measure at the connectors unless you make an adapter tap cable or something, and probing on the Pi happens to be very hazardous, in that the convenient spots near the connector happen to be very near places to blow out stuff if you slip. (Don't ask me how I know!!) Be careful if you try that.

An aside about these USB "Batteries". This makes me giggle a bit, as a hardware electronics guy, about people hoping for better "audiophile" effects of running off a battery, but using one of these USB supply packs. An actual battery is a pretty low noise power supply, if that's going to be important. USB battery paks invariably have a dreaded switcher, probably built cheap by some mega producer? Hmmm... you might be better off with that phone charger. Or, maybe your modern Hat designer did enough with a decent design, and it rejects normal noisy USB power, and the "audiophile" needs are satisfied with either?

You just need a well regulated supply that won't sag under your load. And a solid, low resistance cable that won't drop too much getting it there.

dmozell · (This post was last modified: 08-05-2021, 09:22 PM by dmozell.)

(08-03-2021, 05:02 PM)TheOldPresbyope Wrote:
Quote:
Code:
... [ 30.397058] Under-voltage detected! (0x00050005) [ 34.557113] Voltage normalised (0x00000000) [ 55.357316] Under-voltage detected! (0x00050005) [ 59.517110] Voltage normalised (0x00000000) [ 342.392624] rpi_firmware_get_throttled: 1 callbacks suppressed [ 342.392633] Under-voltage detected! (0x00050005) [ 346.552599] rpi_firmware_get_throttled: 1 callbacks suppressed [ 346.552606] Voltage normalised (0x00000000) [ 487.991461] Under-voltage detected! (0x00050005) [ 494.231161] Voltage normalised (0x00000000) [ 731.352489] Under-voltage detected! (0x00050005) [ 735.512505] Voltage normalised (0x00000000) [ 781.272257] Under-voltage detected! (0x00050005) [ 787.512229] Voltage normalised (0x00000000) [ 804.152142] Under-voltage detected! (0x00050005) [ 808.312038] Voltage normalised (0x00000000) [ 1087.029838] rpi_firmware_get_throttled: 1 callbacks suppressed [ 1087.029847] Under-voltage detected! (0x00050005) [ 1091.189805] rpi_firmware_get_throttled: 1 callbacks suppressed [ 1091.189813] Voltage normalised (0x00000000) [ 1134.869409] Under-voltage detected! (0x00050005) [ 1141.109256] Voltage normalised (0x00000000) ...

For sure the RPi isn't happy with its power source. I'd be surprised if an up-to-date moOde install would change this but I've been known to be wrong before

In addition to the usual voltage/current numbers published for rechargeable batteries, one has to know the battery is a "stiff" power source, e.g., the voltage doesn't droop with high current draw. Some are; some aren't.

Then there's the USB cable between the battery and the RPi. It should be short and have adequately sized conductors so the voltage drop with high current draw is manageable.

Regards,
Kent

Thanks to Tim and Kent for your replies. I've done many experiments with different power supplies, (The point of the battery was only to use on my porch where the nearest outlet is inconvenient), different sd cards and fresh installs. Did this with Moode and Volumio. My concclusion is that I actually was using a problem raspberry! I changed to a different one and everything has been running continuously with any power source.

dmozell · (This post was last modified: 08-05-2021, 09:22 PM by dmozell.)

(08-04-2021, 07:03 AM)Thanks to Tim,Kent and Jon for your replies. I\ve done many experiments with different power supplies, (The point of the battery was only to use on my porch where the nearest outlet is inconvenient), different sd cards and fresh installs. Did this with Moode and Volumio. My conclusion is that I actually was using a problem raspberry! I changed to a different one and everything has been running continuously with any power source. JonPike Wrote: Yep, the dmesg log is the way to see those undervolt events. I know that (at least some of the Pi versions) the power LED is supposed to flash or change color, but I swear there have been times I haven't seen that, and then there were lots of u-v events in the log.

I have had cables be the culprit, with an otherwise OK power supply, on several occasions. You want one with heavier wires, there are some amazingly thin ones out there, though this isn't often documented. Try ones that say they're for charging rather than just data. If they document that... A cheap, super thin wire cable will have more drop, as TOP has said, and with enough drop your voltage goes too low. A "5.1V" vs a "5V" would give you another tenth of a volt to lose over a cable, so that would be leeway. If the supply is doing that.

For testing, try the following. It might be worth trying to create as much load as you can, run high bitrate radio, turn on resampling to high bit and data rates, maybe other CPU using features, for a worst case current draw. Then try swapping different cables in and out, and reading the log for undervolt events. That's the quickest, easiest thing to do.
Then try swapping the supplies, with a known "better" cable. Standard process of elimination process. Hopefully you end up with at least 2 good cables, throw away a few bad ones, and find both supplies worthy.

Interesting note on the "5.1V" battery. There is no such thing as a 5.1V battery. All "batteries" that provide a USB compatible voltage are batteries
(usually single cell Lithium at 3.6V or therabouts) with a switching power supply to bring it up to 5 or 5.1V. So, you're actually at the mercy of the switcher supply in the battery pack, as to stiffness under load. If well designed, that would be better than a raw battery. I'd normally ask if you had a decent meter to measure the voltage, but it's difficult on USB systems, since it's hard to measure at the connectors unless you make an adapter tap cable or something, and probing on the Pi happens to be very hazardous, in that the convenient spots near the connector happen to be very near places to blow out stuff if you slip. (Don't ask me how I know!!) Be careful if you try that.

An aside about these USB "Batteries". This makes me giggle a bit, as a hardware electronics guy, about people hoping for better "audiophile" effects of running off a battery, but using one of these USB supply packs. An actual battery is a pretty low noise power supply, if that's going to be important. USB battery paks invariably have a dreaded switcher, probably built cheap by some mega producer? Hmmm... you might be better off with that phone charger. Or, maybe your modern Hat designer did enough with a decent design, and it rejects normal noisy USB power, and the "audiophile" needs are satisfied with either?

You just need a well regulated supply that won't sag under your load. And a solid, low resistance cable that won't drop too much getting it there.

Wheel_nut · 08-05-2021, 10:39 PM

@dmozell - A very good discussion on the pitfalls in powering low voltage devices especially in the context of the current practice of powering devices from USB 5v supplies.

I have encountered problems with USB Cables for several years now, ever since the supply requirement went up to 2.1Amps. I have given up on trying to buy USB cables to use in Charging or Power Supply applications and now treasure my accumulated collection of cables that came with original equipment.

I have disected many cables and have discovered that most of the cable is NOT Copper but CCA (Copper Clad Aluminium)! This is ductile enough to be drawn into very fine and then stranded wire which is usually crimped at the ends. This is even more common in Cat5 and Cat6 patch cables with IDC terminations. Whereas it is possible to solder CCA wire, you have to be careful not to scrape the conductors because if you do, it will expose the Aluminium core which oxidises to a black mess when it comes in contact with activated Flux. Having said that, I have managed succesfully to solder CCA by carefully stripping the insulation and soldering very quickly with a good Rosin cored Solder.

As an aside, If you examine the connections from the incoming BT Cable to your Master Socket, you will probably find that the incoming Pair is crimped using "Jelly" (Gel filled) Crimps to a short pair od tail befor connection to the Master Socket A & B Terminals. I believe this to be because BT installed a lot of Aluminium cable in the 70's and 80's which corrodes very quickly when in contact with other metals and moisture.

Login
Username:
Password:	Lost Password?
	Remember me