Raspberry image 1.4.1 - Pi will not boot

edited August 2022 in General
Now that I have my connectivity issues resolved, I thought I would try the new Raspberry image file 1.4.1

I have done a fresh install to another SD card but for some reason, it will not boot up.
I get the Repetier splash screen and a few file names scroll, but then end up with a blank screen and a blinking cursor, even after allowing over 10 minutes, given I understand the first boot can take a while.

I have also tried a different SD card which was reformatted, but still the same issue - no boot up.

I also note that despite setting the LCD rotation to 180 degrees in the initial config file, the screen is still upside down (cursor blinks at bottom right).

Would appreciate some assistance in relation to what I should try to resolve.

Comments

  • 1.4.1 is based on bullseye and that uses the new pi graphic driver where the rotate is not working always as expected. See https://www.repetier-server.com/download-images/ roatate screen section on how to rotate for at least the final browser view. The xrandr solution works fine and is independent from config.txt settings - here the x server rotates. Alternative use repetier-setup -> raspi->config  and select pi cam to use legacy driver. This switches back to old graphic driver where the settings still work.

    Question still open is why you can not boot or where it fails. What pi model are you using and what display? First start takes a while and even triggers a reboot after expanding file size, so waiting a few minutes is good.

    Also when you unpower and repower, does it still not boot?
  • edited August 2022
    Thanks for your reply.

    Comments re graphic driver are noted. I'll check out the link you provided.

    I am running a genuine Raspberry Pi 3B and an Official Raspberry 7" Touch screen.

    I will always get the Repetier flash screen on boot and then a few file names scroll before I get a flashing cursor.
    I have left the boot for up to an hour on a few occasions without success.

    I am running Samsung 32GB EVO SD cards and have tried a new download and image a few times, conducting full and quick card reformats before hand.

    I had no trouble whatsoever when I installed the current Raspberry version which is running which is V 1.3.0 V28.

    If I repower the Pi or remove and reinsert the SD card, this makes no difference.
  • This is strange....

    I obtained another SD card, reformatted it and imaged V 1.4.1

    It will boot up.

    If I make the network connections and then enter the licence details, it works until I turn off and start again next time. All I end up with is a blank screen and a flashing cursor (I have not at this stage fixed the screen rotation issue).

    I have tried this a few time now and the same result. Works once or twice and then doesn't.
     


  • Turn off means you shut down linux cleanly using shutdown function or just power off? You always should cleanly shut down the pi. We therefor have added a shutdown button in the main menu for pi. Without you might get corrupted filesystem or sd card defects sooner or later. But it is normally not that frequent that a restart already has it defect.

    If we forget the screen, can you at least connect to server or run ssh to login to pi. If you can run
    dmesg
    to see startup messages. The blinking cursor is just text mode, so it did not start x server with graphic interface. The question is more if that was just disabled e.g. through a update from linux or if something is really broken after restart.

    You might also just try the old buster based image. After install just update server in autoupdater to get last version. The bullseye version is new, also it runs stable or 2 month now on my pis.
  • edited August 2022
    By way of update:
    I turned on the Pi this afternoon and it booted up to V 1.4.1 I don't know why, given that yesterday I had no success whatsoever the last 4 or 5 times I tried rebooting the newly created 1.4.1 image.

    I backed up my Pi 1.3.1 version to another SD card and booted it up (Buster version)
    I then did the autoupdate to V 1.4.1 I encountered an error stating that it could not connect to 127.0.0.1 and I tried a reload, only to receive the same error.
    I left it for 5 or so seconds and then it actually came up with success on the update to V 1.4.1 and I now have that version on the Pi.

    Because I used the update method, screen rotation is still correctly set.

    Strange that it now appears to work, despite the errors and issues previously experienced.

    Thanks for your help with this Repetier.
  • edited August 15
    Need help!I install version 14.8 on raspberry pi3b, the installation begins and ends on the command (plymouth-poweroff.service),raspberry pi turns off, tried several different cards, cables and wifi
  • What did you do after burning image to sd card? On first startup image will adjust filesystem and reboot. Do not interrupt in that stage. Depending on sd card size and speed it can take a few minutes but after a while it should be running.
  • Repetier said:
    What did you do after burning image to sd card? On first startup image will adjust filesystem and reboot. Do not interrupt in that stage. Depending on sd card size and speed it can take a few minutes but after a while it should be running.
    after the command (plymouth-poweroff.service) raspberry pi turned off together with the monitor, I waited 20 minutes the green light on the raspberry pi does not blink((
  • Does repowering help? plymouth-poweroff.service is shutdown and that seemed to work, just the restart sounds to not happen here. If it comes up after repowering all would be ok I guess.
  • Repetier said:
    Does repowering help? plymouth-poweroff.service is shutdown and that seemed to work, just the restart sounds to not happen here. If it comes up after repowering all would be ok I guess.
    I did 10 times, in a circle the same thing
  • Beeing curious I burned a fresh image with pi imager using latest image from us (no modifications in settings!) and inserted it on a pi 3+.
    Ist started until interface appeared very shortly before doing the expected reboot. Then it came back showing the register interface and stayed there.

    So it seems the image is ok and works on pi3+. So how did you burn the image? Did it maybe download the image incomplete or which software are you using to burn? Pi imager knows the checksums so errors in image should be impossible with that software.
  • edited August 16
    Version (Repetier-Server 1.4.18) is not installed on raspberry pi3b, it is installed and works well in the version(Repetier-Server 1.4.15), I am very saddened(((( I have several bambulab))).
    ------------------------------------------------------------------------------------------------------------
    I was able to upgrade to the new version, but the monitor connected to raspbury pi does not work(((

  • Bambulab is planned for next big release 1.5.0. 

    What monitor do you use? Some need extra settings/drivers which must match the linux kernel version. Only HDMI displays with eeprom providing settings work out of the box.
  • Repetier said:
    Bambulab is planned for next big release 1.5.0. 

    What monitor do you use? Some need extra settings/drivers which must match the linux kernel version. Only HDMI displays with eeprom providing settings work out of the box.

    The monitor is connected via HDMI and the screen via GPO

  • Installed on PI3, work well installed. Only on 3B is installed through the old version. Thank you very much for your help, I'm waiting for a new version



Sign In or Register to comment.