MakerGram Logo

    MakerGram

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups

    Green Light not blinking on Raspberry Pi 3B on inserting Sd Card

    Raspberry Pi
    raspberrypi
    3
    5
    2129
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Gladiator54 last edited by

      Hi all,
      My raspberry pi 3b was working recently ... Installed raspbian os.. but lately on inserting sd card no green light blinks ... Just the red light is there for the power supply... The sd card is being read at other sd card readers or in phone but not in raspberry pi ... Have also tested other sd cards but have got no success... Pls do let me know what can i do ?

      S 1 Reply Last reply Reply Quote 0
      • S
        sreu13 @Gladiator54 last edited by

        @arunksoman , any idea on this

        1 Reply Last reply Reply Quote 0
        • salmanfaris
          salmanfaris last edited by salmanfaris

          @Gladiator54 are you getting any updates on the monitor? and how did you flashed the SD card? which OS are you used?

          1 Reply Last reply Reply Quote 0
          • G
            Gladiator54 last edited by

            No not as such ... I was using it for headless mode using putty... I initially flashed NOOBs using normal extract zip procedure to extract files at the sd card's location but it didnt boot then after resetting the sd card by formatting it on my phone ... installed Raspbian OS (Full Buster) latest version using Balena Etcher and Sd card formatter ... but no success after that ... I have also flashed lite version of NOOBs and Raspbian but no success either

            salmanfaris 1 Reply Last reply Reply Quote 0
            • salmanfaris
              salmanfaris @Gladiator54 last edited by salmanfaris

              @Gladiator54 There are some case raspberry fail to boot in my experience.

              • insufficient power from USB Adapter -> Try y to use 2/3 Amps Adapter

              • Broken Micro SD Card / OS FIle -> Try another uSD card

              • Polymeric Fuse failure -> It's self-resetting and usually return to normal operating parameters within a finite time, in such case check any shortage in the board PCB like small wires/coppers ..etc.

              You can try load a new Raspbian OS with GUI and connect HDMI Monitor, if any error occurs you can see that, keep an eye on the ACT led (Green).

              1 Reply Last reply Reply Quote 1
              • First post
                Last post

              Recent Posts

              • Testing Raspberry Pi's Camera Module 3 (NEW for 2023)

                • read more
              • 1666287f-258d-437d-b2c5-91851d08617c-image.png
                The classic compact camera for Raspberry Pi with a 12MP sensor and autofocus

                Available from $25 with your choice of standard and wide lenses, with or without an infrared filter

                bf34763e-5ba3-4962-8e92-75583fd1e96c-image.png

                More details: https://www.raspberrypi.com/products/camera-module-3/

                Raspberry Pi Camera Module 3 - Autofocus cameras!

                Resource:
                Documentation: https://www.raspberrypi.com/documentation/accessories/camera.html
                Camera Software: https://www.raspberrypi.com/documentation/computers/camera_software.html

                • read more
              • Hey @rafitc99 ,

                Did your issue resolve? Curious to know 😊

                • read more
              • @rafitc99 said in NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2:

                host="MyRPiAPMode"
                sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
                sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
                sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
                sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
                sudo nmcli radio wifi on
                sudo nmcli con up $host

                Hi @rafitc99, Are you able to set up the AP when trying the commands individually?

                • read more
              • I was trying to configure AP mode in Raspberrypi by using Network Manager. I'm using the below script. but it is throwing some errors.

                Bash Script to set AP Mode

                host="MyRPiAPMode" sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword" sudo nmcli radio wifi on sudo nmcli con up $host

                Error ----

                Connection 'MyRPiAPMode' (60965f2a-f510-48ef-afaf-0864242d0c06) successfully added. Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).

                nmcli con (After script execution)

                NAME UUID TYPE DEVICE Wired connection 1 9589ff1a-9923-3de3-a8a4-90b319661878 ethernet eth0 MyRPiAPMode 60965f2a-f510-48ef-afaf-0864242d0c06 wifi --

                nmcli dev

                DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi unavailable -- lo loopback unmanaged --

                I tried to make it availble via sudo nmcli radio wifi on
                But not working.

                this is the log

                -- Journal begins at Sat 2021-08-07 09:28:21 IST. -- Aug 10 15:06:19 NWPI-b5b072 NetworkManager[16140]: <info> [1660124179.9816] audit: op="connection-update" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" args="802-11-wireless-security.psk" pid=25120 uid=0 result="success" Aug 10 15:06:20 NWPI-b5b072 NetworkManager[16140]: <info> [1660124180.0902] audit: op="radio-control" arg="wireless-enabled" pid=25125 uid=0 result="success" Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4241] agent-manager: agent[641f99ab55d9691c,:1.692/nmcli-connect/0]: agent registered Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4281] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0573] agent-manager: agent[70ee130ba0f26cd7,:1.696/nmcli-connect/1000]: agent registered Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0614] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0370] agent-manager: agent[cc77ef461499c164,:1.700/nmcli-connect/0]: agent registered Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0414] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8406] agent-manager: agent[79b01af218789b42,:1.702/nmcli-connect/0]: agent registered Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8446] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."

                • read more
              By MakerGram | A XiStart Initiative | Built with ♥ NodeBB
              Copyright © 2021 MakerGram, All rights reserved.
              Privacy Policy | Terms & Conditions | Disclaimer | Code of Conduct