Monday, December 21, 2015
Raspberry Pi how to show less info at bootup
You can substantially decrease the amount of info scrolling by on the screen at bootup time by adding the word 'quiet' (without quotes) to the end of the first line of the file /boot/cmdline.txt
Raspberry Pi Custom Splash Screen (blank screen problem)
I followed the instructions found at http://www.edv-huber.com/index.php/problemloesungen/15-custom-splash-screen-for-raspberry-pi-raspbian for
a customized splash screen on the Pi. Everything went well, except….at the end
of the boot sequence, the splash screen disappeared and all I was left with was
a blank screen. I found out (by trying) that I could type the userid and
password blindly, followed by startx (also blindly) and then LXDE would appear
as normal.
Hunting around on the forums, I found a post that stated that if you were presented with a blank screen after booting, you should try pressing Ctrl+Alt+F2 to get back to a regular console screen. It worked. I hunted around some more for a better solution, but to no avail.
By the way, this problem does not occur if you have it setup so that you automatically startup startx after booting.
Hunting around on the forums, I found a post that stated that if you were presented with a blank screen after booting, you should try pressing Ctrl+Alt+F2 to get back to a regular console screen. It worked. I hunted around some more for a better solution, but to no avail.
By the way, this problem does not occur if you have it setup so that you automatically startup startx after booting.
Saturday, December 19, 2015
Screen blanking Raspberry Pi B+
I have a Raspberry Pi running headlessly as a display. Therefore, the screen should never blank.
Here's the link where I got the solution to my problem:
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=57552
User jwzumwalt came up with the post, I'm just repeating it here for my own reference.
The long and the short of it: there are 2 files to be modified
#1
change two settings in /etc/kbd/config
BLANK_TIME=0
POWERDOWN_TIME=0
#2
Add these lines to /etc/xdg/lxsession/LXDE/autostart
@xset s noblank
@xset s off
@xset -dpms
Then reboot and test.
Here's the link where I got the solution to my problem:
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=57552
User jwzumwalt came up with the post, I'm just repeating it here for my own reference.
The long and the short of it: there are 2 files to be modified
#1
change two settings in /etc/kbd/config
BLANK_TIME=0
POWERDOWN_TIME=0
#2
Add these lines to /etc/xdg/lxsession/LXDE/autostart
@xset s noblank
@xset s off
@xset -dpms
Then reboot and test.
Thursday, December 17, 2015
Error 98 Address already in use in Python
Sometimes bottlewebserver in Python on my Raspberry Pi hangs 'for no good reason'. Upon restarting from the LX Terminal window, the above error appears and Bottle Web Server will not start.
I've read Stack Overflow postings where, if you wait for one and a half minutes the port will free up and the server can then be started. This does not seem to happen in my case.
The only way to restart the server, other than a reboot, is to do the following:
The result will then give a line something like this:
Then simply issue:
I've read Stack Overflow postings where, if you wait for one and a half minutes the port will free up and the server can then be started. This does not seem to happen in my case.
The only way to restart the server, other than a reboot, is to do the following:
$ ps -fA | grep python
The result will then give a line something like this:
root 2130 1 0 11:08 ? 00:00:00 sudo python bottlewebserver4.py
Then simply issue:
$ sudo kill 2130
After this the bottlewebserver will start.
Monday, December 14, 2015
Putty network error connection refused
One of my Raspberry Pi’s that performs sump pump depth measurements every 5
minutes works headlessly. Last week it stopped supplying values via the network
to my other Pi, which does the reporting via a web page.
So I tried to reach the Pi via putty. Putty responded with “network error connection refused”. This led me to checking cables, and I found that everything was fine. To make a long story short, it turned out that a recent power loss must have caused a corruption within the networking setup of the Pi.
I hooked up a monitor, keyboard and mouse and did a “sudo apt-get update” followed by “sudo apt-get upgrade”, followed by “sudo apt-get upgrade --fix-missing”. Lastly, I reset the SSH keys by issuing “sudo rm /etc/ssh/ssh_host_*” followed by “sudo dpkg-reconfigure openssh-server”.
After this, things were back to normal.
So I tried to reach the Pi via putty. Putty responded with “network error connection refused”. This led me to checking cables, and I found that everything was fine. To make a long story short, it turned out that a recent power loss must have caused a corruption within the networking setup of the Pi.
I hooked up a monitor, keyboard and mouse and did a “sudo apt-get update” followed by “sudo apt-get upgrade”, followed by “sudo apt-get upgrade --fix-missing”. Lastly, I reset the SSH keys by issuing “sudo rm /etc/ssh/ssh_host_*” followed by “sudo dpkg-reconfigure openssh-server”.
After this, things were back to normal.
Subscribe to:
Posts (Atom)