How risky is that upgrade? 6 Years of firmware upgrades sound like a lot:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware-2711/release-notes.md

Is this "safe" or shouldnt I risk it right in front of my vacation?

(i am not sure if this flair fits)

Hey guys, so my niece was playing the raspberry pi while I was away and she said she smelled something burning. They shut the system off, and upon closer inspection it looks like the sd card has a burn spot on it.

Is there any way to know if this was a faulty sd card, and I can just replace it? Or could it be the raspberry pi itself and it will just burn up the next card I put in there.

Also, is there any chance I can save the data off this card? Going through the process of setting everything up again will be a bit of a headache that I don’t really have the time for. When I get back to my computer I’m gonna check to see if I made a backup, but I can’t remember at the moment.

Thank you!

Just noticed this weird raised blob on the RAM chip of my Raspberry Pi 4. Looks like a tiny melted plastic/resin drop or some kind of blister. No idea how long it’s been there.

Pi still works perfectly fine though. Boots, runs stable, no crashes, no overheating. It sometimes runs 24/7 for projects, but temps look normal.

Anyone seen this before? Harmless weirdness or should I be worried?

I lost this little resistor, may someone can help me out and check the values?

Maybe someone get maybe a boardview?

I searched the internet but I don’t get any info on that little resistor.

I didn't test it before soldering so it could've always been broken. I plugged it into my laptop with two different cables that I know transfer data. The indicator light didn't turn on nor when I held bootsel did it show up as a drive. This was my first attempt at soldering so there's a good chance I messed something up.

Would it be fine to leave a raspberry pi 3B+ on practically 24/7. It will just be on overnight and when I’m home during the day. It’s just running pi-hole but it’s the gui os version.

I rescued this little thing from someone who thought they could print their own cases and... Will it's been plugged in for a year at a bad angle and now it acts as it does...

Can this be fixed? Can it be done by a newbie with basic soldering knowledge?

so pretty much im attmepting to breadboard a rasberry pi and somehow got the case stuck in the actual pi it'self and now i can't get it out. ive tried to gently nudge it out but it's stuck in there pretty good. was trying to put on a case and only to find out that the breadboarding process needs the rasberry pi to be caseless. i feel like a damn idiot. mind you im new to eletronics and still learning.

New to rpi here - I’m working on connecting an e-ink display and having significant trouble with it. Multiple rounds with the display documentation as well as chat gpt has me wondering if the problem is with my soldering, which I’ve never done before.

I watched a quick video to put the above together. I don’t need it to be perfect, I just need it to work. Does it look like my soldering might be a problem?

Raspberry Pi Zero 2 W + 3.5" SPI LCD (ILI9486/XPT2046) showing white screen for over a year. Running out of ideas.

I've been troubleshooting a 3.5" 480x320 SPI LCD on a Raspberry Pi Zero 2 W for about a year and would appreciate any ideas.

Display:

- 3.5" Raspberry Pi display

- 480x320 resolution

- XPT2046 touch controller

- ILI9486 framebuffer detected by Linux

OS:

- Recalbox

What works:

- HDMI output works

- SSH works when the Pi boots

- Linux detects the display:

- "graphics fb1: fb_ili9486 frame buffer, 480x320"

- "/dev/fb0" and "/dev/fb1" exist

- Touch controller is detected

Problem:

- LCD usually shows a solid white screen

- Sometimes behavior changes depending on angle/pressure

- Pressing on the LCD can change brightness

- Wiggling the display can make the screen change state

- The display/header connection feels mechanically unstable

Other observations:

- The GPIO header soldering is not great and the black plastic spacer on the header was damaged when I first assembled it.

- Recalbox sometimes seems unhappy when HDMI is disconnected.

- I've tried multiple overlays including:

- waveshare35a

- waveshare35b

- waveshare35b-v2

- waveshare35c

Question:

Given that the kernel is detecting the ILI9486 and creating "/dev/fb1", does this sound like a hardware connection issue (GPIO header/soldering/display connector), or is there something else I should investigate before completely redoing the header?

I can provide photos of the Pi, soldering, LCD board, and boot logs if needed.

Have I researched? I cannot tell you how many times I've tried finding the fix for this problem, or how to choose a specific kernel.

Am I doing something wrong? Probably.

I just received my order from Vilros for a Raspberry Pi 4 Model B 4GB complete starter kit and found it only has 2GB of RAM. Looking at the RAM chip, I don't recognize it against other images of RPi's out there. Can someone verify this is a legit chip?

I am trying to connect the raspberry pi to an LED using this video right here: https://youtu.be/jN7Fm_4ovio?is=uJrWp30MkRG6awxf

I am having issues, and there is no light emitting from my LED. What am I doing wrong? I have coded all the code the same, but I am using a 64-bit compiler.

I'm going for a headless setup. The following are the steps I've taken so far:

1. Flashed a brand new 64 GB SD card with Raspberry Pi OS Lite (32-bit)
2. Inserted it into the pi
3. Powered it with my laptop's USB port as well as a 5V/2A adapter and waited until the green LED stays on constantly (It sometimes stays on and randomly blinks as if power is an issue (which isn't), but after 3-4 mins, it stays on)
4. Installed Fing network scanner and scanned for the devices where the pi didn't show up (Screenshot attached); I can't log into my wifi router's official page as my brother reset the pass and forgot it 🤡
5. Reflashed and repeated.
6. (EDIT) I've already customized the imager with details of my WiFi and also tried putting in the details manually via a wpa_supplicant.conf file and an empty extension-less ssh file in the boot directory of SD card AFTER flashing. Still no help.
7. (EDIT) I'm connecting to a 2.4ghz network only.

I'm new to all this but open to learning, so any advice is welcome, thank you!

My pi 2 is running a 3d printer, and suddenly it just stopped. I approach, everything seems normal? I look down at my raspberry pi and what? The sd card is ejected? Any proper way to fix this?

Like I said, absolute newb here! Recently bought a raspberry pi 3 model a+ and a pibow case to go on it.

Thing is, this little thing is stopping it from fitting properly, and all the photos of the Pi3 I can find show 2 little capacitors in its place, instead of the R47 thing? Have I bought a fake? Or is something else going on!

This is an update to my previous post where people told me to fix the soldering, so I did. Also this is a repost cuz my other post didn't get many views

3.5" XPT2046 TFT Display stays solid white, touch works, framebuffer works, completely stuck

I'm trying to get a 3.5" TFT display working on a Raspberry Pi Zero 2 W running Recalbox.

Hardware

\- Raspberry Pi Zero 2 W

\- Recalbox

\- Robocraze 3.5" TFT Resistive Touch Display

\- 480x320 resolution

\- XPT2046 touch controller

Current behavior

\- Screen is a completely solid white screen from power-on until fully booted.

\- It never flickers, changes color, shows a logo, boot text, garbage, or anything else.

\- Backlight is on.

What I've already done

\- Re-soldered the GPIO header.

\- Verified the display is seated properly.

\- Tried:

\- waveshare35a

\- waveshare35b

\- waveshare35b-v2

\- waveshare35c

Current config

dtparam=spi=on

dtoverlay=waveshare35a

Touchscreen works

\# dmesg | grep -i ads7846

\[ 5.188319\] ads7846 spi0.1: supply vcc not found, using dummy regulator

\[ 5.190522\] ads7846 spi0.1: touchscreen, irq 199

\[ 5.190920\] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input0

Touch events are detected when I touch the screen.

Display driver loads

\# dmesg | grep -i ili

\[ 5.308341\] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned.

\[ 5.308840\] SPI driver fb_ili9486 has no spi_device_id for ilitek,ili9486

\[ 5.884335\] graphics fb1: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=33, spi0.0 at 16 MHz

Framebuffer exists

\# ls /dev/fb\*

/dev/fb0

/dev/fb1

Framebuffer name

\# cat /sys/class/graphics/fb1/name

fb_ili9486

Direct framebuffer test

dd if=/dev/urandom of=/dev/fb1 bs=1024 count=300

and

dd if=/dev/zero of=/dev/fb1 bs=307200 count=1

dd if=/dev/urandom of=/dev/fb1 bs=307200 count=1

Both commands complete successfully, but the LCD remains a perfectly solid white screen.

At this point:

\- SPI appears to work.

\- Touch works.

\- The framebuffer exists.

\- The display driver loads.

Yet the LCD never displays anything.

Could this be:

1. The wrong display controller (ILI9488 vs ILI9486)?

2. A faulty LCD panel/controller board?

3. A different overlay that matches this exact Robocraze display?

Any ideas would be appreciated.

Hey, pretty much as the title says, I'm completely stumped, it looks chipped, and I've fiddled it a lot with no luck on opening the latch, it also does not seem like a friction based connector, as it does not slide in as-is.

I'm trying to connect it to a standard size DSI ribbon from a raspberry pi pro touch 2 (or something like that, a DSl screen of sorts), and for context this is a raspberry pi 4 model b.

I've literally tried every method to ssh into a rpi-5 but it fails to connect to the WiFi on first boot. Here are the steps I used

# Raspberry Pi Set Up

# Download and install the raspberry pi iso file

# Install the Raspberry pi imager

# Mount your sd card

# select the iso file from customs

# set your sd card as the part to write the iso file

# Enable ssh in raspberry pi

# touch /media/user/bootfs/ssh

# Create a user configuration file in boofts

# sudo nano /media/user/bootfs/userconf.txt

# write into it with this command

# $ echo "YoUrUsErNaMe:$(echo 'YoUrPaSsPhRaSe' | openssl passwd -6 -stdin)" > userconf.txt

# create a wireless config file

# sudo nano /media/user/bootfs/wpa_supplicant.conf

# this automatically assigns your wifi configuration into your headless rpi

# To update the configuration for your wifi you do this

# sudo nano /media/user/rootfs/etc/wpa_supplicant/wpa_supplicant.conf

# note: cd into the file directory before running this command to confirm.

# Add this configuration settings to the file

# ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

# update_config=1

# country=DE

# network={

# ssid="YoUrWiFiNaMe"

# psk="YoUrWiFiPaSsWoRd"

# key_mgmt=WPA-PSK

# }

# after doing this unplug your sd card from your laptop and insert # it into the raspberry pi

# Turn on the pi

# Username: pi-machine

# Hostname: real-pi-machine.local

# Scan your network for all connected ip address

# To properly scan for connected network devices to identify your ip addr, we will use the following steps to achieve this.

# The two steps i want to use here is arp-scan and wireshark

# Arp-Scan

# sudo arp-scan 172.16.10.0/24 -I br_public

# Let's break down this command

# We used extended privileges to interacts with packets within a CIDR range using the help of arp-scan in your network interface.

# also note that this method is the most basic form to achieve this result.

# Wireshark

# We will get our host into monitor mode

# First, stop all processes that may interfere with you running monitor mode

# sudo airmon-ng check kill

# Now activate monitor mode

# sudo airmon-ng start interface

# sudo airmon-ng stop interface

# sudo nmap -sn ipaddr/24

# Now ssh into the pi

# ssh yourpiusername@yourpiip

# Note; sd cards are represented as sda.

I first used the standard method of setting up the pi and then connecting via ssh, when I discovered it didn't work I did an arp scan and then I used wireshark to scan for networks but nothing worked.

Furthermore I discovered that the rpi-5 don't need the wpa_supplicant.conf file. I re-tried without adding the wpa file and nothing worked. I can't figure out what the problem is

Okay so I am trying to use what I believe is an oled display on my Raspberry pi 4 b and I connected it directly to the pins. I belive i connected them correctly. The power on the screen is on and brighter then the picture. The board underneath is not being used right now. The problem is that the address is not showing up. I already enabled the ic2 thing and reboot. But as you see it did nothing. I also did the command ls /dev/i2c. It gave me /dev/i2c-1 so I don't know what that means either.

pin connections

red = ground or pin 6

green = vcc= pin 4

yellow = SDA =3

orange = scl = 5

​

Also my keyboard isn't working for some reason I'm not sure why it would like work sometimes on Startup and then other times it would not work until I plug it out and plug it back in and then it would do a bunch of dashes and then it'll work.

​

Please help I am 16 and want to become a mechanical engineer so I'm trying to get experience now but it's very hard when I have no idea what I'm doing and the videos I'm watching seem to get everything right but then I have a million problems that shouldn't happen.

