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

Asus TB | Onboard WiFi not functional #1760

Closed
Fourdee opened this Issue May 9, 2018 · 36 comments

Comments

Projects
None yet
4 participants
@Fourdee
Copy link
Collaborator

Fourdee commented May 9, 2018

@ghost

This comment has been minimized.

Copy link

ghost commented May 10, 2018

@Fourdee this is exactly what happens to me #1444 with the Image you've hosted on yours server for downloading about 3 mnths ago. This is a failure at the used kernel in your image from 2.0.4. The actual kernel which should go without a problem is 4.4.120 & 4.4.129.
I did compile myself an armbian image and transformed it with DIetPi.
At this, the WiFi is working without any hickups and problems. Stable!

Therefore i'd suggest, you should even compile an armbian image only with 4.4.xx kernel switch to "nightly" build and than do firmware update within armbian-config. Reboot and login.
After this you could use the PREP-Script and everything works. You could also built it without switching to nightly. Than you get only 4.4.120 with a lot of fixes for WiFi & MaliGPU.

This is how i got mine TB SBC from ASUS working stable on DietPi.

Beware of using the 4.14.xx kernels, as they aren't stable atm with WiFi.

Kind regards.

@MichaIng

This comment has been minimized.

Copy link
Owner

MichaIng commented May 10, 2018

@SuBLiNeR
Okay, so it's a kernel issue somewhere between 4.4.16 and 4.4.119.

Is there a chance for soon Tinker-OS with kernel upgrade to >= 4.4.120 or current kernel sources from their side?

@ghost

This comment has been minimized.

Copy link

ghost commented May 10, 2018

@MichaIng It looks like they merged sources onto theirs git with those fixes and will release a more lately kernel and OS higher than 2.0.5.

'"Default" kernel 4.4 was moved to the Rockchip repository, which provides a huge number of bugfixes/adjustments/new drivers. '

Atm it is best to transform an armbian install to dietpi after self-compiling an armbian-image.

@FaserF

This comment has been minimized.

Copy link

FaserF commented May 10, 2018

Same issue with my TB.

@ghost

This comment has been minimized.

Copy link

ghost commented May 10, 2018

@FaserF Just use this image (https://dl.armbian.com/tinkerboard/archive/Armbian_5.41_Tinkerboard_Debian_stretch_default_4.4.119.7z) and transform it into DietPi with the Prep-Script while connected to ethernet - before using the PREP-Script, use armbian-config to upgrade it to latest 'firmware'. finally than you could run the script as decribed -> #1285

@MichaIng

This comment has been minimized.

Copy link
Owner

MichaIng commented May 10, 2018

Okay, hard to say when next Tinker-OS release will be and we do not release DietPi images based on ARMbian.

Following possibilities:

@SuBLiNeR
Does WiFi work on clean Tinker-OS, as I can't believe them serving a faulty kernel as stable release?
In this case we would need to find out about the difference of their WiFi implementation.

Then hope for soon release of Tinker-OS 2.0.6 with required fix 😄.

@ghost

This comment has been minimized.

Copy link

ghost commented May 10, 2018

@MichaIng the funny thing about it is, as soon as you using anything below 2.0.4, it works!

Second thing is what i tried was following, 4days ago.

Install TOS 2.0.1, boot it up only while on eth0. go into terminal and run the PREP–script ... everything runs well than.
After Dietpi is booting twice times up, you should be able to switch from eth0 to wlan0 and it should wotk after a reboot again.

I than chosed for myself to try it with armbian.... it works. the main difference was, that my kernel is 4.4.126 than.

Again, tha base image from armbian with a self compiled kernel aka 4.4.120 and up, works oob.

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented May 10, 2018

Resolved with our latest DietPi image, based on Tinker OS 2.0.5: https://dietpi.com/downloads/images/DietPi_ASUSTB-ARMv7-Stretch.7z
Cause = kernel.
image

Completed.

@Fourdee Fourdee closed this May 10, 2018

@Fourdee Fourdee referenced this issue May 13, 2018

Merged

v6.8 #1771

Fourdee added a commit that referenced this issue May 13, 2018

Merge pull request #1771 from Fourdee/testing
**v6.8**
(13/05/18)

**Changes / Improvements / Optimizations:**

General | All future DietPi images (v6.8 and onwards), now has serial console enabled by default for the 1st run setup. It will be disabled automatically after first run setup to save on resources, unless 'CONFIG_SERIAL_CONSOLE_ENABLE=1' is set in dietpi.txt: #1759

General | DietPi.com website: Server has been upgraded to Debian Stretch, featuring HTTPS redirect.

General | FBset is no longer a pre-req package for DietPi systems. This will be removed on fresh installations (not existing, to avoid any package conflicts): #1716

General | DietPi login script and globals init moved to /etc/profile.d/99-dietpi-login.sh. Ensuring any user on system with sudo permissions can load them. Global commands are also now supported across multiple users, eg: either 'sudo -i G_AGI pacakge' or 'G_SUDO G_AGI package': #1477

General | G_WHIP*: Improved scaling detection based on character count and line count. We now also calculate character count per line, to determine if additional lines are required against X. In other words, it should be a more 'snug' fit :) #1740

DietPi-Automation | 'AUTO_SETUP_RAMLOG_MAXSIZE' added to dietpi.txt. Sets max /var/log tmpfs size during 1st run. Requires v6.8 or higher image.

DietPi-Config | Native PC > Soundcard: 'firmware-intel-sound' is now installed automatically for Intel based CPUs.

DietPi-Drive_Manager | Added ability to adjust reserved blocks percentage on ext4 file system: #1662

DietPi-Drive_Manager | Added ability to check and optionally repair a filesystem. Many thanks to MonZon for the feature request! rootFS and /boot checks will be added in v6.9, currently additional drives are supported by this feature #1740

DietPi-Drive_Manager | Enabled access for virtual machines: #1765

DietPi-LetsEncrypt | Lighttpd: SSL configuration upgrade according to Mozillas SSL generator: https://mozilla.github.io/server-side-tls/ssl-config-generator/?server=lighttpd-1.4.35&openssl=1.0.1t&hsts=yes&profile=intermediate

DietPi-LetsEncrypt | Minor code and error handling improvements, as well increasing transparency of what the script is currently doing: #1738

DietPi-Process_tool | Rewrite of save file, to allow for stringed entries. The save file will be cleared during the update, to support this feature: #1750

DietPi-Process_tool | Added Plex Media Server to process tool, however, transcoding will not be affected by this: #1750 (comment)

DietPi-Set_Hardware | Allo Piano firmware is now installed on demand and will be removed on update, if not chosen as soundcard: #1656

DietPi-Software | AmiBerry (Amiga Emulator): Updated to v2.19, contains bug fixes and improvements: #1707 (comment)

DietPi-Software | Chromium: No longer requires a desktop and can be installed as a lightweight single use program, using dietpi-autostart to run under kiosk mode. Many thanks to @AYapejian! 720p is the default window size, please see '/var/lib/dietpi/dietpi-software/installed/chromium-autostart.sh' for full options when running under 'dietpi-autostart' mode: #1737

DietPi-Software | Readymedia (MiniDLNA): Removed ALSA pre-req as it is not required. Many thanks to @bokiroki: #1712

DietPi-Software | Pi-hole: Enabled support for FTLDNS: #1696

DietPi-Software | Gitea: Updated to latest version (1.4), for new installations only. Many thanks to @yumiris: #1723

DietPi-Software | PHPBB3: Latest version update (3.2.2), for new installations only.

DietPi-Software | Docker: Enabled for ARMv8 devices: #1736

PREP | G_HW_MODEL: Added for 'OrangePi PC Plus'. Many thanks to @SuBLiNeR: #1704

PREP | Optimized rootfs re-partition and resize. This will reduced the required initial system reboot count by one. Will take affect from official v6.8 DietPi images and onwards.

**Bug Fixes:**

General | Remote SCP/Rsync fix when running under 'dietpi' user: #1703

General | ASUS TB: Resolved issues with onboard WiFi not being detected. Our latest image is required for this fix due to kernel: #1760

General | Sparky SBC: Unmute USB-DAC audio fix applied during boot. Many thanks to @sudeep.

DietPi-Config | RPi onboard sound: Resolved an issue where changing from 3.5mm output back to auto, would not have any effect.

DietPi-Config | Resolved an error when selecting 'Sample Rate' CPU option.

DietPi-Drive_Manager | Resolved issues with incorrect detection of drives and mounts on Debian Stretch: #1748

DietPi-Drive_Manager | Resolved issues RootFS transfer being stuck in a endless rsync loop: #1748

DietPi-Drive_Manager | Resolved an issue where setting read only/write modes had no effect on fstab entries. This affected recent images only: #1758

