As you can read in the title of the post, I have a problem about rebooting the Raspberry PI after doing :
sudo apt-get update && sudo apt-get upgrade.
When the updating and upgrading finished, I restart the Raspberry and I just have a black monitor and the POWER LED (Red) is ON and the Green Led is also ON.
This is the second time the problem appear on my Raspberry PI.
Today, I downloaded the Raspbian and did all the manipulation to boot the Raspberry. And now the problem re-appear. The First time that the problem appear, I just formated the SD Card and I wrote the Raspbian in the SD Card.
If some one had the same problem, please help me to solve it.
Thank you in advance.
PS : I am using a Raspberry PI model B+.
I had similar problem like You.
For me, I have 2 possible reasons :
1) Power Supply - I recommended 5V 2A Power Supply
2) Network ethernet patch cable unshielded (without shield or ground line)
This problems with cable I had also on R-Pi2. Buying shielded cable solve my problems with R-Pi hangs on boot after reboot.
Now my cable looks like this one :
http://www.cabling-supplies.com/media/catalog/product/cache/1/image/512x512/9df78eab33525d08d6e5fb8d27136e95/c/a/cat6a-shielded_1.jpg
The problem resides in the SD card. When the green LED isn't blinking, it means the Pi can't read the SD card. To fix this, get a new SD card.
Related
I'm running Ubuntu Server 22.04 LTS on a Raspberry Pi 4 Model B with 4GB RAM. I'm booting Ubuntu via USB3 and everything works fine so far.
My issue is that at some point the filesystem crashes when I unplug/plug another USB device (It's an EPSON receipt printer). If I boot the system with the printer already attached everything works 100% of the time, but unplugging or plugging the printer at runtime results sometimes in a crash in the filesystem/access to the boot device.
How does the crash show up:
I'm connected via ssh and I can regularly type commands like ls and get the response. Then I unplugged and plugged the EPSON receipt printer multiple times and always executed a ls in between. At some point in time I always get -bash: /usr/bin/ls: Input/output error. And commands like ifconfig or dmesg are unknown. But the pwd command keeps on working. Please notice I did not unplug the SSD from which I booted. I already tried it with booting from an SD card and it seems there I don't get the problem. I already checked journalctl, but could find anything and I'm kinda clueless what's even going on.
PS: After a hard reboot everything works normally and it does not happen if I plug or unplug a regular USB stick, so it seems it's something about the EPSON printer?
UPDATE:
Executing dmesg -w gives this result. Please note Im only removing the EPSON printer, not the SSD.
Does anyone have any idea?
Thanks!
As the title says, I want to run a script on the Raspberry Pi from my Windows PC. The connection between PC and Raspberry Pi 4 (Raspbian OS) should be done using an Ethernet cable. The Rasperry Pi cannot be operated permanently in the network. Is it correct that then a SSH connection is out of the question?
For background: the Raspberry Pi is connected to a camera and a stepper motor. Depending on the position of the object to be photographed, the stepper motor is moved and then a photo is taken. This photo is then to be sent back to the PC via the network cable. The script on the Raspberry Pi (rotation stepper motor and image capture) is implemented with Python and fully functional. Is it generally possible to run the Pi script using the Ethernet cable and transfer the generated images back?
Using a Windows QT GUI I want to start this script and display the images later.
Is this possible or can someone suggest a simpler way? Maybe someone already had a similar problem and would help me.
Many thanks in advance.
If you have an extra Ethernet NIC on your computer, you can directly connect your PC and Raspberry PI (on relatively newer hardware) or if that doesn't work, you can use a crossover Ethernet cable to connect your PC to the PI. Then configure an ssh server on the PI and enable Avahi and dhcpd and execute your script via that using MSYS ssh or Putty (ssh pi#hostname.local). Don't forget to change your hostname.
Bonus tip: you can also send your data (images) back over the same connection.
USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
The problem was described here - https://communities.vmware.com/thread/612551
but anyone has no answer for it.
Generally, the problem is like so:
launch vm
connect usb stick or usb phone cable
vm freezes
it is not possible to terminate vmware-vmx.exe process (even as a SYSTEM user with highest privs).
The issue occurs on vmware workstation 14 & 15 on Windows 10 Pro Build 1903
Also tried disabling windows defender (maybe some strange scan policy) but no results.
Tried also to change almost every setting in workstation but no results...
please help
I was facing exactly the same issue and I have finally found the solution.
Update to VMWare Workstation version 15.5. Update the VM Tools in the Guest operating System, and it works!! Tried with Android Devices, in USB Tethering Mode also.
I recently bought a Raspberry Pi 3 Model B and started to set it up. I followed some tutorials and finally was able to access it remotely without having to plug it to a monitor, a keyboard, a mouse...
Everything is okay but it just bothers me a little bit that whenever I reboot it or I don't use it for some time I have to ping it on the computer before being able to control it remotely. If I don't ping it, connection fails.
It's not a big problem but is something I'd like to be solved. Thank you for your attention!
UPDATE: Just did a clean installation and now it works fine and can be accessed remotely at any time. Thanks to anybody that tried to help!
i tried both noobs and raspbian on sd card to try to boot the raspberry pi 3 but none of them seem to do the job (if the sd card is the problem )
when i power it up , there are 2 lights , red and green
there is a sign that the keyboard and mouse are working , but still
NO DISPLAY on the laptop screen !!!
p.S : i'm using an hdmi cable that used to be working with our tv .
Did you verify the install before attempting to boot? I did the same from my Linux Mint box and it did not format it properly the first time. You have to verify the install per the Raspberry OS install instructions before attempting to boot with it.
Once verified, make sure you insert the card while the power is disconnected from your Pi. Also make sure you have your HDMI, keyboard, and mouse plugged in BEFORE connecting the power the first time you boot. Also, if you plug the power in before the HDMI the Pi 3 will boot to a headless state, plugging in a monitor after this will not work. You will have to unplug the power and plug it back in with the HDMI left plugged in.