[SOLVED] Replacing microSD with USB (RPI3+)

This forum is for discussion about general software issues.

[SOLVED] Replacing microSD with USB (RPI3+)

Postby jyno » Fri Feb 25, 2022 12:10 pm

Hello,

I'm attempting to move my current ArchLinuxARM installation to USB.
Systemd, as it appears, makes it difficult for me to do so.

So far, this is what I've done.

1st phase:
microSD /dev/sda
USB /dev/sdb
$this->bbcode_second_pass_code('', 'dd bs=52M status=progress if=/dev/sda of=/dev/sdb')

2nd phase:
Open /boot/cmdline.txt
Replace mmcblk0p2 by sda2
$this->bbcode_second_pass_code('', 'root=/dev/sda2 rw rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=serial0,115200')

3rd phase:
Failling to startup the alarm user, because of Systemd which is constantly looking for $this->bbcode_second_pass_code('', '/dev/mmcblk0p1')
And yet root user seems to be fully operatable.

Here is an output of $this->bbcode_second_pass_code('', '# journalctl -xb')
https://haste.tchncs.de/rotepobice.yaml (see also following couple of posts)

Please advise!
Thank you

--jyno slaps systemd and tells it to gtfo! and go back to the sandbox where it was coming from
Last edited by jyno on Sun Feb 27, 2022 6:36 am, edited 8 times in total.
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [HELP] Replacing microSD with USB (RPI3+)

Postby jyno » Fri Feb 25, 2022 1:45 pm

Part 1 of journalctl -xb:
$this->bbcode_second_pass_code('', '
Feb 10 21:19:59 alarmpi kernel: Booting Linux on physical CPU 0x0
Feb 10 21:19:59 alarmpi kernel: Linux version 5.10.92-2-rpi-legacy-ARCH (builduser@leming) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP Sat Jan 22 15:47:02 UTC 2022
Feb 10 21:19:59 alarmpi kernel: CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Feb 10 21:19:59 alarmpi kernel: CPU: div instructions available: patching division code
Feb 10 21:19:59 alarmpi kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Feb 10 21:19:59 alarmpi kernel: OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Feb 10 21:19:59 alarmpi kernel: random: fast init done
Feb 10 21:19:59 alarmpi kernel: Memory policy: Data cache writealloc
Feb 10 21:19:59 alarmpi kernel: Reserved memory: created CMA memory pool at 0x1e800000, size 256 MiB
Feb 10 21:19:59 alarmpi kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Feb 10 21:19:59 alarmpi kernel: Zone ranges:
Feb 10 21:19:59 alarmpi kernel: DMA [mem 0x0000000000000000-0x000000003b3fffff]
Feb 10 21:19:59 alarmpi kernel: Normal empty
Feb 10 21:19:59 alarmpi kernel: HighMem empty
Feb 10 21:19:59 alarmpi kernel: Movable zone start for each node
Feb 10 21:19:59 alarmpi kernel: Early memory node ranges
Feb 10 21:19:59 alarmpi kernel: node 0: [mem 0x0000000000000000-0x000000003b3fffff]
Feb 10 21:19:59 alarmpi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x000000003b3fffff]
Feb 10 21:19:59 alarmpi kernel: On node 0 totalpages: 242688
Feb 10 21:19:59 alarmpi kernel: DMA zone: 2133 pages used for memmap
Feb 10 21:19:59 alarmpi kernel: DMA zone: 0 pages reserved
Feb 10 21:19:59 alarmpi kernel: DMA zone: 242688 pages, LIFO batch:63
Feb 10 21:19:59 alarmpi kernel: percpu: Embedded 20 pages/cpu s51084 r8192 d22644 u81920
Feb 10 21:19:59 alarmpi kernel: pcpu-alloc: s51084 r8192 d22644 u81920 alloc=20*4096
Feb 10 21:19:59 alarmpi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Feb 10 21:19:59 alarmpi kernel: Built 1 zonelists, mobility grouping on. Total pages: 240555
Feb 10 21:19:59 alarmpi kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 root=/dev/sda2 rw rootwait console=ttyS0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyS0,115200
Feb 10 21:19:59 alarmpi kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: mem auto-init: stack:off, heap alloc:off, heap free:off
Feb 10 21:19:59 alarmpi kernel: Memory: 670776K/970752K available (13312K kernel code, 1499K rwdata, 3756K rodata, 1024K init, 915K bss, 37832K reserved, 262144K cma-reserved, 0K highmem)
Feb 10 21:19:59 alarmpi kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Feb 10 21:19:59 alarmpi kernel: rcu: Hierarchical RCU implementation.
Feb 10 21:19:59 alarmpi kernel: Tracing variant of Tasks RCU enabled.
Feb 10 21:19:59 alarmpi kernel: rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Feb 10 21:19:59 alarmpi kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Feb 10 21:19:59 alarmpi kernel: random: get_random_bytes called from start_kernel+0x340/0x588 with crng_init=1
Feb 10 21:19:59 alarmpi kernel: arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Feb 10 21:19:59 alarmpi kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Feb 10 21:19:59 alarmpi kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Feb 10 21:19:59 alarmpi kernel: Switching to timer-based delay loop, resolution 52ns
Feb 10 21:19:59 alarmpi kernel: Console: colour dummy device 80x30
Feb 10 21:19:59 alarmpi kernel: printk: console [tty1] enabled
Feb 10 21:19:59 alarmpi kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Feb 10 21:19:59 alarmpi kernel: pid_max: default: 32768 minimum: 301
Feb 10 21:19:59 alarmpi kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: cgroup: Disabling memory control group subsystem
Feb 10 21:19:59 alarmpi kernel: CPU: Testing write buffer coherency: ok
Feb 10 21:19:59 alarmpi kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Feb 10 21:19:59 alarmpi kernel: Setting up static identity map for 0x100000 - 0x100054
Feb 10 21:19:59 alarmpi kernel: rcu: Hierarchical SRCU implementation.
Feb 10 21:19:59 alarmpi kernel: smp: Bringing up secondary CPUs ...
Feb 10 21:19:59 alarmpi kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Feb 10 21:19:59 alarmpi kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Feb 10 21:19:59 alarmpi kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Feb 10 21:19:59 alarmpi kernel: smp: Brought up 1 node, 4 CPUs
Feb 10 21:19:59 alarmpi kernel: SMP: Total of 4 processors activated (153.60 BogoMIPS).
Feb 10 21:19:59 alarmpi kernel: CPU: All CPU(s) started in HYP mode.
Feb 10 21:19:59 alarmpi kernel: CPU: Virtualization extensions available.
Feb 10 21:19:59 alarmpi kernel: devtmpfs: initialized
Feb 10 21:19:59 alarmpi kernel: VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Feb 10 21:19:59 alarmpi kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Feb 10 21:19:59 alarmpi kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: pinctrl core: initialized pinctrl subsystem
Feb 10 21:19:59 alarmpi kernel: NET: Registered protocol family 16
Feb 10 21:19:59 alarmpi kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations
Feb 10 21:19:59 alarmpi kernel: audit: initializing netlink subsys (disabled)
Feb 10 21:19:59 alarmpi kernel: audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
Feb 10 21:19:59 alarmpi kernel: thermal_sys: Registered thermal governor 'step_wise'
Feb 10 21:19:59 alarmpi kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Feb 10 21:19:59 alarmpi kernel: hw-breakpoint: maximum watchpoint size is 8 bytes.
Feb 10 21:19:59 alarmpi kernel: Serial: AMBA PL011 UART driver
Feb 10 21:19:59 alarmpi kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Feb 10 21:19:59 alarmpi kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2022-02-04T12:11:20, variant start
Feb 10 21:19:59 alarmpi kernel: raspberrypi-firmware soc:firmware: Firmware hash is a26faf97e3bf76bcc23949d7cdab2f96f399a0c3
Feb 10 21:19:59 alarmpi kernel: Kprobes globally optimized
Feb 10 21:19:59 alarmpi kernel: cryptd: max_cpu_qlen set to 1000
Feb 10 21:19:59 alarmpi kernel: raid6: neonx8 gen() 622 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx8 xor() 458 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx4 gen() 976 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx4 xor() 674 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx2 gen() 917 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx2 xor() 644 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx1 gen() 762 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: neonx1 xor() 522 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x8 gen() 200 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x8 xor() 125 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x4 gen() 208 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x4 xor() 141 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x2 gen() 290 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x2 xor() 147 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x1 gen() 242 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: int32x1 xor() 131 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: using algorithm neonx4 gen() 976 MB/s
Feb 10 21:19:59 alarmpi kernel: raid6: .... xor() 674 MB/s, rmw enabled
Feb 10 21:19:59 alarmpi kernel: raid6: using neon recovery algorithm
Feb 10 21:19:59 alarmpi kernel: bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Feb 10 21:19:59 alarmpi kernel: iommu: Default domain type: Translated
Feb 10 21:19:59 alarmpi kernel: vgaarb: loaded
Feb 10 21:19:59 alarmpi kernel: SCSI subsystem initialized
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver usbfs
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver hub
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new device driver usb
Feb 10 21:19:59 alarmpi kernel: clocksource: Switched to clocksource arch_sys_counter
Feb 10 21:19:59 alarmpi kernel: VFS: Disk quotas dquot_6.6.0
Feb 10 21:19:59 alarmpi kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 10 21:19:59 alarmpi kernel: FS-Cache: Loaded
Feb 10 21:19:59 alarmpi kernel: CacheFiles: Loaded
Feb 10 21:19:59 alarmpi kernel: simple-framebuffer 3e513000.framebuffer: framebuffer at 0x3e513000, 0x6e7000 bytes, mapped to 0x(ptrval)
Feb 10 21:19:59 alarmpi kernel: simple-framebuffer 3e513000.framebuffer: format=a8r8g8b8, mode=1824x984x32, linelength=7296
Feb 10 21:19:59 alarmpi kernel: Console: switching to colour frame buffer device 228x61
Feb 10 21:19:59 alarmpi kernel: simple-framebuffer 3e513000.framebuffer: fb0: simplefb registered!
Feb 10 21:19:59 alarmpi kernel: NET: Registered protocol family 2
Feb 10 21:19:59 alarmpi kernel: IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: TCP: Hash tables configured (established 8192 bind 8192)
Feb 10 21:19:59 alarmpi kernel: UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Feb 10 21:19:59 alarmpi kernel: NET: Registered protocol family 1
Feb 10 21:19:59 alarmpi kernel: RPC: Registered named UNIX socket transport module.
Feb 10 21:19:59 alarmpi kernel: RPC: Registered udp transport module.
Feb 10 21:19:59 alarmpi kernel: RPC: Registered tcp transport module.
Feb 10 21:19:59 alarmpi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Feb 10 21:19:59 alarmpi kernel: NET: Registered protocol family 44
Feb 10 21:19:59 alarmpi kernel: PCI: CLS 0 bytes, default 64
Feb 10 21:19:59 alarmpi kernel: Trying to unpack rootfs image as initramfs...
Feb 10 21:19:59 alarmpi kernel: Freeing initrd memory: 6688K
Feb 10 21:19:59 alarmpi kernel: hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Feb 10 21:19:59 alarmpi kernel: Initialise system trusted keyrings
Feb 10 21:19:59 alarmpi kernel: workingset: timestamp_bits=14 max_order=18 bucket_order=4
Feb 10 21:19:59 alarmpi kernel: zbud: loaded
Feb 10 21:19:59 alarmpi kernel: FS-Cache: Netfs 'nfs' registered for caching
Feb 10 21:19:59 alarmpi kernel: NFS: Registering the id_resolver key type
Feb 10 21:19:59 alarmpi kernel: Key type id_resolver registered
Feb 10 21:19:59 alarmpi kernel: Key type id_legacy registered
Feb 10 21:19:59 alarmpi kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Feb 10 21:19:59 alarmpi kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
Feb 10 21:19:59 alarmpi kernel: JFS: nTxBlock = 7340, nTxLock = 58725
Feb 10 21:19:59 alarmpi kernel: SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
Feb 10 21:19:59 alarmpi kernel: xor: measuring software checksum speed
Feb 10 21:19:59 alarmpi kernel: arm4regs : 948 MB/sec
Feb 10 21:19:59 alarmpi kernel: 8regs : 705 MB/sec
Feb 10 21:19:59 alarmpi kernel: 32regs : 634 MB/sec
Feb 10 21:19:59 alarmpi kernel: neon : 1213 MB/sec
Feb 10 21:19:59 alarmpi kernel: xor: using function: neon (1213 MB/sec)
Feb 10 21:19:59 alarmpi kernel: async_tx: api initialized (async)
Feb 10 21:19:59 alarmpi kernel: Key type asymmetric registered
Feb 10 21:19:59 alarmpi kernel: Asymmetric key parser 'x509' registered
Feb 10 21:19:59 alarmpi kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
Feb 10 21:19:59 alarmpi kernel: io scheduler mq-deadline registered
Feb 10 21:19:59 alarmpi kernel: io scheduler kyber registered
Feb 10 21:19:59 alarmpi kernel: io scheduler bfq registered
Feb 10 21:19:59 alarmpi kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Feb 10 21:19:59 alarmpi kernel: gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Feb 10 21:19:59 alarmpi kernel: loop: module loaded
Feb 10 21:19:59 alarmpi kernel: Loading iSCSI transport class v2.0-870.
Feb 10 21:19:59 alarmpi kernel: libphy: Fixed MDIO Bus: probed
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver lan78xx
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ax88179_178a
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver cdc_ether
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver r8153_ecm
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver smsc95xx
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver cdc_ncm
Feb 10 21:19:59 alarmpi kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Feb 10 21:19:59 alarmpi kernel: Core Release: 2.80a
Feb 10 21:19:59 alarmpi kernel: Setting default values for core params
Feb 10 21:19:59 alarmpi kernel: Finished setting default values for core params
Feb 10 21:19:59 alarmpi kernel: Using Buffer DMA mode
Feb 10 21:19:59 alarmpi kernel: Periodic Transfer Interrupt Enhancement - disabled
Feb 10 21:19:59 alarmpi kernel: Multiprocessor Interrupt Enhancement - disabled
Feb 10 21:19:59 alarmpi kernel: OTG VER PARAM: 0, OTG VER FLAG: 0
Feb 10 21:19:59 alarmpi kernel: Dedicated Tx FIFOs mode
Feb 10 21:19:59 alarmpi kernel:
Feb 10 21:19:59 alarmpi kernel: WARN::dwc_otg_hcd_init:1072: FIQ DMA bounce buffers: virt = 9e904000 dma = 0xde904000 len=9024
Feb 10 21:19:59 alarmpi kernel: FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
Feb 10 21:19:59 alarmpi kernel: dwc_otg: Microframe scheduler enabled
Feb 10 21:19:59 alarmpi kernel:
Feb 10 21:19:59 alarmpi kernel: WARN::hcd_init_fiq:457: FIQ on core 1
Feb 10 21:19:59 alarmpi kernel:
Feb 10 21:19:59 alarmpi kernel: WARN::hcd_init_fiq:458: FIQ ASM at 80a552dc length 36
Feb 10 21:19:59 alarmpi kernel:
Feb 10 21:19:59 alarmpi kernel: WARN::hcd_init_fiq:496: MPHI regs_base at bb810000
Feb 10 21:19:59 alarmpi kernel: dwc_otg 3f980000.usb: DWC OTG Controller
Feb 10 21:19:59 alarmpi kernel: dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Feb 10 21:19:59 alarmpi kernel: dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
Feb 10 21:19:59 alarmpi kernel: Init: Port Power? op_state=1
Feb 10 21:19:59 alarmpi kernel: Init: Power Port (0)
Feb 10 21:19:59 alarmpi kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
Feb 10 21:19:59 alarmpi kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 10 21:19:59 alarmpi kernel: usb usb1: Product: DWC OTG Controller
Feb 10 21:19:59 alarmpi kernel: usb usb1: Manufacturer: Linux 5.10.92-2-rpi-legacy-ARCH dwc_otg_hcd
Feb 10 21:19:59 alarmpi kernel: usb usb1: SerialNumber: 3f980000.usb
Feb 10 21:19:59 alarmpi kernel: hub 1-0:1.0: USB hub found
Feb 10 21:19:59 alarmpi kernel: hub 1-0:1.0: 1 port detected
Feb 10 21:19:59 alarmpi kernel: dwc_otg: FIQ enabled
Feb 10 21:19:59 alarmpi kernel: dwc_otg: NAK holdoff enabled
Feb 10 21:19:59 alarmpi kernel: dwc_otg: FIQ split-transaction FSM enabled
Feb 10 21:19:59 alarmpi kernel: Module dwc_common_port init
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver uas
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver usb-storage
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-alauda
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-cypress
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-datafab
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums_eneub6250
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-freecom
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-isd200
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-jumpshot
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-karma
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-onetouch
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-realtek
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-sddr09
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-sddr55
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver ums-usbat
Feb 10 21:19:59 alarmpi kernel: mousedev: PS/2 mouse device common for all mice
Feb 10 21:19:59 alarmpi kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Feb 10 21:19:59 alarmpi kernel: device-mapper: uevent: version 1.0.3
Feb 10 21:19:59 alarmpi kernel: device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
Feb 10 21:19:59 alarmpi kernel: device-mapper: multipath round-robin: version 1.2.0 loaded
Feb 10 21:19:59 alarmpi kernel: device-mapper: multipath queue-length: version 0.2.0 loaded
Feb 10 21:19:59 alarmpi kernel: device-mapper: multipath service-time: version 0.3.0 loaded
Feb 10 21:19:59 alarmpi kernel: device-mapper: raid: Loading target version 1.15.1
Feb 10 21:19:59 alarmpi kernel: Indeed it is in host mode hprt0 = 00021501
Feb 10 21:19:59 alarmpi kernel: sdhci: Secure Digital Host Controller Interface driver
Feb 10 21:19:59 alarmpi kernel: sdhci: Copyright(c) Pierre Ossman
Feb 10 21:19:59 alarmpi kernel: mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Feb 10 21:19:59 alarmpi kernel: sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Feb 10 21:19:59 alarmpi kernel: Error: Driver 'sdhost-bcm2835' is already registered, aborting...
Feb 10 21:19:59 alarmpi kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Feb 10 21:19:59 alarmpi kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 10 21:19:59 alarmpi kernel: hid: raw HID events driver (C) Jiri Kosina
Feb 10 21:19:59 alarmpi kernel: usbcore: registered new interface driver usbhid
Feb 10 21:19:59 alarmpi kernel: usbhid: USB HID core driver
Feb 10 21:19:59 alarmpi kernel: bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Feb 10 21:19:59 alarmpi kernel: [vc_sm_connected_init]: start
Feb 10 21:19:59 alarmpi kernel: [vc_sm_connected_init]: installed successfully
Feb 10 21:19:59 alarmpi kernel: Initializing XFRM netlink socket
Feb 10 21:19:59 alarmpi kernel: NET: Registered protocol family 17
Feb 10 21:19:59 alarmpi kernel: Key type dns_resolver registered
Feb 10 21:19:59 alarmpi kernel: Registering SWP/SWPB emulation handler
Feb 10 21:19:59 alarmpi kernel: registered taskstats version 1
Feb 10 21:19:59 alarmpi kernel: Loading compiled-in X.509 certificates
Feb 10 21:19:59 alarmpi kernel: Key type ._fscrypt registered
Feb 10 21:19:59 alarmpi kernel: Key type .fscrypt registered
Feb 10 21:19:59 alarmpi kernel: Key type fscrypt-provisioning registered
Feb 10 21:19:59 alarmpi kernel: Btrfs loaded, crc32c=crc32c-generic
Feb 10 21:19:59 alarmpi kernel: Key type encrypted registered
Feb 10 21:19:59 alarmpi kernel: uart-pl011 3f201000.serial: cts_event_workaround enabled
Feb 10 21:19:59 alarmpi kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2
Feb 10 21:19:59 alarmpi kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Feb 10 21:19:59 alarmpi kernel: mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Feb 10 21:19:59 alarmpi kernel: mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Feb 10 21:19:59 alarmpi kernel: sdhost: log_buf @ (ptrval) (de903000)
Feb 10 21:19:59 alarmpi kernel: usb 1-1: new high-speed USB device number 2 using dwc_otg
Feb 10 21:19:59 alarmpi kernel: Indeed it is in host mode hprt0 = 00001101
Feb 10 21:19:59 alarmpi kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Feb 10 21:19:59 alarmpi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Feb 10 21:19:59 alarmpi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Feb 10 21:19:59 alarmpi kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Feb 10 21:19:59 alarmpi kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Feb 10 21:19:59 alarmpi kernel: of_cfs_init
Feb 10 21:19:59 alarmpi kernel: of_cfs_init: OK
Feb 10 21:19:59 alarmpi kernel: Freeing unused kernel memory: 1024K
Feb 10 21:19:59 alarmpi kernel: Run /init as init process
Feb 10 21:19:59 alarmpi kernel: with arguments:
Feb 10 21:19:59 alarmpi kernel: /init
Feb 10 21:19:59 alarmpi kernel: with environment:
Feb 10 21:19:59 alarmpi kernel: HOME=/
Feb 10 21:19:59 alarmpi kernel: TERM=linux
Feb 10 21:19:59 alarmpi kernel: selinux=0
Feb 10 21:19:59 alarmpi kernel: kgdboc=ttyS0,115200
Feb 10 21:19:59 alarmpi kernel: mmc1: new high speed SDIO card at address 0001
Feb 10 21:19:59 alarmpi kernel: usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Feb 10 21:19:59 alarmpi kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 10 21:19:59 alarmpi kernel: hub 1-1:1.0: USB hub found
Feb 10 21:19:59 alarmpi kernel: hub 1-1:1.0: 4 ports detected
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 10 21:19:59 alarmpi kernel: hub 1-1.1:1.0: USB hub found
Feb 10 21:19:59 alarmpi kernel: hub 1-1.1:1.0: 3 ports detected
Feb 10 21:19:59 alarmpi kernel: usb 1-1.2: new full-speed USB device number 4 using dwc_otg
Feb 10 21:19:59 alarmpi kernel: usb 1-1.2: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.01
Feb 10 21:19:59 alarmpi kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 10 21:19:59 alarmpi kernel: usb 1-1.2: Product: USB Receiver
Feb 10 21:19:59 alarmpi kernel: usb 1-1.2: Manufacturer: Logitech
Feb 10 21:19:59 alarmpi kernel: input: Logitech USB Receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C52B.0001/input/input0
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg
Feb 10 21:19:59 alarmpi kernel: hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-3f980000.usb-1.2/input0
Feb 10 21:19:59 alarmpi kernel: input: Logitech USB Receiver Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:046D:C52B.0002/input/input1
Feb 10 21:19:59 alarmpi kernel: input: Logitech USB Receiver Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:046D:C52B.0002/input/input2
Feb 10 21:19:59 alarmpi kernel: input: Logitech USB Receiver System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:046D:C52B.0002/input/input3
Feb 10 21:19:59 alarmpi kernel: hid-generic 0003:046D:C52B.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-3f980000.usb-1.2/input1
Feb 10 21:19:59 alarmpi kernel: hid-generic 0003:046D:C52B.0003: hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.2/input2
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.2: New USB device found, idVendor=0781, idProduct=55a3, bcdDevice= 1.00
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.2: Product: SanDisk 3.2Gen1
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.2: Manufacturer: USB
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.2: SerialNumber: 0101880e5f1f575bb0650a8cfab46553c085b427c799e9efa2cd6a2bb4feb344b3b00000000000000000000086f653acff1d0a00a3558107b62896f0
Feb 10 21:19:59 alarmpi kernel: usb-storage 1-1.1.2:1.0: USB Mass Storage device detected
Feb 10 21:19:59 alarmpi kernel: scsi host0: usb-storage 1-1.1.2:1.0
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.1: new high-speed USB device number 6 using dwc_otg
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
Feb 10 21:19:59 alarmpi kernel: usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 10 21:19:59 alarmpi kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
Feb 10 21:19:59 alarmpi kernel: libphy: lan78xx-mdiobus: probed
Feb 10 21:19:59 alarmpi kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
Feb 10 21:19:59 alarmpi kernel: scsi 0:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
Feb 10 21:19:59 alarmpi kernel: sd 0:0:0:0: [sda] 240353280 512-byte logical blocks: (123 GB/115 GiB)
Feb 10 21:19:59 alarmpi kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 10 21:19:59 alarmpi kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Feb 10 21:19:59 alarmpi kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 10 21:19:59 alarmpi kernel: sda: sda1 sda2
Feb 10 21:19:59 alarmpi kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Feb 10 21:19:59 alarmpi kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Feb 10 21:19:59 alarmpi kernel: random: crng init done
Feb 10 21:19:59 alarmpi systemd[1]: System time before build time, advancing clock.
Feb 10 21:19:59 alarmpi kernel: NET: Registered protocol family 10
Feb 10 21:19:59 alarmpi kernel: Segment Routing with IPv6
Feb 10 21:19:59 alarmpi systemd[1]: systemd 250.3-4-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
Feb 10 21:19:59 alarmpi systemd[1]: Detected architecture arm.
Feb 10 21:19:59 alarmpi systemd[1]: Hostname set to <alarmpi>.
Feb 10 21:19:59 alarmpi systemd[1]: Queued start job for default target Graphical Interface.
Feb 10 21:19:59 alarmpi systemd[1]: Created slice Slice /system/getty.
Feb 10 21:19:59 alarmpi systemd[1]: Created slice Slice /system/modprobe.
Feb 10 21:19:59 alarmpi systemd[1]: Created slice User and Session Slice.
Feb 10 21:19:59 alarmpi systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Feb 10 21:19:59 alarmpi systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Feb 10 21:19:59 alarmpi systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Local Encrypted Volumes.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Local Integrity Protected Volumes.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Path Units.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Remote File Systems.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Slice Units.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Swaps.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target System Time Set.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Local Verity Protected Volumes.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on Device-mapper event daemon FIFOs.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on Process Core Dump Socket.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on Journal Audit Socket.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on Journal Socket (/dev/log).
Feb 10 21:19:59 alarmpi systemd[1]: Listening on Journal Socket.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on Network Service Netlink Socket.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on udev Control Socket.
Feb 10 21:19:59 alarmpi systemd[1]: Listening on udev Kernel Socket.
Feb 10 21:19:59 alarmpi systemd[1]: Huge Pages File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/mm/hugepages).
Feb 10 21:19:59 alarmpi systemd[1]: Mounting POSIX Message Queue File System...
Feb 10 21:19:59 alarmpi systemd[1]: Mounting Kernel Debug File System...
Feb 10 21:19:59 alarmpi systemd[1]: Mounting Kernel Trace File System...
Feb 10 21:19:59 alarmpi systemd[1]: Mounting Temporary Directory /tmp...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Create List of Static Device Nodes...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Load Kernel Module configfs...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Load Kernel Module drm...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Load Kernel Module fuse...
Feb 10 21:19:59 alarmpi kernel: fuse: init (API version 7.32)
Feb 10 21:19:59 alarmpi systemd[1]: Starting Load Kernel Modules...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Remount Root and Kernel File Systems...
Feb 10 21:19:59 alarmpi systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
Feb 10 21:19:59 alarmpi systemd[1]: Starting Coldplug All udev Devices...
Feb 10 21:19:59 alarmpi systemd[1]: Mounted POSIX Message Queue File System.
Feb 10 21:19:59 alarmpi systemd[1]: Mounted Kernel Debug File System.
Feb 10 21:19:59 alarmpi systemd[1]: Mounted Kernel Trace File System.
Feb 10 21:19:59 alarmpi kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Feb 10 21:19:59 alarmpi systemd[1]: Mounted Temporary Directory /tmp.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Create List of Static Device Nodes.
Feb 10 21:19:59 alarmpi systemd[1]: modprobe@configfs.service: Deactivated successfully.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Load Kernel Module configfs.
Feb 10 21:19:59 alarmpi systemd[1]: modprobe@drm.service: Deactivated successfully.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Load Kernel Module drm.
Feb 10 21:19:59 alarmpi systemd[1]: modprobe@fuse.service: Deactivated successfully.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Load Kernel Module fuse.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Load Kernel Modules.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Remount Root and Kernel File Systems.
Feb 10 21:19:59 alarmpi systemd[1]: Mounting FUSE Control File System...
Feb 10 21:19:59 alarmpi systemd[1]: Mounting Kernel Configuration File System...
Feb 10 21:19:59 alarmpi systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Feb 10 21:19:59 alarmpi systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Feb 10 21:19:59 alarmpi systemd[1]: Starting Load/Save Random Seed...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Apply Kernel Variables...
Feb 10 21:19:59 alarmpi systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Feb 10 21:19:59 alarmpi systemd[1]: Starting Create Static Device Nodes in /dev...
Feb 10 21:19:59 alarmpi systemd[1]: Mounted FUSE Control File System.
Feb 10 21:19:59 alarmpi systemd[1]: Mounted Kernel Configuration File System.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Load/Save Random Seed.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Coldplug All udev Devices.
Feb 10 21:19:59 alarmpi systemd[1]: Finished Apply Kernel Variables.
Feb 10 21:19:59 alarmpi systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Feb 10 21:19:59 alarmpi systemd[1]: Finished Create Static Device Nodes in /dev.
Feb 10 21:19:59 alarmpi systemd[1]: Reached target Preparation for Local File Systems.
Feb 10 21:19:59 alarmpi systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of a failed condition check (ConditionPathExists=/var/lib/machines.raw).
Feb 10 21:19:59 alarmpi systemd[1]: Entropy Daemon based on the HAVEGE algorithm was skipped because of a failed condition check (ConditionKernelVersion=<5.6).
Feb 10 21:19:59 alarmpi systemd[1]: Starting Journal Service...
Feb 10 21:19:59 alarmpi systemd[1]: Starting Rule-based Manager for Device Events and Files...
Feb 10 21:19:59 alarmpi systemd[1]: Started Rule-based Manager for Device Events and Files.
Feb 10 21:19:59 alarmpi systemd-journald[235]: Journal started
░░ Subject: The journal has been started
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system journal process has started up, opened the journal
░░ files for writing and is now ready to process requests.
Feb 10 21:19:59 alarmpi systemd-journald[235]: Runtime Journal (/run/log/journal/482ec136e30f4927ba34dd17f45bec68) is 5.7M, max 45.9M, 40.1M free.
░░ Subject: Disk space used by the journal
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Runtime Journal (/run/log/journal/482ec136e30f4927ba34dd17f45bec68) is currently using 5.7M.
░░ Maximum allowed usage is set to 45.9M.
░░ Leaving at least 22.9M free (of currently available 453.5M of disk space).
░░ Enforced usage limit is thus 45.9M, of which 40.1M 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.
Feb 10 21:19:58 alarmpi systemd-modules-load[225]: Inserted module 'crypto_user'
Feb 10 21:19:58 alarmpi systemd-modules-load[225]: Inserted module 'snd_bcm2835'
Feb 10 21:19:59 alarmpi kernel: audit: type=1130 audit(1644520799.419:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:19:59 alarmpi systemd[1]: Started Journal Service.
Feb 10 21:19:59 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:19:59 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:19:59 alarmpi kernel: audit: type=1130 audit(1644520799.459:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:19:59 alarmpi systemd[1]: Starting Flush Journal to Persistent Storage...
░░ Subject: A start job for unit systemd-journal-flush.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-journal-flush.service has begun execution.
░░
░░ The job identifier is 52.
Feb 10 21:19:59 alarmpi audit: BPF prog-id=9 op=LOAD
Feb 10 21:19:59 alarmpi systemd[1]: Starting Network Configuration...
░░ Subject: A start job for unit systemd-networkd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd.service has begun execution.
░░
░░ The job identifier is 75.
Feb 10 21:19:59 alarmpi kernel: audit: type=1334 audit(1644520799.499:4): prog-id=9 op=LOAD
Feb 10 21:19:59 alarmpi systemd-journald[235]: Time spent on flushing to /var/log/journal/482ec136e30f4927ba34dd17f45bec68 is 89.736ms for 409 entries.
Feb 10 21:19:59 alarmpi systemd-journald[235]: System Journal (/var/log/journal/482ec136e30f4927ba34dd17f45bec68) is 2.7G, max 3.2G, 521.5M free.
░░ Subject: Disk space used by the journal
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ System Journal (/var/log/journal/482ec136e30f4927ba34dd17f45bec68) is currently using 2.7G.
░░ Maximum allowed usage is set to 3.2G.
░░ Leaving at least 1.6G free (of currently available 97.8G of disk space).
░░ Enforced usage limit is thus 3.2G, of which 521.5M 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.
Feb 10 21:20:01 alarmpi systemd-journald[235]: Received client request to flush runtime journal.
Feb 10 21:20:01 alarmpi systemd-journald[235]: File /var/log/journal/482ec136e30f4927ba34dd17f45bec68/system.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 10 21:20:01 alarmpi kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 10 21:20:01 alarmpi kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Feb 10 21:20:01 alarmpi kernel: mc: Linux media interface: v0.10
Feb 10 21:20:01 alarmpi kernel: bcm2835-rng 3f104000.rng: hwrng registered
Feb 10 21:20:01 alarmpi kernel: videodev: Linux video capture interface: v2.00
Feb 10 21:20:01 alarmpi kernel: audit: type=1130 audit(1644520800.499:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:01 alarmpi kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Feb 10 21:20:01 alarmpi kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Feb 10 21:20:01 alarmpi kernel: bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Feb 10 21:20:01 alarmpi kernel: bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video10
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 decode
Feb 10 21:20:01 alarmpi kernel: bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video11
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 encode
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video12
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16

')
Last edited by jyno on Fri Feb 25, 2022 1:46 pm, edited 1 time in total.
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [HELP] Replacing microSD with USB (RPI3+)

Postby jyno » Fri Feb 25, 2022 1:46 pm

Part 2 of journalctl -xb:
$this->bbcode_second_pass_code('', '
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 isp
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register output node 0 with media controller
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video18
Feb 10 21:20:01 alarmpi kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register output node 0 with media controller
Feb 10 21:20:01 alarmpi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
Feb 10 21:20:01 alarmpi kernel: usbcore: registered new interface driver brcmfmac
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
Feb 10 21:20:01 alarmpi kernel: bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
Feb 10 21:20:01 alarmpi kernel: checking generic (3e513000 6e7000) vs hw (0 ffffffff)
Feb 10 21:20:01 alarmpi kernel: fb0: switching to vc4drmfb from simple
Feb 10 21:20:01 alarmpi kernel: Console: switching to colour dummy device 80x30
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: Bluetooth: Core ver 2.22
Feb 10 21:20:01 alarmpi kernel: NET: Registered protocol family 31
Feb 10 21:20:01 alarmpi kernel: Bluetooth: HCI device and connection manager initialized
Feb 10 21:20:01 alarmpi kernel: Bluetooth: HCI socket layer initialized
Feb 10 21:20:01 alarmpi kernel: Bluetooth: L2CAP socket layer initialized
Feb 10 21:20:01 alarmpi kernel: Bluetooth: SCO socket layer initialized
Feb 10 21:20:00 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:00 alarmpi systemd-networkd[248]: lo: Link UP
Feb 10 21:20:00 alarmpi systemd-networkd[248]: lo: Gained carrier
Feb 10 21:20:00 alarmpi systemd-networkd[248]: Enumeration completed
Feb 10 21:20:00 alarmpi systemd[1]: Started Network Configuration.
░░ Subject: A start job for unit systemd-networkd.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd.service has finished successfully.
░░
░░ The job identifier is 75.
Feb 10 21:20:00 alarmpi systemd[1]: Starting Wait for Network to be Configured...
░░ Subject: A start job for unit systemd-networkd-wait-online.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd-wait-online.service has begun execution.
░░
░░ The job identifier is 86.
Feb 10 21:20:00 alarmpi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
░░ Subject: A start job for unit systemd-rfkill.socket has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-rfkill.socket has finished successfully.
░░
░░ The job identifier is 105.
Feb 10 21:20:00 alarmpi systemd-udevd[243]: Using default interface naming scheme 'v250'.
Feb 10 21:20:01 alarmpi systemd-networkd[248]: eth0: Link UP
Feb 10 21:20:01 alarmpi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Feb 10 21:20:01 alarmpi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Feb 10 21:20:01 alarmpi kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2
Feb 10 21:20:01 alarmpi systemd[1]: Finished Flush Journal to Persistent Storage.
░░ Subject: A start job for unit systemd-journal-flush.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-journal-flush.service has finished successfully.
░░
░░ The job identifier is 52.
Feb 10 21:20:01 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:01 alarmpi kernel: audit: type=1130 audit(1644520801.259:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:01 alarmpi systemd[1]: Starting Load/Save RF Kill Switch Status...
░░ Subject: A start job for unit systemd-rfkill.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-rfkill.service has begun execution.
░░
░░ The job identifier is 111.
Feb 10 21:20:01 alarmpi kernel: logitech-djreceiver 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.2/input2
Feb 10 21:20:01 alarmpi systemd-udevd[237]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: input: Logitech Wireless Device PID:4024 Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input5
Feb 10 21:20:01 alarmpi kernel: input: Logitech Wireless Device PID:4024 Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input6
Feb 10 21:20:01 alarmpi kernel: input: Logitech Wireless Device PID:4024 Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input7
Feb 10 21:20:01 alarmpi kernel: hid-generic 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4024] on usb-3f980000.usb-1.2/input2:1
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
Feb 10 21:20:01 alarmpi systemd-udevd[238]: Using default interface naming scheme 'v250'.
Feb 10 21:20:01 alarmpi systemd[1]: Started Load/Save RF Kill Switch Status.
░░ Subject: A start job for unit systemd-rfkill.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-rfkill.service has finished successfully.
░░
░░ The job identifier is 111.
Feb 10 21:20:01 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
Feb 10 21:20:01 alarmpi kernel: audit: type=1130 audit(1644520801.799:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:01 alarmpi kernel: [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
Feb 10 21:20:01 alarmpi kernel: Console: switching to colour frame buffer device 240x67
Feb 10 21:20:01 alarmpi kernel: vc4-drm soc:gpu: [drm] fb0: vc4drmfb frame buffer device
Feb 10 21:20:02 alarmpi systemd-udevd[242]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Feb 10 21:20:02 alarmpi systemd[1]: Huge Pages File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/mm/hugepages).
░░ Subject: A start job for unit dev-hugepages.mount has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit dev-hugepages.mount has finished successfully.
░░
░░ The job identifier is 160.
Feb 10 21:20:02 alarmpi systemd[1]: Entropy Daemon based on the HAVEGE algorithm was skipped because of a failed condition check (ConditionKernelVersion=<5.6).
░░ Subject: A start job for unit haveged.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit haveged.service has finished successfully.
░░
░░ The job identifier is 147.
Feb 10 21:20:02 alarmpi systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-firstboot.service has finished successfully.
░░
░░ The job identifier is 176.
Feb 10 21:20:02 alarmpi systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
░░ Subject: A start job for unit first-boot-complete.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit first-boot-complete.target has finished successfully.
░░
░░ The job identifier is 150.
Feb 10 21:20:02 alarmpi systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
░░ Subject: A start job for unit systemd-hwdb-update.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-hwdb-update.service has finished successfully.
░░
░░ The job identifier is 131.
Feb 10 21:20:02 alarmpi systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
░░ Subject: A start job for unit systemd-repart.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-repart.service has finished successfully.
░░
░░ The job identifier is 159.
Feb 10 21:20:02 alarmpi systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
░░ Subject: A start job for unit systemd-sysusers.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-sysusers.service has finished successfully.
░░
░░ The job identifier is 158.
Feb 10 21:20:02 alarmpi kernel: input: Logitech K400 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input11
Feb 10 21:20:02 alarmpi kernel: logitech-hidpp-device 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-3f980000.usb-1.2/input2:1
Feb 10 21:20:02 alarmpi kernel: Under-voltage detected! (0x00050005)
Feb 10 21:20:06 alarmpi kernel: Voltage normalised (0x00000000)
Feb 10 21:20:06 alarmpi systemd[1]: systemd-rfkill.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-rfkill.service has successfully entered the 'dead' state.
Feb 10 21:20:06 alarmpi audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:06 alarmpi kernel: audit: type=1131 audit(1644520806.809:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:20:23 alarmpi kernel: cam1-reg: disabling
Feb 10 21:20:23 alarmpi kernel: cam-dummy-reg: disabling
Feb 10 21:21:28 alarmpi systemd[1]: dev-mmcblk0p1.device: Job dev-mmcblk0p1.device/start timed out.
Feb 10 21:21:28 alarmpi systemd[1]: Timed out waiting for device /dev/mmcblk0p1.
░░ Subject: A start job for unit dev-mmcblk0p1.device has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit dev-mmcblk0p1.device has finished with a failure.
░░
░░ The job identifier is 23 and the job result is timeout.
Feb 10 21:21:28 alarmpi systemd[1]: Dependency failed for /boot.
░░ Subject: A start job for unit boot.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has finished with a failure.
░░
░░ The job identifier is 22 and the job result is dependency.
Feb 10 21:21:28 alarmpi systemd[1]: Dependency failed for Local File Systems.
░░ Subject: A start job for unit local-fs.target has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit local-fs.target has finished with a failure.
░░
░░ The job identifier is 21 and the job result is dependency.
Feb 10 21:21:28 alarmpi systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Feb 10 21:21:28 alarmpi systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Feb 10 21:21:28 alarmpi systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
Feb 10 21:21:28 alarmpi systemd[1]: dev-mmcblk0p1.device: Job dev-mmcblk0p1.device/start failed with result 'timeout'.
Feb 10 21:21:28 alarmpi systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-ask-password-console.path has successfully entered the 'dead' state.
Feb 10 21:21:28 alarmpi systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
░░ Subject: A stop job for unit systemd-ask-password-console.path has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-ask-password-console.path has finished.
░░
░░ The job identifier is 190 and the job result is done.
Feb 10 21:21:28 alarmpi systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-ask-password-wall.path has successfully entered the 'dead' state.
Feb 10 21:21:28 alarmpi systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
░░ Subject: A stop job for unit systemd-ask-password-wall.path has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-ask-password-wall.path has finished.
░░
░░ The job identifier is 191 and the job result is done.
Feb 10 21:21:28 alarmpi systemd[1]: Reached target Timer Units.
░░ Subject: A start job for unit timers.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit timers.target has finished successfully.
░░
░░ The job identifier is 69.
Feb 10 21:21:28 alarmpi systemd[1]: Reached target Sound Card.
░░ Subject: A start job for unit sound.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sound.target has finished successfully.
░░
░░ The job identifier is 118.
Feb 10 21:21:28 alarmpi systemd[1]: Reached target Login Prompts.
░░ Subject: A start job for unit getty.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit getty.target has finished successfully.
░░
░░ The job identifier is 100.
Feb 10 21:21:28 alarmpi systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
░░ Subject: A start job for unit systemd-machine-id-commit.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-machine-id-commit.service has finished successfully.
░░
░░ The job identifier is 5.
Feb 10 21:21:28 alarmpi systemd[1]: Reached target Socket Units.
░░ Subject: A start job for unit sockets.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sockets.target has finished successfully.
░░
░░ The job identifier is 64.
Feb 10 21:21:28 alarmpi systemd[1]: Started Emergency Shell.
░░ Subject: A start job for unit emergency.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit emergency.service has finished successfully.
░░
░░ The job identifier is 182.
Feb 10 21:21:28 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi systemd[1]: Reached target Emergency Mode.
░░ Subject: A start job for unit emergency.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit emergency.target has finished successfully.
░░
░░ The job identifier is 181.
Feb 10 21:21:28 alarmpi systemd[1]: Rebuild Dynamic Linker Cache was skipped because all trigger condition checks failed.
░░ Subject: A start job for unit ldconfig.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit ldconfig.service has finished successfully.
░░
░░ The job identifier is 30.
Feb 10 21:21:28 alarmpi kernel: audit: type=1130 audit(1644520888.369:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed.
░░ Subject: A start job for unit systemd-binfmt.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-binfmt.service has finished successfully.
░░
░░ The job identifier is 48.
Feb 10 21:21:28 alarmpi systemd[1]: Starting Create Volatile Files and Directories...
░░ Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-tmpfiles-setup.service has begun execution.
░░
░░ The job identifier is 49.
Feb 10 21:21:28 alarmpi systemd[1]: Finished Create Volatile Files and Directories.
░░ Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-tmpfiles-setup.service has finished successfully.
░░
░░ The job identifier is 49.
Feb 10 21:21:28 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
░░ Subject: A start job for unit systemd-journal-catalog-update.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-journal-catalog-update.service has finished successfully.
░░
░░ The job identifier is 53.
Feb 10 21:21:28 alarmpi kernel: audit: type=1130 audit(1644520888.599:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi kernel: audit: type=1334 audit(1644520888.609:11): prog-id=10 op=LOAD
Feb 10 21:21:28 alarmpi audit: BPF prog-id=10 op=LOAD
Feb 10 21:21:28 alarmpi systemd[1]: Starting Network Name Resolution...
░░ Subject: A start job for unit systemd-resolved.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-resolved.service has begun execution.
░░
░░ The job identifier is 89.
Feb 10 21:21:28 alarmpi audit: BPF prog-id=11 op=LOAD
Feb 10 21:21:28 alarmpi kernel: audit: type=1334 audit(1644520888.619:12): prog-id=11 op=LOAD
Feb 10 21:21:28 alarmpi systemd[1]: Starting Network Time Synchronization...
░░ Subject: A start job for unit systemd-timesyncd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-timesyncd.service has begun execution.
░░
░░ The job identifier is 132.
Feb 10 21:21:28 alarmpi systemd[1]: Update is Completed was skipped because all trigger condition checks failed.
░░ Subject: A start job for unit systemd-update-done.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-done.service has finished successfully.
░░
░░ The job identifier is 47.
Feb 10 21:21:28 alarmpi systemd[1]: Starting Record System Boot/Shutdown in UTMP...
░░ Subject: A start job for unit systemd-update-utmp.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-utmp.service has begun execution.
░░
░░ The job identifier is 55.
Feb 10 21:21:28 alarmpi audit[312]: SYSTEM_BOOT pid=312 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi kernel: audit: type=1127 audit(1644520888.639:13): pid=312 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi systemd[1]: Finished Record System Boot/Shutdown in UTMP.
░░ Subject: A start job for unit systemd-update-utmp.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-utmp.service has finished successfully.
░░
░░ The job identifier is 55.
Feb 10 21:21:28 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi kernel: audit: type=1130 audit(1644520888.669:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 10 21:21:28 alarmpi systemd-timesyncd[311]: System clock time unset or jumped backwards, restoring from recorded timestamp: Thu 2022-02-24 07:07:03 IST
Feb 24 07:07:03 alarmpi systemd[1]: Started Network Time Synchronization.
░░ Subject: A start job for unit systemd-timesyncd.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-timesyncd.service has finished successfully.
░░
░░ The job identifier is 132.
Feb 24 07:07:03 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 07:07:03 alarmpi kernel: audit: type=1130 audit(1645679223.356:15): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 07:07:03 alarmpi systemd-resolved[310]: Positive Trust Anchors:
Feb 24 07:07:03 alarmpi systemd-resolved[310]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Feb 24 07:07:03 alarmpi systemd-resolved[310]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Feb 24 07:07:03 alarmpi systemd-resolved[310]: Using system hostname 'alarmpi'.
Feb 24 07:07:03 alarmpi systemd[1]: Started Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-resolved.service has finished successfully.
░░
░░ The job identifier is 89.
Feb 24 07:07:03 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-resolved comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 07:07:03 alarmpi systemd[1]: Reached target Network.
░░ Subject: A start job for unit network.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit network.target has finished successfully.
░░
░░ The job identifier is 76.
Feb 24 07:07:03 alarmpi systemd[1]: Reached target Host and Network Name Lookups.
░░ Subject: A start job for unit nss-lookup.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit nss-lookup.target has finished successfully.
░░
░░ The job identifier is 90.
Feb 24 07:07:03 alarmpi kernel: audit: type=1130 audit(1645679223.496:16): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-resolved comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 07:07:07 alarmpi systemd[308]: emergency.service: Executable /usr/bin/plymouth missing, skipping: No such file or directory
░░ Subject: Process /usr/bin/plymouth could not be executed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The process /usr/bin/plymouth could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Feb 24 07:07:35 alarmpi systemd-networkd-wait-online[257]: Timeout occurred while waiting for network connectivity.
Feb 24 07:07:35 alarmpi systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit systemd-networkd-wait-online.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Feb 24 07:07:35 alarmpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Feb 24 07:07:35 alarmpi systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-networkd-wait-online.service has entered the 'failed' state with result 'exit-code'.
Feb 24 07:07:35 alarmpi systemd[1]: Failed to start Wait for Network to be Configured.
░░ Subject: A start job for unit systemd-networkd-wait-online.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd-wait-online.service has finished with a failure.
░░
░░ The job identifier is 86 and the job result is failed.
Feb 24 07:07:35 alarmpi systemd[1]: Reached target Network is Online.
░░ Subject: A start job for unit network-online.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit network-online.target has finished successfully.
░░
░░ The job identifier is 85.
Feb 24 07:07:35 alarmpi systemd[1]: Startup finished in 11.371s (kernel) + 2min 3.889s (userspace) = 2min 15.260s.
░░ Subject: System start-up is now complete
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ 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 services
░░ might still be busy with completing start-up.
░░
░░ Kernel start-up required 11371090 microseconds.
░░
░░ Initial RAM disk start-up required INITRD_USEC microseconds.
░░
░░ Userspace start-up required 123889021 microseconds.
Feb 24 07:07:35 alarmpi kernel: audit: type=1130 audit(1645679255.306:17): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Feb 24 07:08:16 alarmpi kernel: logitech-hidpp-device 0003:046D:4024.0004: HID++ 2.0 device connected.
Feb 24 07:08:44 alarmpi kernel: Under-voltage detected! (0x00050005)
Feb 24 07:08:48 alarmpi kernel: Voltage normalised (0x00000000)
')
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [HELP] Replacing microSD with USB (RPI3+)

Postby robg » Fri Feb 25, 2022 4:21 pm

Please post the output of `cat /etc/fstab` and `cat /boot/config.txt`.
robg
 
Posts: 186
Joined: Tue Jan 05, 2021 8:22 am

Re: [HELP] Replacing microSD with USB (RPI3+)

Postby jyno » Sat Feb 26, 2022 5:20 pm

$this->bbcode_second_pass_code('', '
$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
/dev/mmcblk0p1 /boot vfat defaults 0 0
')

$this->bbcode_second_pass_code('', '
$ cat /boot/config.txt
# See /boot/overlays/README for all available options

dtoverlay=vc4-kms-v3d
initramfs initramfs-linux.img followkernel

# Uncomment to enable bluetooth
#dtparam=krnbt=on
')
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [HELP] Replacing microSD with USB (RPI3+)

Postby jyno » Sat Feb 26, 2022 5:45 pm

Replacing mmcblk0p1 by sda1 makes it work and enter into the regular login shell prompt.

Problem:
It seems that even when my login credentials are correct, it says otherwise and doesn't let me to login.
It says Login incorrect. (I've tried to login as alarm and root)
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [HELP] Replacing microSD with USB (RPI3+)

Postby jyno » Sat Feb 26, 2022 7:01 pm

I forgot to remove the microSD card.

After removing the microSD. It's working!
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [SOLVED] Replacing microSD with USB (RPI3+)

Postby jyno » Sun Feb 27, 2022 7:01 am

@robg please approve this post viewtopic.php?f=57&t=15913
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm

Re: [SOLVED] Replacing microSD with USB (RPI3+)

Postby robg » Sun Feb 27, 2022 5:07 pm

Glad to hear to you got it working!

I glanced over your tutorial. Thanks for contributing your findings, but without testing it myself, I will not "approve" it (not that you need my approval; this is a forum and people are free to discuss and extend your instructions.) But in any case, I have added some comments.
robg
 
Posts: 186
Joined: Tue Jan 05, 2021 8:22 am

Re: [SOLVED] Replacing microSD with USB (RPI3+)

Postby jyno » Mon Feb 28, 2022 2:58 pm

Certainly so. I must receive opinions and reports of others; experiences.
The main reason I ask for it, is to be sure that I'm doing ok for myself as well.
jyno
 
Posts: 67
Joined: Wed May 05, 2021 4:37 pm


Return to General

Who is online

Users browsing this forum: No registered users and 6 guests