search

MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.78k stars 494 forks source link

DietPi-Config | RPi 3 B+: Disabling WiFi breaks Bluetooth as well #4512

Closed BelgarionNL closed 2 years ago

BelgarionNL commented 3 years ago

Details:

Bug report | N/A
DietPi version | latest stable and beta 7.3
Img creator | DietPi Core Team
SBC device | RPi 3 Model B+ (armv7l) (index=3)
Kernel version | 
Linux DietPi 5.10.17-v7+ #1421 SMP Thu May 27 13:59:01 BST 2021 armv7l

GNU/Linux

Steps to reproduce:

Install dietpi image enable bluetooth in dietpi-config and then nada.

Expected behaviour:

Bluetooth should be working?

Actual behaviour:

Bluetooth does not work

Extra details:

Running the command systemctl start hciuart fails
Tried to disable/enable Bluetooth from the dietpi-software menu, no change

Additional logs:

root@dietpi-woonkamer:~# journalctl -u hciuart
-- Logs begin at Fri 2021-06-25 09:57:19 CEST, end at Fri 2021-06-25 09:58:02 CEST. --
Jun 25 09:57:22 dietpi-woonkamer systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jun 25 09:58:02 dietpi-woonkamer btuart[209]: Initialization timed out.
Jun 25 09:58:02 dietpi-woonkamer btuart[209]: bcm43xx_init
Jun 25 09:58:02 dietpi-woonkamer systemd[1]: hciuart.service: Control process ex
ited, code=exited, status=1/FAILURE
Jun 25 09:58:02 dietpi-woonkamer systemd[1]: hciuart.service: Failed with result
 'exit-code'.
Jun 25 09:58:02 dietpi-woonkamer systemd[1]: Failed to start Configure Bluetooth
 Modems connected by UART.
BelgarionNL commented 3 years ago

similar to this:

https://github.com/MichaIng/DietPi/issues/3018 https://github.com/MichaIng/DietPi/issues/4060 ah seems to be a recurring theme it seems: https://github.com/RPi-Distro/pi-bluetooth/issues/25

and it seems to work fine on raspbian lite image...

UPDATE: seems to work on the 7.3 beta branch but then I did a reboot and it stopped working again.

for now I will just have to use raspbian lite... Please tell me how I should enable bluetooth etc in dietpi.

I think it has something to do with the UART setting in dietpi-config but I didnt change it.

MichaIng commented 3 years ago

Many thanks for your report.

Bluetooth on Raspberry Pi can fail for various reasons, so you'll always find many of those reports on all distros šŸ˜‰.

You had a very old DietPi version when doing the report and the image is a Stretch image (not a new one as stated in the header) with a very strange kernel signature:

Letsencrypt supports Free Noip.com Dynamic DNS #1159 SMP Sun Nov 4 17:50:20 GMT 2018
Distro | stretch (index=4)

Where did you get this image from, and is the first line above really the output of uname -a?

BelgarionNL commented 3 years ago

I got the latest version from your website. tried both the stable and beta 7.3

I copied the layout from another similar bug report so perhaps I forgot to change it :)

nevertheless simply get a fresh install of the latest dietpi and use it with a rpi3b+ I only have those free). and bluetooth will fail after updating everything and configuring the basics like hostname.

Joulinar commented 3 years ago

Can you share uname -a pls. So we know what you are running

BelgarionNL commented 3 years ago

Linux DietPi 5.10.17-v7+ #1421 SMP Thu May 27 13:59:01 BST 2021 armv7l GNU/Linux

BelgarionNL commented 3 years ago

image

I think something is going wrong here because before the reboot I had 3 options :D

MichaIng commented 3 years ago

Ah, there it is: The serial console on ttyAMA0 needs to be disabled, as this is used for Bluetooth. If you need a serial console/device for other purpose, use ttyS0 (mini UART) for this. Toggle the device selector to [On], then reboot, and it becomes available to toggle the console on it.

BelgarionNL commented 3 years ago

image image image

These settings I Just did on a new install.

login as root, run through the installer with default recommended settings. then enable bluetooth and reboot.

and then it does not work?

image

BelgarionNL commented 3 years ago

Just going to document all my steps so you guys can point to my mistake :)

image image image image image

Just checking here, not changing anything: image image image image

Now it works:

image

AFTER REBOOT IT NO LONGER WORKS.

image

