-
-
Notifications
You must be signed in to change notification settings - Fork 495
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
DietPi-Installer | Allow WiFi-only install, workaround NetMan uninstall #2054
Comments
@mohitverma123 As an active eth0 connection is expected (https://github.com/Fourdee/DietPi/blob/master/PREP_SYSTEM_FOR_DIETPI.sh#L8), this might be a general issue on WiFi-only devices. Maybe we find a way to preserve WiFi connection (and settings) when no eth device is available. I hope |
Yep, correct 👍 Always been a problem with image creation on WiFi only devices with The only solution I found, was to run PREP, via serial connection and manually reconfigure WiFi if required. We'll need to see if we can upgrade PREP script to:
Or, (hopeful):
|
Ref: https://wiki.debian.org/WiFi/HowToUse
|
I successfully installed DietPi via preparation script on a WiFi-only device with direct console access. netman however was not pre-installed on the fresh Debian image, installed via Debian netboot installer.
So generally we have two possibilities:
Then testing is required, if connection can stay active, when installing DietPi default network packages first, configure them (/etc/network/interfaces), in case |
Additionally: connman: #1285 (comment) General issue, even when we manually pre-configure the network with ifupdown, if uninstalling netman or connman always drops the connection, the SSH connection breaks which again breaks the installer, so re-connecting is not done anymore. This only works from a screen session which goes on in the background and can be reattached to. So currently indeed, if no local console (keyboard+monitor) is available, a serial console is required to reliably have the installer finish, at least when SSH is only possible via WiFi. Not sure if Ethernet connections, controlled by netman or connman, can break as well? At least I never faced that. |
Orange pi lite has only WIFI and not an ethernet port, hence wifi is only possible network access for it.
The install script removes wifi (even after we select Yes, I need wifi modules)
The text was updated successfully, but these errors were encountered: