brohan
Posts: 25
Joined: Fri Aug 16, 2019 2:47 am

Re: pi 4 32GB sd card doesn't work.

Sun Sep 01, 2019 3:08 pm

Result of minicom using the same cmd and fstab (similar results of if I leave the original UUID settings):

Code: Select all

sudo minicom -b 115200 -o -D /dev/ttyUSB0                       1 ↵  4  192.168.1.146  


Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Jun  5 2018, 10:54:41.
Port /dev/ttyUSB0, 08:06:33

Press CTRL-A Z for help on special keys

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.57-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG cro9
[    0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 256 MiB at 0x000000001ec00000
[    0.000000] On node 0 totalpages: 1012736
[    0.000000]   DMA zone: 1728 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 816128 pages, LIFO batch:63
[    0.000000] random: get_random_bytes called from start_kernel+0xc0/0x4e8 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu s39488 r8192 d21952 u69632
[    0.000000] pcpu-alloc: s39488 r8192 d21952 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1011008
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M  smsc95s
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 3735596K/4050944K available (8192K kernel code, 658K rwdata, 2340K rod)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
[    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
[    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 659 kB)
[    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   ( 851 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 27981 entries in 83 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346,s
[    0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000021] Switching to timer-based delay loop, resolution 18ns
[    0.000243] Console: colour dummy device 80x30
[    0.000795] console [tty1] enabled
[    0.000850] Calibrating delay loop (skipped), value calculated using timer frequency.. 108)
[    0.000892] pid_max: default: 32768 minimum: 301
[    0.001166] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001198] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001951] CPU: Testing write buffer coherency: ok
[    0.002359] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002989] Setting up static identity map for 0x200000 - 0x20003c
[    0.003161] rcu: Hierarchical SRCU implementation.
[    0.004013] smp: Bringing up secondary CPUs ...
[    0.004888] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.005865] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.006806] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.006936] smp: Brought up 1 node, 4 CPUs
[    0.007003] SMP: Total of 4 processors activated (432.00 BogoMIPS).
[    0.007026] CPU: All CPU(s) started in HYP mode.
[    0.007046] CPU: Virtualization extensions available.
[    0.007827] devtmpfs: initialized
[    0.017941] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0
[    0.018180] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19s
[    0.018221] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.025499] pinctrl core: initialized pinctrl subsystem
[    0.026338] NET: Registered protocol family 16
[    0.029060] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.030508] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.030540] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.030740] Serial: AMBA PL011 UART driver
[    0.033767] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[    0.069645] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[    0.072091] vgaarb: loaded
[    0.072472] SCSI subsystem initialized
[    0.072680] usbcore: registered new interface driver usbfs
[    0.072745] usbcore: registered new interface driver hub
[    0.072853] usbcore: registered new device driver usb
[    0.090379] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-07-09 14:37,t
[    0.100108] raspberrypi-firmware soc:firmware: Firmware hash is d2b1b7fb01475cb3914b2086291
[    0.111592] clocksource: Switched to clocksource arch_sys_counter
[    0.188187] VFS: Disk quotas dquot_6.6.0
[    0.188279] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.188438] FS-Cache: Loaded
[    0.188621] CacheFiles: Loaded
[    0.189129] simple-framebuffer: probe of 0.framebuffer failed with error -12
[    0.198147] NET: Registered protocol family 2
[    0.198803] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.198848] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.198929] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.199013] TCP: Hash tables configured (established 8192 bind 8192)
[    0.199139] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.199181] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.199480] NET: Registered protocol family 1
[    0.200009] RPC: Registered named UNIX socket transport module.
[    0.200035] RPC: Registered udp transport module.
[    0.200057] RPC: Registered tcp transport module.
[    0.200078] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.200105] PCI: CLS 0 bytes, default 64
[    0.203154] Initialise system trusted keyrings
[    0.203333] workingset: timestamp_bits=14 max_order=20 bucket_order=6
[    0.212139] FS-Cache: Netfs 'nfs' registered for caching
[    0.212647] NFS: Registering the id_resolver key type
[    0.212688] Key type id_resolver registered
[    0.212709] Key type id_legacy registered
[    0.212740] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.214923] Key type asymmetric registered
[    0.214949] Asymmetric key parser 'x509' registered
[    0.215069] bounce: pool size: 64 pages
[    0.215124] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.215294] io scheduler noop registered
[    0.215318] io scheduler deadline registered (default)
[    0.215476] io scheduler cfq registered
[    0.215499] io scheduler mq-deadline registered (default)
[    0.215521] io scheduler kyber registered
[    0.238863] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x0000000
[    0.238908] brcm-pcie fd500000.pcie: could not get clock
[    0.238980] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    0.239031] brcm-pcie fd500000.pcie:   MEM 0x600000000..0x603ffffff -> 0xf8000000
[    0.291626] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)
[    0.291913] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[    0.291943] pci_bus 0000:00: root bus resource [bus 00-01]
[    0.291972] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address )
[    0.292034] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[    0.292180] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.294866] PCI: bus0: Fast back to back transfers disabled
[    0.294896] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.295075] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[    0.295148] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.295327] pci 0000:01:00.0: PME# supported from D0 D3cold
[    0.297944] PCI: bus1: Fast back to back transfers disabled
[    0.297974] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01
[    0.298033] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[    0.298066] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[    0.298113] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.298143] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
[    0.298215] pci 0000:00:00.0: enabling device (0140 -> 0142)
[    0.298251] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.300000] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.302004] iproc-rng200 fe104000.rng: hwrng registered
[    0.302237] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.302756] vc-sm: Videocore shared memory driver
[    0.303158] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    0.312909] brd: module loaded
[    0.322254] loop: module loaded
[    0.322995] Loading iSCSI transport class v2.0-870.
[    0.324625] libphy: Fixed MDIO Bus: probed
[    0.325054] bcmgenet fd580000.genet: failed to get enet clock
[    0.325085] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000
[    0.325115] bcmgenet fd580000.genet: failed to get enet-wol clock
[    0.325144] bcmgenet fd580000.genet: failed to get enet-eee clock
[    0.325410] unimac-mdio unimac-mdio.-19: DMA mask not set
[    0.341631] libphy: bcmgenet MII bus: probed
[    0.382111] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)
[    0.383004] usbcore: registered new interface driver r8152
[    0.383076] usbcore: registered new interface driver lan78xx
[    0.383141] usbcore: registered new interface driver smsc95xx
[    0.383405] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.383448] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    0.385197] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000000
[    0.385375] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 56
[    0.385997] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.386032] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.386062] usb usb1: Product: xHCI Host Controller
[    0.386086] usb usb1: Manufacturer: Linux 4.19.57-v7l+ xhci-hcd
[    0.386110] usb usb1: SerialNumber: 0000:01:00.0
[    0.386634] hub 1-0:1.0: USB hub found
[    0.386699] hub 1-0:1.0: 1 port detected
[    0.387112] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.387147] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    0.387183] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    0.387529] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    0.387563] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.387591] usb usb2: Product: xHCI Host Controller
[    0.387614] usb usb2: Manufacturer: Linux 4.19.57-v7l+ xhci-hcd
[    0.387637] usb usb2: SerialNumber: 0000:01:00.0
[    0.388140] hub 2-0:1.0: USB hub found
[    0.388205] hub 2-0:1.0: 4 ports detected
[    0.389296] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.414861] dwc_otg fe980000.usb: base=(ptrval)
[    0.615174] Core Release: 2.80a
[    0.615201] Setting default values for core params
[    0.615240] Finished setting default values for core params
[    0.815574] Using Buffer DMA mode
[    0.815597] Periodic Transfer Interrupt Enhancement - disabled
[    0.815620] Multiprocessor Interrupt Enhancement - disabled
[    0.815644] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.815713] Dedicated Tx FIFOs mode
[    0.816368] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = ded30000 dma = 0x04
[    0.816413] FIQ FSM acceleration enabled for :
[    0.816413] Non-periodic Split Transactions
[    0.816413] Periodic Split Transactions
[    0.816413] High-Speed Isochronous Endpoints
[    0.816413] Interrupt/Control Split Transaction hack enabled
[    0.816473] dwc_otg: Microframe scheduler enabled
[    0.816548] WARN::hcd_init_fiq:457: FIQ on core 1
[    0.816581] WARN::hcd_init_fiq:458: FIQ ASM at c07ae05c length 36
[    0.816612] WARN::hcd_init_fiq:497: MPHI regs_base at f0810200
[    0.816661] dwc_otg fe980000.usb: DWC OTG Controller
[    0.816703] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3
[    0.816760] dwc_otg fe980000.usb: irq 37, io mem 0x00000000
[    0.816823] Init: Port Power? op_state=1
[    0.816843] Init: Power Port (0)
[    0.817100] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.817134] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.817163] usb usb3: Product: DWC OTG Controller
[    0.817186] usb usb3: Manufacturer: Linux 4.19.57-v7l+ dwc_otg_hcd
[    0.817210] usb usb3: SerialNumber: fe980000.usb
[    0.817717] hub 3-0:1.0: USB hub found
[    0.817779] hub 3-0:1.0: 1 port detected
[    0.818356] dwc_otg: FIQ enabled
[    0.818377] dwc_otg: NAK holdoff enabled
[    0.818397] dwc_otg: FIQ split-transaction FSM enabled
[    0.818422] Module dwc_common_port init
[    0.818633] usbcore: registered new interface driver uas
[    0.818761] usbcore: registered new interface driver usb-storage
[    0.818943] mousedev: PS/2 mouse device common for all mice
[    0.820103] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    0.820295] bcm2835-cpufreq: min=600000 max=1500000
[    0.820854] sdhci: Secure Digital Host Controller Interface driver
[    0.820877] sdhci: Copyright(c) Pierre Ossman
[    0.821266] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[    0.821729] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.824669] ledtrig-cpu: registered to indicate activity on CPUs
[    0.824821] hidraw: raw HID events driver (C) Jiri Kosina
[    0.824960] usbcore: registered new interface driver usbhid
[    0.824983] usbhid: USB HID core driver
[    0.825688] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    0.826979] [vc_sm_connected_init]: start
[    0.833070] [vc_sm_connected_init]: end - returning 0
[    0.834126] Initializing XFRM netlink socket
[    0.834167] NET: Registered protocol family 17
[    0.834253] Key type dns_resolver registered
[    0.834642] Registering SWP/SWPB emulation handler
[    0.835223] registered taskstats version 1
[    0.835253] Loading compiled-in X.509 certificates
[    0.842919] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    0.843000] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 33, base_baud = 0) is a PL02
[    0.846234] console [ttyS0] disabled
[    0.846280] fe215040.serial: ttyS0 at MMIO 0x0 (irq = 35, base_baud = 62500000) is a 16550
[    0.989246] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    1.232051] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    1.232063] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.232073] usb 1-1: Product: USB2.0 Hub
[    2.283929] console [ttyS0] enabled
[    2.287927] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    2.295918] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver
[    2.304498] hub 1-1:1.0: USB hub found
[    2.308440] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    2.314599] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    2.320477] hub 1-1:1.0: 4 ports detected
[    2.350629] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    2.374888] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    2.382080] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.389249] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.394892] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[    2.404703] of_cfs_init
[    2.407270] of_cfs_init: OK
[    2.410660] Waiting for root device PARTUUID=408190a6-02...
[    2.419035] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    2.426232] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

