Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WiFi not working / SSH on LAN not enabled #570

Open
mortomanos opened this issue Jun 4, 2024 · 6 comments
Open

WiFi not working / SSH on LAN not enabled #570

mortomanos opened this issue Jun 4, 2024 · 6 comments

Comments

@mortomanos
Copy link

mortomanos commented Jun 4, 2024

What were you doing?

Flashed the recent version of FullPageOS 0.14.0 on an SD card, configured the 7" display correctly, configured WiFi correctly

What did you expect to happen?

WiFi should connect and should get the DHCP registration, SSH login via IP should work

What happened instead?

WiFi did not work (no IP address assigned), so I tried to boot with LAN connected, got an IP address, but SSH was not enabled on this IP address
The proof that LAN works is that I can connect via VNC Viewer to the IP address and can remote control the Pi.

Was there an error message displayed? What did it say?

no error message

Version of FullPageOS?

Flash from 0.14.0: https://unofficialpi.org/Distros/FullPageOS/nightly/2024-03-31_2024-03-15-fullpageos-bookworm-armhf-lite-0.14.0.zip

Screenshot(s) showing the problem:

n/a

If you are building FullPageOS - provide a build.log that is created for the build

@guysoft
Copy link
Owner

guysoft commented Jun 4, 2024

How are you setting up wireless?

Note that due to a change in RpiOS wpa_supplicant autoconfigure
I am not sure what we can do about it
raspberrypi/bookworm-feedback#72

@guysoft
Copy link
Owner

guysoft commented Jun 4, 2024

This might be a solution:
raspberrypi/bookworm-feedback#72 (comment)

@mortomanos
Copy link
Author

The problem is that if I cannot login to the shell, I cannot do anything on the filesystem...

@mortomanos
Copy link
Author

I forgot that there might be a local console, so I attached a keyboard and switched to console 1 and was able to login. I noticed that no sshd was running. I then saw that there is a sshswitch service which looks for /boot/firmware/ssh (which was not present). I cannot say for sure why this did not work either after creating /boot/firmware/ssh, but I had to enable ssh manually - now at least I can logon from remote on LAN and can continue to try getting WiFi working.

@mortomanos
Copy link
Author

I can confirm that the solution presented in the comment above (adding a configuration file for NetworkManager) does work for me. Maybe it would make sense to just do it the same way, have a configuration file in /boot and copy it in the destination (and change the access rights to 0600 which is important).

@guysoft
Copy link
Owner

guysoft commented Jun 6, 2024

That file should be created in the build process here:
https://github.com/guysoft/CustomPiOS/blob/devel/src/modules/base/start_chroot_script#L120

I can also see that in 0.14.0 RC1 the line did execute like this

 + touch /boot/firmware/ssh

Also, if I open the image on my computer (using the chroot_in_to_image.sh script), I see the ssh file in place

$ ls -l  mount/boot/firmware/ssh 
-rwxr-xr-x 1 root root 0 Mar 31 12:37 mount/boot/firmware/ssh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants