|
Post by redlance305 on Dec 6, 2014 18:41:43 GMT
Followed normal instructions for creating the RaspiVoice SD card, no problem. System worked fantastic.
Was wondering what the LED was for, now I see.
Did a apt-get update and got-get upgrade and rebooted the system..
Waited..
After about 5 minutes I hooked up a monitor, and was presented with: sh: can't access tty; job control turned off /#
If I unplug power and restart, unplugging eh RaspiVoice, waiting a few seconds, then plugging it back in. The system boots fine.
... Did I miss a step?
~David
|
|
|
Post by Admin on Dec 7, 2014 0:46:54 GMT
Hi David
As you probably have figured out by yourself now, the button is just to easily test that RaspiVoice is ready to receive serial data. When you press it, you just hear the words "Ready and waiting". At the same time the LED also lights up while any sounds are being generated. This helps with debugging if your speaker volume is turned down or something similiar.
Regarding the issue you experieced after doing the apt-get update... I will try to see if I can replicate the issue here. So, do I understand correctly... you Raspberry Pi works fine and boots up etc, but RaspiVoice is not longer working after the apt-get?
Also can you try to go to the RaspVoice folder and start the RaspiVoice app manually using the command "sudo ./raspivoice", just to see if that works.
|
|
|
Post by Admin on Dec 7, 2014 2:24:50 GMT
Hi David Ok, I was able to replicate what you had. I did the following - sudo apt-get update
- sudo apt-get upgrade
- sudo reboot
And then I also saw the "sh: can't access tty; job control turned off" message. However, after I did a proper power cycle reboot (removing power to the Pi), then it booted up and RaspiVoice itself worked just fine again. Can you please confirm that your RaspiVoice itself also worked again after the full reboot?
|
|
|
Post by redlance305 on Dec 7, 2014 15:05:17 GMT
Followed normal instructions for creating the RaspiVoice SD card, no problem. System worked fantastic. Was wondering what the LED was for, now I see. Did a apt-get update and got-get upgrade and rebooted the system.. Waited.. After about 5 minutes I hooked up a monitor, and was presented with: sh: can't access tty; job control turned off /# If I unplug power and restart, unplugging eh RaspiVoice, waiting a few seconds, then plugging it back in. The system boots fine. ... Did I miss a step? ~David
|
|
|
Post by redlance305 on Dec 7, 2014 15:05:59 GMT
(sorry getting used to forum)
Attempted to just unplug the power to restart, 4 times.. each time it returned the "can't access tty" error.. Soon as I unplugged the board, while powering up and plugged it back in, it worked perfectly.
Even tried rebooting from terminal a couple of times, not that it would be different.. Same results.
~David
|
|
|
Post by Admin on Dec 8, 2014 9:30:34 GMT
Questions : 1. Did it boot up correctly before you did the update and upgrade? 2. Do you have your Arduino connected to the RaspiVoice while this is happening? If so, what happens if you disconnect the Arduino and just leave the Raspivoice shield plugged in? I did some Google searching and it sounds to me like the Raspberry Pi trying to boot up in safe mode. Apparently when the RPi senses that pin 5 (GPIO3 on the B+) is connected to ground, it triggers NOOBS into safe mode (the command-line prompt you're seeing). One can avoid it by adding the following modifying the /boot/config.txt file by opening it with: sudo nano /boot/config.txt and the adding the line: avoid_safe_mode=1 and saving the changes with “Ctrl-X”, which has to be confirmed with “Y”. It is worth a shot to try that. I am also very curious why you are experiencing this. --------------------------------------------------------------------------------------- By the way... I saw a post on the .raspberrypi.org/forums that someone experienced exactly the same problem as you after issueing "sudo apt-get update" and "sudo apt-get upgrade". See www.raspberrypi.org/forumsThe advice they got was : I think they are referring to this file : /mnt/raspberrypiroot/boot/cmdline.txt ---------------------------------------------------------------------------------------
|
|
support@raspivoice.com
Guest
|
Post by support@raspivoice.com on Dec 9, 2014 9:19:13 GMT
Hi David I have also been playing a fair amount with this bootup issue today and I’m convinced that this is just voltage related. I was able to reliably replicate the same bootup issue. Here is my findings: 1. The micro USB cable can cause this. I have two USB cables. One is a nice thick one made for fast charging cellular phones, and the other one is a rather thin cheap one that I received with some inexpensive product. With the thin one I can replicate the issue all the time, but with the thick one not. If I measure the voltage over the power pins with a mulltimeter, I can see that with the thin cable I only get about 4.4V on the supposedly 5V line. And with the thick one about 4.6V. 2. I also found even when I power my Raspberry Pi with the thick cable from either my powered USB hub or my laptop USB, then I also sometimes get this issue, but when I plug it directly into my desktop PC or its side USB ports, then it boots up correctly every single time. 3. I then decided to try and power the unit up from an external power supply (instead of using the micro USB cable). IfI set my power supply to 5V on the dot, then absolutely no issues at all. Also even when I reduce the voltage down to 4.6V it still works fine. But at 4.5 it becomes a bit dodgy... sometimes I get the problem and sometimes not. Usually if it goes past that point where the problem occurs then it runs fine. If I reduce the voltage all the way down to 4.4V my Raspberry Pi boots up with this same "sh: can't access tty; job control turned off" issue that you get. 4. The last thing I tried was to use the power supply at 5.0V but play with the current limiting. If I set the current limiting to anything less than 350mA, then it also gives the same bootup error. But the interesting thing in this case is that voltage dips must be so fast that I cannot even see it with a multimeter. On the multimeter reading it looks like the voltage stays on 5V and my power supply shows the Raspberry Pi is drawing about 280 mA. When I also supply the Arduino from the RaspiVoice shield then it draws about 320 ma due to the additional load from the Arduino board. I found in this case that my current limitation of 350mA is marginal whether or not the Raspberry Pi will boot up or not. Therefore I strongly advise that you try a different cable or USB port. I think what happens is that with the RaspiVoice shield and Arduino connected the supply voltage on your Raspberry Pi might also drop just enough that your get this problem. And if possible, try to measure the voltage on the 5V line of you Raspberry Pi (Pin 2 and 6) of the image blow and see what you get there.
|
|
|
Post by redlance305 on Dec 9, 2014 23:33:54 GMT
Interesting:
I never gave it much thought before I did the upgrade. Most online instructables always suggest doing a upgrade/update after setting up an SD card, so I just did. Without thinking.. While doing all my testing, I am using a Raspberry Pi B, with 8gb and nothing else attached.. Hooked to a speaker and a network switch.
Ok I've searched high and low for as many different USB chargers as I can find..
I have 2.4 amps, 2.1 amps and a 1 amp...
Here are the voltages returned 2.4 amp - 4.69 volts 2.1 amp - 4.66 volts 1 amp - 4.67
All three returned the same results when reboot after a good start. Even after I tried an assortment of cables. Most of my 'bench' cables are 10 footers purchased from SparkFun electronic..
Wow, I learned something, I was able to get composite video working by editing the config.txt file.. Impressed!! Big Thanks! Seems they want to force HDMI in NOOBS.
Nothing shows in /mnt/raspberrypiroot/boot/cmdline.txt, blank. - added avoid_safe_mode=1 to sudo nano /boot/config.txt...
~David
|
|
|
Post by Admin on Dec 13, 2014 2:56:03 GMT
I'm a little bit confused now. Is the booting issue still happening or is it gone now?
If gone, which of your actions resolved it?
And if still happening, then maybe another option would be to just reload the original image on the SD card without doing the upgrade/update. Or do you think this issue also happened before did the upgrade/update?
|
|
|
Post by redlance305 on Dec 13, 2014 16:45:27 GMT
Good Day.
Today I recreated a new SD card with RaspiVoice image. Modified the /boot/config.txt file. and make sure I was using 2.4 amp power source. WITHOUT running raspy-config or any updates.
Results: First startup, get the "Ready and waiting" SSH login then did a sudo reboot Then nothing..
Pull power reboot, get Ready and waiting.. Basically same results as before.. Will not work on SD card with this NEW image without modes see if I can figure anything out.
~David
|
|
|
Post by Admin on Dec 20, 2014 5:01:31 GMT
Thank you very much David for your continued feedback. Ok, here is my conclusion: I could reproduce the "sh: can't access tty; job control turned off" issue, but only under the following two circumstances: - If I used a bad power supply source that drops the voltage supply to the Raspberry to about 4.3V instead of proper 5V
- If I reboot using the "sudo reboot" command. If I plugging and unplugging the power supply (USB cable) then it does not happen.
I was also able to overcome the "sudo reboot" problem by editing the /boot/config.txt file and adding the line "avoid_safe_mode=1" as described earlier in this thread. This sounds to me like this ties up with your observations as well.
|
|