brohan
Posts: 25
Joined: Fri Aug 16, 2019 2:47 am

Re: pi 4 32GB sd card doesn't work.

Sun Sep 01, 2019 3:35 pm

And the same sdcard outpout in my new "good" pi:

Code: Select all

sudo minicom -b 115200 -o -D /dev/ttyUSB0

Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Jun  5 2018, 10:54:41.
Port /dev/ttyUSB0, 08:32:12

Press CTRL-A Z for help on special keys

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.57-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG cro9
[    0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 256 MiB at 0x000000001ec00000
[    0.000000] On node 0 totalpages: 1012736
[    0.000000]   DMA zone: 1728 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 816128 pages, LIFO batch:63
[    0.000000] random: get_random_bytes called from start_kernel+0xc0/0x4e8 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu s39488 r8192 d21952 u69632
[    0.000000] pcpu-alloc: s39488 r8192 d21952 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1011008
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M  smsc95s
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 3735596K/4050944K available (8192K kernel code, 658K rwdata, 2340K rod)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
[    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
[    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 659 kB)
[    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   ( 851 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 27981 entries in 83 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346,s
[    0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000021] Switching to timer-based delay loop, resolution 18ns
[    0.000245] Console: colour dummy device 80x30
[    0.000821] console [tty1] enabled
[    0.000874] Calibrating delay loop (skipped), value calculated using timer frequency.. 108)
[    0.000917] pid_max: default: 32768 minimum: 301
[    0.001191] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001223] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001980] CPU: Testing write buffer coherency: ok
[    0.002391] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.003022] Setting up static identity map for 0x200000 - 0x20003c
[    0.003193] rcu: Hierarchical SRCU implementation.
[    0.004044] smp: Bringing up secondary CPUs ...
[    0.004916] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.005897] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.006840] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.006971] smp: Brought up 1 node, 4 CPUs
[    0.007038] SMP: Total of 4 processors activated (432.00 BogoMIPS).
[    0.007061] CPU: All CPU(s) started in HYP mode.
[    0.007081] CPU: Virtualization extensions available.
[    0.007860] devtmpfs: initialized
[    0.017979] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0
[    0.018215] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19s
[    0.018256] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.025532] pinctrl core: initialized pinctrl subsystem
[    0.026365] NET: Registered protocol family 16
[    0.029090] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.030535] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.030567] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.030766] Serial: AMBA PL011 UART driver
[    0.033785] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[    0.069617] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[    0.072067] vgaarb: loaded
[    0.072444] SCSI subsystem initialized
[    0.072655] usbcore: registered new interface driver usbfs
[    0.072720] usbcore: registered new interface driver hub
[    0.072830] usbcore: registered new device driver usb
[    0.090380] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-07-09 14:37,t
[    0.100110] raspberrypi-firmware soc:firmware: Firmware hash is d2b1b7fb01475cb3914b2086291
[    0.111609] clocksource: Switched to clocksource arch_sys_counter
[    0.188198] VFS: Disk quotas dquot_6.6.0
[    0.188290] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.188450] FS-Cache: Loaded
[    0.188630] CacheFiles: Loaded
[    0.189140] simple-framebuffer: probe of 0.framebuffer failed with error -12
[    0.198163] NET: Registered protocol family 2
[    0.198817] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.198862] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.198943] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.199028] TCP: Hash tables configured (established 8192 bind 8192)
[    0.199152] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.199194] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.199494] NET: Registered protocol family 1
[    0.200021] RPC: Registered named UNIX socket transport module.
[    0.200046] RPC: Registered udp transport module.
[    0.200068] RPC: Registered tcp transport module.
[    0.200089] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.200117] PCI: CLS 0 bytes, default 64
[    0.203164] Initialise system trusted keyrings
[    0.203350] workingset: timestamp_bits=14 max_order=20 bucket_order=6
[    0.212124] FS-Cache: Netfs 'nfs' registered for caching
[    0.212621] NFS: Registering the id_resolver key type
[    0.212662] Key type id_resolver registered
[    0.212684] Key type id_legacy registered
[    0.212714] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.214906] Key type asymmetric registered
[    0.214933] Asymmetric key parser 'x509' registered
[    0.215053] bounce: pool size: 64 pages
[    0.215109] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.215280] io scheduler noop registered
[    0.215304] io scheduler deadline registered (default)
[    0.215462] io scheduler cfq registered
[    0.215485] io scheduler mq-deadline registered (default)
[    0.215508] io scheduler kyber registered
[    0.238836] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x0000000
[    0.238880] brcm-pcie fd500000.pcie: could not get clock
[    0.238953] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    0.239004] brcm-pcie fd500000.pcie:   MEM 0x600000000..0x603ffffff -> 0xf8000000
[    0.301641] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)
[    0.301926] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[    0.301957] pci_bus 0000:00: root bus resource [bus 00-01]
[    0.301985] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address )
[    0.302046] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[    0.302193] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.304875] PCI: bus0: Fast back to back transfers disabled
[    0.304906] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.305088] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[    0.305161] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.305340] pci 0000:01:00.0: PME# supported from D0 D3cold
[    0.307969] PCI: bus1: Fast back to back transfers disabled
[    0.307999] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01
[    0.308057] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[    0.308090] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[    0.308138] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.308167] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
[    0.308240] pci 0000:00:00.0: enabling device (0140 -> 0142)
[    0.308275] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.310025] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.312029] iproc-rng200 fe104000.rng: hwrng registered
[    0.312264] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.312784] vc-sm: Videocore shared memory driver
[    0.313186] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    0.322957] brd: module loaded
[    0.332335] loop: module loaded
[    0.333074] Loading iSCSI transport class v2.0-870.
[    0.334711] libphy: Fixed MDIO Bus: probed
[    0.335138] bcmgenet fd580000.genet: failed to get enet clock
[    0.335169] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000
[    0.335199] bcmgenet fd580000.genet: failed to get enet-wol clock
[    0.335228] bcmgenet fd580000.genet: failed to get enet-eee clock
[    0.335496] unimac-mdio unimac-mdio.-19: DMA mask not set
[    0.351640] libphy: bcmgenet MII bus: probed
[    0.392126] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)
[    0.393015] usbcore: registered new interface driver r8152
[    0.393086] usbcore: registered new interface driver lan78xx
[    0.393150] usbcore: registered new interface driver smsc95xx
[    0.393412] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.393455] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    0.395203] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000000
[    0.395381] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 56
[    0.396000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.396034] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.396063] usb usb1: Product: xHCI Host Controller
[    0.396087] usb usb1: Manufacturer: Linux 4.19.57-v7l+ xhci-hcd
[    0.396111] usb usb1: SerialNumber: 0000:01:00.0
[    0.396633] hub 1-0:1.0: USB hub found
[    0.396698] hub 1-0:1.0: 1 port detected
[    0.397113] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.397148] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    0.397185] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    0.397528] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    0.397561] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.397590] usb usb2: Product: xHCI Host Controller
[    0.397614] usb usb2: Manufacturer: Linux 4.19.57-v7l+ xhci-hcd
[    0.397638] usb usb2: SerialNumber: 0000:01:00.0
[    0.398141] hub 2-0:1.0: USB hub found
[    0.398205] hub 2-0:1.0: 4 ports detected
[    0.399293] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.424856] dwc_otg fe980000.usb: base=(ptrval)
[    0.625167] Core Release: 2.80a
[    0.625194] Setting default values for core params
[    0.625233] Finished setting default values for core params
[    0.825568] Using Buffer DMA mode
[    0.825591] Periodic Transfer Interrupt Enhancement - disabled
[    0.825613] Multiprocessor Interrupt Enhancement - disabled
[    0.825637] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.825706] Dedicated Tx FIFOs mode
[    0.826364] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = ded30000 dma = 0x04
[    0.826409] FIQ FSM acceleration enabled for :
[    0.826409] Non-periodic Split Transactions
[    0.826409] Periodic Split Transactions
[    0.826409] High-Speed Isochronous Endpoints
[    0.826409] Interrupt/Control Split Transaction hack enabled
[    0.826469] dwc_otg: Microframe scheduler enabled
[    0.826544] WARN::hcd_init_fiq:457: FIQ on core 1
[    0.826576] WARN::hcd_init_fiq:458: FIQ ASM at c07ae05c length 36
[    0.826608] WARN::hcd_init_fiq:497: MPHI regs_base at f0810200
[    0.826656] dwc_otg fe980000.usb: DWC OTG Controller
[    0.826699] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3
[    0.826756] dwc_otg fe980000.usb: irq 37, io mem 0x00000000
[    0.826818] Init: Port Power? op_state=1
[    0.826839] Init: Power Port (0)
[    0.827094] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.827128] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.827156] usb usb3: Product: DWC OTG Controller
[    0.827179] usb usb3: Manufacturer: Linux 4.19.57-v7l+ dwc_otg_hcd
[    0.827204] usb usb3: SerialNumber: fe980000.usb
[    0.827709] hub 3-0:1.0: USB hub found
[    0.827771] hub 3-0:1.0: 1 port detected
[    0.828350] dwc_otg: FIQ enabled
[    0.828371] dwc_otg: NAK holdoff enabled
[    0.828391] dwc_otg: FIQ split-transaction FSM enabled
[    0.828416] Module dwc_common_port init
[    0.828628] usbcore: registered new interface driver uas
[    0.828757] usbcore: registered new interface driver usb-storage
[    0.828937] mousedev: PS/2 mouse device common for all mice
[    0.830100] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    0.830290] bcm2835-cpufreq: min=600000 max=1500000
[    0.830849] sdhci: Secure Digital Host Controller Interface driver
[    0.830873] sdhci: Copyright(c) Pierre Ossman
[    0.831263] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[    0.831724] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.834671] ledtrig-cpu: registered to indicate activity on CPUs
[    0.834827] hidraw: raw HID events driver (C) Jiri Kosina
[    0.834967] usbcore: registered new interface driver usbhid
[    0.834990] usbhid: USB HID core driver
[    0.835688] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    0.836966] [vc_sm_connected_init]: start
[    0.843070] [vc_sm_connected_init]: end - returning 0
[    0.844123] Initializing XFRM netlink socket
[    0.844163] NET: Registered protocol family 17
[    0.844261] Key type dns_resolver registered
[    0.844650] Registering SWP/SWPB emulation handler
[    0.845232] registered taskstats version 1
[    0.845261] Loading compiled-in X.509 certificates
[    0.852912] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    0.852990] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 33, base_baud = 0) is a PL02
[    0.856233] console [ttyS0] disabled
[    0.856281] fe215040.serial: ttyS0 at MMIO 0x0 (irq = 35, base_baud = 62500000) is a 16550
[    0.999241] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    1.242043] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    1.242054] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.242064] usb 1-1: Product: USB2.0 Hub
[    2.293916] console [ttyS0] enabled
[    2.297911] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    2.305903] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver
[    2.314426] hub 1-1:1.0: USB hub found
[    2.318455] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    2.324589] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    2.330468] hub 1-1:1.0: 4 ports detected
[    2.360944] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    2.385205] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    2.392395] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.399569] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.405214] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[    2.415025] of_cfs_init
[    2.417593] of_cfs_init: OK
[    2.420990] Waiting for root device PARTUUID=408190a6-02...
[    2.429362] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    2.436559] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.484205] random: fast init done
[    2.539372] mmc1: new high speed SDIO card at address 0001
[    2.546408] mmc0: new ultra high speed DDR50 SDHC card at address 0001
[    2.554106] mmcblk0: mmc0:0001 EB1QT 29.8 GiB
[    2.559701]  mmcblk0: p1 p2
[    2.573663] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    2.581102] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    2.788210] EXT4-fs (mmcblk0p2): recovery complete
[    2.796232] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.804524] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.812245] devtmpfs: mounted
[    2.821715] Freeing unused kernel memory: 2048K
[    2.826558] Run /sbin/init as init process
[    3.195757] systemd[1]: System time before build time, advancing clock.
[    3.289405] NET: Registered protocol family 10
[    3.295106] Segment Routing with IPv6
[    3.329248] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +AP)
[    3.351491] systemd[1]: No virtualization found in DMI
[    3.356757] systemd[1]: No virtualization found in CPUID
[    3.362257] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
[    3.369801] systemd[1]: No virtualization found in /proc/device-tree/*
[    3.376820] systemd[1]: UML virtualization not found in /proc/cpuinfo.
[    3.383550] systemd[1]: This platform does not support /proc/sysinfo
[    3.390023] systemd[1]: Found VM virtualization none
[    3.395130] systemd[1]: Detected architecture arm.
[    3.400470] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with optio.
[    3.514835] systemd-bless-boot-generator[83]: Skipping generator, not an EFI boot.
[    3.569825] systemd-gpt-auto-generator[89]: Failed to chase block device '/', ignoring: Noy
[    3.576929] systemd-fstab-generator[87]: Parsing /etc/fstab
[    3.588095] systemd-fstab-generator[87]: Found entry what=proc where=/proc type=proc makefo
[    3.588098] systemd-gpt-auto-generator[89]: mmcblk0p2: Root device /dev/mmcblk0.
[    3.597940] systemd-hibernate-resume-generator[90]: Not running in an initrd, quitting.
[    3.599149] systemd-fstab-generator[87]: Found entry what=/dev/mmcblk0p1 where=/boot type=o
[    3.602876] systemd-rc-local-generator[91]: Automatically adding rc-local.service.
[    3.604401] systemd-rc-local-generator[91]: /usr/sbin/halt.local does not exist, skipping.
[    3.618152] systemd-sysv-generator[94]: Native unit for paxctld.service already exists, sk.
[    3.636534] systemd-gpt-auto-generator[89]: No suitable partition table found, ignoring.
[    3.636842] systemd-fstab-generator[87]: Found entry what=/dev/mmcblk0p2 where=/ type=ext4o
[    3.671075] systemd-getty-generator[88]: Automatically adding serial getty for /dev/ttyS0.
[    3.672212] systemd-sysv-generator[94]: Native unit for cron.service already exists, skipp.
[    3.688578] systemd-sysv-generator[94]: Cannot find unit rng-tools.service.
[    3.695967] systemd-sysv-generator[94]: Native unit for sudo.service already exists, skipp.
[    3.706762] systemd-sysv-generator[94]: Native unit for ssh.service already exists, skippi.
[    3.716909] systemd-sysv-generator[94]: Native unit for rpcbind.service already exists, sk.
[    3.727332] systemd-sysv-generator[94]: Native unit for apparmor.service already exists, s.
[    3.737856] systemd-sysv-generator[94]: Native unit for lightdm.service already exists, sk.
[    3.748306] systemd-sysv-generator[94]: Native unit for dphys-swapfile.service already exi.
[    3.758249] systemd-sysv-generator[94]: Native unit for x11-common.service already exists,.
[    3.807888] systemd-sysv-ge: 82 output lines suppressed due to ratelimiting
[    4.204167] random: systemd: uninitialized urandom read (16 bytes read)
[    4.225872] random: systemd: uninitialized urandom read (16 bytes read)
[    4.238700] random: systemd: uninitialized urandom read (16 bytes read)
[    4.292198] systemd[103]: Operating on architecture: arm
[    4.299904] systemd[103]: Operating on architecture: arm
[    4.306019] systemd[103]: Operating on architecture: arm
[    4.311765] systemd[103]: Restricting namespace to: .
[    4.317019] systemd[103]: Operating on architecture: arm
[    4.322669] systemd[103]: Blocking cgroup.
[    4.322733] systemd[103]: Blocking ipc.
[    4.322797] systemd[103]: Blocking net.
[    4.322861] systemd[103]: Blocking mnt.
[    4.322927] systemd[103]: Blocking pid.
[    4.322990] systemd[103]: Blocking user.
[    4.323054] systemd[103]: Blocking uts.
[    4.323446] systemd[103]: Operating on architecture: arm
[    4.373151] i2c /dev entries driver
[    4.434129] systemd-journald[103]: Found cgroup2 on /sys/fs/cgroup/unified, unified hierarr
[    4.448954] systemd-journald[103]: Journal effective settings seal=no compress=yes compresB
[    4.459830] systemd-journald[103]: Fixed min_use=1.0M max_use=195.3M max_size=24.4M min_si0
[    4.491750] systemd-journald[103]: Reserving 44444 entries in hash table.
[    4.502742] systemd-journald[103]: Vacuuming...
[    4.507591] systemd-journald[103]: Vacuuming done, freed 0B of archived journals from /run.
[    4.521241] systemd-journald[103]: Flushing /dev/kmsg...
[    4.531643] systemd-journald[103]: /run/log/journal/a4fad59c89b649c2b23ff7464c897f72/syste.
[    4.546641] systemd-journald[103]: Rotating...
[    4.547063] systemd-journald[103]: Journal effective settings seal=no compress=yes compresB

Raspbian GNU/Linux 10 raspberrypi ttyS0

raspberrypi login: 

hwdornbush
Posts: 27
Joined: Fri Jan 20, 2017 7:08 pm

Re: pi 4 32GB sd card doesn't work.

Tue Dec 03, 2019 11:06 pm

I had this same problem with a 32GB MicroSD card. I got a 16GB card to boot, and updated all including the firmware. Then I reloaded a new copy of Raspbian on the same 32GB card that failed previously. It now booted. I also updated it. It now works, so I conclude that the firmware update fixed the problem since that was the only thing that changed.

Booting is terribly slow, slower than with a Pi Zero. But I am happy that it boots.

brohan
Posts: 25
Joined: Fri Aug 16, 2019 2:47 am

Re: pi 4 32GB sd card doesn't work.

Wed Dec 04, 2019 4:10 pm

Thank you for the update, I will try to upgrade the firmware

pcmanbob
Posts: 9261
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: pi 4 32GB sd card doesn't work.

Wed Dec 04, 2019 4:42 pm

hwdornbush wrote:
Tue Dec 03, 2019 11:06 pm
I had this same problem with a 32GB MicroSD card. I got a 16GB card to boot, and updated all including the firmware. Then I reloaded a new copy of Raspbian on the same 32GB card that failed previously. It now booted. I also updated it. It now works, so I conclude that the firmware update fixed the problem since that was the only thing that changed.

Booting is terribly slow, slower than with a Pi Zero. But I am happy that it boots.
You pi4 no not take as long to boot as a pi zero , I would suspect your SD card is faulty or a fake , how long does the pi4 take to boot on the 16GB SD card.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

brohan
Posts: 25
Joined: Fri Aug 16, 2019 2:47 am

Re: pi 4 32GB sd card doesn't work.

Sun Dec 08, 2019 9:42 pm

I followed the Pi instructions to update the Pi 4 firmware (using Raspbian lite). In my case this update unfortunately did not solve the memory card size limit.

hwdornbush
Posts: 27
Joined: Fri Jan 20, 2017 7:08 pm

Re: pi 4 32GB sd card doesn't work.

Mon Dec 09, 2019 1:50 am

I received a new Samsung 32 GB microSD card, and this one works much better in the Raspberry Pi 4. The old card still works fine in a Raspberry Pi 3, so I suspect there is still some problem with the RPi 4 and some 32GB memory cards.

hary
Posts: 75
Joined: Wed Jan 18, 2017 8:17 am

Re: pi 4 32GB sd card doesn't work.

Tue Dec 10, 2019 5:54 pm

May I join the party ?

I hope I won't hurt anyone that I'm coming here but as I'm facing some same problem, that might help/confirm some kind of problem.

I've been using 32Go SAMSUNG EVO+ uSDcard and I've been facing so many problem.
I think the problem came way more important from the time I switch to a new Pi4.

The problem where mostly when updating/upgrading just after a new install. The Pi4's behaviour was very strange and inconstant that it wasn't possible to find a clear reason for the problem.
It could freeze during the upgrade, sometime, it would seem to finish the upgrade but wouldn't start again after, or would start, work for some time, then end to misbehave.

I'm a beginner, so, all what I say has to be taken as beginner's talk ! I might also have done things wrong ...

But facing that problem, I used an old 16Go SanDisk card and it seems to work, (update/upgrade has past with no problem) at least on my old Pi3. I didn't tried that old 16Go SanDisk on the PI4 yet.

I must says that since I've used the 32GO EVO+ SAMSUNG card (but are they genuine Samsung ?) in the Pi4, out back in the Pi3, they behave also very strangely, 1 of the 2 I have seems to have completely failed as I cannot use it any more : To be precise, I cannot copy a new Buster .img to it, using dd, nor balenaEtcher won't work.

Despite what just says, I can put that "bad" 32GO EVO Samsung in my digital camera, then format it and use it to take photos and video and it seems to work great with the camera.

All my SDcard have been checked with f3write/f3read, and none of them have reported any error. The only strange part is that the read/write speed were very slow compared to what Samsung advertised for their EVO+ (maybe 10MB/s reading and less than 3MB/s writing)

pcmanbob
Posts: 9261
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: pi 4 32GB sd card doesn't work.

Wed Dec 11, 2019 11:14 am

hary wrote:
Tue Dec 10, 2019 5:54 pm

All my SDcard have been checked with f3write/f3read, and none of them have reported any error. The only strange part is that the read/write speed were very slow compared to what Samsung advertised for their EVO+ (maybe 10MB/s reading and less than 3MB/s writing)
I think your last statement might explain your problem,

1. either the SD card is faulty.

2. your card reader is not fully compatible with the SD card, when writing the image to the SD card in the first place

3. your card is a fake.


Option 2 can be simply proved by trying a new USB card reader, if this does not solve the problem then either option 1 or 2 is true but which is hard to decide.

I recently had an SD card fail , it would test fine with H2testW but would return slow read/write speeds, but when used in a pi would cause all sorts of crashes and strange behaviour.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

hary
Posts: 75
Joined: Wed Jan 18, 2017 8:17 am

Re: pi 4 32GB sd card doesn't work.

Wed Dec 11, 2019 9:23 pm

pcmanbob wrote:
Wed Dec 11, 2019 11:14 am



2. your card reader is not fully compatible with the SD card, when writing the image to the SD card in the first place

I used the SD/uSD card adapter provided by SAMSUNG, then, the SD adapter was inserted in my laptop's slot.

Same was done with the Sandisk uSD card witch was much faster for reading/writing and didn't show any problem till now.

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 5588
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: pi 4 32GB sd card doesn't work.

Wed Dec 11, 2019 11:13 pm

hary wrote:
Wed Dec 11, 2019 9:23 pm
pcmanbob wrote:
Wed Dec 11, 2019 11:14 am



2. your card reader is not fully compatible with the SD card, when writing the image to the SD card in the first place

I used the SD/uSD card adapter provided by SAMSUNG, then, the SD adapter was inserted in my laptop's slot.

Same was done with the Sandisk uSD card witch was much faster for reading/writing and didn't show any problem till now.
The "SD/uSD card adapter" is a passive device and your laptop's (SD) slot may not be fully SDHC/SDXC compatible esp. if it's not marked/labelled as such (depends somewhat on the age of the laptop). A USB-based card reader/writer is more likely to be fully compatible and uSDHC card manufacturers sometimes supplied one packaged with the uSDHC card - some examples here: https://www.cpmspectrepi.uk/raspberry_p ... cardReader
and here: https://www.cpmspectrepi.uk/raspberry_p ... cards.html

Trev.
Still running Raspbian Jessie or Stretch on some older Pi's (an A, B1, 2xB2, B+, P2B, 3xP0, P0W, 2xP3A+, P3B+, P3B, B+, and a A+) but Buster on the P4B's. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

hwdornbush
Posts: 27
Joined: Fri Jan 20, 2017 7:08 pm

Re: pi 4 32GB sd card doesn't work.

Thu Dec 12, 2019 12:38 am

Trev,
I think you are missing our point. It is possible that we have a bad SD card or reader. But I don't think so because mine work just fine in my Raspberry Pi 3. The same card, reader, and image don't work fine in my Raspberry Pi 4. And a 16GB SD card works fine in my RPi 4. I conclude that the RPi 4 still has a problem with 32GB SD cards.

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 5588
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: pi 4 32GB sd card doesn't work.

Thu Dec 12, 2019 9:26 am

hwdornbush wrote:
Thu Dec 12, 2019 12:38 am
Trev,
I think you are missing our point. It is possible that we have a bad SD card or reader. But I don't think so because mine work just fine in my Raspberry Pi 3. The same card, reader, and image don't work fine in my Raspberry Pi 4. And a 16GB SD card works fine in my RPi 4. I conclude that the RPi 4 still has a problem with 32GB SD cards.
Possibly with some cards >=32Gb - however, in my experience, all of the 32Gb cards I've used, so far, have worked fine - and I've tried several types. However, because I have more than one P4B, Raspbian has been installed using Linux tools and a known compatible USB3 card reader writer. All I'm saying is, with other methods YMMV.
Trev.
Still running Raspbian Jessie or Stretch on some older Pi's (an A, B1, 2xB2, B+, P2B, 3xP0, P0W, 2xP3A+, P3B+, P3B, B+, and a A+) but Buster on the P4B's. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

renice123
Posts: 181
Joined: Tue Oct 15, 2019 3:56 pm

Re: pi 4 32GB sd card doesn't work.

Thu Dec 12, 2019 9:59 am

If we are talking about Samsung EVO + cards, then I have already seen a lot of messages on the Internet that there are problems with these memory cards. These messages come not only from Raspberry owners, but from x86 users. I know that these are popular cards, but alas, such messages come. I quote
link:
“Interestingly, this only happens with the Samsung EVO 64 GB microSD card. The card is being tested for reading and writing, and I had no problems with it on other devices, so I don’t believe that something is wrong. I cloned the contents to another cheap 64 GB microSD card and it works fine without errors ”
https://github.com/raspberrypi/linux/issues/2802
And for some reason, this problem is especially acute on the fourth version of Raspberries.
(I think this is due to the fact that in the fourth version the algorithm for working with a memory card was changed, including the option to set the frequency in config.txt was removed. But only the developers of the engineering know the answers here)
I do not know if this will help if you switch to the memory card of another company
And I do not know the reasons why Samsung memory cards suddenly began to cause such an error.
Some believe that the error is associated with an unusual Samsung memory card controller - including due to the algorithm for working with erroneous sectors
By the way, I use old Sandisk Ultra cards and I never had such errors
You can check if your errors are related to the operation of the Samsung memory card controller if the following messages appear in your logs
raspberrypi kernel: [*****] mmc0: Timeout waiting for hardware interrupt.
Here is the thread where there was a discussion
https://www.raspberrypi.org/forums/view ... 8&t=258722

hary
Posts: 75
Joined: Wed Jan 18, 2017 8:17 am

Re: pi 4 32GB sd card doesn't work.

Thu Dec 12, 2019 8:03 pm

@renice123.

I keep posting on that thread from my last "experiment".

Would be nice if I could get some advices, or maybe should do more experiment since I didn't yet inserted my brand new 32Go EV+ SAMSUNG uSDcard in a Pi4 at the moment. It seems to work ok on my Pi3

User avatar
HawaiianPi
Posts: 5699
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: pi 4 32GB sd card doesn't work.

Tue Dec 31, 2019 12:26 am

This is such an odd problem. I use 32GB cards in most of my Pi systems, including both of my Pi 4B models (2GB & 4GB). I sometimes use 16GB cards for testing, but mostly use 32GB in systems I'm using for anything (or if I need more than that, I use an SSD). Both of my Pi 4B models have been booted and run from 32GB cards in the past, but I decided to test the latest image (just in case).

I just tested the following 32GB cards with my 4B4 and the latest Raspbian Buster Lite image (2019-09-26-raspbian-buster-lite.zip).

Cards were written with Etcher using a SanDisk MobileMate USB 3.0 micro SD reader on my Win10 laptop.

Lexar High-Speed 32GB
Samsung EVO Select 32GB
Samsung EVO+ 32GB
Samsung EVO Plus 32GB
Samsung Pro (grey) 32GB
Transcend Class-10 32GB
SanDisk Ultra A1 32GB

And I also gave the following larger cards a try.

SanDisk Ultra Plus A1 64GB
PNY High Performance 128GB (P-SDUX128U160G-GE)
SanDisk Ultra A1 400GB

Every single one of those booted fine in my Raspberry Pi 4B 4GB (using the old micro USB official 5.1V/2.5A PSU with a USB-C adapter).

And curiously, the 400GB card also booted on my old 3B, which I suppose is a subject for another thread ... :?
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

hary
Posts: 75
Joined: Wed Jan 18, 2017 8:17 am

Re: pi 4 32GB sd card doesn't work.

Tue Dec 31, 2019 2:17 pm

And did you try to upgrade ?

Things starts began to turn bad when trying to update/upgrade for me.

User avatar
HawaiianPi
Posts: 5699
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: pi 4 32GB sd card doesn't work.

Wed Jan 01, 2020 4:33 am

hary wrote:
Tue Dec 31, 2019 2:17 pm
And did you try to upgrade ?

Things starts began to turn bad when trying to update/upgrade for me.
I tested a Samsung EVO+ 32GB card with the Raspbian Buster full image, and everything is still working fine after an upgrade. In the other thread there are claims that there may be problems with the EVO+ cards, but those were replaced a few years ago with EVO Plus cards (+ sign vs "Plus" word), so if you recently purchased a new "EVO+" card it may be a fake.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

LTolledo
Posts: 3297
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: pi 4 32GB sd card doesn't work.

Wed Jan 01, 2020 5:18 am

hary wrote: And did you try to upgrade ?

Things starts began to turn bad when trying to update/upgrade for me.
have you tested your card using H2testw (w$) or F3 Fight Flash Fraud (mac/Linux)?
better test it

the only bad microSD I had was "bad from the beginning" meaning Etcher cannot even proceed to flashing. H2testw confirmed it.
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

maceddy
Posts: 3
Joined: Wed Mar 25, 2020 9:09 pm

Re: pi 4 32GB sd card doesn't work.

Thu Mar 26, 2020 9:18 am

Hello,

may I join also?
I'm also having troubles with a 32GB SD Card.

Tried a 4GB card. Boots normally. Updated firmware/eeprom to see if that fixes the problem.
4 blinking green lights with the 32GB card.

Etcher does write the card and no problems when using the H2testw software.

I tried every instruction I could find and the card seems fine. The reseller where I bought the stuff are one of the best (if not the best) reseller in the Netherlands so they know what they sell..

pcmanbob
Posts: 9261
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: pi 4 32GB sd card doesn't work.

Thu Mar 26, 2020 10:29 am

Hi.

As you seem to have done the tests to prove your card is good , I would suggest you try a different card reader, preferably a recently new USB one, especially if you are use an existing one that built in to your PC, as it might well not be fully SD/HC or SD/XC compliant.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

maceddy
Posts: 3
Joined: Wed Mar 25, 2020 9:09 pm

Re: pi 4 32GB sd card doesn't work.

Thu Mar 26, 2020 10:51 am

Same reader/writer as where I flashed my Pi3 64GB card with. That works fine (only not in the Pi4 off course).

Despite the fact that the card tests are positive, I do think it's the SD card.
It also does not boot in my Pi3.

User avatar
B.Goode
Posts: 10130
Joined: Mon Sep 01, 2014 4:03 pm
Location: UK

Re: pi 4 32GB sd card doesn't work.

Thu Mar 26, 2020 10:57 am

maceddy wrote:
Thu Mar 26, 2020 9:18 am
Hello,

may I join also?
I'm also having troubles with a 32GB SD Card.

Tried a 4GB card. Boots normally. Updated firmware/eeprom to see if that fixes the problem.
4 blinking green lights with the 32GB card.

Etcher does write the card and no problems when using the H2testw software.

I tried every instruction I could find and the card seems fine. The reseller where I bought the stuff are one of the best (if not the best) reseller in the Netherlands so they know what they sell..

What I am about to say has almost certainly been discussed earlier in this thread...

Presumably you know that there is a summary of all the knowledge accumulated from these forums during the past 8 years about difficulties getting an RPi to boot, see - STICKY: Is your Pi not booting? (The Boot Problems Sticky) - https://www.raspberrypi.org/forums/view ... 28&t=58151

That contains the following -
Shortly after launch [of the RPi4] there appeared to be an issue with some 32GB cards that expressed itself with that the boot aborts. The four raspberry's appear followed by a short burst of text, then the system halts. The base of the issue seems to be the card reader of the PC used, but later firmware seems to have solved the issue: https://www.raspberrypi.org/forums/view ... 8&t=248968 in the mean time, if you have this exact problem, I would suggest using a 16GB card, try using another card reader, or upgrade the boot code


That information is now 9 months old, but might still be applicable.

Everything so far has been 'fact'. My 'opinion' follows..
If your reseller is reputable then they should accept that an RPi board that won't boot up correctly is faulty and should be replaced.



Contribution invalidated by the revelation that the same card also fails to work with another model of RPi board. That detail was added after I started researching and typing my response. Consider me no longer part of this discussion.
Last edited by B.Goode on Thu Mar 26, 2020 11:34 am, edited 1 time in total.

pcmanbob
Posts: 9261
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: pi 4 32GB sd card doesn't work.

Thu Mar 26, 2020 11:12 am

maceddy wrote:
Thu Mar 26, 2020 10:51 am
Same reader/writer as where I flashed my Pi3 64GB card with. That works fine (only not in the Pi4 off course).

Despite the fact that the card tests are positive, I do think it's the SD card.
It also does not boot in my Pi3.
If you had added this information to your first post it would have been helpful.

If the same SD card will not boot a pi3 which does not have the pi4 EEPROM then I would suggest the problem is with the particular SD card or the make of SD card.

I would suggest trying a different SD card and possibly a different make.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 5588
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: pi 4 32GB sd card doesn't work.

Thu Mar 26, 2020 11:21 am

maceddy wrote:
Thu Mar 26, 2020 10:51 am
Same reader/writer as where I flashed my Pi3 64GB card with. That works fine (only not in the Pi4 off course).

Despite the fact that the card tests are positive, I do think it's the SD card.
It also does not boot in my Pi3.
Given that you appear to have a working P3 maybe try updating that and using the Raspbian version of the new imaging tool (https://www.raspberrypi.org/forums/view ... 3&t=268534 ) to write the card?
Since the original (PC/MAC) versions of that tool were released I've tested image writing to another 5 32Gb uSDHC card (3 brands, 2 sample for 2 of them. Total samples 14, over 11 brands, using various methods/platforms with known compatible, mainly USB-based hardware.) with both the PC (Win8) version (built-in card slot) and the Pi version - the latter is now installed on a "dedicated" P3A+. All cards have booted w/o issues but some (older) types are "slow".
Trev.
Still running Raspbian Jessie or Stretch on some older Pi's (an A, B1, 2xB2, B+, P2B, 3xP0, P0W, 2xP3A+, P3B+, P3B, B+, and a A+) but Buster on the P4B's. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

Return to “Troubleshooting”