Ken,
Here’s a couple thoughts:

— The first time you connect to a new device using SSH you should get a message about the host (or device you are connecting to) not being verified and asking if you want to trust it. This happens the first time you connect and your SSH client will remember the “fingerprint.” If you flash a fresh SDcard then the next time you connect you will get a warning that the signature has changed and the host is no longer trusted.?
— When using SSH that you will not see asterisks when putting in the password.
— If you have an iPhone or iPad, I recommend an app called Network Analyzer Pro (there is a lite version too but I paid for the full version, it’s not a subscription but a one time fee). This app allows for scanning your LAN and showing all the devices on your network. Once you know the IP address for a device you can give it an alias to make it easier to differentiate it from other devices in the future.

My initial question to you is whether or not you are receiving the warning when you connect to your Pi for the very first time. If not, you are not connecting to your new Pi.?

Jay
73 de N0SR

开云体育

I, too, upgraded PAT Menu using BAP 3.0.2 and lost Winlink capability as described in the link below:??

Um....I'm outta ideas (for the moment) Ken. Sorry about that.

Hey agn. Ken;

Got the power hat and case recommended above. ?Modified it for use with the power jack and also drilled some holes in the top for the fan. ?Had a nice pretty pattern laid out but due to lack of a drill press it didn't end up as pretty as it looked in pencil...whatever, still just as functional I guess.

I use An app on my phone called WUM Wifi, It gives a lot more information on the stuff connected to the router. With my Bell Fibre op, the router shows Mac address and the IP address of the unit. The app USUALLY gives more. I also find the mac address of the PI, and assign it to a specific PI. helps me keep it straight in my head.

Steven
VE9SY

Great on the Progress OM !

If you want a "write-up" on this (videos are sometimes harder to follow for some of us (like me !!)) you can go here;
/g/KM4ACK-Pi/message/1039

( As for your current "situation", what comes to mind immediately is TWO raspberry pi's on the same network. IF that is the case, the router WILL assign two ip addresses (normally) but YOU might have trouble knowing which is which UNLESS you have given one of them a DIFFERENT "hostname" but you have given the earlier/older rpi a new user password.

ALSO, if you did not get to a password prompt (and instead got a longish error message), you might have to "work-a-bit" on the ~/.ssh/known_hosts file of the computer you are using to access the new rpi ).

Thanks Jason
I'll do as you suggest.
I read the change log? and couldn't see anything that might be responsible for the WiFi issue.

73
Bruce G4ABX

Hey Ken OM;

Yep the files are suppose to disappear from the /boot partition/directory on boot-up if things are working o.k. !! ..... You can check this by looking at the /etc/wpa_supplicant/wpa_supplicant.conf file that is in the "other" (root) partition. <- It should be the very same file you placed in the boot partition.

That being the case; it seems like you might have a networking "issue/problem". Please check and look for the proper SSID and PASSWORD in the wpa_supplicant.conf file. (First thought on my part.)

es vy 73 om de "baab" w9ya

After burning the SD card and, after I create the SSH file and the wpa_supplicant.conf files in the root folder of my SD card, install SD card in the Pi and try to find it's IP address....which doesn't show up, as below the two files have disappeared.

After the Pi didn't show up on my Router's list of connected devices, I removed the SD card and re-mounted it on my desktop computer from where it was generated...the two files have disappeared from the SD card. It appears that the Pi is removing the files.

After doing this a couple of times. I very carefully checked to be sure the files were on the SD card before I plugged it into the Pi. I did this by ejecting the card, re-mounting the card (in it's USB holder) and sure enough the files were still there.

BUT!!!!! gone after trying to boot the Pi to find the IP address.

By the way, the Pi is a 3B (not +). The OS is the Pi OS desktop as Jason has recommended for the regular Pi computers.

Any suggestions??? Jason, anybody???

Ken
KB4XT

Bruce,

There was nothing in 3.0.3 that should have messed with the wifi. I think this is just coincidental. One suggestion might be to disable the hotspot using hotspot tools. Reboot and then enable the hotspot. I ran into a similar issue once and this seemed to "reset" things. Also, if you aren't actively using the hotspot and the pi is in the shack most of the time, you can also leave the hotspot disabled. This will prevent it from running.

To see what was changed in 3.0.3, check out the
--

There has been a bug found in 3.0.2 & 3.0.3. If you update Pat Menu using the build a pi script, you will lose your Pat Menu config file.

I will get this resolved in 3.0.4 which we are already busy working on. For now, either copy your config file to your desktop so you can restore after updating Pat Menu or write down your settings before updating so you have a reference point.
--

Thanks for that
cheers
Greg

Good evening all

I upgraded from 3.02 to 3.03
That went smoothly. everything appeard to work.

Now here is my problem:
I run the Raspi-4b 'Headless' using VNC from various Macs/tablets I have around.

On 4 occasions today, post upgrade, the Raspi has lost its wifi connection and the Wifi 'Fan' has reverted to opposing arrows.
Each time I've connected an HDMI screen directly to the Pi and had to reboot the Pi in order to see anything on the screen at all. (Just plugging in the screen did not bring up any image on the Monitor)

I checked the status of Wifi from other computers whenn the VNC 'failed' and it has been solid -- so the Raspi hasn't lost Wifi becuase -- say a router has packed up.
It seems to have unilatterally 'lost' its wifi connection (and of course the VNC connection)

The only change I've done is the upgrade from 3.02 -- which incidently had been solid and 'up' for 2 weeks without a glitch.

Once I can 'see' the Raspi on the monitor, following a further 'controlled' reboot from the menu, the wifi comes up normally -- as if nothing was wrong -- either now or in the past.

Thoughts, Ideas or suggestions please.

Many thanks
73
Bruce G4ABX

On Tue, Aug 18, 2020 at 09:16 AM, David Thompson wrote:

HiFiBerry case

Thanks David, I’ll look into that!
Jay
73 de N0SR

Thanks to all, for what they do for me.
Until now I was becoming very unhappy.
I am new to Linux and was not following very well.
Again thank you one and all.
Jason, thank you. my order is here.
Ronnie