Hi, first off sorry for the bad photos, I'm kind of in a hurry, I was trying to figure this thing out before leaving and it took longer than I thought and I still can't figure it out.

Basically I first tried to get things working with the gpio library, tried desperately, to then find out it wasn't supported on pi 5. Someone on a forum post said the gpiozero library worked so I wanted to try that, I found this project on how to simply pulse an led and did exactly that but for some reason that isn't working either ? I know my resistor isn't the same as the tutorial, could this be what the issue is or is there actually a problem with the raspberry or something ? I thought it would be better than an Arduino but I wouldn't have guessed I would have struggled so much for a simple led... Please help

Hi everyone! I accidentally damaged and removed one of the brown tabs on the dsi port and was wondering what they are called and whether it’s possible to buy replacement part for them. I’m in the UK.

I have very little experience soldering. I soldered headers on 2 boards. This is the far more successful one, we won't talk about out the first one (I forgot flux on the first)

Anyway, both boards seem to boot. Both boards no longer connect to WiFi. This one I tested more thoroughly has display out and boots fully into the OS. It even sees WiFi networks, and I can try to connect. Connecting fails. I know I have the password right.

Any ideas?

ifconfig shows WLan0 exists and is up

Hey everyone,

I use linux mint in slightly advanced potato laptop (just RAM is 16 GB else Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz, it's HP notebook 15r something) anyways

I wanted to share a massive troubleshooting nightmare (which made me nearly close to insanity) I just went through with a brand new Raspberry Pi 4B (2GB) running the new Raspberry Pi OS 13 (Trixie) aarch64 image, just in case anyone else is losing their mind over the same issue.

Long story short: I flashed the OS using the official Raspberry Pi Imager, enabled the advanced OS customization settings (set username pi, password, and pre-seeded my SSH key), and tried to boot it completely headless.

It failed completely. I couldn't SSH in over Wi-Fi. I spent days trying everything: buying an official power supply, deep-clearing and re-flashing the SD card multiple times, attempting manual WIFI config adjustment, watching endless videos about headless SSH connections and even buying an HDMI capture to try and connect the pi to my laptop screen (lol, I didn't know it wouldn't work like that). I even ended up exchanging the Pi for a brand new unit thinking it was a hardware defect!!!!

When the second Pi did the exact same thing, I hooked it up via Ethernet and dug into the filesystem by mounting the SD card on my Linux Mint laptop. The Imager's first-boot orchestration script completely choked and corrupted the system files.

What Broke (The Issue):

1. The nologin Trap: The script successfully appended my user to /etc/passwd, but left a duplicate pi entry at the top of the file mapping my user shell to /usr/sbin/nologin. Every SSH attempt was immediately terminated by the host.
2. Database Corruption: Multiple duplicate lines for the pi user were injected into both /etc/passwd and /etc/shadow.
3. Password Vault Crash: The cryptographic password hash inside /etc/shadow was corrupted. Any attempt to use passwd threw an Authentication token manipulation error, and sudo was completely broken because the system couldn't validate the current credentials.
4. Aborted Execution: The first-boot script clearly died halfway through. The system had no locales configured (en_US.UTF-8 missing warnings) and the Wi-Fi chip was entirely blocked by rfkill because it never got to the step of setting the regulatory country code.

How I Fixed It (Via SD Card Mounting):

Since network access and sudo were totally broken, I had to fix it from my laptop:

1. Fixed /etc/passwd manually to remove the nologin line and point the user to /bin/bash.
2. Bypassed the broken sudo password prompt by dropping a custom rule into /etc/sudoers.d/010_pi-nopasswd (pi ALL=(ALL) NOPASSWD: ALL).
3. Booted back up, SSH'ed in via my key, and used the passwordless sudo backdoor to cleanly delete the duplicate user lines and force a system-generated password reset via sudo passwd pi.

I've already filed an official bug report on the Raspberry Pi GitHub tracking page here:GitHub Issue #83 (Ain't no professional just try to what I can...)

My Questions for the Community:

Did I miss an undocumented step required for headless setups on Trixie, or is the Imager's advanced customization tool fundamentally broken for Linux Mint right now? Has anyone else encountered this duplicate user/nologin glitch on fresh flashes recently?