sudo iw wlan0 set power_save off
I have successfully run through a full install and had no issues that adversely effect the application.
I use the Raspbian Stretch with desktop image: 2018-11-13-raspbian-stretch.img from here:
Everything to this point is now working. Who is willing to rest this out on a freshly formatted SD Card?
if it can wait Saturday ā¦ got a spare pi on which I can fool and most importantly, feed back. Evenings it is to short.
1 Like
I would like to know how many here use the RPi with built-in Wi-Fi and also have an adapter for a second Wi-Fi interface via USB .
Or if any of you have a Wi-Fi adapter via USB if the RPi does not have built in Wi-Fi.
Iām not having any luck with the scripts completing. I installed a new NOOBS, let it do the updates, manually ran
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo npm cache clean -f
but npm wasnāt installed so that command didnāt do anything. I then tried
bash -e <(wget -qO - http://fsoft.com/archivesw/script/updaterpi.sh)
but it quit at
Checking for NPM ...
========================================
NPM is not installed, skipping updates
On earlier tests I started with the access point creating script and it would give errors I couldnāt quite copy or get a picture of before the RPi would reboot. I figured would update fully and try again it doesnāt get past the above. I guess Iāll start with the ArchiveSW install script tomorrow and see what happens.
1 Like
That is exactly what it should do.
NodeJS and NPM will get installed by the install.sh
The updaterpi.sh script will only install and update the basic RPi files and then only update newly installed nodejs files.
As for the access point script, I tested it on a fresh install and had no issues. However I did make several changes during my testing. All scripts should complete with no errors on a fresh image.
I will be creating a guide to install Stretch with Desktop on a clean SD Card. Thatās going to take a few days as there is a lot to go over.
Thank you for the report. I will add a better explanation as to why it quits. And please report any issue or concern. This entire process is very complicated and very intimidating to users. I am trying to make this as easy as possible.
2 Likes
Hi @GaryFunk,
My wifi adapter (Edimax N150 model EW-7811Un) just arrived and I have another new RPi B+ to setup, AND a new solarpowered Sky with the magic coating and Hub to install which I intend to setup in full duplicate for some severe testing including remote from wifi access for some maximum distance, speed tests, vibration mount tests and more. It will be a few more days before I get to setting everything up. Then to mount beside my original sky for more comparison testing in strong windy rainy conditions.
cheers Ian 
3 Likes
Hello, boys and girls,
I have made great progress in the accesspint.sh script. It works each time I run it.
I received the Edimax N150 (EW-7811Un) this afternoon and I am happy to say it just works. I have also tested with the CanaKit Wi-Fi adapter and it just works. In fact, I had both plugged in at the same time.
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.120 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::9a4:12a7:dfe6:b912 prefixlen 64 scopeid 0x20<link>
ether 74:da:38:f6:b5:b4 txqueuelen 1000 (Ethernet)
RX packets 894 bytes 147101 (143.6 KiB)
RX errors 0 dropped 55 overruns 0 frame 0
TX packets 36 bytes 6516 (6.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.118 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::67af:39f4:99b:c9e0 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:0b:f0:f8 txqueuelen 1000 (Ethernet)
RX packets 730 bytes 130982 (127.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35 bytes 6237 (6.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.119 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::bcdb:f530:14c6:f163 prefixlen 64 scopeid 0x20<link>
ether 00:0f:60:04:67:d7 txqueuelen 1000 (Ethernet)
RX packets 2414 bytes 350050 (341.8 KiB)
RX errors 0 dropped 153 overruns 0 frame 0
TX packets 37 bytes 6347 (6.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
As you can see from the above output, it show the built-in Wi-Fi and the two adapters and actually names them wlan1 & wlan2.
I think I am actually starting to enjoy programming again. 
5 Likes
I still am running into a problem during access point setup. I was running a VNC window the last time and was able to capture this before the VNC window timed out.
After the reboot only one wlan interface is associated with anything.
Iām starting over with a freshly formatted microSD card and was wondering if this is the order you are doing the steps.
The quickest method to install ArchiveSW is to run this script from a terminal window:
bash -e <(wget -qO - http://fsoft.com/archivesw/script/install.sh)
To turn the RPi into a Wi-Fi access point:
bash -e <(wget -qO - http://fsoft.com/archivesw/script/accesspoint.sh)
To keep your RPi updated I suggest you run this script once a week
bash -e <(wget -qO - http://fsoft.com/archivesw/script/updaterpi.sh)
Iām using a RPi 3B+ and a 32GB card. I have a Logitech USB transceiver and the WiFi dongle as the only other items running on the RPi. Iām using a HDMI screen on this, not the Raspberry 7" display.
1 Like
The screenshot looks good. No issues there.
For testing you can run accesspoint.sh first and insure it sets up both interfaces correctly. It should set eth0 as the uplink and wlan0 as the access point.
I am currently working on the script to display all the interfaces and prompt the user as to which interfaces to use.
Except that is the point at which the RPi instantly rebooted! I was only able to capture this because it was on a VNC screen and it takes a while to time out. The attached screen blanks so fast I have never been able to see where the reboot occurs.
It doesnāt seem to matter when I do what, the instant reboot occurs and only one interface works after that. I have set wlan0 as AP and wlan1 as uplink. It is strange that it works for you and not for me. Iām installing NOOBS with minimal software with the desktop but I had the same result when installing the full install.
1 Like
I have removed the reboot from the script so you can see it complete. I suspect VNC is not keeping up with the script as the last few commands happen very quickly.
Please try the script again.
On a fresh NOOBS install, I let it update during final setup then ran the accesspoint.sh script and let it run the update script. It rebooted again so I re-ran the script and videoed the screen to get past the VNC delay and this is the frame just before the terminal window closed and the RPi rebooted.
1 Like
CRAP!!!
You are running an old script. I need to fix that.
Use this one.
bash -e <(wget -qO - http://fsoft.com/archivesw/script/accesspoint.sh)Ok, that one didnāt cause a reboot but still has the hostapd.txt error.
Editing /etc/dnsmasq.conf
Copying /etc/hostapd/hostapd.txt
sed: can't read hostapd.txt: No such file or directory
sed: can't read hostapd.txt: No such file or directory
sed: can't read hostapd.txt: No such file or directory
Renaming /etc/hostapd/hostapd.txt to /etc/hostapd/hostapd.conf
mv: cannot stat 'hostapd.txt': No such file or directory
Editing /etc/default/hostapd
Editing /etc/init.d/hostapd
Unmask hostapd
Removed /etc/systemd/system/hostapd.service.
Enabling hostapd
Synchronizing state of hostapd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable hostapd
Starting hostapd
Job for hostapd.service failed because the control process exited with error code.
See "systemctl status hostapd.service" and "journalctl -xe" for details.
Starting dnsmasq
Editing /etc/sysctl.conf
Editing /etc/rc.local
Setting Wi-Fi channels and power save off
Adding net.ifnames=0 to /boot/cmdline.txt
sed: can't read cmdline.txt: No such file or directory
PLEASE Reboot the RPi Now!
pi@raspberrypi:~ $
1 Like
I made changes. Please run it again my website and let me know what happens.
Looks like a DNS error somewhere. I ran it twice with the same error.
Copying /etc/hostapd/hostapd.txt
--2019-03-08 21:07:15-- http://fsoft.com/archivesw/script/hostapd.txt
Resolving fsoft.com (fsoft.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address āfsoft.comā
sed: can't read /etc/hostapd.txt: No such file or directory
1 Like
That is strange. It resolved the name to get the script but not to get the file.
go to /etc/hostapd
run sudo wget -N http://fsoft.com/archivesw/script/hostapd.txt
That worked. Strange.
pi@raspberrypi:/etc/hostapd $ sudo wget -N http://fsoft.com/archivesw/script/hostapd.txt
--2019-03-08 21:16:00-- http://fsoft.com/archivesw/script/hostapd.txt
Resolving fsoft.com (fsoft.com)... 162.253.126.169
Connecting to fsoft.com (fsoft.com)|162.253.126.169|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://fsoft.com/archivesw/script/hostapd.txt [following]
--2019-03-08 21:16:00-- https://fsoft.com/archivesw/script/hostapd.txt
Connecting to fsoft.com (fsoft.com)|162.253.126.169|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 221 [text/plain]
Saving to: āhostapd.txtā
hostapd.txt 100%[==================================>] 221 --.-KB/s in 0s
2019-03-08 21:16:01 (50.0 MB/s) - āhostapd.txtā saved [221/221]
Rerunning the script still gives some strange errors. Is there a path error in the script?
Copying /etc/hostapd/hostapd.txt
--2019-03-08 21:18:50-- http://fsoft.com/archivesw/script/hostapd.txt
Resolving fsoft.com (fsoft.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address āfsoft.comā
sed: can't read /etc/hostapd.txt: No such file or directory
sed: can't read /etc/hostapd.txt: No such file or directory
sed: can't read /etc/hostapd.txt: No such file or directory
Renaming /etc/hostapd/hostapd.txt to /etc/hostapd/hostapd.conf
1 Like
Never fix code when you have a cold. Iām too darn restless to lay in bed, so this is what happens.
Please try again.