Reposting this in networking hoping to get an answer.

I bought a Rpi, finally got it working, after trying many systems. I got Raspbian loaded and tweaked a bit with remote log-in that I'm still not able to log into. My first question is I can log onto one wifi signal, my android hotspot, but not on the other the land based router. I don't understand why it would log on one, but not the other...?!?!


So why is it logging on one wifi but not the other...?

I got a "error 15" sigterm come up after it was trying to log on, after 4 way handshake established. It was reading the mac and trying to get an ip address, but kept resetting, then code 15 came up.

The other wifi logs on OK I get internet.

Usually it's your login/password.

If you're on wpa encryption, have you run wpa_passphrase? The format is

wpa_passphrase Essid password

It returns a chunk to put in wpa_supplicant.conf

The usual reason for not being able to log on to a network is an incorrect password. Not always, but probably close to 99 of the time.

Thanks guys, I have the correct password, I log on with windows no prob.

I'll try this way with Business guy says: wpa_passphrase Essid password
It's wpa2 encryption, does that make a difference?
I suppose I have to log on with the command prompt since the desktop just asks for password.

OK I ran sudo wpa_passphrase Essid password
and got

ssid="Essid"
#psk="password"
psk= "A939393bunch2321of22020numbers"

Now I put 'the whole thing' into; wpa_supplicant.conf
So being a newbie, how do I get into wpa_supplicant.conf

OK I did /etc

Frustrating to be such a clutz again.

Running updates and upgrades
then installing some this and that...

Lots to do...

It's nice to make progress.

Problem now I can't log in as su... I get permission denied. :?

I set the root password, log in as root, and still get permission denied when I type

/etc/network/interfaces

/etc/network/interfaces is probably a directory. You can't execute a directory.
If root is not allowed to do something with a file, check the file permissions

OK I was able to get into the file, learned how to set root password. But there is something strange going on, when I click on the network image at the top right, I get a listing of all available networks, the strange thing is the first four networks show up like this, with a network signal at the end of each line.

/000///000///000///000///000///000//
/000///000///000///000///000///000///000//
/000///000///000///000///000///000///000///000//
/000///000///000///000///000///000///000///000///000///000//

After this the usual networks show up normally.
That's not normal, so I don't know what to make of this.

You do not set the root password through /etc/network/interfaces. That has nothing at all to do with the root password.

/tears hair out.

thenetworkinterfaces will probably be a list of network stuff. To set root passord, use
Sudo Passwd root

Hi Guys,

I'm making progress fast.
I now know how to set up root password, get into files, (have yet to get into syslogs). Got mc installed, another rpi setup as a server, able to log onto it, same network, but not from another network. Got putty working, though I don't get the rpi desktop, just prompt, able to issue commands to the shell.

I think this garbage...

/000///000///000///000///000///000//
/000///000///000///000///000///000///000//
/000///000///000///000///000///000///000///000//
/000///000///000///000///000///000///000///000///000///000//

... is picked up by the antenna, perhaps routers farther away, not completely identified. They come and go, from two lines, one line or sometimes no lines at all. But they're at the beginning, on top of the list of available networks.

Then I can't log onto a known network, land based router nearby. I log onto it with Window$ no problem, but not with the rpi. So I'm perplexed...

ooops, I saw something. The network logged on for an instant, then quit. I think something killed the connection, so how do I find out more about this?

1: Where do I find syslogs?
2: Where do I insert this code?

Found this code for sigterm:

It pops out the program responsible for the sigterm signal... I compiled a little "C" code (Hello World) and got it written in a file, and was able to run it from the shell...(Kool 8-)) the guy says it must be inserted at the start early, to catch the culprit. So it's in the boot somewhere. The call is 'sigaction()' and the program should be somewhere not too far away from the call. So I need a little help here, I'm newbie at C, though did a lot of C++ I'd say intermediate level, so not a total beginner.

Logs are in /var/log and subdirectories. As for the code, I have no idea what you're doing with that. It's C, so it goes in a C program somewhere, but I don't know what you're writing or what it's supposed to do. Compile it and run it, I suppose. It's a complete program, with a main and all. You don't provide much information.

Just being practical & pessimistic, do a backup before esting code in case it breaks something. Especially running code blocks you didnt write