BelgarionNL commented 3 years ago
Logfile attached. Click to expand! ``` root@DietPi:~# journalctl -xe -- Logs begin at Sat 2021-06-26 14:25:16 BST, end at Sat 2021-06-26 15:39:42 BST . -- Jun 26 14:25:16 DietPi kernel: Booting Linux on physical CPU 0x0 Jun 26 14:25:16 DietPi kernel: Linux version 5.10.17-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1421 SMP Thu May 27 13:59:01 BST 2021 Jun 26 14:25:16 DietPi kernel: CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7 ), cr=10c5383d Jun 26 14:25:16 DietPi kernel: CPU: div instructions available: patching divisio n code Jun 26 14:25:16 DietPi kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT ali asing instruction cache Jun 26 14:25:16 DietPi kernel: OF: fdt: Machine model: Raspberry Pi 3 Model B Pl us Rev 1.3 Jun 26 14:25:16 DietPi kernel: Memory policy: Data cache writealloc Jun 26 14:25:16 DietPi kernel: Reserved memory: created CMA memory pool at 0x3a4 00000, size 64 MiB Jun 26 14:25:16 DietPi kernel: OF: reserved mem: initialized node linux,cma, com patible id shared-dma-pool Jun 26 14:25:16 DietPi kernel: Zone ranges: Jun 26 14:25:16 DietPi kernel: DMA [mem 0x0000000000000000-0x000000003e5f ffff] Jun 26 14:25:16 DietPi kernel: Normal empty Jun 26 14:25:16 DietPi kernel: Movable zone start for each node Jun 26 14:25:16 DietPi kernel: Early memory node ranges Jun 26 14:25:16 DietPi kernel: node 0: [mem 0x0000000000000000-0x000000003e5 fffff] Jun 26 14:25:16 DietPi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x00 0000003e5fffff] Jun 26 14:25:16 DietPi kernel: On node 0 totalpages: 255 488 Jun 26 14:25:16 DietPi kernel: DMA zone: 2246 pages us ed for memmap Jun 26 14:25:16 DietPi kernel: DMA zone: 0 pages reser ved Jun 26 14:25:16 DietPi kernel: DMA zone: 255488 pages, LIFO batch:63 Jun 26 14:25:16 DietPi kernel: percpu: Embedded 20 pages/cpu s50700 r8192 d23028 u81920 Jun 26 14:25:16 DietPi kernel: pcpu-alloc: s50700 r8192 d23028 u81920 alloc=20*4096 Jun 26 14:25:16 DietPi kernel: pcpu-alloc: [0] 0 [0] 1 [ 0] 2 [0] 3 Jun 26 14:25:16 DietPi kernel: Built 1 zonelists, mobility grouping on. Total p ages: 253242 Jun 26 14:25:16 DietPi kernel: Kernel command line: cohe rent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable _hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm 2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console= tty1 root=PARTUUID=9730496b-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet net.ifnames=0 Jun 26 14:25:16 DietPi kernel: Kernel parameter elevator = does not have any effect anymore. Please use sysfs to set IO scheduler for individual devices. Jun 26 14:25:16 DietPi kernel: Dentry cache hash table entries: 131072 (order: 7 , 524288 bytes, linear) Jun 26 14:25:16 DietPi kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) Jun 26 14:25:16 DietPi kernel: mem auto-init: stack:off, heap alloc:off, heap fr ee:off Jun 26 14:25:16 DietPi kernel: Memory: 930564K/1021952K available (9216K kernel code, 1311K rwdata, 2940K rodata, 1024K init, 860K bss, 25852K reserved, 65536K cma-reserved) Jun 26 14:25:16 DietPi kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4 , Nodes=1 Jun 26 14:25:16 DietPi kernel: ftrace: allocating 31910 entries in 63 pages Jun 26 14:25:16 DietPi kernel: ftrace: allocated 63 pages with 6 groups Jun 26 14:25:16 DietPi kernel: rcu: Hierarchical RCU implementation. Jun 26 14:25:16 DietPi kernel: Rude variant of Tasks RCU enabled. Jun 26 14:25:16 DietPi kernel: Tracing variant of Tasks RCU enabled. Jun 26 14:25:16 DietPi kernel: rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. Jun 26 14:25:16 DietPi kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 Jun 26 14:25:16 DietPi kernel: random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=0 Jun 26 14:25:16 DietPi kernel: arch_timer: cp15 timer(s) running at 19.20MHz (ph ys). Jun 26 14:25:16 DietPi kernel: clocksource: arch_sys_counter: mask: 0xffffffffff ffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns Jun 26 14:25:16 DietPi kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, w raps every 4398046511078ns Jun 26 14:25:16 DietPi kernel: Switching to timer-based delay loop, resolution 5 2ns Jun 26 14:25:16 DietPi kernel: Console: colour dummy device 80x30 Jun 26 14:25:16 DietPi kernel: printk: console [tty1] enabled Jun 26 14:25:16 DietPi kernel: Calibrating delay loop (skipped), value calculate d using timer frequency.. 38.40 BogoMIPS (lpj=192000) Jun 26 14:25:16 DietPi kernel: pid_max: default: 32768 minimum: 301 Jun 26 14:25:16 DietPi kernel: LSM: Security Framework initializing Jun 26 14:25:16 DietPi kernel: Mount-cache hash table entries: 2048 (order: 1, 8 192 bytes, linear) Jun 26 14:25:16 DietPi kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Jun 26 14:25:16 DietPi kernel: Disabling memory control group subsystem Jun 26 14:25:16 DietPi kernel: CPU: Testing write buffer coherency: ok Jun 26 14:25:16 DietPi kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Jun 26 14:25:16 DietPi kernel: Setting up static identity map for 0x100000 - 0x1 0003c Jun 26 14:25:16 DietPi kernel: rcu: Hierarchical SRCU implementation. Jun 26 14:25:16 DietPi kernel: smp: Bringing up secondary CPUs ... Jun 26 14:25:16 DietPi kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 Jun 26 14:25:16 DietPi kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 Jun 26 14:25:16 DietPi kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Jun 26 14:25:16 DietPi kernel: smp: Brought up 1 node, 4 CPUs Jun 26 14:25:16 DietPi kernel: SMP: Total of 4 processors activated (153.60 Bogo MIPS). Jun 26 14:25:16 DietPi kernel: CPU: All CPU(s) started in HYP mode. Jun 26 14:25:16 DietPi kernel: CPU: Virtualization extensions available. Jun 26 14:25:16 DietPi kernel: devtmpfs: initialized Jun 26 14:25:16 DietPi kernel: VFP support v0.3: implementor 41 architecture 3 p art 40 variant 3 rev 4 Jun 26 14:25:16 DietPi kernel: clocksource: jiffies: mask: 0xffffffff max_cycles : 0xffffffff, max_idle_ns: 19112604462750000 ns Jun 26 14:25:16 DietPi kernel: futex hash table entries: 1024 (order: 4, 65536 b ytes, linear) Jun 26 14:25:16 DietPi kernel: pinctrl core: initialized pinctrl subsystem Jun 26 14:25:16 DietPi kernel: NET: Registered protocol family 16 Jun 26 14:25:16 DietPi kernel: DMA: preallocated 1024 KiB pool for atomic cohere nt allocations Jun 26 14:25:16 DietPi kernel: audit: initializing netlink subsys (disabled) Jun 26 14:25:16 DietPi kernel: audit: type=2000 audit(0. 010:1): state=initialized audit_enabled=0 res=1 Jun 26 14:25:16 DietPi kernel: thermal_sys: Registered thermal governor 'step_wi se' Jun 26 14:25:16 DietPi kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint a nd 4 watchpoint registers. Jun 26 14:25:16 DietPi kernel: hw-breakpoint: maximum watchpoint size is 8 bytes . Jun 26 14:25:16 DietPi kernel: Serial: AMBA PL011 UART driver Jun 26 14:25:16 DietPi kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled Jun 26 14:25:16 DietPi kernel: raspberrypi-firmware soc:firmware: Attached to fi rmware from 2021-05-27T14:04:46, variant start_cd Jun 26 14:25:16 DietPi kernel: raspberrypi-firmware soc:firmware: Firmware hash is 7d9a298cda813f747b51fe17e1e417e7bf5ca94d Jun 26 14:25:16 DietPi kernel: bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1 Jun 26 14:25:16 DietPi kernel: SCSI subsystem initialize d Jun 26 14:25:16 DietPi kernel: usbcore: registered new interface driver usbfs Jun 26 14:25:16 DietPi kernel: usbcore: registered new interface driver hub Jun 26 14:25:16 DietPi kernel: usbcore: registered new device driver usb Jun 26 14:25:16 DietPi kernel: clocksource: Switched to clocksource arch_sys_cou nter Jun 26 14:25:16 DietPi kernel: VFS: Disk quotas dquot_6. 6.0 Jun 26 14:25:16 DietPi kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Jun 26 14:25:16 DietPi kernel: FS-Cache: Loaded Jun 26 14:25:16 DietPi kernel: CacheFiles: Loaded Jun 26 14:25:16 DietPi kernel: NET: Registered protocol family 2 Jun 26 14:25:16 DietPi kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) Jun 26 14:25:16 DietPi kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) Jun 26 14:25:16 DietPi kernel: TCP bind hash table entries: 8192 (order: 4, 6553 6 bytes, linear) Jun 26 14:25:16 DietPi kernel: TCP: Hash tables configured (established 8192 bin d 8192) Jun 26 14:25:16 DietPi kernel: UDP hash table entries: 512 (order: 2, 16384 byte s, linear) Jun 26 14:25:16 DietPi kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) Jun 26 14:25:16 DietPi kernel: NET: Registered protocol family 1 Jun 26 14:25:16 DietPi kernel: RPC: Registered named UNIX socket transport modul e. Jun 26 14:25:16 DietPi kernel: RPC: Registered udp transport module. Jun 26 14:25:16 DietPi kernel: RPC: Registered tcp transport module. Jun 26 14:25:16 DietPi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jun 26 14:25:16 DietPi kernel: hw perfevents: enabled with armv7_cortex_a7 PMU d river, 7 counters available Jun 26 14:25:16 DietPi kernel: Initialise system trusted keyrings Jun 26 14:25:16 DietPi kernel: workingset: timestamp_bits=14 max_order=18 bucket _order=4 Jun 26 14:25:16 DietPi kernel: zbud: loaded Jun 26 14:25:16 DietPi kernel: FS-Cache: Netfs 'nfs' reg istered for caching Jun 26 14:25:16 DietPi kernel: NFS: Registering the id_r esolver key type Jun 26 14:25:16 DietPi kernel: Key type id_resolver regi stered-- Jun 26 14:25:16 DietPi kernel: Key type id_legacy regist ered Jun 26 14:25:16 DietPi kernel: nfs4filelayout_init: NFSv4 File Layout Driver Reg istering... Jun 26 14:25:16 DietPi kernel: Key type asymmetric regis terede-- Jun 26 14:25:16 DietPi kernel: Asymmetric key parser 'x5 09' registered Jun 26 14:25:16 DietPi kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) Jun 26 14:25:16 DietPi kernel: io scheduler mq-deadline registered Jun 26 14:25:16 DietPi kernel: io scheduler kyber registered Jun 26 14:25:16 DietPi kernel: bcm2708_fb soc:fb: FB found 1 display(s) Jun 26 14:25:16 DietPi kernel: Console: switching to colour frame buffer device 90x30 Jun 26 14:25:16 DietPi kernel: bcm2708_fb soc:fb: Registered framebuffer for dis play 0, size 720x480 Jun 26 14:25:16 DietPi kernel: bcm2835-rng 3f104000.rng: hwrng registered Jun 26 14:25:16 DietPi kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3f000000 mem_size:0x3f600000(1014 MiB) Jun 26 14:25:16 DietPi kernel: gpiomem-bcm2835 3f200000.gpiomem: Initialised: Re gisters at 0x3f200000 Jun 26 14:25:16 DietPi kernel: brd: module loaded Jun 26 14:25:16 DietPi kernel: loop: module loaded Jun 26 14:25:16 DietPi kernel: Loading iSCSI transport class v2.0-870. Jun 26 14:25:16 DietPi kernel: libphy: Fixed MDIO Bus: probed Jun 26 14:25:16 DietPi kernel: usbcore: registered new interface driver lan78xx Jun 26 14:25:16 DietPi kernel: usbcore: registered new interface driver smsc95xx Jun 26 14:25:16 DietPi kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Jun 26 14:25:16 DietPi kernel: Core Release: 2.80a Jun 26 14:25:16 DietPi kernel: Setting default values fo r core params Jun 26 14:25:16 DietPi kernel: Finished setting default values for core params Jun 26 14:25:16 DietPi kernel: Using Buffer DMA mode Jun 26 14:25:16 DietPi kernel: Periodic Transfer Interru pt Enhancement - disabled Jun 26 14:25:16 DietPi kernel: Multiprocessor Interrupt Enhancement - disabled Jun 26 14:25:16 DietPi kernel: OTG VER PARAM: 0, OTG VER FLAG: 0 Jun 26 14:25:16 DietPi kernel: Dedicated Tx FIFOs mode m Jun 26 14:25:16 DietPi kernel: Jun 26 14:25:16 DietPi kernel: WARN::dwc_otg_hcd_init:10 74: FIQ DMA bounce buffers: virt = ba514000 dma = 0xfa514000 len=9024 Jun 26 14:25:16 DietPi kernel: FIQ FSM acceleration enab led for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled- Jun 26 14:25:16 DietPi kernel: dwc_otg: Microframe sched uler enabled Jun 26 14:25:16 DietPi kernel: Jun 26 14:25:16 DietPi kernel: WARN::hcd_init_fiq:457: F IQ on core 1 Jun 26 14:25:16 DietPi kernel: Jun 26 14:25:16 DietPi kernel: WARN::hcd_init_fiq:458: F IQ ASM at 807be568 length 36 Jun 26 14:25:16 DietPi kernel: Jun 26 14:25:16 DietPi kernel: WARN::hcd_init_fiq:497: M PHI regs_base at be810000 Jun 26 14:25:16 DietPi kernel: dwc_otg 3f980000.usb: DWC OTG Controller Jun 26 14:25:16 DietPi kernel: dwc_otg 3f980000.usb: new USB bus registered, ass igned bus number 1 Jun 26 14:25:16 DietPi kernel: dwc_otg 3f980000.usb: irq 89, io mem 0x00000000 Jun 26 14:25:16 DietPi kernel: Init: Port Power? op_stat e=1 Jun 26 14:25:16 DietPi kernel: Init: Power Port (0) Jun 26 14:25:16 DietPi kernel: usb usb1: New USB device found, idVendor=1d6b, id Product=0002, bcdDevice= 5.10 Jun 26 14:25:16 DietPi kernel: usb usb1: New USB device strings: Mfr=3, Product= 2, SerialNumber=1 Jun 26 14:25:16 DietPi kernel: usb usb1: Product: DWC OTG Controller Jun 26 14:25:16 DietPi kernel: usb usb1: Manufacturer: Linux 5.10.17-v7+ dwc_otg _hcd Jun 26 14:25:16 DietPi kernel: usb usb1: SerialNumber: 3f980000.usb Jun 26 14:25:16 DietPi kernel: hub 1-0:1.0: USB hub found Jun 26 14:25:16 DietPi kernel: hub 1-0:1.0: 1 port detected Jun 26 14:25:16 DietPi kernel: dwc_otg: FIQ enabled Jun 26 14:25:16 DietPi kernel: dwc_otg: NAK holdoff enab led Jun 26 14:25:16 DietPi kernel: dwc_otg: FIQ split-transa ction FSM enabled Jun 26 14:25:16 DietPi kernel: Module dwc_common_port in it Jun 26 14:25:16 DietPi kernel: usbcore: registered new interface driver usb-stor age Jun 26 14:25:16 DietPi kernel: mousedev: PS/2 mouse device common for all mice Jun 26 14:25:16 DietPi kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdo g timer Jun 26 14:25:16 DietPi kernel: sdhci: Secure Digital Host Controller Interface d river Jun 26 14:25:16 DietPi kernel: sdhci: Copyright(c) Pierre Ossman Jun 26 14:25:16 DietPi kernel: sdhost-bcm2835 3f202000.mmc: could not get clk, d eferring probe Jun 26 14:25:16 DietPi kernel: sdhci-pltfm: SDHCI platform and OF driver helper Jun 26 14:25:16 DietPi kernel: ledtrig-cpu: registered to indicate activity on C PUs Jun 26 14:25:16 DietPi kernel: hid: raw HID events driver (C) Jiri Kosina Jun 26 14:25:16 DietPi kernel: usbcore: registered new interface driver usbhid Jun 26 14:25:16 DietPi kernel: usbhid: USB HID core driver Jun 26 14:25:16 DietPi kernel: Initializing XFRM netlink socket Jun 26 14:25:16 DietPi kernel: NET: Registered protocol family 17 Jun 26 14:25:16 DietPi kernel: Key type dns_resolver reg istered- Jun 26 14:25:16 DietPi kernel: Registering SWP/SWPB emul ation handler Jun 26 14:25:16 DietPi kernel: registered taskstats version 1 Jun 26 14:25:16 DietPi kernel: Loading compiled-in X.509 certificates Jun 26 14:25:16 DietPi kernel: Key type ._fscrypt regist ered Jun 26 14:25:16 DietPi kernel: Key type .fscrypt registe red Jun 26 14:25:16 DietPi kernel: Key type fscrypt-provisio ning registered Jun 26 14:25:16 DietPi kernel: uart-pl011 3f201000.serial: cts_event_workaround enabled Jun 26 14:25:16 DietPi kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2 Jun 26 14:25:16 DietPi kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 pow er domains driver Jun 26 14:25:16 DietPi kernel: sdhost: log_buf @ (ptrval) (fa513000) Jun 26 14:25:16 DietPi kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) Jun 26 14:25:16 DietPi kernel: of_cfs_init Jun 26 14:25:16 DietPi kernel: of_cfs_init: OK Jun 26 14:25:16 DietPi kernel: Waiting for root device PARTUUID=9730496b-02... Jun 26 14:25:16 DietPi kernel: mmc0: host does not suppo rt reading read-only switch, assuming write-enable Jun 26 14:25:16 DietPi kernel: mmc0: new high speed SDHC card at address aaaa Jun 26 14:25:16 DietPi kernel: mmcblk0: mmc0:aaaa SC32G 29.7 GiB Jun 26 14:25:16 DietPi kernel: mmcblk0: p1 p2 Jun 26 14:25:16 DietPi kernel: EXT4-fs (mmcblk0p2): mounted filesystem with orde red data mode. Opts: (null) Jun 26 14:25:16 DietPi kernel: VFS: Mounted root (ext4 filesystem) readonly on d evice 179:2. Jun 26 14:25:16 DietPi kernel: devtmpfs: mounted Jun 26 14:25:16 DietPi kernel: Freeing unused kernel memory: 1024K Jun 26 14:25:16 DietPi kernel: Indeed it is in host mode hprt0 = 00021501 Jun 26 14:25:16 DietPi kernel: Run /sbin/init as init process Jun 26 14:25:16 DietPi kernel: with arguments: Jun 26 14:25:16 DietPi kernel: /sbin/init Jun 26 14:25:16 DietPi kernel: with environment: Jun 26 14:25:16 DietPi kernel: HOME=/ Jun 26 14:25:16 DietPi kernel: TERM=linux Jun 26 14:25:16 DietPi kernel: random: fast init done Jun 26 14:25:16 DietPi kernel: usb 1-1: new high-speed USB device number 2 using dwc_otg Jun 26 14:25:16 DietPi kernel: Indeed it is in host mode hprt0 = 00001101 Jun 26 14:25:16 DietPi kernel: usb 1-1: New USB device found, idVendor=0424, idP roduct=2514, bcdDevice= b.b3 Jun 26 14:25:16 DietPi kernel: usb 1-1: New USB device strings: Mfr=0, Product=0 , SerialNumber=0 Jun 26 14:25:16 DietPi kernel: hub 1-1:1.0: USB hub found Jun 26 14:25:16 DietPi kernel: hub 1-1:1.0: 4 ports detected Jun 26 14:25:16 DietPi systemd[1]: System time before build time, advancing cloc k. Jun 26 14:25:16 DietPi kernel: NET: Registered protocol family 10 Jun 26 14:25:16 DietPi kernel: Segment Routing with IPv6 Jun 26 14:25:16 DietPi systemd[1]: systemd 241 running in system mode. (+PAM +AU DIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTL S +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierar chy=hybrid) Jun 26 14:25:16 DietPi systemd[1]: Detected architecture arm. Jun 26 14:25:16 DietPi kernel: usb 1-1.1: new high-speed USB device number 3 usi ng dwc_otg Jun 26 14:25:16 DietPi systemd[1]: Set hostname to . Jun 26 14:25:16 DietPi kernel: usb 1-1.1: New USB device found, idVendor=0424, i dProduct=2514, bcdDevice= b.b3 Jun 26 14:25:16 DietPi kernel: usb 1-1.1: New USB device strings: Mfr=0, Product =0, SerialNumber=0 Jun 26 14:25:16 DietPi kernel: hub 1-1.1:1.0: USB hub found Jun 26 14:25:16 DietPi kernel: hub 1-1.1:1.0: 3 ports detected Jun 26 14:25:16 DietPi kernel: random: systemd: uninitia lized urandom read (16 bytes read) Jun 26 14:25:16 DietPi kernel: random: systemd: uninitia lized urandom read (16 bytes read) Jun 26 14:25:16 DietPi systemd[1]: Listening on udev Control Socket. Jun 26 14:25:16 DietPi kernel: random: systemd: uninitia lized urandom read (16 bytes read) Jun 26 14:25:16 DietPi systemd[1]: Started Forward Password Requests to Wall Dir ectory Watch. Jun 26 14:25:16 DietPi systemd[1]: Listening on fsck to fsckd communication Sock et. Jun 26 14:25:16 DietPi systemd[1]: Started Dispatch Password Requests to Console Directory Watch. Jun 26 14:25:16 DietPi systemd[1]: Reached target Remote File Systems. Jun 26 14:25:16 DietPi systemd[1]: Set up automount Arbitrary Executable File Fo rmats File System Automount Point. Jun 26 14:25:16 DietPi systemd[1]: Listening on udev Kernel Socket. Jun 26 14:25:16 DietPi kernel: dwc_otg_handle_wakeup_det ected_intr lxstate = 2 Jun 26 14:25:16 DietPi systemd-journald[110]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Jun 26 14:25:16 DietPi systemd-journald[110]: Runtime journal (/run/log/journal/ 5c98b9cf4fdb4158b7ca06b7869273e7) is 6.0M, max 48.6M, 42.6M free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Runtime journal (/run/log/journal/5c98b9cf4fdb4158b7ca06b7869273e7) is curren tly using 6.0M. -- Maximum allowed usage is set to 48.6M. -- Leaving at least 73.0M free (of currently available 480.7M of disk space). -- Enforced usage limit is thus 48.6M, of which 42.6M are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Jun 26 14:25:16 DietPi fake-hwclock[105]: Sat Jun 26 13:25:16 UTC 2021 Jun 26 14:25:16 DietPi systemd[1]: Started udev Coldplug all Devices. -- Subject: A start job for unit systemd-udev-trigger.service has finished succe ssfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-udev-trigger.service has finished successfully. -- -- The job identifier is 15. Jun 26 14:25:16 DietPi systemd[1]: Starting Helper to synchronize boot up for if updown... -- Subject: A start job for unit ifupdown-pre.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifupdown-pre.service has begun execution. -- -- The job identifier is 78. Jun 26 14:25:16 DietPi systemd-fsck[122]: e2fsck 1.44.5 (15-Dec-2018) Jun 26 14:25:16 DietPi systemd[1]: Started Helper to synchronize boot up for ifu pdown. -- Subject: A start job for unit ifupdown-pre.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifupdown-pre.service has finished successfully. -- -- The job identifier is 78. Jun 26 14:25:16 DietPi systemd-fsck[122]: rootfs: clean, 22925/1925760 files, 56 4769/7725184 blocks Jun 26 14:25:16 DietPi systemd[1]: Started File System Check on Root Device. -- Subject: A start job for unit systemd-fsck-root.service has finished successf ully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck-root.service has finished successfully. -- -- The job identifier is 34. Jun 26 14:25:16 DietPi systemd[1]: Starting Remount Root and Kernel File Systems ... -- Subject: A start job for unit systemd-remount-fs.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-remount-fs.service has begun execution. -- -- The job identifier is 33. Jun 26 14:25:16 DietPi systemd[1]: Started Set the console keyboard layout. -- Subject: A start job for unit keyboard-setup.service has finished successfull y -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit keyboard-setup.service has finished successfully. -- -- The job identifier is 13. Jun 26 14:25:16 DietPi kernel: EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Jun 26 14:25:16 DietPi systemd[1]: Started Remount Root and Kernel File Systems. -- Subject: A start job for unit systemd-remount-fs.service has finished success fully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-remount-fs.service has finished successfully. -- -- The job identifier is 33. Jun 26 14:25:16 DietPi systemd[1]: Starting Load/Save Random Seed... -- Subject: A start job for unit systemd-random-seed.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-random-seed.service has begun execution. -- -- The job identifier is 10. Jun 26 14:25:16 DietPi systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. -- Subject: A start job for unit systemd-hwdb-update.service has finished succes sfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-hwdb-update.service has finished successfully. -- -- The job identifier is 11. Jun 26 14:25:16 DietPi systemd[1]: Starting Create System Users... -- Subject: A start job for unit systemd-sysusers.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-sysusers.service has begun execution. -- -- The job identifier is 20. Jun 26 14:25:16 DietPi systemd[1]: Activating swap /var/swap... -- Subject: A start job for unit var-swap.swap has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-swap.swap has begun execution. -- -- The job identifier is 55. Jun 26 14:25:16 DietPi systemd[1]: Started Load/Save Random Seed. -- Subject: A start job for unit systemd-random-seed.service has finished succes sfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-random-seed.service has finished successfully. -- -- The job identifier is 10. Jun 26 14:25:16 DietPi systemd[1]: Started Create System Users. -- Subject: A start job for unit systemd-sysusers.service has finished successfu lly -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-sysusers.service has finished successfully. -- -- The job identifier is 20. Jun 26 14:25:16 DietPi systemd[1]: Starting Create Static Device Nodes in /dev.. . -- Subject: A start job for unit systemd-tmpfiles-setup-dev.service has begun ex ecution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup-dev.service has begun execution. -- -- The job identifier is 24. Jun 26 14:25:16 DietPi systemd[1]: Activated swap /var/swap. -- Subject: A start job for unit var-swap.swap has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-swap.swap has finished successfully. -- -- The job identifier is 55. Jun 26 14:25:16 DietPi systemd[1]: Reached target Swap. -- Subject: A start job for unit swap.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit swap.target has finished successfully. -- -- The job identifier is 54. Jun 26 14:25:16 DietPi systemd[1]: Started Create Static Device Nodes in /dev. -- Subject: A start job for unit systemd-tmpfiles-setup-dev.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup-dev.service has finished successf ully. -- -- The job identifier is 24. Jun 26 14:25:16 DietPi systemd[1]: Reached target Local File Systems (Pre). -- Subject: A start job for unit local-fs-pre.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit local-fs-pre.target has finished successfully. -- -- The job identifier is 14. Jun 26 14:25:16 DietPi systemd[1]: Mounting /tmp... -- Subject: A start job for unit tmp.mount has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit tmp.mount has begun execution. -- -- The job identifier is 31. Jun 26 14:25:16 DietPi kernel: Adding 1100796k swap on /var/swap. Priority:-2 e xtents:4 across:1141756k SSFS Jun 26 14:25:16 DietPi systemd[1]: Mounting /var/log... -- Subject: A start job for unit var-log.mount has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-log.mount has begun execution. -- -- The job identifier is 22. Jun 26 14:25:16 DietPi systemd[1]: Starting udev Kernel Device Manager... -- Subject: A start job for unit systemd-udevd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-udevd.service has begun execution. -- -- The job identifier is 16. Jun 26 14:25:16 DietPi systemd[1]: Mounted /tmp. -- Subject: A start job for unit tmp.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit tmp.mount has finished successfully. -- -- The job identifier is 31. Jun 26 14:25:16 DietPi systemd[1]: Mounted /var/log. -- Subject: A start job for unit var-log.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit var-log.mount has finished successfully. -- -- The job identifier is 22. Jun 26 14:25:16 DietPi systemd[1]: Starting Flush Journal to Persistent Storage. .. -- Subject: A start job for unit systemd-journal-flush.service has begun executi on -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-journal-flush.service has begun execution. -- -- The job identifier is 48. Jun 26 14:25:16 DietPi systemd-udevd[138]: Network interface NamePolicy= disable d on kernel command line, ignoring. Jun 26 14:25:16 DietPi systemd-journald[110]: Runtime journal (/run/log/journal/ 5c98b9cf4fdb4158b7ca06b7869273e7) is 6.0M, max 48.6M, 42.6M free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Runtime journal (/run/log/journal/5c98b9cf4fdb4158b7ca06b7869273e7) is curren tly using 6.0M. -- Maximum allowed usage is set to 48.6M. -- Leaving at least 73.0M free (of currently available 480.7M of disk space). -- Enforced usage limit is thus 48.6M, of which 42.6M are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Jun 26 14:25:16 DietPi systemd[1]: Started Flush Journal to Persistent Storage. -- Subject: A start job for unit systemd-journal-flush.service has finished succ essfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-journal-flush.service has finished successfully. -- -- The job identifier is 48. Jun 26 14:25:16 DietPi kernel: usb 1-1.1.1: new high-speed USB device number 4 u sing dwc_otg Jun 26 14:25:16 DietPi systemd[1]: Started udev Kernel Device Manager. -- Subject: A start job for unit systemd-udevd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-udevd.service has finished successfully. -- -- The job identifier is 16. Jun 26 14:25:16 DietPi kernel: usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00 Jun 26 14:25:16 DietPi kernel: usb 1-1.1.1: New USB device strings: Mfr=0, Produ ct=0, SerialNumber=0 Jun 26 14:25:16 DietPi kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uniniti alized): No External EEPROM. Setting MAC Speed Jun 26 14:25:16 DietPi kernel: libphy: lan78xx-mdiobus: probed Jun 26 14:25:16 DietPi kernel: lan78xx 1-1.1.1:1.0 (unna med net_device) (uninitialized): int urb period 64 Jun 26 14:25:16 DietPi systemd-udevd[142]: Using default interface naming scheme 'v240'. Jun 26 14:25:17 DietPi systemd[1]: Found device /dev/disk/by-partuuid/9730496b-0 1. -- Subject: A start job for unit dev-disk-by\x2dpartuuid-9730496b\x2d01.device h as finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dev-disk-by\x2dpartuuid-9730496b\x2d01.device has finish ed successfully. -- -- The job identifier is 29. Jun 26 14:25:17 DietPi systemd[1]: Starting File System Check on /dev/disk/by-pa rtuuid/9730496b-01... -- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-9730496b\x 2d01.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-9730496b\x2d01.serv ice has begun execution. -- -- The job identifier is 27. Jun 26 14:25:17 DietPi systemd[1]: Found device 7800. -- Subject: A start job for unit sys-subsystem-net-devices-eth0.device has finis hed successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sys-subsystem-net-devices-eth0.device has finished succe ssfully. -- -- The job identifier is 97. Jun 26 14:25:17 DietPi systemd-fsck[195]: fsck.fat 4.1 (2017-01-24) Jun 26 14:25:17 DietPi systemd-fsck[195]: /dev/mmcblk0p1: 325 files, 100996/5161 90 clusters Jun 26 14:25:17 DietPi systemd[1]: Started File System Check on /dev/disk/by-par tuuid/9730496b-01. -- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-9730496b\x 2d01.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-fsck@dev-disk-by\x2dpartuuid-9730496b\x2d01.serv ice has finished successfully. -- -- The job identifier is 27. Jun 26 14:25:17 DietPi systemd[1]: Mounting /boot... -- Subject: A start job for unit boot.mount has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit boot.mount has begun execution. -- -- The job identifier is 26. Jun 26 14:25:17 DietPi systemd[1]: Mounted /boot. -- Subject: A start job for unit boot.mount has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit boot.mount has finished successfully. -- -- The job identifier is 26. Jun 26 14:25:17 DietPi systemd[1]: Reached target Local File Systems. -- Subject: A start job for unit local-fs.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit local-fs.target has finished successfully. -- -- The job identifier is 25. Jun 26 14:25:17 DietPi systemd[1]: Starting Set console font and keymap... -- Subject: A start job for unit console-setup.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit console-setup.service has begun execution. -- -- The job identifier is 86. Jun 26 14:25:17 DietPi systemd[1]: Condition check resulted in Commit a transien t machine-id on disk being skipped. -- Subject: A start job for unit systemd-machine-id-commit.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-machine-id-commit.service has finished successfu lly. -- -- The job identifier is 47. Jun 26 14:25:17 DietPi systemd[1]: Starting Create Volatile Files and Directorie s... -- Subject: A start job for unit systemd-tmpfiles-setup.service has begun execut ion -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup.service has begun execution. -- -- The job identifier is 19. Jun 26 14:25:17 DietPi systemd[1]: Started vmtouch. -- Subject: A start job for unit vmtouch.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit vmtouch.service has finished successfully. -- -- The job identifier is 32. Jun 26 14:25:17 DietPi systemd[1]: Started Set console font and keymap. -- Subject: A start job for unit console-setup.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit console-setup.service has finished successfully. -- -- The job identifier is 86. Jun 26 14:25:17 DietPi systemd[1]: Started Create Volatile Files and Directories . -- Subject: A start job for unit systemd-tmpfiles-setup.service has finished suc cessfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-setup.service has finished successfully . -- -- The job identifier is 19. Jun 26 14:25:17 DietPi systemd[1]: Starting Update UTMP about System Boot/Shutdo wn... -- Subject: A start job for unit systemd-update-utmp.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp.service has begun execution. -- -- The job identifier is 82. Jun 26 14:25:17 DietPi systemd[1]: Started Update UTMP about System Boot/Shutdow n. -- Subject: A start job for unit systemd-update-utmp.service has finished succes sfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp.service has finished successfully. -- -- The job identifier is 82. Jun 26 14:25:17 DietPi systemd[1]: Reached target System Initialization. -- Subject: A start job for unit sysinit.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sysinit.target has finished successfully. -- -- The job identifier is 7. Jun 26 14:25:17 DietPi systemd[1]: Started Discard unused blocks once a week. -- Subject: A start job for unit fstrim.timer has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit fstrim.timer has finished successfully. -- -- The job identifier is 63. Jun 26 14:25:17 DietPi systemd[1]: Listening on D-Bus System Message Bus Socket. -- Subject: A start job for unit dbus.socket has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dbus.socket has finished successfully. -- -- The job identifier is 59. Jun 26 14:25:17 DietPi systemd[1]: Reached target Sockets. -- Subject: A start job for unit sockets.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit sockets.target has finished successfully. -- -- The job identifier is 58. Jun 26 14:25:17 DietPi systemd[1]: Started Daily Cleanup of Temporary Directorie s. -- Subject: A start job for unit systemd-tmpfiles-clean.timer has finished succe ssfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-clean.timer has finished successfully. -- -- The job identifier is 62. Jun 26 14:25:17 DietPi systemd[1]: Reached target Timers. -- Subject: A start job for unit timers.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit timers.target has finished successfully. -- -- The job identifier is 61. Jun 26 14:25:17 DietPi systemd[1]: Reached target Basic System. -- Subject: A start job for unit basic.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit basic.target has finished successfully. -- -- The job identifier is 3. Jun 26 14:25:17 DietPi systemd[1]: Starting DietPi-RAMlog... -- Subject: A start job for unit dietpi-ramlog.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-ramlog.service has begun execution. -- -- The job identifier is 76. Jun 26 14:25:17 DietPi systemd[1]: Started D-Bus System Message Bus. -- Subject: A start job for unit dbus.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dbus.service has finished successfully. -- -- The job identifier is 88. Jun 26 14:25:17 DietPi systemd[1]: Started Start entropy gathering daemon (rngd) . -- Subject: A start job for unit rngd.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit rngd.service has finished successfully. -- -- The job identifier is 73. Jun 26 14:25:17 DietPi systemd[1]: Starting Configure Bluetooth Modems connected by UART... -- Subject: A start job for unit hciuart.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit hciuart.service has begun execution. -- -- The job identifier is 72. Jun 26 14:25:17 DietPi kernel: random: crng init done Jun 26 14:25:17 DietPi kernel: random: 7 urandom warning (s) missed due to ratelimiting Jun 26 14:25:18 DietPi kernel: uart-pl011 3f201000.serial: no DMA platform data Jun 26 14:25:18 DietPi systemd[1]: Started DietPi-RAMlog. -- Subject: A start job for unit dietpi-ramlog.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-ramlog.service has finished successfully. -- -- The job identifier is 76. Jun 26 14:25:18 DietPi systemd[1]: Starting DietPi-PreBoot... -- Subject: A start job for unit dietpi-preboot.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-preboot.service has begun execution. -- -- The job identifier is 85. Jun 26 14:25:18 DietPi DietPi-PreBoot[238]: DietPi-CPU_set Jun 26 14:25:18 DietPi DietPi-PreBoot[238]: ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ Jun 26 14:25:18 DietPi DietPi-PreBoot[238]: Mode: Applying CPU governor setting s: schedutil Jun 26 14:25:18 DietPi DietPi-PreBoot[238]: [ OK ] DietPi-CPU_set | Applied CP U governor settings: schedutil Jun 26 14:25:18 DietPi systemd[1]: Started DietPi-PreBoot. -- Subject: A start job for unit dietpi-preboot.service has finished successfull y -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-preboot.service has finished successfully. -- -- The job identifier is 85. Jun 26 14:25:18 DietPi systemd[1]: Reached target Network (Pre). -- Subject: A start job for unit network-pre.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit network-pre.target has finished successfully. -- -- The job identifier is 66. Jun 26 14:25:18 DietPi systemd[1]: Starting DietPi-Boot... -- Subject: A start job for unit dietpi-boot.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-boot.service has begun execution. -- -- The job identifier is 84. Jun 26 14:25:18 DietPi systemd[1]: Starting Raise network interfaces... -- Subject: A start job for unit networking.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit networking.service has begun execution. -- -- The job identifier is 77. Jun 26 14:25:18 DietPi systemd[1]: Starting ifup for eth0... -- Subject: A start job for unit ifup@eth0.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifup@eth0.service has begun execution. -- -- The job identifier is 94. Jun 26 14:25:18 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:18 DietPi dhclient[289]: Internet Systems Consortium DHCP Client 4. 4.1 Jun 26 14:25:18 DietPi ifup[258]: Internet Systems Consortium DHCP Client 4.4.1 Jun 26 14:25:18 DietPi dhclient[289]: Copyright 2004-2018 Internet Systems Conso rtium. Jun 26 14:25:18 DietPi ifup[258]: Copyright 2004-2018 Internet Systems Consortiu m. Jun 26 14:25:18 DietPi dhclient[289]: All rights reserved. Jun 26 14:25:18 DietPi ifup[258]: All rights reserved. Jun 26 14:25:18 DietPi dhclient[289]: For info, please visit https://www.isc.org /software/dhcp/ Jun 26 14:25:18 DietPi ifup[258]: For info, please visit https://www.isc.org/sof tware/dhcp/ Jun 26 14:25:18 DietPi dhclient[289]: Jun 26 14:25:18 DietPi systemd[1]: Started Raise network interfaces. -- Subject: A start job for unit networking.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit networking.service has finished successfully. -- -- The job identifier is 77. Jun 26 14:25:18 DietPi dhclient[289]: Listening on LPF/eth0/b8:27:eb:0e:61:1f Jun 26 14:25:18 DietPi ifup[258]: Listening on LPF/eth0/b8:27:eb:0e:61:1f Jun 26 14:25:18 DietPi dhclient[289]: Sending on LPF/eth0/b8:27:eb:0e:61:1f Jun 26 14:25:18 DietPi ifup[258]: Sending on LPF/eth0/b8:27:eb:0e:61:1f Jun 26 14:25:18 DietPi ifup[258]: Sending on Socket/fallback Jun 26 14:25:18 DietPi ifup[258]: DHCPDISCOVER on eth0 to 255.255.255.255 port 6 7 interval 8 Jun 26 14:25:18 DietPi dhclient[289]: Sending on Socket/fallback Jun 26 14:25:18 DietPi dhclient[289]: DHCPDISCOVER on eth0 to 255.255.255.255 po rt 67 interval 8 Jun 26 14:25:19 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:20 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:20 DietPi kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jun 26 14:25:21 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:22 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:23 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:24 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:25 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:26 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:26 DietPi dhclient[289]: DHCPDISCOVER on eth0 to 255.255.255.255 po rt 67 interval 3 Jun 26 14:25:26 DietPi ifup[258]: DHCPDISCOVER on eth0 to 255.255.255.255 port 6 7 interval 3 Jun 26 14:25:27 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Boot | Waiting for vali d network connection before continuing boot | Mode=1 Jun 26 14:25:27 DietPi dhclient[289]: DHCPOFFER of 10.0.0.211 from 10.0.0.1 Jun 26 14:25:27 DietPi ifup[258]: DHCPOFFER of 10.0.0.211 from 10.0.0.1 Jun 26 14:25:27 DietPi ifup[258]: DHCPREQUEST for 10.0.0.211 on eth0 to 255.255. 255.255 port 67 Jun 26 14:25:27 DietPi dhclient[289]: DHCPREQUEST for 10.0.0.211 on eth0 to 255. 255.255.255 port 67 Jun 26 14:25:27 DietPi dhclient[289]: DHCPACK of 10.0.0.211 from 10.0.0.1 Jun 26 14:25:27 DietPi ifup[258]: DHCPACK of 10.0.0.211 from 10.0.0.1 Jun 26 14:25:27 DietPi dhclient[289]: bound to 10.0.0.211 -- renewal in 3013 sec onds. Jun 26 14:25:27 DietPi ifup[258]: bound to 10.0.0.211 -- renewal in 3013 seconds . Jun 26 14:25:27 DietPi systemd[1]: Started ifup for eth0. -- Subject: A start job for unit ifup@eth0.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit ifup@eth0.service has finished successfully. -- -- The job identifier is 94. Jun 26 14:25:27 DietPi systemd[1]: Reached target Network. -- Subject: A start job for unit network.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit network.target has finished successfully. -- -- The job identifier is 79. Jun 26 14:25:27 DietPi systemd[1]: Starting Permit User Sessions... -- Subject: A start job for unit systemd-user-sessions.service has begun executi on -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-user-sessions.service has begun execution. -- -- The job identifier is 87. Jun 26 14:25:27 DietPi systemd[1]: Started Permit User Sessions. -- Subject: A start job for unit systemd-user-sessions.service has finished succ essfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-user-sessions.service has finished successfully. -- -- The job identifier is 87. Jun 26 14:25:28 DietPi DietPi-Boot[256]: [FAILED] DietPi-Boot | Waiting for vali d network connection timed out Jun 26 14:25:28 DietPi DietPi-Boot[256]: [ .... ] DietPi-Run_NTPD | systemctl re start systemd-timesyncd Jun 26 14:25:28 DietPi systemd[1]: Starting Network Time Synchronization... -- Subject: A start job for unit systemd-timesyncd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-timesyncd.service has begun execution. -- -- The job identifier is 106. Jun 26 14:25:28 DietPi systemd[1]: Started Network Time Synchronization. -- Subject: A start job for unit systemd-timesyncd.service has finished successf ully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-timesyncd.service has finished successfully. -- -- The job identifier is 106. Jun 26 14:25:28 DietPi DietPi-Boot[256]: [ OK ] DietPi-Run_NTPD | systemctl re start systemd-timesyncd Jun 26 14:25:28 DietPi systemd[1]: Reached target System Time Synchronized. -- Subject: A start job for unit time-sync.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit time-sync.target has finished successfully. -- -- The job identifier is 112. Jun 26 14:25:28 DietPi DietPi-Boot[256]: [ INFO ] DietPi-Run_NTPD | Waiting for completion of systemd-timesyncd (1/60) Jun 26 14:25:37 DietPi systemd-timesyncd[380]: Synchronized to time server for t he first time 94.198.159.10:123 (0.debian.pool.ntp.org). Jun 26 14:25:38 DietPi DietPi-Boot[256]: [ OK ] DietPi-Run_NTPD | systemd-time syncd synced Jun 26 14:25:38 DietPi systemd[1]: Stopping Network Time Synchronization... -- Subject: A stop job for unit systemd-timesyncd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit systemd-timesyncd.service has begun execution. -- -- The job identifier is 114. Jun 26 14:25:38 DietPi systemd[1]: systemd-timesyncd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-timesyncd.service has successfully entered the 'dead' state. Jun 26 14:25:38 DietPi systemd[1]: Stopped Network Time Synchronization. -- Subject: A stop job for unit systemd-timesyncd.service has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit systemd-timesyncd.service has finished. -- -- The job identifier is 114 and the job result is done. Jun 26 14:25:38 DietPi DietPi-Boot[256]: [ OK ] Network time sync | Completed Jun 26 14:25:38 DietPi systemd[1]: Started DietPi-Boot. -- Subject: A start job for unit dietpi-boot.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-boot.service has finished successfully. -- -- The job identifier is 84. Jun 26 14:25:38 DietPi systemd[1]: Started DietPi-PostBoot. -- Subject: A start job for unit dietpi-postboot.service has finished successful ly -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dietpi-postboot.service has finished successfully. -- -- The job identifier is 74. Jun 26 14:25:38 DietPi systemd[1]: Started Getty on tty1. -- Subject: A start job for unit getty@tty1.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit getty@tty1.service has finished successfully. -- -- The job identifier is 68. Jun 26 14:25:38 DietPi systemd[1]: Starting LSB: Lightweight SSH server... -- Subject: A start job for unit dropbear.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dropbear.service has begun execution. -- -- The job identifier is 83. Jun 26 14:25:38 DietPi systemd[1]: Reached target Login Prompts. -- Subject: A start job for unit getty.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit getty.target has finished successfully. -- -- The job identifier is 67. Jun 26 14:25:38 DietPi dropbear[400]: Starting Dropbear SSH server: dropbear. Jun 26 14:25:38 DietPi dropbear[404]: Running in background Jun 26 14:25:38 DietPi systemd[1]: Started LSB: Lightweight SSH server. -- Subject: A start job for unit dropbear.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit dropbear.service has finished successfully. -- -- The job identifier is 83. Jun 26 14:25:43 DietPi systemd[1]: Started Regular background program processing daemon. -- Subject: A start job for unit cron.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit cron.service has finished successfully. -- -- The job identifier is 115. Jun 26 14:25:44 DietPi cron[420]: (CRON) INFO (pidfile fd = 3) Jun 26 14:25:44 DietPi cron[420]: (CRON) INFO (Running @reboot jobs) Jun 26 14:25:56 DietPi systemd[1]: systemd-fsckd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-fsckd.service has successfully entered the 'dead' state. Jun 26 14:25:56 DietPi btuart[209]: Initialization timed out. Jun 26 14:25:56 DietPi btuart[209]: bcm43xx_init Jun 26 14:25:56 DietPi systemd[1]: hciuart.service: Cont rol process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit hciuart.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Jun 26 14:25:56 DietPi systemd[1]: hciuart.service: Fail ed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit hciuart.service has entered the 'failed' state with result 'exit-cod e'. Jun 26 14:25:56 DietPi systemd[1]: Failed to start Confi gure Bluetooth Modems connected by UART. -- Subject: A start job for unit hciuart.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit hciuart.service has finished with a failure. -- -- The job identifier is 72 and the job result is failed. Jun 26 14:25:56 DietPi systemd[1]: Reached target Multi-User System. -- Subject: A start job for unit multi-user.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit multi-user.target has finished successfully. -- -- The job identifier is 2. Jun 26 14:25:56 DietPi systemd[1]: Reached target Graphical Interface. -- Subject: A start job for unit graphical.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit graphical.target has finished successfully. -- -- The job identifier is 1. Jun 26 14:25:56 DietPi systemd[1]: Starting Update UTMP about System Runlevel Ch anges... -- Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp-runlevel.service has begun execution . -- -- The job identifier is 81. Jun 26 14:25:56 DietPi systemd[1]: systemd-update-utmp-runlevel.service: Succeed ed. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-update-utmp-runlevel.service has successfully entered the 'd ead' state. Jun 26 14:25:56 DietPi systemd[1]: Started Update UTMP about System Runlevel Cha nges. -- Subject: A start job for unit systemd-update-utmp-runlevel.service has finish ed successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-update-utmp-runlevel.service has finished succes sfully. -- -- The job identifier is 81. Jun 26 14:25:56 DietPi systemd[1]: Startup finished in 2.544s (kernel) + 32.951s (userspace) = 35.496s. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- All system services necessary queued for starting at boot have been -- started. Note that this does not mean that the machine is now idle as service s -- might still be busy with completing start-up. -- -- Kernel start-up required 2544839 microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 32951995 microseconds. Jun 26 14:26:19 DietPi dropbear[553]: Child connection from 10.0.0.65:59862 Jun 26 14:26:24 DietPi dropbear[553]: Login attempt for nonexistent user from 10.0.0.65:59862 Jun 26 14:26:30 DietPi dropbear[553]: Exit before auth: Exited normally Jun 26 14:26:41 DietPi dropbear[554]: Child connection from 10.0.0.65:59863 Jun 26 14:26:48 DietPi dropbear[554]: Password auth succ eeded for 'root' from 10.0.0.65:59863 Jun 26 14:40:29 DietPi systemd[1]: Starting Cleanup of Temporary Directories... -- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execut ion -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-clean.service has begun execution. -- -- The job identifier is 174. Jun 26 14:40:29 DietPi systemd[1]: systemd-tmpfiles-clean.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' s tate. Jun 26 14:40:29 DietPi systemd[1]: Started Cleanup of Temporary Directories. -- Subject: A start job for unit systemd-tmpfiles-clean.service has finished suc cessfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-tmpfiles-clean.service has finished successfully . -- -- The job identifier is 174. Jun 26 15:15:40 DietPi dhclient[289]: DHCPREQUEST for 10.0.0.211 on eth0 to 10.0 .0.1 port 67 Jun 26 15:15:40 DietPi dhclient[289]: DHCPACK of 10.0.0.211 from 10.0.0.1 Jun 26 15:15:40 DietPi dhclient[289]: bound to 10.0.0.211 -- renewal in 3574 sec onds. Jun 26 15:17:01 DietPi CRON[611]: pam_unix(cron:session): session opened for use r root by (uid=0) Jun 26 15:17:01 DietPi CRON[612]: (root) CMD (cd / && run-parts --report /etc/cr on.hourly) Jun 26 15:17:01 DietPi CRON[611]: pam_unix(cron:session): session closed for use r root Jun 26 15:21:19 DietPi systemd[1]: Starting Configure Bluetooth Modems connected by UART... -- Subject: A start job for unit hciuart.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit hciuart.service has begun execution. -- -- The job identifier is 178. Jun 26 15:21:49 DietPi btuart[640]: Initialization timed out. Jun 26 15:21:49 DietPi btuart[640]: bcm43xx_init Jun 26 15:21:49 DietPi systemd[1]: hciuart.service: Cont rol process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit hciuart.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Jun 26 15:21:49 DietPi systemd[1]: hciuart.service: Fail ed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit hciuart.service has entered the 'failed' state with result 'exit-cod e'. Jun 26 15:21:49 DietPi systemd[1]: Failed to start Confi gure Bluetooth Modems connected by UART. -- Subject: A start job for unit hciuart.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit hciuart.service has finished with a failure. -- -- The job identifier is 178 and the job result is failed. ```
Joulinar commented 3 years ago

Pls if possible don't do screen prints. Try to copy the output from SSH terminal

BelgarionNL commented 3 years ago

updated post with text.

MichaIng commented 3 years ago

Can you try the following:

sed -i '/dtoverlay=disable-wifi/d' /boot/config.txt
reboot

I remember a case where, if I'm not mistaken, the Bluetooth module needed to be enabled for WiFi to work, and I guess in these cases it's true as well the other way round. It's rare RPi 3 revisions where both seem to be on the same lane and always toggled together, instead of independently, as expected. I cannot find the issue currently, let's first see if this is the case for you. As it fails only after reboot, it seems to be one of the boot/firmware configs, done during firstrun setup, at least.

BelgarionNL commented 3 years ago

yep! thats it

its pure luck that both of these rpi3b+ have this then since I got one recently and the other one is a couple years old.

so using the GUI simply enabling wifi will also work? or should I keep using this command for new versions or will you include a improvement in the next beta version?

MichaIng commented 3 years ago

Ah great that we found it.

so using the GUI simply enabling wifi will also work?

Better keep using that command or remove the related line manually form config.txt, so the kernel modules and the network interface stays disabled, but only the hardware device part is enabled.

Could you check the revisions of those two RPis?

echo $G_HW_REVISION
BelgarionNL commented 3 years ago

will do thanks!

a020d3 a020d3

and the other one has raspbian on it that does not give me any. Once I have moved my devices over to the now working dietpi then I will give you the other revision :)

MichaIng commented 3 years ago

On Raspbian, the following shows the revision:

mawk '/Revision/{print $3}' /proc/cpuinfo
BelgarionNL commented 3 years ago

well they are the same. good to know.

https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision-codes/README.md

uhm maybe its just me but is there only 1 revision from the rpi3b+ then? so this bug would affect all rpi3B+ users it seems.

MichaIng commented 3 years ago

Oh you are right. Hmm, it is a little late before the release, but I would want to check this back with the RPi devs. Probably there is a possibility to fix this firmware-wise.

MichaIng commented 3 years ago

Found the two related threads in the Raspberry Pi forum, and indeed it's model 3B+:

And indeed it's when disabling WiFi, that Bluetooth is disabled as well while I couldn't find a hint that it's true the other way round as well, at least.

Joulinar commented 3 years ago

@MichaIng

this is how it looks on my system after reboot. WiFi disabled + BT enabled

root@DietPi3:~# cat /boot/config.txt | grep dtoverlay
dtoverlay=dietpi-disable_vcsm
dtoverlay=disable-wifi
root@DietPi3:~# systemctl status hciuart.service
ā— hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-07-12 23:30:32 CEST; 2min 30s ago
  Process: 224 ExecStart=/usr/bin/btuart (code=exited, status=0/SUCCESS)
 Main PID: 416 (hciattach)
    Tasks: 1 (limit: 2181)
   CGroup: /system.slice/hciuart.service
           ā””ā”€416 /usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow - b8:27:eb:7c:cb:e0