DietPi-Justboom | ALSA must now be installed, and /etc/asound.conf must exist, before this application can be run.

DietPi-LetsEncrypt | Now skips any webserver configuration edit, if CertBot execution returns with error: https://dietpi.com/phpbb/viewtopic.php?f=11&t=1909

DietPi-Software | Pi-SPC: PATH fix for sds.sh.

DietPi-Software | WiringPi: Now installed to '$HOME/WiringPi', previously this would be wiringPi-HEAD-8d188fa.

DietPi-Software | XRDP: Resolved an issue with blue screen running under Xorg. VNC4 is now installed by default, and the new connection method is 'Xvnc': #1727 (comment)

DietPi-Software | AmiBerry: Fix for standard boot SDL2 keyboard leaking to background. Please note fast boot is still affected by the SDL2 keyboard leak: #1707

**Allo GUI v7:**
- Resolved errors with swapfile display/change.
- Resolved issues with CPU gov not being correctly applied.
@FaserF

This comment has been minimized.

Copy link

FaserF commented May 14, 2018

Issue still exists for me on the newest image.
After a reboot it says connected with 0 Mbit and I have no internet. Before the reboot it worked well.
I've tried disabling network, forgetting the wifi network, nothing worked for me.

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented May 15, 2018

@FaserF

After a reboot it says connected with 0 Mbit and I have no internet. Before the reboot it worked well.
I've tried disabling network, forgetting the wifi network, nothing worked for me.

Strange, could be a range issue, have you tried moving the device closer to the WiFi router? What was the speed/dB levels before the reboot?

@FaserF

This comment has been minimized.

Copy link

FaserF commented May 15, 2018

@Fourdee sorry I dont remember that. I am now using my TB with LAN and its working well.
It's just strange that this happened even with your new fix.

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented May 15, 2018

@FaserF

Confirmed bug, able to replicate, i'll reopen for investigations:

root@DietPi:~# dmesg | grep wlan
[    2.176996] usbcore: registered new interface driver rndis_wlan
[    6.182743] [WLAN_RFKILL]: Enter rfkill_wlan_init
[    6.182906] [WLAN_RFKILL]: Enter rfkill_wlan_probe
[    6.182932] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6212
[    6.182937] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    6.182942] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    6.182948] of_get_named_gpiod_flags: can't parse 'WIFI,poweren_gpio' property of node '/wireless-wlan[0]'
[    6.182954] of_get_named_gpiod_flags: can't parse 'WIFI,reset_gpio' property of node '/wireless-wlan[0]'
[    6.182976] of_get_named_gpiod_flags: parsed 'WIFI,host_wake_irq' property of node '/wireless-wlan[0]' - status (0)
[    6.182982] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,host_wake_irq = 150, flags = 0.
[    6.182987] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio
[    6.182993] [WLAN_RFKILL]: Exit rfkill_wlan_probe
[    8.498510] RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=f0:03:8c:05:d7:05
[    9.884527] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.347086] RTL871X: rtw_set_802_11_connect(wlan0)  fw_state=0x00000008
[   11.376316] RTL871X: rtw_cfg80211_indicate_connect(wlan0) BSS not found !!
[   11.376424] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
root@DietPi:~# lsmod
Module                  Size  Used by
8723bs               1232896  0

Unable to bring up adapter, even after enabling modules

/DietPi/dietpi/func/dietpi-set_hardware wifimodules enable
root@DietPi:~# ifup wlan0
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not permitted.
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
ifup: failed to bring up wlan0

@Fourdee Fourdee reopened this May 15, 2018

@Fourdee Fourdee modified the milestones: v6.8, v6.9 May 15, 2018

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented May 15, 2018

Previously, this also occurred on other kernels:

current with 2.0.5 tinker OS

root@DietPi:~# uname -a
Linux DietPi 4.4.71+ #1 SMP Thu Feb 22 18:23:31 CST 2018 armv7l GNU/Linux

1.8 tinker OS based is reported fine:
#1444 (comment)


Page offline (blank) https://www.asus.com/uk/Single-Board-Computer/Tinker-Board/HelpDesk_Download/

@Fourdee Fourdee modified the milestones: v6.9, v6.10 Jun 4, 2018

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 15, 2018

Any progress here ?

@MichaIng

This comment has been minimized.

Copy link
Owner

MichaIng commented Jul 17, 2018

@Fourdee
Just to not forget, here seems to be still something done. Hmm G_CONFIG_INJECT '^8723bs' '8723bs' /etc/modules would just change something, if the current line is 8723bs<and_something_else_here>, is this the case/intention?

