Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 10 replies
  • Subscribers 666 subscribers
  • Views 1935 views
  • Users 0 members are here
Related

Raspbian Jessie dosn't boot up the GUI after an update!

Former Member

I just installed the latest Raspbian Jessie on a microSD card (without Noobs), I inserted into my Raspberry Pi 2 Model B and the OS started well.

But there is a very strange problem that came out after I did the following:

sudo apt-get update
sudo apt-get build-dep qt4-x11
sudo apt-get build-dep libqt5gui5
sudo apt-get install libudev-dev libinput-dev libts-dev libxcb-xinerama0-dev

After doing that, I wasn't able to start the GUI interface: my RPi seems to performing the boot (white text on black screen) but after that, the desktop interface does not appears anymore! The display is completely black, and the backlight of the display seems to blink and the OS does not start!

Any idea about which can be the cause of that behaviour?

Parents

  • I found the solution: at the first boot, since I didn't use NOOBS but the raw image, the file system has to be expanded before doing anything else.

  • in reply to Former Member

    Hello,

     

    I have the same problem. Could you send some details how do you "expand file system"?

     

    Thank you

  • in reply to Former Member

    I realize it's been a while since you guys had this problem, but it just happened to me now.  I have Raspbian Jessie on RPi 3.  I ran an update command and it seems that I ran out of space on my 4GB root partition - a "df -h" command confirmed that.  A reboot (which I regret now) brought me to this point where the pre-GUI booting sequence seems to be fine, but when the GUI is supposed to come up, it remains stuck with the black screen and a blinking cursor.

     

    @lasersrl, @Maciej Jozefiak - I appreciate that you both found the solution, but the mystery is killing me.  Could you please tell me how you solved the problem?  All I managed to find on expanding the file system unfortunately required the boot to finish successfully and then do the expansion with some raspbian commands.

     

    Thanks.

  • in reply to elementzero

    Hi,

     

    If the file system is full then you either need to move or remove some content (either your own content, or by removing installed packages) or start from scratch with a new install.

    You can't do anything if you've run out of space, unless you remove some stuff or move it to off-board storage.

    If that doesn't work (e.g. corrupted card due to rebooting when it had failed to boot), then personally, assuming you've backed up your content, I'd suggest starting again with a fresh install and this time keep an eye on disk space.

    If your Pi 3 is set to boot into the GUI, then you can still access the console via the serial port - however the wonderful Pi people broke it : ) it has variable speed, so you'll need to guess and play around with different UART speeds until you get lucky. It can be hard-coded to not vary in speed, but that assumes you did that before you ran out of disk space..

  • in reply to elementzero

    How large is your micro SD card? If your card is somewhat larger that the 4GB, you may be able to use GPARTED to expand the space on the card. I have used this several times to get the space larger.

  • in reply to shabaz

    Thanks, shabaz.  I would have loved to be able to get to the point where I could free up some space on the SD card, but without the ability to finish the bootup sequence, I could never get there.  I don't have another linux system (maybe that's my cue to buy another Raspberry Pi image ) and Windows and Mac could only see the boot partition (FAT16) - some 60MB total of which 20MB were occupied.  On the positive side I did manage to install a free utility that could read the Ext4 partition on Windows, so at least I could do a full backup including my stuff.  The utility couldn't write to Ext4 so, again, that freeing up of space couldn't happen.

     

    In the end I did exactly as you suggested:  started from scratch with another Raspbian install.  All I need to do now is to copy back my files.

    Thanks again.

Reply
  • in reply to shabaz

    Thanks, shabaz.  I would have loved to be able to get to the point where I could free up some space on the SD card, but without the ability to finish the bootup sequence, I could never get there.  I don't have another linux system (maybe that's my cue to buy another Raspberry Pi image ) and Windows and Mac could only see the boot partition (FAT16) - some 60MB total of which 20MB were occupied.  On the positive side I did manage to install a free utility that could read the Ext4 partition on Windows, so at least I could do a full backup including my stuff.  The utility couldn't write to Ext4 so, again, that freeing up of space couldn't happen.

     

    In the end I did exactly as you suggested:  started from scratch with another Raspbian install.  All I need to do now is to copy back my files.

    Thanks again.

Children
No Data