![]() Since I didn't have internet on the Pi, I couldn't use apt-get. From there, I eventually decided to attempt to Remote desktop in. I connected to my Windows machine with g_ether, and was able to SSH into the pi from raspberrypi.local over USB. I do not know why it was asking for password when that user did not exist on that device, but don't let it fool you, just because it shows the user does not mean that the user exists on the machine you're connecting to. I had properly configured the wpa_nf file, but I specified a 5GHz network instead of 2.4GHz. The Raspberry Pi can only connect to 2.4GHz networks. I've figured out the issues and got in, here's how I did it. ping statistics -ĥ packets transmitted, 0 received, 100% packet loss, time 4151ms TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Ifconfig for the USB ethernet connection returns this: usb0: flags=41 However, I'm getting errors while running sudo apt-get install tightvncserver: Err:41 stretch/main armhf tightvncserver armhf 1:1.3.9-9Ĭannot initiate the connection to :80 (2a00:1098:0:80:1000:75:0:3). I was able to successfully share my internet from my work MacBook and SSH in. After some tinkering around (I'm not entirely sure what changed), I was able to SSH in via an emulated Ethernet over USB as That means my real issue is with connecting to the WiFi - something I've already spent 2 hours trying to get work while connected with g_serial.Įdit3: I decided my best course of action was to try and set up a VNC server on the Pi. Maybe there is some way to generate an SSH key for the pi? (I don't have a Mini HDMI converter so the GUI is not accessible)Įdit2: I was able to get into the terminal via USB OTG, and the default password worked. I am absolutely certain that raspberry is the correct password, as multiple online sources have confirmed it, and I am certain I've type it correctly (I even had a friend type it for me to no avail).Įdit: I've tried from MacOS, Windows, and Android (Termux with OpenSSH installed), and I've tried connecting over USB instead of WiFi. ssh folder, which are for something else (so they don't work of course) and eventually falling back to publickey,password,keyboard-interactive, where it asks for the password again. I get the same password query again, and upon entering it: Received disconnect from 192.168.0.102 port 22:2: Too many authentication failures.Īdding -v for debug just shows it trying all my local private keys in my. It will repeat the password: field 3 times, then ask for password.Īt this point, I get "Permission denied, please try again". It asks for the password, so I type raspberry, as per the online guides. ![]() I log in with which I've confirmed to be the devices' IP Address. I've tried SSH'ing in from multiple different computers, and the problem is the same every time. I've tried installing both the latest Raspbian Stretch lite and the latest Raspbian Stretch with desktop, and was able to get it set up for SSH by configuring the wpa_nf file with WiFi credentials and creating an empty ssh file. It will give you a list where your USB device should be included.I'm trying to set up a Raspberry Pi Zero W as a headless device on my local network, and am performing the initial setup with a fresh copy of Raspbian Stretch To check this, run the mount command without and parameters. Again this can be set on /etc/fstab or maybe somewhere else depending on what you might using in addition. However, if this flag is set during mounting, your files on that device can't be executed - only read and write is permitted. In addition mount can set a device as noexec which pretty much is an good idea for devices as USB-sticks or unknown CD/DVD. Using udev or something else, somewhere else it can be also configured (read: than it depends, what you are using to mount the stick) On traditional Linux systems this can be configured in /etc/fstab. to execute something is based on the umask used for mounting. BTW: When compiling a C file via Geany, it's already set to be executable.Īs you mention your USB stick is formatted with FAT32 which is not supporting the POSIX things here so chmod will not take any effect. So chmod +x should work on most systems using e.g. x-x-x or in hex 0111 on POSIX file systems. To run a file on Linux the user needs to have the x either on user or group.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |