Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: Wildcat on October 21, 2021, 04:06:46 PM
-
Hi all,
Total Noob here with RPI4+ 8GB RAM and wifi.
I got the CLI working fine and played around.
Now I'm trying to get the GUI and WIFI working.
I need to find out the proper steps, (and which TCZs to install).
Any help is greatly appreciated.
-
Hi Wildcat
Welcome to the forum.
For a GUI, try installing Xorg, flwm, aterm, and wbar.
-
Thank you Rich! I have a GUI running now.
Now, to the second part of my question: how do I activate the WIFI?
Thanks again!
-
Hi Wildcat
I guess the first thing we need to know is what kind of wireless device you have. Install usbutils and run:
lsusb > lsusb.txt
Then either post the contents of lsusb.txt or attach lsusb.txt to your next post.
-
To use the RPi3/4 built-in wifi:
* load the firmware-rpi-wifi extension (this must be loaded first)
* load the wifi extension
* execute "sudo wifi.sh"
-
Thank you Juanito and Rich for your reply.
iwconfig recognizes the builtin wifi, but is unable to connect to my router.
The issue is that the router has a hidden ssid (I know it's not making the network more secure).
In RPI OS I would normally edit a wpa_supplicant.conf file as follows:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
country=US
update_config=1
network={
scan_ssid=1
ssid="MY Hidden Router Name"
psk="My password"
key_mgmt=WPA-PSK
}
From what I found on the internet, I should modify a couple of lines:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=staff
But I was unable to find wpa_supplicant.conf
Can you instruct me on the proper procedure in PiCore?
Thanks again for the kind help!
-
Hi Wildcat
I don't see wpa_supplicant.conf listed in the wpa_supplicant extension. If you create a wpa_supplicant.conf
file, you can tell wpa_supplicant where to find it on startup using the -c option:
wpa_supplicant -c /Path/To/wpa_supplicant.conf
-
the wifi.sh script provided will not work with hidden wifi. You will need to manage the connection manually.
Write your wpa_suppliant.conf manually, save it and make sure it's backed up.
Then write a script to start wpa_supplicant and manage dhcp.
-
:D It works! :D
The main steps are:
1. Create hashed password for your network (temporarily in your home directory or wherever you choose):
wpa_passphrase [your_wifi_SSID] [your_plaintext_passphrase] > wpa_supplicant.conf
2. Edit the resulting file (wpa_supplicant.conf), using your favorite editor. It should end up looking like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=staff
country=US (change to your own country 2 letter code)
update_config=1
network={
scan_ssid=1 (use this line only for hidden SSID)
ssid="MY network Name".
#psk="My plain text password" (remove this line to maintain secrecy)
psk="My hashed password" (This is the result of wpa_passphrase)
key_mgmt=WPA-PSK
}
3. Copy the file to it's destination, set ownership and copy to /opt/.filetool.lst as follows:
sudo cp wpa_supplicant.conf /etc/
sudo chown root.root /etc/wpa_supplicant.conf
sudo chmod 600 /etc/wpa_supplicant.conf
echo "etc/wpa_supplicant.conf" >> /opt/.filetool.lst
4. Activate wpa_supplicant (use the exact line - do not substitute anything):
sudo /usr/local/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
---- Continue below ----
-
---- Continued from above ----
5. Activate dhcp (use the exact line - do not substitute anything):
sudo /sbin/udhcpc -b -i wlan0 -x hostname $ (hostname) -p /var/run/udhcpc.wlan0.pid
6. If all is well, you should have wifi working. If not, the original post by kissmurphy has more details that may be helpful:
(http://forum.tinycorelinux.net/index.php/topic,23445.msg147221.html#msg147221)
7. When everything works copy the commands from step 4 to /opt/bootlocal.sh. This way wifi will run on startup:
echo "/usr/local/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf" >> /opt/bootlocal.sh
8. Copy the commands from step 5 to /opt/bootlocal.sh. This way dhcp will run on startup:
echo "/sbin/udhcpc -b -i wlan0 -x hostname $(hostname) -p /var/run/udhcpc.wlan0.pid" >> /opt/bootlocal.sh
9. The final instruction will make the above instructions persistent (back up, next startup the system will remember these instructions):
filetool.sh -b
Thanks again for your kind help!
[Edit]: Removed space from between the $ sign and (hostname). Rich
-
Hi all,
In the previous post I had to insert a space character in step 5 and step 8 between the $ sign and (hostname) right after it, because the server refused to accept them next to one another.
If you need to use this procedure, kindly remove the space when entering these lines in your machine.
Perhaps an experienced user could instruct me how to enter such information?
Thanks
WildCat
-
Hi Wildcat
... Perhaps an experienced user could instruct me how to enter such information? ...
I'm afraid the forum suffers from multiple personality disorder.
Sometimes it takes issue with something you write and other
times you can write the exact same thing and it accepts it.
I removed the added space from your post and it accepted it.
I've run into the issue myself. When it happens, I save a copy
of my post in an editor. Then I copy a few lines at a time and
hit Preview to narrow down the culprit.