So I got a 64gb card for the Pi, can't get it to boot. It did one time, installed the OS, now it won't boot. From the sounds of it, the Pi needs a FAT partition to be bootable, correct? I made a 4gb partition on the 64gb card and installed the OS, still nothing.
Oh well, I'll keep playing with the 4gb card for now.
I got tightVNC setup to run at boot, and I have a wifi dongle and pi camera on the way. I'll see if I can set up everything I want using wifi before trying to switch over to 4g.
edit: Nevermind, I didn't get it to run at boot. Noodle,
theseare the instructions I'm trying to follow. Since I'm a windows guy with zero programming experience, I'm used to creating a batch file and just dropping it into the startup folder. Do you know how I can do this on the pi? The default login using tightVNC is a sudo user, and I don't know how to change that so that I'm logged in as a superuser in the GUI. Trying to change permissions and move files/write scripts via the command line is annoying.
I recently set out to do exactly what you are trying to do bandwagon. I'm a total linux noob, and I found the exact same website but still ended up spending most of an afternoon getting it to work.
If I recall correctly, the problem is that command line to start the VNC server has an argument that was either deprecated or never worked to begin with. So, i'm talking about the bold line here:
#! /bin/sh
# /etc/init.d/vncboot
### BEGIN INIT INFO
# Provides: vncboot
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start VNC Server at boot time
# Description: Start VNC Server at boot time.
### END INIT INFO
USER=pi
HOME=/home/pi
export USER HOME
case "$1" in
start)
echo "Starting VNC Server"
#Insert your favoured settings for a VNC session
su - pi -c "/usr/bin/vncserver :0 -geometry 1280x800 -depth 16 -pixelformat rgb565"
;;
stop)
echo "Stopping VNC Server"
/usr/bin/vncserver -kill :0
;;
*)
echo "Usage: /etc/init.d/vncboot {start|stop}"
exit 1
;;
esac
exit 0
--------------------------------------------------------------------
You'll notice that's different from the command line arguments they use at the top of the article:
#!/bin/sh
vncserver :0 -geometry 1920x1080 -depth 24 -dpi 96
---------------------------------------------------------------------
Anyway, my mistake in debugging this was just in making that shell script, following their steps, restarting the thing and hoping it worked.
Instead:
1) Make sure a vnc server isn't actually running. There is a linux way to do this I think. I have no idea what it is. I just tried connecting from another PC on my network.
2) Run the shell script yourself from the command line. Does it work? Try connecting from your pc. Better yet, try executing just the single command line for starting the vnc server. Once you get that to work, put THAT into your shell script in place of the bolded line above, and then try the script
3) Once you get (2) to start a vnc server for you, try the boot sequencing steps. If the shell script works but the steps to start on boot don't work, then you're past my linux debugging skills.
Separately, there *might* be a default password setup by tightVNC. I just don't remember. If you connect from your PC and you're prompted for a password, then I'd say that you're making progress. Then you can worry about the password.