Jul 12 23:29:57 DietPi3 systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jul 12 23:30:32 DietPi3 btuart[224]: bcm43xx_init
Jul 12 23:30:32 DietPi3 btuart[224]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
Jul 12 23:30:32 DietPi3 btuart[224]: Set BDADDR UART: b8:27:eb:7c:cb:e0
Jul 12 23:30:32 DietPi3 btuart[224]: Set Controller UART speed to 3000000 bit/s
Jul 12 23:30:32 DietPi3 btuart[224]: Device setup complete
Jul 12 23:30:32 DietPi3 systemd[1]: Started Configure Bluetooth Modems connected by UART.
root@DietPi3:~#
MichaIng commented 3 years ago

Many thanks for testing, and strange that it works in your case. The revision is a020d3, right?

mawk '/Revision/{print $3}' /proc/cpuinfo
Joulinar commented 3 years ago

yep

root@DietPi3:~# mawk '/Revision/{print $3}' /proc/cpuinfo
a020d3
root@DietPi3:~#
BelgarionNL commented 3 years ago

gave this another fresh go on 1 of my 2 rpi3b+ and yea for me it fails every time :)

weird yours is working. anyway its working with the workaround so thanks for getting this sorted šŸ‘

MichaIng commented 3 years ago

Nasty, as I'm not sure then how to know whether the workaround is required or not (for an implementation in our scripts) šŸ¤”. I'll keep the issue open and see whether I can find further info about this, if it's a specific charge of the RPi 3+ builds that are affected or so, and how to detect.

MichaIng commented 3 years ago

Issue/question reported: https://github.com/raspberrypi/firmware/issues/1611

MichaIng commented 3 years ago

Okay, indeed there seem to have been a change on the RPi 3B+ models without a revision code increment. On RPi 3A+ it behaves the same. I'm checking back another detail, probably we can implement a probe on RPi 3B+ and then, when user requests to disable WiFi while Bluetooth is enabled or the other way round, we can add an additional continue/abort prompt, informing user that at least the dtoverlay=disable-wifi needs to be/stay absent for Bluetooth to function, which means at some level, WiFi is enabled. Not a real issue IMO, also since we blacklist the Broadcom WiFi kernel modules, but some like to assure that certain communication channel/hardware is disabled lowest possible level.

EDIT: Even better, a firmware-wise fix is planned šŸ‘.

MichaIng commented 3 years ago

@BelgarionNL Could you try to install these two files into your /boot directory (overwriting the existing ones): https://drive.google.com/file/d/10gBNYX6UcFFwjZircjbfgOd7uKzBSnzA/view

To have those loaded, you need to at least have 32 MiB GPU memory applied, i.e. check via dietpi-config > Display Options > GPU/RAM Memory Split and raise it to 32 MiB, if 16 MiB are currently applied. Else the cutdown firmware is loaded, hence start_cd.elf and fixup_cd.dat. Then disable again WiFi, reboot and see if Bluetooth is still working:

G_CONFIG_INJECT 'dtoverlay=disable-wifi' 'dtoverlay=disable-wifi' /boot/config.txt
reboot
systemctl status hciuart
MichaIng commented 3 years ago

Now even easier to apply the fix without manual file download:

apt install rpi-update
rpi-update
G_CONFIG_INJECT 'dtoverlay=disable-wifi' 'dtoverlay=disable-wifi' /boot/config.txt
reboot
systemctl status hciuart
MichaIng commented 2 years ago

@BelgarionNL Could you test with recent stable kernel/firmware (apt update && apt upgrade)? It should be fixed now, i.e. you should be able to disable WiFi now without breaking Bluetooth.

MichaIng commented 2 years ago

I'll mark this as closed now, AFAIK it has been solved, though I have no RPi 3+ to test.