@MichaIng MichaIng reopened this Jul 17, 2018

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Jul 17, 2018

@MichaIng

would just change something, if the current line is 8723bs<and_something_else_here>, is this the case/intention?

On the ASUS TB, the modules file is blank, so we just need to add this by default:

root@DietPi:~# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

8723bs

Then our blacklist overrides it, when WiFi is disabled in DietPi:

root@DietPi:~# cat /etc/modprobe.d/disable_wifi.conf
blacklist bcmdhd
blacklist 8723bs
blacklist ap6211
blacklist brcmutil
blacklist brcmfmac
blacklist cfg80211

@Hax4us
Apologies for the delay, is this still an issue you are experiencing?

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Jul 17, 2018

🈯️ Fresh install + WiFi test after reboot:

root@DietPi:~# lsmod
Module                  Size  Used by
8723bs               1232896  0

root@DietPi:~# dmesg | grep wlan
[    2.176142] usbcore: registered new interface driver rndis_wlan
[    5.762855] [WLAN_RFKILL]: Enter rfkill_wlan_init
[    5.763466] [WLAN_RFKILL]: Enter rfkill_wlan_probe
[    5.763554] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6212
[    5.763581] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    5.763606] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    5.763638] of_get_named_gpiod_flags: can't parse 'WIFI,poweren_gpio' property of node '/wireless-wlan[0]'
[    5.763669] of_get_named_gpiod_flags: can't parse 'WIFI,reset_gpio' property of node '/wireless-wlan[0]'
[    5.763759] of_get_named_gpiod_flags: parsed 'WIFI,host_wake_irq' property of node '/wireless-wlan[0]' - status (0)
[    5.763788] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,host_wake_irq = 150, flags = 0.
[    5.763811] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio
[    5.763839] [WLAN_RFKILL]: Exit rfkill_wlan_probe
[    7.467751] RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=80:c5:f2:46:e1:81
[    9.076056] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   10.645049] RTL871X: rtw_set_802_11_connect(wlan0)  fw_state=0x00000008
[   10.747431] RTL871X: rtw_cfg80211_indicate_connect(wlan0) BSS not found !!
[   10.747520] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

root@DietPi:~# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

8723bs

root@DietPi:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
    link/sit 0.0.0.0 brd 0.0.0.0
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 88:d7:f6:c2:f0:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.22/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::8ad7:f6ff:fec2:f042/64 scope link
       valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 80:c5:f2:46:e1:81 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.23/24 brd 192.168.0.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::82c5:f2ff:fe46:e181/64 scope link
       valid_lft forever preferred_lft forever

Dmesg diff: https://www.diffchecker.com/UB3Zhvn9

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Jul 17, 2018

Notes:

  • Connects fine, but this appears to be the issue for @Hax4us OnDeAuth
IPv6: ADDRCONF(NETDEV_CHANGE):  wlan0: link becomes ready 
RTL871X:  OnDeAuth(wlan0) reason=3,  ta=9e:df:b1:00:81:a7, ignore=0
RTL871X:  OnDeAuth(wlan0) reason=3,  ta=9e:df:b1:00:81:a7, ign

https://bbs.archlinux.org/viewtopic.php?id=164279

https://superuser.com/questions/974017/ubuntu-wlan0-authenticates-and-then-drops

@Hax4us
Try setting the following, then reboot system. Default is GB for DietPi systems, change this if you have set a different country code.
G_CONFIG_INJECT 'REGDOMAIN=' 'REGDOMAIN=GB' /etc/default/crda

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 18, 2018

@Fourdee still not working , maybe it will work after fresh installation ? Where is latest image ?

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 18, 2018

Still old SET failed blah blah. error

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Jul 18, 2018

@Hax4us

Latest image: https://dietpi.com/downloads/images/DietPi_ASUSTB-ARMv7-Stretch.7z
However, the fix is only applied during the DietPi update, so you'll need to use ideally ethernet for the first run setup, then switch to WiFi once updated.

@Fourdee Fourdee modified the milestones: v6.12, v6.13 Jul 18, 2018

@Fourdee Fourdee referenced this issue Jul 18, 2018

Merged

v6.12 #1938

Fourdee added a commit that referenced this issue Jul 19, 2018

Merge pull request #1938 from Fourdee/testing
**v6.12**
(19/07/18)

**Changes / Improvements / Optimizations:**

DietPi-Drive_Manager | Samba/CIFS mounting: Now automatically uses the highest available CIFS version supported on client and server: #1893 (comment)

DietPi-Software | Jackett: Now runs as its own user, and, from the /opt/jackett directory, for new installations only. Many thanks to @userdeveloper98 for contributing this improvement: #1895

DietPi-Software | MiniDLNA: Now uses a SystemD service, also updates its library during service start.

DietPi-Software | JRiver: Removed and no longer available for installation: #1080 (comment)

DietPi-Software | Various titles: Now run under their own system user account, with limited permissions (previously root): #1877 (comment)

DietPi-Software | SABnzbd: Language packs are now installed by default: #1917 (comment)

DietPi-RAMlog | Increased the max size of /var/log to 50MB by default (previously 20MB). This should prevent 0 free space errors for excessive log file usage. Pi-Hole max logfile size is now 50MB/3 (16MB~) for high usage with daily stats support: pi-hole/pi-hole#2270 (comment) | #1923

DietPi-RAMlog | Service is now disabled when RAMlog mode is not selected: #1924

**Bug Fixes:**

General | Resolved an issue where cron jobs, containing DietPi scripts, failed: #1923

General | Resolved an issue on ARM64 + Jessie with APT, due to debian-security removing suppport and packages for those devices. If you experience this issue, and are unable to update DietPi, please see : #1915

General | Resolved an issue where NFSv3 network drives could not be mounted: #1898

DietPi-Config | ASUS TB: Resolved loss of WiFi device after a reboot: #1760

DietPi-Drive_Manager | Resolved an issue where the program could remove a non-empty directory in rare situations.

DietPi-Software | Resolved a potential Mono instability issue with Radarr, Sonarr and Jackett, due to using '--optimize=all --server'. This has now been removed for new installations. Many thanks to @hellfirehd for debugging/testing and @Taloth for dev insights: #1896

DietPi-Software | Mono: Temp mono files are now cleared from memory once installed, preventing out of memory errors for additional software installs afterwards: #1877 (comment)

DietPi-Software | Xserver: Resolved rarely occuring uninstall issus by not purging dependencies, but leaving them for autoremove: #1921

DietPi-Software | MineOS: Resolved failed installation due to incompatibilities with nodejs v10. v8 is now installed: #1880

DietPi-Update | Resolved an issue where incorrect version would be displayed, once update was completed. This is due to '| tee' on a function, making var changes local: #1877 (comment)
@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 21, 2018

@Fourdee I can confirm that same problem is exist in my TB DietPi 6.12

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 21, 2018

It worked only first time after flashing new image and I did some things like installing some tools and LXDE ,and in each reboot WiFi was working but after shutdown same problem ......😑😑

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 21, 2018

What the hell is going on in my TB now after reboot it works but idk why and how, well I will report back in case of same problem ..

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 21, 2018

Again same problem. It is very unstable for me :(

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Jul 23, 2018

@Hax4us

It worked only first time after flashing new image and I did some things like installing some tools and LXDE ,and in each reboot WiFi was working but after shutdown same problem ......😑😑

Apologies for the delay. Thanks for confirming issue still exists.

Apologies, however, i'am out of ideas as to why this is occurring on your device. I am unable to replicate the issue here with TB DietPi 6.12, and, everything appears in order on your system (excluding #1760 (comment)).

I'am unsure how to debug this further (#1760 (comment)), and, it may be some time before either myself, or comminuty support can find a solution.

The only thing I can suggest, is to try the official TinkerOS image (if not done already), and, just verify if the loss of WiFi on reboot issue exists with that (eg: could be a hardware issue?).

@Hax4us

This comment has been minimized.

Copy link

Hax4us commented Jul 27, 2018

@Fourdee thnx for your all work and now I have armbian in my tinker and there is no WiFi issue
But I have one doubt , can abnormal (sudden) shutdown be a culprit ?
Abnormal shutdown can arise any problem for WiFi ?

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Jul 28, 2018

@Hax4us

can abnormal (sudden) shutdown be a culprit ?

Is possible. A hard power cycle will most likely cause filesystem corruptions, which could affect various areas of the systems software (and therefore hardware).

So just to confirm:

I've done the same above test multiple times and i'am unable to replicate on my local devices. The /etc/modules fix was successful at least my end.

@Fourdee

This comment has been minimized.

Copy link
Collaborator Author

Fourdee commented Aug 13, 2018

No response, unable to replicate, marking as closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.