If you search this forum you will see that I had the same problem on RPI3b+ and changing the country code does not always work - e.g. Ubuntu Mate . Raspbian it worked. "Grey" imported AP's also seem to cause this problem as they are built for the country they are normally sold in and have different REGS/freq etc - its just a mess
Hope the country code works for you.
I have set up 1000's of networks,some very large and complex , over the years and I know my statement is true.
"But, firstly my point is that the rpi can connect direct to another PC with Ethernet cable without the need for a static ip, just plug the cable between and it works straight away"
This only works if either a DHCP server is available somewhere on your network , you have a static address defined in the Wired Ethernet settings or you have connected via the Ethernet(wired) before and the lease time provided by DHCP that you originally connected to hasn't expired - the latter should fail but I have noticed this does work sometimes.
This is standard networking, be it Windows or Linux
IMHO - the bottom line ,at this moment in time, is to have a "script" to enable "normal" users to easily build a fully working Kstars/Indilib etc system on a RPI4 and not worry about 4k monitors used with Remote working. Nobody really knows how long a stable and fully working Ubuntu Mate on RPI4 will be .
Astronerd has this working on his system anyway
So thank you,on behalf of "normal" users, Rlancastle for your efforts.
Must admit for now I have gone with a straight forward 4gb Gigabyte Brix dual core 2807 which is about the same size as RPI but has a Sata interface (so I use SSD's) and Ubuntu Mate 19.04 works (together with Kstars/Indi/Ekos) out of the box AND can be updated simply. And not a real difference in price or performance after adding case,cooling system power supply.
After much digging and playing _ good job its high summer - I found the problem.
All my wifi ap/routers work great with every piece of kit I have in their std set up.
Ubuntu mat 18.04 on RPI3b+ does not like GB Wifi settings and no matter how many times I changed this to GB it reverts back to global and does not work on the 5ghz band.
So changing my routers/Ap's 5ghz settings to work on a set channel and band width - the Ubuntu Mate 18.04.2 works - this has got to be a BUG.
RPI-CONFIG on Ubuntu does not give you the option to change the WiFi Country however on Raspbian RPI-CONFIG you can change the WiFi country - how annoying. So if you are unlucky enough to have this problem check you AP/Router settings and change to a channel and band that is supported by 18.04.2 on RPI3b+
I am going to check if there is a setting in the config boot files.
I agree - RPI3b+ was late (and some of us are still having problems with it using the Beta.2 ) so how much later is RPI4 going to be if RPI3b+ isn't fully released yet. The guy has only so much time and compared to Raspbian seems to lack people resources.
Maybe Jasem has the same problem in supporting Raspbian versions ?
But at least Raspbian comes out with the new hardware - even if it still has a few problems.
If its a case of "someone" doing the donkey work to get a supported Raspbian version with automatic updates as per the present Ubuntu Mate (not compiling from some) I would stick my hand up to help in some way.
Frustrating I guess for all
Went back to basics down loaded latest Ubuntu Mate 18.04 (again) and ran through the APT Update etc etc (again) - wired works first time again.
Then tried 5ghz wireless it asked me 5 times for the password (each time was correct - even got the Wife to check) . Still US !
I have used 5ghz with all my computer kit - it all works but I cant get Ubuntu Mate 18.04 to work with 5GHZ using my standard TPLink kit
It even works with 2.4ghz on the same router (TPLINK dual band 5 and 2.4) - tried a different router(not TPLINK but dual band) - same. Even tried switching off security still asks again and again for password then fails. Log just says taking too long and fails.
P.S. Raspbian on same RPI3b+ no problem with any connection 2.4 or 5ghz - so I am at a loss
I have no hair to pull out else I would !
Cant see why software update has caused this but only he Dev's will know for sure. Maybe someone will answer who knows.
Do you have a backup SD which was before the upgrade - if yes try that and see what happens!
However it could be your Power source is degrading for some reason showing a problem - plus longer or poor quality cables can also give the same problem. Have you another power source to try. Even if you haven't changed anything.
Normally you never see this via any VNC software (ones that I have used anyway) even if its shown on a monitor connected to the RPI. But the boot logs do show if this is happening.
Useful info Hans
I notice that Stellarmate has been updated to Mate 18.04 and I am told 5ghz Wifi works.
I have tried this on a std Indi installation (Not Stellarmate) on Mate 18.04 and it doesn't (or didn't) what was changed on the Stellarmate version to make 5ghz work - if thats not giving away trade secrets - LOL
Have you been able to try your RPI4 set up for real yet ?
But there is still the old problem - people do not want to compile(build) Kstars/Ekos on Raspbian. They want the equiv of Unbuntu Mate PPA installation / updates - does that exist and more important does it work? Plus on RPI3b+ after a std compile/build (following std instructions on this forum) the button icons are just "std" large icon which I guess if down to a theme not being present?
Again many people bought RPI4 straight away,not me, expecting Kstars/Ekos/Indi to run without compiling/building - maybe the Indi requirements should be better described via a simple "Truth Table" showing which flavours of hardware/OS require compiling/building and which do not , are supported by an update mechanism (not requiring recomp etc) etc.
I know what Indigo server is thanks - I was referring to,I believe, the non existent Indigo Equiv of free Kstars/Ekos (really the EKOS part) - All I have found runs on Apple OS's only except Pixinsight (which is not free and would seem to too resource hungry for RPI4 - but I have not tried it on any RPI). e.g. AstroImager, AstroGuider, AstroDSLR, AstroTelescope, INDIGO Control Panel and INDIGO Dashboard.
Quote "so called agents" - what does that mean ?