Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does the pre-compiled disk image works? #46

Closed
phlau74 opened this issue Apr 17, 2014 · 7 comments
Closed

Does the pre-compiled disk image works? #46

phlau74 opened this issue Apr 17, 2014 · 7 comments

Comments

@phlau74
Copy link

phlau74 commented Apr 17, 2014

I tried the pre-complied disk image with my Ethernet connected Raspberry Pi and it just does work.
During the booting I saw "check syslog for diagnostics ...failed" and isc-dhcp-server ...failed" - are this critical?

Once I log into pi, I ran the boot.sh, saw a whole lot of script but it just doesn't response to anything. Did I missed out anything step?
Or should try manual configuring
Help help! Someone please advise.

@nicktones
Copy link

It does work, with some tweaking. I had the same issue as your self, follow the instructions in the first reply on the closed issue below:
#11

@phlau74
Copy link
Author

phlau74 commented Apr 18, 2014

Hi nicktones, thanks for your reply. I am connecting my Raspberry Pi to Ethernet cable( not wireless), plug in an usb keyboard and microphone. Connect to a monitor using the HDMI. Anything wrong with my setup? Must I really need to be using wifi?

"[FAIL] check syslog for diagnostics. ... failed!"
"[FAIL] startpar: service(s) returned failure: isc-dhcp-server ... failed!"

@nicktones
Copy link

No problems, all looks good.

You should still be able to use Jasper with those errors. It is just failing to setup the DHCP server which is initially used when setting up wifi.

@phlau74
Copy link
Author

phlau74 commented Apr 18, 2014

Once I ran the populate.py and reboot, jasper should auto start after the reboot, right?

After reboot, I tried to speak to the usb mic but no response. Anything I missed out?

Thanks.

@nicktones
Copy link

It should, but it doesn't the first time sometimes. Have a read of the post below, which talks about manually starting Jasper. I've found that after starting it manually it starts automatically on reboot after that.
#36

@nicktones
Copy link

Just to confirm, do this -

cd jasper/client
python ~/jasper/boot/boot.py

@tiny-tinker
Copy link

I was having a lot of issues with the pre-compiled image and for some reason running boot.py as @nicktones mentions is important. I was doing:

cd ~/jasper/boot
python boot.py

That kept overwriting the /etc/network/interface file and causing Jasper to fail to connect to the internets (I could ping google.com just fine before running this command). I hope that helps someone. Thanks nicktones!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants