Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No boot on PiSDR 6.1 RPi 4 2GB #98

Open
a-oxide opened this issue Apr 28, 2023 · 7 comments
Open

No boot on PiSDR 6.1 RPi 4 2GB #98

a-oxide opened this issue Apr 28, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@a-oxide
Copy link

a-oxide commented Apr 28, 2023

Describe the bug
Rpi 4 2gb will not boot after flashed. Device has a keyboard and the official RPi 7" touchscreen attached.

To Reproduce
Steps to reproduce the behavior:

  1. Flash SD Card
  2. Insert into Pi
  3. Attempt to boot
  4. See black screen, or occasional blinking "_"

Expected behavior
The Pi to boot into desktop

Device Version
RPi 4 2GB

Additional context
I have tried downloading multiple versions, redownloading version 6.1, booting from a battery and from an official RPi power supply. I have tried flashing with both BalenaEtcher and RPI Imager. The screen consistently boots into a black screen after the initial rainbow box.
@a-oxide a-oxide added the bug Something isn't working label Apr 28, 2023
@luigifcruz
Copy link
Owner

Hi, thanks for trying PiSDR. Is the behavior the same as the original Raspberry Pi OS? I don't have a screen so I can’t validate it works with PiSDR.

@a-oxide
Copy link
Author

a-oxide commented May 21, 2023 via email

@luigifcruz
Copy link
Owner

No problem! Interesting. I can't remember any setting to turn this on by default in the image builder. Perhaps there might be a setting that you can enable in rasp-config.

@a-oxide
Copy link
Author

a-oxide commented May 21, 2023 via email

@JoeMatt
Copy link

JoeMatt commented Jun 28, 2023 •
edited
Loading

Same problem on 3B+. It starts to load desktop and then blacks out. Using the older 7" touchscreen for the 3B+, latest release with Balana.

The first boot it went to resizing and rebooted after that was complete. So the screen was working then.
Llater in the second boot it gets stuck. You can nearly catch the line if you turn off the boot screen.

Not sure if it's X or init.d process but it hard locks aftwards.

I'll update with a video once it's rendered.

Update. I got it to work by finding similar reported issues.

I think the important lines are

dtoverlay=vc4-fkms-v3d
dtparam=i2c_arm=on
dtparam=spi=on

# rpi3 only 
dtparam=i2c_vc_baudrate=50000

config.txt

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1920
#framebuffer_height=1080
framebuffer_width=1280
framebuffer_height=720 

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on
# Possible rpi 7" touchscreen "fade to white/black" fix
# https://github.com/raspberrypi/firmware/issues/1658#issuecomment-975416756

### !!! WARNING Only for rpi3 bug and might not be necessary even then.
dtparam=i2c_vc_baudrate=50000 

# Uncomment this to enable infrared communication.
dtoverlay=gpio-ir,gpio_pin=17
dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Set to "on" to enable autoprobing of Bluetooth driver without need of hciattach/btattach
# Default: off
dtparam=krnbt=on

# Enable DRM VC4 V3D driver
#dtoverlay=vc4-kms-v3d
#dtoverlay=vc4-kms-v3d,composite
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

# RPI Touchscreen
#dtoverlay=vc4-kms-dsi-7inch

# Run in 64-bit mode
arm_64bit=1

# Disable compensation for displays with overscan
disable_overscan=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
#otg_mode=0
otg_mode=1


[all]

[pi4]
# Run as fast as firmware / board allows
arm_boost=1
gpu_mem=256

[all]

@JoeMatt
Copy link

JoeMatt commented Jun 28, 2023

FYI: I ran raspi-config and turned on all advanced graphics options and GL except wayland. Rebooted and X performance and SDR++ rendering was way better.

Screen does blank out mid boot for a second but comes back up to X as normal. Touch works too.

@luigifcruz
Copy link
Owner

luigifcruz commented Jun 28, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JoeMatt @luigifcruz @a-oxide